HP Virtual Connect Version 1.
© Copyright 2008, 2009 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.34) contains the following firmware versions: • HP VC-Enet version 1.34 • HP 4Gb VC-FC version 1.30 Supported hardware Version 1.
o HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter 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
Upgrade/downgrade from To VC 1.30 (VC-FC To VC 1.31 (VC1.20) FC 1.20 To VC 1.32 (VCFC 1.21) To VC 1.34 (VCFC 1.30) VC 1.32 Normal Normal — Fabric outage* VC 1.34 Fabric outage* Fabric outage* Fabric outage* — * The module must be reset after the upgrade or downgrade. For additional information on required firmware versions and to download firmware upgrades, see the HP website (http://www.hp.com/go/bladesystemupdates).
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 higher. — 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 higher. 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 higher. NC360m, NC364m C Class option ROM 1.0.
Switch family Supported versions Unsupported switches McDATA and E/OS 9.07.02 — HP M-series E/OS 9.07.01 Fibre Channel switches E/OS 9.06.02 E/OS 9.03.00 E/OS 9.02.00 E/OS 9.00.00 E/OS 8.02.00 Cisco and NX-OS 4.1(1b) HP C-series SAN-OS 3.3(1a), 3.2(3), 3.2(2c), 3.1(3a), 3.1(2b), 3.1(2a) Fibre Channel switches HP 8Gb simple SAN connection switches 7.6.0.02.00 Cisco MDS 9020 Fabric Switch — For the most up-to-date support information, see the HP website (http://www.hp.com/storage/spock).
New features Virtual Connect version 1.
Resolved issues The following issues that existed in Virtual Connect v1.32 have been resolved in Virtual Connect v1.34: • With LDAP authentication, users were unable to login/authenticate to Virtual Connect Manager when their CN (Common Name) contained a comma (Example: Jones, Fred). • With LDAP authentication, users were unable to login/authenticate to Virtual Connect Manager using their sAMAccountName.
Important notes and recommendations When a c-Class enclosure is used with Virtual Connect v1.34 and higher, the following configuration restrictions and guidelines apply: • HP recommends using HP BladeSystem c-Class Virtual Connect Support Utility v1.3.1 or higher to install the HP VC-Enet v1.34 and HP 4Gb VC-FC v1.30 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.
• Cisco MSD 9134 requires minimum firmware revision of 3.2(2)c, or higher. • The Fibre Channel login sequence can be delayed by approximately 20 seconds when more than one server blade HBA is aggregated through the same VC-FC uplink port attached to a Cisco switch and these HBAs are in the same zone. To avoid this problem, do not place server HBAs in the same zone on the fabric switch.
• If a server is rebooted several times while its server profile is being edited, an error displaying an XSL transformation failure may be displayed. Do not edit a server profile while repeatedly rebooting a server. • In the Bay Summary screen for a VC-FC module in Virtual Connect Manager, some servers might be displayed with the incorrect model number. The model number is displayed correctly in other screens and in the Onboard Administrator.
• In some circumstances while uploading (staging) a firmware update package, the progress indicator might appear to be stuck at 0%. Normally, the upload operation completes in a few minutes. If the upload does not complete, the operation times out in 30 minutes, and then the upload can be restarted.
3. Click Backup Configuration. 4. Navigate to the hard drive location for the backup file. 5. Name the file (usually the domain name), and then click Save. 6. Log out of Virtual Connect and close the browser. Step 2—Run a health check on the Virtual Connect domain 1. From a local system with VCSU installed, execute the following command: vcutil -a healthcheck -i -u -p 2. 3.
o If successful, continue to Step 4—Run a health check on the Virtual Connect domain. o If all modules are not successfully updated, contact HP Support (on page 21). o If the update process fails to complete after 1 hour, contact HP Support (on page 21). Step 4—Run a health check on the Virtual Connect domain 1. From a local system with VCSU installed, execute the following command: vcutil -a healthcheck -i -u -p 2. 3.
3. o Domain Configuration=In Sync (bays 1 and 2 only) o Module Configuration=In Sync (all bays) Verify that the status on all VC-FC modules in the enclosure are in the following state: Health=OK 4. If the health on all modules is OK and all configurations are In Sync, upgrade is complete. 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.
