A significant design improvement in a number of 4Gb/sec FC HBAs is the use of the PCI Express I/O architecture. Earlier PCI and PCI-X architectures required FC HBAs to arbitrate for control of a shared bus architecture on servers. The PCI Express architecture eliminates the requirement for arbitration and introduces a switch-like architecture that allows the HBA to act as a high-speed interconnect between the server and the FC SAN. Atto Technology Inc.'s Celerity FC-44ES, Emulex's LPe11000, Hewlett-Packard (HP) Co.'s FC2142SR, LSI Logic Corp.'s LSI7104EP and QLogic's SANblade QLE2460 all have the PCI Express architecture, but these HBAs can only be used in newer servers that support PCI Express.
The performance of onboard HBA ASICs has been improved to keep up with the new switching technologies. Emulex reflects what most FC HBAs vendors are doing: Its dual-port LPe11002 Zephyr controller has two ARM11 processors that use less memory but deliver higher performance than earlier generations of processors; a chip is dedicated to each channel. Each chip also has a separate flash memory. That means users can have separate flash memory loads and even run different versions of the flash memory if called for by a specific application configuration.
Issues to consider
There are presently three major roadblocks to using an NPIV-capable FC HBA: NPIV is only available on the latest FC HBAs and vendors don't provide a way to upgrade previous versions of their HBAs. Secondly, NPIV requires the FC switch to recognize and manage multiple, unique WWNs logging into each FC port. Currently, operating systems on FC directors allow only one unique WWN to log into each port. This means that even if the HBA supports NPIV, attempts by the HBA to log into the fabric multiple times will fail.
To allow multiple logins, users must update their FC director's operating system to the latest version; this will permit multiple WWN logins on a port and route the traffic accordingly. For instance, Brocade Communications Systems Inc.'s SilkWorm products require Fabric OS Version 5.1.0, while Cisco Systems Inc.'s MDS directors require the firm's SAN-OS Software Release 3.0 (2). In addition, Cisco doesn't provide NPIV as a standard feature of its SAN-OS; users must purchase and license the NPIV feature separately.
The third and most significant roadblock is that no server OS natively recognizes and interacts with the NPIV API. FC HBA vendors estimate that full integration between the various server OSes and NPIV will occur in approximately two years. Until that happens, admins need to manually assign the virtual WWN in the OS to the FC HBA when moving applications to new server hardware or when cloning virtual servers. Although creating unique NPIVs is a matter of procedure when cloning virtual servers, moving applications to different server hardware will require application outages (see "Alternatives to NPIV," at right).
HBA, show yourself
Identifying which HBA is used by what application is key to avoiding application outages and troubleshooting app problems. However, with servers supporting multiple HBAs and applications rolling virtually from one server to another, identifying which HBA is in use, when it's in use and how it's used becomes problematic. HBA vendors are beginning to introduce features like beaconing, link-speed indicators and express bus modules to assist administrators in identifying, troubleshooting and replacing HBAs.
Beaconing allows administrators to send a signal from the FC HBA's management software to a specific HBA that causes an indicator light on the HBA to blink repeatedly to identify its location in the server. But before administrators can implement beaconing, they need to determine how the management software communicates with the FC HBA. FC HBAs from Emulex and QLogic can communicate in-band (over the FC SAN) or out-of-band (over the Ethernet network), and each approach has its drawbacks.
For beaconing to work in-band, the FC HBA's management server must have an FC HBA port attached to each FC SAN in which it will manage client FC HBAs. To communicate with the FC HBA over an FC SAN, administrators need to create a zone that includes the HBA WWNs of both the management and client servers. However, putting the management server's HBAs in the same zone as the client server may slow boot times for some server operating systems, such as Sun Solaris, as it communicates and identifies the role of the management server's HBA WWN in the zone.
Out-of-band management is equally problematic. Administrators need to install agents on each client server so that the management server can communicate with them. If the client servers are on different subnets or on restricted internal networks, admins need to create the appropriate routes and put the right firewall policies in place to allow the management server to communicate with the client servers.
Another problem admins can encounter with FC HBAs is establishing the exact speed at which each port on a multiport FC HBA connects to the FC SAN. To address this problem, FC HBA vendors are providing separate link-speed indicator lights for each possible speed at which each port of their FC HBAs can connect to the SAN. For instance, QLogic's quad-port SANblade QLE2464 provides 12 different link-speed indicator lights (three for each port on the HBA) to let admins determine the connection speed of each port on the HBA. (See "Quad-port Fibre Channel host bus adapters" on Storage's Web site.)
HBA vendors also need to minimize or eliminate the need to take a server offline when a faulty HBA needs to be replaced. QLogic's SANblade QEM2462 takes advantage of the PCIe ExpressModule specification that lets admins remove and insert HBAs in servers without any tools. However, the SAN zoning and LUN masking on arrays must still be updated with the new WWN of the replacement HBA unless they use NPIV.
As data centers become increasingly virtual, FC HBA vendors must make the management and trouble-shooting of their HBAs virtual. While beaconing and link-speed indicators are small steps in that direction, NPIV is a more important step to keep FC HBAs relevant in the emerging virtual data center. Although NPIV provides some short-term benefits, such as allowing admins to create and use virtual WWNs instead of static ones, the big benefits of NPIV won't come until it's fully integrated with server and network OSes in 2008.