HP Virtual Connect Version 2.02 Release Notes and Compatibility Matrix

Resolved issues
The following issue has been resolved in Virtual Connect v2.02:
Virtual Connect Manager versions 1.31 through 2.01 did not work properly with Virtual Connect
Enterprise Manager v1.20 when a server port existed with multiple network connections and one network
connection was untagged.
A customer advisory has been created, which provides a detailed description of this issue, and the proper
resolution steps required to resolve this issue.
To access this customer advisory:
1. Go to the HP Website (http://www.hp.com/go/vcem).
2. Under the "Support" heading, click Support & Documents.
3. Click Customer Advisories.
The following issue that existed in Virtual Connect v2.00 has been resolved in Virtual Connect v2.01:
Fixed an issue where VC-defined WWNs were not being written to the server HBA after upgrading
firmware to VC v2.00. This defect was triggered if a profile created in pre VC v2.00 was assigned to an
empty bay, and firmware was upgraded to v2.00. Inserting a server in the empty bay did not write the
WWNs to the server.
The following issues that existed in Virtual Connect v1.32 have been resolved in Virtual Connect v2.01:
• Resolved an issue with the GUI firmware upgrade where the activation of the primary module did
not occur after a successful firmware upgrade.
• Resolved an issue with the VCM CLI that caused the shell to abort under certain conditions when the
character "-" was part of a command.
• Resolved an issue where the Virtual Connect Ethernet modules would reboot if the modules could not
acquire an IP address from a DHCP server after trying for several minutes.
• Resolved an issue that caused the Fibre Channel configuration to be lost when multiple fabrics were
created on a single FC module, and the module was swapped, reset, or hot-plugged.
• Resolved an issue with the Fibre Channel firmware where the FC configuration was not restored
correctly when hot-plugging HP VC-FC modules.
Resolved an issue with the VC GUI where it did not allow the• edit of a server profile if the profile
• bric define, edit, and summary pages in the VC GUI to display the Fabric
• zard and configuration screen. This
• onsive if the Virtual Connect Manager encountered
• the VC primary module to become unresponsive and reset when
multiple OA resets occurred.
had a connection with multiple networks associated with it.
Added a column in FC fa
type (static or dynamic).
The enclosure serial number is now displayed in the enclosure wi
addition helps ensure that the correct enclosure is imported.
Resolved an issue where the VC GUI was unresp
a server with a bad signature in the enclosure.
Resolved an issue that caused
Resolved issues 10