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 In this section HP Virtual Connect Manager firmware ....................................................................................................... 4 Supported hardware................................................................................................................................. 4 Firmware upgrade requirements.................................................................................................................
o HP QLogic QMH2462 4Gb FC HBA for c-Class BladeSystem o HP Emulex LPe1105-HP 4Gb FC HBA for c-Class BladeSystem (Microsoft® Windows® and VMware ESX 3.01) For the latest list of supported hardware, see the HP website (http://www.hp.com/go/bladesystemupdates). Firmware upgrade requirements IMPORTANT: For compatibility and proper operation of HP Virtual Connect Manager, all system firmware must be current.
Server blades and mezzanine cards that do not meet the required firmware versions will not properly accept Virtual Connect-assigned parameters (MACs, WWNs, etc.) and will maintain factory defaults. However, these server blades will have the Ethernet network and Fibre Channel fabric connectivity specified in their Virtual Connect server profiles. This connectivity enables the use of network-based firmware update tools to update server blade and mezzanine firmware.
New features The VC-Enet version 1.15 firmware includes the following features: • Smart Link A network enabled with Smart Link automatically drops link to the server ports if all uplink ports lose link. This feature can be useful for certain server network teaming (bonding) configurations. • Native VLAN Identifying a network on a shared uplink set as the native VLAN causes all untagged incoming packets to be placed on this network. All outgoing packets are VLAN tagged.
Important notes and recommendations When a c-Class enclosure is used with Virtual Connect v1.15 or v1.15a, 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 VC-Enet or VC-FC module, it remains configured for that module type until the overall VC domain is deleted.
• Back up the VC 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 In this section General ................................................................................................................................................ 10 Fibre Channel and SAN boot .................................................................................................................. 10 User interface ........................................................................................................................................ 11 Firmware update ..........
• Server blade boot can be delayed when a VC-FC uplink port is attached to a Brocade switch and more than one server blade HBA is aggregated through that uplink port 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. User interface • Virtual Connect Manager allows users to change the number of VC-FC Module uplink ports connected to an external Fabric Switch without a warning while a server might be accessing remote storage devices.
stylesheet may be empty, or it may not be a well-formed XML document." This pop-up can be dismissed without consequences.
Resolved issues The following issues that existed in Virtual Connect 1.10 have been resolved in Virtual Connect 1.15. • To move a server profile from a device bay containing a storage blade to another bay, the storage blade must first be removed. • Do not create or modify a network name with a hyphen ("-") in the name. Only use characters that are alpha-numeric (a-z, A-Z, 0-9) and the underscore ("_").
• When running with 16:1 oversubscription ratio on a VC-FC module, the hardware registers do not allow auto-routed traffic for the sixteenth server blade. When this scenario occurs, the firmware routes FC frames, causing a significant drop in the performance.
