Dell OpenManage Baseboard Management Controller User Manual

Download

Dell OpenManage Baseboard

Management Controller

Utilities 4.3

User’s Guide

Notes and Cautions

NOTE: A NOTE indicates important information that helps you make better use of

your computer.

CAUTION: A CAUTION indicates potential damage to hardware or loss of data if

instructions are not followed.

____________________

Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell™, the DELL™ logo, OpenManage™, PowerVault™, PowerConnect™, and PowerEdge™ are trademarks of Dell Inc. Microsoft

Server

, and MS-DOS® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat trademarks of Red Hat, Inc. in the United States and/or other countries. SUSE™ is a registered trademark of Novell, Inc. Intel countries. UNIX

Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

is a registered trademark of The Open Group.

is a registered trademark of Intel Corporation in the U.S. and other

and Red Hat Enterprise Linux® are registered

, Windows®, Windows

July 2010

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 9

Supported Systems and Operating Systems. . . . . . . 10

BMC Configuration and Management Tasks . . . . . . 10

Configuring the BMC

. . . . . . . . . . . . . . . . 10

Managing the System Using BMC . . . . . . . . . 11

BMC Action on Event

Basic BMC Alerting Over a LAN

. . . . . . . . . . . . . . . . 13

. . . . . . . . . . 13

IPMI Shell Over a LAN . . . . . . . . . . . . . . . 14

IPMI Shell Over the Serial Cable

SOL Proxy Over a LAN

. . . . . . . . . . . . . . . 18

. . . . . . . . . . 16

BMC Configuration and Management Tools

. . . . . . 20

Using the Remote Access Configuration Utility

in x9xx systems

. . . . . . . . . . . . . . . . . . . 20

Using Deployment Toolkit. . . . . . . . . . . . . . 20

Using the BMC Management Utility

Using Server Administrator

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. The BMC provides the following features:

• Access through the system’s serial port and integrated NIC

• Fault logging and SNMP alerting

• Access to the system event log (SEL) and sensor status

• Control of system functions including power on and power off

• Support that is independent of the system’s power or operating state

• Text console redirection for system setup, text-based utilities, and operating system consoles

• Access to Linux Enterprise server 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 you to configure and manage your system through the BMC:

• The BMC Management Utility allows remote, out-of-band LAN and/or serial port power control, event log access, and console redirection.

• The Remote Access Configuration Utility in configuring BMC in a pre-operating system environment.

• The Dell OpenManage Deployment Toolkit SYSCFG utility provides a powerful command line configuration tool.

• Dell OpenManage Server Administrator allows remote, in-band access to event logs, power control, and sensor status information and provides the ability to configure the BMC.

• Command Line Interface (CLI) tools provide a command line tool for sensor status information, System Event Log (SEL) access, and power control.

x9xx

systems enables

Introduction 9

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.

Supported Systems and Operating Systems

BMC Management Utility supports new Dell systems running supported Microsoft Windows and Linux systems by implementing the new IPMItool commands to monitor your system’s power, view, and set the LCD status.

For the complete list of supported systems and operating systems, see the

readme.txt file in the root installation folder, or the Dell Systems Software Support Matrix available on the Dell Support website at

support.dell.com/manuals.

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.

NOTE: The new power monitoring features are not supported on IPMIsh and

SOLProxy.

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. These basic tasks are:

•Configuring the BMC

•Managing the BMC

Configuring the BMC

To configure the BMC on a managed system in a pre-boot environment, you can use:

• Dell Deployment Toolkit (DTK)

• Remote Access Configuration Utility in

NOTE: The Remote Access Configuration Utility is called the BMC Setup Module in

Dell PowerEdge x8xx systems, iDRAC Configuration Utility in xx0x systems, and iDRAC6 Configuration Utility in xx1x systems.

10 Introduction

x9xx

systems

• Dell Remote Access Controller (DRAC) 5 graphical user interface (GUI)

• iDRAC6 Enterprise graphical user interface (GUI)

• Command Line Interface (CLI)

from a management station depending on the scope of your required configuration tasks. Alternately, you can configure the BMC on a managed system with a running operating system using the Server Administrator home page GUI or CLI. See "Baseboard Management Controller Configuration" on page 31 for more information.

Managing the System Using BMC

To manage the BMC in a pre-boot environment, or to access the BMC of a system, you can use the BMC Management Utility. See "Using the BMC Management Utility" on page 51. To configure the BMC on a system with a running operating system or to perform everyday BMC management tasks, you can use the GUI on the Server Administrator home page. See the Server Administrator User’s Guide for more information about using Server Administrator to manage your system’s BMC functions. Figure 1-1 shows the configuration matrix for BMC.

Introduction 11

Figure 1-1. BMC Configuration Matrix

12 Introduction

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 Ta b l e 1 - 1 .

Table 1-1. BMC Action on Event Configuration Guidelines

Features Connection

Medium

•System

Reset

•System

Power Off

•System

Power Cycle

LAN

BMC Configuration Tools

• Deployment Toolkit (pre-operating system environment)

• Server Administrator

Basic Configuration Ta sk s

•Enable platform events

•Enable alert actions

Management Tools

Basic BMC Alerting Over a LAN

If you plan to use your system’s BMC to send alerts (Platform Event Traps), you must follow the BMC configuration guidelines listed in Table 1-2.

NOTE: The LAN-sharing depends on the NIC selection configuration option.

The available options are Shared and Failover. If you are using iDRAC6 Enterprise, the additional option available is Dedicated. See the NIC Selection option in the table in "Remote Access Configuration Utility Options" on page 32 for more information on Shared, Failover, and Dedicated.

Introduction 13

Table 1-2. BMC LAN Alerting Configuration Guidelines

Features Connection

Medium

Platform Event Alerts (SNMP Tr a ps )

LAN

BMC Configuration Tools

•Remote Access Configuration

x9xx

Utility in systems (pre-operating system environment)

•Deployment To ol k i t (pre-operating system environment)

•Server Administrator

Basic Configuration Tas ks

Configure NIC Selection to select Shared, Failover, or Dedicated

NOTE: This option is

available only on Dell PowerEdge

x9xx, xx0x, and xx1x

systems.

Configure the IP address, Subnet mask, and Gateway on the managed system

Configure the VLAN (optional)

Enable alerting

Configure the Alert destination IP address

Configure the Host Name (optional)

Management Tools

IT Assistant

IPMI Shell Over a LAN

Table 1-3 lists the actions you can perform, if you plan to use the BMC Management Utility’s IPMI Shell or IPMItool to access your system’s BMC over a LAN.

14 Introduction

Table 1-3. BMC LAN Access Configuration Guidelines

Features Connection

Medium

• Remote SEL

LAN

access

•Power control

•System identification

•Sensor information

BMC Configuration Tools

• Remote Access Configuration

x9xx

Utility in systems (pre-operating system environment)

• Deployment Toolkit (pre-operating system environment)

•Server Administrator

Basic Configuration Tas ks

Enable IPMI over LAN on the managed system

Configure NIC selection to select Shared, Failover, or Dedicated

NOTE: This

option is available only on Dell PowerEdge

x9xx, xx0x, and xx1x systems.

Configure the IP address, Subnet mask, and Gateway on the managed system

Configure IPMI encryption key (optional)

NOTE: This

option is available only on Dell PowerEdge

x9xx, xx0x, and xx1x systems.

Configure VLAN (optional)

Configure BMC users

Management Tools

IPMI Shell

Introduction 15

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. BMC Serial Configuration Guidelines

Features Connection

Medium

•Interactive mode

•Remote SEL access

•Power control

•System identification

•System information

•Access the BMC of the remote system

Accessed through the serial channel by using a null modem cable

BMC Configuration Tools

•BIOS (pre-operating system environment)

• Deployment To ol k i t (pre-operating system environment)

•Server Administrator (to enable BMC serial only)

Basic Configuration Ta sk s

Configure Serial Port 1 to BMC Serial

NOTE: This

option is available only on Dell PowerEdge

x8xx systems.

Configure External Serial Connector to Remote Access

NOTE: This

option is available only on Dell PowerEdge

x9xx, xx0x, and xx1x systems.

Management Tools

• IPMI Shell (Basic mode)

•Terminal emulation (Terminal mode only)

16 Introduction

Table 1-4. BMC Serial Configuration Guidelines

(continued)

Features Connection

Medium

•System information

•Access the BMC of the remote system

BMC Configuration Too ls

Basic Configuration Tas ks

Set Serial baud rate to match the rate to be used by the management tool

Set BMC Serial Connection Mode to Basic for IPMI Shell or Terminal for Te rm i n al emulation

Configure BMC users

Management Too ls

Introduction 17

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. BMC SOL Configuration Guidelines

Features Connection

Medium

• Text Utility console redirection

•Remote BIOS setup

•Microsoft text console redirection

•Linux text console redirection

LAN

BMC Configuration Tools

•BIOS (pre-operating system environment)

• Remote Access Configuration

x9xx

Utility in systems (pre-operating system environment)

•Deployment Toolkit (pre-operating system environment)

•Server Administrator

Basic Configuration Tas ks

Configure Serial Port 1 to BMC NIC

NOTE: This

option is available only on Dell

PowerEdge x8xx

systems.

Configure BIOS console redirection to Serial Port 1.

NOTE: This option

is available only on Dell

PowerEdge x9xx

systems.

Configure Console Redirection to On with Console Redirection via COM2

NOTE: This option

is available only on Dell

PowerEdge x9xx, xx0x, and xx1x

systems.

Management Too ls

•SOL Proxy

•IPMI Shell

18 Introduction

Table 1-5. BMC SOL Configuration Guidelines

(continued)

Features Connection

Medium

•Force a reboot on a remote system and activate console redirection

•Access BMC of the remote system

BMC Configuration Tools

Basic Configuration Ta sk s

Configure other Console Redirection parameters, such as baud rate, emulation type, and so on.

Enable IPMI over LAN on the managed system

Configure the IP address, Subnet mask, and Gateway on the managed system

Configure IPMI encryption key (optional)

NOTE: This

option is available only on Dell

PowerEdge x9xx, xx0x, and xx1x

systems.

Configure VLAN (optional)

Configure BMC users

Management Tools

Introduction 19

BMC Configuration and Management Tools

Using the Remote Access Configuration Utility in

The Remote Access Configuration Utility in x9xx systems provides basic BMC setup and configuration functions that can be accessed during system boot. Use the 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.

NOTE: The Remote Access Configuration Utility is called the BMC Setup Module in

Dell PowerEdge x8xx systems, iDRAC Configuration Utility in xx0x systems, and iDRAC6 Configuration Utility in xx1x systems.

x9xx

systems

Using Deployment Toolkit

The Deployment Toolkit (DTK) SYSCFG utility provides a powerful Microsoft Windows Preinstallation Environment (PE) and Linux command an initial deployment. Use the DTK SYSCFG utility to set all supported BMC features. Additionally, you can use the Deployment Toolkit utilities to capture and replicate system settings on similar systems. See "Configuring Your BMC Using the Deployment Toolkit Utility" on page 40 for more information on how to install and set up the DTK SYSCFG utility.

-line interface for locally configuring your system’s BMC as part of

Using the BMC Management Utility

The BMC Management Utility provides a command-line interface to your remote management station to manage BMC-supported functions. Use the BMC Management Utility to manage your BMC from a remote management station and as your managed system’s emergency management console. The utility gives you the option of using either a command line interface (IPMI Shell) or a SOL Proxy to access and manage the BMC. To use the BMC Management Utility, you must perform the following tasks:

• Configure BMC using the Remote Access Configuration Utility in systems, the DTK SYSCFG utility, or Server Administrator.

• Install the BMC Management Utility on a management station.

See "Configuring Your Managed System" on page 25 for instructions on configuring the BMC on a managed system in preparation for using the BMC Management Utility.

x9xx

20 Introduction

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. Server Administrator requires that the system has an operating system installed and functioning. As a result, Server Administrator is best suited for everyday BMC management tasks, and is not an option for performing pre-boot setup or accessing the BMC as an emergency management console. To use Server Administrator, you must perform the following tasks:

• Install Server Administrator on the managed system.

• Access the Server Administrator home page remotely or locally from a supported browser on a management station.

• Configure BMC remotely or locally on the managed system.

See the Dell OpenManage Server Administrator User’s Guide and Command line Interface User’s Guide on the Dell Support website at support.dell.com/manuals for more information about using Server Administrator to configure and manage your system BMC.

Obtaining Technical Assistance

If at any time you do not understand a procedure described in this guide or if your product does not perform as expected, help tools are available to assist you. For more information about these help tools, see "Getting Help" in your system's Installation and Troubleshooting Guide or the Hardware Owner’s Manual.

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.

Introduction 23

24 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.

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 target BMC, using a null modem cable.

This section describes the basic procedures you must perform to prepare your BMC to be accessed and managed using the BMC Management Utility. The following procedures are described:

• BIOS Configuration

• Baseboard Management Controller Configuration

• Configuring your BMC with the Dell OpenManage Deployment ToolKit (DTK) SYSCFG utility

• Configuring your BMC with Dell OpenManage Server Administrator

BIOS Configuration

For most configurations, you must configure the serial port settings and the console redirection settings in your system BIOS before you can use the BMC Management Utility. To configure the necessary system BIOS setting, your must enter the System Setup Program. The BIOS settings can also be configured using the Deployment Toolkit or the

NOTE: For more information about configuring BIOS settings, see your system

User’s Guide.

Configuring Your Managed System 25

Server Administrator.

Configuring System BIOS in Dell PowerEdge x8

Turn on or restart your system.

Press <F2> immediately after you see the following message:

xx/x9xx

<F2> = Setup

The

System Setup

NOTE: If the operating system begins to load before you press <F2>,

allow your system to boot, and then restart your system, and try again.

Use the up- and down- arrow keys to navigate to the

screen appears.

field and press <Enter>.

Use the up- and down- arrow keys to navigate to the press <Enter>.

Use the space bar to select the serial port option.

The options are

COM1, COM3, BMC Serial, BMC NIC, Off

(if an optional RAC is installed in the system).

Systems

Integrated Devices

Serial Port 1

field and

, and

RAC

To use BMC, serial port 1 uses the

COM1

address and communication can be through the serial port or the integrated shared NIC. RAC control uses only the

COM1

address.

Off

and

COM3

are not available options

when Console Redirection is set to use serial port 1.

Select

BMC Serial

if you are planning to access the BMC through the

serial cable connection.

Select

BMC NIC

if you are using SOL proxy and are planning to

access the BMC over a shared LAN.

Press <Enter> to return to the

Use the up- and down- arrow keys to navigate to the

System Setup

screen.

Console Redirection

field and press <Enter>.

Use the up- and down- arrow keys to navigate to the

Console Redirection

option and then use the space bar to set the console redirection feature to

Serial Port 1

Use the up- and down- arrow keys to navigate to the

. Optionally, you can also enable

Redirection after Boot.

Failsafe Baud Rate

option and then use the space bar to set the console failsafe baud rate, if applicable.

26 Configuring Your Managed System

Use the up- and down- arrow keys to navigate to the

Ty p e

option and then use the space bar to select either

ANSI, if applicable.

Press <Enter> to return to the

Press <Esc> to exit the System Setup program. The the following options:

•

Save Changes and Exit

•

Discard Changes and Exit

•

Return to Setup

Choose the appropriate option and exit the system setup.

System Setup

screen.

Remote Terminal

VT 100/VT 200

Exit

screen displays

Configuring System BIOS in Dell PowerEdge x9

Turn on and restart your system.

Press <F2> immediately after you see the following message:

<F2> = Setup

The

System Setup

NOTE: If the operating system begins to load before you press <F2>,

allow your system to boot, and then restart your system, and try again.

Use the up- and down- arrow keys to navigate to the

Communication

Use the spacebar to select the appropriate serial communication option.

Press <Enter> to select the appropriate option for Console Redirection. The following options are available:

On without Console Redirection:

available for use by the operating system or applications. Console redirection is disabled. This is the default option.

On with Console Redirection via COM1:

redirection is enabled through COM1, the COM1 port is not available to applications through the operating system.

On with Console Redirection via COM2:

redirection is enabled through COM2, the COM2 port is not available to applications through the operating system.

screen appears.

field and press <Enter>.

COM1 and COM2 are enabled and

and xx0x Systems

Serial

When BIOS console

Configuring Your Managed System 27

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.

Use the up- and down- arrow keys to navigate to the

Communication

Use the spacebar to select the appropriate external serial communication

field and press <Enter>.

External Serial

option.

The available options are The default option is

NOTE: Select Remote Access to access the BMC through the serial cable

connection. This option can be set to any value for using SOL and accessing the BMC over LAN.

Press <Enter> to select.

If required, use the spacebar to navigate to and change the settings for

COM1, COM2

COM1

, and

Remote Access.

Redirection after Boot.

Use the up- and down- arrow keys to navigate to the

Failsafe Baud Rate

option and then use the space bar to set the console failsafe baud rate, if applicable.

Use the up- and down- arrow keys navigate to the option and then use the space bar to select either

Remote Terminal Type

VT 100/VT 200

if applicable.

Press <Enter> to return to the

Press <Esc> to exit the System Setup program. The

System Setup

screen.

Exit

screen displays

the following options:

•

Save Changes and Exit

•

Discard Changes and Exit

•

Return to Setup

ANSI,

NOTE: For most options, any changes that you make are recorded but do not take

effect until you restart the system.

NOTE: Press <F1> to display the help file for the System Setup program.

28 Configuring Your Managed System

Configuring System BIOS in Dell PowerEdge

Turn on and restart your system.

Press <F2> immediately after you see the following message:

xx1x

Systems

<F2> = Setup

The

System Setup

NOTE: If the operating system begins to load before you press <F2>,

allow your system to boot, and then restart your system, and try again.

Use the up- and down- arrow keys to navigate to the

Communication

Use the spacebar to select the appropriate serial communication option.

Press <Enter> to select the appropriate option for Console Redirection.

screen displays.

Serial

field and press <Enter>.

The following options are available:

On without Console Redirection:

COM1 and COM2 are enabled and available for use by the operating system or applications. Console redirection is disabled. This is the default option.

On with Console Redirection via COM1:

When BIOS console redirection is enabled through COM1, the COM1 port is not available to applications through the operating system.

On with Console Redirection via COM2:

When BIOS console redirection is enabled through COM2, the COM2 port is not available to applications through the operating system.

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.

Use the up- and down- arrow keys to navigate to the

Selection

Use the up- and down- arrow keys to navigate to the appropriate

Serial Connector

The available options are

field to select

option.

COM1

COM2

SerialDevice1, SerialDevice2

Serial Port Address

, and

Remote

Access Device.

NOTE: Use only SerialDevice2 for SOL.

Configuring Your Managed System 29

External

Use the up- and down- arrow keys to navigate to the

Failsafe Baud Rate

option and then use the space bar to set the console failsafe baud rate, if applicable.

Use the up- and down- arrow keys to navigate to the

Ty p e

option and then use the space bar to select either

ANSI,

if applicable.

Use the up- and down- arrow keys to navigate to and change the settings for

Redirection After Boot.

Press <Enter> to return to the

Press <Esc> to exit the System Setup program. The

System Setup

Remote Terminal

VT 100/VT 220

screen.

Exit

screen displays

the following options:

• Save Changes and Exit

• Discard Changes and Exit

• Return to Setup

NOTE: For most options, any changes that you make are recorded but do not take

effect until you restart your system.

NOTE: Press <F1> to display the help file for the System Setup program.

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.

By default, some operating systems, such as Windows Server 2003, are automatically configured to send text console output to the BIOS. Manual configuration of the Redirection after Boot feature through the system BIOS may not be visible to the operating system. This results in both, the operating system feature and the BIOS redirection feature, being enabled. Depending on the operating system and its setup, the results may vary. Dell recommends the following steps as good practice:

DR-DOS: Do not configure DR-DOS for serial console output. Enable console redirection after reboot in system BIOS.

30 Configuring Your Managed System

Windows Special Administrative Console (SAC): Do not configure Windows SAC for serial console redirection. Enable console redirection after reboot in system BIOS.

Linux: Do not configure console redirection after rebooting the system BIOS. Do the tasks listed in the "Installation and Setup for Linux Operating Systems" on page 44, to configure Linux for console redirection.

NOTE: See "Escape Key Sequences" on page 129 for a list of keystrokes to be used for

BIOS Setup operations from a serial terminal.

Baseboard Management Controller Configuration

You can perform basic BMC configuration using the Remote Access Configuration Utility in x9xx systems during system startup. See Figure 2-1. For more advanced configuration options, see the instructions for the DTK SYSCFG utility in the Deployment Toolkit User’s Guide.

NOTE: The Remote Access Configuration Utility in Dell PowerEdge x9xx systems is

called the BMC Setup Module in x8xx systems, iDRAC Configuration Utility in xx0x systems and iDRAC6 Configuration Utility in xx1x systems. For more information on the iDRAC Configuration Utility, see the Integrated Dell Remote Access Controller User’s Guide available on the Dell Support website at support.dell.com/manuals.

x9xx

Figure 2-1. Remote Access Configuration Utility in

systems

Configuring Your Managed System 31

Entering the Remote Access Configuration Utility in

Turn on or restart your system.

Press <

If your operating system begins to load before you press <

Ctrl-E

> when prompted after POST.

x9xx

systems

Crtl-E

>, 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. After entering all settings, press <Esc> and select one of the following:

•

Save Changes and Exit—

Configuration Utility.

•

Discard Changes and Exit

Configuration Utility.

•

Return to Setup

— Continue using the Remote Access Configuration

Utility.

Keep all entries made in the Remote Access

— Undo all entries made in the Remote Access

Table 2-1. Remote Access Configuration Utility in

Option Description

iDRAC6 LAN

NOTE: This option is

available in the iDRAC6 Configuration Utility on

Dell PowerEdge xx1x

systems.

IPMI Over LAN Enables or disables the out-of-band LAN channel access to

Enables or disables the iDRAC6 LAN. The LAN must be enabled to permit use of iDRAC6 facilities, such as the Web interface, telnet/SSH access to the SM-CLP command line interface, console redirection, and virtual media.

the shared network controller.

x9xx

systems

NOTE: When you select Off, the iDRAC will not accept IPMI

messages arriving over the LAN interface on Dell PowerEdge

xx1x systems.

32 Configuring Your Managed System

Table 2-1. Remote Access Configuration Utility in

Option Description

NIC Selection

NOTE: This option is

available only on Dell

PowerEdge x9xx, xx0x, and xx1x systems.

Displays the configuration option.

•Shared

Select this option to share the network interface with the host operating system. The remote access device network interface is fully functional when the host operating system is configured for NIC teaming.

The remote access device receives data through NIC 1 and NIC 2, but transmits data only through NIC 1.

If NIC 1 fails, the remote access device will not be accessible.

NOTE: The NIC 2 is not available on PowerEdge 1900

system.

•Failover

The remote access device receives data through NIC 1 and NIC 2, but transmits data only through NIC 1. If NIC 1 fails, the remote access device fails over to NIC 2 for all data transmission.

The remote access device continues to use NIC 2 for data transmission. If NIC 2 fails, the remote access device fails over all data transmission back to NIC 1.

NOTE: This option cannot be selected on the PowerEdge 1900

system.

x9xx

systems

(continued)

Configuring Your Managed System 33

Table 2-1. Remote Access Configuration Utility in

Option Description

•Dedicated

Select this option to enable the remote access device to utilize the dedicated network interface available on iDRAC6 Enterprise. 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.

systems

(continued)

x9xx

NOTE: This option is available only on systems with iDRAC6

Enterprise.

LAN Parameters

RMCP+ Encryption Key

IP Address Source Displays whether the network controller will be assigned a

Ethernet IP Address The static IP address of the BMC. This field is limited to a

NOTE: This option is available only on PowerEdge x9xx,

xx0x,and xx1x systems.

The Key is used to encrypt the IPMI sessions. The encryption key is entered as a maximum of 20 pairs of ASCII hexadecimal characters representing 20 bytes. For example, 01FA3BA6C812855DA001FA3BA6C812855DA0A0A0.

Static IP address or a DHCP address.

maximum value of 255.255.255.255.

The following IPv4 rules apply:

• IP addresses cannot be between

• The first octet must be between

143.xxx.xxx.xxx

0-255

127.xxx.xxx.xxx

)

1-223

, where

(that is,

xxx

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.

MAC Address This field is read-only.

Displays the network controller’s BMC MAC address.

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.

34 Configuring Your Managed System

Table 2-1. Remote Access Configuration Utility in

Option Description

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.

A valid value for the virtual LAN ID must be a number from 1 to 4094.

x9xx

systems

(continued)

NOTE: If you enter a value outside the specified range, either 1

or 4094 is entered, whichever is closest.

VLAN This field is read-only when VLAN Enable is set to off.

Specifies the priority of the VLAN. The valid values range from Priority 0 - Priority 7.

NOTE: This option is

available in the iDRAC6 Configuration Utility on

Dell PowerEdge xx1x

systems.

iDRAC6 Name

NOTE: This option is

available in the iDRAC6 Configuration Utility on

Dell PowerEdge xx1x

systems.

LAN Alert Enabled

Alert Policy Entry 1

Select On to register the iDRAC6 name in the DNS service.

Off

Select in DNS.

If edit the

Enter

< name. Press < iDRAC6 name must be a valid DNS host name.

Enables or disables LAN alerting.

Enables or disables the first alert destination.

if you do not want users to find the iDRAC6 name

Current DNS iDRAC6 Name

> when you have finished editing the iDRAC6

Esc

is set to On, press <

text field. Press

> to return to the previous menu. The

Enter

> to

Configuring Your Managed System 35

Table 2-1. Remote Access Configuration Utility in

x9xx

systems

(continued)

Option Description

Alert Destination 1 This field is read-only when LAN Alert Enabled is set to

off.

Enter the IP address of the first alert destination. Use the Left or Right arrow keys to navigate to each octet. Use the numeric keypad to enter each octet.

The following IPv4 rules apply:

• IP addresses cannot be between

0-255

• The first octet must be between

143.xxx.xxx.xxx

• The last octet must not be (i.e.

xxx.xxx.xxx.0

127.xxx.xxx.xxx

)

xxx.xxx.xxx.255

1-223

255

, where

xxx

(i.e.

)

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.

Smart Card Logon Select Enabled to enable Smart Card logon. Enabling Smart

Card logon disables all CLI out-of-band interfaces. Select Disabled to disable Smart Card logon. All command line outof-band interfaces are set to their default state. Select Enabled with RACADM to enable Smart Card logon along with remote RACADM. All other CLI out-of-band interfaces are disabled.

NOTE: This option is available only on xx0x and xx1x systems.

IPv6 Settings Specifies the LAN Configuration for IPv6.

NOTE: This option is available in the iDRAC6 Configuration

Utility on xx1x systems. See the Integrated Dell Remote Access Controller User’s Guide available on the Dell Support website

at support.dell.com/manuals for more information.

Advanced LAN Parameters

Dedicated NIC Configuration Options

NIC Enables or disables the NIC

Auto-Negotiate Enables or disables Auto-Negotiation of the LAN Speed.

NOTE: This option is available only on systems with a DRAC

installed.

36 Configuring Your Managed System

Table 2-1. Remote Access Configuration Utility in

x9xx

systems

(continued)

Option Description

LAN Speed Setting This field is read-only when Auto-Negotiate is set to

Enabled.

Sets the LAN Speed Setting to 10 or 100 Mbps

LAN Duplex Setting This field is read-only when Auto-Negotiate is set to

Enabled.

Sets the LAN communication method to Half or Full Duplex.

DNS Configuration Options

DNS Servers from DHCP

on = IP addresses of the DNS Servers are assigned by the DHCP

off = IP addresses of the DNS Servers are set manually

DNS Server 1

This field is read-only when DNS Servers from DHCP is set to on.

Enter the IP Address of DNS Server 1

The following IPv4 rules apply:

DNS Server 2

• IP addresses cannot be between

0-255

• The first octet must be between

143.xxx.xxx.xxx

• The last octet must not be (i.e.

xxx.xxx.xxx.0

This field is read-only when DNS Servers from DHCP is

127.xxx.xxx.xxx

)

xxx.xxx.xxx.255

1-223

255

, where

xxx

(i.e.

)

set to on.

Enter the IP Address of DNS Server 2

The following IPv4 rules apply:

• IP addresses cannot be between

0-255

• The first octet must be between

143.xxx.xxx.xxx

• The last octet must not be (i.e.

xxx.xxx.xxx.0

on = You may enter the Current DNS RAC Name.

127.xxx.xxx.xxx

)

xxx.xxx.xxx.255

1-223

255

, where

xxx

(i.e.

)

Configuring Your Managed System 37

Table 2-1. Remote Access Configuration Utility in

Option Description

Domain Name from DHCP

Domain Name

Virtual Media Configuration

Virtual Media

Virtual Flash

LCD Configuration Configures the virtual Keyboard Video Mouse (vKVM)

LCD User Defined String

LCD System Power Units

LCD Ambient Temp Units

LCD Error Display

LCD Front Panel Access

LCD Remote KVM Indication

LAN User Configuration

This field is read-only when Register RAC Name is set to off.

Enter the Current DNS RAC Name using 1-32 alphanumerics, spaces, and symbols. Press <Enter> to save the value. Press <Esc> to exit the field without saving.

Turns the domain name on or off.

This field is read-only when DNS Servers from DHCP is set to on.

Enter the Domain Name using 1-64 alpha-numerics, spaces, and symbols. Press <Enter> to save the value. Press <Esc> to exit the field without saving.

NOTE: This option is available only on systems with a DRAC

installed.

Attaches or detaches a virtual media drive.

Enables or disables virtual flash memory.

session status on LCD and the access level to the LCD.

Sets the line of user-defined text on the system LCD.

Sets the unit for the system power.

Sets the unit for the ambient temperature.

Sets the error display field.

Allows you to either View, or View and Modify, or Lock the data on the LCD.

Enables or disables the vKVM session status on the LCD.

Enables setting the user name, user password, user privilege, and enables user access for user ID=2.

x9xx

systems

(continued)

38 Configuring Your Managed System

Table 2-1. Remote Access Configuration Utility in

Option Description

Account Access

Account Privilege

Account User Name

Enter Password

Confirm Password

Reset To Default

System Event Log Menu

Total System Event Log Entries

View System Event Log

Clear System Event Log

Enables or disables account privileges.

Sets the account to:

Admin, User, Operator, or No Access

Sets the account user name.

Enter the password for this Account User. You must enter at least one non-null character.

Confirm the password you entered.

Clears the BMC settings and resets the BMC setting to the defaults.

CAUTION: Resetting to factory defaults will restore

remote non-volatile settings.

Enables viewing and clearing the System Event Log (SEL). A popup box will indicate that the SEL is being read.

Displays the number of records in the SEL.

Displays a record in the SEL, starting with the most recent record. Enter a record number to view, using the Advance to Entry field. Use the Right and Left arrow keys to scroll up and down the SEL.

Erases all records in the SEL.

x9xx

systems

(continued)

NOTE: If the first integrated network interface controller (NIC 1) is used in an Ether

Channel team or link aggregation team, the BMC management traffic will not

function on PowerEdge x8xx systems. The NIC teaming option is supported on PowerEdge x9xx, xx0x, and xx1x systems. For more information about network

teaming, see the documentation for the network interface controller.

Configuring Your Managed System 39

Configuring Your BMC Using the Deployment Toolkit Utility

The Dell OpenManage Deployment Toolkit SYSCFG utility includes a set of Microsoft Windows PE and Linux-based utilities for configuring and deploying Dell systems. The Deployment ToolKit (DTK) SYSCFG utility is specifically designed to address all necessary BMC configuration tasks using a powerful and comprehensive command-line interface. This utility runs on PowerEdge 1435SC and all supported PowerEdge x7xx, x8xx, x9xx, xx0x, and xx1x systems.

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

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.

Installation and Setup for Microsoft Windows PE Operating Systems

NOTE: See the Deployment Toolkit User’ s Guide for additional information about

installing and using the utilities, and the Deployment Toolkit Command Line Interface Reference Guide for a complete list of valid options, suboptions, and

arguments for using the SYSCFG.EXE to configure and manage your BMC.

The DTK components are provided as a self-extracting zip file on the Dell Support website at support.dell.com. The self-extracting file can be opened on any system running a Microsoft Windows operating system, or it can be extracted at the Windows Command Prompt (cmd.exe) using the PKUNZIP.EXE utility (not supplied with the Deployment Toolkit). By default, the dtk-2.X-winpe-AXX.exe files are extracted to the root directory of your local hard drive, for example, C:\. This location can be changed by giving a different path when extracting the file. Perform the following steps to extract the DTK components to a workstation running Windows:

the Dell Support website at

40 Configuring Your Managed System

Download the DTK file website at

support.dell.com

dtk-2.X-winpe-AXX

.exe

from the Dell Support

and save it on a system running a supported

Windows operating system.

After the zip file downloads, double-click the file.

Click OK.

Click

Unzip

By default, the DTK files are unzipped to located in the located in the

C:\Dell\Toolkit\Tools C:\Dell\drivers

folder.

\. The

SYSCFG.EXE

directory. Dell-provided drivers are

Creating a Bootable Windows PE 2005 ISO Image

NOTE: See "Creating a Bootable Windows PE 2.0 ISO Image" on page 43 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:

Integrating DTK tools and scripts: Copy the folder unzipped from the Dell-supplied zip file to

DellWinPEBuild,

the Dell-supplied file directly into the Windows PE build.

Installing necessary drivers into Windows PE: Execute

\Dell\Drivers\DRIVERINST.BAT

•Path to

DellWinPEBuild

with two required arguments:

• Path where the Dell-provided drivers are located. These drivers can be found in the DTK zip file under the

Adding support for mass storage drivers into Windows PE:

\Dell\drivers

\Dell

folder.

that you

utility is

or extract

NOTE: You must implement this step to ensure mass storage drivers are

installed into Windows PE.

In the

winpeoem.sif

file (available under

I386\SYSTEM32

in your Windows PE directory), edit the following text to remove the semicolons from the names for the Dell

Oem Driver Params

-m

ass storage drivers:

section and append the directory

OemDriverRoot="" OemDriverDirs=MRAID, PERC4IM, PERC5, SAS5

Configuring Your Managed System 41

NOTE: For your reference, a sample winpeoem.sif file is available under

\Dell\Toolkit\template\Configs.

Starting required services: The started for RAID to function; the

mr2kserv

racsvc

service should be installed and

service should be installed and started for RACADM to function. For details on how to start the required services, see the sample

\Dell\Toolkit\template\Configs

NOTE: When booting the target system, ensure that the RAC and the

mr2kserv services are running.

Extracting the following files from your Windows Server 2003 product CD to

\Dell\Toolkit\Tools

winbom.ini

file under

•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:

Create a directory,

Insert the Windows OEM Preinstallation Kit (OPK) CD into your CD

WinPE_OPKTools

, on your hard drive.

drive.

Copy all CD files from the Windows PE directory to the

WinPE_OPKTools

Copy

factory.exe

the

WinPE_OPKTools

Remove the CD from the CD drive.

Create and name a directory on your development system hard drive.

directory.

and

netcfg.exe

directory.

from the

CD drive

\tools\x86 directory to

This is where the ISO file is stored.

Navigate to the

Run the following command:

WinPE_OPKTools

directory through a command prompt.

OSCDIMG -bETFSBOOT.COM -n <DELLWINPEBUILD>

42 Configuring Your Managed System

ETFSBOOT.COM is part of the OPK tools and makes the Windows PE CD bootable. The following command line creates a bootable ISO image called Dellx86winpe.iso:

C:\WINPE_OPKTOOLS\OSCDIMG -bETFSBOOT.com -n c:\DELLWINPEBUILD

C:\FINALBUILD\Dellx86winpe.iso

Copy the SYSCFG.EXE utility to the root of the directory.

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 Installation Kit (WAIK) from the Microsoft website. By default, WAIK is copied to the

Integration of DTK Directory Structure in Windows PE Build

C:\Program Files\Windows AIK

DTK provides a script, VPE_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 2.0 image offline. Use the following steps to execute this script:

Open a command prompt on your system and change the directory to the location of VPE_driverinst.bat. For example:

cd C:\Dell\Drivers\winpe2.x

Windows Administrative

directory.

Execute VPE_driverinst.bat with two required arguments

and

. For example:

VPE_driverinst.bat <WINPEPATH> <DTKPATH>

Where

structure for Windows PE 2.0 and

i s t h e d e st in a ti o n p a th to c re a te t he d ir e ct o ry

is the path to Dell

drivers in the extracted DTK toolkit. For example:

VPE_driverinst.bat C:\vistaPE_x86 C:\DELL\DRIVERS

Configuring Your Managed System 43

NOTE: <WINPEPATH> is passed as the destination to the WAIK command

copype.cmd. The destination folder C:\vistaPE_x86 is created as part of the

process, and should not already exist.

Creating a Bootable CD

Use the following steps to create bootable media:

Click

Start

, navigate to

Click

Windows PE Tools Command Prompt

All ProgramsMicrosoft Windows AIK

to open a command prompt

window.

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.

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.

Installation and Setup for Linux Operating Systems

NOTE: See the Deployment Toolkit User’ s Guide for additional information about

installing and using the utilities, and the Deployment Toolkit Command Line Interface Reference Guide for a complete list of all valid options, suboptions, and

arguments for using the SYSCFG utility to configure and manage your BMC.

Obtain the ISO image of embedded Linux available on the Dell Support website at

Burn the ISO image using any commonly available CD burning software.

support.dell.com

NOTE: When you create a bootable CD, this image is supplied to the CD burning

software along with the complete deployment directory structure, which includes all necessary supporting files to perform the deployment.

The CD burning software creates an image of the self-bootable ISO image and the deployment files on the CD.

Extract the contents of the ISO image to a folder on your hard drive.

Copy your custom scripts into the folder you created in step 4.

44 Configuring Your Managed System

NOTE: Your scripts should also take care of copying miscellaneous items to

unlock the CD, so that the CD can be mounted and ejected as required by the operating system’s installation process.

/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.

Copy the directory structure created in your work station, into the root folder that you created in "step 4".

This folder contains the DTK CD files necessary for operating system installation, and files required for replication.

Use the

isolinux

utility to burn the contents of the folder you created in

"step 7" to a CD and make it bootable.

Your ISO image is ready for booting.

Basic configuration

Before you can use the BMC Management Utility to remotely manage the BMC on a managed system, you must perform some basic configuration tasks. The Deployment Toolkit SYSCFG utility provides a powerful command-line interface for performing the following configuration tasks:

• Configuring BMC users for the managed system

• Configuring the BMC IP address for IPMI LAN access and SOL access for the managed system

• Configuring the BMC serial channel for IPMI serial access for the managed system

NOTE: See the Deployment Toolkit User’s Guide for additional information about

installing and using the Deployment Toolkit utilities, and the Command Line Interface Reference Guide for a complete list of valid options, suboptions, and

arguments for using the SYSCFG utility to configure and manage your BMC.

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.

Configuring Your Managed System 45

Insert the bootable BMC configuration diskette or CD into the appropriate drive of the system to be deployed and reboot the system.

To create a new user, at the command prompt, type:

syscfg username --userid=X --name=name

where X is a number between 2–10 and

name

is an ASCII string of 16 or

fewer characters.

Press <Enter> to execute the command line options.

To enable the new user ID, at the command prompt, type:

syscfg useraction --userid=X --action=enable

Press <Enter> to execute the command line options.

To set the password for a BMC user, at the command prompt, type:

syscfg passwordaction --action=setpassword --userid=X -

-password=password

where

password

PowerEdge

CAUTION: A password must be set for each BMC user. The BMC firmware does

not allow access to users with null user names or passwords.

is an ASCII string of 16 or fewer characters for both

x8xx

and

x9xx

systems.

Press <Enter> to execute the command-line options.

To configure BMC user privilege, at the command prompt, type:

syscfg lanuseraccess --usrprivlmt=bmcuserprivilege where bmcuserprivilege=user, operator, administrator, noaccess

Press <Enter> to execute the command-line options.

Configuring the BMC IP Address

Insert the Deployment Toolkit CD into the appropriate drive of the system to be deployed and reboot the system.

To configure the BMC IP address source for the LAN channel to DHCP, at the command prompt, type:

syscfg lcp --ipaddrsrc=dhcp

Press <Enter> to execute the command line options.

46 Configuring Your Managed System

For a complete list of valid options, suboptions, and arguments for configuring the BMC LAN channel see the

Line Interface Reference Guide

To configure the BMC IP address source for the LAN channel to a static

Deployment Toolkit Command

IP address, at the command prompt, type:

syscfg lcp --ipaddrsrc=static --ipaddress= XXX.XXX.XXX.XX

--subnetmask=XXX.XXX.XXX.X --gateway= XXX.XXX.XXX.X

Press <Enter> to execute the command line options.

For a complete list of valid options, suboptions, and arguments for configuring the BMC LAN channel see the

Line Interface Reference Guide

Configuring the BMC Serial Channel Access

Insert the bootable diskette or CD into the appropriate drive of the system

Deployment Toolkit Command

to be deployed, and reboot the system.

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 <Enter> to execute the command line options.

To configure the terminal mode for BMC, at the command prompt, type:

syscfg scp --connectionmode=terminal -msgcommbitrate=XXXXX

where

XXXXX

is the baud rate in bps.

Press <Enter> to execute the command line options.

For a complete list of valid options, suboptions, and arguments for configuring the BMC serial channel, see the

Line Interface Reference Guide

Configuring Your Managed System 47

Deployment Toolkit Command

Configuring Your BMC Using Server Administrator

You can also configure the BMC options using Server Administrator Version 5.3 or later, which is a one-to-one systems management software program that must be installed on the managed system. Once installed, you can remotely access Server Administrator from a management station with a supported browser to perform BMC configuration tasks. See the Server Administrator User’s Guide for more information about installing and using Server Administrator.

You can configure the BMC settings from either the Server Administrator home page or from its command line interface. Users must have Administrator privileges to access the BMC settings. Users logged in with User or Power User group privileges can view the BMC information but cannot change the settings.

See the Dell OpenManage Server Administrator Command Line Interface User's Guide for information about configuring the BMC from the command line.

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.

The Server Administrator Instrumentation Service allows you to manage BMC features, such as, general BMC information, configuration of the LAN and serial port, BMC users, and BIOS setup. To use Server Administrator to configure the BMC on a managed system, perform the following steps:

NOTE: You must be logged in with Admin privileges to configure the BMC settings.

Click the

The

Click the

Under the Serial Over LAN.

48 Configuring Your Managed System

System

object.

Main System Chassis

Remote Access

BMC Information

Configuration

object.

window is displayed.

tab.

tab, you can configure LAN, Serial Port, and

Click the

Under the

CAUTION: A password must be set for each BMC user. The BMC firmware does

not allow access to users with null user names or passwords.

Configuring BIOS in Server Administrator

Users

tab.

Users

tab, you can modify the BMC user configuration.

To configure BIOS in Server Administrator, complete the following steps:

Click the

In the

communication

System

object.

Main System Chassis

BIOS

object.

Setup

tab.

Setup

tab, you can configure

parameters.

object.

Console Redirection

and

Serial Port

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.

NOTE: Most DHCP servers require a server to store a client identifier token in its

reservations table. The client (DRAC 5, for example) must provide this token during DHCP negotiation. For RACs, the DRAC 5 supplies the client identifier option using a one-byte interface number (0) followed by a six-byte MAC address.

NOTE: If your managed system DRAC is configured in Shared or Shared with Failover

mode and the DRAC is connected to a switch with Spanning Tree Protocol (STP) enabled, network clients will experience a 20- to 30-second delay in connectivity when the management station’s LOM link state changes during the STP convergence.

Access the DRAC 5 Web-based interface. See the

Controller 5 User’s Guide

Click

Remote Access

Click the

Configuration

for more information.

in the

System

tree.

tab and then click

Configuring Your Managed System 49

Dell Remote Access

Network

Configure the DRAC 5 NIC settings in the

Network Configuration

page.

Table 2-1 describes the Network Settings and IPMI Settings on the

Network Configuration

Click

Apply Changes

Click the appropriate

Adding and Configuring DRAC 5 Users

page.

when completed.

Network Configuration

page button to continue.

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.

Expand the System tree and click

Click the

Configuration

tab and then click

Remote Access

Users

. The

Users

page appears, which includes each user’s State, RAC Privilege, IPMI LAN Privilege, and IPMI Serial Privilege.

Click a user ID number in the User ID column.

Configure the user’s properties and privileges in the

User Configuration

page.

Click

Apply Changes

Click the appropriate

See the

Dell Remote Access Controller 5 User’s Guide

when completed.

User Configuration

page button to continue.

for more information on the IPMI user privileges, DRAC group permissions, and the DRAC user privilege settings.

50 Configuring Your Managed System

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. IPMI Shell supports both serial access and LAN access to the BMC. IPMItool supports only LAN access to the BMC.

The IPMI Shell can be used either in the generic CLI mode or the interactive mode. The interactive mode allows for a dedicated connection to a server and availability of all commands from the operating system CLI. Using the IPMI Shell in this mode improves usability and reduces time and traffic required for connecting and authenticating. The IPMItool can only be used in the CLI mode.

Both IPMI Shell and IPMItool allow administration of one or more managed systems from a command line shell, rather than a graphical user interface (GUI). Use the IPMI Shell or IPMItool to perform the following tasks:

– System power management – System identifier control – Access to the event log – Access to the system sensors – Enable Serial-over-LAN for a remote managed system

Using the BMC Management Utility 51

• 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. The SOL protocol coupled with the remote system's BIOS console redirection allows administrators to remotely view and change a managed system’s BIOS settings over a LAN. The Linux serial console and Microsoft's EMS/SAC interfaces can also be accessed over a LAN using SOL.

CAUTION: All versions of the Microsoft Windows operating system include

Hilgraeve's HyperTerminal terminal emulation software. However, the included version does not provide many functions required during console redirection. Instead, you can use any terminal emulation software that supports VT100 or ANSI emulation mode. One example of a full VT100 or ANSI terminal emulator that supports console redirection on your system is Hilgraeve's HyperTerminal Private Edition 6.1 or later.

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.

NOTE: HyperTerminal and telnet settings must be consistent with the settings on

the managed system. For example, the baud rates and terminal modes should match.

NOTE: The Windows "telnet" command that is run from a MS-DOS prompt supports

ANSI terminal emulation, and the BIOS needs to be set for ANSI emulation to display all the screens correctly.

NOTE: In future releases, IPMItool will replace IPMI Shell (IPMISH) and SOL Proxy

utilities.

Installing the BMC Management Utility

The BMC Management Utility is installed on a management station to remotely connect to the managed system’s BMC. See Figure 3-1.

52 Using the BMC Management Utility

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" on page 25.

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

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

Using the BMC Management Utility 53

Installing on Systems Running Supported Windows Operating Systems

To install the BMC Management Utility on a management station running the Windows operating system, perform the following steps:

Exit any open application programs and disable any virus-scanning software.

Insert the your system's DVD drive.

If the DVD does not automatically start the setup program, click the button, click drive letter of your DVD drive).

The

Click

The

Station

Click

A software license agreement appears.

Select

The

Select

The

Dell Systems Management Tools and Documentation

Run

, and then type

Dell OpenManage Management Station Installation

Install, Modify, Repair or Remove Management Station

Welcome to Install Wizard for Dell OpenManage Management

screen appears.

I accept the terms in the license agreement,

Setup Type

Custom Setup

screen appears.

and click

screen appears.

x:\windows\setup.exe

if you agree.

DVD into

(where x is the

screen appears.

Start

From the drop-down menu, which appears on the left side of BMC Console, select

local hard drive

To accept the default directory path, click and navigate to the directory where you want to install your software, and then click

The

Ready to Install the Program

54 Using the BMC Management Utility

This feature, and all subfeatures will be installed on the

. Otherwise, click

screen appears.

Browse

Ensure that all information is correct and click

The

Installing Dell OpenManage Management Station

and displays the status of the installation.

When installation is complete, the appears. Click

NOTE: Enable the virus scanning software after installation.

See the Dell OpenManage Installation and Security User’s Guide for additional information about installing the BMC Management Utility on a management station.

By default, the installation program copies the files to the following directory: C:\Program Files\Dell\SysMgt\bmc.

The SOL Proxy service does not auto-start after installation. To start the SOL Proxy service after installation, you can reboot the system (SOL Proxy automatically starts on a reboot). To restart the SOL Proxy service on Windows systems, complete the following steps:

Right-click

Management

Click

Services and Applications

are displayed to the right.

Locate start the service.

Finish

My Computer

window is displayed.

DSM_BMU_SOLProxy

and click

Install Wizard Completed

Manage.

and then click

in the list of services and right-click to

Install

The

Computer

Services.

screen appears

screen

Available services

Uninstalling on Systems Running Supported Windows Operating Systems

To uninstall the BMC Management Utility, use the Add/Remove Programs utility in the Control Panel.

Using the BMC Management Utility 55

Installing on Systems Running Supported Linux Enterprise Operating Systems

To install the BMC Management Utility on a management station running the Linux operating system:

If required, mount the appropriate media supplied by Dell using the command:

mount /mnt/cdrom

Install the BMC Management Utility with the following command for SUSE Linux Enterprise server:

rpm -ivh /linux/bmc/osabmcutil9g-SUSE*.rpm

or for Red Hat Enterprise Linux, use the following command:

rpm -ivh /linux/bmc/osabmcutil9g-RHEL*.rpm

By default, the installation program copies the files to the following locations:

/etc/init.d/SOLPROXY.cfg

/etc/SOLPROXY.cfg

/usr/sbin/dsm_bmu_solproxy32d

/usr/sbin/solconfig

/usr/sbin/ipmish

The SOL Proxy will start automatically during system startup. Alternatively, you can go to directory commands to manage the SOL Proxy service:

solproxy status

/etc/init.d

and use the following

dsm_bmu_solproxy32d start

dsm_bmu_solproxy32d stop

solproxy restart

56 Using the BMC Management Utility

Uninstalling on Systems Running Supported Linux Enterprise Operating Systems

To uninstall the BMC Management Utility, perform the following steps:

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.

root

IPMI Shell

IPMI Shell is a CLI console application and has no GUI. Its commands and options are specified using command line arguments only.

IPMI Shell supports out-of-band (OOB) access (over a LAN or through the serial port) to a single system at a time, however, multiple IPMI Shell sessions can run simultaneously on the same managed system. See Figure 3-2.

IPMI Shell allows a user with user-level BMC privileges to:

• Display the current power status.

• Display the 16-byte system GUID of the managed system.

• Display information from the system’s field replaceable unit (FRU).

• Display the BMC firmware information.

• Display summary information about the event log.

• Display logged events.

• Display current status of platform sensors.

• Enable or disable SOL.

Using the BMC Management Utility 57

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.

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. 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" on page 113 for a complete list of possible BMC Management Utility error codes.

Figure 3-2. IPMI Shell Diagram

58 Using the BMC Management Utility

Using IPMI Shell

To use IPMI Shell, perform the following steps:

On systems running a supported Microsoft Windows operating system:

Start a

Command Prompt

Locate the directory:

Enter IPMI Shell commands (see "IPMI Shell Command Syntax" on page 59) to manage the remote system. See "IPMI Shell Commands" on page 66 for a complete list of valid options, commands, subcommands, and arguments.

On systems running a supported Linux operating system:

Start an operating system (OS) shell.

NOTE: The IPMI Shell will be located in /usr/sbin.

ipmish.exe

C:\Program Files\Dell\SysMgt\bmc.

window.

file. By default,

ipmish.exe

is located in the

IPMI Shell Command Syntax

The general syntax of IPMI Shell CLI commands is as follows:

ipmish [global-options] … command [; command] …

The general usage for a command is:

command [subcommand] [command option and argument] …

Both global options and command-specific options are always in the following form:

-option argument

For examp l e:

-help

-max 20

-u John

Using the BMC Management Utility 59

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.

IPMI Shell Global Options

IPMI Shell has the following global options:

Running IPMISH over LAN Option -ip

Synopsis

ipmish -ip bmc_ip_address | bmc_hostname -u username p password

[-k KG value] <command>

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.

NOTE: This global option cannot be used independently to connect to the BMC.

One or more IPMISH commands must follow the option.

Options

-ip bmc_ip_address | bmc_hostname

Specifies the IP address or hostname of the remote managed system.

-u username

Specifies the BMC username.

-p password

Specifies the BMC user password.

-k KG value

60 Using the BMC Management Utility

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, and so on to disable encryption.

NOTE: The IPMI encryption key is available only on Dell x9xx,xx0x and xx1x systems.

Running IPMISH over Serial - Option -com

Synopsis

ipmish -com serial_port -baud baud_rate -flow flow_control -u username -p password

The following attributes should be configured for IPMISH over serial to function correctly.

NOTE: These options can be configured in BIOS Setup, as well as using

Dell OpenManage tools. Log on to Server Administrator and navigate to BIOS Setup.

• "External Serial Connector" must be configured and set to "Remote Access" for PowerEdge

x9xx, xx0x,

and

xx1x

systems. This option is

available in the "Serial Communication" submenu in BIOS setup.

• Disable the "RAC serial Console" if you have a DRAC 5 card installed. Log on to the DRAC GUI, navigate to Serial and deselect the "Enable Serial console" checkbox.

• Set "Serial port 1" to "BMC Serial" for PowerEdge

x8xx

systems. This

option is available under the Integrated Devices menu in BIOS Setup.

The Serial communication connection mode for the BMC must be set to "Direct Connect Basic Mode" for all systems. This can be configured using Server Administrator. Log on to Server Administrator and navigate to Serial Port.

Description

This option establishes a connection to a remote managed system using the serial channel.

NOTE: This global option cannot be used independently to connect to the BMC.

One or more IPMISH commands must follow the option.

Using the BMC Management Utility 61

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. The maximum reliably supported baud rates are:

• 19200 for PowerEdge x8

• 57600 for PowerEdge

x9xx

systems

and

xx0x

systems without Dell Remote Access

Controller 5 (DRAC 5)

• 115200 for PowerEdge

NOTE: The baud rate for serial channel should match the baud rate set in the

managed system.

x9xx

xx1x

and

xx0x

systems

systems with DRAC 5

-flow flow_control

Specifies the data flow control method. There are two flow control options:

cts (hardware flow control) and none (no flow control).

-u username

Specifies the BMC username.

-p password

Specifies the BMC user password.

IPMI Help Option -help

Synopsis

ipmish -help [command]

62 Using the BMC Management Utility

Description

This option displays the following information:

• A summary page for all commands

• A summary of all subcommands for a single command

• A detailed description of a command-subcommand combination

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-3 and Figure 3-4.

Figure 3-3. IPMI Help Option Example 1

Using the BMC Management Utility 63

Figure 3-4. IPMISH Help option Example 2

IPMI Session Option -interactive

Synopsis

ipmish -interactive [-cfg <config_file>]

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.

Options

-interactive

Invokes the interactive CLI mode.

-cfg <config_file>

64 Using the BMC Management Utility

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" on page 93 for more information on configuration files.

Figure 3-5. IPMISH interactive option

The following line edit functions are supported during the interactive session:

Up and Down arrow keys to browse command history.

Left and Right arrow keys to move the input cursor.

Home and End keys to move the input cursor to the beginning or end of the line.

Backspace key to move the input cursor back by one space.

The following line edit functions are supported for the SOL proxy menu mode:

Left and Right arrow key to move the input cursor.

Home and End keys to move the input cursor to the beginning or end of the line.

Backspace key to move the input cursor back by one space.

Using the BMC Management Utility 65

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.

sel Displays or deletes information from the SEL.

sol Enables Serial-over-LAN for the remote managed system.

sensor Displays current status of platform sensors.

LCD Displays information on and helps configure the LCD panel in

Dell

x9xx, xx0x,

powermonitor Displays information on and helps manage your system’s power.

connect Connects to the BMC of the remote managed system.

help Displays a command list with descriptions and syntax of options.

quit Exits the command prompt.

and

xx1x

systems

identify

Synopsis

identify [on [-t seconds] | off]

Description

This command controls the identification LED on the front panel. See Figure 3-6.

66 Using the BMC Management Utility

Subcommands

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.

Default Subcommand

If a subcommand is not specified, this command acts the same as the identify on command.

Figure 3-6. identify Option Example

sysinfo

Synopsis

sysinfo [fru | id]

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.

Using the BMC Management Utility 67

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. sysinfo Option Example

Figure 3-8. sysinfo FRU Example

68 Using the BMC Management Utility

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

value is

•

off

NOTE: This reboot feature mimics restarting the system using the server's power

button. A graceful shutdown of the server operating system may not be possible when the server software stops responding, or if the local security policy of the operating system does not allow a graceful shutdown. In these cases, specify a forced reboot instead of graceful reboot of Windows.

•

cycle

•

reset

— Displays the current power status of the system, the returned

off

— Turns on the managed system.

— Issues a "graceful shutdown" IPMI command.

— Turns off the system, pauses, then turns the system back on.

— 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.

Using the BMC Management Utility 69

Figure 3-9. Power Option Example

sel

Synopsis

sel status

sel get [[-begin index1] [-end index2 | -max count]] | [-last n] [-format <oemlist|legacy>]

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

get

clear

— Displays the total number of system event log records.

— Prints all or part of the event log.

— Deletes all the records in the event log.

70 Using the BMC Management Utility

Options

-begin index1

Specifies the first record to display.

-end index2

Specifies the last record to display.

-max count

Specifies the maximum number of records to display.

If the value of the argument count is bigger than the total number of the records, the last record displayed will be the last one in the event log.

-last n

Specifies the number of records to be displayed, starting from the last record and counting backwards.

Default Subcommand

If a subcommand is not specified, this command acts the same as sel status.

Display Format

System event log records are displayed using either a tabular format (legacy) or a vertical format (oemlist) consistent with the SEL log output found in other Dell OpenManage products. The default is the oemlist format. The column headers for the legacy format are: Ordinal Number, Date, Time, Sensor Number, Sensor Type, and Brief Description. See Figure 3-10 for an example of oemlist and legacy formatted SEL display.

Using the BMC Management Utility 71

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. See Figure 3-11.

NOTE: The command prompt responds with an error message if a command is

used before establishing an IPMI session with connect.

Subcommands

•

enable

disable

•

config

— Allows you to enable SOL of connected server.

— Allows you to disable SOL of connected server.

— Allows you to configure SOL baud rate and privilege level.

72 Using the BMC Management Utility

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. The maximum and minimum values are 7 and 0, respectively.

• -retry interval retry_interval

Specifies the retry time interval that the BMC will wait before resending SOL packets to the remote console. It is specified in 10 ms increments. For example, if you set 100 as the value, the BMC will wait 1000 ms before retrying to send SOL packages to the remote console. If you specify zero as the value, the BMC will retry sending instantly, without any time intervals.

Figure 3-11. IPMISH SOL option

Using the BMC Management Utility 73

sensor

Synopsis

Description

This command displays the current status of platform sensors using one of the two possible formats. See Figure 3-12.

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 <oemlist|legacy>

Use different formats to output the sensor data. Default format is oemlist. Legacy format is displayed as below:

Subcommands

[temp | fan | volt | discrete | numeric]

Specifies the sensor group for which information is displayed. If no sensor group is specified, information is displayed for all groups.

74 Using the BMC Management Utility

Figure 3-12. Sensor option example

connect

Synopsis

connect -ip bmc_ip_address | bmc_hostname [-u username] [-p password] [-k IPMI encryption key value]

connect -com bmc_ip_address | bmc_hostname -u username

-p password

[-k KG value] <command>

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

Options

-ip bmc-ip-address|bmc_hostname

Specifies the out-of-band IP address or hostname of the remote managed system.

-u username

Specifies the username to connect to the remote system.

Using the BMC Management Utility 75

-p password

Specifies the password to be used to connect to the remote managed system.

-k IPMI encryption key value

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, and so on to disable encryption.

Figure 3-13. IPMISH connect option

LCD

Synopsis

LCD info

Description

This command displays the status of the LCD display on a x9xx, xx0x, or xx1x system. You can also configure the LCD display using this command.

Subcommands

•

info

•

set other

•

none

•

default

— Displays information about the LCD display.

— Sets LCD display to either

none, default, other

to set a string of your choice.

— Turns the LCD display off.

— Sets the default display on the LCD.

. Choose

76 Using the BMC Management Utility

Default Subcommand

If a subcommand is not specified, this command functions the same as LCD info.

powermonitor

Synopsis

powermonitor status

Description

This command displays the current power status of the managed system.

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

•

clear cumulativepower

Default Subcommand

— Deletes the peak power value.

— Deletes the cumulative power values.

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.

Using the BMC Management Utility 77

help

Synopsis

help [command]

Description

This command lists commands and capsule descriptions with syntax for each command. See Figure 3-14.

Argument

command

Specifies the command for which detailed description is required.

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. SOL Proxy does not support in-band or serial connection to the managed system’s BMC.

78 Using the BMC Management Utility

When BIOS console redirection to serial port is enabled on the remote managed system, any application that uses the BIOS to read from or write to the system console will have its I/O redirected to the designated serial I/O port. When SOL is activated, the BMC firmware reads any data written to the serial port and transmits it to the SOL Proxy as LAN packets. SOL Proxy then forwards the data to the telnet client as TCP/IP packets.

Conversely, any keyboard activity at the telnet client is sent to the BMC by SOL Proxy. BMC then writes the packets to the system serial I/O port.

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.

Figure 3-15. SOL Proxy Diagram

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.

Using the BMC Management Utility 79

You can use a variety of telnet clients to access SOL Proxy features. For exam ple :

• In a Windows environment, you can use a Command Prompt window as your console. However, function keys such as <F1> and <F2> will not operate correctly with this client except on systems running Windows Server 2003.

• In a Windows environment, you can also use any telnet application that supports VT100 or ANSI emulation mode (such as HyperTerminal) as your console.

CAUTION: All versions of the Microsoft Windows operating system include

CAUTION: SOL Proxy supports only local user login and not Active Directory

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.

• In a Linux environment, you can use a shell such as

csh

ksh

as your console, or you can use any telnet application supporting VT100 or ANSI emulation mode.

NOTE: Telnet settings must be consistent with the settings on the managed

system. For example, the baud rates and terminal modes should match.

You can also send the terminal break function while in console redirection. The use of this functionality requires that the specific terminal program in use has the ability to send the break function. For example, you can send the break signal through the Linux telnet modules by typing:

Ctrl+]send brk<Enter>

80 Using the BMC Management Utility

The Linux SysRq function is one example of an advanced debugging feature that is enabled by use of the break function. See the "BIOS Configuration" on page 25 on how to use this feature. See the "Serial Console redirection With SOL Proxy" on page 133 for more information on the SysRq feature.

To enable BIOS console redirection for use with SOLProxy:

•Configure the

Redirection via COM2

the

Serial Communication

COM2

Console redirection

for Dell

attribute to

x9xx

and

attribute to

On with Console Redirection via

. This option is available under the

On with Console

xx0x

. For

xx1x systems, configure

Serial Communication

submenu in BIOS setup.

•Configure the PowerEdge

Redirection

option is available under the

Console Redirection

x8xx

systems. This option is available under the

menu in

BIOS Setup

attribute to

. Set

Serial Port 1

Integrated Devices

Serial Port1

menu in

BMC NIC

for

Console

. This

BIOS Setup

Using SOL Proxy

Depending on the console you use, there are different steps for accessing SOL Proxy. Throughout this section, the management station where the SOL Proxy is running is referred to as the SOL Proxy Server.

Initiating the SOL Proxy session using the Windows Command Prompt:

To connect and use SOL Proxy:

Open a Command Prompt window on your management station.

Enter 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

telnet

command in the command-line and provide the

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" on page 93.

If you are prompted for a username, provide the operating system login credentials of the system running the service:

Using the BMC Management Utility 81

DSM_BMU_SOLProxy

Provide a password when prompted. SOL Proxy will use this combination of operating system username and password to authenticate you on the SOL Proxy Server. The specific authentication scheme will depend on the operating system configuration for the SOL Proxy Server. However, if

localhost

or an IP address of 127.0.0.1 is used, it is assumed that the user has login privileges to the current host, and is not prompted for a username and password.

After authentication, a login successful message and the SOL Proxy main menu prompt appear. You are ready to use SOL Proxy. By default, you will be logged in the menu mode. See "SOL Proxy Main Menu" on page 83 for further instructions.

The following line edit functions are supported during the SOLProxy session:

Up- and down- arrow keys to browse command history.

Left- and right- arrow keys to move the input cursor.

Using a Linux Shell

To connect and use SOL Proxy:

Open a Linux shell on your management station.

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" on page 93.

If you are prompted for a username, provide the operating system login credentials of SOL Proxy Server.

localhost

or an IP address of 127.0.0.1 is used, it is assumed that the user has login privileges to the current host, and is not prompted for a username and password.

82 Using the BMC Management Utility

After authentication, a login successful message and the SOL Proxy main menu prompt appear. You are ready to use SOL Proxy. See "SOL Proxy Main Menu" on page 83 for further instructions.

SOL Proxy Main Menu

After the telnet connection with SOL Proxy is successfully established, you are presented with the following choices. See Figure 3-16.

Figure 3-16. 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.” If you select menu options 2, 3, or 4, and the application state is not “connected,” you are prompted to connect to a BMC.

Using the BMC Management Utility 83

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. Menu option 3 establishes a SOL session without changing the remote system’s state. This option is ideal for connecting to the Microsoft SAC/EMS or the Linux console. Menu option 4 reboots the remote managed system and establishes a SOL session. This option is best suited for performing BIOS setup and system configuration tasks.

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.

Select option 1 in the main menu.

Enter the BMC IP address of the remote managed system.

Provide the BMC username and password for the BMC on the managed system. The BMC username and password must be assigned and stored in the BMC non-volatile storage. See "Configuring Your Managed System" on page 25 for more information about configuring BMC users. Only one SOL session with one BMC is permitted at one time.

The connection status displays on the main menu. See Figure 3-17.

Provide the IPMI encryption key if it was configured in the BMC.

84 Using the BMC Management Utility

Figure 3-17. 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, 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. See "Connecting to the Remote Managed System’s BMC" on page 84 for more information.

Using the BMC Management Utility 85

The SOL configuration menu appears. According to the current SOL status, the content of the SOL configuration menu varies:

• If SOL is already enabled, the current settings are displayed and you are presented with three choices. See Figure 3-18.

Figure 3-18. Configuring the Serial-Over-LAN for the Remote System, Example 1

• If SOL is currently disabled, the options shown in Figure 3-19 are displayed. Type

to enable SOL or N to keep SOL disabled. See

Figure 3-19.

86 Using the BMC Management Utility

Figure 3-19. 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. Select the number before a value to set it as the new setting, and press <Enter> to confirm your changes. The new SOL settings are then displayed. See Figure 3-20.

Using the BMC Management Utility 87

Figure 3-20. 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" on page 84 for more information.

The remote managed system’s text console is redirected to your management station. See Figure 3-21.

NOTE: BIOS Console Redirection must be enabled on the managed system and

correctly configured before SOL can be successfully activated. See "Configuring Your Managed System" on page 25 for more information.

88 Using the BMC Management Utility

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

The power state of the remote managed system is confirmed. If power is on, you are prompted to decide between a graceful or forceful shutdown.

NOTE: This reboot feature mimics restarting the system using the server's power

Next, the power state is monitored until the status changes to on. Console redirection begins, and the remote managed system text console is redirected to your management station. Use the escape character sequence <~><.> to terminate console redirection and return to the top-level menu.

Using the BMC Management Utility 89

While the managed system reboots, you can enter the BIOS system setup program to view or configure BIOS settings. See Figure 3-22.

NOTE: Before activating the console redirection, you must first enable the console

redirection features. See "Configuring Your Managed System" on page 25 for more information.

Figure 3-22. Reboot Example

Getting Help

Select option 5 in the main menu to display detailed descriptions for each option. See Figure 3-23.

90 Using the BMC Management Utility

Figure 3-23. 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" on page 93 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. In addition to supporting all commands of the IPMI Shell interactive mode, the SOL Proxy supports the following additional commands.

Using the BMC Management Utility 91

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". See Figure 3-24.

Options

-force

This option is used to force the system to shut down. If this option is omitted, the "reboot" command is executed using a graceful shutdown.

Figure 3-24. reboot Option Example

92 Using the BMC Management Utility

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. This item defines what kind of connection can be accepted to establish a SOL Proxy telnet session. There are three possible values:

•

INADDR_ANY

server.

•

127.0.0.1

•

IP address

For examp l e:

ip=INADDR_ANY

—

SOL proxy listens for input on any interface on the

— SOL proxy listens for input on the localhost only.

—

SOL proxy listens for input on this IP address only.

Port Binding

Specifies the port at which the SOL Proxy listens for incoming connections. By default, the port is set to 623 and can be modified by the user.

This item defines the port when you telnet SOL Proxy. If this item is absent, 623 is set as the default port. For example:

port=623

Session Timeout

Specifies the time in minutes before the SOL Proxy session times out.

If there is no keyboard activity for the specified timeout period, the telnet session and the SOL session will be closed. The timeout value is specified in minutes and can be changed during SOL Proxy installation. For example:

Using the BMC Management Utility 93

session_timeout=30

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.

NOTE: When Reboot and Activate Console Redirection is selected and power for

the remote managed system is on, a power off IPMI command is issued. The power status is then continually monitored until the power status reports “off.” If power status remains “on” longer than this timeout period, Reboot and Activate Console Redirection reports an error and returns to the top-level menu. This timeout value is specified in seconds and can be changed during SOL Proxy installation.

For example:

power_off_timeout=60

Retry Interval

Specifies the period of time in seconds that the BMC waits before it tries to resend 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. For example:

retry_interval=2

Retry Count

Specifies the maximum number of times that the software tries to resend a packet if it does not receive a response from the BMC. Before each retry, the software waits for the interval specified by the retry_interval parameter. For example:

retry_count=10

User Interface

Specifies the default settings for SOL Proxy startup. The user can edit and set this comment in the command or menu mode. For example:

user_interface=menu

94 Using the BMC Management Utility

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 e xa mp le :

sol_loss_silent=0 or 1

Sol Loss Threshold

Specifies number of SOL packets that can be lost before SOL deactivation. The default value is 0, which means that the system will deactivate SOL, if any SOL packets are lost. For example:

sol_loss_silent_threshold=0

Sdr Cache

Specifies whether the system probe information is saved. This information enhances speed of providing sensor and System Event Log (SEL) data. The possible values are on and off. Default value is on. For example:

sdr_cache=on

Sdrcache Path

Specifies path where the system probe information is saved. Default location is the installed BMC directory on your hard drive. For example,

sdrcache_path=<specified path directory>

Max Session

Specifies the maximum number of concurrent SOL sessions possible. This default value is 1; any value less than 1 will be ignored or treated as 1. You cannot set more than 20 sessions. For example:

max_session=2

Logpath

Specifies the path for storing the log files. Two log files, solproxy.log and solproxyipmi.log, are created at the specified path. For example,

logpath=<specified location for log file>

Using the BMC Management Utility 95

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) 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.

• Display the 16-byte system GUID of the managed system.

• Display information from the system’s FRU.

• Display the BMC firmware information.

• Display summary information about the system event log.

• Display logged events.

• Display current status of platform sensors.

•Enable or disable SOL.

NOTE: See the IPMItool man page available on the World Wide Web for a

comprehensive list of features.

NOTE: While running ipmitool inband on Linux, if the OpenIPMI driver is not

running by default, it may cause commands to fail. To start the OpenIPMI drivers, use the command driver automatically during boot, use

service ipmi start. To set the system to start the

chkconfig ipmi on.

In addition to the operations that can be performed by a user with user-level BMC user privileges, IPMItool 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.

96 Using the BMC Management Utility

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" on page 113 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.

delloem

The delloem commands provide information on Dell-specific features.

Table 3-2 lists the delloem subcommands with a brief description.

NOTE: The vFlash info Card command can be used only for in-band access.

Table 3-2. delloem Subcommands

Command Description

lcd

powermonitor

sysinfo

sel

sensor

mac

lan

windbg

vFlash info

Displays information on and helps configure the LCD

Dell

panel in

Displays power tracking statistics information.

Displays information about your system.

Displays the system event log information.

Displays information on and helps manage your system’s sensors.

Displays information about the system NICs.

Displays the NIC selection mode information.

Controls the debugging sessions.

Displays the vFlash SD card properties.

x9xx, xx0x,

and

xx1x

systems.

Card

Options for LCD

• lcd set {mode}|{lcdquallifier}|{errordisplay}

•

lcd set mode

: Allows you to set the LCD mode and user defined

string.

Using the BMC Management Utility 97

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd set mode {none}|{modelname}|{ipv4address}|{macaddress}|{sy stemname}|{servicetag}|{ipv6address}|{ambienttemp }|{systemwatt}|{userdefined}|<text>{assettag}

NOTE: The kgkey (-k option in lanplus) is a string of 20 ASCII characters.

This feature is enhanced for xx1x systems to support the kgkey in hex. The

option is

work, ensure that this kgkey is the same as what is set on the xx1x system.

Except for the default value, the 40 character hex kgkey should start with a non–zero value. If you enter a value less than 40 characters or any non-hex values, an error message displays.

•

lcd set lcdquallifier

–x followed by a 40 character hex value. For the lanplus interface to

: Allows you to set the unit for the

system Watt and ambient temperature modes.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd set lcdquallifier {watt}|{btuphr}|{celsius}|{fahrenheit}

•

lcd set errordisplay

: Allows you to set the error display.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd set errordisplay {sel}|{simple}

•

info

: Displays information about the LCD display.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd info

•

lcd set vkvm:

To set the vKVM status,

Active

Inactive

Command Syntax:

98 Using the BMC Management Utility

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd set vkvm {active}|{inactive}

•

lcd set frontpanelaccess

: Sets the LCD mode to view and

modify, view only, or disabled.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd set frontpanelaccess{viewandmodify}|{viewonly}| {disabled}

•

lcd status

: To view the vKVM status (Active or Inactive) and to view the front panel access mode (View and Modify, View Only, or Disabled) on the LCD.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem lcd status

Options for powermonitor

•

status

: Displays the current power status of the system. The returned values denote energy consumption, peak power (in Watts), and peak amperage (in Amperes).

•

clear peakpower:

•

clear cumulativepower

•

powersupplyrating:

Resets the peak power value.

: Resets the cumulative power values.

Gets the power rating for all the power supplies

attached in rated Watts.

Command Syntax:

ipmitool -I lanplus -H <ip-address> -U <user> -P <password> -k <kgkey> delloem powermonitor powersupplyrating

•

powerconsumption

: Displays the warning threshold, failure threshold, system instantaneous headroom, and system peak headroom in Watts or BTU/hr and the instantaneous current consumption in Amperes.

Command Syntax:

Using the BMC Management Utility 99

ipmitool -I lanplus -H <ip-address> -U <user> -P <password> -k <kgkey> delloem powermonitor powerconsumption <watt|btuphr>

The system peak headroom is applicable on systems with PMBus support. The peak headroom is reported in BTU/hr or Watt. Peak Headroom (in Watts) = Input Wattage to Power Supply

–

Peak Power drawn by the system. For redundant power supplies, the minimum input wattage between the two power supplies is taken. This value is not displayed in modular systems. The system instantaneous headroom is applicable on systems with PMBus support. The instantaneous headroom is reported in BTU/hr or Watt. Instantaneous Headroom (in Watts) = Input Wattage to the Power Supply

–

Instantaneous Power drawn by the system. For redundant power supplies, the minimum input wattage between the two power supplies is taken. This value is not displayed in modular systems.

•

getpowerbudget

: Displays the maximum power, minimum power, and the power budget cap either in BTU/hr or Watt and is supported on

xx1x

systems supporting PMBus.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem powermonitor getpowerbudget <watt|btuphr>

•

setpowerbudget

BTU/hr, or Watt, or in percentage and is supported on

: Allows you to set the power budget cap either in

xx1x

systems

supporting PMBus.

Command Syntax:

ipmitool -I lanplus -H <ipaddress> -U <user> -P <password> -k <kgkey> delloem powermonitor setpowerbudget <val><watt|btuphr|percent>

NOTE: <val> should be a positive integer.

•

enablepowercap

•

disablepowercap

•

powerconsumptionhistory

: Enables set power cap.

: Disables set power cap.

power consumption history in Watts or BTU/hr for the last minute, last hour, last day, and the last week.

100 Using the BMC Management Utility

: Allows you to get the average and peak

Dell OpenManage Baseboard Management Controller User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

User’s Guide

Contents

Introduction

Supported Systems and Operating Systems

BMC Configuration and Management Tasks

Configuring the BMC

Managing the System Using BMC

BMC Action on Event

Basic BMC Alerting Over a LAN

IPMI Shell Over a LAN

IPMI Shell Over the Serial Cable

SOL Proxy Over a LAN

BMC Configuration and Management Tools

Using Deployment Toolkit

Using the BMC Management Utility

Using Server Administrator

Other Documents You May Need

Obtaining Technical Assistance

Configuring Your Managed System

BIOS Configuration

Using BIOS Console Redirection With SOL Proxy

Baseboard Management Controller Configuration

Remote Access Configuration Utility Options

Configuring Your BMC Using the Deployment Toolkit Utility

Installation and Setup for Microsoft Windows PE Operating Systems

Creating a Bootable Windows PE 2005 ISO Image

Creating a Bootable Windows PE 2.0 ISO Image

Installation and Setup for Linux Operating Systems

Basic configuration

Configuring Your BMC Using Server Administrator

Using Dell Remote Access Controller 5

Using the BMC Management Utility

Installing the BMC Management Utility

Installation Prerequisites

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

Uninstalling on Systems Running Supported Linux Enterprise Operating Systems

IPMI Shell

Using IPMI Shell

IPMI Shell Command Syntax

IPMI Shell Global Options

IPMI Shell Commands

SOL Proxy

Using SOL Proxy

Using SOL proxy in command mode

Configuring the SOL Proxy Configuration File

IPMItool