HP Virtual Connect Version 2.12 Release Notes

 VC currently supports up to 8 ports in a single Link Aggregation Groups (LAG) using LACP protocol.

LAGs are created on Ethernet network uplinks using "auto" mode, or automatically created when

connecting multiple ports of the same speed between two VC-Enet modules to form stacking links.

Although up to 8 ports can be aggregated, attempting to form a LAG with more than 40G total

throughput results in the LAG becoming unusable. This problem affects only VC Flex-10 Ethernet

modules because that is the only module with more than four 10G ports.

There is no work-around for creating a LAG with greater than 40G total throughput, whether it is an

uplink or stacking link. If more than 40G of uplink capacity is required for a network, the only

solution is to divide the network into two or more VC Ethernet networks in an Active/Active

configuration, where each network has at most a 40G uplink LAG.

VC 8Gb FC module

 If NPIV capability of a SAN Fabric switch port is lost, the disabled uplink port of the VC 8Gb FC

module remains disabled until the module is reset. HP requires connectivity to NPIV-enabled switches

for all HP VC-FC modules.

 If an uplink port 8 is present in the VC SAN Fabric definition and the fabric type is set to Dynamic,

this port is treated as the lowest-numbered port and receives server logins before any other uplink

ports.

 Due to an issue when auto-negotiating 8Gb speed with the Emulex LPe1205 mezzanine card, HP

recommends setting either the module downlink port speed or the HBA port speed to 8Gb.

 When a VCM domain is deleted, VCM resets VC 8Gb FC modules to a default factory condition.

This operation can take up to 50 seconds per VC 8Gb FC module.

 When a VC Fabric has all of the uplink ports in an offline state and one of the uplink ports comes

back online, VC 8Gb FC modules fail to reconfigure server connectivity to that online uplink port.

 When an uplink port is added to a VC Fabric that already has all of the uplink ports in an offline

state, VC 8Gb FC modules fail to map server connections to newly added uplink ports.

 When VC 8Gb FC module uplink port speed are configured at 2Gb and other uplink ports are

configured at 4Gb or 8Gb, LEDs might illuminate "faint green" or "faint amber".

 When SNMP configuration parameters are modified, VC 8Gb FC modules do not generate SNMP

traps to indicate that the parameters have been changed.

 When Dynamic Login Distribution is selected, servers connected through VC 8Gb FC modules can

take between 15 and 25 seconds to recover from a module uplink port failure.

 The VC 8Gb FC module SNMP System Contact string length must be greater than four characters.

 After a VC domain deletion, the expected operational behavior for the VC 8Gb FC module is to

allow SAN connectivity for all the servers in the enclosure. However, VC 8Gb FC modules only

allow connectivity for the servers with previously assigned server profiles.

 The VC 8Gb FC module does not properly populate the SNMP MibStatus Array.

The VC 8Gb FC module returns an SNMP System Product Name of "HP Virtual Connect 8Gb 24-

port FC Module," while the Onboard Administrator lists the Product Name from the FRU data as "HP

VC 8Gb 24-port FC Module." These values are equivalent.

Known issues