Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1137

June 8th, 2011 02:00

Need help on Federated Live Migration to understand an error

Hi,

I am trying to setup a demo with Federated Live Migration (thick-to-thin) and I reach an error I am not able to fix.
Basically, the environment consists in 1 DMX-4 (Enginuity 5873) and 1 VMAX-2 (Enginuity 5875), and an AIX host.

The DMX-4 has 4 thick LUNs for the migration and the VMAX 4 thin LUNs (I also tried with 4 thick LUNs, but this fails the same way).


I have tried 2 different scenarii which gave the same error:
Case1: using the SMC GUI and the FLM wizard
Case2: using SYMCLI directly on the AIX host with the Solution Enabler installed on this AIX host.
I have followed the white papers and other documents I have found on FLM, but
in both cases I got this error when creating the FLM session:

# cat FLM_pairs.txt
symdev=000292600092:06D5 symdev=000000004960:0807
symdev=000292600092:06D6 symdev=000000004960:0808
symdev=000292600092:06D7 symdev=000000004960:0809
symdev=000292600092:06D8 symdev=000000004960:080A

# symrcopy -f  FLM_pairs.txt create -pull -migrate -host_type AIX -name flm -v

Execute 'Create' operation for the 4 specified devices
in device file 'FLM_pairs.txt' (y/ ) ? y

'Create' operation execution is in progress for the device list
in device file 'FLM_pairs.txt'. Please wait...


STARTING a REMOTE Copy CREATE (PULL) (HOT) (NODIFFERENTIAL) (NOCOPY) (DONOR UPDATE) (MIGRATE) (HOST_TYPE=AIX) (HBA_TYPE=N/A) (MP_TYPE=N/A)

SELECTING Control device - Remote devices:

  (Ctl)Sym: 000292600092 Device: 006D5 -   LUN WWN: 60060480000000004960533030383037 - [SELECTED]
  (Ctl)Sym: 000292600092 Device: 006D6 -   LUN WWN: 60060480000000004960533030383038 - [SELECTED]
  (Ctl)Sym: 000292600092 Device: 006D7 -   LUN WWN: 60060480000000004960533030383039 - [SELECTED]
  (Ctl)Sym: 000292600092 Device: 006D8 -   LUN WWN: 60060480000000004960533030383041 - [SELECTED]

STARTING a RCOPY 'CREATE' operation.

  (Ctl)Sym: 000292600092 Device: 006D5 -   LUN WWN: 60060480000000004960533030383037 - [loc_dir:07E, rem_num:0, rem_sts:0x25SANCOPY_DEV_FLM_NOT_SUPPORTED ]
  (Ctl)Sym: 000292600092 Device: 006D5 -   LUN WWN: 60060480000000004960533030383037 - [SYMAPI_C_RCOPY_DISCOVER_ERROR]

The Rcopy 'CREATE' operation FAILED. (SYMAPI_C_RCOPY_DISCOVER_ERROR)

An rcopy remote device discover error occurred

The good news is that the pairs are detected as well as the WWN matching the devices ID I gave in the FLM_pairs.txt file, but the 'create' operation fails.


Can someone help me what to fix in my environment to avoid this error?

Thanks a lot.

Message was edited by: SymmetrixForumsModerator Changed WWNs.

3 Posts

June 10th, 2011 13:00

I am also trying to do FLM setup for first time and have been stuck on same error.

I reviewed and re-reviewed my setup, and had an EMC SR opened. They pointed me to the fact that the donor array needs an e-pack (Enginuity patch) to support FLM.   I'm attempting with Gen 6 & 7 Symms, and there are specific microde releases and e-packs required.

For your case..   5773 code would need an e-pack request put in to bring them to 5773_163/0006.

It does not state specifically about microcode levels in the FLM support matrix, so I recommend you discuss with your support team to review what you have, and determine exactly what you need to support FLM in your environment.

448 Posts

June 8th, 2011 05:00

Make sure that the V-max FA's are zoned to all the FA's on the donor array that the luns are mapped to and that the V-max is masked to those luns on all the FA's.

I received a similar error and I had zoned the V-max but forgotten to mask the devices to the V-max WWN's.

35 Posts

June 8th, 2011 07:00

Hi,

Thanks for the answer, however it does not seem to be the root cause of my issue.
Here is the Masking/Mapping info of my configuration:

Arch_FLM.bmp

Any other idea? Thanks

448 Posts

June 8th, 2011 10:00

Looking at the error I think it either does not like somethign about how you are setup; it has to be done in a very specific order, or for some reason it doesnt think you are licensed for FLM.  You are running a high enough version of powerpath to support FLM right?

June 8th, 2011 13:00

I think you forgott to mention the  -hba_type and -mpio_type.when  you are creating session.

symrcopy -sid xxxx create -f -hot -pull -migrate -host_type -hba_type -mpio_type

35 Posts

June 8th, 2011 14:00

Hi

Thanks for the answer, however on an AIX host these arguments seem not mandatory, but I will try that first time tomorrow. We never know!

Thanks

448 Posts

June 9th, 2011 08:00

You are correct those are options and are not required.

Alhtough the error seems to point at the discovery aspect of the devices so it doesnt like something about that.

35 Posts

June 16th, 2011 02:00

Hi,

Thanks for this tip, it worked indeed. I used the latest microcode update for the DMX-4 and the issue was fixed.

So now, I can go to my next question on FLM, see the new thread I opened.

Thanks

No Events found!

Top