HP Virtual Connect Version 1.34 Release Notes and Compatibility Matrix

Known issues 16
• Cisco MSD 9134 requires minimum firmware revision of 3.2(2)c, or higher.
• The Fibre Channel login sequence can be delayed by approximately 20 seconds when more than
one server blade HBA is aggregated through the same VC-FC uplink port attached to a Cisco switch
and these HBAs are in the same zone. To avoid this problem, do not place server HBAs in the same
zone on the fabric switch.
• When configuring Trap Destination IP addresses for the VC-FC modules, be sure that trap
destinations are capable of supporting SNMPv1 type traps.
• In a c3000 enclosure with full-height server blades and FC mezzanine cards installed in slot 2 and
slot 3, the VC Manager might assign and incorrectly display the same WWN to both FC mezzanine
cards. This configuration is unsupported and one of the mezzanine cards should be removed.
• If updating from Virtual Connect Manager v1.10 firmware, the VC-Enet module firmware must be
updated before the VC-FC module firmware. Otherwise, the VC-FC firmware might not appear to be
updated successfully.
• Under certain circumstances, after making Fibre Channel configuration changes or when a port state
on the VC-FC modules changes (for example, when a cable is pulled from an unlink port on the VC-
FC module), the VC GUI might respond slowly and take up to 2 minutes to refresh. The checkpoint
icon in the GUI might also persist for several minutes. The GUI eventually refreshes itself and reflects
the configuration or port state change.
• When using the multi-fabric feature with Dynamic Login Distribution, and a SAN Fabric with two or
more uplink ports has been created, VMware ESX Virtual Machine logins are distributed evenly
across all the available uplink ports. In environments with Emulex HBAs, if one of the VC-FC module
uplink ports loses connectivity because of a cable pull or loss of sync, physical or logical servers
logged-in through that uplink port failover to the alternate path, as defined in the VMware ESX
console, instead of failing over to the next available VC-FC module uplink port. If this situation
occurs, restore the downed uplink port, and then go into the VCM server profile and disable/re-
enable the FC connection for the corresponding HBA port.
• When a login redistribution is invoked, there might be no changes or the redistribution might leave
some uplink ports with two fewer server logins than the others. This operation depends on the
number of servers and number of uplink ports.
User interface
• Virtual Connect Manager allows users to change the number of VC-FC Module uplink ports
connected to an external Fabric Switch without a warning while a server might be accessing remote
storage devices.
• Virtual Connect Manager shows either a server blade or an interconnect module as degraded (but
not both) for an I/O mismatch where the incompatibility has been detected by electronic signature
(eKEY) of the modules.
• Network uplinks that are linked after the Network Setup Wizard has been started may not show
proper link status in the wizard. When the wizard is completed, all uplink link statuses are displayed
correctly.
• A server profile can be assigned to a device bay with a server that has fewer physical NIC ports
than defined in the server profile. In most cases, a warning is provided, but in some cases it is not.