What is a Service Processor?

A service processor is a separate, dedicated internal processor located on the motherboard of a server, a PCI card, or on the chassis of a blade server or telecommunications platform. It operates independently from the server’s CPU and operating system (OS), even if the CPU or OS is locked up or otherwise inaccessible.



Service processors monitor a server’s on-board instrumentation (temperature sensors, CPU status, fan speed, voltages), provide remote reset or power-cycle capabilities, enable remote access to basic input/output system (BIOS) configuration or OS console information, and, in some cases, provide keyboard and mouse control.

Depending on the manufacturer, service processors may also provide console redirection capabilities to view server processes or to configure server parameters, system information on components installed, including ports used and devices connected, and event logs, notifications and alarms.

Some leading service processor technologies include:

• Intelligent Platform Management Interface (IPMI)
• HP Integrated Lights Out (iLO)
• IBM® Remote Supervisor Adapter (RSA)
• Dell Remote Assistant Card (DRAC)
• Sun Advanced Lights Out Management (ALOM)
• Sun Integrated Lights Out Management (ILOM)

Service processors are accessible through either a dedicated Ethernet interface (out-of-band) or a shared data Ethernet interface (sideband). See below.



Note that with sideband access, although there is only one Ethernet jack in use at the back of the server, there are still two Ethernet hardware sets inside the server, which means those interfaces can have separate IP addresses.

Features

The feature set of service processors varies depending on the service processor type.

Nevertheless, there are some features common to all service processors. All service processors provide remote power control (on/off/cycle/status) and enable remote console access via Serial over LAN (SoL). Depending on the service processor type, however, they can also provide more advanced functionality, such as server health monitoring (fan speed and status, temperature, voltages), graceful (OS-level) shutdown capabilities, remote keyboard, video and mouse (KVM) and Virtual Media capabilities. These features are discussed in more detail below.

• Remote power control – Servers can be remotely powered off, on, or cycled through service processors. This is one of the most useful features of service processors. Remote power control is used to restore servers that are locked up, to power down overheated servers, or any other function that requires low-level interaction with the server.
  
  
• Graceful shutdown support – Certain service processors support a remote power control command that actually sends a signal to the server OS to shut down gracefully before actually power cycling or turning off the server. This prevents the possible effects of a “brute force” power cycle or shutdown, such as data corruption in the server hard drives and other undesirable outcomes.
  
  
• Remote SoL console access – The server console can be accessed through the Ethernet interface of its service processor by using a standard telnet or SSH client in the same way it would be available through a regular serial port. If the server supports BIOS redirection to the serial port (which is usually the case with servers equipped with service processors), a user can have full access to the server console from the time it is booted up, through the BIOS and all the way up to the OS login prompt. This is very useful for remote troubleshooting.
  
  
• Health monitoring – Service processors communicate with the appropriate sensor hardware in the server (e.g., fan speed monitors, voltage meters and temperature readers) to access and monitor vital server statistics so that server problems can be detected quickly. The health information can be stored on the server, sent to a remote storage device or communicated directly to the user workstation.
  
  
• Remote ID LED control – Service processors allow the administrator to turn on or off the server’s ID LED, which can be used to identify a specific server in a rack of multiple similar servers. This is especially useful when maintenance is needed on a server and the local technician who has physical access to the server does not have access to server information. In that case, the administrator can turn on the ID LED to visually designate for the local technician which server needs maintenance.
  
  
• Local and server-based authentication – In order to access the service processor features, a user needs to log in to it first. The user database is usually stored locally in the service processor. Some service processors can also communicate with central authentication server mechanisms, such as LDAP and Active Directory.
  
  
• Data encryption – The communication between the service processor and the user may be encrypted if the service processor supports communication protocols that allow for encryption, such as Secure Shell (SSH) or Secure Socket Layer (SSL). Most recent service processors support some level of data encryption.
  
  
• System event log (SEL) – Service processors can store information about events related to the server hardware, such as chassis opening and closing, hard drive functional alarms, RAM test errors and so on. Those event logs can then be verified by the server administrators directly, or be used as the source for automated alerts.
  
  
• Platform Event Traps (PET) – Service processors can be programmed with information about critical thresholds for server environmental variables, such as the maximum operating temperature, minimum CPU fan speed, etc. Based on those thresholds, it can then send out alerts (traps) to a management system, usually in SNMP format, so that the server administrator can take immediate action to remediate the issue at hand.
  
  
• Data logging – Some service processors provide the ability to log the data flowing through the server’s serial console, regardless of whether there is a user directly connected to that session at that time. This enables administrators to review the history of events that happened to the server before a certain issue occurred, providing a useful audit trail for change tracking and troubleshooting.
  
  
• Virtual KVM – This is similar to the SoL feature, but instead of exposing the server’s text-based serial console to the user, Virtual KVM provides access to the server’s GUI. This is especially important for operating systems that rely heavily on their GUIs, such as Windows.
  
  
• Virtual Media – Certain service processors allow the server to access storage media such as CD-ROMs, floppy disks and even DVD-ROMs anywhere on the network - just as if they were directly attached to that server. This allows users to quickly move and copy data between their user workstations to the server (and vice versa), which is useful for emergency OS and application patch installations, as well as diagnostic testing and BIOS upgrades. Virtual Media along with Virtual KVM enable a true lights-out management experience using the interfaces and tools that users are already accustomed to in their daily routine.

Benefits

Most of the features provided by service processors are not new, as many of these features are available in some shape or form through other remote management solutions, such as console servers, KVM switches, IPDUs, etc. The obvious question, therefore, is: what new benefits do service processors provide?

At the same time, service processors are widely deployed in these environments, since the vast majority of servers purchased in the past three years includes some form of embedded service processor. According to estimates from leading server manufacturers Dell, HP, IBM and Sun, approximately 9 million servers with service processors were shipped in 2005. It has been estimated that this figure will grow to 13 million servers in 2006. It should be the perfect marriage between demand and supply, especially considering that the investment in the service processors needed for remote server management has already been made.

Challenges

However, service processor adoption has been slow. In spite of all the benefits service processors provide, IT managers are still leaving them unplugged or disabled, not taking advantage of an asset that can provide the exact capabilities they are looking for. The same leading server manufacturers estimate that by the end of 2005, only 1.4 million of the available service processors in the market were being utilized, with an estimated total of 2.2 million used by the end of 2006.

At the same time, service processors are widely deployed in these environments, since the vast majority of servers purchased in the past three years include some form of embedded service processor. According to estimates from leading server manufacturers Dell, HP, IBM and Sun, approximately 9 million servers with service processors were being used in the market by the end of 2005. It should be the perfect marriage between demand and supply, amplified by the fact that the service processors needed for remote server management have already been paid for.

However, service processor use and adoption have been discouraging, to say the least. In spite of all the benefits service processors provide, IT managers are still leaving those service processor Ethernet ports unplugged or disabled, not taking advantage of an asset that can provide the exact capabilities they are looking for. The same leading server manufacturers estimate that by the end of 2005, only 1.4 million of the service processors available in the market were being utilized.

Mainstream adoption of service processors has been hampered by a number of factors. Server vendors are reluctant to adhere to a standard service processor interface such as IPMI, because of its perceived limitations. In fact, most server vendors include IPMI in their platforms, but hide it behind proprietary service processor firmware extensions and bundled management solutions. These vendor-specific features only support their own servers and fail to work with products from other vendors.

To add to that issue, many enterprises are completely unaware of the potential power of service processors; and even when they are aware, specific concerns about how to integrate service processors into their existing management framework prevent their adoption. Some are simply encumbered by compatibility concerns, cost issues and the lack of centralized management, while others are hampered by security and functionality concerns.

Deployment Challenges

• Service processors require an extra Ethernet connection and IP address per server, which translates into extra costs. These costs do not only arise from the need to have an additional Ethernet switch port available, but also from maintenance of that connection in accordance to the company’s policies. This issue only affects service processors that require a dedicated Ethernet port.
• Lack of proper authentication, authorization and accounting (AAA) security support built in to service processors, which prevents integration and compliance with existing security mechanisms and policies. The exception to this rule is HP’s iLO.
• Specifically for sideband deployments, IPMI comes disabled in the server, due to security concerns. In order to enable IPMI in that server, the IT manager would need to either access the server BIOS or PXE boot the server with a specific OS image that contains the proper BIOS configuration commands. This is a challenging task, especially in large environments with many servers already deployed.
• Lack of a discovery mechanism for service processor capabilities already deployed, which prevents IT managers from taking immediate advantage of service processors already present and available in their IT environment.
• Consolidation tools for multiple servers are either vendor-specific or do not offer enough features, which causes interoperability and scalability issues in service processor adoption.
• Integration of service processor management into the existing management framework is hard, due to the lack of standardization and the limitations of vendor-specific tools. Also service processors do not integrate with existing remote server management tools such as console servers and KVM switches.

Types of Processors

Type	Meaning	Vendor	Versions
IPMI	Intelligent Platform Management Interface	Multivendor	1.5, 2.0
iLO	Intergrated Lights-Out	HP	1x ,2
RILO	Remote Insight Lights-Out	HP (Compaq)
DRAC	Dell Remote Access Controller	Dell	III, IV, V
RSA	Remote Server Admin	IBM	I, II
RSC	Remote System Controller	SUN
ALOM	Advanced Lights-Out Management	SUN
ILOM	Integrated Lights-Out Management	SUN

IPMI
Originally proposed in 1998, IPMI is an open standard service processor technology, originally driven by Intel (its main proponent), Dell, HP and NEC. Since then, IPMI has been adopted by more than 150 other companies, including IBM, Sun and every major server platform vendor. The goal of IPMI is to provide a single service processor protocol for servers manufactured by different vendors.

The first version of IPMI supported serial interfaces only and required the use of console servers. A subsequent version (1.5) provided IPMI over a LAN interface. Currently, IPMI version 2.0 provides serial console redirection over LAN, improved CLI, encryption capabilities and additional support for modular systems like server blades. These new features enhance management security by supporting well-known and trusted security mechanisms, making IPMI easier to implement within current enterprise security frameworks.

IPMI features include:

• Remote power control, including graceful shutdown support
• Serial over LAN (SoL) console access
• Server health monitoring (fans, temperature, voltages, etc.)
• System event log (SEL) functionality
• Platform Event Traps (PET)
• IPMI’s user interface is a text-based CLI, although there are software programs available to present IPMI information through a GUI.

HP iLO

Integrated Lights Out or iLO is HP’s proprietary service processor technology. iLO is a dedicated application-specific integrated circuit (ASIC) on the motherboard of the server that is accessible through a dedicated Ethernet port on the server. Like other service processors, iLO remains active and available, even when the CPU or OS is halted or when the server’s power is turned off.

iLO is available in two levels: basic and advanced. Since 2003, almost every HP server – including blades – ships with basic iLO included as a standard feature. Basic iLO provides the following features:

• SoL console access (text mode only)
• Remote power control
• Remote ID LED control
• Local user accounts
• Security (SSL, SSH2, user access logging, integrated managment log, iLO event log)
• Remote firmware update
• Alert administration (SNMP traps)

Although basic iLO provides a very comprehensive feature set, it can be upgraded to advanced iLO through the purchase and installation of an iLO Advanced Pack, which enables additional functionality in the service processor, such as:

• Virtual KVM
• Virtual Media (floppy, CD)
• Lightweight Directory Access Protocol (LDAP) and Active Directory integration
• Multifactor (smartcard) authentication
• Terminal Services (RDP) integration

Besides these functionalities, there are other features provided by iLO to make its deployment easier. iLO supports both static IP address configuration and dynamic IP address assignment via Dynamic Host Configuration Protocol (DHCP). Unlike IPMI where the only user interface available is text-based, iLO has two user interfaces – a Web-based interface and a CLI available through telnet or SSH sessions. By accessing this Web interface through a standard Web browser, the user is able to perform any service processor function available at that iLO level. Later versions of iLO (v1.60 or greater) in more recent servers (G4 or later, except for blades) also allow for the user to select the Ethernet connection it uses to be either dedicated (default) or shared with the main server Ethernet interface. The latter allows iLO to be deployed without the need for an additional Ethernet cable and switch port. In those cases, iLO also supports VLANs for logical segregation of the management network traffic.

More recently, HP has released the next generation of iLO, called iLO2, which comes embedded in the most recent models of HP servers. iLO2 also has basic and advanced levels, and the advantages of iLO2 when compared with iLO are as follows:

Basic iLO2:

• Virtual KVM text console (allows access to BIOS and POST messages)
• Power consumption information
• Embedded system health (fans, temperature, power supply, etc.)

Advanced iLO2:

• Java-free virtual KVM
• Virtual Media (DVD-ROM)
• Embedded system health monitoring (fans, temperature, power supply, etc.)
• iLO2 is also compatible with IPMI 2.0, for easier integration with existing IPMI-based environments.

IBM RSA

IBM’s Remote Supervisor Adapter II or RSA II is a service processor that exists on a PCI card that manages the Baseboard Management Controller (BMC) located on the motherboard of a server. A version of the RSA II, called SlimLine, is an internal card that includes the BMC and uses a dedicated Ethernet connector on the server for communication. The IBM BladeCenter’s management module uses a modified version of the RSA firmware with an integrated KVM switch to provide access to individual server blades.

RSA II provides many remote server management options, including:

• Alert and notification management
• Event logging
• Storage of the last screen before a server failure
• Remote power control
• Server health monitoring

All these features are available from the RSA II command line interface. Additionally, RSA II offers a Web-based interface that provides access to all these features plus Virtual Media and Virtual KVM support.

Dell DRAC

Dell Remote Assistant Cards or DRAC is Dell’s proprietary service processor technology. DRAC provides administrators with access to servers and control of the server hardware and operating system from client workstations through a Web browser. A telnet connection to DRAC provides access to only a few of the DRAC features when compared to what is available through DRAC’s Web user interface. However, it does enable text-based console access. In addition, DRAC logs the probable causes of system crashes and saves current error displays. By communicating with the system’s embedded system management hardware, DRAC can report warnings or errors related to voltages, temperatures and fan speeds.

Currently there are five versions of DRAC:

• DRAC II – The initial version of DRAC, provided as a full-length PCI card that requires Dell OpenManage IT Assistant software to be installed on the client management workstation. DRAC II can be used with Dell PowerEdge™ EMS2-based systems (i.e., x3xx, x4xx, x5xx servers).
• DRAC III – A half-length PCI card that provides enhancements in Virtual KVM, Virtual Media, and allows access for up to 16 users per card. DRAC III can be used with Dell PowerEdge ESM3-based systems (i.e., 1650, 4600, 6600 and 6650 servers).
• DRAC 4 – Available as either a daughter card (DRAC 4/I) or a half-length PCI card (DRAC 4/P) depending on the system, DRAC 4 can be configured to send e-mail alerts for warnings or errors related to voltages, temperatures and fan speeds. It can also log event data and the most recent crash screen (for systems running the Windows OS only) to help diagnose the probable cause of a system crash. DRAC 4 can be used with the 8th generation Dell PowerEdge servers (i.e., 800, 1800, 1850, 2800, 2850, 6800 and 6850 servers).
• DRAC 5 – The most recent release of DRAC, it contains major enhancements in the feature set, making DRAC 5 comparable with the most advanced service processors in the market. DRAC 5 can be used with the 9th generation Dell PowerEdge servers (i.e., 1900, 1950, 2900 and 2950 servers).
• DRAC/MC – This version of DRAC, used in Dell’s PowerEdge 1855/1955 blade systems, incorporates DRAC functionality along with add-on features specific to the blade environment.

DRAC includes software modules that provide a set of OS-specific services. These services communicate with the DRAC hardware to allow in-band configuration as well as console redirection to the out-of-band connection.

Sun ALOM

Advanced Lights Out Management or ALOM is one of Sun’s most recent service processor technologies.

Sun was one of the first vendors to have service processors in their servers, which they called System Service Processors (SSPs). SSPs were originally accessible only through the server’s serial port, yet provided most of the functionality of more modern service processors, such as remote power control, serial console access and low-level system debugging capabilities.

Throughout its history, Sun released other versions of service processors that were accessible through both the server’s serial port and through a dedicated Ethernet port, such as Remote System Control (RSC) and Lights Out Management (LOM and LOMlite). Going forward, ALOM is the service processor technology of choice for Sun’s Volume System Products (VSP) servers and Netra servers, replacing RSC and LOM.

Following Sun’s SSP tradition, ALOM is accessible through both the server’s serial port and a dedicated Ethernet port on the server.

The servers that currently support ALOM as of its latest version (v1.6) and that have ALOM pre-installed as a standard component are as follows:

• Sun Fire V125
• Sun Fire V210
• Sun Fire V215
• Sun Fire V240
• Sun Fire V245
• Sun Fire V250
• Sun Fire V440
• Sun Fire V445
• Sun Netra 210
• Sun Netra 240
• Sun Netra 440

New servers in the VSP and Netra families are also expected to have ALOM installed.

ALOM combines the features of RSC and LOM and adds several new features as well. These features include:
SoL console access

• Data logging for the SoL sessions
• Remote power control
• Remote ID LED control
• Hardware environmental monitoring (disks, fans, power, temp, FRU info, etc.)
• System event logs
• Event management and notification through email and syslog
• OS self watchdog with automatic restart capability
• SSH support for secure access

ALOM’s user interface is entirely command line based. It does not provide a built-in GUI or access to the server’s GUI.

Sun ILOM

Integrated Lights Out Management or ILOM is Sun’s latest addition to its portfolio of service processor technologies. ILOM is available on the Sun Fire X4x00 x64 servers (X4100, X4200, X4500 and X4600).

ILOM combines the functionality of ALOM with the following features:

• Virtual KVM
• Virtual Media (floppy, CD)
• LDAP integration

Besides the text-based CLI, ILOM also has a built-in Web-based interface for the user, the WebGUI. The WebGUI is the only interface that allows access to the Virtual KVM and Virtual Media features of ILOM.

Furthermore, ILOM also supports IPMI 2.0 and SNMP versions 1, 2c and 3. With so many supported interfaces and management protocols, ILOM can be easily integrated into most IT management environments, and represents the ultimate evolution in service processor functionality delivered by Sun.

Solutions

Avocent offers industry-first server management solutions that will help IT organizations leverage the service processor technologies already present in their servers, enabling reduced operational costs and faster troubleshooting and problem resolution through proactive monitoring and maintenance of server health. For companies that need to achieve optimum service levels with fewer staff resources, Avocent’s server management solutions are the best way to fully capitalize on the service processor technologies present in today’s servers.

The MergePoint™ 5200 service processor manager enables IT professionals to perform secure, remote server management from any location using IPMI (versions 1.5 and 2.0), iLO and DRAC. The MergePoint 5200 appliance provides secure SoL, console access, power control and server hardware monitoring, along with IPMI provisioning and service processor auto discovery. Click for more		The MergePoint 5224/5240 service processor managers simplify out-of-band management of servers with service processor technologies by consolidating IP connections, user access and server health information. With multiple Ethernet ports, the MergePoint 5224/5240 appliances connect point-to-point with Ethernet-based iLO, IPMI (versions 1.5, 2.0), DRAC, RSA and ALOM service processors. Click for more.

Service Processor Enabled Servers

This list is a collection of public information available at the server vendor's web sites, and is meant to make it easier for users to gather information about specific servers and their service processor capabilities. It includes servers that have service processors embedded in them, either included as standard capability or as an optional upgrade, as well as certain servers known not to have service processor capabilities.

 
This list is being constantly updated as new information about servers and service processors become available, so make sure to check back periodically. Also, if you would like to provide feedback about a certain server or service processor type, please click here.
 
In order to see the list and search for servers with service processors, click here