HP Virtual Connect Version 1.34 Release Notes and Compatibility Matrix

Resolved issues 10
Resolved issues
The following issues that existed in Virtual Connect v1.32 have been resolved in Virtual Connect v1.34:
• With LDAP authentication, users were unable to login/authenticate to Virtual Connect Manager
when their CN (Common Name) contained a comma (Example: Jones, Fred).
• With LDAP authentication, users were unable to login/authenticate to Virtual Connect Manager
using their sAMAccountName.
• The VC GUI was not updating the "connected to" field on the FC module overview page after a
manual redistribution of server logins.
• The Virtual Connect GUI would hang if VC encountered a server with a bad checksum.
• A VC module or modules could become inaccessible (NO_COMM) after configuration changes
were made to a configuration that had a large number of networks created (greater than 30).
• The VC CLI did not allow changes to the native or private parameters of two networks if both the
networks were members of two different shared uplink sets, but had the same VLAN ID.
• A memory leak in the Virtual Connect Manager was triggered when the OA in the enclosure had no
IP address.
• The VC GUI would stop responding for a brief period, and timeout, when VC modules were hot-
plugged in an enclosure.