Dell™ OpenManage™ Baseboard Management Controller Utilities User’s Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2007 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 . . . . . . . . . . . . . . . . . . . 10 . . . . . . 12 . . . . . . . . . . . . . . . . 12 . . . . . . . . . 12 . . . . . . . . . . . . . . . 14 . . . . . . . . . . 14 . . . . . . . . . . . . . . . 15 What’s New in BMC Management Utility 3.
2 Configuring Your Managed System BIOS Configuration . . . . . 25 . . . . . . . . . . . . . . . . . . . 25 Configuring System BIOS in Dell PowerEdge™ x8xx/x9xx Systems . . . . . . . Configuring System BIOS in Dell PowerEdge™ x9xx and xx0x Systems . . . . . 27 . . . . . . . 29 . . . 29 . . . . 30 . . . . . . . 30 . . . . . . . . . . . . 36 Using BIOS Console Redirection With SOL Proxy . . . . . . . . . . . . . . .
Installation Procedures . . . . . . . . . . . . . . . . . Installing on Systems Running Supported Windows Operating Systems . . . . . . . . . . . Uninstalling on Systems Running Supported Windows Operating Systems . . . . . . . . Installing on Systems Running Supported Linux Enterprise Operating Systems . . . 53 . . . . . 54 . . . 55 . . . . . . . . . . . . . . . . . . . . . . . . 55 . . . . . . . . . . . . . . . . . . 57 Using IPMI Shell IPMI Shell Command Syntax . . . . . . . . . . . .
A BMC Management Utility Error Codes . . . . . . . . . . . B Terminal Mode Commands 111 111 112 . . . . . . . . . . . . . . . . . . 112 . . . . . . . . . . . . . . . . . . . . . . . . . . 113 . . . . . . . . . . . . . . . . . . 113 . . . . . . . . . . . . . . . . . 113 . . . . . . . . . . . . . . 114 . . . . . . . . . . . . . . . . . . 114 . . . . . . . . . . . . . . . . . . . . . . 115 Security Information .
D Serial Port Console Redirection . . . . . . 125 . . . . . . . . . . . . . . . . . 125 Console Redirection Via COM1 . . . . . . . . . . 125 Console Redirection Via COM2 . . . . . . . . . . 125 Serial Communication Serial Terminal Communication to BMC or DRAC . . . . . . . . . . SPCR Table . . . . . . . . . 126 . . . . . . . . . . . . . . . . . . . . . . . 126 . . . . . . 127 . . . . . . 127 . . . . .
Contents
Introduction The Dell™ systems’ baseboard management controller (BMC) monitors the system for critical events by communicating with various sensors on the system board and sends alerts and logs events when certain parameters exceed their preset thresholds. The BMC supports the industry-standard Intelligent Platform Management Interface (IPMI) specification, enabling you to configure, monitor, and recover systems remotely.
Additionally, the BMC can be accessed by standard, off-the-shelf terminal or terminal emulator utilities that allow access to sensor status information and power control. What’s New in BMC Management Utility 3.0 The BMC Management Utility (BMU) 3.0 has the following new features: • IPMItool command line interface available for Dell x8xx, x9xx, and xx0x systems running supported Microsoft® Windows® and Linux systems. • New commands to manage the LCD display in x9xx and xx0x systems.
• 1955 • 2800 • 2850 • 2900 • 2950 • 2970 • 6800 • 6850 • 6950 • T105 • R900 • Dell PowerVault™ NX1950 • PowerVault 100 • PowerVault 500 • PowerVault 600 NOTE: All references in this document to x9xx systems also apply to the PowerVault NX1950, PowerVault 500, and PowerVault 600 systems. All references to the PowerEdge 840 system also apply to the PowerVault 100 system.
BMC Configuration and Management Tasks The following sections document the basic tasks needed to set up and configure the BMC on a managed system in preparation for using the BMC Management Utility.
Figure 1-1.
BMC Action on Event If you plan to use your system’s BMC to perform actions when events occur, you must follow the BMC Action on Event configuration guidelines listed in Table 1-1. Table 1-1.
Table 1-2. Features BMC LAN Alerting Configuration Guidelines Connection BMC Configuration Medium Tools Platform LAN Event Alerts (SNMP Traps) Basic Configuration Management Tasks Tools • Remote Access Configuration Utility (preoperating system environment) 1 Configure NIC • Deployment Toolkit (preoperating system environment) NOTE: This option is • Server Administrator IT Assistant Selection to select Shared, Failover, or Dedicated available only on Dell PowerEdge x9xx and xx0x systems.
Table 1-3.
IPMI Shell Over the Serial Cable If you plan to use the BMC Management Utility’s IPMI Shell to access your system’s BMC over a serial cable, you must follow the BMC configuration guidelines listed in Table 1-4. NOTE: Console redirection does not apply to BMC when using the serial interface. Table 1-4.
Table 1-4.
SOL Proxy Over a LAN If you plan to use the BMC Management Utility’s SOL Proxy to access your system’s console over a LAN, you must follow the BMC configuration guidelines listed in Table 1-5. Table 1-5.
Table 1-5. BMC SOL Configuration Guidelines (continued) Features Connection BMC Configuration Basic Configuration Management Medium Tools Tasks Tools • Force a reboot on a remote system and activate console redirection • Access BMC of the remote system 4 Configure other Console Redirection parameters, such as baud rate, emulation type, and so on.
BMC Configuration and Management Tools Using the Remote Access Configuration Utility The Remote Access Configuration Utility provides basic BMC setup and configuration functions that can be accessed during system boot. Use the Remote Access Configuration Utility for initial BMC setup and configuration only. For advanced configuration tasks, you must use the Deployment Toolkit SYSCFG utility or Server Administrator Version 2.0 or later.
Using Server Administrator The Server Administrator provides a convenient and easy-to-use GUI for remotely configuring or managing your system’s BMC on a system running a supported operating system. You can use the Server Administrator to configure the most relevant BMC features, such as Platform Event Filter (PEF) parameters and alert destinations. Additionally, Server Administrator can be used as a command line interface.
• The Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide provides a complete list of all valid BMC-related command-line options, suboptions, and arguments. • The Dell OpenManage IT Assistant User’s Guide provides information about how to monitor and manage a large number of client and server systems on a local area network (LAN) or wide area network (WAN).
Introduction
Configuring Your Managed System Before using the BMC Management Utility, configure certain items, such as the necessary system BIOS, network, Intelligent Platform Management Interface (IPMI) encryption key, and serial connection settings, depending on the functionality to be performed, to enable access to the BMC. NOTE: The IPMI encryption key is a public key that is used to generate an encryption key for use between the firmware and the application.
Configuring System BIOS in Dell PowerEdge™ x8xx/x9xx Systems 1 Turn on or restart your system. 2 Press immediately after you see the following message: = Setup The System Setup screen appears. NOTE: If your operating system begins to load before you press , allow the system to finish booting, and then restart your system and try again. 3 Use the up- and down-arrow keys to navigate to the Integrated Devices field and press .
10 Use the up- and down-arrow keys to navigate to the Remote Terminal Type option and then use the space bar to select either VT 100/VT 200 or ANSI, if applicable. 11 Press to return to the System Setup screen. 12 Press to exit the System Setup program. The Exit screen displays the following options: • Save Changes and Exit • Discard Changes and Exit • Return to Setup 13 Choose the appropriate option and exit the system setup.
Off: COM1 and COM2 are both disabled and not available for use by the operating system or applications. BIOS Console redirection is disabled. NOTE: Select On with Console Redirection via COM2 to use Console Redirection with SOL. 6 Use the up- and down-arrow keys to navigate to the External Serial Communication field and press . 7 Use the spacebar to select the appropriate external serial communication option. The available options are COM1, COM2, and Remote Access. The default option is COM1.
Using BIOS Console Redirection With SOL Proxy Console redirection allows maintenance of a system from a remote location by redirecting keyboard input and output through the serial port. Any console-based feature or operating system can then be used to access the server. DR-DOS, Linux (init 3) and Windows® Special Administrative Console (SAC) are examples of operating systems and consoles that can be used to access the server.
Figure 2-1. Remote Access Configuration Utility Entering the Remote Access Configuration Utility 1 Turn on or restart your system. 2 Press when prompted after POST. If your operating system begins to load before you press , allow the system to finish booting, and then restart your system and try again. Remote Access Configuration Utility Options Table 2-1 lists the Remote Access Configuration Utility options and shows how to configure the BMC on a managed system.
Table 2-1. Remote Access Configuration Utility Option Description IPMI Over LAN Enables or disables the out-of-band LAN channel access to the shared network controller. NIC Selection Displays the configuration option. NOTE: This option is • Shared available only on Dell PowerEdge x9xx and xx0x systems. Select this option to share the network interface with the host operating system.
Table 2-1. Remote Access Configuration Utility (continued) Option Description • Dedicated Select this option to enable the remote access device to utilize the dedicated network interface available on the Remote Access Controller (RAC). This interface is not shared with the host operating system and routes the systems management traffic to a separate physical network, enabling it to be separated from the application traffic. NOTE: This option is available only on systems with a DRAC installed.
Table 2-1. Remote Access Configuration Utility (continued) Option Description Subnet Mask The subnet mask for the static IP address. NOTE: IP address 169.254.0.2 subnet mask 255.255.0.0 is returned when the BMC is unable to contact the DHCP server. Default Gateway The IP gateway for the static IP address. VLAN Enable Enables or disables the virtual LAN ID. VLAN ID This field is read-only when VLAN Enable is set to off. To enter a value, navigate to the VLAN ID field from another field.
Table 2-1. Remote Access Configuration Utility (continued) Option Description Host Name String Specifies the managed system hostname used to correlate Platform Event Traps to the system on which they originate. Use alpha-numerics, but no symbols (except ’-’) or spaces. Advanced LAN Parameters NOTE: This option is available only on systems with a DRAC installed. Dedicated NIC Configuration Options NIC Enables or disables the NIC Auto-Negotiate Enables or disables Auto-Negotiation of the LAN Speed.
Table 2-1. Remote Access Configuration Utility (continued) Option Description DNS Server 2 This field is read-only when DNS Servers from DHCP is set to on. Enter the IP Address of DNS Server 2 The following IPv4 rules apply: • IP addresses cannot be 127.xxx.xxx.xxx, where xxx is between 0-255. • The first octet must be between 1-223 (i.e. 143.xxx.xxx.xxx) • The last octet must not be 0 or 255 (i.e. xxx.xxx.xxx.0 or xxx.xxx.xxx.255) Register RAC Name on = You may enter the Current DNS RAC Name.
Table 2-1. Remote Access Configuration Utility (continued) Option Description Enter Password Enter the password for this Account User. You must enter at least one non-null character. Confirm Password Confirm the password you entered. Reset To Default Clears the BMC settings and resets the BMC setting to the defaults. NOTICE: Resetting to factory defaults will restore remote non-volatile settings. System Event Log Menu Enables viewing and clearing the System Event Log (SEL).
To use the BMC Management Utility, configure your managed system with the SYSCFG utility by performing the following tasks: • Obtain the latest version of DTK from the Dell Support website at support.dell.com. • Create a BMC configuration CD containing a bootable image, and the SYSCFG utility. • Configure BMC Users. • Configure BMC SOL access. • Configure BMC IPMI serial access.
Creating a Bootable Windows PE 2005 ISO Image NOTE: See "Creating a Bootable Windows PE 2.0 ISO Image" on page 40 for information on creating a bootable CD for Windows PE 2.0. Integration of DTK Directory Structure in the Windows PE Build This task involves a five-step process: 1 Integrating DTK tools and scripts: Copy the folder \Dell that you unzipped from the Dell-supplied zip file to DellWinPEBuild, or extract the Dell-supplied file directly into the Windows PE build.
5 Extracting the following files from your Windows Server 2003 product CD to \Dell\Toolkit\Tools: • rpcns4.dll • rpcrt4.dll • rpcss.dll NOTE: The directory name should not have any spaces. You can now customize the Windows PE according to your requirements. Creating a Bootable CD Use the following steps to create bootable media that can be used to configure the BMC on a managed system: 1 Create a directory, WinPE_OPKTools, on your hard drive.
9 Copy the SYSCFG.EXE utility to the root of the directory. 10 After you create an ISO image, you can use any CD-burning software to burn the image onto a CD. You are now ready to use your bootable CD to configure the BMC on a managed system. See the Deployment Toolkit User’s Guide for additional information. Creating a Bootable Windows PE 2.0 ISO Image If you are using Windows PE 2.0, download Windows Administrative Installation Kit (WAIK) from the Microsoft website.
Creating a Bootable CD Use the following steps to create bootable media: 1 Click Start, navigate to All Programs→ Microsoft Windows AIK. 2 Click Windows PE Tools Command Prompt to open a command prompt window. 3 Run the following command: oscdimg -n -bc:\vistaPE_x86\etfsboot.com c:\vistaPE_x86\ISO c:\vistaPE_x86\WinPE2.0.iso This command creates a CD bootable ISO image called WinPE2.0.iso. 4 You can use any CD burning software to burn the image onto a CD.
6 In /mnt/cdrom/isolinux.cfg, the cd install section points to your customized start-up script. NOTE: The scripts that you copy into the CD will be copied to and run from the RAM disk. This task is done to ensure the CD is not locked. Ensure that your sample scripts have valid path names. 7 Copy the directory structure created in your work station, into the root folder that you created in "step 4".
Configuring New BMC Users The BMC is configured by default with user ID 2 set to username: root and password: calvin. It is highly recommended that you change the user name and password when deploying your system. 1 Insert the bootable BMC configuration diskette or CD into the appropriate drive of the system to be deployed and reboot the system.
Configuring the BMC IP Address 1 Insert the Deployment Toolkit CD into the appropriate drive of the system to be deployed and reboot the system. 2 To configure the BMC IP address source for the LAN channel to DHCP, at the command prompt, type: syscfg lcp --ipaddrsrc=dhcp Press to execute the command line options. For a complete list of valid options, suboptions, and arguments for configuring the BMC LAN channel see the Deployment Toolkit Command Line Interface Reference Guide.
Configuring the BMC Serial Channel Access 1 Insert the bootable diskette or CD into the appropriate drive of the system to be deployed, and reboot the system. 2 To configure the serial port for BMC, at the command prompt, type: syscfg scp --connectionmode=basic -msgcommbitrate=XXXXX where XXXXX is the baud rate in bps. Press to execute the command line options.
When using Server Administrator, you can click Help on the global navigation bar for more detailed information about the specific window you are viewing. Server Administrator help is available for all windows accessible to the user based on user privilege level and the specific hardware and software groups that Server Administrator discovers on the managed system.
Using Dell Remote Access Controller 5 The Dell Remote Access Controller (DRAC) 5 provides a Web-based interface and RACADM (a command-line interface) that enables you to configure the DRAC 5 properties and users, perform remote management tasks, and troubleshoot a remote (managed) system for problems. Configuring the Network and IPMI LAN Settings NOTE: You must have Configure DRAC 5 permission to do the following steps.
Adding and Configuring DRAC 5 Users Create unique users with specific administrative permissions (or role-based authority) to manage your system with the DRAC 5 and maintain system security. For additional security, you can also configure alerts that are e-mailed to specific users when a specific system event occurs. NOTE: You must have Configure DRAC 5 permission to do the following steps. 1 Expand the System tree and click Remote Access. 2 Click the Configuration tab and then click Users.
Using the BMC Management Utility The BMC Management Utility is a collection of software applications that enable remote management and configuration of Dell™ systems equipped with a BMC. The BMC Management Utility includes the following components: • Command Line Interface (IPMI Shell and IPMItool) Both IPMI Shell and IPMItool are scriptable console application programs used for the control and management of remote systems using the IPMI version 1.5 and later protocol.
• Serial-Over-LAN Proxy (SOL Proxy) The SOL Proxy is a telnet daemon that allows LAN-based administration of remote systems using the Serial Over LAN (SOL) and IPMI protocols. Any standard telnet client application, such as HyperTerminal on Microsoft® Windows® or telnet on Linux, can be used to access the daemon's features. SOL can be used either in the menu mode or command mode.
In addition, to access the BMC using the IPMI serial feature, you must have a working connection between the management station and the correct serial I/O port of the managed system’s BMC using a null modem cable. Figure 3-1. Installing on a Management Station Supported Operating Systems The management station must be running one of the following supported operating systems: • Red Hat Enterprise Linux AS, ES, WS (version 4.
Installation Procedures The following installation procedures provide step-by-step instructions for installing and uninstalling the BMC Management Utility for each supported operating system: • Installing/uninstalling on systems running supported Windows operating systems • Installing/uninstalling on systems running supported Linux operating systems Installing on Systems Running Supported Windows Operating Systems To install the BMC Management Utility on a management station running the Windows operatin
8 From the drop-down menu, which appears on the left side of BMC Console, select This feature, and all subfeatures will be installed on the local hard drive. To accept the default directory path, click Next. Otherwise, click Browse and navigate to the directory where you want to install your software, and then click Next. The Ready to Install the Program screen appears. 9 Ensure that all information is correct and click Install.
Installing on Systems Running Supported Linux Enterprise Operating Systems To install the BMC Management Utility on a management station running the Linux operating system: 1 Log in as root to the system where you want to install the management station components. 2 If required, mount the Dell Systems Console and Agent CD using the command: mount /mnt/cdrom 3 Install the BMC Management Utility with the following command for SUSE Linux Enterprise server: rpm -ivh /linux/bmc/osabmcutil9g-SUSE*.
Uninstalling on Systems Running Supported Linux Enterprise Operating Systems To uninstall the BMC Management Utility, perform the following steps: 1 Log in as root. 2 Enter either of the following commands to remove all the installed packages from SUSE Linux Enterprise Server or Red Hat® Enterprise Linux®. rpm -e osabmcutil9g-SUSE* rpm -e osabmcutil9g-RHEL* If the BMC Management Utility has been uninstalled, you will receive a success message.
In addition to the operations that can be performed by a user with user-level BMC user privileges, IPMI Shell allows a user with operator-level and administrator-level BMC user privileges to: • Power on, reset, or power cycle a managed system. • Simulate a hard power off on a managed system (forcing the system to turn off without shutting down the operating system). • Clear the system event log (SEL). • Turn the blinking system identification LED on or off.
Using IPMI Shell To use IPMI Shell, perform the following steps: On systems running a supported Microsoft Windows operating system: 1 Start a Command Prompt window. 2 Locate the ipmish.exe file. By default, ipmish.exe is located in the directory: C:\Program Files\Dell\SysMgt\bmc. 3 Enter IPMI Shell commands (see "IPMI Shell Command Syntax") to manage the remote system. See "IPMI Shell Commands" for a complete list of valid options, commands, subcommands, and arguments.
Arguments with embedded tabs or spaces must be enclosed in matching double quotation marks ("). For example: -user "John Smith" Every command has one default action. The default action is typically, but not always, the equivalent of reading and displaying the current setting or status for the command.
Specifies the KG value in Hex format. The IPMI encryption key is a public key used to generate an encryption key for use between firmware and application. It is differentiated from a password, which is not public and is used to access the firmware. The maximum value is 20 ASCII hex pairs with no spaces between the pairs. NOTE: Even number of hexadecimal characters is valid and odd number of hexadecimal characters is invalid. For example, 123456AB67 is valid, and 123 is invalid. Enter 00, 0000, etc.
Options -com serial_port Specifies the serial port used when establishing an IPMI session to the managed system. For a system running Windows, the management station port can be 1, 2, 3, and so on. For systems running Linux, the management station port can be ttyS0, ttyS1, ttyS2, and so on. -baud baud_rate Specifies the communication baud rate over the serial channel.
Options -help subcommand A command list and a capsule description of options are printed if no argument is given. When there is an argument specifying a valid command, the help option displays a detailed description of the command. See Figure 3-7 and Figure 3-4. Figure 3-3.
Figure 3-4. IPMISH Help option Example 2 IPMI Session Option -interactive Synopsis ipmish -interactive [-cfg ] Description This option invokes the interactive CLI mode. An IPMISH prompt appears when entering interactive CLI mode. Type quit to exit the IPMISH prompt and return to the CLI prompt. NOTE: The command prompt responds with an error message in the interactive mode, if a command is used before establishing an IPMI session with connect.
Specifies the configuration file for BMU to start the CLI mode with. If a configuration file is not specified, BMU operates with default configuration settings. NOTE: The -interactive option must be followed by connect for ipmish to work. See "Configuring the SOL Proxy Configuration File" for more information on configuration files. Figure 3-5. IPMISH interactive option The following line edit functions are supported during the interactive session: 1 Up and Down arrow keys to browse command history.
IPMI Shell Commands Table 3-1 lists IPMI Shell commands with a brief description. NOTE: The sol, sensor, and connect commands can be used in the IPMI Shell interactive and non-interactive modes and the quit command can be used only in the interactive mode. Table 3-1. IPMI Shell Commands Command Description identify Controls the identification LED on the front panel. sysinfo Retrieves and displays managed system information. power Controls the power state of the managed system.
Subcommands on off Turns the managed system’s front panel LED on or off. If the BMC supports the IPMI extension Chassis Identify On command, then the identify on command turns the LED on indefinitely until the identify off command is used to turn the LED off. NOTE: Acknowledgement or status check of the command is not displayed on the command prompt. You should manually check the status on the system. Options -t seconds Specifies how long the LED is on. It should be no longer than 255 seconds.
Description This command retrieves and displays the system information, including field replaceable unit (FRU) and BMC information for the managed system. See Figure 3-7 and Figure 3-8. Subcommands fru — Returns FRU related information id — Returns BMC related information Default Subcommand If a subcommand is not specified, this command acts the same as sysinfo id. See Figure 3-7. Figure 3-7.
Figure 3-8. sysinfo FRU Example power Synopsis power status power off [-force] | on | cycle | reset Description This command displays the current power status of the managed system, turns the system on or off, or resets the system. See Figure 3-9. Subcommands • status — Displays the current power status of the system, the returned value is on or off. • on — Turns on the managed system. • off — Issues a "graceful shutdown" IPMI command.
• cycle — Turns off the system, pauses, then turns the system back on. • reset — Pulses the system reset signal, regardless of the power state. Options -force This option simulates pressing and holding the power button for four or more seconds. Default Subcommand If a subcommand is not specified, this command functions the same as power status. Figure 3-9.
sel clear Description This command displays the system event log information, displays the contents of the event log, and deletes all the event log records. See Figure 3-10. Subcommands • status — Displays the total number of system event log records. • get — Prints all or part of the event log. • clear — Deletes all the records in the event log. Options -begin index1 Specifies the first record to display. -end index2 Specifies the last record to display.
Figure 3-10. sel Option Example SOL Synopsis sol[enable |disable] sol config [-baud baud rate][-priv privilege level] [retry count retry_count] [retry interval retry_interval] Description This command allows you to configure sol session parameters of a remote BMC. NOTE: The command prompt responds with an error message if a command is used before establishing an IPMI session with connect. Subcommands 70 • enable — Allows you to enable SOL of connected server.
Options • -baud baud_rate Specifies the communication baud rate over the serial channel, such as 9600 or 19200. It should be in conformity with the SOL baud rate of the managed server. • -priv privilege_level Specifies minimum privilege levels required to establish an SOL session. Possible values are User, Operator, and Administrator. • -retry count retry_count Specifies number of times the BMC will retry sending SOL packages if no acknowledgement is received.
Description This command displays the current status of platform sensors using one of the two possible formats. OPTIONS [temp|fan|volt|discrete|numeric] Specifies the sensor group (temp, volt, fan, discrete, or numeric) for which information is displayed. If you do not specify a sensor group, all sensors for which there is information will be displayed. -format Use different formats to output the sensor data. Default format is oemlist.
connect Synopsis connect -ip bmc-ip-address | bmc-host-name [-u username] [-p password] [-k IPMI encryption key value] connect -com bmc_ip_address | bmc_hostname -u username -p password [-k KG value] Description This command establishes an IPMI connection with the remote server in the interactive mode to enable the user to perform server management activities. The command remains active until the user quits the command prompt or uses the command again to connect to a different server.
Figure 3-13. IPMISH connect option LCD Synopsis lcd info Description This command displays the status of the LCD display on a x9xx or xx0x system. You can also configure the LCD display using this command. Subcommands • info — Displays information about the LCD display. • set — Sets LCD display to either none, default, custom. Choose custom to set a string of your choice. • none — Turns the LCD display off. • default — Sets the default display on the LCD.
Subcommands • status — Displays the current power status of the system. The returned values denote energy consumption, peak power (in Watts), and peak amperage. • clear peakpower — Deletes the peak power value. • clear cumulativepower — Deletes the cumulative power values. Default Subcommand If a subcommand is not specified, this command functions the same as power status. quit Synopsis quit Description This command exits the IPMI Shell interactive mode and returns to the command mode.
Figure 3-14. IPMISH help option SOL Proxy SOL Proxy is a simple telnet server. It allows a telnet client to interact with the hardware-designated serial port of a remote managed system using the LAN communication channel. See Figure 3-15. With SOL Proxy, administrators can view and change the BIOS settings over a shared LAN. In addition, you can also access your managed system’s BMC using SOL Proxy using the Linux serial console and Microsoft’s EMS/SAC interfaces.
The SOL Proxy communication scheme enables you to view and configure the BIOS settings of a managed system, as well as to reset the managed system remotely using a telnet client. SOL Proxy is installed as a daemon service and automatically starts each time the system boots. SOL Proxy can accommodate only one telnet session at a time. You can use a variety of telnet clients to access SOL Proxy features. For example: • In a Windows environment, you can use a Command Prompt window as your console.
NOTE: When using HyperTerminal, you must deselect the Wrap lines that exceed terminal width check box to avoid console redirected data that may appear to be corrupted or garbled. To deselect this feature, click File→ Properties→ Settings→ ASCII Setup…→ Wrap lines that exceed terminal width. NOTE: See your system’s User’s Guide for more information about console redirection, including hardware and software requirements and instructions for configuring host and client systems to use console redirection.
Initiating the SOL Proxy session using the Windows Command Prompt: To connect and use SOL Proxy: 1 Open a Command Prompt window on your management station. 2 Enter the telnet command in the command-line and provide the IP address of the SOL Proxy server and the port number that you specified in the SOL Proxy installation (the default value is 623). For example: telnet 192.168.1.24 623 NOTE: The IP address and port number you provide should conform to the ones defined in the SOL Proxy configuration file.
Using a Linux Shell To connect and use SOL Proxy: 1 Open a Linux shell on your management station. 2 Enter the telnet command and provide the IP address of the SOL Proxy Server and the port number you specified in SOL Proxy installation. For example: telnet 192.168.1.24 623 NOTE: The IP address and port number you provide should conform to the ones defined in the SOL Proxy configuration file. For more details, see “Configuring the SOL Proxy Configuration File.
Figure 3-15. SOL Proxy Main Menu Example The SOL Proxy main menu allows you to change the SOL settings of a remote managed system’s BMC, reboot the remote BMC, or activate console redirection. When you select menu option 1, Connect to the Remote Server’s BMC, you are prompted for the BMC IP address and BMC login. After you enter the required information and make a successful connection, the internal state SLP is changed to “connected.
To exit an active SOL session, use the <~><.> character sequence. This sequence terminates SOL and returns you to the top-level menu. Connecting to the Remote Managed System’s BMC NOTE: While multiple SOL sessions can be active at the same time, only one console redirection session can be active at any given time for a managed system. 1 Select option 1 in the main menu. 2 Enter the BMC IP address of the remote managed system. 3 Provide the BMC username and password for the BMC on the managed system.
Configuring the SOL for the Remote Managed System Select option 2 in the main menu. NOTE: You must be connected to the managed system’s BMC before you can configure the SOL features. If SOL Proxy is not yet connected to the managed system’s BMC, you are prompted for an IP address, a username/password combination, and an IPMI encryption key. The IPMI encryption key value will be ignored if no key was set at the BMC on the target server.
Figure 3-18. • Configuring the Serial-Over-LAN for the Remote System, Example 2 If SOL is enabled, two BMC settings are displayed: – The communication baud-rate between the system serial port and the BMC – The minimum BMC user privilege level required for activating console redirection SOL Proxy displays a list of valid values for each feature, as well as the current value of the feature enclosed in a pair of brackets.
Figure 3-19. SOL Settings, Example 3 Activating Console Redirection Select option 3 in the main menu. NOTE: You must be connected to the managed system’s BMC before you can configure the SOL features. If SOL Proxy is not yet connected to the managed system’s BMC, you are prompted for an IP address and a username/password combination. See "Connecting to the Remote Managed System’s BMC" for more information. The remote managed system’s text console is redirected to your management station. See Figure 3-20.
Figure 3-20. Console Redirection Example Rebooting the Managed System and Activating Console Redirection Select option 4 in the main menu. NOTE: You must be connected to the managed system’s BMC before you can configure the SOL features. If SOL Proxy is not yet connected to the managed system’s BMC, you are prompted for an IP address, a username/password combination, and an IPMI encryption key. The IPMI encryption key value will be ignored if no key was set at the BMC on the target server.
While the managed system reboots, you can enter the BIOS system setup program to view or configure BIOS settings. See Figure 3-21. NOTE: Before activating the console redirection, you must first enable the console redirection features. See "Configuring Your Managed System" for more information. Figure 3-21. Reboot Example Getting Help Select option 5 in the main menu to display detailed descriptions for each option. See Figure 3-22.
Figure 3-22. Sample Help Screen Exit Select option 6 to end your telnet session and disconnect from SOL Proxy. Using SOL proxy in command mode By default, SOL Proxy is installed for use in the menu mode by the system. See "Configuring the SOL Proxy Configuration File" section for instructions on how to change the default settings to command mode. Commands in SOL Proxy SOL Proxy command mode is similar to the IPMI Shell interactive mode.
console Synopsis console Description This command allows users to establish an SOL session with the connected server. NOTE: BMU responds with an error message if console is used before establishing an IPMI session with connect. reboot Synopsis reboot[-force] Description This command allows you to control power configurations and establish an SOL session in one atomic operation. It is equivalent to executing the menu command of "Reboot and Activate Console Redirection".
Configuring the SOL Proxy Configuration File Certain parameters, for IPMI Shell and SOL Proxy, must be correctly configured in the SOL Proxy Configuration file, - SOLProxy.cfg, which is located in the default installation BMC directory. The parameters and their descriptions are as follows: Comments Any line starting with a “#” is treated as a comment. For example: #The file is an example. IP Address Specifies the specific IP address used to connect to SOL Proxy.
Power-off Timeout Specifies the time in seconds before the SOL Proxy gives up polling for the managed system's power status. If the SOL Proxy issues the power off command and the system does not power off within the specified interval, the SOL Proxy returns with a message, indicating that the SOL Proxy was unable to power off the system due to the timeout interval.
Sol Loss Silent Specifies system behavior when one or more SOL packets are lost. The possible values are 0 and 1. If it is set to 0 or is absent, the system will print an error message on the screen each time an SOL packet is lost. If it is set to 1, the system will not print error messages for loss of SOL packets. For example: sol_loss_silent=0 or 1 Sol Loss Threshold Specifies number of SOL packets that can be lost before SOL deactivation.
debug Specifies if the debug data will be logged. The default is off. debug=off IPMItool IPMItool is a CLI utility that helps in configuring and managing devices using the IPMI version 1.5 and later protocol. IPMItool supports out-of-band (OOB) access (over a LAN or through the serial port) to a single system at a time. However, multiple IPMItool sessions can run simultaneously on the same managed system. IPMItool allows a user with user-level BMC privileges to: • Display the current power status.
To facilitate command scripting, upon successful execution, IPMItool terminates with an exit code of zero, and will output the execution results in a parsable format. If an error is encountered, the program exits with a nonzero error code and outputs the error in a parsable format. See "BMC Management Utility Error Codes" for a complete list of possible BMC Management Utility error codes. The complete list of commands listed under delloem in Table 3-2 are supported by the IPMItool.
status—Displays the current power status of the system. The returned values denote energy consumption, peak power (in Watts), and peak amperage. clear peakpower—Resets the peak power value. clear cumulativepower—Resets the cumulative power values. Default Subcommand If a subcommand is not specified, this command functions the same as powermonitor status. Options for sysinfo This command returns both FRU and BMC related information for your system.
Default Subcommand If a subcommand is not specified, this command functions the same as sel info. Options for sensor • list — Displays the complete list of sensors and thresholds in a wide table format. • get ... [] — Displays information for sensors specified by ID number. • thresh — Allows you to set a particular sensor threshold value. The sensor is specified by name.
For example, to set the DNS server name to "foo": ipmitool raw 0x18 0x58 0xe4 0x15 0x66 0x6f 0x6f 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 The ASCII character conversion chart is displayed in Table 3-3: Table 3-3.
Table 3-3.
Table 3-3.
Table 3-3.
Table 3-3.
Using the BMC Management Utility
Known Issues and Frequently Asked Questions This section discusses known issues with using the BMC Management Utility, along with frequently asked questions. Known Issues General Issues • You must assign a valid BMC user name and password before you can connect to your system's BMC using the BMC Management Utility.
IPMI Shell Issues • If you type ipmish from any directory other than the directory where the BMU is installed, you will receive a "command not found" error from MS-DOS®. This is because the BMU install directory is not included in the system search path. You can execute IPMISH directly by specifying a fully-qualified path or by first navigating to the BMC directory and then executing the command. You may also manually add the BMU install directory to the execution search path.
Q: Why can’t I connect to a console using the terminal emulation software included with my Microsoft Windows® operating system? A: The version of HyperTerminal included with Windows does not provide many functions required during console redirection. Either upgrade to HyperTerminal Private Edition 6.1 or later, or select any other terminal emulation software that supports full configuration of VT100 or ANSI emulation mode. Q. What is the Spanning Tree feature? A.
Q: Why do I see a connection time-out error message when I perform the Power Reset command using the IPMISH command line tool? A: The spanning-tree feature described in the previous Q&A can cause problems during power management as well. Use the solution above to help assure that power reset and other power management commands can function without network timeouts.
BMC Management Utility Error Codes The following is a list of error messages for the BMC Management Utility. In case of a functional failure, an error message will be printed to stderr. The text of the error message is listed in the Message column in Table A-1. Errors will always be printed in a parsable format such as: Error ():! The following is an example: Error(0xC1):Invalid Command! Table A-1. BMC Management Utility Error Codes Code Classification Message A1h Connection errors.
Table A-1. BMC Management Utility Error Codes (continued) Code Classification Message Description A5h Initialization errors. Authentication failure. Request for a session from the local or remote proxy was rejected. Access denied. Trying to access the proxy from a forbidden IP address. Unknown language. Unknown language code. Invalid IP address. IP resolving error. Session buffer limit exceeded. Length exceeds the limit of telnet input. A6h A8h A7h Syntax errors. Command syntax error.
Table A-1. BMC Management Utility Error Codes (continued) Code Classification Message Description IPMI Error First index larger than The first index is larger total SEL records. than the total SEL records. A8h A9h H/W or F/W errors. Unsupported command. Unsupported operation. Sensor not present. Request sensor, data, or 0xCB record not present. Sensor command error. Command illegal for specified sensor or record type. Firmware error. Command response 0xCE could not be provided.
Table A-1. BMC Management Utility Error Codes (continued) Code Classification Message Description IPMI Error SDR busy. Sensor Data Record Repository in update mode. 0xD0 Device busy. Device in firmware update mode. 0xD1 BMC unavailable. BMC initialization in progress. 0xD2 Bad BMC state. Request not supported 0xD5 in present BMC state. BMC out of sessions. No session slots are 0x81, available for connection 0x82, request. 0x83 AEh AFh 110 Unexpected IPMI errors.
Terminal Mode Commands This appendix provides information about terminal mode commands. Terminal mode allows you to directly connect to the system's Baseboard Management Controller (BMC) using a serial port connection and execute text-based commands.
• Disable the RAC serial Console if you have a DRAC 5 installed. Login to the DRAC GUI, navigate to Serial from Remote Access, and disable Enable Serial console. • Set Serial Port 1 for PowerEdge x8xx systems. This option is available in the BIOS Setup, in the Integrated Devices menu. Using Terminal Mode Use the Terminal Mode feature to perform the following tasks: • Power the server on or off. • Reset the server. • Retrieve the server's health status.
Syntax Terminal mode messages follow the general syntax below: [] Each terminal mode message must be preceded with the left bracket "start” character and must be ended with a right bracket “stop” character and the appropriate input new-line sequence. No input characters are accepted until the start character has been received. NOTE: Hex-ASCII commands can either use upper or lower-case letters for ASCII representations of hex digits.
Hex-ASCII Command Format Binary IPMI commands are sent and received as a series of case-insensitive hex-ASCII pairs, where each is separated from the preceding pair by a single space character. Table B-1 lists the terminal mode requests to BMC and Table B-2 lists the terminal mode responses from BMC. The following is an example of a binary IPMI request message: [18 00 22] Table B-1.
Examples Hex-ASCII command example (IPMI Reset Watchdog Cmd): [18 00 22] [1C 00 22 00] Text command example: [SYS TMODE] [OK TMODE] Table B-3. Terminal Mode Text Commands Command Switches Description SYS PWD -U -U activates a terminal mode session. USERNAME USERNAME corresponds to the ASCII text for the username. represents a printable password (up to 16 characters). If is not provided, then a Null password (all binary 0’s) is submitted.
Table B-3. Terminal Mode Text Commands (continued) Command Switches Description SYS TMODE Used as a no-op confirm that Terminal Mode is active. The BMC returns an OK response followed by TMODE. SYS SET BOOT XX YY ZZ AA BB Sets the boot flags to direct a boot to the specified device following the next IPMI command or action initiated reset or power-on. XX…BB represent five hex-ASCII encoded bytes, which are the boot flags parameter in the Boot Option Parameters.
Table B-3. Terminal Mode Text Commands (continued) Command SYS GET BOOTOPT XX YY ZZ Switches Description This is a text version of the IPMI Get System Boot Options command. It allows any of the boot option parameters to be retrieved. XX YY ZZ represents the hex-ASCII for the data bytes that are passed in the Get System Boot Options request. The BMC returns the data from the command in hexASCII format. XX—Parameter selector. [7]—Reserved. [6:0]—Boot option parameter selector. YY—Set Selector.
Table B-3. Terminal Mode Text Commands (continued) Command Switches SYS SET TCFG Description Returns the Terminal Mode Configuration bytes where XX and YY represent hex-ASCII encoding for the volatile version of data bytes 1 and 2 as specified in Table B-4, and AA BB represent hex-ASCII encoding of the non-volatile version. V:XX
Table B-3. Command SYS HEALTH QUERY Terminal Mode Text Commands (continued) Switches Description Causes the BMC to return a high level version of the system health status in terse format. The BMC returns a string with the following format if the command is accepted. PWR:zzz H:xx T:xx V:xx PS:xx C:xx D:xx S:xx O:xx Where: PWR is system POWER state. H is overall Health. T is Temperature. V is Voltage. PS is Power Supply subsystem. C is cooling subsystem (Fans). D is Hard Drive/RAID Subsystem.
Table B-3. Terminal Mode Text Commands (continued) Command Switches Description SYS HEALTH QUERY -V Causes the BMC to return a high level version of the system health status in multi-line verbose format. The BMC returns a string of the following format: SYS Health:xx
Table B-3. Terminal Mode Text Commands (continued) Command Switches Description SYS IDENTIFY -ON Causes the BMC to indicate the system’s location, for example, with a blinking LED or beep for a specific period of time. XX is an optional hex-ASCII byte representing the number of seconds the BMC is to cause the system to identify itself. If XX is not provided, the BMC will indicate the system’s location only for 15 seconds. This is a text version of the optional Chassis Identify command.
Table B-4. Terminal Mode Configuration (continued) Byte Explanation 2 [7:4]—Output newline sequence (BMC to console). Selects what characters the BMC uses as the sequence when the BMC writes a line to the console in Terminal Mode. 0h = no termination sequence. 1h = (Factory default) 2h = 3h = 4h = 5h = All other = reserved [3:0]—Input newline sequence (Console to BMC).
Escape Key Sequences Console redirection uses ANSI or VT100/220 terminal emulation, which are limited to basic ASCII characters. There are no function keys, arrow keys, or control keys in this character set. However, most BIOS software requires the use of function keys and control keys for ordinary actions. Specific function keys and escape keys can be emulated by using a special key sequence, called an escape sequence, to represent a specific key.
Escape Key Sequences
Serial Port Console Redirection Serial Communication For PowerEdge x9xx and xx0x servers, serial console redirection can be accomplished using COM1 or COM2.
Serial Terminal Communication to BMC or DRAC Serial Terminal Mode allows you to directly connect to the BMC or DRAC using a serial port connection and execute text-based commands. Refer to the Appendix B for information about configuring your BMC and DRAC for Serial Terminal Communication as well as available Terminal Mode Commands.
[Data] EMSPort EMSBaudrate Where, EMSPort = Port used for serial communication. For example, COM1 or COM2. EMSBaudrate = Configured baud rate for communication. The minimum supported baud rates for supported Dell™ PowerEdge™ systems is 19200. Serial Console redirection With SOL Proxy Configuring Linux for Serial Redirection During Boot The "SysRq key" is a key sequence that allows basic commands to be passed directly to the kernel for debugging.
This sample file, using a baud rate of 19200, is an example. The following maximum baud rates are allowed for BMC serial communication and SOL: • 19200 for PowerEdge 1425SC and other PowerEdge x8xx systems. • 57600 for PowerEdge x9xx and xx0x systems without Dell Remote Access Controller 5 (DRAC 5). • 115200 for PowerEdge x9xx and xx0x systems with DRAC 5. Table D-1. Sample File: /etc/grub.con # grub.
Additional information for editing the grub.conf: 1 You may need to disable GRUB's graphical interface and use the text-based interface instead; otherwise, the GRUB screen will not be displayed in BMU console redirection. To do so, comment out the line starting with splashimage. 2 If you have multiple options in GRUB and you want all of them to start a console session through the BMU serial connection, add console= ttyS1,19200 to all options.
Table D-2. Sample File: /etc/innitab # # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg,
Table D-2. Sample File: /etc/innitab (continued) # Things to run in every runlevel. ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly.
Edit the file /etc/securetty, as follows: Add a new line, with the name of the serial tty for COM1: ttyS0 See the sample file, which shows the addition of the new line. Table D-3.
Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in your system documents. adapter card An expansion card that plugs into an expansion-card connector on the system's system board. An adapter card adds some specialized function to the system by providing an interface between the expansion bus and a peripheral device. Examples of adapter cards include network cards, sound cards, and SCSI adapters. ANSI Abbreviation for American National Standards Institute.
autoexec.bat file The autoexec.bat file is executed when you boot your system (after executing any commands in the config.sys file). This start-up file contains commands that define the characteristics of each device connected to your system, and it finds and executes programs stored in locations other than the active directory. backup A copy of a program or data file. As a precaution, you should back up your system's hard drive on a regular basis.
bootable diskette You can start your system from a diskette. To make a bootable diskette on a system running Windows, insert a diskette in the diskette drive, type sys a: at the command line prompt, and press . Use this bootable diskette if your system will not boot from the hard drive. bus An information pathway between the components of a system.
Command The combination of an option and argument or just an option if no argument is required, such as in the following command line instances: utilname --option utilname --option=argument command line instance A series of valid commands, options, and arguments typed in the command line.
conventional memory The first 640 KB of RAM. Conventional memory is found in all systems. Unless they are specially designed, programs run from the Windows Command Prompt are limited to running in conventional memory. CPU Abbreviation for central processing unit. See also microprocessor. device driver A program that allows the operating system or some other program to interface correctly with a peripheral device, such as a printer.
DRAC II Acronym for Dell OpenManage™ Remote Assistant Card, version 2. DRAC III Acronym for Dell™ Remote Access Card III. DRAC III/XT Acronym for Dell Remote Access Card III/XT. DRAC 4 Acronym for Dell Remote Access Card 4. DRAC MC Acronym for Dell Remote Access Card MC. DRAM Acronym for dynamic random-access memory. A system's RAM is usually made up entirely of DRAM chips.
ERA/MC Abbreviation for embedded remote access modular computer. See modular system. ERA/O Abbreviation for embedded remote access option. ESM Abbreviation for embedded systems management, which is a set of instruction coding in system software and firmware that notifies a user about potential hardware problems on a system. expanded memory A technique for accessing RAM above 1 MB. To enable expanded memory on your system, you must use an EMM.
flash memory A type of EEPROM chip that can be reprogrammed from a utility on diskette while still installed in a system; most EEPROM chips can only be rewritten with special programming equipment. format To prepare a hard drive or diskette for storing files. An unconditional format deletes all data stored on the disk. FRU Abbreviation for field replaceable unit, which identifies a module or component that will typically be replaced in its entirety as part of a field service repair operation.
HMA Abbreviation for high memory area. The first 64 KB of extended memory above 1 MB. A memory manager that conforms to the XMS can make the HMA a direct extension of conventional memory. Also see XMM. host adapter A host adapter implements communication between the system's bus and the controller for a peripheral device. (hard drive controller subsystems include integrated host adapter circuitry.) To add a SCSI expansion bus to your system, you must install or connect the appropriate host adapter.
IPMI Abbreviation for Intelligent Platform Management Interface, which is an industry standard for management of peripherals used in enterprise systems based on Intel® architecture. The key characteristic of IPMI is that inventory, monitoring, logging, and recovery control functions are available independent of the main processors, BIOS, and operating system. IRQ Abbreviation for interrupt request.
MB Abbreviation for megabyte(s). The term megabyte means 1,048,576 bytes; however, when referring to hard drive storage, the term is often rounded to mean 1,000,000 bytes. memory A system can contain several different forms of memory, such as RAM, ROM, and video memory. Frequently, the word memory is used as a synonym for RAM; for example, an unqualified statement such as "a system with 16 MB of memory" refers to a system with 16 MB of RAM.
NIC Acronym for network interface controller. NVRAM Acronym for nonvolatile random-access memory. Memory that does not lose its contents when you turn off your system. NVRAM is used for maintaining the date, time, and system configuration information. option An argument to a command that modifies its function rather than providing data and is usually set off by a delimiter such as - or /.
Plug and Play An industry-standard specification that makes it easier to add hardware devices to personal computers. Plug and Play provides automatic installation and configuration, compatibility with existing hardware, and dynamic support of mobile computing environments. POST Acronym for power-on self-test. Before the operating system loads when you turn on your system, the POST tests various system components such as RAM, the disk drives, and the keyboard.
read-only file A read-only file is one that you are prohibited from editing or deleting. A file can have read-only status if: • Its read-only attribute is enabled. • It resides on a physically write-protected diskette or on a diskette in a writeprotected drive. • It is located on a network in a directory to which the system administrator has assigned read-only rights to you.
server module A modular system component that functions as an individual system. To function as a system, a server module is inserted into a chassis which includes power supplies, fans, a system management module, and at least one network switch module. The power supplies, fans, system management module, and network switch module are shared resources of the server modules in the chassis. See modular system.
SPCR Abbreviation for Serial Port Console Redirection table. This table provides information about how the system firmware and service processor use the outof-band (OOB) management port. The SPCR table is read by the Special Administrative Console (SAC) for console redirection and configures itself automatically during a bootable CD installation. support commands Commands that specify how an action should be performed.
TCP/IP Abbreviation for Transmission Control Protocol/Internet Protocol. A system for transferring information over a computer network containing dissimilar systems, such as systems running Windows and UNIX. text editor An application program for editing text files consisting exclusively of ASCII characters. Windows Notepad is a text editor, for example. Most word processors use proprietary file formats containing binary characters, although some can read and write text files.
UUID Abbreviation for Universal Unique Identification. variable A component of a managed object. A temperature probe, for example, has a variable to describe its capabilities, its health or status, and certain indexes that you can use to help you in locating the right temperature probe. VESA Acronym for Video Electronics Standards Association. virtual memory A method for increasing addressable RAM by using the hard drive.
write-protected Read-only files are said to be write-protected. You can write-protect a 3.5-inch diskette by sliding its write-protect tab to the open position or by setting the write-protect feature in the System Setup program. XMM Abbreviation for extended memory manager, a utility that allows application programs and operating systems to use extended memory in accordance with the XMS. XMS Abbreviation for eXtended Memory Specification.
Glossary
Index A D ANSI, 50, 77-78, 105 delloem, 76 B baseboard management controller, 29 Baseboard Management Controller (BMC) features, 9 management activities, 9 deployment overview network-based, 22 E error codes BMC Management Utility, 107 Escape key sequences, 123 BMC, 29 BMC management tools BMC Management Utility, 9 Server Administrator, 9 standard terminal or terminal emulator utilities, 10 F BMC Management Utility, 49, 107 installation prerequisites, 50 installing, 50 IPMI Shell, 49 SOL Proxy, 50
IPMI Shell, 55 command syntax, 57 commands, 64 diagram, 56 getting help, 60 global options, 58 IPMI help option, 60 management tasks, 55 serial channel session option, 62 using, 57 IPMI Shell diagram, 56 IPMItool, 93 K known issues, 103 P planning to use a BMC BMC LAN access configuration guidelines, 16 BMC LAN alerting configuration guidelines, 14-15 BMC serial configuration guidelines, 17 BMC SOL configuration guidelines, 19 R S sensor, 71 serial redirection, red hat linux, 29 SOL, 70 SOL Proxy, 76 ac
supported terminal emulation software, 50, 77, 105 supporting documentation other dell documents you might need, 22 system setup entering, 26, 30 T telnet, 50, 76-77 terminal emulation software supported, 50, 77 terminal mode commands, 111 U using IPMI Shell, 57 using SOL Proxy, 78 V VT100, 50, 77-78, 105 Index 155
Index
