Instructions on how to upgrade previous VC GbE modules to Virtual Connect Flex-10.

[chuckk281]

If you currently have a Virtual Connect 1/10GbE module and wanted to upgrade to the latest VC Flex-10 GbE module here is info on what it would take to do that. From HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide Upgrading to an HP Virtual Connect Flex-10 Module Upgrading an enclosure to Flex-10 support requires several steps, depending on the starting configuration. Replacing a Virtual Connect Ethernet Module with an HP Virtual Connect Flex-10 Module in bays 3 to 8 1. Upgrade the VC domain firmware to v2.01 or higher. 2. Save the configuration. 3. If there are any Flex-10 NICs with profile connections that are connected to the interconnect bays being upgraded, the profile connections must be removed. This can be done by un-assigning the profile (recommended) or by deleting the connections from the profile. 4. Remove the existing non-Flex-10 modules from BOTH horizontally adjacent bays. 5. Administratively remove the modules. 6. Install the HP Virtual Connect Flex-10 Modules. 7. Re-assign the server profiles or add the connections to the profiles, depending on what was done in step 3. Replacing a Virtual Connect Ethernet Module with an HP Virtual Connect Flex-10 Module in bays 1 or 2 1. Upgrade the VC domain firmware to v2.01 or higher. 2. Save the configuration. 3. Upgrade any modules in bays 3 to 8 using the previous steps. 4. Save the configuration. This is very important. 5. Remove the modules from bays 1 and 2. 6. Install the HP Virtual Connect Flex-10 Modules in bays 1 and 2. 7. Import the domain, and then select the option to restore the domain from a saved configuration file. Possible errors If the previous steps are not followed exactly, the module might be set to the UNKNOWN or INCOMPATIBLE state depending on how the error state was reached. The module should be removed physically and removed administratively, if necessary. Then, the correct module type can be inserted. If the above steps have been followed and the server is not connecting properly to the network, power down the server, and then power it back up.