HP Virtual Connect Version 2.
© Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software.
Contents Hardware and firmware requirements ............................................................................................. 4 HP Virtual Connect firmware ......................................................................................................................... 4 Firmware upgrade requirements .................................................................................................................... 4 Recommended firmware versions for this release ........................
Hardware and firmware requirements HP Virtual Connect firmware The latest HP Virtual Connect firmware package (version 2.33) contains the following firmware versions: • HP VC-Enet version 2.33 • HP VC 4Gb FC version 1.40 • HP VC 8Gb 24-Port FC version 1.01 • HP VC 8Gb 20-Port FC version 1.40 The HP BladeSystem c-Class Virtual Connect Firmware v2.
• HP BladeSystem Onboard Administrator • iLO HP recommends using the HP BladeSystem c-Class Virtual Connect Support Utility version 1.4.1 to install the HP VC-Enet version 2.3x, the HP VC 4Gb FC version 1.40, and the HP VC 8Gb 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).
VC 8Gb 20-Port FC module Firmware Version Virtual Connect firmware 2.3x VC 8Gb 20-Port FC firmware within Virtual Connect VC-FC 1.40 The following table shows firmware upgrade/downgrade support for the HP 8Gb Virtual Connect Fibre Channel modules. Upgrade to or downgrade from To VC 2.10/2.12 To VC 2.3x (VC-FC2 1.01) (VC-FC2 1.00) VC 2.10/2.12 — Normal VC 2.3x Normal — For more information on required firmware versions and to download firmware upgrades, see the HP website (http://www.hp.
Product Minimum firmware version NC382m Boot code version 4.4.14 and MBA version 4.4.16 or higher NC370i, NC373i, and NC373m Boot code version 1.9.6 and C Class option ROM 1.1.3* or higher. To use NC373m with the BL680c G5 server blade, the option ROM must be updated to NC373m Boot code version 1.9.6 and C Class option ROM 1.2.7 or higher. NC326i, NC325m, and NC326m Boot code version 3.28 and C Class option ROM 1.1.3* or higher.
defaults. However, these server blades do have the Ethernet network and Fibre Channel fabric connectivity specified in their Virtual Connect server profiles. This connectivity enables the use of networkbased firmware update tools for server blade and mezzanine firmware updates. Important notes • The HP Virtual Connect Flex-10 10Gb Ethernet Module is supported by VC v2.xx and higher versions of VC firmware only. This module is not supported by older versions (1.3x) of VC firmware.
New features The VC 2.33 release has no additional new features. The VC 2.32 release has no additional new features. The VC 2.31 release has no additional new features. The VC 2.30 release includes the following new features: • Support for the HP Virtual Connect 8Gb 20-Port Fibre Channel Module. 8Gb configuration and operation is supported only by G6 servers.
Resolved issues The following issue has been resolved in VC 2.33: • Resolved an issue with Virtual Connect Flex-10 modules and NICs, where IGMP Snooping is enabled. The IGMP snooping might stop working after a VC-Enet module is reset, restarted, or power-cycled. The following issues have been resolved in VC 2.32: • Resolved an issue when un-initialized servers were installed and continuously attempted to PXE boot.
• 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 enabled 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.
Known issues General • No System Log message is logged for FC contact name changes. • For server or I/O interconnect hardware changes involving adding or removing Flex 10 functionality, the profile assigned to a server or server bay must be removed, all hardware changes performed, and the profile reassigned. Otherwise, indeterminate network operation might result. • After a configuration is changed, the VC Manager can take up to 90 seconds to save the new information to non-volatile storage.
• If a BL2x220c server blade is present in an enclosure, the Hardware overview page in VC does not display a graphical picture of the server in the Enclosure View. The graphical image can be seen on the OA web page. • When the VC wizard is used to configure domain, network, SAN, and server profiles, the server profile wizard does not allow double-dense server bay assignment for BL2x220c server blades. Run the domain, network, and SAN wizards, and then log out.
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.
IMPORTANT: When upgrading the HP VC 4Gb FC firmware from version VC-FC 1.2x to version VC-FC 1.40, the VC-FC module can drop connectivity temporarily during the activation process. A redundant customer configuration experiences a failover with no loss of application connectivity to the fabric. • If the firmware update procedure indicates a failure to activate a module or appears to be stuck, it might be caused by a timeout, a stale web page, or both.
Virtual Connect Enterprise Manager Support • Virtual Connect Enterprise Manager (VCEM) v1.40 provides full compatibility and support for VC firmware v1.3x, v2.x, v2.1x, and v2.3x. • For VCEM availability and full product details, visit the HP website (http://www.hp.com/go/vcem) or contact your HP representative.
