Installing an HBA
Setting up any HBA requires answering various questions: What operating systems will it work with? What settings and configuration files need tweaking prior to, during and after installation? How does the HBA discover new LUNs on the SAN?
Probably the biggest initial task facing many system administrators centers on the installation and configuration of a new HBA in a server. Loading the correct driver, verifying the firmware, tweaking the configuration files, ensuring it is compatible with your SAN and discovering the LUNs for the first time can take hours--if not days--for new or experienced SAN administrators.
HBA vendors now ship HBAs that address many of the issues surrounding the initial install and configuration by eliminating or automating these tasks. Most vendors--including Atto Technology, Emulex, QLogic, and LSI Logic--now offer HBAs for Windows systems that are plug-and-play and require little or no intervention on the part of the system administrator to install and configure.
Amherst, NY-based Atto Technology's product manager, Pete Donnelly, lists interoperability of Atto's HBAs with Microsoft Windows as a top priority. Atto is currently working with Microsoft to ensure its HBAs are automatically recognized by Windows after being installed.
For Unix environments, installations are far from being hassle free, but there's encouraging work in this area. According to Charles Kraus, HBA business unit director
Sun Microsystems appears to be heading down the same path as HP and IBM. While all of the major HBA vendors currently provide drivers for Sun Solaris, Sun has included the leadville driver as part of its current SAN Foundation software. This driver offers full fabric support, along with failover and management capabilities, and replaces the one provided by the HBA vendors, though this driver currently only works with the newest HBAs provided by QLogic. The upside of this approach, according to Christopher Poelker, a storage architect with Hitachi Data Systems (HDS), is that the leadville driver removes the need to edit the sd.conf file because it runs at the kernel level and uses a different configuration file--sdd.conf--which needs no editing.
Managing an HBA
Once an HBA is installed, the focus changes to managing it. Here's where new struggles arise. In some large IT departments when upgrades occur on the SAN, administrators can find themselves at their wit's end trying to figure out which server has what HBA with what firmware and driver level.
Again, new features and tools from vendors such as Emulex, JNI and QLogic enable administrators to better control this part of their environment.
Costa Mesa, CA-based Emulex offers a central management console called HBAnyware that performs three critical management tasks that work in conjunction with their native driver kit.
HBAnyware grants administrators the ability to do local and remote discovery of Emulex HBAs. It also contains the ability to do local and remote management and real-time installation of firmware anywhere in a Fibre Channel (FC) SAN. Finally, it allows the administrator to gather FC HBA port status, attributes and statistics.
While having software like this becomes a powerful tool for administrators, knowing how to use it becomes just as critical. For instance, HBAnyware grants administrators the ability to upgrade Emulex HBA firmwares and drivers remotely. What the administrator needs to know is that upgrading Emulex's firmware can be done nondisruptively and won't require a reboot; however, changing its driver can be disruptive and may require a server reboot. So, administrators need to practice a think-first, act-second mentality when performing tasks like this.
The rest of the HBA vendors primarily provide tools that are locally installed and managed on each server. Atto has its ExpressPCI Configuration Tool for driver and firmware upgrades for its HBAs. Atto Technology's Donnelly says that while its firmware and driver updates may be done on the fly, he doesn't recommend that approach--especially for novice users. He sees the management of these functions being done locally for the time being, though when CIM becomes universally available, there will be more opportunities to perform these tasks remotely.
JNI and LSI Logic also provide similar utilities that simplify HBA installation and configuration for their specific HBA cards, though the other major vendors lack the central management control consoles offered by Emulex. LSI Logic's Charles Kraus says that interoperability with third-party SAN management software tools such as EMC's ControlCenter is one of LSI Logic's priorities for 2003. LSI Logic also plans to have a tool similar to Emulex's HBAnyware released by the end of 2003 to centrally manage LSI Logic HBAs.
QLogic provides a management tool similar to HBAnyware called SANblade Manager, which simplifies the configuration and setup of QLogic HBAs. This tool works in conjunction with its SANblade Control FX utility, which is controlled by the SANblade Manager software. The SANblade Control FX utility enables a faster HBA installation and configuration through a wizard-like interface, includes diagnostic tools that report on the firmware and driver levels and also includes a display that shows attached devices and LUN properties.