hit counter code
Dell PowerEdge 7250 User Manual
  1. Manuals
  2. Brands
  3. Dell Manuals
  4. Server
  5. PowerEdge 7250
  6. User manual
Dell PowerEdge 7250 User Manual

Dell PowerEdge 7250 User Manual

Product guide (.htm)
Hide thumbs Also See for PowerEdge 7250:
Table of Contents

Advertisement

Quick Links

Download this manual
Dell OpenManage™

Baseboard Management Controller

User's Guide
w w w . d e l l . c o m | s u p p o r t . d e l l . c o m

Advertisement

Table of Contents
loading

Related Manuals for Dell PowerEdge 7250

Summary of Contents for Dell PowerEdge 7250

  • Page 1: Baseboard Management Controller

    Dell OpenManage™ Baseboard Management Controller User’s Guide w w w . d e l l . c o m | s u p p o r t . d e l l . c o m...
  • Page 2 Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, and PowerEdge, are trademarks of Dell Inc.; Microsoft and Windows are registered trademarks of Microsoft Corporation; Red Hat is a registered trademark of Red Hat Corporation.

  • Page 3: Table Of Contents

    ..... . . Other Dell Documents You Might Need ....
  • Page 4 BMC Management Utility Installing the BMC Management Utility ....Installation Prerequisites ..... . . Supported Operating Systems .
  • Page 5 C Terminal Mode Commands Security Information ......Hex-ASCII Command Format ......Text Command Format .
  • Page 6 Figure 3-11. Connecting to the Remote System’s BMC ..Figure 3-12. Configuring the Serial-Over-LAN for the Remote System, Example 1 ... . Figure 3-13. Configuring the Serial-Over-LAN for the Remote System, Example 2 .

  • Page 7: Introduction

    Access to the Microsoft EMS/SAC and Red Hat Linux serial console interfaces by using serial over LAN (SOL). Dell provides several distinct utilities and programs for accessing the BMC to perform management activities. The following BMC interfaces allow users to configure and manage your system through the BMC.

  • Page 8: Supported System

    Supported System The BMC-management features documented in this guide are supported on the following Dell PowerEdge system: • 7250 BMC Configuration and Management Tasks This user’s guide documents the basic tasks needed to set up and configure the BMC on a managed system in preparation for using the BMC Management Utility.

  • Page 9: Bmc Configuration Matrix

    Figure 1-1. BMC Configuration Matrix Introduction...

  • Page 10: Basic Bmc Alerting Over A Shared Lan

    Basic BMC Alerting Over a Shared LAN If you plan to only use your system’s BMC functionality to monitor BMC Alerts using IT Assistant, you will need follow the BMC configuration guidelines listed in Table 1-1. Table 1-1. BMC LAN Alerting Configuration Guidelines Features Connection BMC Configuration Tools...

  • Page 11: Sol Proxy Over A Shared Lan

    Table 1-3. BMC Serial Configuration Guidelines Features Connection BMC Configuration Tools Basic Configuration Tasks BMC Management Medium Tools • SEL Access Accessed through • SMU (pre-operating system • Configure BMC user(s) • IPMI Shell the serial channel environment) (Basic Mode •...

  • Page 12: Bmc Configuration And Management Tools

    BMC Configuration and Management Tools Using the System Maintenance Utility The System Maintenance Utility is an EFI-based program that provides the ability to view or modify the systems management firmware configuration, which is maintained by the BMC. The SMU lets you: •...

  • Page 13: Using Sever Administrator

    BMC. Other Dell Documents You Might Need In addition to this User's Guide, you can find the following guides either on the Dell Support website or on the Systems Management and Documentation CD: The Dell OpenManage Software Quick Installation Guide provides additional information •...

  • Page 14: Obtaining Technical Assistance

    For more information about these help tools, see "Getting Help" in your system's Installation and Troubleshooting Guide. Additionally, Dell Enterprise Training and Certification is available; see www.dell.com/training for more information. This service may not be offered in all locations.

  • Page 15: Configuring Your Managed System

    Configuring Your Managed System In order to use the BMC Management Utility, you must first configure the necessary system BIOS, network, and serial connection settings to enable access to the BMC. In addition, to utilize the BMC Management Utility IPMI Serial functions, you must have a working connection between the management station and the correct serial I/O port of the managed system, using a null modem cable.

  • Page 16: Using The System Setup Utility

    Table 2-1. Using Setup Screens Action Left arrow Scroll left through the main menu screens Right Scroll right through the main menu screens arrow Enter Select a submenu item or accept a drop-down choice Select a field within a value (for example, date field) Select the default value Save your changes and exit Setup Go back to a previous screen...
  • Page 17 (continued) Table 2-2. Setup Console Redirection Submenu Items Submenu Item Default Value Description Flow Control No Flow Control No flow control. [CTS/RTS] CTS/RTS = Hardware-based flow control. CTS/RTS + CD CTS/RTS +CD = Hardware-based + carrier-detect flow control. When the BMC Management Utility is sharing XON/XOFF the COM port as console redirection, the flow control must be set to CTS/RTS or CTS/RTS+CD depending...

  • Page 18: Configuring Your Managed System With The System Maintenance Utility (Smu)

    Configuring Your Managed System with the System Maintenance Utility (SMU) NOTE: The SMU can be run from both the Resource CD and from the system’s utility partition (UT). See the System Software Guide on the Resource CD for instructions on running the SMU from the UT. The managed system must have a CD drive.

  • Page 19: User Configuration Subtask

    User Configuration Subtask The User Configuration subtask provides a way to configure the user access to the LAN and Serial channels. Up to four users are allowed. Some of the options presented in these screens depend on how the channels have been configured; therefore, the channels should be configured before you access these settings.

  • Page 20: Edit User Configuration Screen

    Otherwise, the firmware attempts to use the first entry in the user table that it finds that allows access to the specified channel and would expect the password associated with that entry to be the one entered to gain access to the specified channel. The figure below shows the screen that is displayed when a User Name is selected and then the Edit button is clicked.

  • Page 21: Lan Channel Configuration Subtask

    The password can be from 1 to 16 ASCII characters long. The characters accepted by the SMU for usernames are the ASCII printable characters in the range 0x21 through 0x7e, except for left and right bracket characters ('[' and ']'). These characters are reserved for framing packets for terminal mode sessions.

  • Page 22: Lan Channel Configuration Screen

    Figure 2-3. LAN Channel Configuration Screen After completing this screen, click Next to move to the next screen to continue this sub-task. Default LAN Configuration Settings Set by the SMU The SMU automatically configures some server management firmware settings. These are not displayed on the screen above, but are listed below.
  • Page 23 The meanings of the different privilege levels are described below: • Callback: Only commands needed to initiate a callback session are allowed. Although Dell OpenManage system management software does not support callback as a connection mechanism, it is still a valid privilege level because it defines a set of BMC commands that can be executed by a user.
  • Page 24 Host IP Address This edit box is for the logical or Internet address of the host. The IP address is required when DHCP is disabled. The IP address is entered as a dotted notation, such as 192.168.0.2. Subnet Mask The edit box is for the host's subnet mask. The system uses this to decide if alert destinations are in the local subnet or in another subnet relative to the client console.

  • Page 25: Serial Over Lan Configuration Subtask

    Backup Gateway MAC Address This edit box allows you to enter the MAC address of the backup gateway router. The MAC address is entered as a series of six pairs of hex digits separated by dashes, such as 00-01-62-d0-3e-66. Alphabetic hex digits (a-f) can be entered in uppercase or lowercase. This edit box is disabled by default and is only activated if the check box for Automatically resolve Backup Gateway MAC address is not checked.

  • Page 26: Serial Over Lan Configuration Screen

    Figure 2-4. Serial Over LAN Configuration Screen After configuring the SOL information, click Save to complete this subtask. Enable Serial Over LAN This check box is used to enable or disable the serial over LAN capability. SOL Privilege Level This setting is used to select the minimum BMC privilege level that is required to be able to activate SOL.

  • Page 27: Lan Alert Configuration

    Baud Rate This field sets the baud rate at which serial data is transferred by the BMC when SOL is active. The choices are Default IPMI, 9600 bps, 19.2 kbps, 38.4 kbps, 57.6 kbps, and 115.2 kbps. If Default IPMI is selected, the baud rate used is the rate currently set for BIOS serial redirection. When SOL is active, serial communication with the BMC always occurs with 8 data bits, no parity, 1 stop bit, and RTS/CTS (hardware) flow control.
  • Page 28 Click the BMC object. The BMC Information window appears. Click the Configuration tab. Under the Configuration tab, you can configure LAN, Serial Port, and Serial Over LAN. Click the Users tab. Under the Users tab, you can modify the BMC user configuration. Configuring Your Managed System...

  • Page 29: Bmc Management Utility

    BMC Management Utility The BMC Management Utility is comprised of a collection of software applications that enable remote management and configuration of systems equipped with a BMC. The BMC Management Utility includes the following components: • Command Line Interface (IPMI Shell) The IPMI Shell is a scriptable console application program for the control and management of remote systems using the IPMI 1.5 protocol.

  • Page 30: Installing The Bmc Management Utility

    Installing the BMC Management Utility The BMC Management Utility is installed on a management station system in order to remotely connect to the managed system’s BMC. See Figure 3-1. Installation Prerequisites Before using the BMC Management Utility, you must perform at least the basic BIOS and BMC configuration tasks described in "Configuring Your Managed System."...

  • Page 31: Installation

    When the installation is complete, close the installation window. See the for more information. See the Dell OpenManage™ Version 1.8.3 User's Guide for additional information about installing the BMC Management Utility on a management station. Windows Operating Systems By default, the installation program copies the files to the following directory: C:\ProgramFiles\ Dell\OpenManage\bmcconsole.

  • Page 32: Ipmi Shell

    The SOL Proxy will start automatically during system startup. Alternatively, you can go to directory /etc/init.d and use the following command to manage the SOL Proxy service: solproxy status solproxy start solproxy stop solproxy restart Uninstalling the BMC Management Utility To uninstall the BMC Management Utility, perform the following procedures: Log in as root.

  • Page 33: Ipmi Shell Diagram

    In addition to the operations that can be performed by a user with operator-level BMC user privileges, IPMI Shell allows a user with administrator-level BMC user privileges to: • Set and change user privileges. To facilitate command scripting, upon successful execution IPMI Shell terminates with an exit code of zero, and will output the execution results in a parsable format.

  • Page 34: Using Ipmi Shell

    Start a Command Prompt window. Go to the directory where the file ipmish.exe is located. By default, ipmish.exe is located at the directory: C:\ProgramFiles\ Dell\OpenManage\bmcconsole. Enter IPMI Shell commands (see "IPMI Shell Command Syntax") to manage the remote system. Go to "IPMI Shell Commands" for a complete list of valid options, commands, subcommands, and arguments.

  • Page 35: Ipmi Shell Global Options

    IPMI Shell Global Options IPMI Shell has the following global options: IPMI Session Option -ip Synopsis ipmish -ip bmc_ip_address | bmc_hostname -u username -p password Description This option is used to establish a connection to a remote managed system using the LAN channel. The IP port specified in installation (default value is 623) is used unless another port has been configured.

  • Page 36: Help Command

    Options NOTE: The following options cannot be used independently. One or more IPMISH command must follow the option. -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 Red Hat Linux, the management station port can be ttyS0, ttyS1, ttyS2, and so on.

  • Page 37: Ipmi Help Option Example

    Figure 3-3. IPMI Help Option Example 1 BMC Management Utility...

  • Page 38: Ipmi Shell Commands

    Figure 3-4. IPMI Help Option Example 2 IPMI Shell Commands The table below lists IPMI Shell commands with a brief description. 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.

  • Page 39: Identify Option Example

    Subcommands 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. Otherwise, the LED will be turned on for the maximum allowed time of 255 seconds.

  • Page 40: Sysinfo Option Example

    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-6. Figure 3-6. sysinfo Option Example power Synopsis power status power off [-force] | on | cycle | reset Description This command is used to display the current power status of the managed system, turn the system...

  • Page 41: Power Option Example

    — Issues a “graceful shutdown” IPMI command. NOTE: The off subcommand is not supported on the PowerEdge 7250. You must use the force option to turn off the system. cycle — Turns off the system, pauses, then turns the system back on.
  • Page 42 Synopsis sel status sel get [ [-begin index1 ] [-end index2 | -max count] ] | [-last n] sel clear Description This command is used to display event log information, display the contents of the event log, and delete all the event log records. See Figure 3-8. Subcommands status —...

  • Page 43: Sol Proxy

    Figure 3-8. sel Option Example 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-9. With SOL Proxy, administrators can view and change the BIOS settings over a shared LAN.

  • Page 44: Sol Proxy Diagram

    Figure 3-9. SOL Proxy Diagram The SOL Proxy communication scheme enables the viewing and configuration of the BIOS settings of a managed system, as well as resetting the managed system remotely using a telnet client. SOL Proxy is installed as a daemon service and automatically starts each time the system boots.

  • Page 45: Using Sol Proxy

    NOTE: When using HyperTerminal, uncheck the Wrap lines that exceed terminal width check box to avoid console redirected data that may appear to be corrupted or garbled. To uncheck this → → → → feature, click File Properties Settings ASCII Setup… Wrap lines that exceed terminal width.
  • Page 46 Using Windows HyperTerminal Console To connect and use SOL Proxy: Open a HyperTerminal session on your management station. Create a new TCP/IP connection, providing the IP address of SOL Proxy Server and the port number you have specified in SOL Proxy installation (the default value is 623). The Emulation mode is VT100 and ANSI.

  • Page 47: Sol Proxy Main Menu Example

    After authentication is performed, you will see a login successful message and the SOL Proxy main menu prompt. You are ready to use SOL Proxy. See "SOL Proxy Main Menu" for further instructions. SOL Proxy Main Menu After the telnet connection with SOL Proxy is successfully established, you are presented with the following menu of choices.
  • Page 48 Menu option 2 allows you to enable, disable, and configure the SOL defaults, including the minimum user privilege level required for activating SOL and the communication baud-rate. Menu options 3 and 4 allow you to establish a SOL remote console session through the SOL Proxy main menu.
  • Page 49 Figure 3-11. Connecting to the Remote System’s BMC 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 and a username/password combination.

  • Page 50: Configuring The Serial-Over-Lan For The Remote System, Example 1

    Figure 3-12. Configuring the Serial-Over-LAN for the Remote System, Example 1 • If SOL is currently disabled, the options shown in Figure 3-13 are displayed. Type Y to enable SOL or N to keep SOL disabled. See Figure 3-13. BMC Management Utility...

  • Page 51: Configuring The Serial-Over-Lan For The Remote System, Example 2

    Figure 3-13. 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.

  • Page 52: Configuring The Serial-Over-Lan For The Remote System, Example 3

    Figure 3-14. Configuring the Serial-Over-LAN for the Remote System, 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.
  • Page 53 Figure 3-15. 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 and a username/password combination.
  • Page 54 Figure 3-16. Reboot Example Getting Help Select option 5 in the main menu to display detailed descriptions for each option. See Figure 3-17. BMC Management Utility...

  • Page 55: Configuring Sol Proxy With The Sol Proxy Configuration File

    Figure 3-17. Sample Help Screen Exit Select option 6 to end your telnet session and disconnect from SOL Proxy. Configuring SOL Proxy with the SOL Proxy Configuration File SOL Proxy must be correctly configured and running before establishing telnet connection. There are certain SOL parameters that the user can set by modifying the solproxy.cfg file.
  • Page 56 IP address ip — specifies the specific IP address used to connect to the SOL Proxy. This item defines what kind of connection can be accepted to establish a SOL Proxy telnet session. There are three possible values: • INADDR_ANY — SOL Proxy accepts the telnet request to any system. •...
  • Page 57 Retry Interval retry_interval — specifies the period of time in seconds that the BMC waits before it retries sending a packet. The retry_interval unit is half a second. Therefore, a value of 2 means that the software waits one second for the BMC to respond before it tries to resend the packet, a value of 4 means that it waits two seconds, and so on.
  • Page 58 BMC Management Utility...

  • Page 59: Known Issues And Frequently Asked Questions

    Known Issues and Frequently Asked Questions Q: Do IPMI Shell commands correspond one-to-one to IPMI commands? A: IPMI Shell provides only the most useful IPMI commands. It includes a definitive set of commands that can be used to accomplish the most common management tasks. Therefore, IPMI Shell commands may not correspond one-to-one to IPMI commands.
  • Page 60 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 VT100 or ANSI emulation mode.

  • Page 61: Bmc Management Utility Error Codes

    BMC Management Utility Error Codes 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.
  • Page 62 (continued) Table A-1. BMC Management Utility Error Codes Code Classification Message Description IPMI Error Invalid IP address. IP resolving error. Session buffer limit Length exceeds the limit exceeded. of telnet input. Syntax errors. Command syntax error. Unable to parse command. Unrecognized command.
  • Page 63 (continued) Table A-1. BMC Management Utility Error Codes Code Classification Message Description IPMI Error Destination error. Cannot deliver request to 0xD3 destination. Device error. Device specific (OEM) 0x01–0x7E errors. Processing errors BMC busy. BMC out of processing 0xC0 (transient errors resources.
  • Page 64 BMC Management Utility Error Codes...

  • Page 65: B Using Console Redirection

    Using Console Redirection Console redirection allows you to manage a host (local) system from a client (remote) system by redirecting keyboard input and text output through a serial port. You cannot redirect graphic output. You can use console redirection for tasks such as configuring BIOS settings. You can also connect the client system to a port concentrator that can access numerous host systems using a shared modem.

  • Page 66: Configuring The Client System

    Configuring the Client System After configuring the host system, configure the ports and terminal settings for the client (remote) system. NOTE: The examples in this section assume that you have upgraded to Hilgraeve's HyperTerminal Private Edition 6.1 or later. If you are using other terminal emulation software, see the documentation for that software.

  • Page 67: Managing The Host System Remotely

    Managing the Host System Remotely After you configure the host and client systems (see "Configuring the Host System" and "Configuring the Client System"), you can use console redirection to restart a host system or to change a host system's configuration settings. Reboot the host system using the client system.
  • Page 68 (continued) Table B-1. Supported Escape Sequences Key(s) Supported Sequence Terminal Emulation <F1> <Esc><O><P> VT 100/220, ANSI <F2> <Esc><O><Q> VT 100/220, ANSI <F3> <Esc><O><R> VT 100/220, ANSI <F4> <Esc><O><S> VT 100/220, ANSI <F5> <Esc><O><T> VT 100, ANSI <F6> <Esc><O><U> VT 100, ANSI <Esc><[><1><7><~>...

  • Page 69: Table B-2. Additional Escape Sequences

    (continued) Table B-1. Supported Escape Sequences Key(s) Supported Sequence Terminal Emulation <Shift><Tab> <Esc><[><Z> VT 100 <Esc><[><0><Z> VT 220 <Esc><[><Shift><z> ANSI After creating macros for the keys listed in Table B-1, press <F1> on the client system's keyboard during terminal emulation to send the escape sequence <Esc><O><P> to the host system. The host system then interprets the sequence as <F1>.
  • Page 70 Using Console Redirection...

  • Page 71: Security Information

    Terminal Mode Commands Terminal mode allows you to directly interface to the server's Baseboard Management Controller (BMC) using a serial port connection and execute text-based commands. Two types of text commands are supported: • A limited selection of text commands •...

  • Page 72: Hex-Ascii Command Format

    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. Terminal mode text commands are case sensitive, but hex-ASCII commands can either use upper or lower case letters for ASCII representations of hex digits.

  • Page 73: Text Command Format

    The software ID and LUN for the remote console are fixed and implied by the command. The SWID for messages to the remote console is always 47h, and the Logical Unit Number (LUN) is 00b. Instead, there is a "bridge" field that is used to identify whether the message should be routed to the BMC’s bridged message tracking or not.

  • Page 74: Terminal Mode Ipmi Message Bridging

    Text command example: [SYS TMODE]<CR> [OK TMODE]<CR-LF> Terminal Mode IPMI Message Bridging Terminal mode supports the ability to bridge IPMI messages to another interface when binary hex-ASCII IPMI commands are used. The message bridge is determined by the following: the bridge field, whether the message is a request or a response, the message direction with respect to the BMC and the LUN.

  • Page 75: Table C-4. Terminal Mode Text Commands

    Table C-4. Terminal Mode Text Commands Command Switches Description SYS PWD -U USERNAME Used to activate a terminal mode session. USERNAME <password> corresponds to the ASCII text for the username. <password> represents a printable password (up to 16 characters). If <password>...
  • Page 76 (continued) Table C-4. Terminal Mode Text Commands Command Switches Description SYS SET This is essentially a text version of the IPMI Set System Boot Options command. It allows any of the boot option parameters to BOOTOPT XX YY…NN be set, not just the boot flags. XX YY…NN represent the hex- ASCII encoding for the data bytes that are passed in the Set System Boot Options request.
  • Page 77 (continued) Table C-4. Terminal Mode Text Commands Command Switches Description SYS SET TCFG 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 C-6, and AA BB represent hex-ASCII encoding of the non-volatile version.
  • Page 78 (continued) Table C-4. Terminal Mode Text Commands Command Switches Description SYS HEALTH Causes the BMC to return a high level version of the system health QUERY 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.

  • Page 79: Boot Option Parameters

    (continued) Table C-4. Terminal Mode Text Commands Command Switches Description SYS HEALTH Causes the BMC to return a high level version of the system health QUERY status in multi-line "verbose" format. The BMC returns a string of the following format: SYS Health:xx<output termination sequence>.

  • Page 80: Table C-5. Boot Option Parameters

    Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Set In Progress Data 1 - This parameter is used to indicate when any of the following parameters are being updated, and when the updates are (volatile) completed.
  • Page 81 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) BMC boot flag Data 1 - BMC boot flag valid bit clearing. Default = 0000b. valid bit clearing [7:5] - Reserved. (semi-volatile) [4] - 1b = Do not clear valid bit on reset/power cycle caused by PEF.
  • Page 82 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Boot info These flags are used to allow individual parties to track whether acknowledge they have already seen and handled the boot information. Applications that deal with boot information should check the (semi-volatile) boot info and clear their corresponding bit after consuming the boot options data.
  • Page 83 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Boot flags Data 1 (semi-volatile) [7] - 1b = Boot flags valid. The bit should be set to indicate that valid flag data is present. This bit may be automatically cleared based on the boot flag valid bit clearing parameter.
  • Page 84 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Boot flags Data 3 (semi-volatile) [7] - 1b = Lock out (power off/ sleep request) using the Power (continued) Button. [6:5] - Firmware (BIOS) Verbosity (Directs what appears on POST display).
  • Page 85 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Boot flags Data 4 (semi-volatile) [7:4] - Reserved. (continued) [3] - BIOS Shared Mode Override. Can be used to request BIOS to temporarily place the channel into shared access mode.
  • Page 86 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Boot initiator info Address and Identity information for the party that initiated the (semi-volatile) boot. The party that initiates the boot writes this parameter and the boot info acknowledge parameter prior to issuing the command that causes the system power up, power cycle, or reset.
  • Page 87 (continued) Table C-5. Boot Option Parameters Parameter Number Parameter Data (non-volatile unless otherwise noted) Boot initiator This parameter is used as a "mailbox" for holding information that mailbox directs the operation of the operating system loader or service partition software. (semi-volatile) NOTE: Since this information is retained by the BMC and may be...

  • Page 88: Table C-6. Terminal Mode Configuration

    Table C-6. Terminal Mode Configuration Byte Explanation [7:6] - Reserved . [5]—Line Editing. 0b = Disable. 1b = Enable (Factory default). [4]—Reserved. [3:2]—Delete control (only applies when line editing is enabled). 00b = BMC outputs a <DEL> character when <BKSP> or < DEL > is received. 01b = BMC outputs a <...
  • Page 89 Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in your system documents. adapter card asset tag code An expansion card that plugs into an expansion-card An individual code assigned to a system, usually by a connector on the system's system board.
  • Page 90 BIOS byte Acronym for basic input/output system. Your system's Eight contiguous bits of information, the basic data BIOS contains programs stored on a flash memory chip. unit used by your system. The BIOS controls the following: cache • Communications between the microprocessor and A fast storage area that keeps a copy of data or peripheral devices, such as the keyboard and the instructions for quicker data retrieval.
  • Page 91 The device names for the first through fourth serial Abbreviation for central processing unit. See also ports on your system are COM1, COM2, COM3, and microprocessor. COM4. The default interrupt for COM1 and COM3 is IRQ4, and the default interrupt for COM2 and device driver COM4 is IRQ3.
  • Page 92 Acronym for Dell™ OpenManage Remote Assistant Acronym for erasable programmable read-only Card, version 2. memory. DRAC III Acronym for Dell Remote Access Card III. Abbreviation for embedded remote access. DRAC III/XT ERA/MC Acronym for Dell Remote Access Card III/XT. Abbreviation for embedded remote access modular computer.
  • Page 93 FAT file system. The operating system maintains a table to keep track of the status of various segments Abbreviation for gigabyte(s). A gigabyte equals of disk space used for file storage. 1024 megabytes or 1,073,741,824 bytes. FAT32 — A derivative of the FAT file system. •...
  • Page 94 integrated host adapter circuitry.) To add a SCSI includes a 16-KB internal cache, which is set up as an expansion bus to your system, you must install or 8-KB read-only instruction cache and an 8-KB connect the appropriate host adapter. read/write data cache.
  • Page 95 local bus On a system with local-bus expansion capability, Abbreviation for megahertz. certain peripheral devices (such as the video adapter circuitry) can be designed to run much faster than they microprocessor would with a traditional expansion bus. Some local-bus The primary computational chip inside the system that designs allow peripherals to run at the same speed and controls the interpretation and execution of arithmetic with the same width data path as the system's...
  • Page 96 NVRAM Plug and Play Acronym for nonvolatile random-access memory. An industry-standard specification that makes it easier Memory that does not lose its contents when you turn to add hardware devices to personal computers. Plug off your system. NVRAM is used for maintaining the and Play provides automatic installation and date, time, and system configuration information.
  • Page 97 RAM disk SCSI A memory-resident program that emulates a hard Acronym for small computer system interface. An I/O drive. bus interface with faster data transmission rates than standard ports. You can connect up to seven devices (15 for some newer SCSI types) to one SCSI interface. read-only file A read-only file is one that you are prohibited from server module...
  • Page 98 managed system or about potential hardware file to determine a variety of options for the Windows problems. operating environment. Among other things, the system.ini file records which video, mouse, and keyboard drivers are installed for Windows. Abbreviation for Serial Over LAN. SOL enables Running the Control Panel or Windows Setup program suitably designed servers to transparently redirect the may change options in the system.ini file.
  • Page 99 the upper memory area, in which you can load device drive, the operating system would manage the system drivers and memory-resident programs. as though it had 32 MB of physical RAM. VT-100 Abbreviation for Uniform Resource Locator (formerly Abbreviation for Video Terminal 100, which is used by Universal Resource Locator).
  • Page 100 Abbreviation for eXtended Memory Specification. X Windows system The graphical user interface used in the Red Hat Linux environment. Glossary...
  • Page 101 Index BMC Management Utility, 27, 59 ANSI, 15, 27, 42-43, 57-58 error codes Installation, 29 BMC Management Utility, 59 installation prerequisites, 28 installing, 28 IPMI Shell, 27 SOL Proxy, 27 Baseboard Management Controller (BMC) supported operating FAQ, 57 systems, 28 features, 5 frequently asked management activities, 5...
  • Page 102 IPMI Shell, 30 supporting documentation command syntax, 32 other documents you might serial port, 15 need, 11 commands, 36 Server Administrator diagram, 31 System Maintenance Utility configuring your managed getting help, 34 (SMU) system, 25 global options, 33 configuring your managed IPMI help option, 34 SOL Proxy, 41 system, 16...

Table of Contents