IBM® recently introduced software-based iSCSI Boot on Blades that enables a Blade with no local disk to boot over the network using only the standard, built-in network connections. The configuration process for iSCSI Boot includes a number of interdependent steps spanning BladeCenter®, Blades, N-Series storage, and optionally DHCP.

Because the SAN configuration process involves numerous steps and requires the coordination of arcane parameters between the numerous separate entities, automation of this process is beneficial.

IBM iSCSI Boot Commander assists in configuring and managing an iSCSI Boot SAN environment. This technology provides a unifying management console that automates and simplifies SAN configuration and operating system deployment.

This utility walks the user through the complexities of configuring a Blade and N-Series storage device by automatically contacting the network devices and providing contextual data and an appropriate set of parameters, resulting in increased accuracy and speed of operation.

How does it work?

IBM iSCSI Boot Commander is a Windows®-based application that connects to an IBM BladeCenter and allows the administrator to select a Blade for configuration. IBM iSCSI Boot Commander then connects to an N-Series storage device and walks the administrator through the configuration of storage and optional deployment of an operating system. Specifically, IBM iSCSI Boot Commander walks the administrator through the following:

• Filer (N-Series) discovery and selection
• BladeCenter discovery and selection
• Blade Selection
• SAN connection selection
• Filer volume management
• LUN creation and optional deployment
• CHAP security
• NVRAM and optional DHCP configuration
• Blade power-up.

All these steps are easily accessible: A few mouse clicks direct the operation.

Richard Bealkowski, Ph.D., is a Senior Technical Staff Member in IBM Systems and Technology Group.