FCP NPIV WWPN migration

Steps

1. Ordering the Feature Code 0099 with the new machine order.
   • This feature cannot be ordered alone. It needs to be ordered with the machine order. The new machine with a different machine serial number will have the same IOSN (IO serial number) as the old machine.
   • If the customer forgot to order the feature with their new machine, customer can open a PMH to correct the issue.
2. Export the NPIV WWPN from the old machine
   • If the old machine is older than driver 27, open a PMH for hardware support to export the NPIV WWPN.
   • If the old machine is at driver 27 or newer, FCP provided import/export configuration panel on the SE.
     • This export step needs to be done by the Customer
     • Logon SYSPROG or service mode on the HMC
     • Disable Dynamic I/O
       • Enable/Disable Dynamic Channel Subsystem, pick the CEC
       • 
       • Change to disable and click ok
     • Pick the FCP configuration task, choose the CEC
     • 
       • Choose Import/export configuration
       • 
       • Pick the Export binary NPIV system configuration file.
       • 
       • provide the FTP login information and file path for the file name.
       • If login local HMC, it will allow USB export.
       • Export the binary NPIV mode configuration file.
3. Import NPIV WWPN files to the new system (z15 or later)
   • This step should be done by customer
   • Logon SYSPROG or service mode on the HMC
   • The system should be in a deactivated status or PORed with customer IOCDS
   • If the machine is PORed with customer IOCDS, it will require disable dynamic I/O.
   • Import the NPVI WWPN
     • Pick the FCP configuration task, choose the CEC
     • Choose Import/export configuration
     • Pick the import binary NPIV system configuration file.
     • Either use the FTP or USB media as export function.
     • Check the successful message:

     •                       The import of a WWPN configuration completed successfully.                      The imported configuration will become active after the next IML. The system may assign                      additional WWPNs to I/O devices that are part of the current FCP I/O configuration, but not                      part of the imported WWPN configuration. If FCP channels were used in NPIV mode on this                      system before this task was started, different WWPNs may be used by the FCP channels, or                      WWPNs may have moved to different FCP channels.                      It is strongly recommended to perform an IML and then verify the new WWPN configuration                      by viewing/exporting it using the NPIV configuration panels. Omitting the IML may leave                      the system in an inconsistent state.                      It is strongly recommended to backup your critical console data by performing the                      'Backup Critical Console Data' task following the next IML.

     • Pick the import binary NPIV mode configuration file
     • Either use the FTP or USB media as export function.
     • Check the successful message

     •                       The import of NPIV mode settings completed successfully.                      The imported configuration will become active after the next IML. Omitting the IML may leave the system in an inconsistent state.                      It is strongly recommended to backup your critial console data by performing the 'Backup Critical Console Data' task following the next IML.

     • For the NPIV WWPN set and mode files to take place an IML is required. Just re-iml with the same IOCDS might not trigger the reload of the NPIV WWPN that was just imported. We recommend a deactivate and activate of the CEC. This will make sure the NPIV configuration loads to HSA. After the IML the customer can verify the NPIV WWPNs with the display all NPIV WWPN that are currently assigned to FCP subchannels... option. If the verification is not what was expected, please open a hardware record and provide the imported files and health check data to the IBM Support.