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. 
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.txtsymdev=000292600092:06D5 symdev=000000004960:0807symdev=000292600092:06D6 symdev=000000004960:0808symdev=000292600092:06D7 symdev=000000004960:0809symdev=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.
Need help on Federated Live Migration to understand an error