HP Virtual Connect Version 3.17 Release Notes

Resolved issues 11
• Resolved a loss of FC connectivity issue when a VC 8Gb 24-Port FC Module received a multi-sequence
frame from an in-band storage management application (the application was executing on a server
within the c7000 enclosure). This resulted in a VC 8Gb 24-Port FC Module reset and loss of FC
connectivity.
• Resolved an issue where the VC 8Gb 24-Port FC Module might not recover from a NO-COMM state
after an OA failover. The IP address for the FC module was not being updated correctly, which was
blocking the proper communication with the primary VC module.
• Resolved an issue where VCM reported a NO-COMM state for a VC-FC module, even though the
VC-FC module was still responding to a ping command.
• Resolved an issue where the VC 8Gb 24-Port FC Module firmware version information did not display
correctly on the OA rack firmware page after an OA reset. This resolution requires OA version 3.30 or
higher.
• The VC recovery algorithm has been changed so that the current configuration number is validated after
a complete recovery from an OA NO-COMM state. Previously, the read of the configuration number
might have failed, and the module was scheduled unnecessarily for a full reset and recovery (the
configuration numbers were not out of sync).
• Resolved an issue where the network nativelan setting cleared after adding another network.
• Resolved an issue where an hpvcm_deleteManagedObjects return code error occurred when deleting
a profile.
• Resolved an issue that delayed the startup time on an enclosure with eight Flex-10/FlexFabric modules.
• Resolved a performance issue where adding a single network caused an update of all configured
networks.
• Resolved an issue where firmware details did not display on a Firefox browser window.
• Resolved an issue where FCoE login took longer than expected when changing between fabrics. When
FCoE connectivity from FlexFabric adapters is utilized with FlexFabric modules, and server connectivity
is changed between two different SAN fabrics within VCM, it can take the server up to 2 minutes to log
in to the external SAN fabric. A change in the handling of the FCoE Initialization Protocol (FIP) was
implemented to expedite the login process.
• Resolved an issue where the VCM CLI command "set enet-vlan" did not return an error for the command
"set enet-vlan VlanTagControl=Tunnel SharedServerVlanId=true".
• Resolved an HP Integrity BL8x0c i2 Series Server Blade issue where there were problems disconnecting
Flex-10 ports with I/O modules that do not support Flex-10, which could result in disabled network ports
appearing as enabled.
• Resolved a GUI issue where titles on the Device Bay Summary screen were not displayed consistently.
• Resolved an issue where an SNMP trap configuration with only FC traps selected could not have an
associated set of severities. VC Manager appeared to allow specification of SNMP trap severities for
FC trap categories. This functionality is not currently supported. The SNMP Configuration page was
updated to disable severity selection if only FC trap categories are selected.
• Resolved an issue where an error was not indicated for login redistribution for a degraded/failed SAN
in external connections.
• Resolved a GUI issue for HP Integrity BL8x0c i2 Series Server Blades where the entries in the Server
Ethernet Adapter Information table did not properly collapse and expand.