Dell OpenManage Server Administrator Version 6.5 Command Line Interface Guide

Dell OpenManage

Server Administrator

Version 6.5

Command Line

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

____________________

Information in this publication is subject to change without notice.
© 2011 Dell Inc. All rights reserved.

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

Trademarks used in this text: Dell™, PowerEdge™, and OpenManage™ are trademarks of Dell Inc.
Microsoft
or registered trademarks of Microsoft Corporation in the United States and/or other countries. SUSE™
is a registered trademark of Novell Inc. in the United States and other countries. Red Hat
Hat Enterprise Linux
countries. Intel
Intel Corporation in the United States and other countries. AMD
AMD PowerNow!™ are trademarks of Advanced Micro Devices Inc. VMware
trademark and ESX Server™ is a trademark of VMware Inc in the United States and/or other jurisdictions.
Citrix
Systems, Inc. in the United States and/or other countries.

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.

®

, Windows®, Active Directory®, MS-DOS®, and Windows Server® are either trademarks

®

®

are registered trademarks of Red Hat, Inc. in the United States and other

®

, Pentium®, and Itanium® are registered trademarks and Intel386™ is a trademark of

®

, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix

®

, AMD Opteron™, AMD-V™, and

®

is a registered

and Red

2011 - 03

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 15

Overview . . . . . . . . . . . . . . . . . . . . . . . . 15

What's New in Version 6.5

Using CLI Commands From Windows
Command Prompts

Primary CLI Commands . . . . . . . . . . . . . . . . . 18

CLI Error Checking and Error Messages

Success Messages

Failure Messages

Scripting and Comparing With the CLI

Command Syntax Overview

. . . . . . . . . . . . . . . 16

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

. . . . . . . . 19

. . . . . . . . . . . . . . . . 19

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

. . . . . . . . . 22

. . . . . . . . . . . . . . . 23

2 Using the omhelp Command . . . . . . . . . . 25

Example Help Commands . . . . . . . . . . . . . . . . 25

3 omreport: Viewing System Status

Using the Instrumentation Service . . . . . 29

Conventions for Parameter Tables . . . . . . . . . 30

Command Summary of the omreport Command

Help With the omreport Command

. . . . . . . . . . . 37

. . . . 30

Contents 3

omreport modularenclosure . . . . . . . . . . . . . . . 37

omreport about

. . . . . . . . . . . . . . . . . . . . . 38

omreport chassis/
omreport mainsystem Commands

. . . . . . . . . . . . 39

omreport chassis/
omreport mainsystem

. . . . . . . . . . . . . . . 39

omreport chassis acswitch/

omreport mainsystem acswitch . . . . . . . . . . 40

omreport chassis batteries/

omreport mainsystem batteries . . . . . . . . . . 41

omreport chassis bios/
omreport mainsystem bios

. . . . . . . . . . . . . 41

omreport chassis biossetup/

omreport mainsystem biossetup . . . . . . . . . . 41

omreport chassis currents/

omreport mainsystem currents . . . . . . . . . . . 45

omreport chassis removableflashmedia/

omreport mainsystem removableflashmedia

omreport chassis fans/

omreport mainsystem fans . . . . . . . . . . . . . 47

omreport chassis firmware/

omreport mainsystem firmware . . . . . . . . . . 47

omreport chassis frontpanel/

omreport mainsystem frontpanel . . . . . . . . . . 47

omreport chassis fru/
omreport mainsystem fru

. . . . . . . . . . . . . . 48

omreport chassis hwperformance/

omreport mainsystem hwperformance . . . . . . 48

omreport chassis info/

omreport mainsystem info

omreport chassis intrusion

. . . . . . . . . . . . . 49

. . . . . . . . . . . . . 50

omreport chassis leds/

omreport mainsystem leds . . . . . . . . . . . . . 50

omreport chassis memory/
omreport mainsystem memory

. . . . . . . . . . . 51

. . . 45

4 Contents

omreport chassis nics/
omreport mainsystem nics

. . . . . . . . . . . . . 52

omreport chassis ports/
omreport mainsystem ports

. . . . . . . . . . . . 53

omreport chassis processors/

omreport mainsystem processors . . . . . . . . . 54

omreport chassis pwrmanagement/

omreport mainsystem pwrmanagement . . . . . . 57

omreport chassis pwrmonitoring/
omreport mainsystem pwrmonitoring

. . . . . . . 58

omreport chassis pwrsupplies/

omreport mainsystem pwrsupplies

. . . . . . . . 61

omreport chassis remoteaccess/

omreport mainsystem remoteaccess . . . . . . . 62

omreport chassis slots/
omreport mainsystem slots

. . . . . . . . . . . . 63

omreport chassis temps/

omreport mainsystem temps . . . . . . . . . . . . 64

omreport chassis volts/

omreport mainsystem volts . . . . . . . . . . . . 64

omreport system Commands/
omreport servermodule Commands

omreport system/omreport servermodule

Commands for Viewing Logs

. . . . . . . . . . . 65

. . . . . 65

. . . . . . . . . . . . 66

omreport system alertaction/
omreport servermodule alertaction

. . . . . . . . 67

omreport system assetinfo/

omreport servermodule assetinfo . . . . . . . . . 69

omreport system events/

omreport servermodule events

. . . . . . . . . . 69

omreport system operatingsystem/

omreport servermodule operatingsystem . . . . . 71

omreport system pedestinations/

omreport servermodule pedestinations . . . . . . 72

omreport system platformevents/

omreport servermodule platformevents

. . . . . . 73

Contents 5

omreport system recovery/
omreport servermodule recovery

. . . . . . . . . 73

omreport system shutdown/
omreport servermodule shutdown

. . . . . . . . . 74

omreport system summary/

omreport servermodule summary . . . . . . . . . 74

omreport system thrmshutdown/

omreport servermodule thrmshutdown

. . . . . . 80

omreport system version/
omreport servermodule version

. . . . . . . . . . 81

omreport preferences Commands

. . . . . . . . . . . . 82

4 omconfig: Managing Components

Using the Instrumentation Service . . . . . 83

Conventions for Parameter Tables . . . . . . . . . 84

omconfig Command Summary . . . . . . . . . . . . . . 84

Help With the omconfig Command

omconfig about

. . . . . . . . . . . . . . . . . . . . . 90

omconfig chassis/omconfig mainsystem

omconfig chassis biossetup/
omconfig mainsystem biossetup

omconfig chassis currents/

omconfig mainsystem currents . . . . . . . . . . 107

omconfig chassis fans/
omconfig mainsystem fans

omconfig chassis frontpanel/

omconfig mainsystem frontpanel . . . . . . . . . 108

omconfig chassis info/

omconfig mainsystem info

omconfig chassis leds/
omconfig mainsystem leds

. . . . . . . . . . . 89

. . . . . . . . 92

. . . . . . . . . . 92

. . . . . . . . . . . . . 107

. . . . . . . . . . . . . 110

. . . . . . . . . . . . . 111

6 Contents

omconfig chassis memorymode/
omconfig mainsystem memorymode

. . . . . . . . 112

omconfig chassis pwrmanagement/
omconfig mainsystem pwrmanagement

. . . . . . 114

omconfig chassis pwrmonitoring/

omconfig mainsystem pwrmonitoring . . . . . . . 116

omconfig chassis remoteaccess/

omconfig mainsystem remoteaccess . . . . . . . 117

omconfig chassis temps/
omconfig mainsystem temps

. . . . . . . . . . . . 129

omconfig chassis volts/

omconfig mainsystem volts

. . . . . . . . . . . . 130

omconfig preferences

omconfig preferences cdvformat

omconfig preferences dirservice

omconfig preferences snmp

. . . . . . . . . . . . . . . . . . 132

. . . . . . . . . 132

. . . . . . . . . 132

. . . . . . . . . . . . 133

omconfig preferences useraccess . . . . . . . . 135

omconfig preferences webserver

omconfig system/omconfig servermodule

. . . . . . . . . 135

. . . . . . . 137

omconfig system alertaction/
omconfig servermodule alertaction

. . . . . . . . 137

Commands for Clearing Logs . . . . . . . . . . . 142

omconfig system pedestinations/
omconfig servermodule pedestinations

. . . . . . 142

omconfig system platformevents/

omconfig servermodule platformevents . . . . . . 143

omconfig system events/

omconfig servermodule events

. . . . . . . . . . 146

omconfig system webserver/
omconfig servermodule webserver

. . . . . . . . 149

omconfig system recovery/
omconfig servermodule recovery

. . . . . . . . . 149

omconfig system shutdown/

omconfig servermodule shutdown . . . . . . . . 151

Contents 7

omconfig system thrmshutdown/
omconfig servermodule thrmshutdown

. . . . . . 152

5 omconfig system or servermodule

assetinfo: Editing Cost of

Ownership Values . . . . . . . . . . . . . . . . . 155

User Level Required for

Adding Asset Information . . . . . . . . . . . . . 155

Adding Acquisition Information

. . . . . . . . . . . . . 155

Example Commands for
Adding Acquisition Information

Adding Depreciation Information

. . . . . . . . . . 157

. . . . . . . . . . . . 158

Example Commands for
Adding Depreciation Information

Adding Extended Warranty Information

. . . . . . . . . 158

. . . . . . . . 159

Example Command for
Adding Extended Warranty Information

Adding Lease Information

. . . . . . . . . . . . . . . . 161

. . . . . . 160

Example Command for

Adding Lease Information . . . . . . . . . . . . . 162

Adding Maintenance Information

. . . . . . . . . . . . 162

Example Command for
Adding Maintenance Information

Adding Outsource Information

. . . . . . . . . 163

. . . . . . . . . . . . . 164

Example Command for
Adding Outsource Information

. . . . . . . . . . . 165

8 Contents

Adding Owner Information

Example Command for
Adding Owner Information

. . . . . . . . . . . . . . . 165

. . . . . . . . . . . . . 166

Adding Service Contract Information . . . . . . . . . . 167

Example Command for
Adding Service Information

. . . . . . . . . . . . 167

Adding Support Information . . . . . . . . . . . . . . . 168

Example Command for
Adding Support Information

. . . . . . . . . . . . 169

Adding System Information . . . . . . . . . . . . . . . 170

Example Command for
Adding System Information

. . . . . . . . . . . . 170

Adding Warranty Information . . . . . . . . . . . . . . 171

Example Command for
Adding Warranty Information

. . . . . . . . . . . 172

6 Using the Storage Management

Service . . . . . . . . . . . . . . . . . . . . . . . . . 173

CLI Command Syntax . . . . . . . . . . . . . . . . . . 173

Syntax for Required, Optional, and
Variable Command Elements

. . . . . . . . . . . . . . 174

User Privileges for omreport storage and
omconfig storage

. . . . . . . . . . . . . . . . . . . . 176

7 omreport storage Commands . . . . . . . . 177

omreport Physical Disk Status . . . . . . . . . . . . . 178

omreport Virtual Disk Status

omreport Controller Status

omreport Enclosure Status

omreport Temperature Probe Status

. . . . . . . . . . . . . . 180

. . . . . . . . . . . . . . . 181

. . . . . . . . . . . . . . . 182

. . . . . . . 183

Contents 9

omreport Fan Status . . . . . . . . . . . . . . . . 184

omreport Power Supply Status . . . . . . . . . . . 185

omreport EMM Status

. . . . . . . . . . . . . . . 186

omreport Enclosure Slot

Occupancy Report . . . . . . . . . . . . . . . . . 187

omreport Battery Status . . . . . . . . . . . . . . . . . 187

omreport Global Information (Smart Thermal
Shutdown Status, Hot Spare Protection Policy)

. . . . 188

omreport Connector Status

omreport Cachecade Status

. . . . . . . . . . . . . . . 189

. . . . . . . . . . . . . . . 190

8 omconfig storage Commands . . . . . . . . 191

omconfig Physical Disk Commands . . . . . . . . . . . 192

omconfig Blink Physical Disk

omconfig Unblink Physical Disk . . . . . . . . . . 193

omconfig Prepare to Remove Physical Disk

omconfig Instant Erase Secured

Physical Disk . . . . . . . . . . . . . . . . . . . . 195

omconfig Initialize Physical Disk

omconfig Offline Physical Disk . . . . . . . . . . . 196

omconfig Online Physical Disk

omconfig Assign Global Hot Spare

omconfig Rebuild Physical Disk . . . . . . . . . . 199

omconfig Cancel Rebuild Physical Disk

omconfig Cancel Replace Member

omconfig Clear Physical Disk . . . . . . . . . . . 201

omconfig Cancel Clear Physical Disk

. . . . . . . . . . . . 193

. . . . 194

. . . . . . . . . . 196

. . . . . . . . . . . 197

. . . . . . . . . 198

. . . . . . 200

. . . . . . . . 201

. . . . . . . 202

10 Contents

omconfig Virtual Disk Commands

omconfig Check Consistency

omconfig Cancel Check Consistency

. . . . . . . . . . . . 202

. . . . . . . . . . . 204

. . . . . . . 204

omconfig Pause Check Consistency . . . . . . . . 205

omconfig Resume Check Consistency . . . . . . . 205

omconfig Blink Virtual Disk

omconfig Unblink Virtual Disk

. . . . . . . . . . . . 206

. . . . . . . . . . . 206

omconfig Initialize Virtual Disk . . . . . . . . . . . 207

omconfig Fast Initialize Virtual Disk

omconfig Slow Initialize Virtualize Disk

. . . . . . . . 207

. . . . . . 208

omconfig Cancel Initialize Virtual Disk . . . . . . . 209

omconfig Cancel Background Initialize

omconfig Assign Dedicated Hot Spare

. . . . . . 209

. . . . . . 210

omconfig Delete Virtual Disk . . . . . . . . . . . . 211

omconfig Format Virtual Disk

omconfig Reconfiguring Virtual Disks

. . . . . . . . . . . 211

. . . . . . . 212

omconfig Secure Virtual Disk . . . . . . . . . . . 213

omconfig Clear Virtual Disk Bad Blocks

omconfig Change Virtual Disk Policy

. . . . . . 214

. . . . . . . 214

omconfig Replace Member Virtual Disk . . . . . . 215

omconfig Rename Virtual Disk

. . . . . . . . . . . 216

omconfig Controller Commands

omconfig Rescan Controller

omconfig Enable Controller Alarm

. . . . . . . . . . . . 217

. . . . . . . . . . . . 220

. . . . . . . . . 220

omconfig Disable Controller Alarm . . . . . . . . 221

omconfig Quiet Controller Alarm

omconfig Test Controller Alarm

. . . . . . . . . . 221

. . . . . . . . . . 222

omconfig Reset Controller Configuration . . . . . 222

omconfig Create Virtual Disk

omconfig Set Controller Rebuild Rate

. . . . . . . . . . . . 223

. . . . . . . 229

omconfig Change Controller Properties . . . . . . 230

omconfig Discard Preserved Cache

omconfig Create Encryption Key

omconfig Change Encryption Key

omconfig Delete Encryption Key

. . . . . . . . 231

. . . . . . . . . . 231

. . . . . . . . . 232

. . . . . . . . . . 232

Contents 11

omconfig Set Background
Initialization Rate

omconfig Set Reconstruct Rate

omconfig Set Check Consistency Rate

. . . . . . . . . . . . . . . . . . 233

. . . . . . . . . . 233

. . . . . . . 234

omconfig Export the Controller Log . . . . . . . . 234

omconfig Import Secure
Foreign Configuration

. . . . . . . . . . . . . . . 235

omconfig Unlock DKM

Foreign Configuration . . . . . . . . . . . . . . . 235

omconfig Import Foreign Configuration

. . . . . . 236

omconfig Import/Recover

Foreign Configuration . . . . . . . . . . . . . . . 236

omconfig Clear Foreign Configuration

. . . . . . . 237

omconfig Physical Disk

Power Management . . . . . . . . . . . . . . . . 237

omconfig Set Patrol Read Mode

. . . . . . . . . . 238

omconfig Start Patrol Read . . . . . . . . . . . . 238

omconfig Stop Patrol Read

omconfig Create Cachecade

. . . . . . . . . . . . . 239

. . . . . . . . . . . . 239

omconfig Enable LKM Controller . . . . . . . . . . 240

omconfig Switch to LKM Controller

. . . . . . . . 241

omconfig Rekey LKM Controller . . . . . . . . . . 241

omconfig Switch to DKM Controller

omconfig Enable DKM Controller

omconfig Rekey DKM Controller

. . . . . . . . 242

. . . . . . . . . 242

. . . . . . . . . . 243

omconfig Unlock DKM
Foreign Configuration

. . . . . . . . . . . . . . . 243

12 Contents

omconfig Enclosure Commands

omconfig Enable Enclosure Alarm

omconfig Disable Enclosure Alarm

omconfig Set Enclosure Asset Tag

omconfig Set Enclosure Asset Name

. . . . . . . . . . . . . 244

. . . . . . . . . 245

. . . . . . . . 245

. . . . . . . . . 246

. . . . . . . 247

omconfig Set Temperature

Probe Thresholds . . . . . . . . . . . . . . . . . . 247

omconfig Reset Temperature
Probe Thresholds

. . . . . . . . . . . . . . . . . 248

omconfig Set All Temperature
Probe Thresholds

. . . . . . . . . . . . . . . . . 249

omconfig Reset All Temperature

Probe Thresholds . . . . . . . . . . . . . . . . . 250

omconfig Blink

. . . . . . . . . . . . . . . . . . . 250

omconfig Battery Commands

omconfig Start Battery Learn Cycle

omconfig Delay Battery Learn Cycle

omconfig Global Commands

. . . . . . . . . . . . . . 251

. . . . . . . . 251

. . . . . . . . 252

. . . . . . . . . . . . . . 252

omconfig Global Enable Smart

Thermal Shutdown . . . . . . . . . . . . . . . . . 253

omconfig Global Disable Smart

Thermal Shutdown . . . . . . . . . . . . . . . . . 254

omconfig Global Rescan Controller

. . . . . . . . 254

omconfig Set Hot Spare Protection Policy . . . . 255

omconfig Connector Commands . . . . . . . . . . . . 256

omconfig Rescan Connector

. . . . . . . . . . . . 256

omconfig Cachecade Commands . . . . . . . . . . . . 257

omconfig Blink Cachecade

omconfig Unblink Cachecade

omconfig Delete Cachecade

omconfig Resize Cachecade

. . . . . . . . . . . . 257

. . . . . . . . . . . 258

. . . . . . . . . . . . 258

. . . . . . . . . . . . 259

omconfig Rename Cachecade . . . . . . . . . . . 260

9 Working With CLI

Command Results

Output Options for Command Results . . . . . . . . . . 261

Controlling Command Output Display

. . . . . . . . . . . . . . . . . 261

. . . . . . . . . 261

Contents 13

Writing Command Output to a File . . . . . . . . . . . 262

Saving Command Results to a File
That Can Be Overwritten

. . . . . . . . . . . . . . 262

Append Command Results to
an Existing File

. . . . . . . . . . . . . . . . . . . 263

Selecting a Format for Your CLI
Command Output

List (lst)

. . . . . . . . . . . . . . . . . . . . . 264

. . . . . . . . . . . . . . . . . . . . . . . 265

Table (tbl) . . . . . . . . . . . . . . . . . . . . . . 266

Semicolon-separated Values (ssv)

Custom Delimited Format (cdv)

. . . . . . . . . 266

. . . . . . . . . . . 267

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

14 Contents

1

Introduction

Overview

Dell OpenManage Server Administrator (OMSA) provides a comprehensive,
one-to-one systems management solution in two ways: from an integrated,
Web browser-based graphical user interface (GUI) and from a command line
interface (CLI) through the operating system. Server Administrator is
designed for system administrators to manage systems locally and remotely
on a network. It allows system administrators to focus on managing their
entire network by providing comprehensive one-to-one systems management.

In the context of Server Administrator, a system refers to a stand-alone
system, a system with attached network storage units in a separate chassis, or
a modular system consisting of one or more server modules in a modular
enclosure.

Server Administrator provides easy-to-use management and administration of
local and remote systems through a comprehensive set of integrated
management services. Server Administrator is the sole installation on the
system being managed and is accessible both locally and remotely from the
Server Administrator home page. Remotely monitored systems may be
accessed by dial-in, LAN, or wireless connections.

Configuration features allow Server Administrator to perform essential tasks
described in detail in the following sections. This CLI guide documents all
the commands that apply to Server Administrator and Storage Management.

Introduction 15

The reporting and viewing features allow retrieval of overall health status for
systems on your network. At the component level, you can view information
about voltage, temperature, fan’s

revolutions per minute (

RPM), memory
functioning, and many other critical component details. You can see a
detailed account of cost of ownership (COO) facts about your system in a
summary view. You can retrieve version information for BIOS, firmware,
operating system, and all installed software is easy to retrieve.

NOTE: You can use the CLI instead of the Server Administrator home page, and turn

the Server Administrator Web server off if you have encryption concerns. The CLI
does not use the Web server. Use the omconfig system webserver action=stop
command to turn off the Web server. The Web server starts automatically after a
reboot, so this command must be issued each time a system starts up. See "omconfig
system webserver/omconfig servermodule webserver" on page 149 for more
information.

NOTE: After installing the Dell OpenManage Server Administrator, ensure that you

log out and log in to reset the path to access Dell OpenManage CLI utilities.

NOTE: For information on terms used in this document, see the Glossary at

support.dell.com.

What's New in Version 6.5

The release highlights of OpenManage Server Administrator 6.5:

• Added support for the following operating systems:

– VMware ESX 4.0 U3

– VMware ESX 4.1 U1

–VMware ESXi 4.1 U1

–VMware ESXi 4.0 U3

– Citrix XenServer 5.6 FP1

– Microsoft Windows Small Business Server 2011

– Microsoft Windows 2008 R2 SP1

16 Introduction

• Deprecated the following operating systems:

– Red Hat Enterprise Linux 4.x

– VMware ESX 4.0 U2

– VMware ESX 4.1

– VMware ESXi 4.0 U2

– VMware ESXi 4.1

– Citrix XenServer 5.6

•New Platforms supported

–PowerEdge R210 II

– PowerEdge T110 II

• Server Administrator reports whether a Converged Network Adapter
(CNA) has Fibre Channel over Ethernet (FCoE)/iSCSI over Ethernet
(iSoE) capability or not. Also, Server Administrator supports new team
types for CNA cards. For more information on team types, refer to the
online help.

• Added support for a new memory redundancy mode called Double Device
Data Correction (DDDC).

• Added support for display of Lifecycle Controller/Unified Server
Configurator (USC) version information. To display this information, the
minimum iDRAC version for Dell monolithic systems is 1.70 and for Dell
modular systems is 3.20.

• Added support for 32x32 GB Dual In-line Memory Module (DIMM) for
Server Administrator to report the correct memory capacity.

• Supports Express Service Code for Direct-Attached Storage.

NOTE: For the supported operating systems list, see the Dell Systems Software

Support Matrix. To access this document, go to support.dell.com/manuals, click

Software, and select your product.

NOTE: CLI commands are not supported on systems with VMware ESXi operating

system.

Introduction 17

Using CLI Commands From Windows Command Prompts

If you are running the Microsoft Windows operating system, use the 32-bit
command prompt to issue a Server Administrator CLI command. You can
access the 32-bit command prompt using one of the following methods:

•Click

•Click

Start Programs Accessories Command Prompt

Start

NOTE: Do not type command into the Run dialog box to launch a command line

window; this activates the MS-DOS emulator command.com, which has
environment variable limitations that can cause subtle problems with the CLI.

Run

and type

cmd.exe

Primary CLI Commands

The commands that carry out the functions of Server Administrator are:

•

omconfig

•

omhelp

•

omreport

The omconfig command writes values that you assign to an object's
properties. You can specify values for warning thresholds on components or
prescribe what action your system is to take when a certain warning or failure
event occurs. You can also use the omconfig command to assign specific
values to your system's asset information parameters, such as the purchase
price of the system, the system's asset tag, or the system's location.

The omhelp command displays short text help for CLI commands.
The shorthand equivalent of omhelp is the command for which you want
help followed by -?. For example, to display help for the omreport command,
type one of the following commands:

omhelp omreport

omreport -?

The omreport command displays reports of the management information of
your system.

NOTE: For an overall summary of CLI commands, type omhelp.

Table 1-1 lists the primary CLI commands used by Server Administrator.
This guide contains a section for each primary command.

18 Introduction

Table 1-1. CLI Commands and Sections in This Guide

Primary CLI
Command

omconfig "omconfig: Managing Components

omhelp "Using the omhelp Command" on

omreport "omreport: Viewing System Status

NOTE: omupdate commands are no longer supported in Server Administrator and

are replaced by Dell Update Package or Server Update Utility commands. To update
the different components, download the Dell Update Package and run <package

name> /s [/f]. For more information on corresponding CLI syntax, see the Dell Update
Packages for Operating Systems User’s Guide or the Dell OpenManage Server Update
Utility User’s Guide at support.dell.com/manuals.

Section Title Related Sections

"omconfig system or
Using the Instrumentation Service"
on page 83

page 25

Using the Instrumentation Service"
on page 29

servermodule assetinfo: Editing

Cost of Ownership Values" on

page 155

Additional useful topics about the CLI include:

• "Working With CLI Command Results" on page 261

CLI Error Checking and Error Messages

When you type CLI commands, the CLI checks these commands for correct
syntax. If you type a command and the command is executed successfully,
a message displays, stating that your command has been successful.

Success Messages

When you type a successful omconfig command, data for that
component displays.

The following omconfig command examples displays valid CLI commands
and their success messages:

Command:

omconfig chassis temps index=0 warnthresh=default

Introduction 19

Message:

Temperature probe warning threshold value(s) set
successfully.

Command:

omconfig chassis biossetup attribute=numlock
setting=on

Message:

BIOS setup configured successfully. Change will
take effect after the next reboot.

Command:

omconfig system assetinfo info=depreciation
duration=6

Message:

Asset information set successfully.

Failure Messages

CLI failure messages provide reasons why some commands do not succeed.
Some common reasons why commands fail include syntax errors and
components that are not present. Many error messages provide syntax
information that you can use to execute the command successfully.

If you try to execute a command for a component or feature not present in
your system configuration, the error message states that the component is not
present.

Command:

omconfig chassis volts index=3 minwarnthresh=

3.3000

20 Introduction

Example message:

Error! Number with up to 3 digits after decimal
point expected, read 3.3000

The value given by the command specifies more than
3 digits after the decimal point. A valid minimum
warning threshold value for volts contains up to
3 digits after the decimal point.

Ty p e :

omconfig chassis volts index=3 minwarnthresh=3.300

When you type the revised command with three decimal points, you receive
another error message:

Error! This voltage probe min warning threshold
must be between 11.400 and 12.480.

Revised command:

omconfig chassis volts index=3 minwarnthresh=

11.500

Message:

Voltage probe warning threshold(s) set
successfully.

Introduction 21

Scripting and Comparing With the CLI

The Server Administrator CLI allows administrators to write batch programs
or scripts to be executed by the operating system. For an enterprise with many
systems, an administrator could write a configuration script that specified the
warning thresholds for each major component of a system and also specified
a set of actions that the administrator wants each system to take in case of
a warning or failure event. In the most critical cases, the administrator could
write a script so that the system shuts down to prevent damage.
The administrator could then distribute and execute the script to many
managed systems at the same time. Such a scenario facilitates configuring
any number of new systems acquired by a company and makes
implementation of new system administration policies easier across many
existing systems that require reconfiguration.

A similar scenario could be used to populate a large number of newly acquired
systems with detailed asset information. Much of the information would be the
same, such as the manufacturer or lessor of the system, whether support for the
system is outsourced, insurance company name of the system, method of
depreciation, and so on. Any variable that is common to all systems could be
scripted, sent to all managed systems, and executed. Asset information that is
unique to a system could be scripted as a group and sent to that managed
node for execution. For example, a script could specify values for all unique
variables such as owner, primary user phone number, asset tag, and so on.
Scripts to populate unique values would set all unique variables at once rather
than one by one through the system's command line.

In many cases, the CLI allows a user with a very well-defined task in mind to
retrieve information about the system rapidly. If a user wants to review a
comprehensive summary of all system components and save that summary
information to a file for comparison with later system states, the CLI is ideal.

Using CLI commands, administrators can write batch programs or scripts to
execute at specific times. When these programs execute, they can capture
reports on components of interest, such as fan RPMs during periods of high
system usage compared with the same measurements at times of lowest
system usage. Command results can be routed to a file for later analysis.
Reports can help administrators gain information that can be used to adjust
usage patterns, to justify purchasing new system resources, or to focus on the
health of a problem component.

22 Introduction

Command Syntax Overview

Commands vary in complexity. The simplest command has only command
level 1. The omhelp command is a simple command. When you type
omhelp, a list of the main CLI commands is displayed.

The next level of complexity includes commands that contain command
levels 1 and 2. All of the about commands are examples of command level 2
complexity. The omconfig about and omreport about commands cause a
very brief summary to display. The summary shows version information for
the systems management software installed on your system; for example,
Server Administrator 1.x.

Some commands have command level 1 and command level 2 and one
name=value pair. Consider the following example command that instructs
Server Administrator for more details about the environment for Server
Administrator:

omreport about details=true

Command level 1 is omreport, command level 2 is about, and the name=
value pair is details=true.

Many commands use command level 1, command level 2, and command
level 3, but do not require any parameters (name=value pairs). Most
omreport commands are of this type. For example:

omreport system alertaction

causes a list of alert actions that are configured for components on your
system to be displayed.

The most complex commands have all three command levels and can
have multiple name=value pairs. An example of two name=value pairs:

omconfig system assetinfo info=depreciation
duration=3

An example of nine name=value pairs:

omconfig system assetinfo info=acquisition
purchasecost=
purchasedate=<mmddyy> ponum=
expensed=<yes | no> costcenter=<text>

<n> waybill=<n> installdate=<mmddyy>

<n> signauth=<text>

Introduction 23

In each section, command syntax and other information about commands is
formatted with any of the following fields that apply:

command
level 1

command
level 2

command
level 3

name=value
pair 1

name=value
pair 2

24 Introduction

2

Using the omhelp Command

The omhelp command and its equivalent, <command> -?, accesses
the detailed help text interface of Command Line Interface (CLI). You can
get help at several levels of detail.

Each fully qualified CLI command may have a variable number of distinct
parts: the command (command level 1), one or more subcommands
(command level 2 and command level 3, if present), and one or more name=
value pair(s).

By appending -? (space-dash-question mark) to any command, you can get
help for that command.

Example Help Commands

When you type omconfig -?, you get general help about the omconfig
command. The help at this level lists the available subcommands for
omconfig:

•about

• preferences

•chassis

•system

When you type omconfig system -?, CLI help lists all the
subcommands available for omconfig system:

•alertaction

•alertlog

•assetinfo

•cmdlog

•esmlog

•events

• platformevents

• pedestinations

Using the omhelp Command 25

• recovery

• shutdown

• thrmshutdown

• webserver

Figure 2-1 shows the levels of help for a command.

Figure 2-1. Different Levels of Help for a Command

You can also parse the omconfig system assetinfo command as follows:

<command level 1 command level 2 command level 3>
<name=value pair 1> [name=value pair 2]

where command levels 1, 2, and 3 are represented by omconfig system assetinfo,
name=value pair 1 is represented by info=depreciation, and name=value pair 2
is represented by method=straightline.

To set your depreciation method to straight line, type:

omconfig system assetinfo info=depreciation
method=straightline

The CLI responds with the following message:

Asset information set successfully.

When you type omconfig system assetinfo -?, the help that
displays provides information about assigning values for the name and
option fields. Partial results for the request omconfig system assetinfo -? are
as follows:

assetinfo Set asset information.

26 Using the omhelp Command

For one info value, specify one or more optional parameter(s).
Table 2-1 displays the optional parameters for info=acquisition:

Table 2-1. Optional Parameters

Info Value Optional parameters

Info=acquisition purchasecost=<num>

waybill=<num>
installdate=<mmddyy>
purchasedate=<mmddyy>
ponum=<num>
signauth=<text>
expensed=<yes|no>
costcenter=<text>
info=depreciation
method=<text>
duration=<num>
percent=<percent>
unit=<months|years|unknown>

Using the omhelp Command 27

28 Using the omhelp Command

3

omreport: Viewing System Status Using the Instrumentation Service

The omreport command allows you to see detailed information about
your system components. You can retrieve summaries for many system
components at one time, or you can get details about a specific component.
This chapter shows you how to get reports with the level of detail that you
want.

Commands documented in this chapter vary in whether they define the fields that
appear in the results of a particular omreport command. Fields are defined only
if they have a special or less familiar use.

As with all other components, you can use omreport to view component
status, and omconfig to manage a component. For information on
configuring components for management, see "omconfig: Managing
Components Using the Instrumentation Service" on page 83.

You can use omreport commands to get information you need to execute an
omconfig command. For example, if you want to edit the minimum
temperature for a warning event on a temperature probe, you need to know
the index of the probe you want to configure. You can use omreport chassis
temps to display a list of probes and their indexes.

Table 3-1. System Availability for the omreport Command

Command Level 1 Command Level 2 Applicable To

omreport modularenclosure Modular system

servermodule Modular system

mainsystem Modular system

system Non-modular system

chassis Non-modular system

preferences Modular/Non-modular

system

omreport: Viewing System Status 29

Conventions for Parameter Tables

When listing the parameters that a command can take, the parameters are
listed in alphabetical order instead of the order in which they appear in the
command line interface.

The symbol |, often called pipe, is the logical exclusive or operator.
For example, enable | disable means that you can enable or disable the
component or feature, but you cannot simultaneously enable and disable the
component or feature.

Command Summary of the omreport Command

NOTE: Although this chapter lists all possible omreport commands, the commands

available on your system depend on your system configuration. The results of the
omreport command vary from one system to another. Data displays for installed
components only.

NOTE: When a system includes an external chassis, the displayed results vary by

operating system. On SUSE Linux Enterprise Server and Red Hat Enterprise Linux
systems, omreport commands display external chassis information in a separate
section after the main chassis information. On Microsoft Windows systems, data
about the external chassis does not appear in the omreport output.

Table 3-2 is a high-level summary of the omreport command. The column
titled Command level 1 shows the omreport command at its most general.
Command level 2 shows the major objects or components that you can view
using omreport (about, chassis, storage, and system). Command level 3 lists
the specific objects and components for which you can view reports. User
privilege required refers to the type of privilege you need to perform the
command, where U=User, P=Power User, and A=Administrator. Use is
a very general statement about the actions that can be performed using
omreport. More details about syntax and use of the command appear later in
this section.

Tab le 3- 2 di spl ays the omreport commands available for about, system, and
main system chassis. For information about viewing storage components,
see "omreport: Viewing System Status Using the Instrumentation Service" on
page 29.

30 omreport: Viewing System Status

Table 3-2. Command Level 1, Level 2, and Level 3 for omreport

Command
Level 1

omreport

Command Level 2 Command

Level 3

User
Privilege
Required

Use

modularenclosure U, P, A Shows information

for all the modular
chassis.

about U, P, A Shows version

number and
properties for Server
Administrator.

details=true U, P, A Displays information

for all the Server
Administrator
programs installed.

chassis/mainsystem U, P, A Shows the general

status of all the main
components.

acswitch U, P, A Shows failover

settings where
redundant AC power
lines are supported in
a system.

batteries U, P, A Shows the properties

set for batteries.

bios U, P, A Shows BIOS

information such as
manufacturer,
version, and release
date.

biossetup A Shows BIOS setup

properties configured
during system boot.

omreport: Viewing System Status 31

Table 3-2. Command Level 1, Level 2, and Level 3 for omreport

(continued)

Command
Level 1

Command Level 2 Command

Level 3

fans U, P, A Shows the status and

firmware U, P, A Shows the name and

frontpanel U, P, A Shows whether the

fru U, P, A Shows the Field

hwperformance U, P, A Shows the status and

info U, P, A Shows a status

intrusion U, P, A Shows the status of

User
Privilege
Required

Use

thresholds for system
fans.

version of the
firmware.

front panel button
settings, such as the

Power button and/or
Nonmasking
Interrupt (NMI)

button (if present on
the system), are
enabled or disabled. It
also displays the front
panel encryption
access information
and the front panel
LCD information.

Replaceable Unit
(FRU) information.

cause for the system’s
performance
degradation.

summary for main
system chassis
components.

the system’s intrusion
sensor(s).

32 omreport: Viewing System Status

Table 3-2. Command Level 1, Level 2, and Level 3 for omreport

(continued)

Command
Level 1

Command Level 2 Command

Level 3

leds U, P, A Shows the properties

memory U, P, A Shows properties of

nics U, P, A Shows the NIC and

ports U, P, A Shows the properties

processors U, P, A Shows properties of

pwrmanagement U, P, A Shows power

pwrmonitoring U, P, A Shows properties of

pwrsupplies U, P, A Shows properties of

User
Privilege
Required

Use

you have set for
light-emitting diodes
to flash under various
alert conditions.

your system's memory
arrays.

Team interface
properties.

for your system’s
parallel and serial
ports, such as I/O
address, IRQ level,
connector type, and
maximum speed.

your system’s
processors, including
speed, manufacturer,
and processor family.

inventory details such
as system idle power,
system maximum
potential power, and
power budget
information.

power consumption.

power supplies.

omreport: Viewing System Status 33

Table 3-2. Command Level 1, Level 2, and Level 3 for omreport

(continued)

Command
Level 1

Command Level 2 Command

Level 3

User
Privilege
Required

Use

remoteaccess U, P, A Shows general

information on
remote access.

slots U, P, A Shows properties of

your system’s
expansion slots and
other slot types.

temps U, P, A Shows the status and

thresholds for the
system temperature
sensors.

volts U, P, A Shows the status and

thresholds for the
system voltage
sensors.

removableflashmedia U, P, A Shows the system’s

virtual flash (vFlash)
and secure digital
(SD) card details.

storage U, P, A See "Using the

Storage Management
Service" on page 173.

system/servermodule U, P, A Shows a high-level

summary of system
components.

alertaction U, P, A Shows warning and

failure threshold
values, as well as
actions configured
when an essential
component detects
a warning or
failure state.

34 omreport: Viewing System Status

Table 3-2. Command Level 1, Level 2, and Level 3 for omreport

(continued)

Command
Level 1

Command Level 2 Command

Level 3

alertlog U, P, A Allows the

assetinfo U, P, A Shows the cost of

cmdlog U, P, A Allows the

esmlog U, P, A Allows the

events U, P, A Shows the system’s

operatingsystem U, P, A Shows the name and

pedestinations U, P, A Shows destinations

platformevents U, P, A Shows the system’s

User
Privilege
Required

Use

administrator to
display the alert log.

ownership
information for
your system.

administrator to
display the
command log.

administrator to
display the
hardware log.

Simple Network
Management
Protocol (SNMP)
event settings.

version of your
operating system.

where alerts for
platform events are
configured to be sent.

response for each
listed platform event.

omreport: Viewing System Status 35

Table 3-2. Command Level 1, Level 2, and Level 3 for omreport

(continued)

Command
Level 1

Command Level 2 Command

Level 3

User
Privilege
Required

Use

recovery P, A Shows how your

system is configured
to respond to a hung
operating system.

shutdown P, A Shows how the

shutdown action is to
be performed.

summary U, P, A Shows the key facts

for all system
components,
including main
system chassis,
software, and storage.

thrmshutdown P, A Shows the shutdown

action, if any, to be
taken when a
temperature warning
or failure condition is
detected.

version U, P, A Shows a summary for

all updatable
components on your
system.

preferences webserver U, P, A Shows the URL

information of your
Server Administrator
Web ser v er.

36 omreport: Viewing System Status

Help With the omreport Command

Use the omreport -? command to get a list of the available commands
for omreport.

Use omreport
and system commands. The following information on omreport system -? also
applies to get help for the omreport chassis command.

To see a list of valid commands for omreport system, type:

omreport system -? | more

<command level 2> -?

to get help on the level 2 about, chassis,

omreport modularenclosure

Use the omreport modularenclosure command to view details of the
modular system. Type:

omreport modularenclosure

NOTE: This CLI command is available when Dell OpenManage Server

Administrator is installed on Dell modular systems.

Server Administrator displays information related to the modular enclosure
and chassis management controller CMC (if available):

NOTE: The output varies depending on the configuration of your system.

Modular Chassis Information

Chassis Information

Attribute : Model

Value : Modular Server Enclosure

Attribute : Lock

Value : true

Attribute : Service Tag

Value : 8RLNB1S

Attribute : Express Service Code

Value : 18955029124

CMC Information

omreport: Viewing System Status 37

Attribute : Product

Value : Chassis Management Controller (CMC)

Attribute : Description

Value : The system component provides a

complete set of remote management
functions for Dell systems.

Attribute : Version

Value : 3.20

Attribute : IP Address

Value : 101.102.103.104

Attribute : IP Address Source

Value : Dynamic Source

Attribute : IP Address Type

Value : IPv4

Attribute : Remote Connect Interface

Value : Launch CMC Web Interface

omreport about

Use the omreport about command to learn the product name and version
number of the systems management application installed on your system.
The following is an example output from the omreport about command:

Product name :Dell OpenManage Server Administrator
Version :6.x.x
Copyright :Copyright (C) Dell Inc. xxxx-xxxx. All

rights reserved.

Company :Dell Inc.

For details about the environment for Server Administrator, type:

omreport about details=true

38 omreport: Viewing System Status

Server Administrator includes a number of services, each of which has a
version number of its own. The Contains field reports version numbers for
the services as well as other useful details. The output below is an example,
and can change depending on your system’s configuration and the version of
Server Administrator installed on your system:

Contains: Instrumentation Service 6.x.x

Storage Management Service 2.x.x
Sun JRE - OEM Installed Version 1.x.x
Secure Port Server 3.x.x
Core Service 1.x.x
Instrumentation Service Integration Layer

1.x.x
Storage Management Service Integration

Layer 1.x.x
Server Administrator 6.x.x

omreport chassis/omreport mainsystem Commands

Use the omreport chassis or omreport mainsystem commands to view details
for the entire chassis or for a particular component.

omreport chassis/ omreport mainsystem

Ty p e :

omreport chassis
or
omreport mainsystem

omreport: Viewing System Status 39

Server Administrator displays a general status for your main system
chassis/main system components.

SEVERITY : COMPONENT
Ok : Fans
Critical : Intrusion
Ok : Memory
Ok : Power Supplies
Ok : Temperatures
Ok : Voltages

omreport chassis acswitch/omreport mainsystem acswitch

Use the omreport chassis acswitch or omreport mainsystem acswitch
command if your system has redundant AC power lines that are configured in
a failover arrangement. Type:

omreport chassis acswitch
or
omreport mainsystem acswitch

Server Administrator displays the following output:

AC Failover Switch
AC Switch Redundancy

Redundancy Status : Full
Number of devices

required for full
redundancy

Redundancy Mode :
Redundancy

Configuration

AC Power Lines
Status : Ok
Location : AC Power Line 1
AC Present : Power Present
Active Source : Active
Status : Ok

:2

: Input Source Line 1, upon

redundancy restoration,
return to Line 1

40 omreport: Viewing System Status

Location : AC Power Line 2
AC Present : Power Present
Active Source : Not Active

Server Administrator reports values for the Redundancy Status and
Redundancy Mode fields.

omreport chassis batteries/omreport mainsystem batteries

Use the omreport chassis batteries or omreport mainsystem batteries
command to view battery properties. Type:

omreport chassis batteries
or
omreport mainsystem batteries

Server Administrator displays the summary of the battery information for
your system.

omreport chassis bios/omreport mainsystem bios

Use the omreport chassis bios/omreport mainsystem bios command to view
the current BIOS information. Type:

omreport chassis bios
or
omreport mainsystem bios

Server Administrator displays the summary of the BIOS information for
your system.

omreport chassis biossetup/omreport mainsystem biossetup

Use the omreport chassis biossetup or omreport mainsystem biossetup
command to view BIOS setup parameters that are normally available only
during system boot. Type:

omreport chassis biossetup
or
omreport mainsystem biossetup

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

omreport: Viewing System Status 41

Tab le 3- 3 di spl ays the ava ila ble BIOS setup parameters:

NOTE: All the BIOS Setup parameters are not displayed. Only those BIOS setup

properties configured during system boot are displayed.

Table 3-3. BIOS Setup Parameters

Parameters Description

Attribute

Bootsequence Displays the device used to boot the system.

Numlock Displays whether the keypad can be used as number keys.

Embedded Video
Controller

Boot Mode Displays whether the boot mode is configured to BIOS or

Processor C1-E Displays the Processor C1-E status.

CPU Execute Disable Displays whether the Execute Disable (XD) option is

Processor C State
Control

Processor CMP Displays the number of cores enabled per processor.

User accessible USB
Ports

CPU Virtualization
Te ch n o lo g y

AC Power Recovery
Mode

Embedded SATA
Controller

SATA port 0 Displays the state of SATA port 0.

SATA Port 1 Displays the state of SATA port 1.

Dual NIC (1/2) Displays whether NIC 1 and NIC 2 with PXE/iSCSI is

Dual NIC (3/4) Displays whether NIC 3and NIC 4 with PXE/iSCSI is

Displays whether the Embedded Video Controller option is
enabled or disabled.

Unified Extensible Firmware Interface (UEFI).

enabled or disabled.

Displays whether the Processor C State Control option is
enabled or disabled.

Displays whether the user-accessible USB port is enabled or
disabled.

Displays the additional hardware capabilities provided by
Virtualization Technology.

Displays the system state when input power is restored after
an outage.

Displays whether the embedded SATA controller is set to
ATA mode, RAID mode, or is disabled.

enabled or disabled.

enabled or disabled.

42 omreport: Viewing System Status

Table 3-3. BIOS Setup Parameters

Parameters Description

NIC 1 Displays whether the first NIC is enabled (with or without

PXE/iSCSI) or disabled during system boot.

NIC 2 Displays whether the second NIC is enabled (with or

without PXE/iSCSI) or disabled during system boot.

NIC 3 Displays whether the third NIC is enabled (with or without

PXE/iSCSI) or disabled during system boot.

NIC 4 Displays whether the fourth NIC is enabled (with or

without PXE/iSCSI) or disabled during system boot.

Trusted Cryptographic
Module (TCM)

Tru s te d P la tf or m
Module (TPM)
Security

Internal USB Port
(number)

Operating System
Wat ch do g T i me r

HT Assist Displays the status of the probe filter chipset option.

Internal SD Card Displays whether the internal SD card is enabled or

Bezel Displays whether the bezel removal intrusion check during

Console Redirection Displays if the BIOS screen is redirected over a particular

Diskette Displays whether the diskette is disabled, auto enabled, or

Demand Based Power
Management (DBS)

Embedded Hypervisor Displays whether the embedded hypervisor is enabled or

IDE Displays whether the drive is enabled or disabled.

Displays if TCM is on or off.

Displays if TPM is off, on with pre-boot measurements, or
on without pre-boot measurements.

Displays if the internal USB is enabled or disabled.

NOTE: Server Administrator may not display the USB

sequence number if there is only one USB port on the system.

Displays whether the operating system watchdog timer is
enabled or disabled.

disabled.

system reboot is enabled or disabled.

serial port or if it is turned off.

read-only.

Displays whether DBS is enabled or disabled on the system.

disabled.

(continued)

omreport: Viewing System Status 43

Table 3-3. BIOS Setup Parameters

Parameters Description

IDE Primary Drive 0 Displays whether the device is automatically detected and

enabled or if the device is disabled.

IDE Primary Drive 1 Displays whether the device is automatically detected and

enabled or if the device is disabled.

Intrusion Displays whether the intrusion check is enabled or disabled

during system boot.

Mouse Displays whether the mouse is enabled or disabled.

Optical Drive
Controller

Parallel port address Displays whether the address is located on LPT1, LPT2, and

Parallel port mode Displays the setting associated with the parallel port.

Primary SCSI Displays whether the device is on or off.

RAID on motherboard Displays whether RAID-on-motherboard is detected as a

RAID Channel A Displays whether RAID-on-motherboard Channel A is

RAID Channel B Displays whether RAID-on-motherboard Channel B is

SATA

Serial Port 1 Displays whether serial port 1 is mapped to a COM port, a

Serial Port 2 Displays whether serial port 2 is mapped to a COM port, a

Speaker Displays whether the speaker is on or off.

USB or USBB Displays whether the USB port is enabled or disabled.

Secondary SCSI Displays whether the device is enabled or disabled.

Serial Communications Displays whether COM port 1 and COM port 2 are off or on

Displays whether the optical drive controller is enabled or
disabled.

LPT3, or if it is disabled.

RAID device, a SCSI device, or if the device is disabled
during system boot.

detected as a RAID device or a SCSI device.

detected as a RAID device or a SCSI device.

COM port 1, a COM port 3, a COM1 BMC, a BMC Serial,
a BMC NIC, a BMC RAC, or is disabled.

COM port 2, a COM port 4, or is disabled.

with or without console redirection.

(continued)

44 omreport: Viewing System Status

Table 3-3. BIOS Setup Parameters

Parameters Description

Console Redirection
After Boot

External Serial
Connector

Console Redirection
Failsafe Baud Rate

Serial Address Select Displays port address for the serial devices.

Displays whether console redirection after system reboot is
enabled or disabled.

Displays whether the external serial connector is mapped to
Serial Device 1, Serial Device 2, or a Remote Access Device.

Displays the setting for console redirection failsafe baud
rate.

(continued)

To view all available boot devices, alias names, and boot order sequences,
type:

omreport chassis biossetup attribute=bootorder

NOTE: On Linux systems, user/user groups upgraded to

administrator/administrator groups cannot view the boot order sequence.

omreport chassis currents/omreport mainsystem currents

This command is no longer available through Server Administrator.

omreport chassis removableflashmedia/omreport mainsystem removableflashmedia

Use the omreport chassis removableflashmedia or omreport mainsystem
removableflashmedia to view the removable flash media details on the

system along with its health status. Type:

omreport chassis removableflashmedia
or
omreport mainsystem removableflashmedia

Server Administrator displays a summary of your system’s removable flash
media information.

NOTE: If the vFlash or SD card size is less than 1 GB, size is displayed in MB.

omreport: Viewing System Status 45

Depending on your configuration of your system, you may notice the
following output:

Removable Flash Media Information

Health : Critical

Internal Dual SD Module Redundancy :

Attribute

Value

Internal SD Modules Status

Status

Connector Name

State

Storage Size

Status

Connector Name

State

Storage Size

VFlash Media Details

Connector Name

Type

State

: Redundancy

: Lost

: OK

: System Board SD Status 1

: Present

: 512 MB

: OK

: System Board SD Status 2

: Present

: 512 MB

: System Board SD Status 1

: vFlash SD Card

: Present

Critical

Available Size

Storage Size

46 omreport: Viewing System Status

: 472 MB

: 512 MB

omreport chassis fans/omreport mainsystem fans

Use the omreport chassis fans or omreport mainsystem fans command to
view the fan probe status and settings. Type:

omreport chassis fans index=n
or
omreport mainsystem fans index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of status, readings, and thresholds set for
any fan probes that might be present on your system. If you specify the index,
Server Administrator displays a summary for a specific fan probe.

omreport chassis firmware/omreport mainsystem firmware

Use the omreport chassis firmware or omreport mainsystem firmware
command to view current firmware properties. Type:

omreport chassis firmware
or
omreport mainsystem firmware

Server Administrator displays a summary of your system’s firmware
properties.

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

NOTE: If iDRAC is installed, Server Administrator displays Life Cycle Controller

(LCC) version. If BMC is installed, Server Administrator displays Unified Server
Configurator (USC) version.

omreport chassis frontpanel/omreport mainsystem frontpanel

Use the omreport chassis frontpanel or omreport mainsystem frontpanel
command to view if the front panel button control settings, such as the Power
button and/or Nonmasking Interrupt (NMI) button (if present on the
system), are enabled or disabled.

If the Power button override is present on your system, you can see whether
the Power button override is enabled or not. If enabled, the Power button
turns the power to the system On and Off.

omreport: Viewing System Status 47

If the NMI button is present on your system, you can see whether the NMI
button is enabled or not. The NMI button can be used to troubleshoot
software and device errors when using certain operating systems.

The Front Panel LCD Security Access displays if the front panel encryption
access information is set to View, Modify, or Disable.

The Front Panel LCD Information displays information such as service tag,
remote indication status, and so on.

omreport chassis fru/omreport mainsystem fru

Use the omreport chassis fru or omreport mainsystem fru command to view
FRU information. When you type:

omreport chassis fru
or
omreport mainsystem fru

Server Administrator displays a summary of your system’s FRU information.
This information is available in the Server Administrator GUI, SNMP,
and Common Information Model and is primarily used to support
troubleshooting activities.

omreport chassis hwperformance/omreport mainsystem hwperformance

Use the omreport chassis hwperformance or omreport mainsystem
hwperformance command to view the status and cause for the system’s

performance degradation. When you type:

omreport chassis hwperformance
or
omreport mainsystem hwperformance

Server Administrator displays a summary of your system’s hardware
performance degradation information.

NOTE: This command is applicable only to selected Dell xx0x systems that support

PMBus.

48 omreport: Viewing System Status

Depending on your system’s configuration, you may notice the following
output:

Hardware Performance

Index

Probe Name

Status

Cause

: 0

: System Board Power Optimized

: Normal

: [N/A]

omreport chassis info/omreport mainsystem info

Use the omreport chassis info or omreport mainsystem info command to see
a summary of installed component versions:

omreport chassis info index=n
or
omreport mainsystem info index=n

The index parameter specifies a chassis number and is optional. If you do
not specify the index, Server Administrator displays summary chassis
information for each chassis. If you specify the index, Server Administrator
displays summary information for a specific chassis.

NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC

is installed, Server Administrator displays the USC version.

Depending on your system’s configuration, you may notice the following
output:

Index : 0

Chassis Name : Main System

Chassis

Host Name : everglades

Baseboard Management Controller

: 1.80

Version

Primary Backplane Version : 1.01

Sensor Data Record Version : SDR Version 0.33

Chassis Model : PowerEdge 1750

omreport: Viewing System Status 49

System Revision Name : II

Chassis Lock : Present

Chassis Service Tag : 8RLNB1S

Express service code : 19083204784

Chassis Asset Tag :

Flash chassis indentify LED state : Off

Flash chassis indentify LED
timeout value

: 300

omreport chassis intrusion

Use the omreport chassis intrusion command to find out whether the cover
of your system is open or not. Server Administrator tracks chassis intrusion
events because intrusions may indicate an attempt to steal a system
component, or to perform unauthorized maintenance on the system. Type:

omreport chassis intrusion

A message that resembles the following displays:

Status

Probe Name

State

: Ok

: Main chassis intrusion

: Chassis is closed

omreport chassis leds/omreport mainsystem leds

Use the omreport chassis leds or omreport mainsystem leds command to find
out whether clear hard drive fault is supported and what severity level lights
up the LED. Type:

omreport chassis leds index=n
or
omreport mainsystem leds index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of LED information for chassis 0. If you
specify the index, Server Administrator displays a summary for a specific
chassis.

50 omreport: Viewing System Status

The following is an example output:

Flash chassis indentify LED state

Flash chassis indentify LED timeout

: Off

: 300

value

omreport chassis memory/omreport mainsystem memory

Use omreport chassis memory or omreport mainsystem memory to view
details for each memory module slot in your system. If your system supports
redundant memory, this command also displays the status, state, and type of
memory redundancy implemented on your system. Type:

omreport chassis memory index=n
or
omreport mainsystem index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays information for all memory modules on your system.
If you specify the index, Server Administrator displays a summary for a
specific memory module.

NOTE: To maintain consistency across the commands, the output format of this

command and the subsequent command levels has changed. So, you may have to
change the user scripts as applicable.

Output for an occupied memory slot may resemble the following:

Index
Status
Connector Name
Type
Size

: 1
: OK
: DIMM_B
: SDRAM-SYNCHRONOUS
: 256 MB

An unoccupied memory slot still has a connector name. Output for an
unoccupied memory slot may resemble the following:

Index
Status
Connector Name
Type
Size

: 2
: Unknown
: DIMM_D
: Not Occupied
: Unknown

omreport: Viewing System Status 51

If your system supports redundant memory, the redundancy output may
resemble the following:

Memory Redundancy
Redundancy Status
Fail Over State
Redundancy
Configuration
Attributes of Memory
Array(s)
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1

: Full
: Inactive

: DDDC

: Location
: System Board or Motherboard
: Use
: System memory
: Installed Capacity
: 131072 MB
: Maximum Capacity
: 1048576 MB
: Slots Available
: 32
: Slots Used
: 32
: Error Correction
: Multibit ECC

omreport chassis nics/omreport mainsystem nics

Use the omreport chassis nics or omreport mainsystem nics command to
view NIC and Team interface details.

To view NIC properties, type:

omreport chassis nics index=n
or
omreport mainsystem nics index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays properties of all NICs on your system and the values
for the following fields: Index (NIC card number), Interface Name, Ven do r,
Description, Connection Status, and Slot.

52 omreport: Viewing System Status

If you specify the index, Server Administrator displays properties for a specific
NIC and the values for the following fields: Physical Interface, Interface

name, IPv4 Addresses, IPv6 Addresses, Physical Interface Receive Statistics,
Physical Interface Transmit Statistics, Interface Receive Statistics, and
Interface Transmit Statistics.

NOTE: The Fibre Channel over Ethernet (FCoE) and iSCSI over Ethernet (iSoE)

features of Converged Network Adapter (CNA) cards are not supported on VMware
ESX and VMware ESXi systems.

To view Team interface properties, type:

omreport chassis nics config=team index=n
or
omreport mainsystem nics config=team index=n

NOTE: This command is applicable only if Team interface is configured in the

system. Team interface can be configured using NIC vendor tools, such as
Broadcom.

The index parameter is optional. If you do not specify the index, Server
Administrator displays details of all the Team interfaces on your system and
the values for the following fields: Index (NIC card number), Interface
Name, Ve nd or, Description, and Redundancy Status.

If you specify the index, Server Administrator displays the Team interface
details for the specific NIC and the values for the following fields: Team

Interface, Interface, IPv4 Addresses, IPv6 Addresses, Team Interface
Receive Statistics, Team Interface Transmit Statistics, Interface Receive
Statistics, and Interface Transmit Statistics.

omreport chassis ports/omreport mainsystem ports

Use the omreport chassis ports or omreport mainsystem ports command to
view properties of your system’s parallel and serial ports.

Values display for the following fields: Port Type, External Name,

Base I/O Address, IRQ Level, Connector Type, and Maximum Speed.

Port Type is the detailed type of each system port, from the more general

serial, parallel, and USB ports to the names of ports by device type connected
to it, for example, pointing device or keyboard.

External Name is the name of the port, such as serial or parallel, USB, mouse,
keyboard, and so on.

omreport: Viewing System Status 53

Base I/O Address is the starting I/O address expressed in hexadecimal.

IRQ Level is a hardware interrupt on a system. The hardware interrupt

signals the system's CPU that an event has started or ended in a peripheral
component such as a modem or printer. When communicated over a
peripheral component interconnect card, the IRQ level is a standard way
to identify the type of device that is sending the interrupt request.

Connector Type refers to the type of plug or cable and plug that connects
two devices together, in this case, the type of connector that attaches an
external device to a system. There are many connector types, each designed
to connect a different device type to a system. Examples include DB-9 Male,
AT, Access Bus, PS/2, and so on.

Maximum Speed is the port speed. Port speed refers to the data transmission
rate of an input/output channel, measured in numbers of bits per second.
Serial ports usually have a maximum speed of 115 Kbps and USB version 1.x
ports have a maximum speed of 12 Kbps.

omreport chassis processors/omreport mainsystem processors

Use the omreport chassis processors or omreport mainsystem processors
command to view properties of your system’s processors.

Values display for the following fields: Index, Status, Connector Name,

Processor Brand, Processor Version, Current Speed, State, and Core Count.

Index is the processor number.

Status is the current status of the processor.

Connector Name is the name or number of the device that occupies the

processor slot in the system.

Processor Brand is the type of processor made by a manufacturer such as
Intel Itanium, Intel Pentium III, Intel Xeon, or AMD Opteron.

Processor Version is the model and stepping number of the processor.

Current Speed is the actual processor speed in MegaHertz at system boot

time.

State is whether the processor slot is enabled or disabled.

Core Count is the number of processors integrated into one chip.

54 omreport: Viewing System Status

Capabilities and Cache Properties of a Specific Processor

To view the cache properties of a processor on a given connector, type:

omreport chassis processors index=n
or
omreport mainsystem processors index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays properties for all processors. If you specify the index,
Server Administrator displays properties for a specific processor.

The following fields are defined for the capabilities present on a particular
microprocessor:

For Intel Processor

• 64-bit Support

•Hyperthreading (HT)

• Virtualization Technology (VT)

• Demand-Based Switching (DBS)

• Execute Disable (XD)

•Turbo Mode

For AMD Processor

• 64-bit Support

•AMD-V

•AMD PowerNow!

• No Execute (NX)

The following fields are defined for a cache present on a particular
microprocessor. If the cache is internal to the processor, the fields do not
appear in the cache report:

• Speed

• Cache Device Supported Type

• Cache Device Current Type

• External Socket Name

omreport: Viewing System Status 55

NOTE: Due to the limitations of certain operating systems (for example, VMware

ESXi), certain features may not be available with this release of OpenManage
Server Administrator.

Fields Reported for Each Cache on a Particular Processor

The following fields are displayed for each cache on a particular processor:

Status reports whether a specific cache on the processor is enabled or
disabled.

Level refers to a primary or secondary cache. Primary-level cache is a memory
bank built into the processor. Secondary-level cache is a staging area that
feeds the primary cache. A secondary-level cache may be built into the
processor or reside in a memory chipset outside the processor. The internal
processor cache is referred to as a Level 1 (or L1). L2 cache is the external
cache in a system with an Intel Pentium processor, and it is the second level
of cache that is accessed. The names L1 and L2 are not indicative of where
the cache is physically located (internal or external), but describe which cache
is accessed first (L1, therefore internal).

Speed refers to the rate at which the cache can forward data from the main
memory to the processor.

Max Size is the maximum amount of memory that the cache can hold in
kilobytes.

Installed Size is the actual size of the cache.

Ty p e indicates whether the cache is primary or secondary.

Location is the location of the cache on the processor or on a chipset outside

the processor.

A Writ e Policy describes how the cache deals with a write cycle. In a
write-back policy, the cache acts like a buffer. When the processor starts a
write cycle, the cache receives the data and stops the cycle. The cache then
writes the data back to the main memory when the system bus is available.

In a write-through policy, the processor writes through the cache to the main
memory. The write cycle does not complete until the data is stored into the
main memory.

56 omreport: Viewing System Status

Associativity refers to the way in which main memory content is stored on
the cache.

• A fully associative cache allows any line in main memory to be stored at
any location in the cache.

•A

n

-way set-associative cache directly maps n specific lines of memory to

the same

n

lines of cache. For example, line 0 of any page in memory must

be stored in line 0 of cache memory.

Cache Device Supported Type is the type of static random access memory
(SRAM) that the device can support.

Cache Device Current Type is the type of the currently installed SRAM that
the cache is supporting.

External Socket Name Silk Screen Name is the name printed on the system
board next to the socket.

Error Correction Type identifies the type of error checking and correction
(ECC) that this memory can perform. Examples are correctable ECC or
uncorrectable ECC.

This report shows cache information for each cache present on the
microprocessor.

omreport chassis pwrmanagement/omreport mainsystem pwrmanagement

Use the omreport chassis pwrmanagement or omreport mainsystem
pwrmanagement command to view the power budget cap and power

management profiles of your system. The values display either in Watts or
BTU/Hr based on the configuration. Type:

omreport chassis pwrmanagement
or
omreport mainsystem pwrmanagement

NOTE: To maintain consistency across the commands, the output format of this

command and the subsequent command levels has changed. So, you may have to
change the user scripts as applicable.

For each power management profile in the system, values display for the
following fields:

Maximum Performance, Active Power Controller, OS Control, and Custom.

omreport: Viewing System Status 57

Custom attributes are:

CPU Power and Performance Management, Memory Power and
Performance Management, and Fan Power and Performance Management.

NOTE: The omreport chassis pwrmanagement or omreport mainsystem

pwrmanagement command is applicable only to selected Dell xx1x systems that
support Power Management Bus (PMBus).

NOTE: Power Management features are only available for PowerEdge systems

that have hot-swappable power supplies and not systems that have a fixed, non­redundant power supply installed.

Power Inventory

System Idle Power

Attribute
Value
Attribute
Value

:

153 W

:

System Maximum Potential Power

:

597 W

:

Power Budget

Enable Power Cap

Attribute
Values

Attribute
Values

:

Enabled

:

Power Cap

:

400 W (56%)

:

omreport chassis pwrmonitoring/omreport mainsystem pwrmonitoring

Use the omreport chassis pwrmonitoring or omreport mainsystem
pwrmonitoring command to view the properties of your system’s power

consumption. The values display either in Watts or BTU/Hr based on the
configuration. Type:

omreport chassis pwrmonitoring
or
omreport mainsystem pwrmonitoring

58 omreport: Viewing System Status

For each power monitoring profile in the system, values display for the
following fields:

• Power Consumption Status

•Probe Name

•Reading

• Warning Threshold

•Failure Threshold

• Amperage: Location and Reading

• Power Tracking Statistics

• Energy Consumption

• Measurement Start Time

• Measurement Finish Time

•Reading

• System Peak Power

• System Peak Amperage

NOTE: The omreport chassis pwrmonitoring or omreport mainsystem

pwrmonitoring command is applicable only to selected Dell xx0x and xx1x systems
that support PMBus.

NOTE: Power Management features are only available for PowerEdge systems

that have hot-swappable power supplies and not systems that have a fixed, non­redundant power supply installed.

NOTE: To maintain consistency across the commands, the output format of this

command and the subsequent command levels has changed. So, you may have to
change the user scripts as applicable.

Table 3-4. omreport chassis pwrmonitoring/omreport mainsystem pwrmonitoring

name=value pair Description

config=stats Reports power statistics in Watts.

omreport: Viewing System Status 59

Power Consumption Information

Power Consumption

Index

Status

Probe Name

Reading

Warning Threshold

Failure Threshold

Power Headroom

Name

Reading

Name

Reading

Amperage

Location

Reading

Location

: 2

: Ok

: System Board System

Level

: 539W

: 994W

: 1400 W

: System Instantaneous

Headroom

: 300 W

: System Peak Headroom

: 340 W

: PS 1 Current 1

: 1.2 A

: PS 2 Current 2

Reading

60 omreport: Viewing System Status

: 1.0 A

Power Tracking Statistics

Statistics

Measurement Start Time

Measurement Finish

: Energy consumption

: Thu Jun 28 11:03:20 2007

: FRI Jun 28 11:05:46 2007

Time

Reading

Statistics

Measurement Start Time

Peak Time

Peak Reading

Statistics

Measured Since

Read Time

Peak Reading

: 5.9 KWH

: System Peak Power

: Mon Jun 18 16:03:20 2007

: Wed Jun 27 00:23:46 2007

: 630 W

: System Peak Amperage

: Mon Jun 18 16:03:20 2007

: Tue Jun 19 04:06:32 2007

: 2.5 A

omreport chassis pwrsupplies/omreport mainsystem pwrsupplies

Use the omreport chassis pwrsupplies or omreport mainsystem pwrsupplies
command to view properties of your system’s power supplies. Type:

omreport chassis pwrsupplies
or
omreport mainsystem pwrsupplies

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

omreport: Viewing System Status 61

For each power supply profile in the system, values display for the following
fields:

• Status

•Location

•Type

• Rated Input Wattage (in Watts)

• Maximum Output Wattage

• Online Status

• Power Monitoring Capable

omreport chassis remoteaccess/omreport mainsystem remoteaccess

Use the omreport chassis remoteaccess or omreport mainsystem
remoteaccess command to view general information on baseboard

management controller or integrated Dell remote access controller
(BMC/iDRAC) and

Ty p e :

omreport chassis remoteaccess
or
omreport mainsystem remoteaccess

NOTE: To maintain consistency across the commands, the output format of this

command and the subsequent command levels has changed. So, you may have to
change the user scripts as applicable.

The output of the omreport chassis remoteaccess/omreport mainsystem
remoteaccess command lists each of the valid parameters. Table 3-5 shows

the available settings.

remote access controller if DRAC is installed.

62 omreport: Viewing System Status

Table 3-5. omreport chassis remoteaccess/omreport mainsystem remoteaccess

name=value pair Description

config=additional Reports the current state of IPv4 and IPv6 addresses on

iDRAC6.

config=advsol Reports advanced BMC/iDRAC6 or remote access information

on a serial over local area network (LAN) connection.

config=nic Reports BMC/iDRAC6 or remote access information for the

LAN.

config=serial Reports serial port information for BMC or remote access.

config=serialoverlan Reports BMC/iDRAC6 or remote access information on a serial

over LAN connection.

config=
terminalmode

config=user Reports information on BMC/iDRAC6 or remote access users.

Reports terminal mode settings for the serial port.

omreport chassis slots/omreport mainsystem slots

Use the omreport chassis slots or omreport mainsystem slots command to
view properties of your system’s slots.

Ty p e :

omreport chassis slots index=n
or
omreport mainsystem slots index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays properties for all of the slots in your system. If you
specify the index, Server Administrator displays properties for a specific slot.

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

For each slot in the system, values display for the following fields: Index,
Slot ID, Adapter, and Data Bus Width.

Index is the number of the slot in the system.

Slot ID is the silk screen name printed on your system's motherboard next to

the slot. Alphanumeric text uniquely identifies each slot in the system.

omreport: Viewing System Status 63

Adapter refers to the name and/or type of the card that fits into the slot, for
example, a storage array controller, SCSI adapter, iDRAC6 Enterprise, or
HBA.

Data Bus Width is the width, in bits, of the information pathway between
the components of a system. The range of the data bus width can be from
16 to 64 bits.

omreport chassis temps/omreport mainsystem temps

Use the omreport chassis temps or omreport mainsystem temps command to
view properties of your system’s temperature probes. Type:

omreport chassis temps index=n
or
omreport mainsystem temps index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of status, readings, and thresholds set for
any temperature probes that might be present on your system. If you specify
the index, Server Administrator displays a summary for a specific
temperature probe.

omreport chassis volts/omreport mainsystem volts

Use the omreport chassis volts or omreport mainsystem volts command to
view properties of your system’s voltage probes. Type:

omreport chassis volts index=n
or
omreport mainsystem volts index=n

The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of status, readings, and thresholds set for
any voltage probes that might be present on your system. If you specify the
index, Server Administrator displays a summary for a specific voltage probe.

64 omreport: Viewing System Status

omreport system Commands/omreport servermodule Commands

Use the omreport system or omreport servermodule commands to view logs,
threshold values, cost of ownership information, and information about how
shutdown actions and recovery actions are configured.

omreport system/omreport servermodule

Use the omreport system or omreport servermodule command to see a
general status of the components of your system. When you specify a level 3
command, such as omreport system shutdown/omreport servermodule
shutdown, you can get detailed information for one system component rather
than the high-level status obtained with omreport system or omreport
servermodule.

Ty p e :

omreport system
or
omreport servermodule

If your system has both a main system chassis/main system and at least one
direct attached storage device, Server Administrator may display a summary
that resembles the following example:

SEVERITY : COMPONENT

Ok : Main System Chassis

Critical : Storage

omreport: Viewing System Status 65

Commands for Viewing Logs

You can use the omreport system or omreport servermodule command to
view logs: the alert log, the command log, and the hardware or ESM log.

NOTE: If the Alert log or Command log displays invalid XML data (such as when

XML data generated for the selection is not well-formed), to clear the log and
resolve the issue type: omconfig system alertlog action=clear or
omconfig system cmdlog action=clear. If you need to retain the log
information for future reference, save a copy of the log before clearing. See
"Commands for Clearing Logs" on page 142 for more information about clearing logs.

To view the contents of the alert log, type:

omreport system alertlog
or
omreport servermodule alertlog

To view the contents of the command log, type:

omreport system cmdlog
or
omreport servermodule cmdlog

To view the contents of the ESM log, type:

omreport system esmlog
or
omreport servermodule esmlog

Overall Health Status of the ESM Log

When you type omreport system esmlog or omreport servermodule esmlog,
the ESM log displays. The first line of the report reflects the overall health of
the system hardware. For example, Health: OK means that less than
80 percent of the space allotted for the ESM log is occupied by messages.
If 80 percent or more of the allotted space for the ESM log is occupied, the
following caution appears:

Health: Non-Critical

If a caution appears, resolve all warning and critical severity conditions,
and then clear the log.

66 omreport: Viewing System Status

omreport system alertaction/omreport servermodule alertaction

Use the omreport system alertaction or omreport servermodule alertaction
command to view a summary of alert actions that have been configured for
warning and failure events on your system components. Alert actions
determine how Server Administrator responds when a component has a
warning or failure event.

The omreport system alertaction or omreport servermodule alertaction
command is useful for viewing which alert actions have been specified for
components. To set an alert action for a component, use the omconfig system
alertaction or omconfig servermodule alertaction command. For more
information, see "omconfig: Managing Components Using the
Instrumentation Service" on page 83.

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

NOTE: Due to the limitations of certain operating systems (for example, VMware

ESXi), certain features may not be available with this release of OpenManage
Server Administrator.

Components and Events for Which You Can View Alert Actions

You can view alert action properties for the following components and events,
if the components/events are present on the system:

• Battery Warning

• Battery Failure

•Chassis Intrusion

•Current Probe Warning

• Current Probe Failure

•Fan Warning

•Fan Failure

• Memory Pre-failure

•Memory Failure

• System Power Probe Warning

• System Power Probe Detects a Failure

• System Peak Power

omreport: Viewing System Status 67

• Power Supply Warning

• Power Supply Failure

• Degraded Redundancy

• Lost Redundancy

• Temperature Warning

• Temperature Failure

•Voltage Warning

•Voltage Failure

• Processor Warning

•Processor Failure

•Hardware Log Warning

•Hardware Log Full

•Watchdog Asr

•Storage System Warning

•Storage System Failure

• Storage Controller Warning

• Storage Controller Failure

• Physical Disk Warning

• Physical Disk Failure

• Virtual Disk Warning

• Virtual Disk Failure

• Enclosure Warning

• Enclosure Failure

• Storage Controller Battery Warning

• Storage Controller Battery Failure

68 omreport: Viewing System Status

• Removable Flash Media Present

• Removable Flash Media Removed

• Removable Flash Media Failure

NOTE: Storage Controller Battery Warning and Storage Controller Battery Failure

events are not available on modular systems.

NOTE: System Power Probe Warning is not applicable to modular systems.

omreport system assetinfo/omreport servermodule assetinfo

Use the omreport system assetinfo or omreport servermodule assetinfo
command to see cost of ownership data for the system, such as acquisition,
depreciation, and warranty information. To set any of these fields, use the
omconfig system assetinfo or omconfig servermodule assetinfo command.
For more information, see "omconfig system or servermodule assetinfo:
Editing Cost of Ownership Values" on page 155.

omreport system events/omreport servermodule events

Use the omreport system events or omreport servermodule events command
to view the current enabled or disabled SNMP traps. This command displays
a summary of each component in your system for which events can be
generated. For each component, the report shows which severities are set to
be reported and which severities are set not to be reported. The following is
an example output for a few components:

omreport system events
or
omreport servermodule events

Current SNMP Trap Configuration

----------­System

----------­Settings
Enable: Informational, Warning and Critical
Disable: None

omreport: Viewing System Status 69

--------------­Power Supplies

---------------­Settings
Enable: Informational, Warning and Critical
Disable: None

----------­Fans

----------­Settings
Enable: Critical
Disable: Informational and Warning

--------------------­Removable Flash Media

--------------------­Settings
Enable: Informational, Warning and Critical
Disable: None

The full report lists the settings for all components in your system for which
events can be generated.

To view the status for components of a specific type, use the omreport system

events type=

<component name>

<component name>

or omreport servermodule event type=

command. This command displays a summary of each
component in your system for which events can be generated. Table 3-6
shows the events displayed for various component types.

NOTE: Due to the limitations of certain operating systems (for example, VMware

ESXi), certain features may not be available with this release of OpenManage
Server Administrator.

Table 3-6. System Events by Component Type

name=value pair Description

type=accords Reports events for AC power cords

type=battery Reports events for batteries

type=fanenclosures Reports events for fan enclosures

70 omreport: Viewing System Status

Table 3-6. System Events by Component Type

name=value pair Description

type=fans Reports events for fans

type=intrusion Reports events for chassis intrusion

type=log Reports events for logs

type=memory Reports events for memory

type=powersupplies Reports events for power supplies

type=redundancy Reports events for redundancy

type=systempower Reports events for system power

type=temps Reports events for temperatures

type=removableflashmedia Reports events for removable flash media

type=volts Reports events for voltages

Example Command for an Event Type

(continued)

Ty p e :

omreport system events type=fans
or
omreport servermodule events type=fans

The following is an example output:

----------­Fans

----------­Settings
Enable: Critical
Disable: Informational and Warning

omreport system operatingsystem/omreport servermodule operatingsystem

Use the omreport system operatingsystem or omreport servermodule
operatingsystem command to display information about your operating

system.

omreport: Viewing System Status 71

omreport system pedestinations/omreport servermodule pedestinations

Use the omreport system pedestinations or omreport servermodule
pedestinations command to view destinations where alerts for platform

events are configured to be sent. Depending on the number of destinations
displayed, you can configure a separate IP address for each destination
address.

Ty p e :

omreport system pedestinations
or
omreport servermodule pedestinations

The output of the omreport system pedestinations or omreport
servermodule pedestinations command lists each of the valid parameters.

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

NOTE: The actual number of destinations that can be configured on your system

may differ. Table 3-7 shows the available settings.

Table 3-7. Settings for the omreport system pedestinations/omreport servermodule

pedestinations

Output Attributes Description

Destination List

Destination Number:
Destination1

Destination IP Address:

101.102.103.104

Destination Number:
Destination 2

Destination IP Address:

110.120.130.140

Destination Number:
Destination 3

Destination IP Address:

201.202.203.204

destination 1: Displays the first
destination.

101.102.103.104: IP address of the first
destination.

destination 2: Displays the second
destination.

110.120.130.140: IP address of the
second destination.

destination 3: Displays the third
destination.
201:202:203:204: IP address of the third
destination.

72 omreport: Viewing System Status

Table 3-7. Settings for the omreport system pedestinations/omreport servermodule

pedestinations

Output Attributes Description

Destination
Configuration
Settings

(continued)

Destination Number:
Destination 4

Destination IP Address:

210.211.212.213

attribute=
communitystring

destination 4: Displays the fourth
destination.

210.211.212.213: IP address of the
fourth destination.

communitystring: Displays the text
string that acts as a password and is used
to authenticate SNMP messages sent
between the BMC and the destination
management station.

omreport system platformevents/omreport servermodule platformevents

Use the omreport system platformevents or omreport servermodule
platformevents command to view how the system responds for each listed

platform event.

NOTE: To maintain consistency across the commands, the output format of this

command has changed. So, you may have to change the user scripts as applicable.

omreport system recovery/omreport servermodule recovery

Use the omreport system recovery or omreport servermodule recovery
command to see whether there is an action configured for a hung operating
system. You can also view the number of seconds that must elapse before an
operating system is considered hung.

omreport: Viewing System Status 73

omreport system shutdown/omreport servermodule shutdown

Use the omreport system shutdown or omreport servermodule shutdown
command to view any pending shutdown actions for your system.
If properties for shutdown are configured, executing this command displays
these properties.

NOTE: Due to the limitations of certain operating systems (for example, VMware

ESXi), certain features may not be available with this release of OpenManage
Server Administrator.

omreport system summary/omreport servermodule summary

Use the omreport system summary or omreport servermodule summary
command to view a comprehensive summary of software and hardware
components currently installed on your system.

Example Command Output

Ty p e :

omreport system summary
or
omreport servermodule summary

NOTE: If the vFlash or SD card size is less than 1 GB, size is displayed in MB.

NOTE: If iDRAC is installed, Server Administrator displays LCC version. If BMC is

installed, Server Administrator displays the USC version.

The output that appears in your CLI window depends on the systems
management software, operating system, and hardware components and
options installed on your system. The following partial command results are
unique and may not resemble the hardware and software configuration of
your system:

74 omreport: Viewing System Status

System Summary

--------------

---­Software
Profile

--------------

---­System
Management

Name : Dell OpenManage Server

Administrator

Version : 6.x.x

Description : Systems Management Software

Contains : Instrumentation Service 6.x.x

: Storage Management Service 3.x.x

: Sun JRE - OEM Installed Version

1.x.x

: Secure Port Server 1.x.x

: Dell OpenManage Core Service 1.x.x

: Instrumentation Service Integration

Layer 1.x.x

: Storage Management Service

Integration Layer 1.x.x

Operating
System

Name : Microsoft Windows 2003 Server

Version : Service Pack 2(Build 2XXX)

System Time : Fri Sep 20 18:02:52 2XXX

System Bootup

: Wed Sep 18 18:37:58 2XXX

Time

omreport: Viewing System Status 75

System

--------------

Host Name : svctag-dxxxxs

System
Location

Model : PowerEdge 1955

Life Cycle
Controller

Asset Tag : Test

Service Tag : 6JS4V1S

Express
service code

Slot Number : Slot 01-02

Form Factor : Half Height Dual Width

Remote Access
Information

Remote Access
Device

vFlash Media : Present

vFlash Media
Type

vFlash Media
Available Size

vFlash Media
Size

: Please set the value

: Enabled

: 14256807472

: iDRAC6 Enterprise

: vFlash SD Card

: 922 MB

: 976 MB

Processor 1

Processor
Brand

Processor
Version

76 omreport: Viewing System Status

: Intel(R) Xeon(R) CPU

: Model 15 Stepping 6

Voltage : 1400 mV

Processor 2

Processor

: Intel(R) Xeon(R) CPU

Brand

Processor

: Model 15 Stepping 6

Version

Voltage : 1400 mV

Memory

Total

: 2048 MB
Installed
Capacity

Memory

: 2048 MB
Available to
the OS

Total Maximum

: 32768 MB
Capacity

Memory Array

: 1
Count

Remote Access Controller

Remote Access Controller Information

Product : iDRAC6 Enterprise

IP Address : 192.xxx.x.xxx

IP Subnet : 255.xxx.x.xxx

IP Gateway : 192.xxx.x.xxx

IPv6 Address 1 : ::

IPv6 Address 2 : ::

IPv6 Gateway : ::

Network Data

Network
Interface 0

omreport: Viewing System Status 77

IP Address : [No Value]

Network
Interface 1

IP Address : [No Value]

The system summary hardware information includes data values for installed
components of the following types present in your system:

System Attributes

• Host name

• System location

• Life Cycle Controller

Main System Chassis/Main System

Chassis

• Chassis Model

• Chassis Service Tag

•Express Service Code

• Chassis Lock

• Chassis Asset Tag

Remote Access Information

• Remote Access Device

•vFlash Media

• vFlash Media Size

78 omreport: Viewing System Status

Processor

The following are listed for each processor in the system:

• Processor Brand

• Processor Family

• Processor Version

• Current Speed

• Maximum Speed

•External Clock Speed

•Voltage

Memory

• Total Installed Capacity

• Memory Available to the Operating System

• Total Maximum Capacity

• Memory Array Count

Memory Array

The following details are listed for each memory board or module in the
system (for example, the system board or the memory module in a given
slot number):

•Location

•Use

• Installed Capacity

•Maximum Capacity

• Slots Available

•Slots Used

•Ecc Type

omreport: Viewing System Status 79

BIOS

• Manufacturer

•BIOS Version

• Release Date

Firmware

•Name

•Version

Network Data

The following details are listed for each NIC and Team interface, if Team
interface is configured in the system:

•IP Address

•Subnet Mask

•Default Gateway

•MAC Address

Storage Enclosures

The following details are listed for each storage enclosure attached to the
system:

•Name

•Service Tag

omreport system thrmshutdown/omreport servermodule thrmshutdown

Use the omreport system thrmshutdown or omreport servermodule
thrmshutdown command to view the properties configured for a thermal

shutdown action.

The three properties that display for thermal shutdown are disabled, warning,
or failure. If the CLI displays the following message, the thermal shutdown
feature has been disabled:

Thermal protect shutdown severity: disabled

80 omreport: Viewing System Status

If the system is configured to shutdown when a temperature probe detects
a warning or failure event, one of the following messages displays:

Thermal protect shutdown severity: warning
Thermal protect shutdown severity: failure

omreport system version/omreport servermodule version

Use the omreport system version or omreport servermodule version
command to list the version numbers of the BIOS, firmware, systems
management software, and operating system installed on your system.

Example Command Output

Ty p e :

omreport system version
or
omreport servermodule version

NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC

is installed, Server Administrator displays the USC version.

The output that appears in your CLI window depends on the version of the
BIOS, RAID controllers, and firmware installed on your system. The
following partial command results are unique and may not resemble the
results for the configuration of your system:

Version Report

--------------------­Main System Chassis

---------------------

Name : BIOS
Version : 0.2.16

Name : BMC
Version : 0.26

Name : Primary Backplane
Version : 1.01

omreport: Viewing System Status 81

--------------­Software

---------------

Name : Microsoft Windows Server 2003,

Enterprise Edition

Version : 5.2 <Build 3790: Service Pack 2><x86>

Name : Dell Server Administrator
Version : 6.x.x

omreport preferences Commands

Use the omreport preferences command to view the URL information of your
Server Administrator Web server.

Table 3-8 shows the available attributes.

Table 3-8. omreport preferences webserver

name=value pair Description

attribute=geturl Reports the URL information of your Web server.

attribute=getsignalgorithm Reports the current key sign algorithm.

82 omreport: Viewing System Status

4

omconfig: Managing Components Using the Instrumentation Service

The omconfig command allows you to provide values that define warning
events, configure alert actions, clear logs, and configure system shutdown,
as well as allowing you to perform other systems management tasks.

Examples of omconfig capabilities include:

• Administrator privilege to clear command, alert, and hardware logs

• Administrator privilege to configure and execute system shutdown

• Power user and administrator privilege to default or specify values for
warning events on fans, voltage probes, and temperature probes

• Power user and administrator privilege to set alert actions in the event of a
warning or failure event from intrusion, fans, voltage probes, and
temperature probes

For information on using the omconfig system command to view and manage
cost of ownership information (assetinfo), see "omconfig system or
servermodule assetinfo: Editing Cost of Ownership Values" on page 155.

Often, you must use the omreport commands to get the information you need
to execute an omconfig command. For example, if you want to edit the
minimum temperature for a warning event on a temperature probe, you need
to know the index of the probe you want to configure. You can use the
omreport chassis temps or omreport mainsystem temp command to display a
list of probes and their indexes. For more information on using the omreport
command, see "omreport: Viewing System Status Using the Instrumentation
Service" on page 29.

omconfig: Managing Components 83

Table 4-1. System Availability for the omconfig Command

Command Level 1 Command Level 2 Applicable to

omconfig servermodule Modular system

mainsystem Modular system
system Non-modular system
chassis Non-modular system

Conventions for Parameter Tables

When listing the parameters that a command can take, the parameters are
listed in alphabetical order instead of the order in which they appear in the
command line interface.

The symbol |, often called pipe, is the logical exclusive or operator. For
example, enable | disable means that you can enable or disable the
component or feature, but you cannot simultaneously enable and disable the
component or feature.

omconfig Command Summary

NOTE: Although this section lists all possible omconfig commands, the commands

available on your system depend on your system configuration. If you try to get help
or execute a command for a component not installed on your system, Server
Administrator issues a message that the component or feature is not found on
the system.

Table 4-2 is a high-level summary of the omconfig command. The columns
titled Command level 2 and Command level 3 list the major arguments that
can be used with omconfig. User privilege required refers to the type of privilege
you need to perform the command, where U=User, P=Power User, and A=
Administrator. Use is a very general statement about the actions that can be
performed using omconfig. More details about syntax and use of the
command appear later in this section.

84 omconfig: Managing Components

Table 4-2. omconfig Command Level 1, Level 2, and Level 3

Command
Level 1

omconfig

Command Level 2Command Level 3 User

Privilege
Required

Use

about U, P, A Shows version number and

properties for the Server
Administrator program.

details=true U, P, A Displays information for all

of the Server Administrator
programs that are installed.

preferences

cdvformat A Specifies the delimiter for

separating data fields
reported in custom
delimited format (cdv).

dirservice A Configures the Microsoft

Active Directory service.

snmp A Sets the SNMP root

password. Configures
SNMP Set Operations.

useraccess A Determines whether users

below the administrator
level are allowed to use
Server Administrator or not.

webserver A Allows the administrator to

set the encryption levels of
the Web server and
configure the URL launch
point in the Server
Administrator Web server
environment.

system/
servermodule

omconfig: Managing Components 85

Table 4-2. omconfig Command Level 1, Level 2, and Level 3

(continued)

Command
Level 1

Command Level 2Command Level 3 User

Privilege
Required

alertaction P, A Determines in advance the

alertlog P, A Allows the administrator to

assetinfo P, A Enters and edits cost of

cmdlog P, A Allows the administrator to

esmlog P, A Allows the administrator to

events P, A Enables and disables SNMP

pedestinations P, A Sets IP addresses for alert

platformevents A Determines the shutdown

recovery P, A Determines in advance how

Use

actions to be taken for
warning or failure events on
intrusion, fans,
temperatures, voltages,
power supplies, memory,
and redundancy.

clear the alert log.

ownership information for
your system, including
values for depreciation,
lease, maintenance, service,
and support.

clear the command log.

clear the ESM log.

traps.

destinations.

action, if any, to be taken for
a specific platform event.
Also, enables and disables
platform events filter
alert generation.

your system responds to a
hung operating system.

86 omconfig: Managing Components

Table 4-2. omconfig Command Level 1, Level 2, and Level 3

(continued)

Command
Level 1

Command Level 2Command Level 3 User

Privilege
Required

shutdown A Allows the administrator to

thrmshutdown A Sets the severity level at

webserver A Starts or stops the

chassis/
mainsystem

biossetup A Configures the behavior of

fans P, A Configures fan probe

frontpanel A Configures the Power

info P, A Allows you to set an initial

Use

select from several options
when shutting down the
system.

which a thermal event
triggers a system shutdown.

Web s er ve r.

specific system components
controlled by the BIOS.

warning thresholds by
default or by value.

NOTE: You cannot change

threshold values on
embedded server
management (ESM3) and
Dell PowerEdge x8xx
systems.

button, Non-Masking
Interrupt (NMI) button,

encryption access, and LCD
display of the system.

value, or to edit the value
for, asset tag or chassis
name.

omconfig: Managing Components 87

Table 4-2. omconfig Command Level 1, Level 2, and Level 3

(continued)

Command
Level 1

Command Level 2Command Level 3 User

Privilege
Required

leds P, A Specifies when to flash a

memorymode A Enables or disables the

pwrmanagement P, A Allows you to choose

pwrmonitoring P, A Configures power

remoteaccess A Configures remote access

temps P, A Sets warning threshold

volts P, A Sets warning threshold

Use

chassis fault LED or chassis
identification LED, and
allows you to clear the LED
for the system's hard drive.

spare bank, mirroring, raid,
and DDDC (Double Device
Data Correction) memory
modes, and also specify
which mode to use.

between maximum power
economy and optimized
performance of the system.

consumption information
and thresholds.

information.

values by default or value.

NOTE: You cannot change

threshold values on ESM3
and PowerEdge x8xx
systems.

values by default or value.

NOTE: You cannot change

threshold values on ESM3
and PowerEdge x8xx
systems.

88 omconfig: Managing Components

Table 4-2. omconfig Command Level 1, Level 2, and Level 3

(continued)

Command
Level 1

Command Level 2Command Level 3 User

Privilege
Required

storage See "Using the Storage

Use

Management Service" on
page 173.

Help With the omconfig Command

Use the omconfig -? command to get a list of the available commands for
omconfig.

Use omconfig <command level 2> -? to get help on the about, chassis,
preferences, and system’s level 2 commands. The following information on
omconfig system -? applies equally to getting help for the omconfig chassis

command.

Use the omconfig system -? command to get a list of the available commands
for omconfig system.

Use the omconfig preferences -? command to get a list of the available
commands for omconfig preferences, such as cdvformat, which is the custom
delimiter format (cdv). Type the following command to display the list of
delimiter values for the cdv:

omconfig preferences cdvformat -?

Use a command of the form omconfig system <command level 3> -? to get a
list of the parameters you must use to execute a particular omconfig system
command. For example, the following commands produce a list of valid
parameters for omconfig system alertaction and omconfig system shutdown:

omconfig system alertaction -?

omconfig system shutdown -?

In case of the omconfig system alertaction command, you can use various
options to prevent all of the command line interface (CLI) help from
scrolling, before you can read it.

omconfig: Managing Components 89

To scroll command output one screen at a time, type:

omconfig system alertaction -? | more

where | more allows you to press the spacebar to see the next screen of the
CLI help output.

To make a file that contains all the help for the omconfig system alertaction -?
command, type:

omconfig system alertaction -? -outa alert.txt

where -outa directs the output of the command to a file called alert.txt.

To read the help for the alertaction command on a Microsoft Windows, Red
Hat Enterprise Linux, or SUSE Linux Enterprise Server operating system,
type:

more alert.txt

omconfig about

Use the omconfig about command to learn the product name and version
number of the systems management application installed on your system.
The following is an example output of the omconfig about command:

Product
name

Version : 6.x.x

Copyright : Copyright (C) Dell Inc. xxxx-xxxx. All

Company : Dell Inc.

: Dell OpenManage Server Administrator

rights reserved.

For more details about the environment for Server Administrator, type:

omconfig about details=true

90 omconfig: Managing Components

Server Administrator includes a number of services, each of which has a
version number of its own. The Contains field reports version numbers for the
services and provides other useful details. The output that follows is an
example, and it can change depending on the configuration of your system
and the version of Server Administrator that is available:

Contains: Broadcom SNMP Agent 10.xx.xx

Common Storage Module 3.x.x

Data Engine 5.x.x

Hardware Application Programming Interface

5.x.x

Instrumentation Service 6.x.x

Instrumentation Service Integration Layer

1.x.x

Intel SNMP Agent 1.xx.x

OpenManage Inventory Collector 6.x.x

OpenManage Tools 6.x.x

Remote Access Controller 4 Data Populator

4.x.x

Remote Access Controller 4 Managed Node

4.6.3

Secure Port Server 1.x.x

Server Administrator Framework 6.x.x

Agent for Remote Access 1.x.x

Storage Management 3.x.x

Sun Java Runtime Environment 1.x.xx

omconfig: Managing Components 91

omconfig chassis/omconfig mainsystem

Use the omconfig chassis or omconfig mainsystem commands to default or
to set values for fan, voltage, and temperature probes, to configure BIOS
behavior during system start up, to clear memory error counts, and to enable
or disable power button control features where system configuration permits.

Use the omconfig chassis -? or omconfig mainsystem -? command to view a
list of all omconfig chassis/omconfig mainsystem commands.

omconfig chassis biossetup/omconfig mainsystem biossetup

Use the omconfig chassis biossetup or omconfig mainsystem biossetup
command to configure system BIOS settings that are normally available only
in the BIOS setup boot time settings of your system.

CAUTION: Changing certain BIOS setup options might disable your system or

require you to reinstall the operating system.

NOTE: Reboot your system for the BIOS setup options take effect.

NOTE: Not all BIOS setup options are available on every system.

NOTE: Due to the limitations of certain operating systems (for example, VMware

ESXi), certain features may not be available with this release of OpenManage
Server Administrator.

92 omconfig: Managing Components

Table 4-3 shows the name=value pairs you can use with this command.

Table 4-3. BIOS Setup Settings

name=value pair 1
attribute=

attribute=
acpwrrecovery

attribute=bezel setting=enabled |

attribute=
bootsequence

attribute=
bootmode

name=value pair 2
setting=

setting=off | last| on off: System is turned off.

delay=random |
immediate | timedelay
time <value>

disabled

setting=diskettefirst |
hdonly | devicelist
|cdromfirst |
opticaldrive

setting=uefi | bios uefi: Enables the system to boot to

Description

last: System returns to previous state.

on: System is turned on.

random: System is turned on with

random delay.

immediate: System returns to previous
state immediately.

timedelay <value>: System is turned
on based on user specified time delay.

enabled: Enables the bezel removal
intrusion check during system boot.

disabled: Disables the bezel removal
intrusion check during system boot.

Instructs the BIOS which device is used
to boot the system, and the order in
which the boot routine is to check each
device.

NOTE: On Linux systems, user/user

groups upgraded to
administrator/administrator groups
cannot configure this BIOS setup setting.

operating systems that support Unified
Extensible Firmware Interface (UEFI).

bios: Enables the system to boot to
operating systems that do not support
UEFI.

omconfig: Managing Components 93

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=
bootorder

attribute=
hddorder

attribute=cstates setting=enabled |

name=value pair 2
setting=

sequence=aliasname1,

aliasname2,.....

aliasnameN

sequence=aliasname1,

aliasname2,.....

aliasnameN

disabled

Description

Configures the boot sequence according
to the set aliasnames. To view the set
alias names, run the command

omreport chassis
biossetup attribute=
bootorder

.

NOTE: On Linux systems, user/user

groups upgraded to
administrator/administrator groups
cannot configure this BIOS setup setting.

Configures the BIOS setup hard disk
sequence according to the set
aliasnames. Changes takes effect after
rebooting the system. To view the set
alias names, run the command

omreport chassis
biossetup attribute=
bootorder

.

NOTE: On Linux systems, user/user

groups upgraded to
administrator/administrator groups
cannot configure this BIOS setup setting.

enabled: Enables the processor to go into a
deep sleep state when the system is not
utilized.

disabled: Disables the processor to go
into a deep sleep state when the system
is not utilized.

94 omconfig: Managing Components

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=
conredirect

attribute=crab setting=enabled |

attribute=cpuc1e setting=enabled |

attribute=cpuht setting=enabled |

attribute=cpuvt setting=enabled |

name=value pair 2
setting=

setting=enabled |
disabled

disabled

disabled

disabled

disabled

Description

enabled: Redirects the BIOS screen over
Serial Port 1. Keyboard and text output
are redirected over Serial Port 2.

disabled: Turns off the BIOS console
redirection.

enabled: Enables BIOS console
redirection after system reboot.

disabled: Disables BIOS console
redirection.

NOTE: The command crab is valid for Dell

PowerEdge x9xx systems only.

enabled: Enables processor C1-E after
system reboot.

disabled: Disables processor C1-E after
system reboot.

enabled: Enables logical processor
hyperthreading.

disabled: Disables logical processor
hyperthreading.

enabled: Enables virtualization.

disabled: Disables virtualization.

omconfig: Managing Components 95

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=
cpuxdsupport

attribute=cpucore setting=1 | 2 | 4 | 6 |

attribute=dbs setting=enable |

attribute=diskette setting=off | auto |

name=value pair 2
setting=

setting=enabled |
disabled

8 | 10 | 12 |all

disable

writeprotect

Description

enabled: Enables Execute Disable (XD)
support on system.

disabled: Disables XD support on
system.

1: Enables one core per processor.

2: Enables two cores per processor.

4: Enables four cores per processor.

6: Enables six cores per processor.

8: Enables eight cores per processor.

10: Enables ten cores per processor.

12: Enables twelve cores per processor.

all: Enables the maximum cores per

processor.

enable: Enables Demand Based
Switching (DBS) on the system.

disable: Disables DBS on the system.

off: Disables the diskette drive.

auto: Auto-enables the diskette drive.

writeprotect: Do not allow writes. Make

the diskette drive read-only.

96 omconfig: Managing Components

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=dualnic setting=off | on |

attribute=
embhypvisor

name=value pair 2
setting=

pxeboth | nic1pxe
|nic2pxe | isciboth |
nic1isci | nic2isci |
nic1pxenic2isci |
nic1iscinic2pxe |
onpxeboth |
onpxenone |

onpxenic1 | onpxenic2

setting=enabled |
disabled

Description

off: Disables the Network Interface

(

Controllers

on: Enables the network interface (PXE
or iSCSI is not enabled on either of the
NICs).

pxeboth: Enables PXE on both NICs.

nic1pxe: Enables PXE on first NIC and

none (No PXE or iSCSI) on second NIC.

nic2pxe: Enables none (No PXE or
iSCSI) on first NIC and PXE on second
NIC.

isciboth: Enables iSCSI on both NICs.

nic1isci: Enables iSCSI on first NIC and

none (No PXE or iSCSI) on second NIC.

nic2isci: Enables none (No PXE or
iSCSI) on first NIC and iSCSI on
second NIC.

nic1pxenic2isci: Enables PXE on first
NIC and iSCSI on second NIC.

nic1iscinic2pxe: Enables iSCSI on first
NIC and PXE on second NIC.

NICs).

NOTE: The following options are

deprecated:

onpxeboth: Enables PXE on both NICs.

onpxenone: PXE is not enabled on

either of the NICs.

onpxenic1: Enables PXE on NIC 1.

onpxenic2: Enables PXE on NIC 2.

enabled: Enables embedded hypervisor.

disabled: Disables embedded hypervisor.

omconfig: Managing Components 97

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=
embvideoctrl

attribute=
esataport

attribute=
extserial

attribute=fbr setting=9600 | 19200

attribute=htassist setting=enabled |

name=value pair 2
setting=

setting=enabled |
disabled

setting=off | auto off: Sets the embedded SATA port value

setting=com1 | com2
| rad

| 57600 | 115200

disabled

Description

enabled: Enables the embedded video
controller to be the primary video
device.

disabled: Disables the embedded video
controller to be the primary video
device.

to off.

auto: Sets the embedded SATA port
value to auto.

com1: Maps external serial connector to
COM 1.

com2: Maps external serial connector to
COM 2.

rad: Maps external serial connector to
remote access device.

9600: Sets the console redirection failsafe
baud rate to 9600 bits per second.

19200: Sets the console redirection failsafe
baud rate to 19200 bits per second.

57600: Sets the console redirection
failsafe baud rate to 57600 bits per
second.

115200: Sets the console redirection
failsafe baud rate to 115200 bits per
second.

enabled: Enables the probe filter chipset
option.

disabled: Disables the probe filter
chipset option.

NOTE: Certain applications do not

function fully if you enable or disable this
option.

98 omconfig: Managing Components

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=ide setting=on | off

attribute=
idepridrv

attribute=
intrusion

attribute=
intusb[1..2]

name=value pair 2
setting=

force=true

setting=off | auto off: Disables the device.

setting=enabled |
disabled

setting=enabled |
disabled

NOTE: The

following option is
deprecated:

attribute=intusb

Description

on: Enables this device.

off: Disables this device.

force=true: Verification of setting

change.

auto: Detects and enables the device
automatically.

enabled: Enables the intrusion check
during system boot. If the system also
has bezel intrusion checking, then the
intrusion option checks for removal of
the bezel of the system.

disabled: Disables the intrusion check
during system boot.

enabled: Enables the internal USB port.

disabled: Disables the internal USB

port.

attribute=mouse setting=on | off on: Enables the mouse.

off: Disables the mouse.

omconfig: Managing Components 99

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=nic1 setting=enabled |

attribute=nic2 setting=enabled |

name=value pair 2
setting=

enabledwithpxe |
disabled | enabledonly
| enablednonepxe |
enabledwithiscsi

enabledwithpxe |
disabled | enabledonly
| enablednonepxe |
enabledwithiscsi

Description

enabled: Enables the first NIC during
system boot.

enabledwithpxe: Enables the first NIC
during system boot (with PXE on if the
system has PXE).

disabled: Disables the first NIC during
system boot.

enabledonly: Enables the first NIC
during system boot (with PXE off if the
system has PXE).

enablednonepxe: Enables the first NIC
during system boot (with PXE off if the
system has PXE).

enabledwithiscsi: Enables the first NIC
during system boot (with iSCSI on if the
system has iSCSI).

enabled: Enables the second NIC during
system boot.

enabledwithpxe: Enables the second
NIC during system boot (with PXE on if
the system has PXE).

disabled: Disables the second NIC
during system boot.

enabledonly: Enables the second NIC
during system boot (with PXE off if the
system has PXE).

enablednonepxe: Enables the second
NIC during system boot (with PXE off if
the system has PXE).

enabledwithiscsi: Enables the second
NIC during system boot (with iSCSI on
if the system has iSCSI).

100 omconfig: Managing Components