HP Virtual Connect 3.60 Release Notes

Issues and workarounds 9
Issue
Virtual Connect Manager might reset when it contains more assigned and unassigned profiles than can be
in use by physical servers in the domain.
Issue
The VCM CLI show uplinkport command does not display the serial numbers for pluggable modules.
Issue
For double-dense server blades, the side B server mezz port mapping is incorrect.
Issue
The timestamp for SNMP traps from VC FC interconnect modules is not in sync with the timestamp kept by
Virtual Connect Manager.
Issue
The GUI allows importing a new domain from and existing configuration file without warning you to power
off all server blades.
Workaround
Power off all server blades before using a configuration file to import a new domain.
Issue
The HP VC 8 Gb 24-Port FC Module does not respond to the HP Insight Control cpqHoGUID MIB request and
is reported as an error.
Workaround
Remove the FC module from the query.
Issue
HP Systems Insight Manager might incorrectly identify the HP VC 8 Gb 24-Port FC module as a SAN switch
because of the incorrect value returned in the SysObjectOid.
Issue
In expanded VLAN mode, the number of allowed connections to a Flex-10 server port is 162. If a profile has
more than 162 connections defined on a physical Flex-10 port, the port is disabled when the profile is
applied and the port status is displayed as disabled.
Issue
The CLI copy uplinkset command does not allow copying of Private Networks within the shared uplink
set.
Issue
When a HP VC 8Gb 24-Port FC module is connected to a Brocade 8510 (16Gb) switch, the link between the
FC module and the 8510 can only negotiate to 4Gb instead of 8Gb.
Workaround
Lock the 8510 port speed to 8Gb for the port that the FC is connecting to.
Issue
If a user attempts to remove or add a mezzanine card to a server blade, then VCM might not detect the
addition or removal of the mezzanine card when the server is re-inserted into the enclosure. However, the
OA shows the correct configuration.