HP Virtual Connect Version 3.30 Release Notes

Resolved issues 15
Resolved issues
The following issues have been resolved in the VC 3.30 release:
• Resolved an issue where the web server was not being restarted when changes were made to the
certificate/SSL strength.
• Resolved an issue when frequent state change notifications would cause VCM GUI slowness, for
example, if a server was in a constant PXE boot cycle.
• Resolved an issue where a Virtual Connect Domain IP Address became inaccessible after a VC
recovery.
• Resolved an issue where VCM would hang when the primary VC module was rebooted while VCM was
in the middle of writing an entry into the support log.
• Changed the default SSL strength to "High" for new domain imports.
• The SNMP Read Community string for VC-FC SNMP settings has been extended to support up to 24
characters.
• The SNMP System Contact string for VC-FC SNMP settings has been extended to support up 20
characters.
• VC Manager now properly detects when a SAN Fabric connected to the VC-FC uplink ports becomes
segmented into different FC SAN Fabrics and reports appropriate status messages in VCM.
• Resolved a connectivity issue between the HP VC 8Gb 20-Port FC Module and Emulex LPe1205-HP
8Gb FC HBA seen after a VC firmware update from any older version to VC 3.15, 3.17, or 3.18
(VC-FC v1.41) and subsequent server reboot.
• Resolved an issue where maintenance mode in VCEM could not be completed after deleting a port
monitor in the maintenance mode.
• Resolved an issue that could trigger a server to shut down during VC enclosure recovery, such as when
communication with the OA is lost, for HP Integrity BL870c i2 and BL890c i2 Series Server Blades.
During VC enclosure recovery, network and SAN connections can be taken down and then
reestablished exactly as they had been configured before the enclosure recovery. The disconnection
typically lasts for less than a minute and can often be unnoticeable, but for Service Guard operations
there is the potential that this can cause a heartbeat loss that triggers one of the servers (determined
through a configuration priority) to shut down.