HP Virtual Connect Version 1.
© Copyright 2008 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 Supported hardware.................................................................................................................................. 4 Firmware upgrade requirements .........................................
Hardware and firmware requirements HP Virtual Connect firmware The latest HP Virtual Connect firmware package (version 1.32) contains the following firmware versions: • HP VC-Enet version 1.32 • HP 4Gb VC-FC version 1.21 Supported hardware Version 1.
o HP NC326i Integrated Dual Port PCI Express Gigabit Server Adapter o HP NC326m PCI Express Dual Port Multifunction Gigabit Server Adapter o HP NC382m PCI Express Dual Port Multifunction Gigabit Server Adapter o HP NC325m PCI Express Quad Port Gigabit Server Adapter o HP NC360M Dual Port 1GbE BL-c Adapter o HP NC364M Quad Port 1GbE BL-c 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 har
Product Recommended firmware version Minimum firmware version BL460c and BL480c System ROM 2007.08.21 or higher — BL465c and BL685c System ROM 2007.09.23 or higher — xw460c System ROM 2007.04.03 Rev A or higher — BL680c G5 System ROM 2007.08.09 or higher — BL860c System Firmware 04.05 or higher — BL870c System Firmware 04.05 or higher — BL495c G5 System ROM 2008.08.04 or higher — NC382m Boot code version 4.4.14 and MBA version 4.4.
connectivity specified in their Virtual Connect server profiles. This connectivity enables the use of networkbased firmware update tools to update server blade and mezzanine firmware. HP Virtual Connect Fibre Channel Module Compatibility Matrix The following table lists the switches and firmware versions that are supported with HP Virtual Connect Fibre Channel interconnect modules. Switch family Supported versions Unsupported switches Brocade and FOS 5.3.1, 5.3.0, 5.3.0a, 5.3.0b, 5.3.0c, 5.3.0d, 5.2.
New features Virtual Connect version 1.
Important notes and recommendations When a c-Class enclosure is used with Virtual Connect v1.32 and higher, the following configuration restrictions and guidelines apply: • HP recommends using HP BladeSystem c-Class Virtual Connect Support Utility v1.3.0 or higher to install the HP VC-Enet v1.32 and HP 4Gb VC-FC v1.21 firmware. For the procedures, be sure to read the instructions on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.
• To improve network performance and prevent unnecessary Spanning Tree Topology Change Notifications (TCN) on the network, configure Ethernet switches connected to Virtual Connect with the same Spanning Tree settings you would use when connecting to a server blade NIC. For Cisco switches, this is done by using the portfast command to enable ports connected to a VC-Enet module. This action ensures that link state changes on Virtual Connect do not cause a TCN.
• The VC Manager CLI command show fabric X displays only the Port (Connected From) WWN for the physical uplink ports of a Virtual Connect fabric. The term "WWN" in the display output refers to the Port WWN and not the Node WWN. • Support for double-dense server blades (BL2x220c) in a Virtual Connect domain requires the domain to be created or imported using VC v1.31 firmware or higher. If a domain was created in VC v1.2x or lower and then updated to VC v1.
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. A new icon has been added to the Virtual Connect Manager banner line that indicates a configuration update is in progress or if the backup module has not been updated to the current configuration changes. • The VC Manager domain configuration database in VC v1.
any servers are rebooted or power cycled while the credential recovery is occurring, the MAC addresses and WWNs might be returned to the factory default settings. • If an enclosure import is attempted with a server blade in a failed state, VC 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 OA.
• When configuring Trap Destination IP addresses for the VC-FC modules, be sure that trap destinations are capable of supporting SNMPv1 type traps. • In a c3000 enclosure with full-height server blades and FC mezzanine cards installed in slot 2 and slot 3, the VC Manager might assign and incorrectly display the same WWN to both FC mezzanine cards. This configuration is unsupported and one of the mezzanine cards should be removed. • If updating from Virtual Connect Manager v1.
IMPORTANT: With the HP 4Gb VC-FC upgrade for version 1.21, 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 internal GUI-based firmware update support within VC v1.2x is used to perform either a manual or automated firmware update for the HP 4Gb VC-FC v1.
• In some circumstances, the primary module might fail to activate after an Automated firmware update. If the primary module fails to activate and the firmware update page shows the new firmware version under the "Installed" tab, reset the primary module to activate the new firmware version. Virtual Connect Enterprise Manager Support • VCEM v1.10 does not import and manage Virtual Connect domains configured with VC firmware v1.32. • An attempt to import a VC domain running VC v1.
Resolved issues The following issues that existed in Virtual Connect v1.31 have been resolved in Virtual Connect v1.32: • When performing a VC GUI firmware upgrade, the activation of the primary module did not occur after a successful firmware upgrade. • The Fibre Channel configuration was not updated correctly to the Fibre Channel modules when multiple fabrics were created on a single HP Virtual Connect FC module and the module was reset, replaced, or hot-plugged.
4. If the health on all modules is OK and all configurations are In Sync, continue to Step 3—Update the Virtual Connect firmware. 5. If Health=Degraded/Failed, the health of the module as reported by the OA is not healthy. Log in to the OA for additional information or replace the hardware and rerun the health check. 6. If Domain Configuration=Not in Sync, the domain configuration is not in sync between the primary and backup VC Manager. Wait 2 minutes, and then rerun the health check.
4. If the health on all modules is OK and all configurations are In Sync, continue to Step 5—Update the Onboard Administrator firmware. 5. If Health=Degraded/Failed, the health of the module as reported by the OA is not healthy. Log in to the OA for additional information or replace the hardware and rerun the health check. 6. If Domain Configuration=Not in Sync, the domain configuration is not in sync between the primary and backup VC Manager. Wait 2 minutes, and then rerun the health check.
a. Login to VC Manager. b. Create a network named "None" with no uplinks, and then click Apply. c. Delete the "None" network, and then click Apply. d. Rerun the health check. Contact HP Support Before contacting HP Support, do the following: 1. Login to Virtual Connect. 2. Select Export Support Information from the Tools pull-down menu, and then save the file. 3. Login to Onboard Administration and execute the show all command, and then save the output to a file. 4.
