HP Virtual Connect Version 2.33 Release Notes

Known issues 14
in bays 5, 6, 7 or 8 in either the local or remote enclosures, some or all of the compatible FC
modules in the remote enclosures might be designated INCOMPATIBLE after import.
To work around this issue, do the following:
1. Replace inappropriate FC modules with similar and compatible FC modules in bays 5, 6, 7 and 8
on all enclosures.
2. Power cycle any FC module that still remains in an INCOMPATIBLE state.
• The SNMP Managed Status Change trap (vcProfileManagedStatusChange) for all unassigned
Profiles is not sent by VC when the profile status transitions to a Normal state.
• In a multi-enclosure environment, if local and remote enclosures are shut down and powered back
up, VC might incorrectly report that some empty I/O module bays in a remote enclosure are "NO-
COMM". This occurs if there are VC-FC modules in the local enclosure and the corresponding bays
in the remote enclosure are empty. The empty module bays should have been reported as
"MISSING".
• The VC CLI incorrectly allows enabling or disabling of SNMP on a domain. The same VC domain
attributes are not accessible via the GUI. Do not use the VC CLI to enable or disable SNMP on
domain attributes.
• If an adapter is inserted in a server that is incompatible with the VC module that it maps to, the
SNMP Physical Server Managed Status trap (vcPhysicalServerManagedStatusChange) is not sent
when this mismatch is corrected.
• In a multi-enclosure domain, the VC CLI reports an incorrect error and fails when an Ethernet uplink
is enabled or disabled. This occurs only if you try to enable or disable uplinks that are part of a VC
network, and if one or more uplinks are on the remote enclosures. Use the VC GUI to enable or
disable links in these instances.
• The VC CLI incorrectly allows invalid speeds to be set on the uplinks of Ethernet modules. If an
invalid speed (for example, setting 100 Mb on an SFP RJ-45 pluggable module uplink) is set using
the CLI, the link state is disabled. This problem does not appear in the VC GUI. Use only valid
speeds when the VC CLI is being used to configure the uplinks on Ethernet modules.
• When upgrading from VC v2.10 to VC v2.3x, the VC 2.10 SNMP configuration is converted to a
comparable VC 2.3x SNMP configuration. If a downgrade is performed from VC 2.3x to v2.10, the
SNMP configuration prior to the v2.3x upgrade is restored. Thus any changes made to the 2.3x
SNMP configuration are not reflected in the downgraded v2.10 SNMP configuration.
• Even though the system might not prompt for a server reboot, server reboot is required after the
server is upgraded successfully with the latest firmware and drivers for HP Dual Port Flex-10 10GbE
Multifunctional BL-c Adapters, NC532i or NC532m. The reboot allows the newly upgraded drivers
and boot code to run, which then allows Virtual Connect to be able to configure the new feature
"Dynamic Changes to FlexNICs," which is included in this release.
Firmware update
HP recommends using the HP BladeSystem c-Class Virtual Connect Support Utility to install the HP VC-Enet
version 2.33, the HP VC 4Gb FC version 1.40, the HP VC 8Gb 20-Port FC version 1.40, and the HP VC
8Gb 24-Port FC version 1.01 firmware.
For more information on installing the firmware, see the HP BladeSystem c-Class Virtual Connect Support
Utility release notes on the HP website (
http://www.hp.com/go/bladesystem/documentation).