- Market surges, Gates predicts 9% unemployment
- Obama the first presidential hopeful to advertise in games
- Microsoft reveals critical holes in Active Directory
- BlackBerry Storm vs. the iPhone
- How will economy affect network equipment vendors?
Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:Application Performance Solutions | App Performance | Networking Solution | SafeGuard Enterprise Solution Center | SOA | Test your Web Filter | Value of WDS
High-performing, reliable systems used to have one drawback: They were usually built with proprietary components that offered little or no interoperability. Server management relied on proprietary tools that made it difficult for IT to manage multi-vendor server racks and blade servers. A standard was needed to tie things together, and it arrived in the form of the Intelligent Platform Management Interface.
Server vendors developed the IPMI standard for cross-platform system management starting in 1998. The standard defines hardware management interfaces that let IT managers receive status alerts, send instructions to servers, and access various console screens to diagnose and recover from faults over a network. More than 160 vendors adopted IPMI Version 1.5.
The latest revision, IPMI Version 2.0, was announced in February and is backward-compatible. The most notable enhancements over Version 1.5 are stronger security and standardized console access.
At the heart of IPMI is a dedicated chip/controller - sometimes called a service processor or baseboard management controller (BMC), which typically sits on the system motherboard or blade. The IPMI firmware is combined with the BMC to create the basis for a stand-alone platform management subsystem.
This subsystem works regardless of the type or state of processors, BIOS or operating system, allowing for manageability, monitoring and recovery even when the rest of the system is unavailable.
All IPMI functions are accomplished by sending commands to the BMC, using instructions identified in the specification. The BMC receives and logs event messages in the system event log, and maintains a sensor data record that describes the sensors in a system.
A separate area, for the field-replaceable unit, stores information about a system's hardware components that also can be retrieved - useful for service and support as well as asset systems.
IPMI 2.0's new serial over LAN (SOL) feature is helpful when remote access to a system is required. SOL redirects the local serial interface over an IPMI session, allowing remote access to Emergency Management Services, the Special Administration Console for Windows, or the Linux serial console. The BMC does this by redirecting information destined for the serial port over the LAN - offering a standard way to remotely view the boot, operating system loader or emergency management consoles, irrespective of vendor, to diagnose and repair problems.
Partner Content
NetScout is one of the world's premier providers of integrated network and application performance solutions.
www.netscout.com
Know First
Get Proactive — Move from Troubleshooting to Monitoring to Management with nGenius K2's Service Dashboard & Intelligent Early Warning Alarms
Watch the Video
Know Where
Get Rapid Performance Problem Isolation with nGenius Performance Manager and Diagnose Problems up to 70% Faster!
Learn More
Know Why
Get the Details to Validate and Solve your Toughest Performance Issues with nGenius InfiniStream and Sniffer Intelligence Modules
Read the Whitepaper
Comments (1)
RE: IPMI V2.0 eases blade managementBy Adrian White on December 12, 2007, 10:34 amHave you ever asked why IPMI is free! Dell and Compaq back in 1998 had their own remote management cards and were not suing each other over the IP and I always...
Reply | Read entire comment
View all comments