HP Virtual Connect 3.75 Release Notes

Issues and workarounds 9

Under rare conditions, if the time setting on an enclosure is modified in such a way that the HP VC 8Gb

20-Port FC Module or the HP Virtual Connect 4Gb FC Module set the DHCP lease renewal date far in the

future, the module might stop renewing the lease, which can potentially result in duplicate IP address

assignments in the network.

Issue

The SCSI command aborts under load with the HP VC 8Gb 24-Port FC Module.

Issue

The HP VC 8Gb 24-Port FC Module does not respond to the HP Insight Control cpqHoGUID MIB request and

reports as an error.

Workaround

Remove the FC module from the query.

Issue

During an OA failover, the VC GUI might be unable to communicate with VCM for some amount of time.

However, VCM is still operational and working to recover from the OA failover. During this time, the browser

might display an alert dialog to inform you about the loss of communication. Additional alert dialogs might

then be displayed for WebService calls that fail.

Workaround

Start a new VCM GUI session and OA credentials can be restored successfully.

Issue

When an HP VC 8Gb 24-Port FC Module is connected to Brocade 16Gb switches and directors or to Cisco

MDS 9000 series switches with an advanced 8Gb line card, the link between the VC-FC module and the

switch can only negotiate to 4Gb instead of 8Gb. For more information, see the HP website

(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03521759).

Workaround

Lock the switch port speed to 8Gb for the port to which the FC module is connected.

Issue

HP Systems Insight Manager might incorrectly identify the HP VC 8Gb 24-Port FC Module as a SAN switch

due to the incorrect value returned in the SysObjectOid.

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