HP 1.10GB Virtual Connect Ethernet Module for c-Class BladeSystem - Manual (Page 25)

Domain management 25
• After an enclosure is imported into a domain, do not change the serial number. The enclosure must have
the enclosure serial number that was present when imported initially. It cannot be replaced with an
enclosure that has a different serial number.
• In the event of an enclosure failure, the replacement enclosure must have the serial number set to that of
the failed enclosure before it is placed into the VC domain.
In an existing VC domain, if the enclosure serial number is changed from the OA with the set enclosure
serial-number command, HP recommends that all the VC Ethernet modules be reset through the OA so that
the new enclosure number is propagated to all the modules in the enclosure.
Firmware updates
To update firmware, use the HP BladeSystem c-Class Virtual Connect Support Utility. For more information on
installing the firmware, see the HP BladeSystem c-Class Virtual Connect Support Utility documentation on the
HP website ( http://www.hp.com/go/bladesystem/documentation ).
When upgrading to v3.00, any SAN fabrics previously using the static login distribution method are
redefined to use dynamic login distribution. Servers will lose connectivity during the upgrade. Therefore, HP
recommends upgrading to v3.00 or later during scheduled downtime only.
To help ensure proper operation, clear the browser cache and reload the browser after firmware updates.
Downgrading from v3.x to a pre-v3.00 version of the VC firmware results in the loss of configuration. HP
recommends that the domain be deleted before a downgrade from v3.x to a pre-v3.00 version of the VC
firmware.
Downgrading from v2.30 to a pre-v2.00 version of the VC firmware is not supported if HP Virtual Connect
Flex-10 modules are installed in an enclosure because it might not be possible to log in to the Virtual Connect
Manager after the downgrade. To downgrade to an older version of Virtual Connect, remove all HP Virtual
Connect Flex-10 modules from the enclosure, ensure that the modules are removed from the GUI, and then
perform the downgrade.
Downgrading from v2.30 to a pre-v2.00 version of the VC firmware is not supported if profiles contain
Flex-10 connections because it might not be possible to log in to the Virtual Connect Manager after the
downgrade. Virtual Connect defines Flex-10 connections as the connections between FlexNICs and the HP
Virtual Connect Flex-10 module or an empty interconnect bay. To downgrade to an older version of Virtual
Connect, remove all the Flex-10 connections from the profile, ensure that the modules are removed from the
GUI, and then perform the downgrade.
When created with HP VC 8Gb FC modules present in the domain, the VC configuration file is not
compatible with the configuration files created by versions of VC previous to v2.10. If the VC firmware is
downgraded to any pre-v2.10 versions, re-importing the domain is required.
When upgrading from VC v2.10 to VC v2.3x or higher, the VC 2.10 SNMP configuration is converted to a
comparable VC 2.3x or higher SNMP configuration. If a downgrade is performed from VC 2.3x to v2.10,
the SNMP configuration prior to the v2.3x upgrade is restored. Therefore, any changes made to the 2.3x
SNMP configuration are not reflected in the downgraded v2.10 SNMP configuration.