Intel® Server Boards and Server Platforms Server Management Guide Intel part number: G37830-002 October 2012
Revision History Revision History Date March 2008 Revision Description 0.5 Initial release. April 2008 0.9 Updated document for all currently shipping servers. March 2009 1.0 Overhauled the entire document. September 2009 1.1 Added S3420GP support. June 2011 2.0 Added S1200BT support. December 2011 3.0 Added S1400/S2400/S2600/S4600 support. October 2012 3.1 Added SDR information. Disclaimers INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS.
Revision History Table of Contents 1 Introduction ....................................................................................................................................... 1 1.1 Industry standards .................................................................................................................... 1 1.1.1 Intelligent Platform Management Interface (IPMI) ................................................. 1 1.1.2 Baseboard Management Controller (BMC) .............................
Table of Contents 2.6 2.5.4 IPMI 2.0 Channel Management ............................................................................ 24 2.5.5 BMC IP Address and external connection ............................................................ 25 2.5.6 Secure Shell (SSH) ................................................................................................ 26 2.5.7 BMC Users ............................................................................................................ 26 2.5.
Table of Contents 4.4 4.5 4.6 5 Intel® System Information Retrieve Utility ........................................................................... 56 4.4.1 Overview ............................................................................................................... 56 4.4.2 Supported Operating System ................................................................................. 57 4.4.3 Install/uninstall ..................................................................................
Table of Contents 5.5 5.6 5.7 vi 5.4.6 Configuring Microsoft Windows Server 2003* to support SOL........................... 86 5.4.7 Configuring Linux* to support SOL ..................................................................... 91 Remote Manage the Server using IPMITOOL ...................................................................... 94 5.5.1 Run IPMITOOL using in-band Solution ............................................................... 94 5.5.
Table of Contents 5.7.13 5.7.14 5.7.15 5.7.16 5.7.17 5.7.18 5.7.19 ® 5.7.12.1 Supported Properties ......................................................................... 115 5.7.12.2 Supported Verbs ................................................................................ 115 Remotesap1 ......................................................................................................... 116 5.7.13.1 Supported Properties .................................................................
List of Figures List of Figures Figure 1. Rear connectors of the Intel® SR2500 server system...........................................................12 Figure 2. Intel® Remote Management Module 2 and NIC .................................................................14 Figure 3. IPMI channel 3 settings on Intel® RMM2 navigation web page ...........................................15 Figure 4. Restart RMM2....................................................................................................
List of Figures Figure 39. Save BMC settings .......................................................................................................80 Figure 40. Gratuitous ARP and BMC ARP Response Setting ............................................................81 Figure 41. BMC LAN Channel Access mode ..................................................................................82 Figure 42. Intel® DPCCLI Installation ................................................................................
List of Tables List of Tables Table 1. Feature Comparison ........................................................................................................................ 7 Table 2. Key differences Between BMC features ......................................................................................... 9 Table 3. Standard Channel Assignments .................................................................................................... 11 Table 4. Shared Ethernet ports with BMC ..........
List of Tables
Introduction 1 Introduction The server management hardware that is part of Intel® server boards and Intel® server platforms serves as a vital part of the overall server management strategy. The server management hardware provides essential information to the system administrator and provides the administrator the ability to remotely control the server, even when the operating system is not running.
Introduction IPMI interface isolates systems management software from hardware. Hardware advancements can be made without impacting the systems management software. IPMI facilitates cross-platform management software. You can find more information on IPMI at the following URL: http://www.intel.com/design/servers/ipmi. 1.1.2 Baseboard Management Controller (BMC) A baseboard management controller (BMC) is a specialized microcontroller embedded on most Intel® server boards.
Introduction provided by management applications and the OS. System management software such as Intel® System Management Software and the OS can provide a more sophisticated control, error handling and alerting, than can be directly provided by the platform management subsystem. Out-of-Band (OOB) This involves communicating directly to the BMC and bypassing the OS.
Introduction the OS. Before IPMI messaging can work on a LAN connection, administrators must enable\configure the system for IPMI over LAN mode. By default, the IPMI over LAN mode is disabled to prevent unauthorized access. However, even if IPMI over LAN is disabled, other related attributes can still be configured through Server Administrator and will take effect whenever IPMI over LAN is finally enabled. From the IPMI point-of-view, the interface to the network controller is dedicated to the BMC.
Introduction Email Alerts BMC supports Email alerting through the Simple Mail Transport Protocol (SMTP). This feature allows the user to receive Email alerts indicating issues with the server. The email alert provides a text string that describes a simple description of the event. Power Management Intel® S5500 Series server boards support power management through the Intel® Node Manager technology. It is a platform-resident technology that enforces power policies for the platform.
Introduction Display a sensor: show /system1/ Example: show /system1/sensor25 show /system1/tempsensor1 1.3 Advanced Management features of Intel® RMM2/RMM3/RMM4 solutions Intel® Remote Management Module (RMM2/3/4) is an add-on solutions to enhance baseboard management control on Intel® server boards.
Baseboard Management Controller 2 Baseboard Management Controller 2.1 Feature comparison between different generation Intel® server boards Different generations of Intel® server boards have a different type of BMC integrated onto the server boards. Also, different generations of Intel® server boards only support different types of add-on remote management cards. The level of monitoring and alerting features provided depend on the type of on-board BMC and addon remote management card.
Baseboard Management Controller Remote management through LAN: Remote power on\off\reset, read SEL, Sensor status (system health) Yes Yes Yes Yes Intel® E5-4600/2600/2 400/1600 Product Families Yes Serial Over LAN (Console redirection over LAN) Yes Yes Yes Yes Yes SNMP traps (LAN alerts) and Platform Event Filtering Yes Yes Yes Yes Yes Email Alerts Yes N/A Yes Yes Yes Remote Management through serial port Yes N/A Yes Yes Yes Auto recovery from hangs during boot – BMC watchdog
Baseboard Management Controller Table 2. Key differences Between BMC features Intel® S5000/S7000 Server Boards Intel® Intel® Intel® Server Boards Intel® Server S3200/X38ML Server Board S5500BC S5500HC/S5520SC/S S1200/S1400/S1600 Server Boards 5520UR/SC5520WB/ /S2400/S2600/S460 S3420GP 0 Product Families IPMI IPMI 2.0 IPMI 2.0 IPMI 2.0 IPMI 2.0 IPMI 2.
Baseboard Management Controller between the BMC and the external world. The BMC supports a maximum of three LAN interfaces: Two LAN interfaces utilize the embedded ESB2 NICs (one channel per embedded NIC). One LAN interfaces utilizes an optional external NIC known as the ASMI NIC. Use of this NIC requires the installation of the optional Intel® Remote Management Module add-in card.
Baseboard Management Controller Table 3. Standard Channel Assignments Channel ID Interface 0 IPMB Supports Sessions No 1 LAN 1 (ESB2 NIC) Yes 2 LAN 2 1 (ESB2 NIC) Yes 1 ® 3 LAN 3 (Intel Remote Management Module 2) No 4 EMP (Basic/PPP) Yes 5 Reserved – 6 PCI SMBus – 7 SMM No 0Eh Self – 0Fh SMS/Receive Message Queue No Note: If supported by the server system. 2.2.4 Dedicated MAC Address Each of the ESB2’s two NIC channels has a unicast MAC filter reserved for BMC use.
Baseboard Management Controller NOTE Only one dedicated interface can be enabled for management traffic at any time. For details on which Ethernet port is shared with the BMC to ensure successful communication, see the following table. Table 4. Shared Ethernet ports with BMC Intel® Server Boards Intel S5000 Server Boards System Ethernet port shared with the BMC On-board NIC1 or NIC 2 Intel® S7000 Server Boards On-board NIC1 or NIC 2 ® NOTE ® Intel S3000 server boards does not have an on-board BMC.
Baseboard Management Controller Table 5. BMC Users Users User 1 User Name Null Null Password Status Disabled Characteristics Only Password can be changed. User 2 root Superuser Disabled Only Password can be changed. User 3 test1 Superuser Disabled User name and password can be changed. User 4 test2 Superuser Disabled User name and password can be changed. User 5 test3 Superuser Disabled User name and password can be changed.
Baseboard Management Controller Figure 2. Intel® Remote Management Module 2 and NIC Intel® RMM2 contains a dedicated NIC that is able to support both DHCP and static IP addresses. RMM2 has its own user authorization solution that is not similar to BMC’s user authorization. Intel® RMM2 has several utilities to perform network and user configuration. The Intel® RMM2 module features an embedded operating system and applications that offer a variety of standardized interfaces.
Baseboard Management Controller Examples on step by step instructions: 1. Update both Intel® RMM2 and system’s BMC FW to the latest 2. Use psetup or kiratool to setup Intel® RMM2’s IP address (static or DHCP) 3.
Baseboard Management Controller Figure 4. Restart RMM2 6. Check/confirm RMM2’s IP address by psetup or kiratool (DHCP IP address could be changed after RMM2 reset) 7. Restart BMC by doing: > syscfg /rbmc 8. User IPMITOOL to access BMC through Intel® RMM2’s dedicate NIC: > ipmitool -I lan -H 10.239.56.103 -U "admin" -P "password" fru NOTE Here “10.239.56.103” is an example of Intel® RMM2’s IP address. Your BMC’s configuration about user name and IP address may be varied. 2.
Baseboard Management Controller 2.3.2 IPMI 2.0 Channel Management Every messaging interface is assigned an IPMI channel ID by IPMI 2.0. Commands are provided to configure each channel for privilege levels and access modes. The following table shows the standard channel assignments. Table 6. Standard Channel Assignments Channel ID Interface Supports Sessions 0 IPMB No 1 LAN 1 Yes 4 Reserved – 5 Reserved – 6 Reserved – 7 SMM No 0Eh Self – 0Fh SMS/Receive Message Queue No 2.3.
Baseboard Management Controller Table 7. Shared Ethernet ports with BMC Intel® Server Boards Intel S3200 Server Boards System Ethernet port shared with the BMC On-board NIC1 Intel® Server Board X38ML On-board NIC1 ® The following figure displays the location for NIC1 and NIC2 on Intel® server system SR1520ML to serve as a reference. NOTE The location of the on-board NICs may be slightly different on other Intel® server boards. A On-board NIC1 B On-board NIC2 Figure 5.
Baseboard Management Controller Table 8. Feature Comparison Users User Name Password Status Characteristics User 1 Null Null Disabled Only Password can be changed. User 2 root superuser Disabled Only Password can be changed. User 3 test1 superuser Disabled Both user name and password can be changed. User 4 test2 superuser Disabled Both user name and password can be changed. User 5 test3 superuser Disabled Both user name and password can be changed.
Baseboard Management Controller Host-BMC communication over the same physical LAN connection, also known as “loopback”, is not supported. This includes “ping” operations. 2.4.3 IPMI 2.0 Channel Management Every messaging interface is assigned an IPMI channel ID by IPMI 2.0. Commands are provided to configure each channel for privilege levels and access modes. The following table shows the standard channel assignments. Table 9.
Baseboard Management Controller If the BMC’s IP address on a LAN channel changes while a LAN session is in progress over that channel, the BMC does not take action to close the session except through a normal session timeout. The remote client must re-sync with the new IP address. The BMCs communicate through NIC 1 or NIC 2 depending on your network configuration. To communicate with the BMC, you need to attach a standard Ethernet cable. You can use PING to confirm that this connection is valid.
Baseboard Management Controller 2.4.6 BMC Users The BMC supports the IPMI 2.0 user model including support for User ID 1. 15 user IDs are supported. These 15 users can be assigned to any channel. The following restrictions are placed on user-related operations: User names for User IDs 1 and 2 cannot be changed. These will always be “” (Null) and “root” respectively. User 2 (“root”) will always have the administrator privilege level.
Baseboard Management Controller Intel® RMM2 uses its own user authorization, while Intel® RMM3 uses BMC’s user authorization. Intel® RMM2 uses its dedicated utility, Psetup.exe, to configure Intel® RMM2’s IP address, user name, and password. Intel® RMM3 uses common utilities, such as the Intel® Deployment Assistant (IDA), SYSCFG utility or BIOS menu to configure its IP address, username, and password for remote access. The web server is available on all enabled LAN channels.
Baseboard Management Controller Interface 3: This interface is available from an optional Intel® RMM4, which is a dedicated management NIC and not shared with the host. For these channels, support can be enabled for IPMI-over-LAN and DHCP. For security reasons, embedded LAN channels have the following default settings: IP Address: Static All users disabled IPMI-enabled network interfaces may not be placed on the same subnet.
Baseboard Management Controller Channel ID Interface Supports Sessions 4 Reserved Yes 5 USB No 6 Secondary IPMB No 7 SMM No 8 – 0Dh Reserved – 0Eh Self 2 – 0Fh SMS/Receive Message Queue No 2.5.5 BMC IP Address and external connection The BMC IP address for a particular embedded NIC is always different from the IP address of the Server’s operating system. The BMC supports static and DHCP sourced IP address assignment on all of its management NICs.
Baseboard Management Controller 2.5.6 Secure Shell (SSH) Secure Shell (SSH) connections are support for SMASH-CLP sessions to the BMC. 2.5.7 BMC Users The BMC supports the IPMI 2.0 user model including support for User ID 1. 15 user IDs are supported. These 15 users can be assigned to any channel. The following restrictions are placed on user-related operations: User names for User IDs 1 and 2 cannot be changed. These will always be “” (Null) and “root” respectively.
Baseboard Management Controller 2.5.9 New Features of BMC Compared to Intel® S5500 series server boards, in the current generation of servers, new features have been added to BMC (Even with no Intel® RMM4 module installed), they are: Embedded Web Server BMC Base manageability provides an embedded web server and an OEM-customizable web GUI which exposes the manageability features of the BMC base feature set.
Baseboard Management Controller Figure 9. Console Redirection Window Additional features supported by the web GUI includes: Figure 10. Power Control and Status Window Presents all the Basic features to the users. Power on/off/reset the server and view current power state. Displays BMC, ME and SDR version information. Display overall system health. Configuration of various IPMI over LAN parameters for both IPV4 Configuration of alerting (SNMP and SMTP).
Baseboard Management Controller – Display system asset information for the product, board, and chassis. Display of BMC-owned sensors (name, status, current reading, enabled thresholds), including color-code status of sensors. Provides ability to filter sensors based on sensor type (Voltage, Temperature, Fan and Power supply related) Automatic refresh of sensor data with a configurable refresh rate. On-line help.
Baseboard Management Controller CPU/memory register data useful for diagnosing the cause of the following system errors: CATERR, ERR[2], SMI timeout, PERR, and SERR - The debug data is saved and time-stamped for the last 3 occurrences of the error conditions. a. PCI error registers b. MSR registers c. MCH registers BMC configuration data BMC FW debug log (that is, SysLog) – Captures FW debug messages. o SMBIOS table data. The entire SMBIOS table is captured from the current boot.
Baseboard Management Controller critical incidents and to undertake necessary maintenance. Intel® RMM4 is comprised of up to two boards – Intel® RMM4 Lite and the optional Intel® Dedicated Server Management NIC (DMN). Figure 11. Intel® RMM4 Lite and Dedicated NIC The Intel® RMM4 Lite is a small board that unlocks advanced management features on the RGMII 1Gb interface when installed on Intel® server boards.
Baseboard Management Controller Configure BMC LAN Channel 3’s IP address (DHCP or static IP) The web server is available on all enabled LAN channels. If a LAN channel is enabled, properly configured, and accessible, the web server is available. For security reasons, the null user (user 1) may not be used to access the web server. The session inactivity timeout for the embedded web server is 30 minutes. This is not user-configurable.
Baseboard Management Controller MAC addresses are assigned for management NICs from a pool of up to 3 MAC addresses allocated specifically for manageability. The total number of MAC addresses in the pool is dependent on the product HW constraints (for example, a board with 2 NIC ports available for manageability would have a MAC allocation pool of 2 addresses). IPMI-enabled network interfaces may not be placed on the same subnet.
Baseboard Management Controller BMC LAN channel 3 (RMM) MAC address = NIC1 MAC address + 6. 2.6.4 BMC LAN Failover The BMC firmware provides a LAN failover capability such that the failure of the system HW associated with one LAN link will result in traffic being rerouted to an alternate link. This functionality is configurable through IPMI methods as well as through the BMC’s embedded user interface.
Baseboard Management Controller The BMC LAN failover functionality can be configurable from the IDA/SYSCFG as well as the BMC’s Embedded UI, you specify the physical LAN links constitute the redundant network paths or physical LAN links constitute different network paths. BMC will support only an “all or nothing” approach – that is, all interfaces bonded together, or none are bonded together. The LAN Failover feature applies only to BMC LAN traffic.
Baseboard Management Controller 2.6.6 BMC IP Address and external connection The BMC IP address for a particular embedded NIC is always different from the IP address of the Server’s operating system. The BMC supports static and DHCP sourced IP address assignment on all of its management NICs. The IP address source parameter must be set to “static” before the IP address, subnet mask, or gateway address can be manually set.
Baseboard Management Controller respectively. User 2 (“root”) will always have the administrator privilege level. All user passwords (including passwords for 1 and 2) may be modified. User IDs 3-15 may be used freely, with the condition that user names are unique. Therefore, no other users can be named as “” (Null), “root,” or any other existing user name. Table 15. Feature Comparison Users User Name Password Status Characteristics User 1 Null Null Disabled Only Password can be changed.
Baseboard Management Controller Figure 13. System Information Window The GUI presented by the embedded web server authenticates the user before allowing a web session to initiate. It presents all functions to all users but grays-out those functions that the user does not have privilege to execute. (For example, if a user does not have privilege to power control, then the item is displayed in grayed-out font in that user’s UI display).
Baseboard Management Controller Additional features supported by the web GUI includes: Figure 15. Power Control and Status Window Presents all the Basic features to the users. Power on/off/reset the server and view current power state. Displays BIOS, BMC, ME and SDR version information. Display overall system health. Configuration of various IPMI over LAN parameters for both IPV4 and IPV6 . Configuration of alerting (SNMP and SMTP).
Baseboard Management Controller Embedded Platform Debug feature - Allow the user to initiate a “diagnostic dump” to a file that can be sent to Intel® for debug purposes. Virtual Front Panel. The Virtual Front Panel provides the same functionality as the local front panel. The displayed LEDs match the current state of the local panel LEDs. The displayed buttons (for example, power button) can be used in the same manner as the local buttons. Severity level indication of SEL events.
Baseboard Management Controller The Main Purpose of the Virtual Front Panel is to provide the front panel functionality virtually. For Reset from the Virtual Front Panel, the reset is done by a Chassis control command. For Reset from the Virtual Front Panel, the restart cause will be because of Chassis control command. Virtual Front Panel help is available for virtual panel module.
Baseboard Management Controller Data Center Management Interface (DCMI) The DCMI Specification is an emerging standard that is targeted to provide a simplified management interface for Internet Portal Data Center (IPDC) customers. It is expected to become a requirement for server platforms that are targeted for IPDCs. DCMI is an IPMI-based standard that builds upon a set of required IPMI standard commands by adding a set of DCMI-specific IPMI OEM commands.
Baseboard Management Controller The Intel® Remote Management Module 4 is currently supported on the following Intel® server and workstation boards: S1200BTL S2400BB S2400SC S2600CP S2600GL S2600GZ S2600IP W2600CR The Intel® RMM4 has two different packages, RMM4 Lite edition (AXXRMM4Lite) and RMM4 full edition (AXXRMM4). RMM4 Lite edition box contains Intel® Remote Management Module 4 Lite module.
Baseboard Management Controller Key features of the Intel® RMM4 add-on card are: KVM redirection through either the RMM4 NIC or the baseboard NIC used for management traffic; up to two simultaneous KVM sessions. Media redirection – The media redirection feature is intended to allow system administrators or users to mount a remote IDE or USB CD-ROM, floppy drive, or a USB flash disk as a remote device to the server.
BMC Firmware Update Procedure 3 BMC Firmware Update Procedure BMC firmware can be updated from pre-OS and OS present environments, such as Extensible Firmware Interface, Microsoft Windows* Pre-installation Environment (WinPE), Microsoft Windows* Server and Red Hat* or SuSE* Linux Enterprise Server operating systems. You can download the server firmware update package from http://www.intel.com/p/en_US/support/. 3.
BMC Firmware Update Procedure 3.3 Update BMC firmware under IDA Intel® Deployment Assistant: To use IDA, download and copy “Firmware Update Package for the Intel® Deployment Assistant, Intel® One-boot Flash Utility, Intel® embedded EFI shell and Microsoft Windows* Pre-installation Execution Environment (WinPE)” (name of the package may vary depending on the platform) to your USB key: Boot system using the Intel® Server Deployment Toolkit CD that shipped with the system. Click “Get System Updates”.
BMC Firmware Update Procedure This method requires the Intel® One Boot Flash Update Utility (Intel® OFU), which needs to be downloaded from Intel®’s support web site and is part of the “BIOS, Firmware Update and configuration utilities for Linux*”. Extract the Intel® OFU package for Linux* and run ./setup to install the Intel® OFU utility on your system.
Server Management Software and Utilities 4 Server Management Software and Utilities In order to perform in-band and out-of-band management of Intel® Servers, Intel® provides several solutions such as tools, utilities, and management software to allow you to manage the system easily. This chapter provides an overview of Intel® Server management utilities, tools, and software. 4.
Server Management Software and Utilities On S1400/S1600/S2400/S2600/S4600 platform series: When BIOS administrator password is set and it value is “admin@123” syscfg /bcs “admin@123” “Quiet Boot” 0 syscfg /bcs “admin@123” “Main” “Quiet Boot” 0 “POST Error Pause” 1 syscfg /bcs “admin@123” “system acoustic and performance configuration” “Set throttling mode” 2 “Altitude” 900 “Set fan profile” 2 When BIOS administrator is not set.
Server Management Software and Utilities must be located in this directory.) – In Microsoft Windows*, Microsoft Windows Preinstallation Environment*, or EFI, type: syscfg /r ini filename.ini /b – In Linux*, type: ./syscfg /r ini filename.ini /b 4.1.4 SYSCFG installation and usage Linux*: – Download BIOS, Firmware Update, and Configuration Utilities for Linux* from http://www.intel.com/ and unzip the "syscfg-linux.zip" file into a folder on your Linux* system.
Server Management Software and Utilities PE” package. 4.2 Intel® Deployment Assistant CD The Intel® Deployment Assistant (IDA) provides a single interface with an easy to use HTML like graphic UI to ease the process of setting up and deploying an Intel® server from initial boot through the initiation of an unattended OS installation. Each Intel® server board ships with a copy of Intel® Deployment Assistant CD.
Server Management Software and Utilities Figure 18. Intel® Deployment Assistant CD Homepage 4.2.1 Get System Updates A system firmware update can be performed in an online or offline manner. Figure 19. System Update page of IDA CD Optionally, the user can: Perform online update from http://www.intel.com/. IDA can automatically mount the remote network drive using the user name, password and remote network share name provided by the user.
Server Management Software and Utilities 4.2.2 Configure a server IDA allows the user to configure key BIOS and server management settings. A wizard automatically displays only the screens that the user chooses to configure on the server, for example, set the asset tag, configure BIOS, and configure server management such as set the BMC LAN channel information. Figure 20. Configure a server page on the IDA CD 4.2.
Server Management Software and Utilities 4.2.4 Unattended OS installation IDA can be used to configure an unattended OS installation, resulting in the user answering questions within the IDA user interface and then adding the OS CD(s). OS installation starts automatically after the server reboots and requires no further input. Supported Operating Systems: Microsoft Windows* Linux* (SuSE* and Red Hat* Enterprise Linux) VMware Figure 22. Unattended Installation GUI screen 4.
Server Management Software and Utilities 4.3.1 The SEL Log format The SEL entry is originally in HEX format. The SEL viewer utility has the ability to translate the SEL records from hexadecimal format to human readable text format.
Server Management Software and Utilities For detailed information on how to use the SEL viewer, refer to the System Event Log (SEL) Viewer Utility User Guide that is provided with BIOS, Firmware Update, and Configuration Utilities. 4.4 Intel® System Information Retrieve Utility The Intel® System Information Retrieval Utility (hereinafter referred to as sysinfo) is used for collecting system information.
Server Management Software and Utilities 4.4.2 Supported Operating System Intel® offered UEFI version, Microsoft Windows* version and Linux* version Intel® System Information Retrieval Utility that the customers are able to run it and collect system information under these environments. 4.4.3 Install/uninstall For sysinfo install and uninstall under Microsoft Windows*/Linux*, you have to refer Release Notes and User Guide to perform some pre-request tasks.
Server Management Software and Utilities Figure 25. Example of part of Sysinfo Log 4.5 Intel® System Management Software Intel® System Management Software (SMS) offers remote monitoring, configuration, software distribution, updates, and troubleshooting management features. It includes a collection of software applications targeted for all market segments. Intel® SMS DVD that is shipped with Intel® server boards contains the following components: Table 16.
Server Management Software and Utilities Server Management Pack User Guide that were included in the Intel® SMS DVD. The following table lists the features and benefits of Intel® System Management Software Suite of Products: Table 17.
Server Management Software and Utilities 4.5.1 Intel® Multi-Server Manager The Intel® Multi-Server Manager is a product offering from the Intel® System Management Software a suite of software products designed to reduce the cost and time of managing servers and keep businesses running 24/7. Intel® Multi-Server Manager is included with almost all Intel® server products at no additional charge giving user “peace of mind” that servers are healthy. Prime benefits include: Proactive alerting.
Server Management Software and Utilities Figure 26. Intel® Multi-Server Manager 4.5.2 Intel® Active System Console The Intel® Active System Console is a simple, lightweight web application console that gives you a dashboard view of the Server hardware on which it is running. It helps you proactively monitor the health of your Server, allows remote configuration of Server, tracking of assets, alerting of any issues and generation of asset reports.
Server Management Software and Utilities Figure 27. Intel® ASC Home Page The Intel® Active System Console displays the hardware sensors, Field Replaceable Unit (FRU) data, and System Event Log (SEL) for the Intel® Computer selected in the Intel® Computers view. This console is only available for Intel® servers that have an ESB2 BMC or Integrated BMC. To launch the Intel® Active System Console, go to Start > Programs > Intel® Server Management Software > Intel® Active System Console.
Server Management Software and Utilities 4.5.3.1 Intel® Server Management Pack The Intel® Server Management Pack for Microsoft System Center Essentials 2007* SP1 provides hardware monitoring capabilities to Intel® Servers that support IPMI version 2.0. This Management Pack works on both Microsoft System Center Essentials* and Microsoft System Center Operations Manager*.
Server Management Software and Utilities Discovery Configuration Wizard detects networked Intel® Modular server systems. Displays the health and alerts from Intel® Modular Server Compute Modules. Supports launching the Intel® Modular Server Control Software web-based console. For detailed information on usage of Intel® Module Server Management Pack, refer to the Intel® Modular Server Management Pack User Guide. 4.5.3.
Server Management Software and Utilities Platform control mode When the Intel® Command Line Interface is in Platform Control mode, you can issue commands to the remote system. To start an Intel® Command Line Interface session with dpccli, the network proxy dpcproxy must be running, either on the managing console or a central network proxy system.
Server Management Software and Utilities server, regardless of which operating system (Microsoft Windows* or Linux*) you are running on either system. Start the telnet session to the remote server as follows: At the operating system command prompt, type telnet xxx.xxx.xxx.xxx 623 The xxx represent the IP address of the system running the Network Proxy. This may be a central network server with the Proxy installed.
Server Management Software and Utilities Microsoft Windows* operating system. For systems running the Microsoft Windows* operating system, the SNMP subagent is implemented as a dynamic link library (DLL) and is configured in the Registration Database. For Linux* systems, the SNMP subagent is implemented as an rpm package. It is installed, configured and started as a service. The SNMP master agent (net-snmp) communicates with the subagent through Agent protocol. 4.5.5.
Scenarios and Best Practices 5 Scenarios and Best Practices This chapter provides examples that show how to make the Intel® Server Management Interface to work. Topics covered in this chapter include: Configure BMC for OOB function using SYSCFG Configure BMC for OOB function using IDA Remotely manage Intel® server use DPCCLI 5.
Scenarios and Best Practices 5.1.3 Configure BMC LAN Failover To use SYSCFG to configure BMC LAN Failover, perform the following step: syscfg /lfo enable On S1400/S1600/S2400/S2600/S4600 platform BMC FW provides a LAN failover capability such that the failure of the system HW associated with one LAN link will result in traffic being rerouted to an alternate link. NOTE S1200BT platforms will not have support for above switch. 5.1.
Scenarios and Best Practices Figure 28. Configure Console Redirection for Serial B 5.2 Configure the BMC using IDA Intel® Deployment Assistant Software is provided on the Intel® Server Deployment Toolkit CD that is shipped with the system. With IDA, it is easy to configure the BMC using the Graphical User Interface (GUI). 5.2.1 Configure BMC for LAN connection To use the IDA to configure OOB LAN, perform the following steps: Select “Configure a Server” after booting from the IDA CD.
Scenarios and Best Practices key in your IP address/Subnet Mask/Gateway depending on your network configuration. You can also select Enable Serial Over LAN and Configure Alert on these screens. Figure 29. Enabling Serial Over LAN and Configure Alert 5.2.2 Configure BMC to use SOL To use IDA to configure SOL, select “Enable Serial Over LAN”. 5.2.3 Configure BMC for embedded email alerts To use IDA to configure email alerts, perform the following steps: Select “Enable LAN alerting”.
Scenarios and Best Practices Figure 30. Enable LAN Alerting 5.2.4 Configure BMC Platform Event Filters To use IDA to configure PEF filters, perform the following steps: Select the check boxes for the events that are to trigger alerts as shown in the following figure. Figure 31. Configure BMC PEF Click the “Next” button to move on to the next configuration page. 5.2.
Scenarios and Best Practices NOTE You can configure other BMC users depending on your preference. Figure 32. Configure BMC Users In the “Edit User Data” dialog box, you can enable the user account you selected and assign user privileges to this user. Make sure to select the “Change Username and Password” check box and enter the password and confirm the password. Then, click the “OK” button.
Scenarios and Best Practices Figure 33. Set BMC user’s password Apply the configuration and click “Restart” to reboot the server. This will save the configuration that is applied. 5.3 Configure basic Integrated BMC setting from BIOS menu Starting from Intel® S5500 and S3420 server board platforms, we have enabled BMC basic setting (IP address, username and password) to be done from BIOS menu.
Scenarios and Best Practices Figure 34. BMC LAN Configuration 5.3.
Scenarios and Best Practices Figure 35. BMC IP Configuration Go to “Baseboard LAN configuration” or “Intel® RMM3/4 LAN configuration” area.
Scenarios and Best Practices 5.3.2 Configure BMC users To use BIOS menu to configure users perform the following steps: Go to “BMC LAN configuration” sub-menu under “Server Management” section of BIOS menu Move to “User configuration” section and chose “anonymous” user or “root” user: NOTE You can configure other BMC users depending on your preference. Figure 36. Configure BMC Users NOTE The User ID “anonymous” cannot be used through the RMM3 interface.
Scenarios and Best Practices Select the “Enable” to enable “root” user account (here is an example) Figure 37.
Scenarios and Best Practices Create and confirm user’s password: Figure 38.
Scenarios and Best Practices Confirm the changes by press F10, “Save configuration and Exit” Figure 39. Save BMC settings NOTE BMC LAN Channel setting change only take effect after next reboot by pressing F10 to “Save configuration and Exit”. 5.4 Remotely Manage the Server through DPCCLI The Intel® Command Line Interface (CLI) console runs on the management console and enables communication between the management console and the network proxy, which in turn communicates to the managed server.
Scenarios and Best Practices 5.4.
Scenarios and Best Practices If this setting is set, you may not be able to see the BIOS boot information from SOL for ESB2 BMC. To enable it, type #syscfg /lc 1 7 Always Integrated BMC has this setting enabled by default. Figure 41. BMC LAN Channel Access mode 5.4.
Scenarios and Best Practices Figure 42. Intel® DPCCLI Installation If you are installing DPCCLI on Microsoft Windows 2008* system, you must enable telnet service in your management console. 5.4.3 Remote manage server by DPCCLI You must first complete the steps detailed in section 5.2 or 5.4 to enable the BMC for OOB and SOL connection. Then, you can connect the managed server using DPCCI. You can use Telnet to remotely manage the server.
Scenarios and Best Practices Figure 43. DPCCLI login screen The following tasks demonstrate some of the features of the Intel® Command Line Interface utility. This includes monitoring system information, retrieving and saving the system event log and starting a SOL session. 1. 2. 3. 84 To read the temperature sensors of the remote managed system, type: dpccli> sensors –v –T temp 11/14/2008 | 13:58:32 | Baseboard Temp | ok | 28.00 11/14/2008 | 13:58:32 | P1 Mem Margin | ok | 1.
Scenarios and Best Practices 11/14/2008 | 13:58:03 | BB +1.1V IOH 11/14/2008 | 13:58:04 | BB +1.1V P1 Vccp 11/14/2008 | 13:58:04 | BB +1.1V P2 Vccp 11/14/2008 | 13:58:04 | BB +1.5V P1 DDR3 | ok | ok | ok | ok | | | | 1.28 0.84 0.84 1.52 | Volts | Volts | Volts | Volts dpccli> You can use the Intel® Command Line Interface to display and save the system event log on remote management clients. 1.
Scenarios and Best Practices 5.4.5 Using SOL to access BIOS Menu When the ESB2 BMC or Integrated BMC are used for serial port sharing, SOL and Console Redirection on the Serial B port are mutually exclusive features, but SOL setting and console redirection setting must be synced. In order to access the BIOS Setup Menu from a SOL session, you may have to configure BIOS console redirection as a pre-request. You can use Telnet to remotely manage the server.
Scenarios and Best Practices Microsoft Windows Server 2003* has two components that work with DPCCLI and the BMC to provide out-of-band access to the operating system: Microsoft Emergency Messaging Service* (EMS) Microsoft Special Administration Console* (SAC) To exit SOL and return to the SMBridge prompt, press the tilde key and the period key (that is, press ~.). For more information, see: http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/enus/EMS_SAC_commands.
Scenarios and Best Practices Figure 46. Enable Microsoft Windows* EMS on Serial Port 2 NOTE In order to perform this step, you must enable console redirection on COM2 (SOL session) with a baud rate of 115200 in advance for this setting (115200 baud rate is only used as an example in this guide). Figure 47. Console Redirection on Serial Port B 88 Reissue the bootcfg command to see the result. The changes are highlighted in the example shown.
Scenarios and Best Practices Figure 48. EMS setting results Reboot the server in order for the changes to take effect. NOTE To turn EMS off again, issue the following command: bootcfg /ems off /id 1 Where 1 is the boot entry you modified in the preceding steps. Reboot the server to bring the changes online. Once you reboot and engage the DPCCLI console, you will see the EMS console.
Scenarios and Best Practices Figure 49. EMS Console Type the ch –si command to log in to the Microsoft Windows* OS command line environment. NOTE In the Login screen, key in username/domain name/password for authorization. Now, you are under the Microsoft Windows* Command Line Prompt: Figure 50.
Scenarios and Best Practices To close the command prompt channel, type exit. To leave the channel open and return to the SAC prompt, press ++0 (the number zero) (three keys in sequence). To leave the remote console and return to DPCCLI, press + (that is, ~.) 5.4.7 Configuring Linux* to support SOL You must configure Linux* to expose the Linux* initialization (booting) process through SOL.
Scenarios and Best Practices Enable Linux* boot procedure to be seen in the SOL console by adding the following lines for SOL boot session (an example is as shown below): title SUSE Linux Enterprise Server 10 SP2 SOL Session root (hd,5) kernel /boot/vmlinuz-2.6.16.60-0.21-bigsmp root=/dev/bi-id/scsi-SATA_ST31600811AS_6PT03YN8part vga=0x314 acpi=off resume=/dev/sda5 splash=slient showtpts console=ttyS1,19200 console=tty1 initrd /boot/initrd-2.6.16.60-0.
Scenarios and Best Practices Figure 54. Enable users login at SOL console 5. Allow users to log in as root from the SOL console by modifying the /etc/securetty file to add the following line: ttyS1 The result is shown in the following image: Figure 55. Enable users login as root from SOL console 6. Reboot Linux* to see the GRUB menu from SOL console. Figure 56.
Scenarios and Best Practices The following figure displays the Linux* SOL login console: Figure 57. SuSE Linux* SOL login console 5.5 Remote Manage the Server using IPMITOOL Apart from The Intel® Command Line Interface (CLI), Intel® Servers is IPMI2.0 standard, it follows IPMI Spec 2.0 and able to support open sourced IPMITOOL and other IPMI utilities.
Scenarios and Best Practices [root@localhost ~]# ipmitool fru list FRU Device Description : Builtin FRU Device (ID 0) Chassis Type : Main Server Chassis Chassis Part Number : TR2104 Chassis Extra : Intel Systems. Board Mfg Date : Sat Nov 12 11:45:00 2011 Board Mfg : Intel Corporation Board Product : S2600CP Board Serial : ............ Board Part Number : ..........
Scenarios and Best Practices Here, “192.168.1.10” is BMC IP address “root”/“password” is BMC’s user name and password. This results is same what you do it as in-band: # ipmitool sdr list 5.5.4 Activate SOL from IPMITOOL command If you want to activate SOL, you have three more steps: Enable console redirection (from BIOS menu or by SYSCFG command line), example: Figure 58.
Scenarios and Best Practices 5.6 SDR Update Guideline 5.6.1 What is SDR? There is Sensor Data Record (SDR) for many devices in the system. These SDR can be viewed as data files that are used by the Baseboard Management Controller (BMC) to determine system configuration and translate some BMC IPMI messages. The basic SDR format is defined in the Intelligent Platform Management Interface (IPMI) V2.0 specification (which can be downloaded from http://www.intel.com/design/servers/ipmi/).
Scenarios and Best Practices Power Unit Redundancy, Fan Redundancy, System Air Flow, Firmware Update Status, and Aggregate Temperature Margin Sensors. The BMC is not the only device that can have Sensor Data Records. There also can be records that are owned by the Management Engine (ME) or the Hot Swap Controller (HSC). You can tell which ones these are by the Sensor Owner ID of the record. The following table provides the list of Sensor Owner ID to the Sensor Owner.
Scenarios and Best Practices 5.6.3 When do you need to update the SDR? In general, the SDR should be updated under two main circumstances: Anytime that there is a change to the system that would affect the thermal characteristics of the system. You permanently add or remove a device that needs to be monitored.
Scenarios and Best Practices to the range and limits being different for each wattage power supply so it is recommended that an update be done to set the correct limits. On Intel® server boards with the Intel® 5500/5520 Chipset the SDR should be updated when replacing the processors with ones that have dramatically different thermal characteristic the Fan Speed Control curves will be affected. Therefore, it is best to update the SDR.
Scenarios and Best Practices 5.7 Managing Server using SMASH The Systems Management Architecture for Server Hardware (SMASH) is a suite of specifications that deliver industry-standard protocols to increase productivity of the management of a data center. The SMASH Command Line Protocol (SM CLP) specification provides an interface to heterogeneous servers, independent of machine state or OS state, system topology or access method.
Scenarios and Best Practices Verb help Is used to Provide information on using SMASH*. show Show all the targets, properties, and verbs supported by this target. version Show the current version of SMASH*. Figure 59. SMASH* Target 5.7.4 System1 The system target represents the server/blade. Power control is available on the target .System1, It contains sol1, sp1, and other sensor monitoring targets. Here sp1 means Service Process Configuration. 5.7.4.
Scenarios and Best Practices Property SysIdentification Task This R/W property reflects the current state of system identification. It can set to any of the following values: System identification can be turned off as follows: ->Set SysIdentification=OFF System identification can be timed ON as follows: ->Set SysIdentification=TIMED Set the timeout value. The TimeOutValue property is set to TIMED and SysIdentification property value is set to ON.
Scenarios and Best Practices Figure 60.
Scenarios and Best Practices Figure 61.
Scenarios and Best Practices 5.7.5 Settings1 Settings1 target represents the settings of the current session of SMASH* and does not have any targets. This target affects the current session: 5.7.5.1 Supported Properties The supported properties of the Settings1 target are as follows: Table 20. Setting 1 Target Property Task cdt Represents the current default directory. This is the path from where the session starts. outputformat This R/W property gives the output format: clpxml, text, clpcsv.
Scenarios and Best Practices Figure 62. Setting1 Target 5.7.6 SP1 The SP1 target (service processor) provides information of the user accounts Ethernet port and logs. It contains three targets -- enetport1 (Ethernet port target), accounts, and logs. 5.7.6.1 Supported Properties The supported property of the SMASH* target is identity: Property Identity Task This read only property gives a brief explanation of the present target and cannot be changed. 5.7.6.
Scenarios and Best Practices Figure 63. SP1 Target 5.7.7 SOL1 Serial Over LAN (SOL) is the name for the redirection of baseboard serial controller traffic over an IPMI session. It does not have any targets. 5.7.7.1 Supported Properties The supported property of the SOL1 target is as follows: Property Identity 108 Task This read only property gives a brief explanation of the present target and cannot be changed.
Scenarios and Best Practices 5.7.7.2 Supported Verbs The supported verbs of the SOL1 target are as follows: cd Verb Is used to Change from one valid target path to any other valid target path. exit Exit from the current SMASH* session. help Provide information on using SMASH*. show Show all the targets, properties, and verbs supported by this target. start Start the device. version Show the current version of SMASH*. Figure 64. SOL1 Target 5.7.7.
Scenarios and Best Practices to respond to UDP/IP packets or generate LAN alerts. Enetport1 (Ethernet port target) gives the port address information. Enetport1 contains only one target named lanendpt1. 5.7.8.1 Supported Properties The supported properties of the target enetport1 are as follows: Table 21. Target enetport1 Property macaddress Task Address that was received by the activated session. This read only property gives the value of the MAC address.
Scenarios and Best Practices 5.7.9 Lanendpt1 The target Lanendpt1 gives information about LAN configuration. It contains the target: Ipendpt1 - IP configuration. 5.7.9.1 Supported Properties Following is the supported property of lanendpt1 target: Property Identity Task This read only property gives a brief explanation of the present target and cannot be changed. 5.7.9.
Scenarios and Best Practices contains two targets - dnsendpt1 and remotesap1. The supported properties and supported verbs of the Ipendpt1 are as follows. 5.7.10.1 Supported Properties The supported properties of the ipendpt1 target are as follows: Table 22. Ipendpt1 target Property Ipaddress Task The value of ipaddress is the IP address of the SP.
Scenarios and Best Practices Figure 67. IPENDPT1 Target 5.7.11 Remotesap1 The remotesap1 target will enumerate all the configurable IPs under the containing target. A remote access server enables users who are not on a local network to access. This does not contains any targets. 5.7.11.1 Supported Properties The supported properties of the remotesap1 target are as follows: Table 23. Remotesap1 target Property defaultgatewayaddress Task IP address of the gateway.
Scenarios and Best Practices 5.7.11.2 Supported Verbs The supported verbs of the Remotesap1 target are as follows. cd Verb Is used to Change from one valid target path to any other valid target path. exit Exit from the current SMASH* session. help Provide information on using SMASH*. set Set the r/w supported properties show Show all the targets, properties, and verbs supported by this target. version Show the current version of SMASH*. Figure 68. REMOTESAP1 Target 5.7.
Scenarios and Best Practices 5.7.12.1 Supported Properties The supported properties of the dnsendpt1 target are as follows: Table 24. Dnsendpt1 Target Property domainnamefromdhcp Task Dhcp based DNS configuration. This property is a read only property. dnsdomainname This property gives the DNS Domain. This property is a read only property. serversfromdhcp This property shows the servers dhcp. This is a read only property.
Scenarios and Best Practices 5.7.13 Remotesap1 The remotesap1 target enumerates all the configurable IPs under the containing target. A remote access server enables user access to those users who are not on a local network. This does not contain any targets. 5.7.13.1 Supported Properties The supported properties of the remotesap1 target are dnsserveraddress and identity: Table 25. Remotesap1 target Property dnsserveraddress Task This property gives the dns server address. This is a R/W property.
Scenarios and Best Practices Figure 70. REMOTESAP1 Target 5.7.14 Remotesap2 5.7.14.1 Supported Properties The supported properties of the target remotesap2 are as follows: Table 27. Target remotesap2 Property dnsserveraddress Task Gives the dns server address. This is a R/W property. The value of this property can be set as follows: ->set dnsserveraddress=0.0.0.0 Identity This read only property gives a brief explanation of the present target and cannot be changed. 5.7.14.
Scenarios and Best Practices Figure 71. REMOTESAP2 Target 5.7.15 Account The account target represents user accounts. It does not contain any targets. 5.7.15.1 Supported Properties The supported properties of the target account are as follows: Table 28. Target account Property userid username Task This read only property defines the unique id for each user. This property gives the usermname of a particular account. This is settable except for userid=1.
Scenarios and Best Practices Property Identity Task This read only property gives a brief explanation of the present target and cannot be changed. 5.7.15.2 Supported Verbs The supported verbs of the account target are as follows: Verb cd Is used to Change from one valid target path to any other valid target path. exit Exit from the current SMASH* session. help Provide information on using SMASH*. delete Delete. To delete, go to sp1 target and delete account (n) where n>2.
Scenarios and Best Practices 5.7.16.1 Supported Properties The supported properties of the Logs1 target are as follows: Table 29. Logs1 target Property MaxNumberOfRecords Task This read only property gives information about maximum number of log records. Description A read only description about the target. Identity This read only property gives a brief explanation of the present target and cannot be changed. 5.7.16.
Scenarios and Best Practices 5.7.17 Record The record target represents the individual SEL entries. SEL records are in a list. Each SEL entity is a record. This does not have any targets. 5.7.17.1 Supported Properties The supported properties of the Record1 target are as follows: Table 30. Record1 target Property LogCreationClassName Task This read only property gives information about the log creation class name.
Scenarios and Best Practices Figure 74. RECORD1 Target 5.7.18 Sensor A typical server BMC would provide sensors for baseboard temperature, voltage, and chassis intrusion monitoring. A sensor uses one type of energy, a signal of some sort, and converts it into a reading for the purpose of information transfer. The sensor doesn’t have any targets. All properties of this target are read only properties. 5.7.18.1 Supported Properties Table 31.
Scenarios and Best Practices Property CurrentReading Task This read only property gives the current reading shown by the sensor BaseUnits This read only property gives the units for the value given by current reading property. SystemName This read only property gives the target name under which this sensor exists CreationClassName This read only property gives the creation class name of the sensor. DeviceID This read only property gives the device ID.
Scenarios and Best Practices Figure 75. SENSOR2 Target 5.7.19 Creating Targets Dynamic targets in SMASH*(without CIM) are the sensors and their associated entities. You need to go through the sdr and search for Full and Compact record types. Name the Full type as numsensor (indicates the analog sensors) and the Compact type as the sensor (indicates the discrete sensors). While a sensor instance is discovered, the EntityID and the EntityInstance of the record are also seen.
Scenarios and Best Practices Figure 76.
Glossary Glossary Term Definition ACPI Advanced Configuration and Power Interface ARP Address Resolution Protocol BMC Baseboard management controller CLI Command-line interface DHCP Dynamic Host Configuration Protocol DMTF Distributed Management Task Force FRU Field replaceable unit HSBP Hot-swap backplane HSC Hot-swap controller OFU Intel® One Boot Flash Update utility IDA Intel® Deployment Assistant IPMB Intelligent Platform Management Bus IPMI Intelligent Platform Management I
