HP Virtual Connect Migration Guide

Technical white paper | Virtual Connect Migration Techniques
19
Migrating VC modules when the Domain is managed by Virtual Connect
Enterprise Manager
When present, Virtual Connect Enterprise Manager manages the profiles and allows an easy profile preservation. Here is a
very quick overview of the steps necessary to migrate from HP 1/10Gb VC-Enet modules to VC Flex-10/10D modules or
FlexFabric 10Gb/24-Port modules to FlexFabric-20/40 F8 modules in VCEM environment. By using VCEM, the virtual MACs
and WWNs associated with profile connections and logical serial numbers will remain unchanged through the migration.
1) Ensure VCEM is at least version 7.3. This version introduced the feature allowing profiles to be moved between different
VC Domain Groups and supports the HP Virtual Connect FlexFabric-20/40 F8 module. After migrating to the new VC
modules, the enclosures will be in a different domain group. VCEM should be upgraded prior to replacing the VC modules.
2) Power down all servers in the domain which is being migrated.
3) Log into the VCEM UI and unassign all profiles assigned to the VC Domain.
4) If this is the last domain in the VC Domain Group, use VCEM to move the profiles into another VC Domain Group before
deleting the Domain Group that is being updated. If the profiles are not moved into a VC Domain Group before the last
domain is removed from the VC Domain Group, they will be consigned to the domain when it is removed rather than
remaining in VCEM. Moving the profiles to another VC Domain Group keeps them under VCEM management and allows them
to be reassigned to the upgraded domain later in this procedure.
5) Use the VCEM UI to remove the VC Domain being migrated from its VC Domain Group.
6) Ensure that the VC Domain is running VC FW 3.30 or later. If the VC domain firmware must be upgraded, it is strongly
recommended to upgrade to VC 3.61 as noted earlier in this document. Do not upgrade to VC FW 3.30. Note that HP 1/10
VC-Enet modules are not supported by versions of Virtual Connect firmware beyond v 3.61. Also note that the HP 4Gb VC-FC
Module 409513-B21 is not supported by versions of Virtual Connect firmware beyond v4.01.
7) Log into the VCMCLI, issue ‘show config’ commands and capture their output as described in the sections on capturing the
existing VC domain configuration..
8) Modify uplinks and password strings in the configuration script as described earlier in this document in the sections on
creating a script configuration, modifying user credentials, modifying SSL strength setting, and modifying uplink port IDs.
9) Replace VC 1/10 modules with VC Flex-10/10D modules or FlexFabric-10gb/24-Port modules with FlexFabric-20/40 F8
modules.
10) Upgrade the VC firmware to version 4.20 or later
11) Use VCM and PLINK to import the enclosure and deploy the domain configuration script as described earlier in this
document in the section on domain-wide settings. You will use VCEM to assign profiles as described in the steps below. You
will not use the VCM scripts to create and assign profiles.
12) Use VCM to check the status of the domain and resolve any issues before proceeding to the next step.
13) Perform a Systems Insight Manager discovery against the enclosure’s Onboard Administrator IP address. This will make
the new configuration visible to Systems Insight Manager.
14) Use the VCEM UI to add the newly upgraded VC Domain to a new VC Domain group and verify that the group is
successfully created.
15) Use the VCEM UI to assign the server profiles that were unassigned in steps 3 and 4 to the servers in the newly upgraded
domain.
16) Power on servers and test network and storage connectivity.
References
Virtual Connect Manager User Guide