HP Virtual Connect Version 1.34 Release Notes and Compatibility Matrix

Important notes and recommendations 13
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.
Support for double-dense server blades (BL2x220c) in a Virtual Connect domain requires the domain
to be created or imported using VC v1.31 firmware or higher. If a domain was created in VC v1.2x
or lower and then updated to VC v1.31 or higher, double-dense server blades are not supported. To
support double-dense server blades after migrating from a VC v1.2x or lower domain, the VC
domain must be deleted and a new domain created or imported.
CAUTION: Deleting a VC domain causes a complete LAN and SAN outage.
When a login redistribution is invoked for FC modules, there might be no changes, or the
redistribution might leave some uplink ports with two fewer server logins than others. This operation
depends on the number of servers and number of uplink ports.
VC v1.34 supports the Multi Enclosure feature as a beta feature. If an import of a remote enclosure
running VC v2.xx version is attempted, the import might succeed. However, this configuration is not
supported. All the enclosures in a Multi Enclosure beta environment must be running the same
version of the firmware.
When a VC-Enet module is running VC v1.30 firmware or later, 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, reboot, or the module is removed and
inserted.
If the server is rebooted, the link will be established on all ports on both sides of the connection.
Manual toggling of the link from the server should also restore the link. This issue is expected to be
resolved in a newer version of the NC364m mezzanine card.