HP Virtual Connect 3.60 Release Notes

Issues and workarounds 7
current or previously added bay entries. If they were selected, the SAN fabric was not updated with the
current modifications.
• Resolved an issue where in a double-dense domain configuration, interconnect bays 7 and 8 should not
be used to create an FC fabric. The fabric should instead be created on bays 5 and 6. If a fabric was
created on bays 7 or 8 using the VCM CLI, an incorrect error message might appear, indicating
"ERROR: Module not found" instead of "ERROR: A fabric is not allowed to be created with the specified
bay for a double-sense configuration."
• Resolved an issue where VC allowed mapping of non-supported iSCSI connections for NC522m Mezz
ports 1-a and 2-a.
• In a multi-enclosure environment, if local and remote enclosures were shut down and powered back up,
VC might incorrectly report that some empty I/O module bays in a remote enclosure were
"NO-COMM". This error occurred if VC-FC modules were installed in the local enclosure and the
corresponding bays in the remote enclosure were empty. The empty module bays are now correctly
reported as "MISSING".
Issues and workarounds
New issues
Issue
When using the Virtual Connect Support Utility or HP Smart Update Manager, Virtual Connect firmware
upgrades from Virtual Connect firmware v3.18 or earlier might fail on a single module when updating to
Virtual Connect firmware v3.60.
Workaround
For the workaround, see Customer Advisory c03395976 on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03395976).
Issue
When using IE9 to activate the VC GUI, there is no error message when executing without Flash Player.
Issue
The VC Unknown (unmanaged) module states (Operational, VC, OA, Comm) are not being displayed in a
consistent manner.
Issue
HP VC Flex-10 and FlexFabric modules may experience an extended timeout when re-establishing a Link
Aggregation Group (LAG). This issue may increase chances for encountering a ping loss, and the likelihood
of encountering a lost ping also increases with the number of the port members in the LAG that are being
recovered or reintegrated.
Issue
When one of the uplink ports X1–X4 on the FlexFabric module is not configured for FC or is configured for
Enet, but has an FC SFP inserted into the SFP cage, the "Connector Type" displayed by VCM and the
information displayed in the detailed statistics screen are not consistent.