HP Virtual Connect Version 3.
© 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 3.00) contains the following firmware versions: • HP VC-Enet version 3.00 • HP VC 4Gb FC version 1.40 • HP VC 8Gb 24-Port FC version 1.02 • HP VC 8Gb 20-Port FC version 1.40 IMPORTANT: When updating firmware, update each domain with the entire firmware package, which includes the individual VC-Enet and VC-FC firmware.
Firmware Version Version Version Version Version Version N/A N/A N/A 1.00 1.01 1.02 Connect VC 8Gb 20-Port FC firmware within Virtual Connect The following table shows firmware upgrade/downgrade support for the HP FC 4Gb VC Modules or HP FC 8Gb 20-Port VC Modules. To VC 2.3x To 3.00 (VC-FC 1.40) (VC-FC 1.
For more information on required firmware versions and to download firmware upgrades, see the HP website (http://www.hp.com/go/bladesystemupdates). Version 3.00 of HP Virtual Connect Manager checks the server ROM image version and displays an incompatible state only for server blades that have a VC Server Profile assigned and are using incompatible server ROM versions. Version checking of mezzanine card firmware is not available, so be sure to verify that the mezzanine card firmware is up-to-date.
• After an enclosure import, the Virtual Connect CLI Interface will show the Stacking Links "Connections Status" as: "Failed" until all modules have been initialized. This may take up to 30 seconds depending on the actual configuration. • Before installing any BL8*0c i2 servers make sure that the following actions are taken: o Verify that there are no profiles assigned to any of the bays where the BL8*0c i2 servers will be installed. o Perform the updates to the recommended OA and VC FW revisions.
New features The VC 3.
Resolved issues The following issues have been resolved: • Resolved an issue where pre-existing Virtual Server IDs on a blade server will not be cleared when the blade server is inserted into an enclosure with existing profiles that do not contain any Virtual MACs, WWNs, or Server IDs. • Resolved an issue where jumbo frames are incorrectly reported as iflnErrors.
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.
firmware. To resolve this issue, reset the VCM on the primary module, or reset the primary module using the OA. • If a VC-FC module is replaced with a spare VC-FC module without powering down the servers, and if the server has profiles assigned to it with FC connections, servers are allowed to log in for a brief period of time through an uplink of the new module.
• 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 or higher, the VC 2.10 SNMP configuration is converted to a comparable VC 2.
On some combinations of Firefox web browser, Adobe Flash Player, and Operating System, the Adobe Flash Player will cause the Firefox web browser to crash unexpectedly - especially if there are multiple versions of the Flash Player Plugin installed with Firefox or if there is an older/unsupported version of the Flash Player Plugin (e.g. such as Flash v8.0) installed with Firefox, even if the older/unsupported version of the Flash Plugin is disabled. It is recommended that Virtual Connect 3.
Virtual Connect Enterprise Manager Support • Virtual Connect Enterprise Manager (VCEM) v1.60 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.
