HP Virtual Connect Version 2.12 Release Notes
  Virtual Connect Manager uses the enclosure serial number to associate a Virtual Connect domain 
with a particular enclosure. The enclosure serial number can be altered for maintenance procedures 
such as replacing the enclosure midplane. For more information, see SET ENCLOSURE 
SERIAL_NUMBER in the HP BladeSystem Onboard Administrator Command Line Interface User 
Guide. Enclosure serial numbers are unique as shipped from the factory, and must remain unique for 
proper Virtual Connect Manager operation. When altering the enclosure serial number, be sure that 
serial numbers are unique within the management network. 
  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. 
  Downgrading from v2.12 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, administratively remove 
the modules, and then perform the downgrade. 
  Downgrading from v2.12 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, administratively remove the HP Virtual Connect Flex-10 modules, and then perform the 
downgrade. For more information on Flex-10, see the HP Virtual Connect for c-Class BladeSystem 
User Guide. 
  The VC Manager CLI command show fabric X displays only the Port (Connected From) WWN 
for the physical uplink ports of a Virtual Connect fabric. The term "WWN" in the display output 
refers to the Port WWN and not the Node WWN. 
  The enclosure does not support installing an HP Virtual Connect Flex-10 10Gb Module in a bay 
adjacent to any other module type. Always install the module next to either an HP Virtual Connect 
Flex-10 Module or an empty bay. For more information, see the installation guidelines section in the 
HP Virtual Connect for c-Class BladeSystem User Guide. 
  When a VC-Enet module is running VC v1.30 firmware or higher, a link might not be re-established 
between the module and the ports of an NC364m mezzanine card under the following conditions: 
o  The network mappings are changed on the NIC ports through Virtual Connect. 
o  The VC-Enet module is restarted from a power-cycle or reboot, or the module is removed and 
inserted. 
If the server is rebooted, the link is established on all ports on both sides of the connection. Manually 
toggling the link from the server should also restore the link. 
  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. 
Important notes and rec
ommendations  16 










