QuickSpecs

Overview
QLogic QMH2462 4Gb FC HBA for HP c-Class BladeSystem
The QLogic QMH2462 4Gb FC HBA is a dual channel PCI Express mezzanine form factor card specifically designed for c-Class BladeSystem server blades. Operating systems supported include Windows and Linux. This HBA is qualified for use in all c-Class blade servers. It is optimized for HP StorageWorks as well as supported by third-party SAN vendors. For details on supported HP StorageWorks Fibre Channel SAN Switches, please consult the SAN Design Reference Guide at the following WEB address: http://h18006.www1.hp.com/products/storageworks/san/documentation.html

Models

QLogic QMH2462 4Gb FC HBA for HP c-Class BladeSystem 403619-B21

Key Features

Two 4Gb/s Fibre Channel ports 4/2/1 automatic speed negotiation without throttling down to the lowest target speed on the network Multi-Path support for redundant HBAs and paths including Linux driver failover. Superior performance capable of sustaining up to 150,000 I/Os per second per channel RoHS compliance Common drivers for 4Gb and legacy 2Gb HBAs QLogic SANsurfer Manager for centralized management and remote control of distributed HBAs.

Features and Benefits

Higher performance with a low price per channel Investment protection with 4/2/1 auto speed negotiation Supports the Windows and Linux operating environments Provides the flexibility and broad interoperability need for complex highly scalable SANs Multi-path software for Linux built into the driver

DA - 12523

Worldwide Version 8 October 5, 2010

Page 1

Standard Features
Software Features BladeSystem compatibility
NOTE: The QLogic QMH2462 4Gb FC HBA for HP c-Class BladeSystem must be deployed with the c-Class BladeSystem infrastructure and will only work with the BL c-Class Server Enclosure. Compatible with current releases of HP ProLiant and HP Integrity c-class Blade Servers supporting HP ProLiant and Integrity Type 1 Mezzanine Cards Servers

Switch interoperability

HP StorageWorks and Third Party Switches 4Gb Switches and Directors 2Gb Switches and Directors Compatible with Fibre Channel switches including HP StorageWorks and third party vendors including Cisco, Brocade, and McDATA

Page 2

Service and Support
HP Care Pack Services: Packaged server and storage services for increased uptime, productivity and ROI When you buy HP server and storage products and solutions, it's also a good time to think about what levels of support you may need. Our portfolio of service options reduce deployment and management worries while helping you get the most out of your server and storage investments. We take a holistic approach to your environment, bridging servers, blades, storage, software and network infrastructures with our packaged HP Care Pack Services for servers and storage. Protect your business beyond warranty When it comes to robustness and reliability, standard computing equipment warranties have matured along with technology. Good news that can also create problems stemming from depending on standard warranties designed to only protect against product defects and some downtime causes. Using a standard approach to warranty uplifts, such as HP Care Pack Services, helps reduce downtime risks and provides operational consistency for mission-critical and standard business computing. HP Care Pack Services: Upgrading or extending standard server and storage warranties cost effectively HP Care Pack Services offer a standard reactive hardware and software support services suite sold separately, or combined with our Support Plus and Support Plus 24 services. The portfolio also provides a combination of integrated proactive and reactive services, such as Proactive 24 Service and Critical Service. In addition with HP Proactive Select, you can acquire the specific proactive constancy and technical services. HP Proactive Select menu offers a broad set of service options that you can mix and match depending on your specific requirements. Proactive service options include offers for server, storage, network, SAN device, software, environment and education services. HP server and storage lifecycle support services offers a full spectrum of customer care-from technology support to complex migrations to complete managed services. HP Factory Express provides customization, integration and deployment services for turnkey solutions. HP Education Services offer flexible, comprehensive training on to help your IT staff get the most out of your server and storage investments. HP Financial solutions extend innovative financing and cost-effective asset management programs-from purchase to equipment retirement. Learn more: www.hp.com/services/servers and www.hp.com/services/storage NOTE: Care Pack Services availability may vary by product and country. HP Care Pack Services are sold by HP and HP Authorized Service Partners: Services for customers purchasing from HP or an enterprise reseller are quoted using HP order configuration tools. Customers purchasing from a commercial reseller can find HP Care Pack Services at http://www.hp.com/go/lookuptool

Page 3

Recommended Services
Recommended HP Care Pack Services for optimal satisfaction with your HP product
Hardware Options Support HP Care Packs provide support for all HP-branded hardware options qualified for inclusion in your server or storage solution. Any additional HP-qualified options installed within the server are covered at the same service level and for the same period as the server and no additional cost. Help improve or maintain system uptime Convenient onsite support Committed response time http://h20195.www2.hp.com/V2/GetPDF.aspx/5982-6547EEE 3-Year HP Hardware Support Onsite Service, 4-hour response, 24x7 Provides you with rapid remote support and if required an HP authorized representative who will arrive on site any time and day of the year to begin hardware maintenance service within 4 hours of the service request being logged. This service provides a trained HP service specialist to perform an installation that meets HP quality standards, for: Help improve or maintain system uptime Convenient onsite support Committed response time http://h20195.www2.hp.com/V2/GetPDF.aspx/5982-6547EEE HP Installation and Startup of HP ProLiant Servers Provides for the installation of your new HP ProLiant server and operating system to assist you in bringing your new HP ProLiant server and operating system into operation in a timely and professional manner. This service provides a trained HP service specialist to perform an installation that meets HP quality standards, for: Delivery of the service at a mutually scheduled time convenient to your organization Availability of an HP service specialist to answer basic questions during the onsite delivery of this service Custom installation as detailed in "Delivery specifications" or in a Statement of Work (SOW) Verification prior to installation that all service prerequisites are met http://h20195.www2.hp.com/V2/GetPDF.aspx/5982-7572ENN.pdf

Page 4

Optional Services
Optional HP Care Pack Services that will enhance your HP product experience
3-Year HP Hardware Support Onsite Call-to-Repair (CTR) Service, 6- or 24-hour As an alternative to our recommended support level, for customers who need committed call-to-repair for server hardware. Provides your IT manager with a team of support specialists who will quickly begin troubleshooting the system to help return the hardware to operating condition within 6 or 24 hours of the initial service request to the HP Global Solution Center. http://h20195.www2.hp.com/V2/GetPDF.aspx/5981-6636ENN 3-Year HP Support Plus 24 As an alternative to our recommended support level, for customers who need access to responsive 24x7 hardware and software support plus software updates on HP and selected third party products: For a higher return on your server and storage technology, our 3-year combined reactive support service delivers integrated onsite hardware/software support services available 24x7x365, including access to HP technical resources, 4-hour response onsite hardware support and software updates. http://h20195.www2.hp.com/V2/GetPDF.aspx/5981-6638EEE HP Proactive Select Service Customer needs on demand access to consulting, technical proactive services and education courses Provides a flexible way to purchase HP best-in-class consultancy and technical services. You can buy Proactive Select Service Credits when you purchase your hardware and then use the credits over the next 12 months. http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-3842ENN

eSupport

HP eSupport is a portfolio of technology-based services that assist you with managing your business environment - from the desktop to the data center. Support Portal The HP support portal provides one-stop access to the information, tools and services you need to manage the daily operations of your IT environment. include: Features include Access to self-solve tools (including search technical knowledge base) Efficient logging and tracking of support cases Collaboration with other business and IT professionals Download of patches and drivers Access to diagnostic tools Proactive notification of relevant information Access to certain features of the support portal requires an HP service agreement. To access the support portal, visit: http://www.hp.com/support

Page 5

HP Insight Remote Support software delivers secure remote support for your HP Servers and Storage, 24 X 7, so you can spend less time solving problems and more time focused on your business. You can have your systems remotely monitored for hardware failure using secure technology that's been proven at thousands of companies around the world. In many cases, you can avoid problems before they occur.
Customer Technical Training
In today's cost-conscious business environment, IT professionals, developers, consultants and users face an interesting challenge: how to keep up with the latest technologies and expand important skills while delivering profitable results on current projects. To help address this challenge, HP offers innovative training solutions that help keep you up-to-date on virtualization, server, storage, Insight Control, Citrix, Microsoft and open source/Linux-related topics-while spending less time away from business-critical activities.

HP Services Awards

HP Technology Services continues to be recognized for service and support excellence by customers, partners, industry organizations and publications around the world. Recent honors and award reflect our services team's dedications, technical expertise, professionalism and uncompromising commitment to customer satisfaction.
Additional Services Information
To learn more on HP ProLiant servers, HP BladeSystem servers and HP StorageWorks storage products, please contact your HP sales representative or HP Authorized Channel Partner. Or visit: www.hp.com/services/proliant or www.hp.com/services/bladesystem or http://www.hp.com/hps/storage

Page 6

Related Options
Service and Support Offerings (HP Care Pack Services)
NOTE: The HP Care Pack service part numbers below for ProLiant BL c-Class server blades, cover the server blade and all HP branded hardware options qualified for the server, purchased at the same time or afterwards, internal to the server. Hardware Services On-site Service 4-Hour On-site Service, 5-Day x 13-Hour Coverage, 3 Years, Electronic 4-Hour On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic 6-Hour Call to Repair, On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic Support Plus 24 Onsite HW support 24x7, 4hr response and Microsoft O/S SW Tech support offsite, onsite at HP's discretion, 24x7 2hr response time incl. HP holidays, Electronic NOTE: HP Care Pack services for the c7000 and c3000 Enclosure cover the enclosure, power supplies and fans. HP qualified rack options are covered by these services when installed within the same rack. HP Supported Ethernet devices covered include the Ethernet Pass-Through Module, Fibre Channel Pass-Through Module, Cisco Catalyst 3020 Blade Switch and GbE2c Ethernet Blade Switch. Hardware Services On-site Service Next Business Day On-site Service, 5-Day x 9-Hour Coverage, 3 Years, Electronic NOTE: Uplifts the Ethernet devices to the same level of warranty as the c-class enclosure 4-Hour On-site Service, 5-Day x 13-Hour Coverage, 3 Years, Electronic 4-Hour On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic 6-Hour Call to Repair, On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic NOTE: The HP Care Pack service part numbers below covers the HP 4Gb, 12 Port SAN Switch & 4Gb, 12 Port SAN Switch Upgrade LTU. Hardware Services On-site Service Next Business Day On-site Service, 5-Day x 9-Hour Coverage 3 Years, Electronic 4-Hour On-site Service, 5-Day x 13-Hour Coverage, 3 Years, Electronic 4-Hour On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic 6-Hour Call to Repair, On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic NOTE: The HP Care Pack service part numbers below covers the HP 4Gb, 24 Port SAN Switch. Hardware Services On-site Service Next Business Day On-site Service, 5-Day x 9-Hour Coverage, 3 Years, Electronic 4-Hour On-site Service, 5-Day x 13-Hour Coverage, 3 Years, Electronic 4-Hour On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic 6-Hour Call to Repair, On-site Service, 7-Day x 24-Hour Coverage, 3 Years, Electronic Hardware Installation, Electronic NOTE: The HP Care Pack service part numbers below covers the HP 4Gb, 24 Port SAN Switch Power Pack. Hardware Services On-site Service DA - 12523 Worldwide Version 8 October 5, 2010

UE458E UE459E UE460E

UE473E

UE477E

UE478E UE479E UE480E
UC007E UC008E UC009E UC023E
UE436E UE437E UE438E UE439E U5988E

Page 7

Support Plus Onsite HW support, 8am-9pm, M-F, 4hr response and SW Tech support offsite, onsite at HP's discretion, 8am-9pm, M-F 2hr response time excl. HP holidays, Electronic Support Plus 24 Onsite HW support 24x7, 4hr response and SW Tech support offsite, onsite at HP's discretion, 24x7 2hr response time incl. HP holidays, Electronic Installation & Start-up Services HP Installation & Startup Service for HP BladeSystem Infrastructure, Electronic NOTE: Provides for an integrated hardware and software implementation that includes remote service planning, onsite deployment of hardware and software, installation verification testing and customer orientation. Hardware deployment covers the installation of a single BladeSystem enclosure that include server blades (up to 16), Ethernet network interconnect, and power options. Software deployment covers the installation and configuration of HP Systems Insight Manager (SIM), HP Rapid Deployment Pack (RDP), and deploy up to two operating system editions of either Windows or Linux, using scripted operating system installation software ProLiant BL c-Class Blade Server Hardware Installation, Electronic ProLiant BL c-Class Enclosure and Server Blade Hardware Installation, Electronic Provides for the Installation and Start-up of ProLiant Essentials Rapid Deployment Pack, Electronic NOTE: Provides installation on a Customer supplied server designated as a Deployment Server. Includes the deployment of a single server. This new server will be deployed using either one of the pre-configured scripts or an image. In addition, the service will provide for the capture and storage of the configuration of the newly deployed server and orientation on product usage. To be delivered during standard office ours, standard office days. Provides for the Installation and Start-up of Rapid Deployment Pack Implementation of Rapid Deployment Pack (Basic) (Electronic) NOTE: Service coverage: onsite installation of the Vulnerability and Patch Management (VPM) software on a customer designated server, configuration of the VPM software to acquire security patches, enabling the VPM software to scan up to five (5) systems, applying the security patches to the designated servers, generating a report from VPM that shows the vulnerability assessment results, and providing customer with an orientation to the software. Provides for the Installation and Start-up of System Insight Manager (Electronic) Provides for the Installation and Start-up of System Insight Manager Agents (Electronic) NOTE: For more information, customer/resellers can contact http://www.hp.com/services/servers Software Operating Environment Care Packs Microsoft Software Operating Environment Software Telephone 9x5 - 3 incident (Electronic) Red Hat Software Operating Environment Software Telephone 9x5 - 10 incident (Electronic) SUSE Software Operating Environment Software Telephone 9x5 - 3 incident (Electronic)

UE728E

UE729E

UE602E

UE493E UE494E U5683E

UA042E

UA041E UA040E

U8169E U3402E U9615E

Page 8
ProLiant Essentials Operating Environment, - 5 Day, 9x5,1 year, 3 incident (Electronic) ProLiant Essentials Operating Environment, - 5 Day, 24x7,1 year, 3 incident (Electronic) ProLiant Essentials Operating Environment, - 5 Day, 9x5,1 year, 10 incident ProLiant Essentials Operating Environment, - 5 Day, 24x7,1 year, 10 incident ProLiant Essentials Operating Environment, - 5 Day, 9x5,1 year, 25 incident ProLiant Essentials Operating Environment, - 5 Day, 24x7,1 year, 25 incident ProLiant Essentials Operating Environment, - 5 Day, 9x5,1 year, 50 incident ProLiant Essentials Operating Environment, - 5 Day, 24x7,1 year,50 incident ProLiant Essentials Operating Environment, - 5 Day, 9x5,1 year, unlimited SW Tech Support ProLiant Essentials Operating Environment, - 5 Day, 24x7,1 year, unlimited SW Tech Support ProLiant Essentials Operating Environment, - 5 Day, 9x5, 3 year, unlimited SW Tech Support ProLiant Essentials Operating Environment, - 5 Day, 24x7, 3 year, unlimited SW Tech Support NOTE: For more information, customer/resellers can contact http://www.hp.com/services/servers
U8222E U8301E UE006E UE116E UE117E UE118E UE119E UE120E UE121E UE452E UE453E UE454E

Page 9

Technical Specifications
System Unit Dimensions (H x W) Media Ports System Inlet Temperature
Relative Humidity (non-condensing)

Altitude

4.460 in x 3.970 in (113.28mm x 100.84mm) N/A (Backplane connection to Virtual Connect, Switch or Pass-Thru Module) Two Operating 10 to 35C (50 to 95F) at sea level with an altitude derating of 1.0C per every 305 m (1.8F per every 1000 ft) above sea level to a maximum of 3050 m (10,000 ft), no direct sustained sunlight. Maximum rate of change is 10C/hr (18F/hr). The upper limit may be limited by the type and number of options installed. System performance may be reduced if operating with a fan fault or above 30C (86F). Non-operating -30 to 60C (-22 to 140F). Maximum rate of change is 20C/hr (36F/hr). Operating 10 to 90% relative humidity (Rh), 28C (82.4F) maximum wet bulb temperature, noncondensing. Non-operating 5 to 95% relative humidity (Rh), 38.7C (101.7F) maximum wet bulb temperature, noncondensing. Operating 3050 m (10,000 ft). This value may be limited by the type and number of options installed. Maximum allowable altitude change rate is 457 m/min (1500 ft/min). Non-operating 9144 m (30,000 ft). Maximum allowable altitude change rate is 457 m/min (1500 ft/min).

Environment-friendly Products and Approach
End-of-life Management and Recycling
Hewlett-Packard offers end-of-life HP product return, trade-in, and recycling programs in many geographic areas. For trade-in information, please go to http://www.hp.com/go/green. To recycle your product, please go to: http://www.hp.com/go/green or contact your nearest HP sales office. Products returned to HP will be recycled, recovered or disposed of in a responsible manner. The EU WEEE directive (2002/95/EC) requires manufacturers to provide treatment information for each product type for use by treatment facilities. This information (product disassembly instructions) is posted on the Hewlett Packard web site at: http://www.hp.com/go/green. These instructions may be used by recyclers and other WEEE treatment facilities as well as HP OEM customers who integrate and re-sell HP equipment.

Page 10

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.

Page 11

HP Virtual Connect Manager Version 1.21 Release Notes and Compatibility Matrix
Part Number 463680-002 November 2007 (Second Edition)
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. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard commercial license. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
Audience assumptions This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels. About this document These release notes provide information that supersedes the information in the documentation set released with version 1.20a of Virtual Connect Manager.

Contents

Hardware and firmware requirements... 4
HP Virtual Connect Manager firmware.... 4 Supported hardware..... 4 Firmware upgrade requirements.... 5 Recommended firmware versions for this release... 5 HP Virtual Connect Fibre Channel Module Compatibility Matrix... 6
New features.... 8 Important notes and recommendations.... 9 Known issues..... 11
General..... 11 Fibre Channel and SAN boot.... 12 User interface..... 13 Firmware update..... 13

Resolved issues..... 15

Hardware and firmware requirements
HP Virtual Connect Manager firmware
The latest HP Virtual Connect Manager firmware package (version 1.21) contains the following firmware versions:
HP 1/10Gb VC-Enet version 1.21 HP 4Gb VC-FC version 1.10

Supported hardware

Version 1.21 of HP Virtual Connect firmware supports the following hardware:

Virtual Connect modules

HP 1/10Gb Virtual Connect Ethernet Module HP 1/10Gb-F Virtual Connect Ethernet Module HP 4Gb Virtual Connect Fibre Channel Module HP ProLiant BL460c Server Blade HP ProLiant BL465c Server Blade HP ProLiant BL480c Server Blade HP ProLiant BL680c G5 Server Blade HP ProLiant BL685c Server Blade HP Integrity BL860c Server Blade HP ProLiant xw460c Blade Workstation (only the two embedded Ethernet ports are supported; Ethernet and Fibre Channel mezzanine cards are not supported) HP BladeSystem c-Class c7000 Enclosure with Onboard Administrator HP BladeSystem c-Class c3000 Enclosure with Onboard Administrator HP BladeSystem Dual NC370i Multifunction Network Adapter HP NC373i Integrated Multifunction Gigabit Server Adapter HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter HP NC326i Integrated Dual Port PCI Express Gigabit Server Adapter HP NC326m PCI Express Dual Port Multifunction Gigabit Server Adapter HP NC325m PCI Express Quad Port Gigabit Server Adapter HP NC360M Dual Port 1GbE BL-c Adapter
Server blades and workstation blades

o o o o o o o

Enclosures
Integrated Network Interfaces and mezzanine cards
Hardware and firmware requirements 4
HP NC364M Quad Port 1GbE BL-c Adapter HP QLogic QMH2462 4Gb FC HBA for c-Class BladeSystem 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. Install the recommended firmware for the following items:

Server blade system ROMs Ethernet mezzanines Fibre Channel mezzanines HP BladeSystem Onboard Administrator
For additional information on recommended firmware versions and to download firmware upgrades, see the HP website (http://www.hp.com/go/bladesystemupdates).
Recommended firmware versions for this release

Product

HP Onboard Administrator
Recommended firmware version

Minimum firmware version

For c7000 enclosures, version 1.30 or later For c3000 enclosures, version 2.04 or later
For c7000 enclosures, version 2.02a or later For c3000 enclosures, version 2.04 or later
iLO BL460c and BL480c BL465c and BL685c xw460c BL680c G5 BL860c NC370i, NC373i, and NC373m
Version 1.35 or later System ROM 2007.06.28 or later System ROM 2007.04.05 or later System ROM 2007.08.09 or later System, BMC and iLO-2 version 1.01A Boot code version 1.9.6 and C Class option ROM 1.1.3* or later To use NC373m with the BL680c G5 server blade, the option ROM must be updated to NC373m Boot code version 1.9.6 and C Class option ROM 1.2.7 or later.
System ROM 2007.04.03 Rev A or later
Hardware and firmware requirements 5
NC326i, NC325m, and NC326m
Recommended firmware version
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.
NC360m, NC364m QLogic QMH2462 4Gb FC HBA
C Class option ROM 1.0.11 For ProLiant server blades, use QLogic multiboot image 1.63 (with BIOS 1.26) or later. For Integrity server blades use EFI 1.09 (in Multiboot 1.64 ) or later
HP Emulex LPe 1105-HP 4Gb FC
Emulex boot-pair 6.00a2 and 3.2a1 HBAnywhere or later
* Use the HP Gigabit Server Adapter Firmware Upgrade Utility for c-Class Blades version 1.10 (HP website (http://h18023.www1.hp.com/support/files/server/us/download/25604.html)) or one of the online methods available for the OS. To find the online update method for your OS, go to the HP website (http://www.hp.com/go/bladesystemupdates) and search for Server Blade Software & Updates.
Version 1.21 of HP Virtual Connect firmware 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. No version checking of mezzanine card firmware is available, so be sure to verify that the mezzanine card firmware is up-to-date. Server blades and mezzanine cards that do not meet the required firmware versions do not properly accept Virtual Connect-assigned parameters (MACs, WWNs, and so on), and therefore maintain factory defaults. However, these server blades do have the Ethernet network and Fibre Channel fabric 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.
Hardware and firmware requirements 6

Switch family

Brocade and HP B-series Fibre Channel switches

Supported versions

FOS 5.2.1b, 5.3.0, 5.3.0b FOS 5.1.0d

Unsupported switches

Brocade 4/12 SAN Switch for c-Class Brocade 4/24 SAN Switch for c-Class HP MSA SAN switches HP StorageWorks 2/8 EL and 2/16 EL switches McDATA Intrepid 10000 Director switch
McData and HP M-series Fibre Channel switches Cisco and HP C-series Fibre Channel switches
E/OS 9.03.00 E/OS 9.00.00 E/OS 8.02.00
SAN-OS 3.0(2a), 3.0(3), 3.1(2a), 3.1(2b), 3.1(3a)
Cisco MDS 9124e Fabric Switch for c-Class Cisco MDS 9124 Fabric Switch Cisco MDS 9020 Fabric Switch
Hardware and firmware requirements 7

New features

The VC-Enet version 1.21 firmware includes the following features:
Support for HP Virtual Connect Enterprise Manager 'Profile Pending' state handling after OA credentials are recovered caused by the following actions:
A reset of OA to factory default Replacement of a non-redundant OA OA firmware downgrade
Show Configuration Checkpoint icon is displayed on VC Manager banner line if the checkpoint is being updated or not valid.
For additional information, see the HP Virtual Connect Enterprise Manager at the HP website (www.hp.com/go/vcem).

New features 8

Important notes and recommendations
When a c-Class enclosure is used with Virtual Connect v1.21, the following configuration restrictions and guidelines apply:
For v1.21, the VCM behavior for powered up servers, when restarting after a recovery of OA credentials has changed. In previous versions, the servers would enter a "Profile Pending" state and required a power cycle to recover. For v1.21, a new state, "profile recovered", is applied to servers that are powered on when VCM restarts after an OA credential recovery. When VCM detects its restart after a credential recovery, it rewrites the profile parameters for any server that is powered on, connects the server to the appropriate Ethernet networks and FC fabrics, and puts the server and profile in the new "profile recovered" state. The server and profile remain in the "profile recovered" state until the server is powered down or removed from the enclosure. This eliminates the power set requirement for a server to recover. 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. Virtual Connect reports failures for any VC-Enet or VC-FC module that is removed from the domain. Ensure that all Virtual Connect Ethernet and VC-FC modules in a VC domain are at the same firmware revision. To check the firmware revision level, select the "Firmware Update" tab on the "Domain Settings" page. The firmware revision level for each module in the domain is shown. To help ensure proper operation after firmware updates, clear the browser cache and reload the browser. Only connect HP 4Gb VC-FC Module uplinks to Fibre Channel switch ports that are NPIV-enabled. If using a Brocade FC switch, verify that NPIV is properly enabled by using the portshow command. If not properly enabled, you might need to downgrade the Brocade switch firmware, and then upgrade the firmware again for the enable to work properly. Always install a Virtual Connect Ethernet module in interconnect bay 1. For redundancy, HP recommends installing a second Virtual Connect Ethernet module in interconnect bay 2. For c7000 enclosure interconnect bays 3-8, install a Virtual Connect Ethernet module or HP 4Gb VCFC Module in the bay corresponding to the mezzanine signals. Verify that all system component firmware is up-to-date. A server blade is displayed as incompatible by Virtual Connect Manager if the server ROM is not at the minimum level required by Virtual Connect. Virtual Connect Manager is not able to verify firmware revisions for all components, so a server blade component can be incompatible even if the server blade is not listed as incompatible. 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. Do not use Virtual Connect and non-Virtual Connect modules in horizontally adjacent bays.

Virtual Connect Manager assigns or migrates MAC addresses or WWNs for server Ethernet and FC ports connected to HP Virtual Connect modules. Virtual Connect Manager also assigns MAC addresses and WWNs to server Ethernet and WWNs to FC ports that are not connected to an I/O module because Virtual Connect modules can be added later. Server Ethernet and FC ports connected to non-Virtual Connect modules retain the server factory default MACs addresses and WWNs. Verify that all iLOs and Virtual Connect modules have valid and unique IP addresses on the same subnet as the OA. Without IP addresses on all modules, Virtual Connect does not work properly. 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. The CX4 interface on the HP 1/10 Gb VC-Enet modules uses the same physical connector as Infiniband, but Infiniband cables are tuned differently and do not perform as well in CX4 applications. HP recommends purchasing CX4 cable assemblies that meet the IEEE CX4 specifications and support 10-Gigabit communication at distances from 3 m to 15 m (9.84 ft to 49.20 ft). These cables can be used as uplinks to external switches. HP 1/10Gb VC-Enet modules also support 10GBASE-CX4 stacking cables 0.5 m to 7 m (1.64 ft to 23.00 ft). When multiple cables of the same speed are connected to two VC-Enet modules, they are aggregated to provide enhanced throughput for the stacking link.
The Onboard Administrator must have an IP address on the same subnet as the Virtual Connect module before the administrator sets the Enclosure Bay IP Addressing (EBIPA) mode. Changing the EBIPA address for a module causes the module to be reset by the OA (resulting in an outage) when the change is applied. If multiple modules have their EBIPA address changed, all modules experience the outage at approximately the same time. The port monitoring network analyzer port should only be connected directly to an analyzer. Improper connection of the port or improper configuration of the port monitoring could result in network loops and cause a network outage. Port monitoring is disabled in a mixed firmware environment. If any module in the domain is running a version of firmware prior to v1.20a, port monitoring is automatically disabled. When the management network is fully saturated, access to the VC Manager and response times might be slower due to network congestion.

For additional information, see the Virtual Connect user guide on the HP website (http://www.hp.com/go/bladesystem/documentation).

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. 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 CLI set ldap command IpAddress option supports only an IP address. This command option does not support the DNS name of the directory server as stated in the Command Line help and CLI user guide. The VC Manager domain configuration database in v1.21 is not downward compatible with 1.1x versions, causing an issue when downgrading from v1.21 or in an environment where the primary and secondary VC Managers are at different firmware levels. For example, if a primary VC Manager is running v1.21 and a secondary VCM is running v1.16, the primary VC Manager check-points the domain configuration (in v1.21 format) to the secondary VC Manager. If a failover causes the secondary VC Manager to become the primary, it is unable to initialize because it cannot interpret the v1.21 configuration file. Avoid running different firmware versions on the primary and secondary modules in an enclosure.
Install only VC-Ethernet modules running v1.20a firmware or higher in HP BladeSystem c3000 enclosures. If all VC module firmware is below v1.20a, use the following steps to update the firmware: 1. Login to Virtual Connect Manager. 2. Import the VC Domain. 3. Install and activate firmware v1.20a or higher using the VC Manager Firmware Update. 4. Delete the VC Domain. This step is necessary for the identification of the c3000 enclosure.
When updating the VC Manager firmware, the prompt for file downloads to a local system might be blocked by the browser security setting. During an Onboard Administrator failover, Virtual Connect Manager can lose communication with the Onboard Administrator for as long as 15 minutes. During this time, Virtual Connect Manager is not able to make profile changes to server blades or perform some enclosure administration functions, such as powering server blades on and off. When operating in a redundant Onboard Administrator environment and the user requests a "Transition Standby to Active" to the standby Onboard Administrator, then communication between the Virtual Connect Manager and the active Onboard Administrator might be lost. To restore communication, reset the Virtual Connect Manager from the Tools pull-down menu. Replacing the OA in an enclosure containing only one OA causes the OA to leave VC mode. This mode change requires the VCM to re-establish credentials with the OA. During this process, the VC rewrites all server settings and sets the state of the servers to "profile recovered." There should not be

Known issues 11

any disruption to the servers, but the administrator should ensure all servers have the correct MAC addresses and WWNs. Powering off the server will clear the "profile recovered" state. If any servers are rebooted or power cycled while the credential recovery is occurring, the MAC addresses and WWNs may be returned to the factory default settings.
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). If a change is made in RBSU, that change is not reflected in Virtual Connect Manager. If PXE is set through RBSU, HP recommends using the "Use BIOS" setting. RDP "rip and replace" does not work properly when using VC-administered MAC addresses because RDP is tracking the server blades by MAC address rather than by the primary lookup key (which can be set to serial number, MAC address, UID, or Asset Tag). To work around this issue, manually redeploy the server blade. For VC-Enet modules, do not use the Get-Bulk feature with SNMPv2c MIB walk. The MIB walk operation halts prematurely before running through the entire MIB. When using SNMPv2c protocol for MIB walk, make sure that the Get-Bulk option is not enabled. When scripting CLI commands, only a single scripting client should perform remote management operations to a remote Virtual Connect Manager. If multiple scripting clients are used to perform a heavy load of CLI commands to a single Virtual Connect Manager, some management commands might fail, and in some cases, the primary module might need to be reset to properly recover. An unsupported state occurs when a VC Ethernet module is replaced physically with a non-VC Ethernet module without administrative removal of the module from the VC domain. During this state, if either the Help/About HP Virtual Connect Manager page or Firmware Management page of the VCM GUI is opened, the string, "Loading.," appears indefinitely instead of the firmware version number for each module in the VC domain.
Fibre Channel and SAN boot
If updating from Virtual Connect Manager v1.10 firmware, the VC-Enet module firmware must be updated before the VC-FC module firmware. Otherwise, the VC-FC firmware might not appear to be successfully updated. To properly boot from SAN with some versions of Linux and VMware ESX 3.0.1, change the QLogic HBA connection options to "point to point only" in the QLogic BIOS configuration utility. Virtual Connect Manager does not provide an interface to force 1-Gb speed on the VC-FC module uplink and downlink ports. However, the ports will auto-negotiate properly to 1 Gb. 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. When configuring Trap Destination IP addresses for the VC-FC modules, be sure that trap destinations are capable of supporting SNMPv2 type traps. The number of SNMP trap destination addresses is limited to one trap destination for VC-FC modules.

Known issues 12

The default for the SNMP community string for the VC-FC module is Public. Modification of this string is currently not allowed. When two Fibre Channel mezzanine cards are installed in slots 2 and 3 of a full-height server blade (BL480c, BL685c, or BL860c), the VC Manager only creates Fibre Channel connections and assigns WWNs to the ports associated with the Fibre Channel mezzanine card in slot 2.

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. 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. In most cases, a warning is provided, but in some cases it is not. 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 the Server Connections tab of the Ethernet Networks screen, the port status shows OK even if the server port is not linked.

Firmware update

If updating from Virtual Connect Manager v1.10 firmware, the VC-Enet module firmware must be updated before the VC-FC module firmware. Otherwise, the VC-FC firmware might not appear to be successfully updated. If the firmware update procedure indicates a failure to activate a module or appears to be stuck, it might be caused by a timeout and/or a stale web page. To refresh the screen and verify the actual update status, click the Firmware update link under Domain Settings in the left navigation pane of the VCM user interface. During the firmware update activation countdown, an Internet Explorer pop-up might be displayed stating "Failed to create processor object: The stylesheet does not contain a document element. The stylesheet may be empty, or it may not be a well-formed XML document." This pop-up can be dismissed without consequences. After a firmware update, clear the browser cache. If the browser cache is not cleared after a firmware update, VC Manager might not function properly. When using the "Upload from local file system" option on the GUI firmware update page, if the browser is closed, aborts, or loses network contact with the primary VC manager before the upload

Known issues 13

completes, a subsequent upload attempt might fail with the GUI reporting an "unknown error" or format error. Using the "Upload from web URL" option exclusively prevents this error. If the "Upload from local file system" must be used, be sure to keep the browser open until the upload completes, and avoid attempting firmware updates when the management network is unreliable. To recover from this error, force a failover of the primary VC Manager or use the Onboard Administrator Virtual Buttons to reset the primary VC Manager.
While executing individual (not automated) firmware updates, the Update button might appear after clicking the Activate button for a VC-Enet module.
Ignore the Update button if it appears for less than 3 minutes. If the Update button appears for more than 3 minutes, then the firmware update failed and should be re-attempted. If the Update button is clicked in this state, it reports an error in installation. This error can be ignored.
During automated firmware update, if the primary VC module is running the same or a higher version than the selected firmware update package, and the "Allow firmware downgrades and/or re-update" check-box is not selected, then only modules with lower firmware than the selected package are updated. Upon completion of any updates, the firmware update page might display inaccurate version numbers. To correct the display, select the "Firmware management" link in the left navigation pane.

Known issues 14

Resolved issues
The following issues that existed in Virtual Connect v1.20a have been resolved in Virtual Connect v1.21:
The authentication of a user by an SSH key which has been uploaded through the GUI has been resolved. The user is no longer required to enter a password when a valid key exist. LDAP server certificate validation extends beyond the first certificate in a chain. A stale checkpoint issue resulting in out-of-date configuration is resolved. VC Manager recovers from loss of communication when replacing a single OA module, or resetting the OA to factory default. VC Manager now correctly detects and reports module status for OA Ekey mismatch and thermal state events. Incorrect reporting of VC-FC fabric state after a firmware upgrade has been corrected. Virtual Connect v1.21 automated firmware now correctly updates all VC-FC modules. Loss of network connectivity after a firmware upgrade when using native VLANs has been resolved. Wording has been corrected for the Automatic FW update window when the "downgrade or reupdate" checkbox is not selected. It now correctly states that only modules with firmware equivalent to or newer will NOT be affected. The SNMP agent on VC-Enet module now validates the read community string.

Resolved issues 15