HP Virtual Connect Version 3.01 Release Notes

Known issues 11
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.
• 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.
• 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
in bays 5, 6, 7 or 8 in either the local or remote enclosures, some or all of the compatible FC
modules in the remote enclosures might be designated INCOMPATIBLE after import.
To work around this issue, do the following:
1. Replace inappropriate FC modules with similar and compatible FC modules in bays 5, 6, 7 and 8
on all enclosures.
2. Power cycle any FC module that still remains in an INCOMPATIBLE state.
• The SNMP Managed Status Change trap (vcProfileManagedStatusChange) for all unassigned
Profiles is not sent by VC when the profile status transitions to a Normal state.
• In a multi-enclosure environment, if local and remote enclosures are shut down and powered back
up, VC might incorrectly report that some empty I/O module bays in a remote enclosure are "NO-
COMM". This occurs if there are VC-FC modules in the local enclosure and the corresponding bays
in the remote enclosure are empty. The empty module bays should have been reported as
"MISSING".
• If an adapter is inserted in a server that is incompatible with the VC module that it maps to, the
SNMP Physical Server Managed Status trap (vcPhysicalServerManagedStatusChange) is not sent
when this mismatch is corrected.
• In a multi-enclosure domain, the VC CLI reports an incorrect error and fails when an Ethernet uplink
is enabled or disabled. This occurs only if you try to enable or disable uplinks that are part of a VC
network, and if one or more uplinks are on the remote enclosures. Use the VC GUI to enable or
disable links in these instances.