Can you please download the following script and execute on Client LPAR and probable destination VIOS. 1. first on client LPAR to get list of target ports 2. and then on probable destination VIOS to verify if they can host IO for the Client LPAR or not. Please let me know of any suggestions or improvements. Please send all screen outputs of running the script on Client LPAR and destination VIOS for analysis. Sample Output : Client LPAR : ================================================================= # /usr/local/bin/lpmwwpns Version : Sep 1 2015 Date : Wed Sep 9 16:29:28 CDT 2015 Client LPAR hostname : nimtb187 fcs0 C0507600091D002A host_name: vios1_nimtb184 host_device: vfchost4 --- Active C0507600091D002B --- Inactive List of Storage ports mapped to Client: nimtb187 on Active WWPN fcs1 C0507600091D0024 host_name: vios2_nimtb185 host_device: vfchost4 --- Active C0507600091D0025 --- Inactive List of Storage ports mapped to Client: nimtb187 on Active WWPN fcs2 C0507600091D0026 host_name: vios1_nimtb184 host_device: vfchost5 --- Active C0507600091D0027 --- Inactive List of Storage ports mapped to Client: nimtb187 on Active WWPN fscsi2|0000000000651800|204400a0b82697ac|200400a0b82697ac fscsi2|0000000000651f00|204500a0b82697ac|200400a0b82697ac fcs3 C0507600091D0028 host_name: vios2_nimtb185 host_device: vfchost5 --- Active C0507600091D0029 --- Inactive List of Storage ports mapped to Client: nimtb187 on Active WWPN fscsi3|0000000000651a00|202400a0b82697ac|200400a0b82697ac fscsi3|0000000000651d00|202500a0b82697ac|200400a0b82697ac Copy file /tmp/lpm_cli_info file on to destination VIOS at same location to verify NPIV SAN Zoning. or copy paste above info into file /tmp/lpm_cli_info on destination VIOS. Then, execute same script /usr/local/bin/lpmwwpns on VIOS in oem_setup_env shell ================================================================= VIOS : ================================================================= Working.... Version : Sep 1 2015 Date : Wed Sep 9 16:06:51 CDT 2015 on VIOS nimtb184, targets zoned for inactive WWPNs from client nimtb187 WWPN C0507600091D002B WWPN C0507600091D0025 WWPN C0507600091D0027 fscsi1|0000000000651800|204400a0b82697ac|200400a0b82697ac fscsi1|0000000000651f00|204500a0b82697ac|200400a0b82697ac fscsi2|0000000000651800|204400a0b82697ac|200400a0b82697ac fscsi2|0000000000651f00|204500a0b82697ac|200400a0b82697ac fscsi4|0000000000651800|204400a0b82697ac|200400a0b82697ac fscsi4|0000000000651f00|204500a0b82697ac|200400a0b82697ac WWPN C0507600091D0029 fscsi1|0000000000651a00|202400a0b82697ac|200400a0b82697ac fscsi1|0000000000651d00|202500a0b82697ac|200400a0b82697ac fscsi2|0000000000651a00|202400a0b82697ac|200400a0b82697ac fscsi2|0000000000651d00|202500a0b82697ac|200400a0b82697ac fscsi4|0000000000651a00|202400a0b82697ac|200400a0b82697ac fscsi4|0000000000651d00|202500a0b82697ac|200400a0b82697ac -------------------------------------- There are 2 VIOS providing NPIV disks to nimtb187 They are vios1_nimtb184 vios2_nimtb185 -------------------------------------- Checking Inactive wwpns .. C0507600091D002B C0507600091D0027 Target wwpn 204400a0b82697ac can be reached using inactive wwpn C0507600091D0027 via 3 adapters. Target wwpn 204500a0b82697ac can be reached using inactive wwpn C0507600091D0027 via 3 adapters. **** YES. VIOS nimtb184 CAN host Client LPAR nimtb187 like Source VIOS vios1_nimtb184 after LPM **** Checking Inactive wwpns .. C0507600091D0025 C0507600091D0029 Target wwpn 202400a0b82697ac can be reached using inactive wwpn C0507600091D0029 via 3 adapters. Target wwpn 202500a0b82697ac can be reached using inactive wwpn C0507600091D0029 via 3 adapters. **** YES. VIOS nimtb184 CAN host Client LPAR nimtb187 like Source VIOS vios2_nimtb185 after LPM **** In order to host Client LPAR nimtb187, VIOS nimtb184 should be able to virtualize FC adapters for at least one set of inactive WWPNS listed above. If not, verify zoning. =================================================================