HP Virtual Connect 3.51 Release Notes

Enhancements 5
Enhancements
Version 3.51 of Virtual Connect contains the following enhancements:
• Enhanced support for network loop protection
• Support for Internet Explorer 9.x
• Support for Mozilla Firefox 6.x and 7.x
• Support for the following products:
o HP ProLiant BL460c Gen8 Server Blade
o HP QMH2572 8Gb FC HBA for c-Class BladeSystem
o HP FlexFabric 10Gb 2-port 554M Adapter
o HP FlexFabric 10Gb 2-port 554FLB Adapter
o HP Flex-10 10Gb 2-port 530FLB Adapter
o HP Flex-10 10Gb 2-port 530M Adapter
o HP Flex-10 10Gb 2-port 552M Adapter
Fixes
The following issues have been resolved in the VC 3.51 release:
• Resolved an issue for VC 8Gb 20-port FC module firmware where it would not always perform Link
Reset when there were no FC buffer credits available. This fix improves link stability between the VC-FC
module and the HBA.
• Resolved an issue that caused network connectivity loss for Integrity multi-blade servers, such as the HP
Integrity BL870c i2 server, with a profile assigned. The issue could be triggered by a sequence of
interaction between VCM and the OA, through which a profile "pending" state was left unattended.
• Resolved an issue where CLI server profiles associated with a non-default network access group
reverted to the "Default" network access group after profiles were assigned to physical servers.
• Resolved an issue where the defined VC domain IP address became inaccessible after the primary VC
module host name was changed.
• Resolved an issue where upgrading from VC v3.xx to v3.30 in configurations using multi-blade servers
caused the domain to become inactive. This issue is also documented in Customer Advisory
c03057267 on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03057267).
• Resolved an issue for multi-blade servers where FlexFabric ports were being over-allocated for FCoE
entries and were unavailable for Ethernet connections.
• Previously the VCM CLI splash screen, which asks for acceptance to the terms on the screen, did not
precede the login credentials. The VCM CLI now displays the customer configurable splash screen first,
asking for acceptance to the terms before asking for login credentials.