HP Virtual Connect Version 2.31Release Notes

Resolved issues 10
Resolved issues
The following issues that existed in previous versions of Virtual Connect have been resolved in Virtual
Connect v2.30 or v2.31:
• Resolved an issue on VC Flex-10 Ethernet modules where Link Aggregation Groups (LAG) cannot be
formed with more than 40Gb total throughput. With this fix, VC Flex-10 Ethernet modules can
support LAGs with up to 80Gb total throughput.
• Resolved an issue with some server links mapped to the VC Flex-10 Ethernet module not being able
to link up under certain enclosure/server configurations.
The effect of this fix is that it can take an additional 30 seconds for a VC Flex-10 Ethernet module to
become ready after initial power-on of the module.
• Resolved an issue for VC 8Gb 24-Port FC Modules when a VC Fabric has all of the uplink ports in
an offline state and one of the uplink ports comes back online. VC 8Gb 24-Port FC Modules now
reconfigure server connectivity to that online uplink port.
• Resolved an issue for VC 8Gb 24-Port FC Modules that failed to map server connections to a newly
added uplink port on a VC Fabric that already has all of the uplink ports in an offline state.
• Resolved an issue for VC 8Gb 24-Port FC Modules to generate SNMP traps to indicate that the
parameters have been changed when any of the SNMP configuration parameters are modified.
• Resolved an issue for VC 8Gb 24-Port FC Modules so the SNMP System Contact string can now be
less than four characters.
• Resolved an issue for VC 8Gb 24-Port FC Modules to behave correctly after a VC domain deletion.
SAN connectivity is allowed for all the servers in the enclosure, regardless whether a server has
previously has assigned a server profile.
• Resolved an issue for VC 8Gb 24-Port FC Modules that did not properly populate the SNMP
MibStatus Array.
• Resolved an issue for VC 8Gb 24-Port FC Module so that under the default port group configuration,
the server(s) port logins can occur.
• Resolved issues when VC FW is upgraded to v2.3x in a Virtual Connect Enterprise Manager (VCEM)
environment. The problem resulted in an incorrect SNMP configuration, which was not re-admitted to
its VCEM Virtual Connect Domain Group.
• Resolved a v2.30 issue on a Multi-enclosure system in which the VC Manager user responses are
slow or the system appears to be locked up. This behavior is due to high overhead startup of the
SNMPD process.
• Resolved an issue in which the SNMP SMI-S enabled flag was not being carried forward to the
configuration from pre-VC 2.30 versions.