HP Virtual Connect Manager Version 1.
© Copyright 2007 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 Manager firmware ......................................................................................................... 4 Supported hardware.................................................................................................................................. 4 Firmware upgrade requirements ..............................................
Hardware and firmware requirements HP Virtual Connect Manager firmware The latest HP Virtual Connect Manager firmware package (version 1.20) contains the following firmware versions: • HP 1/10Gb VC-Enet version 1.20 • HP 4Gb VC-FC version 1.10 IMPORTANT: The VC-Enet module firmware must be updated to version 1.20 before updating the VC-FC module firmware. Otherwise, the VC-FC firmware might not appear to be successfully updated. Supported hardware Version 1.
o HP NC326m PCI Express Dual Port Multifunction Gigabit Server Adapter o HP NC325m PCI Express Quad Port Gigabit Server Adapter o HP QLogic QMH2462 4Gb FC HBA for c-Class BladeSystem o HP Emulex LPe1105-HP 4Gb FC HBA for c-Class BladeSystem For the latest list of supported hardware, see the HP website (http://www.hp.com/go/bladesystemupdates). Firmware upgrade requirements IMPORTANT: For optimal operation of HP Virtual Connect Manager, use the recommended firmware versions.
Product Recommended firmware version Minimum firmware version NC326i, NC325m, and NC326m Boot code version 3.28 and C Class option ROM 1.1.3* or later — To use NC325m with the BL680c G5 server blade, the option ROM must be updated to NC325m Boot code version 3.28 and C Class option ROM 1.2.8 or later. To use NC326m with the BL680c G5 server blade, the option ROM must be updated to NC326m Boot code version 3.28 and C Class option ROM 1.2.8 or later.
Switch family Supported versions Unsupported switches McData and E/OS 9.03.00 • McDATA Intrepid 10000 Director switch HP M-series E/OS 9.00.00 Fibre Channel switches E/OS 8.02.00 Cisco and SAN-OS 3.1(2a), 3.1(2b), 3.
New features The VC-Enet version 1.20 firmware includes the following features: • HP BladeSystem c-Class c3000 Enclosure support • HP ProLiant BL680c G5 Server Blade support • HP ProLiant xw460c Blade Workstation support • Command line interface for Virtual Connect Manager The CLI enables administrators to manage a Virtual Connect Domain configuration using the command line, either interactively at the SSH login console or by using a script.
• Support for Multiple Users Multiple users are allowed within multiple VC Manager windows. • Support for longer passwords Password length has been extended to 39 characters. • Separate MAC and PXE assignments Previously, PXE support was associated with VC assigned MAC addresses. This feature enables the user to control PXE settings even if they are not using VC assigned MACs. PXE settings for each server profile now include "Enabled", "Disabled", or "Use BIOS".
Important notes and recommendations When a c-Class enclosure is used with Virtual Connect v1.20, the following configuration restrictions and guidelines apply: • Plan your interconnect module usage carefully before running the Virtual Connect Domain Setup Wizard. After an interconnect bay is configured for use with a Virtual Connect Ethernet module or VC-FC module, it remains configured for that module type until the overall VC domain is deleted.
• Back up the Virtual Connect domain configuration each time changes are made. While saved in non-volatile memory and check-pointed to the neighboring module, HP recommends saving the configuration external to the enclosure. • Removing a VC-Enet module and plugging it into another enclosure causes the configuration information on that module to be cleared. This action prevents a configured spare from overwriting configuration data in another enclosure.
Known issues General • For configuration changes, the VC Manager can take up to 90 seconds for the new information to be saved to non-volatile storage. Configuration information might be lost if power is removed during this update time. • When an SSH key is uploaded using the GUI interface, user authentication fails. The user must enter the password when logging in using SSH. • The VC Manager CLI set ldap command IpAddress option supports only an IP address.
• If an enclosure import is attempted with a server blade in a failed state, the Virtual Connect Manager might report an erroneous error. If the import completes, close the browser and log in again to verify the import was successful. The working state of all server blades can be verified using the Onboard Administrator. • Changes in the server ROM-based setup utilities (RBSU) can override Virtual Connect server profile settings for PXE (enabled or disabled).
• Virtual Connect Manager shows either a server blade or an interconnect module as degraded (but not both) for an I/O Ekey mismatch. • Network uplinks that are linked after the Network Setup Wizard has been started may not show proper link status in the wizard. When the wizard is completed, all uplink link statuses are displayed correctly. • A server profile can be assigned to a device bay with a server that has fewer physical NIC ports than defined in the server profile.
• • While executing individual (not automated) firmware updates, the Update button might appear after clicking the Activate button for a VC-Enet module. o Ignore the Update button if it persists for more than 3 minutes. If the Update button appears for more than 3 minutes, then the firmware update failed and should be re-attempted. o If the Update button is clicked in this state, it reports an error in installation. This error can be ignored.
Resolved issues The following issues that existed in Virtual Connect v1.16 have been resolved in Virtual Connect v1.20: • The Virtual Connect Manager now recovers from a dual-OA failover or the replacement of a single OA without requiring a reset of the Virtual Connect Manager. • Under certain fail-over conditions a loop could be caused for a very short window (up to about 120 mS). This time was sufficient for BPDUs to slip through and BPDUguard to run.
