|
Try applying some “glue” to facilitate less painful management of your blade servers.
Blade glue is the standardization of silicon, firmware, drivers, providers, utilities and applications that provide blade managers with always-available solutions. Unlike proprietary approaches, blade glue provides standard management capabilities that are common across multiple platforms, making management of blade systems less painful. There are three layers to blade glue:
Some of the key technologies and standards that provide these features include: Intelligent platform management interface (IPMI). This specification represents a proven approach to hardware health monitoring and management. IPMI is typically pre-integrated into a blade and chassis by the vendor. Specialized IPMI software running on dedicated controllers allows IPMI to act as a completely separate subsystem immune to the condition of a blade. This independence allows administrators to utilize IPMI features any time via IPMI-enabled remote applications. Monitoring the health of components, such as temperature, power and inventory information, can be done even during times where the blade operating system may have hung or when the blade is inactive. IPMI also features user-defined thresholds for specific events. Systems-management architecture for server hardware (SMASH). This is a Distributed Management Task Force initiative that is delivering, among other things, a standard command-line protocol (CLP) to provide a consistent way to manage servers from multiple vendors. The first version was expected to be available for public review mid-2005. The goal of CLP is to offer a standard way for administrators to send commands and receive responses back from managed servers. Think of SMASH as the primary interface, out of the box, accessing IPMI features in the box. This command consistency across different vendors’ servers or blades is critical, not just for reducing the learning curve, but especially when considering investments in scripts that many customers have made. CLP typically will be supported on the blade in firmware and elsewhere in the chassis via management modules–offering multiple access and control points. Keyboard, video, mouse. By redirecting the KVM from multiple servers to a single console, considerable cost savings in space and equipment are achieved. As a hardware approach, it does not require any additional software on the blade server, and is typically accessible over the LAN from remote locations. Using IPMI features, an enterprise manager can learn that the temperature of a blade has exceeded a threshold, making him aware of a potential failure. With SMASH then serving as a common command interface and a remote KVM appliance offering cost-effective centralized, graphical access, the manager can remotely and gracefully power down the blade and activate a backup to keep services running while scheduling the blade fan for replacement. For more information from Avocent: Steve Rokov is director of technical marketing, Avocent Manageability Solutions Group. He is also the secretary of the Blade Systems Alliance, an industry consortium seeking to advance the adoption of blade-based computing systems. Send comments for publication to guest@comnews.com.
|
||