HP Virtual Connect Version 2.33 Release Notes

Known issues 13
• If a BL2x220c server blade is present in an enclosure, the Hardware overview page in VC does not
display a graphical picture of the server in the Enclosure View. The graphical image can be seen on
the OA web page.
• When the VC wizard is used to configure domain, network, SAN, and server profiles, the server
profile wizard does not allow double-dense server bay assignment for BL2x220c server blades. Run
the domain, network, and SAN wizards, and then log out. After logging back in, run the server
profile wizard. Double-dense bay assignment for BL2x220c server blades is now possible.
• When a VC-FC module is replaced with another VC-FC module in a Virtual Connect domain, server
blade Fibre Channel SAN connectivity might not be restored properly. To resolve this problem after
the module is installed, either reset the VC-FC module from the Onboard Administrator GUI or reboot
the affected server blades.
• Under certain circumstances, the checkpoint status icon in the GUI persists for a long time and is not
cleared. The CLI also shows a "Checkpoint Status: Invalid" status in the "show domain" output. This
condition has been observed periodically after a VCSU firmware upgrade of the VC module
firmware. To resolve this issue, reset the VCM on the primary module, or reset the primary module
using the OA.
• If a VC-FC module is replaced with a spare VC-FC module without powering down the servers, and
if the server has profiles assigned to it with FC connections, servers are allowed to log in for a brief
period of time through an uplink of the new module. Approximately 8 seconds after discovering the
new VC-FC module, VCM configures it with the correct information, mapping downlinks to the
correct uplinks. To work around this problem, power down the servers in the enclosure before
replacing or swapping FC modules.
• When a c7000 enclosure is fully populated with BL870c server blades and static login distribution is
used on VC 4Gb FC modules with all 4 uplinks included, VCM does not map any server blades to
uplink 1 and uplink 3. The server blades in bay 2 and bay 4 are mapped to uplink 2, and the server
blades in bay 6 and bay 8 are mapped to uplink 4. HP recommends using dynamic login
distribution.
• If an HP Virtual Connect Flex-10 10Gb Ethernet Module is removed from an enclosure, it cannot be
administratively removed unless it is re-inserted and removed a second time.
• If NPIV capability of a SAN Fabric switch port is lost, the disabled uplink port of the VC 8Gb 24-Port
FC module remains disabled until the module is reset. HP requires connectivity to NPIV-enabled
switches for all HP VC-FC modules.
• For VC 8Gb 24-Port 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.
• When a VCM domain is deleted, VCM resets VC 8Gb 24-Port FC modules to a default factory
condition. This operation can take up to 50 seconds per VC 8Gb 24-Port FC module.
• When VC 8Gb 24-Port FC module uplink port speeds are configured at 2Gb and other uplink ports
are configured at 4Gb or 8Gb, LEDs might illuminate "faint green" or "faint amber".
• When Dynamic Login Distribution is selected, servers connected through VC 8Gb 24-Port FC
modules can take between 15 and 25 seconds to recover from a module uplink port failure.
• When an enclosure is being imported, an erroneous "vcCheckpointCompleted" trap might be sent
by VC.
• Multi-enclosure (ME) Double Dense domains require similar and compatible FC modules in bays 5,
6, 7 and 8 in all enclosures. If a ME Double Dense configuration contains incompatible FC modules