Dell OpenManage Server Administrator Version 5.5 User Manual

Dell™ OpenManage™

Server Administrator Version 5.5

Command Line Interface

User's Guide

Notes and Notices

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

your computer.

NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and

tells you how to avoid the problem.

____________________

Information in this document is subject to change without notice.
© 2008 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, the DELL logo, PowerEdge, PowerVault, and OpenManage are
trademarks of Dell Inc.; Microsoft, Windows, Active Directory, Hyper-V, and Windows Server are
either trademarks 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 and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc.; Intel, Pentium, and
Itanium are registered trademarks and Intel386 is a trademark of Intel Corporation; AMD, AMD
Opteron, AMD-V, and AMD PowerNow! are trademarks of Advanced Micro Devices, Inc.; VESA is

a registered trademark of Video Electronic Standards Association; UNIX is a registered trademark of
The Open Group in the United States and other countries; OS/2 is a registered trademark of
International Business Machines Corporation; Rambus is a registered trademark of Rambus, Inc; Citrix and
XenServer are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/
or other countries.

Other trademarks and trade names may be used in this document 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.

July 2008

Contents

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

What's New for Version 5.5 . . . . . . . . . . . . . . . 15

Using CLI Commands from Windows
Command Prompts

Primary CLI Commands . . . . . . . . . . . . . . . . . 16

CLI Error Checking and Error Messages . . . . . . . . 18

Scripting and Comparing With the CLI . . . . . . . . . 20

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

Success Messages

Failure Messages . . . . . . . . . . . . . . . . . 19

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

Command Syntax Overview

. . . . . . . . . . . . . . . 21

2 Using the omhelp Command . . . . . . . . . . 23

Example Help Commands . . . . . . . . . . . . . . . . 23

3 omreport: Viewing System Status

Using the Instrumentation Service . . . . . 27

Conventions for Parameter Tables . . . . . . . . . 28

Command Summary of the omreport Command

Help With the omreport Command

omreport modularenclosure

. . . . . . . . . . . 32

. . . . . . . . . . . . . . 32

. . . . 28

Contents 3

omreport about . . . . . . . . . . . . . . . . . . . . . 33

omreport chassis/omreport mainsystem
Commands

. . . . . . . . . . . . . . . . . . . . . . . . 34

omreport chassis/ omreport mainsystem

. . . . . 34

omreport chassis acswitch/ omreport
mainsystem acswitch

. . . . . . . . . . . . . . . 35

omreport chassis batteries/omreport
mainsystem batteries

. . . . . . . . . . . . . . . . 35

omreport chassis bios/omreport mainsystem
bios

. . . . . . . . . . . . . . . . . . . . . . . . . 36

omreport chassis biossetup/omreport
mainsystem biossetup

. . . . . . . . . . . . . . . 36

omreport chassis bmc/omreport
mainsystem bmc

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

omreport chassis currents/omreport
mainsystem currents

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

omreport chassis fans/omreport
mainsystem fans

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

omreport chassis fancontrol/omreport
mainsystem fancontrol

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

omreport chassis firmware/omreport
mainsystem firmware

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

omreport chassis frontpanel/omreport
mainsystem frontpanel

. . . . . . . . . . . . . . . 40

omreport chassis fru/omreport
mainsystem fru

. . . . . . . . . . . . . . . . . . . 40

omreport chassis hwperformance/omreport
mainsystem hwperformance

. . . . . . . . . . . . 40

omreport chassis info/omreport
mainsystem info

omreport chassis intrusion

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

. . . . . . . . . . . . . 42

omreport chassis leds/omreport
mainsystem leds

. . . . . . . . . . . . . . . . . . 42

omreport chassis memory/omreport
mainsystem memory

. . . . . . . . . . . . . . . . 42

4 Contents

omreport chassis nics/omreport
mainsystem nics

. . . . . . . . . . . . . . . . . . 44

omreport chassis ports/omreport
mainsystem ports

. . . . . . . . . . . . . . . . . . 44

omreport chassis processors/omreport
mainsystem processors

. . . . . . . . . . . . . . 45

omreport chassis pwrmonitoring/omreport
mainsystem pwrmonitoring

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

omreport chassis pwrsupplies/omreport
mainsystem pwrsupplies

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

omreport chassis remoteaccess/omreport
mainsystem remoteaccess

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

omreport chassis slots/omreport
mainsystem slots

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

omreport chassis temps/omreport
mainsystem temps

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

omreport chassis volts/omreport
mainsystem volts

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

omreport system Commands/omreport
servermodule Commands

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

omreport system/omreport servermodule

Commands for Viewing Logs

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

omreport system alertaction/omreport
servermodule alertaction

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

omreport system assetinfo/omreport
servermodule assetinfo

. . . . . . . . . . . . . . 55

omreport system events/omreport
servermodule events

. . . . . . . . . . . . . . . . 56

omreport system operatingsystem/omreport
servermodule operatingsystem

. . . . . . . . . . 58

omreport system pedestinations/omreport
servermodule pedestinations

. . . . . . . . . . . 58

omreport system platformevents/omreport
servermodule platformevents

. . . . . . . . . . . 59

omreport system recovery/omreport
servermodule recovery

. . . . . . . . . . . . . . 59

. . . . . 52

Contents 5

omreport system shutdown/omreport
servermodule shutdown

. . . . . . . . . . . . . . 59

omreport system summary/omreport
servermodule summary

. . . . . . . . . . . . . . 60

omreport system thrmshutdown/omreport
servermodule thrmshutdown

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

omreport system version/omreport
servermodule version

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

4 omconfig: Managing Components

Using the Instrumentation Service . . . . . 65

Conventions for Parameter Tables . . . . . . . . . 66

omconfig Command Summary

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

Help With the omconfig Command . . . . . . . . . . . 69

omconfig about . . . . . . . . . . . . . . . . . . . . . 70

omconfig chassis/omconfig mainsystem

. . . . . . . . 71

omconfig chassis biossetup/omconfig

mainsystem biossetup . . . . . . . . . . . . . . . 71

omconfig chassis bmc/omconfig
mainsystem bmc

. . . . . . . . . . . . . . . . . . 79

omconfig chassis currents/omconfig
mainsystem currents

. . . . . . . . . . . . . . . . 79

omconfig chassis fans/omconfig
mainsystem fans

. . . . . . . . . . . . . . . . . . 79

omconfig chassis fancontrol/omconfig
mainsystem fancontrol

. . . . . . . . . . . . . . . 81

omconfig chassis frontpanel/omconfig
mainsystem frontpanel

. . . . . . . . . . . . . . . 81

omconfig chassis info/omconfig
mainsystem info

. . . . . . . . . . . . . . . . . . 81

omconfig chassis leds/omconfig
mainsystem leds

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

6 Contents

omconfig chassis memorymode/omconfig
mainsystem memorymode

. . . . . . . . . . . . . 83

omconfig chassis pwrmonitoring/omconfig
mainsystem pwrmonitoring

. . . . . . . . . . . . 84

omconfig chassis remoteaccess/omconfig
mainsystem remoteaccess

. . . . . . . . . . . . . 85

omconfig chassis temps/omconfig
mainsystem temps

. . . . . . . . . . . . . . . . . 95

omconfig chassis volts/omconfig
mainsystem volts

. . . . . . . . . . . . . . . . . . 96

omconfig preferences

omconfig preferences cdvformat

omconfig preferences dirservice

. . . . . . . . . . . . . . . . . . 98

. . . . . . . . . 98

. . . . . . . . . 98

omconfig preferences snmp . . . . . . . . . . . . 99

omconfig preferences useraccess . . . . . . . . 101

omconfig system/omconfig servermodule . . . . . . . 101

omconfig system alertaction/omconfig
servermodule alertaction

Commands for Clearing Logs

. . . . . . . . . . . . . 101

. . . . . . . . . . . 105

omconfig system pedestinations/omconfig
servermodule pedestinations

. . . . . . . . . . . 106

omconfig system platformevents/omconfig
servermodule platformevents

. . . . . . . . . . . 106

omconfig system events/omconfig
servermodule events

. . . . . . . . . . . . . . . . 109

omconfig system webserver/omconfig
servermodule webserver

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

omconfig system recovery/omconfig
servermodule recovery

. . . . . . . . . . . . . . 112

omconfig system shutdown/omconfig
servermodule shutdown

. . . . . . . . . . . . . . 112

omconfig system thrmshutdown/omconfig
servermodule thrmshutdown

. . . . . . . . . . . 113

Contents 7

5 omconfig system or servermodule

assetinfo: Editing Cost of

Ownership Values . . . . . . . . . . . . . . . . . 115

Overview . . . . . . . . . . . . . . . . . . . . . . . . . 115

User Level Required for Adding
Asset Information

Adding Acquisition Information . . . . . . . . . . . . . 116

Example Commands for Adding

Acquisition Information

Adding Depreciation Information . . . . . . . . . . . . 118

Example Commands for Adding

Depreciation Information

Adding Extended Warranty Information . . . . . . . . 119

Example Command for Adding

Extended Warranty Information

Adding Lease Information . . . . . . . . . . . . . . . . 120

Example Command for Adding

Lease Information

. . . . . . . . . . . . . . . . . 115

. . . . . . . . . . . . . . 117

. . . . . . . . . . . . . . 118

. . . . . . . . . . 120

. . . . . . . . . . . . . . . . . 121

8 Contents

Adding Maintenance Information . . . . . . . . . . . . 121

Example Command for Adding
Maintenance Information

. . . . . . . . . . . . . 122

Adding Outsource Information . . . . . . . . . . . . . 123

Example Command for Adding

Outsource Information

Adding Owner Information

. . . . . . . . . . . . . . . 123

. . . . . . . . . . . . . . . 124

Example Command for Adding

Owner Information

. . . . . . . . . . . . . . . . . 124

Adding Service Contract Information . . . . . . . . . . 125

Example Command for Adding

Service Information

. . . . . . . . . . . . . . . . 125

Adding Support Information . . . . . . . . . . . . . . . 126

Example Command for Adding

Support Information

. . . . . . . . . . . . . . . . 127

Adding System Information . . . . . . . . . . . . . . . 127

Example Command for Adding

System Information

. . . . . . . . . . . . . . . . . 128

Adding Warranty Information . . . . . . . . . . . . . . 129

Example Command for Adding

Warranty Information

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

6 Using the Storage Management

Service . . . . . . . . . . . . . . . . . . . . . . . . . 131

CLI Command Syntax . . . . . . . . . . . . . . . . . . 131

Syntax for Required, Optional, and Variable
Command Elements

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

User Privileges for omreport storage and
omconfig storage

omreport Command

omreport Storage Help

omreport Controller Status

. . . . . . . . . . . . . . . . . . . . 134

. . . . . . . . . . . . . . . . . . . 134

. . . . . . . . . . . . . . . . . 135

. . . . . . . . . . . . . 135

omreport Global Information (Smart
Thermal Shutdown Status)

omreport Battery Status

omreport Connector Status

omreport Enclosure Status

. . . . . . . . . . . . . 136

. . . . . . . . . . . . . . 136

. . . . . . . . . . . . 137

. . . . . . . . . . . . . 137

Contents 9

omreport Temperature Probe Status . . . . . . . . 138

omreport Fan Status . . . . . . . . . . . . . . . . 139

omreport Power Supply Status . . . . . . . . . . . 140

omreport EMM Status

. . . . . . . . . . . . . . . 141

omreport Physical Disk Status . . . . . . . . . . . 142

omreport Virtual Disk Status . . . . . . . . . . . . 143

omconfig Global Commands . . . . . . . . . . . . . . 143

omconfig Global Enable Smart
Thermal Shutdown

. . . . . . . . . . . . . . . . . 143

omconfig Global Disable Smart
Thermal Shutdown

. . . . . . . . . . . . . . . . . 144

omconfig Global Rescan Controller . . . . . . . . 145

omconfig Controller Commands . . . . . . . . . . . . . 145

omconfig Rescan Controller

. . . . . . . . . . . . 147

omconfig Enable Controller Alarm . . . . . . . . . 147

omconfig Disable Controller Alarm

. . . . . . . . 148

omconfig Quiet Controller Alarm . . . . . . . . . . 148

omconfig Test Controller Alarm . . . . . . . . . . 149

omconfig Reset Controller Configuration

. . . . . 149

omconfig Create Virtual Disk . . . . . . . . . . . . 150

omconfig Set Controller Rebuild Rate . . . . . . . 156

omconfig Set Background Initialization Rate

omconfig Set Reconstruct Rate

. . . . . . . . . . 157

. . . 157

omconfig Set Check Consistency Rate . . . . . . . 158

omconfig Export the Controller Log

omconfig Import Foreign Configuration

. . . . . . . . 158

. . . . . . 159

omconfig Import/Recover Foreign
Configuration

omconfig Clear Foreign Configuration

omconfig Set Patrol Read Mode

omconfig Start Patrol Read

omconfig Stop Patrol Read

. . . . . . . . . . . . . . . . . . . . 159

. . . . . . . 160

. . . . . . . . . . 160

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

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

10 Contents

omconfig Change Controller Properties . . . . . . 162

omconfig Storage Virtual Disk . . . . . . . . . . . 162

omconfig Storage Controller . . . . . . . . . . . . 163

omconfig Virtual Disk Commands . . . . . . . . . . . 164

omconfig Blink Virtual Disk

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

omconfig Unblink Virtual Disk . . . . . . . . . . . 165

omconfig Initialize Virtual Disk

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

omconfig Cancel Initialize Virtual Disk . . . . . . . 166

omconfig Fast Initialize Virtual Disk . . . . . . . . 166

omconfig Slow Initialize Virtualize Disk

. . . . . . 167

omconfig Cancel Background Initialize . . . . . . 167

omconfig Restore Dead Segments . . . . . . . . 168

omconfig Split Mirror

. . . . . . . . . . . . . . . 168

omconfig Unmirror . . . . . . . . . . . . . . . . . 169

omconfig Assign Dedicated Hot Spare . . . . . . 170

omconfig Unassign Dedicated Hot Spare

. . . . . 171

omconfig Check Consistency . . . . . . . . . . . 172

omconfig Cancel Check Consistency . . . . . . . 172

omconfig Pause Check Consistency

. . . . . . . . 173

omconfig Resume Check Consistency . . . . . . . 173

omconfig Delete Virtual Disk . . . . . . . . . . . . 174

omconfig Format Virtual Disk

omconfig Reconfiguring Virtual Disks

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

. . . . . . . 175

omconfig Change Virtual Disk Policy . . . . . . . 175

omconfig Rename Virtual Disk

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

omconfig Physical Disk Commands

omconfig Blink Physical Disk

. . . . . . . . . . . 177

omconfig Unblink Physical Disk

omconfig Prepare to Remove Physical Disk

omconfig Initialize Physical Disk

omconfig Offline Physical Disk

omconfig Offline Physical Disk

. . . . . . . . . . 177

. . . . . . . . . . 178

. . . . 179

. . . . . . . . . . 180

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

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

Contents 11

omconfig Online Physical Disk . . . . . . . . . . . 182

omconfig Assign Global Hot Spare . . . . . . . . . 183

omconfig Unassign Global Hot Spare . . . . . . . 183

omconfig Rebuild Physical Disk

. . . . . . . . . . 184

omconfig Cancel Rebuild Physical Disk . . . . . . 185

omconfig Remove Dead Segments . . . . . . . . 186

omconfig Clear Physical Disk

. . . . . . . . . . . 187

omconfig Cancel Clear Physical Disk . . . . . . . 188

omconfig Cancel Replace Member . . . . . . . . 188

omconfig Battery Commands . . . . . . . . . . . . . . 189

omconfig Recondition Battery

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

omconfig Start Battery Learn Cycle . . . . . . . . 190

omconfig Delay Battery Learn Cycle

. . . . . . . . 190

12 Contents

omconfig Connector Commands

omconfig Rescan Connector

. . . . . . . . . . . . 191

. . . . . . . . . . . . 191

omconfig Enclosure Commands . . . . . . . . . . . . . 192

omconfig Enable Enclosure Alarm

. . . . . . . . . 192

omconfig Disable Enclosure Alarm . . . . . . . . 193

omconfig Set Enclosure Asset Tag

. . . . . . . . . 194

omconfig Set Enclosure Asset Name . . . . . . . 194

omconfig Set Temperature Probe
Thresholds

. . . . . . . . . . . . . . . . . . . . . 195

omconfig Reset Temperature Probe
Thresholds

. . . . . . . . . . . . . . . . . . . . . 196

omconfig Set All Temperature Probe
Thresholds

. . . . . . . . . . . . . . . . . . . . . 196

omconfig Reset All Temperature Probe
Thresholds

omconfig Blink

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

. . . . . . . . . . . . . . . . . . . 198

7 Working With CLI Command Results . . 199

Output Options for Command Results . . . . . . . 199

Controlling Command Output Display . . . . . . . 199

Writing Command Output to a File

Selecting a Format for Your CLI
Command Output

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

. . . . . . . . . 200

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Contents 13

14 Contents

1

Introduction

Using Dell™ OpenManage™ Server Administrator’s graphical user interface
(GUI) or the command line interface (CLI) you can perform essential
systems management tasks.

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 voltages, temperatures, fan’s
functioning, and many other critical component details. You can see a
detailed account of many relevant cost of ownership (COO) facts about your
system in a summary view. Version information for BIOS, firmware, operating
system, and all installed software is easy to retrieve.

Configuration features allow Server Administrator to perform essential tasks
described in detail in the following sections.

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

the Server Administrator Web server off if you have security 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 112" for more information.

revolutions per minute (

RPM), memory

What's New for Version 5.5

The following features are new in this release of Server Administrator:

• The Dell OpenManage systems management software kit is now available
on a single DVD titled

NOTE: The Dell Systems Management Tools and Documentation DVD contains

version 5.5 of the Dell OpenManage systems management software kit and version

1.0.7 of the Dell Systems Build and Update Utility. The root of the DVD also contains
ISO images of the Dell Systems Build and Update Utility (version 1.0) and the Dell
Systems Console and Agent CD (Dell OpenManage software version 5.3.0.1). You
can use these ISO images to create CDs for systems that do not have DVD drives.
However, if you need version 1.0.7 of the Dell Systems Build and Update Utility (to
support x6xx and x7xx Dell systems and Windows Server
you can download the ISO image from the Dell Support site at support.dell.com.

Dell Systems Management Tools and Documentation

®

2008 operating systems),

Introduction 15

.

• Added support for the next generation PERC/SAS controller firmware
version (version 6.1).

• Added support for Intelligent Mirroring/RAID 10E.

• Added support for Redundant Path view.

• Added support for Import preview of foreign configuration.

• Added support for the Battery Learn Mode.

• Added support for hot plug of enclosures.

• Added support for Disk Cache Policy.

• Added support for Change Controller Properties.

• Enhancement to the Storage Dashboard.

• Added support for preserved cache management.

For information about various Dell systems, the operating systems supported
by these systems, and the Dell OpenManage components that can be
installed on these systems, see the latest Dell Systems Software Support
Matrix in the Dell Systems Management Tools and Documentation DVD or on
the Dell Support website at support.dell.com.

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 by clicking the Start button and pointing
to Programs→ Accessories→ Command Prompt shortcut, or by clicking the
Start button, selecting Run, and typing cmd.exe in the Run dialog box.

Do not type command into the Run dialog box to launch a command line
window; this activates the MS-DOS
environment variable limitations that can cause subtle problems with the CLI.

®

emulator command.com, which has

Primary CLI Commands

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

•

omconfig

•

omhelp

•

omreport

16 Introduction

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 produces reports of your system’s management
information.

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.

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

Primary CLI
Command

omconfig "omconfig: Managing Components

omhelp "Using the omhelp Command"

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]. See the Dell Update Packages for Microsoft Windows Operating Systems
User’s Guide, the Dell Update Packages for Linux User’s Guide, or the Server Update
Utility User’s Guide for more information on corresponding CLI syntax.

Section Title Related Sections

Using the Instrumentation Service"

Using the Instrumentation Service"

"omconfig system or servermodule
assetinfo: Editing Cost of Ownership
Va lu es "

Introduction 17

Additional useful topics about the CLI include:

• "Working With CLI Command Results"

•"Glossary"

CLI Error Checking and Error Messages

When you type CLI commands, the CLI checks these commands for correct
syntax. If you enter 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 show valid CLI commands and
their success messages:

Command:

omconfig chassis temps index=0 warnthresh=default

Message:

Temperature probe warning threshold value(s) set
successfully.

Command:

omconfig chassis biossetup attribute=speaker
setting=on

Message:

BIOS setup configured successfully.

Command:

omconfig system assetinfo info=depreciation
duration=6

Message:

Asset information set successfully.

18 Introduction

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

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 enter 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 19

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, name of the system's insurance company, 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.

20 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

Introduction 21

An example of nine name=value pairs:

omconfig system assetinfo info=acquisition
purchasecost=
purchasedate=<
expensed=<

<n> waybill=<n> installdate=<

mmddyy

yes | no

> ponum=<n> signauth=<

> costcenter=<

text

mmddyy

text

>

>

>

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

22 Introduction

2

Using the omhelp Command

The omhelp command and its equivalent, <command> -?, accesses the CLI's
detailed help text interface. 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

• recovery

•shutdown

•thrmshutdown

• webserver

Using the omhelp Command 23

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.

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

26 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."

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

servermodule

mainsystem

system

chassis

omreport: Viewing System Status Using the Instrumentation Service 27

Modular system

Modular system

Modular system

Non-modular system

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.

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 that
display for 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

®

systems, omreport commands display external chassis information in a

Linux
separate section after the main chassis information. On Microsoft
systems, data about the external chassis does not appear in the omreport output.

®

Linux Enterprise Server and Red Hat® Enterprise

®

Windows®

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 sh ow s th e 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."

28 omreport: Viewing System Status Using the Instrumentation Service

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

Command
Level 1

omreport

Command
Level 2

modularen
closure

about U, P, A Shows version number and properties for

chassis/mai
nsystem

Command
Level 3

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

acswitch U, P, A Shows failover settings where redundant

batteries U, P, A Shows the properties set for batteries.

bios U, P, A Shows BIOS information such as

biossetup A Shows BIOS setup properties configured

fancontrol U, P, A Shows the properties set for fan speed.

fans U, P, A Shows the status and thresholds for system

firmware U, P, A Shows firmware properties such as version,

frontpanel U, P, A Shows whether the front panel button

fru U, P, A Shows the Field Replaceable Unit (FRU)

hwperformance U, P, A Shows the status and cause for the

User
Privilege
Required

U, P, A Shows information for all the modular

U, P, A Shows the general status of all the main

Use

chassis.

Server Administrator.

Administrator programs installed.

components.

AC power lines are supported in a system.

manufacturer, version, and date last
updated.

during system boot.

fans.

date of last update, and whether the
firmware is updatable.

settings, such as the Powe r button and/or
Nonmasking Interrupt (NMI) button
(if present on the system), are enabled or
disabled.

information.

system’s performance degradation.

omreport: Viewing System Status Using the Instrumentation Service 29

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

(continued)

Command
Level 1

Command
Level 2

storage U, P, A See "Using the Storage Management

system/serv
ermodule

Command
Level 3

info U, P, A Shows a status summary for main system

intrusion U, P, A Shows the status of the system’s intrusion

leds U, P, A Shows the properties you have set for light-

memory U, P, A Shows properties of your system's memory

nics U, P, A Shows the number of NICs installed in

ports U, P, A Shows the properties for your system’s

processors U, P, A Shows properties of your system’s

pwrmonitoring U, P, A Shows properties of power consumption.

pwrsupplies U, P, A Shows properties of power supplies.

remoteaccess U, P, A Shows general information on remote

slots U, P, A Shows properties of your system’s

temps U, P, A Shows the status and thresholds for the

volts U, P, A Shows the status and thresholds for the

User
Privilege
Required

U, P, A Shows a high-level summary of system

Use

chassis components.

sensor(s).

emitting diodes to flash under various alert
conditions.

arrays.

your system, NIC vendor, NIC description,
IP address, and connection status.

parallel and serial ports, such as I/O
address, IRQ level, connector type, and
maximum speed.

processors, including speed, manufacturer,
and processor family.

access.

expansion slots and other slot types.

system temperature sensors.

system voltage sensors.

Service."

components.

30 omreport: Viewing System Status Using the Instrumentation Service

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

(continued)

Command
Level 1

Command
Level 2

Command
Level 3

alertaction U, P, A Shows warning and failure threshold

alertlog U, P, A Allows the administrator to display the

assetinfo U, P, A Shows the cost of ownership information

cmdlog U, P, A Allows the administrator to display the

esmlog U, P, A Allows the administrator to display the

events U, P, A Shows the system’s Simple Network

operatingsystemU, P, A Shows the name and version of your

pedestinations U, P, A Shows destinations where alerts for

platformevents U, P, A Shows the system’s response for each listed

recovery P, A Shows how your system is configured to

shutdown P, A Shows how the shutdown action is to be

summary U, P, A Shows the key facts for all system

thrmshutdown P, A Shows the shutdown action, if any, to be

version U, P, A Shows a summary for all updatable

User
Privilege
Required

Use

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

alert log.

for your system.

command log.

hardware log.

Management Protocol (SNMP) event
settings.

operating system.

platform events are configured to be sent.

platform event.

respond to a hung operating system.

performed.

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

taken when a temperature warning or
failure condition is detected.

components on your system.

omreport: Viewing System Status Using the Instrumentation Service 31

Help With the omreport Command

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

Use omreport

<command level 2> -?

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

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

omreport system -? | more

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

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

NOTE: As with all output shown in this guide, the following output is an example

and may vary depending on your system configuration.

Modular Chassis Information

Chassis Information

Attribute : Model

Value : Modular Server Enclosure

Attribute : Lock

Value : true

Attribute : Service Tag

Value : 8RLNB1S

CMC Information

Attribute : Product

Value : Chassis Management Controller (CMC)

Attribute : Description

32 omreport: Viewing System Status Using the Instrumentation Service

Value : The system component provides a complete set

Attribute : Version

Value : 1.0 (100)

Attribute : IP Address

Value : 101.102.103.104

Attribute : IP Address Source

Value : Dynamic

Attribute : IP Address Type

Value : IPv4

Attribute : Remote Connect Interface

Value : Launch CMC Web Interface

of remote management functions for Dell
systems.

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 : 5.x.x

Copyright : Copyright (C) Dell Inc. 1995-2008. All rights

reserved.

Company : Dell Inc.

For details about the environment for Server Administrator, type:

omreport about details=true

omreport: Viewing System Status Using the Instrumentation Service 33

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 configuration and the version of Server
Administrator installed on your system:

Contains: Instrumentation Service 5.

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

x

x.x

x

x

x

x

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

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

NOTE: As with all output shown in this guide, the following output is an example

and may vary depending on your system configuration.

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

34 omreport: Viewing System Status Using the Instrumentation Service

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 : Input Source Line 1, upon redundancy

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

:2

restoration, return to Line 1

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: Viewing System Status Using the Instrumentation Service 35

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.

Ty p e :

omreport chassis biossetup

or

omreport mainsystem biossetup

Table 3-3 displays the available 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

Bezel Displays whether the bezel removal intrusion check during system

Bootsequence Displays the device used to boot the system.

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

Console Redirection
After Boot

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

Demand Based Power
Management (DBS)

reboot is enabled or disabled.

or if it is turned off.

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

read-only.

Displays whether DBS is enabled or disabled on the system.

36 omreport: Viewing System Status Using the Instrumentation Service

Table 3-3. BIOS Setup Parameters

Parameters Description

Dual NIC Displays whether NIC 1 and NIC 2 with PXE/iSCSI is enabled or

External Serial Connector Displays whether the external serial connector is mapped to

Console Redirection
Failsafe Baud Rate

Embedded Hypervisor Displays whether the embedded hypervisor is enabled or disabled.

IDE Displays whether the drive is enabled or disabled.

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

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

Internal USB Displays whether internal USB is enabled or disabled.

Intrusion Displays whether the intrusion check is enabled or disabled during

Mouse Displays whether the mouse is enabled or disabled.

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

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

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

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

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

Optical Drive Controller Displays whether the optical drive controller is enabled or disabled.

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

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

disabled.

COM port 1 or COM port 2 or a Remote Access Device.

Displays the setting for console redirection failsafe baud rate.

or if the device is disabled.

or if the device is disabled.

system boot.

PXE/iSCSI) or disabled during system boot.

PXE/iSCSI) or disabled during system boot.

PXE/iSCSI) or disabled during system boot.

PXE/iSCSI) or disabled during system boot.

or if it is disabled.

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

(continued)

omreport: Viewing System Status Using the Instrumentation Service 37

Table 3-3. BIOS Setup Parameters

Parameters Description

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

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

SATA Displays whether the onboard SATA controller is set to ATA mode,

SATA port Displays if the SATA 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 with or

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.

Trusted Platform Module Displays whether Trusted Platform Module is off, on with pre-boot

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

User accessible USB Displays whether the user-accessible USB port is enabled or

Operating System
Wat c hd og Ti m er

RAID device or a SCSI device.

RAID device or a SCSI device.

RAID mode, or is disabled.

without console redirection.

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.

measurements, or on without pre-boot measurements

disabled.

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

(continued)

omreport chassis bmc/omreport mainsystem bmc

This command is phased-out in this releases. It is replaced by the command
"omreport chassis remoteaccess/omreport mainsystem remoteaccess" on
page 50.

omreport chassis currents/omreport mainsystem currents

This command is no longer available through Server Administrator.

38 omreport: Viewing System Status Using the Instrumentation Service

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 fancontrol/omreport mainsystem fancontrol

Use the omreport chassis fancontrol or omreport mainsystem fancontrol
command to view the fan speed settings on your system. Fan speed can be set
to optimize speed for cooling or for quiet operation. Table 3-4 shows the
available settings.

Table 3-4. Fan Control Settings

name=value pair Description

speed=quiet Set fan speed for quiet operation.

speed=maxcool Set fan speed for maximum cooling.

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.

omreport: Viewing System Status Using the Instrumentation Service 39

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.

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.

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.

40 omreport: Viewing System Status Using the Instrumentation Service

Depending on your configuration, output may resemble the following
example:

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=

or

omreport mainsystem info

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.

Depending on your configuration, output may resemble the following example:

Index : 0

Chassis Name : Main System Chassis

Host Name : everglades

Baseboard Management Controller Version : 1.80

Primary Backplane Version : 1.01

Sensor Data Record Version : SDR Version 0.33

Chassis Model : PowerEdge 1750

System Revision Name : Triathlon MLK II

Chassis Lock : Present

Chassis Service Tag : 8RLNB1S

Chassis Asset Tag :

Flash chassis indentify LED state : Off

Flash chassis indentify LED timeout value : 300

n

index=n

omreport: Viewing System Status Using the Instrumentation Service 41

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=

or

omreport mainsystem leds index=

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.

The following is an example output:

Flash chassis indentify LED state

Flash chassis indentify LED timeout value

n

n

: Off

: 300

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=

or

omreport mainsystem index=

42 omreport: Viewing System Status Using the Instrumentation Service

n

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.

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

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

Memory Redundancy
Redundancy Status
Fail Over State
Redundancy Configuration
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1
Attributes
Memory Array 1

: Full
: Inactive
: SpareBank
: Location
: Proprietary Add-on Card
: Use
: Unknown
: Installed Capacity
: 1536 MB
: Maximum Capacity
: 12288 MB
: Slots Available
: 12

omreport: Viewing System Status Using the Instrumentation Service 43

omreport chassis nics/omreport mainsystem nics

Use the omreport chassis nics or omreport mainsystem nics command to
view NIC properties. Type:

omreport chassis nics index=

or

omreport mainsystem nics index=

The index parameter is optional. If you do not specify the index, Server
Administrator displays properties about all NICS on your system. If you
specify the index, Server Administrator displays properties for a specific NIC.

Values display for the following fields: Index (number of the NIC card),
IP Address, Ve nd or, Description, and Connection Status.

n

n

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.

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.

44 omreport: Viewing System Status Using the Instrumentation Service

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: Connector Name, Manufacturer,
Processor Family, Processor Version, Current Speed, External Clock Speed,
and State.

Connector Name refers to the name or number of the device that occupies
the processor slot in the system.

Manufacturer is the business entity that sells the processor.

Processor Family refers to the type of processor made by a manufacturer such

as Intel

Processor Version refers to the model and stepping number of the processor.

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

time.

External Clock Speed is the speed of the processor's external clock in
MegaHertz.

State refers to whether the processor slot is enabled or disabled.

Core Count refers to the number of processors integrated into one chip.

®

Itanium® or Pentium® III or AMD™ Opteron™.

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.

omreport: Viewing System Status Using the Instrumentation Service 45

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)

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

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

46 omreport: Viewing System Status Using the Instrumentation Service

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

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 4-way set-associative cache directly maps four specific lines of memory
to the same four lines of cache.

• A 3-way set-associative cache directly maps three specific lines of memory
to the same three lines of cache.

• A 2-way set-associative cache directly maps two specific lines of memory to
the same two lines of cache.

• A 1-way set-associative cache directly maps a specific line of memory in the
same line 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.

omreport: Viewing System Status Using the Instrumentation Service 47

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 pwrmonitoring/omreport mainsystem pwrmonitoring

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

consumption. Type:

omreport chassis pwrmonitoring

or

omreport mainsystem pwrmonitoring

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

Power Consumption Status, Probe Name, Reading, Warning Threshold, and
Failure Threshold, Amperage: Location and Reading, Power Tracking
Statistics, Energy Consumption, Measurement Start Time, Measurement
Finish Time, Reading, System Peak Power, and System Peak Amperage.

NOTE: The omreport chassis pwrmonitoring or omreport mainsystem

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

Power Consumption Information

Power Consumption

Index

Status

Probe Name

Reading

Warning Threshold

Failure Threshold

: 2

: Ok

: System Board System Level

: 539 W

: 994 W

: 1400 W

48 omreport: Viewing System Status Using the Instrumentation Service

Amperage

Location

Reading

Location

Reading

Power Tracking Statistics

Statistics

Measurement Start Time

Measurement Finish Time

Reading

: PS 1 Current 1

: 1.2 A

: PS 2 Current 2

: 1.0 A

: Energy consumption

: Thu Jun 28 11:03:20 2007

: FRI Jun 28 11:05:46 2007

: 5.9 KWH

Statistics

Measurement Start Time

Peak Time

Peak Reading

Statistics

Measured Since

Read Time

Peak Reading

: 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

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

Status, Location, Ty p e , Maximum Output Wattage, Online Status, and
Power Monitoring Capable.

omreport: Viewing System Status Using the Instrumentation Service 49

omreport chassis remoteaccess/omreport mainsystem remoteaccess

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

management controller (BMC) and

Ty p e :

omreport chassis remoteaccess

or

omreport mainsystem remoteaccess

NOTE: This command is applicable to Dell PowerEdge x8xx and x9xx systems only.

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

the available settings.

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

name=value pair Description

config=advsol Reports advanced BMC/iDRAC or remote access information on a

serial over local area network (LAN) connection.

config=nic Reports BMC/iDRAC or remote access information for the LAN.

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

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

LAN connection.

config=terminalmode Reports terminal mode settings for the serial port.

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

remote access if DRAC is installed.

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=

or

omreport mainsystem slots index=

50 omreport: Viewing System Status Using the Instrumentation Service

n

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.

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.

Adapter refers to the name and or type of the card that fits into the slot, for
example, a storage array controller, SCSI adapter, 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=

or

omreport mainsystem temps index=

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.

n

n

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=

or

omreport mainsystem volts index=

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.

omreport: Viewing System Status Using the Instrumentation Service 51

n

n

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

NOTE: As with all output shown in this guide, the following output is an example

and may vary depending on your system configuration.

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

omconfig system cmdlog action=clear" resolves the issue.

"

52 omreport: Viewing System Status Using the Instrumentation Service

omconfig system alertlog action=clear" or

If you need to retain the log information for future reference, save a copy of the log
before clearing. See "Commands for Clearing Logs" 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 Embedded Systems Management (ESM) report 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.

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.

omreport: Viewing System Status Using the Instrumentation Service 53

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

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

• Power Supply Warning

• Power Supply Failure

• Degraded Redundancy

• Lost Redundancy

• Temperature Warning

•Temperature Failure

•Voltage Warning

•Voltage Failure

• Processor Warning

•Processor Failure

54 omreport: Viewing System Status Using the Instrumentation Service

• 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

NOTE: Storage Controller Battery Warning and

Failure

events are not available on modular systems.

Storage Controller Battery

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

omreport: Viewing System Status Using the Instrumentation Service 55

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

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

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

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

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

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

56 omreport: Viewing System Status Using the Instrumentation Service

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: Some component types may be unavailable on your system.

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

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=volts Reports events for voltages.

Reports events for fan enclosures.

Example Command for an Event Type

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: Viewing System Status Using the Instrumentation Service 57

omreport system operatingsystem/omreport servermodule operatingsystem

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

system.

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

58 omreport: Viewing System Status Using the Instrumentation Service

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

pedestinations

Output Attributes Description

Destination Number:
Destination 3

Destination IP Address:

201.202.203.204

Destination Number:
Destination 4

Destination IP Address:

210.211.212.213

Destination
Configuration
Settings

attribute=communitystring communitystring: Displays the text string

(continued)

destination 3: Displays the third destination.

201:202:203:204: IP address of the third

destination.

destination 4: Displays the fourth
destination.

210.211.212.213: IP address of the fourth
destination.

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.

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

omreport: Viewing System Status Using the Instrumentation Service 59

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

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 results for your system’s hardware and
software configuration:

System Summary

-----------------­Software Profile

-----------------­System Management

Name : Dell OpenManage Server Administrator

Version : 5.

Description : Systems Management Software

Contains: : Instrumentation Service 5.

x.x

x.x

: Storage Management Service 3.x.

: Sun JRE - OEM Installed Version 3.x.

: Secure Port Server 1.x.

: Dell OpenManage Core Service 1.x.

: Instrumentation Service Integration Layer

1.

x.x

: Storage Management Service Integration Layer

x.x

1.

x

x

x

x

60 omreport: Viewing System Status Using the Instrumentation Service

Operating System

Name : Microsoft Windows 2000 Server

Version : Service Pack 3 (Build 2

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

System Bootup Time : Wed Sep 18 18:37:58 2

XXX

XXX

XXX

)

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

Main System Chassis/Main System

Chassis

•Chassis Model

• Chassis Service Tag

•Chassis Lock

• Chassis Asset Tag

Processor

The following are listed for each processor in the system:

• Processor Manufacturer

•Processor Family

• Processor Version

• Current Speed

•Maximum Speed

• External Clock Speed

•Voltage

omreport: Viewing System Status Using the Instrumentation Service 61

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

BIOS

• Manufacturer

•BIOS Version

• Release Date

• BIOS Firmware Information

•Name

• BIOS Firmware Version

Firmware

•Name

•Version

62 omreport: Viewing System Status Using the Instrumentation Service

Network Interface Card

The following details are listed for each NIC 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

•Product ID

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

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.

omreport: Viewing System Status Using the Instrumentation Service 63

Example Command Output

Ty p e :

omreport system version

or

omreport servermodule 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 your
system’s configuration:

Version Report

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

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

Name : BIOS
Version : 0.2.16
Updateable : N/A

Name : BMC
Version : 0.26
Updateable : N/A

Name : Primary Backplane
Version : 1.01
Updateable : N/A

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

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

Name : Microsoft Windows Server 2003,
Enterprise Edition
Version : 5.2 <Build 3790 : Service Pack 1>
<x86>
Updateable : N/A

Name : Dell Server Administrator
Version : 5.5.0
Updateable : N/A

64 omreport: Viewing System Status Using the Instrumentation Service

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 the administrator's privilege to
clear command, alert, and hardware logs; the administrator's privilege to
configure and execute system shutdown; power user and administrator's
privilege to default or specify values for warning events on fans, voltage
probes, and temperature probes; power user and administrator's 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."

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

Table 4-1. System Availability for the omconfig Command

Command Level 1 Command Level 2 Applicable to

omconfig servermodule

mainsystem
system
chassis

Modular system
Modular system
Non-modular system
Non-modular system

omconfig: Managing Components Using the Instrumentation Service 65

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.

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

Command
Level 1

omconfig

Command
Level 2

about U, P, A Shows version number and properties for

preferences

Command
Level 3

details=true U, P, A Displays information for all of the Server

cdvformat A Specifies the delimiter for separating data

User
Privilege
Required

Use

the Server Administrator program.

Administrator programs that are installed.

fields reported in custom delimited
format (cdv).

66 omconfig: Managing Components Using the Instrumentation Service

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

(continued)

Command
Level 1

Command
Level 2

system/
servermodule

Command
Level 3

dirservice A Configures the Microsoft Active

snmp A Sets the SNMP root password. Configures

useraccess A Determines whether users below the

alertaction P, A Determines in advance the actions to be

alertlog P, A Allows the administrator to clear the alert

assetinfo P, A Enters and edits cost of ownership

cmdlog P, A Allows the administrator to clear the

esmlog P, A Allows the administrator to clear the ESM

events P, A Enables and disables SNMP traps.

pedestinations P, A Sets IP addresses for alert destinations.

platformevents A Determines the shutdown action, if any, to

recovery P, A Determines in advance how your system

shutdown A Allows the administrator to select from

User
Privilege
Required

Use

®

Directory

SNMP Set Operations.

administrator level are allowed to use
Server Administrator or not.

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

log.

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

command log.

log.

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

responds to a hung operating system.

several options when shutting down the
system.

service.

omconfig: Managing Components Using the Instrumentation Service 67

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

(continued)

Command
Level 1

Command
Level 2

chassis/
mainsystem

Command
Level 3

thrmshutdown A Sets the severity level at which a thermal

webserver A Starts or stops the Web server.

biossetup A Configures the behavior of specific system

bmc A Configures remote access information.

User
Privilege
Required

Use

event triggers a system shutdown.

components controlled by the BIOS.

NOTE: This command is phased-out in this

releases. It is replaced by the remoteaccess
command.

fans P, A Configures fan probe warning thresholds

by default or by value.

NOTE: You cannot change threshold

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

fancontrol P, A Allows you to optimize fan speed for

maximum cooling or quiet operation.

frontpanel A Configures the Po wer button and

info P, A Allows you to set an initial value, or to edit

leds P, A Specifies when to flash a chassis fault LED

memorymode A Enables or disables the spare bank and

pwrmonitoring P, A Configures power consumption

remoteaccess A Configures remote access information.

Nonmasking Interrupt (NMI) button if
present on the system.

the value for, asset tag or chassis name.

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

mirroring memory modes, and also specify
which mode to use.

information and thresholds.

68 omconfig: Managing Components Using the Instrumentation Service

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

(continued)

Command
Level 1

Command
Level 2

Command
Level 3

temps P, A Sets warning threshold values by default or

User
Privilege
Required

Use

value.

NOTE: You cannot change threshold

values on ESM3 and PowerEdge x8xx
systems.

volts P, A Sets warning threshold values by default or

value.

NOTE: You cannot change threshold

values on ESM3 and PowerEdge x8xx
systems.

storage See "Using the Storage Management

Service."

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 -?

omconfig: Managing Components Using the Instrumentation Service 69

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 the case of the omconfig system alertaction command, you can use various
options to prevent all of the command line interface (CLI) help from
scrolling by before you can read it.

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
Red Hat

®

Enterprise Linux®, or SUSE® Linux Enterprise Server operating

®

Windows®,

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 : Dell OpenManage Server Administrator

Version : 5.

Copyright : Copyright (C) Dell Inc. 1995-2008. All rights

Company : Dell Inc.

70 omconfig: Managing Components Using the Instrumentation Service

x.x

reserved.

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

omconfig about details=true

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 your configuration and the version
of Server Administrator that is available:

Contains: Instrumentation Service 5.

Storage Management Service 3.x.

Sun JRE - OEM Installed Version 3.x.

Secure Port Server 1.x.

Core Service 1.x.

Instrumentation Service Integration Layer 1.x.

Storage Management Service Integration Layer 1.x.

Server Administrator 5.x.

x

x.x

x

x

x

x

x

x

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 your system's BIOS setup boot time settings.

NOTICE: 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.

omconfig: Managing Components Using the Instrumentation Service 71

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=enable | disable enable: Enables the bezel removal intrusion

attribute=
bootsequence

attribute=
conredirect

attribute=crab setting=enable | disable enable: Enables BIOS console redirection

name=value pair 2
setting=

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

setting=diskettefirst |
hdonly | devicelist
|cdromfirst

setting=enable | disable enable: Redirects the BIOS screen over Serial

Description

last: System returns to previous state.

on: System is turned on.

check during system boot.

disable: 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.

Port 1. Keyboard and text output are
redirected over Serial Port 2.

disable: Turns off the BIOS console
redirection.

after system reboot.

disable: Disables BIOS console redirection.

NOTE: The command crab is valid for Dell

PowerEdge x9xx systems only.

attribute=cpuht setting=enable | disable enable: Enables logical processor

hyperthreading.

disable: Disables logical processor
hyperthreading.

attribute=cpuvt setting=enable | disable enable: Enables virtualization.

disable: Disables virtualization.

attribute=dbs setting=enable | disable enable: Enables Demand Based Power

Management (DBS) on the system.

disable: Disables DBS on the system.

72 omconfig: Managing Components Using the Instrumentation Service

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=diskette setting=off | auto |

attribute=dualnic setting=off | on |

attribute=
embhypvisor

attribute=extserial setting=com1 | com2 |

name=value pair 2
setting=

writeprotect

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

onpxenic1 | onpxenic2 |

setting=enabled |
disabled

rad

Description

off: Disables the diskette drive.

auto: Auto-enables the diskette drive.

writeprotect: Do not allow writes. Make the

diskette drive read-only.

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.

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.

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.

(

NICs).

omconfig: Managing Components Using the Instrumentation Service 73

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=fbr setting=9600 | 19200 |

attribute=ide setting=on | off

attribute=idepridrv setting=off | auto off: Disables the device.

attribute=intrusion setting=enable | disable enable: Enables the intrusion check during

attribute=intusb setting=enabled |

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

name=value pair 2
setting=

57600 | 115200

force=true

disabled

Description

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.

on: Enables this device.

off: Disables this device.

force=true: Verification of setting change.

auto: Detects and enables the device

automatically.

system boot. If the system also has bezel
intrusion checking, then the intrusion option
checks for removal of the bezel of the system.

disable: Disables the intrusion check during
system boot.

enabled: Enables the internal USB drive.

disabled: Disables the internal USB drive.

off: Disables the mouse.

74 omconfig: Managing Components Using the Instrumentation Service

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

omconfig: Managing Components Using the Instrumentation Service 75

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=nic3 setting=enabled |

attribute=nic4 setting=enabled |

attribute=numlock setting=on | off on: Uses the keypad as number keys.

name=value pair 2
setting=

enabledwithpxe |
disabled | enabledonly |
enablednonepxe |
enabledwithiscsi

enabledwithpxe |
disabled | enabledonly |
enablednonepxe |
enabledwithiscsi

Description

enabled: Enables the third NIC during
system boot.

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

disabled: Disables the third NIC during
system boot.

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

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

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

enabled: Enables the fourth NIC during
system boot.

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

disabled: Disables the fourth NIC during
system boot.

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

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

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

off: Uses the keypad as arrow keys.

76 omconfig: Managing Components Using the Instrumentation Service

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=ppaddress setting=off | lpt1 | lpt2 |

attribute=ppmode setting=at | ps2 | ecp |

attribute=
primaryscsi

attribute=romb setting=raid | off | scsi

attribute=romba setting=raid | scsi

attribute=rombb setting=raid | scsi

name=value pair 2
setting=

lpt3

epp

setting=on | off
force=true

force=true

force=true

force=true

Description

off: Disables the parallel port address.

lpt1: Locates the device on LPT1.

lpt2: Locates the device onLPT2.

lpt3: Locates the device on LPT3.

at: Sets the parallel port mode to type AT.

ps2: Sets the parallel port mode to type PS/2.

ecp: Sets the parallel port mode to type ECP

(extended capabilities port).

epp: Sets the parallel port mode to type EPP
(enhanced parallel port).

NOTICE: If you modify the setting for

primary scsi, romb, romba, or rombb,
your system becomes inoperable until
you reinstall the operating system.

on: Enables this device.

off: Disables this device.

force=true: Verification of setting change.

raid: Instructs the BIOS to detect RAID-on-

motherboard as a RAID device.

off: Disables the device during system boot.

scsi: Instructs the BIOS to detect this device

as a SCSI device.

force=true: Verification of setting change.

raid: Instructs the BIOS to detect RAID-on-

motherboard channel A as a RAID device.

scsi: Instructs the BIOS to detect this device
as a SCSI device.

force=true: Verification of setting change.

raid: Instructs the BIOS to detect RAID-on-

motherboard channel B as a RAID device.

scsi: Instructs the BIOS to detect this device
as a SCSI device.

force=true: Verification of setting change.

omconfig: Managing Components Using the Instrumentation Service 77

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

attribute=sata setting=off | ata | raid off: Disables the SATA controller.

attribute=sataport
(0...7) or (A...H)

attribute=
secondaryscsi

attribute=serialcom setting=off | on |com1

attribute=
serialport1

name=value pair 2
setting=

setting=off | auto off: Disables the SATA port.

setting=on | off on: Enables this device.

|com2

setting=off | auto | com1
| com3 | bmcserial |
bmcnic | rac | com1bmc

Description

ata: Sets the onboard SATA controller to ATA
mode.

raid: Sets the onboard SATA controller to
RAID mode.

auto: Automatically enable the SATA port.

off: Disables this device.

off: Disables serial communication setting.

on: Enables serial communication setting

without console redirection.

com1: Enables serial communication setting
with console redirection via COM 1.

com2: Enables serial communication setting
with console redirection via COM 2.

off: Disables serial port 1.

auto: Maps serial port 1 to a COM port.

com1: Maps serial port 1 to COM port 1.

com3: Maps serial port 1 to COM port 3.

bmcserial: Maps serial port 1 to BMC Serial.

bmcnic: Maps serial port 1 to the Baseboard

Management Controller (BMC) NIC.

rac: Maps serial port 1 to the Remote Access
Controller (RAC).

com1bmc: Maps serial port 1 to COM port 1
bmc.

NOTE: This command is valid on PowerEdge

1850, 2800, and 2850 systems only.

attribute=
serialport2

setting=off | auto | com2
|com4

off: Disables serial port 2.

auto: Maps serial port 2 to a COM port.

com2: Maps serial port 2 to COM port 2.

com4: Maps serial port 2 to COM port 4.

78 omconfig: Managing Components Using the Instrumentation Service

Table 4-3. BIOS Setup Settings

(continued)

name=value pair 1
attribute=

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

attribute=uausb setting=on | backonly |

attribute=usb setting=enabled |

name=value pair 2
setting=

off

disabled

Description

off: Disables the speaker.

on: Enables the user-accessible USB port(s)

backonly: Enables only the user accessible

USB port(s) located at the back of the system.

off: Disables the user-accessible USB port(s).

enabled: Enables the USB port(s).

disabled: Disables the USB port(s).

NOTE: Depending on your system’s hardware,

only one of the two attributes usb and usbb is
available for configuring the USB port(s).

attribute=usbb setting=enabled |

enabledwithbios|
disabled

enabled: Enables the USB port(s) during
system boot, without BIOS support.

enabledwithbios: Enables the USB port(s)
during the system boot, with BIOS support.

disabled: Disables the USB port(s) during
system boot.

NOTE: Depending on your system’s hardware,

only one of the two attributes usb and usbb is
available for configuring the USB port(s).

omconfig chassis bmc/omconfig mainsystem bmc

NOTE: This command is phased-out in this release. It is replaced by the omconfig

chassis remoteaccess/omconfig mainsystem remoteaccess command.

omconfig chassis currents/omconfig mainsystem currents

NOTE: This command is no longer available through Server Administrator.

omconfig chassis fans/omconfig mainsystem fans

Use the omconfig chassis fans or omconfig mainsystem fans command to
set fan probe warning thresholds. As with other components, you can view
both warning and failure threshold values, but you cannot set failure
thresholds. Your system's manufacturer sets the minimum and maximum
failure thresholds.

omconfig: Managing Components Using the Instrumentation Service 79

Valid Parameters for Fan Warning Thresholds

Table 4-4 shows the valid parameters for setting fan warning thresholds:

Table 4-4. omconfig chassis fans/omconfig chassis fans

name=value pair Description

index=<n> Number of the probe or probe index (must be specified).

warnthresh=default Sets minimum and maximum warning thresholds to default.

minwarnthresh=<n> Minimum warning threshold.

maxwarnthresh=<n> Maximum warning threshold.

Default Minimum and Maximum Warning Thresholds

NOTE: Systems that contain ESM3, ESM4, and BMC capabilities do not allow you to

set warning threshold values to default values.

If you want to set both the upper and lower fan warning threshold values to
the recommended default value, type:

omconfig chassis fans index=0 warnthresh=default

or

omconfig mainsystem fans index=0 warnthresh=
default

You cannot default one value and set another. In other words, if you default
the minimum warning threshold value, you are also selecting the default
value for the maximum warning threshold value.

Specifying a Value for Minimum and Maximum Warning Thresholds

If you prefer to specify values for the fan probe warning thresholds, you must
specify the number of the probe you are configuring and the minimum and/or
maximum warning threshold values. In the following example, the probe that
is being configured is probe 0. The first command sets only the minimum
threshold; the second sets minimum and maximum thresholds:

omconfig chassis fans index=0 minwarnthresh=4580

or

omconfig mainsystem fans index=0 minwarnthresh=
4580

80 omconfig: Managing Components Using the Instrumentation Service

omconfig chassis fans index=0 minwarnthresh=4580
maxwarnthresh=9160

or

omconfig mainsystem fans index=0 minwarnthresh=
4580 maxwarnthresh=9160

When you issue the command and the system sets the values you specify, the
following message appears:

Fan probe warning threshold(s) set successfully.

NOTE: Minimum and maximum warning thresholds for the fan probe cannot be set

on PowerEdge

x

8xx and x9xx systems.

omconfig chassis fancontrol/omconfig mainsystem fancontrol

Use the omconfig chassis fancontrol or omconfig mainsystem fancontrol
command to set the fan speed. You can optimize speed for cooling or for
quiet operation. Table 4-5 shows the valid parameters for the command.

Table 4-5. omconfig chassis fancontrol/omconfig mainsystem fancontrol

name=value pair Description

speed=quiet Sets fan speed for quiet operation.

speed=maxcool Sets fan speed for maximum cooling.

omconfig chassis frontpanel/omconfig mainsystem frontpanel

Use the omconfig chassis frontpanel or omconfig mainsystem frontpanel
command to configure the Power button and the Nonmasking Interrupt
(NMI) button and to specify and configure the LCD line number.

NOTE: The Power and NMI buttons can be configured only if present on the

system.

Table 4-6 shows the valid parameters for the command.

Table 4-6. omconfig chassis frontpanel/omconfig mainsystem frontpanel

name=value pair 1 name=value pair 2 Description

lcdindex=<index> NA Specifies the LCD line number.
config=none |

default | custom

omconfig: Managing Components Using the Instrumentation Service 81

NA none: Sets the LCD text to none.

default: Sets the LCD text to default.

custom: Sets the LCD text to custom.

Table 4-6. omconfig chassis frontpanel/omconfig mainsystem frontpanel

name=value pair 1 name=value pair 2 Description

text=<custom text> NA Sets the custom text for LCD when config=

custom.

nmibutton enable=true | false true: Enables the NMI button on the system.

false: Disables the NMI button on the system.

powerbutton enable=true | false true: Enables the Power button on the system.

false: Disables the Power button on the system.

(continued)

omconfig chassis info/omconfig mainsystem info

Use the omconfig chassis info or omconfig mainsystem info command to
enter an asset tag name for your system and a chassis name for your system.
If your system is a modular one, you can enter asset tag names for modular
components as well. Table 4-7 shows the valid parameters for the command.

Table 4-7. omconfig chassis info/omconfig mainsystem info

name=value pair Description

index=<n> Number of the chassis whose asset tag or name you are setting.
tag=<text> Asset tag in the form of alphanumeric text. Letters or numbers

name=<text> Name of the chassis.

In the following example, the asset tag for the main system chassis is being set
to buildsys:

omconfig chassis info index=0 tag=buildsys

or

omconfig mainsystem info index=0 tag=buildsys

cannot exceed 10 characters.

Index 0 always defaults to the main system chassis. The following command
omits index=n, but accomplishes the same thing:

omconfig chassis info tag=buildsys

or

omconfig mainsystem info tag=buildsys

An acceptable command, when executed, results in the following message:

Chassis info set successfully.

82 omconfig: Managing Components Using the Instrumentation Service

For some chassis, you can assign a different name. You cannot rename the
main system chassis. In the example below, the command renames chassis 2
from storscsi1 to storscsia:

omconfig chassis info index=2 name=storscsia

or

omconfig mainsystem info index=2 name=storscsia

As with other commands, the CLI issues an error message if you do not have a
chassis 2 (the main chassis=0). The CLI allows you to issue commands only
for the system configuration you have.

omconfig chassis leds/omconfig mainsystem leds

Use the omconfig chassis leds or omconfig mainsystem leds command to
specify when to flash a chassis fault LED or chassis identification LED. This
command also allows you to clear the LED for the system's hard drive.
Table 4-8 shows the valid parameters for the command.

Table 4-8. omconfig chassis leds/omconfig mainsystem leds

name=value pair 1 name=value pair 2 Description

index=<n> NA Number of the chassis where the LED resides

(defaults to chassis 0, main system chassis).

led=fault severity=warning | critical Select to flash the LED either when a warning

led=hdfault action=clear Sets the number of faults for the hard drive

led=identify flash=off | on

time-out=<n>

event occurs or when a critical event occurs.

back to zero (0).
Sets the chassis identification LED to off or on.

Set the time-out value for the LED to flash to a
number of seconds.

omconfig chassis memorymode/omconfig mainsystem memorymode

Use the omconfig chassis memorymode or omconfig mainsystem
memorymode command to specify the redundancy mode you want to use for

your system’s memory in case of memory errors.

Redundant memory enables a system to switch to other available memory
modules if unacceptable errors are detected in the modules that the system is
currently using. The omconfig chassis memorymode or omconfig
mainsystem memorymode command allows you to disable redundancy;

omconfig: Managing Components Using the Instrumentation Service 83

when you disable redundancy, you instruct the system not to switch to other
available memory modules when the module the system is using begins to
encounter errors. To enable redundancy, choose among spare, mirror, and RAID.

Spare mode disables a bank of system memory in which a correctable memory
event is detected, enables the spare bank, and copies all the data from the
original bank to the spare bank. Spare bank requires at least three banks of
identical memory; the operating system does not recognize the spare bank.

Mirror mode switches to a redundant copy of memory when an uncorrectable
memory event is detected. After switching to the mirrored memory, the
system does not switch back to the original system memory until the next
reboot. The operating system does not recognize half of the installed system
memory in this mode.

RAID mode provides an extra level of memory checking and error recovery at
the expense of some memory capacity.

84 omconfig: Managing Components Using the Instrumentation Service

Table 4-9 shows the valid parameters for the command.

Table 4-9. omconfig chassis memorymode/omconfig mainsystem memorymode

name=value pair 1 Description

index=<n> Number of the chassis where the memory module resides (the default is

redundancy=spare |
mirror | disabled |
raid5

chassis 0, the main system chassis).
Spare disables the memory module that has a correctable memory event

and copies the failing module’s data to a spare bank.
Disabled indicates that the system is not to use other available memory
modules if uncorrectable memory events are detected.
Mirror switches the systems to a mirrored copy of the memory if the
failing module has an uncorrectable memory event. In the mirror mode,
the operating system does not switch back to the original module until
the system reboots.
RAID-5 is a method of system memory configuration. This is logically
similar to the RAID-5 mode used in hard drive storage systems. This
memory mode provides an extra level of memory checking and error
recovery at the expense of some memory capacity. The RAID mode
supported is RAID level 5 striping with rotational parity.

omconfig chassis pwrmonitoring/omconfig mainsystem pwrmonitoring

Use the omconfig chassis pwrmonitoring or omconfig mainsystem
pwrmonitoring command to configure power consumption information.

Table 4-10. omconfig chassis pwrmonitoring/omconfig mainsystem pwrmonitoring

name=value pair 1 name=value pair 2 Description

index=<n> NA Number of the probe or probe index

config=probe NA Sets the threshold value for the power

warnthresh=settodefault NA Sets minimum and maximum warning

warnthresh=<n> NA Sets a value for the warning threshold.
config=resetreading type=energy | peakpower energy: Resets the system energy reading.

(must be specified).

consumption probe.

thresholds values to default.

peakpower: Resets the system peak power.

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

PMBus only.

omconfig: Managing Components Using the Instrumentation Service 85

Default Warning Thresholds

NOTE: The capabilities for managing sensors vary by systems.

If you want to set both the upper and lower power consumption probe
warning threshold values to the recommended default value, type:

omconfig chassis pwrmonitoring index=0 warnthresh=
settodefault

or

omconfig mainsystem pwrmonitoring index=0
warnthresh=settodefault

You cannot default one value and set another. In other words, if you default
the minimum warning threshold value, you are also selecting the default
value for the maximum warning threshold value.

Specify a Value for Warning Thresholds

If you prefer to specify values for the power consumption probe warning
thresholds, you must specify the number of the probe you are configuring and
the minimum and/or maximum warning threshold value. In the following
example, the probe that is being configured is probe 4:

omconfig chassis pwrmonitoring index=4 warnthresh=
325

or

omconfig mainsystem pwrmonitoring index=4
warnthresh=325.

When you issue the command and the system sets the values you specify, the
following message appears:

Power consumption probe warning threshold(s) set
successfully.

omconfig chassis remoteaccess/omconfig mainsystem remoteaccess

NOTE: This command is applicable to PowerEdge x8xx and x9xx systems only.

Use the omconfig chassis remoteaccess or omconfig mainsystem
remoteaccess command to configure:

• Remote access on a local area network (LAN).

• The serial port for BMC or RAC, whichever is installed.

86 omconfig: Managing Components Using the Instrumentation Service

• The BMC or RAC on a serial over LAN connection.

• Terminal settings for the serial port.

• Advanced settings for a serial over LAN connection.

• Information on a BMC or RAC user.

NOTE: You have to Enter the user ID to configure user information.

Ty p e :

omconfig chassis remoteaccess

or

omconfig mainsystem remoteaccess

The output of the omconfig chassis remoteaccess or omconfig mainsystem
remoteaccess command lists each of the available configurations. Table 4-11

shows the valid parameters:

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=advsol characcuminterval=number number: Sets the character accumulate

config=nic enable=true | false true: Enables IPMI over LAN.

name=value pair 2 Description

interval in 5 millisecond intervals.

charsendthreshold=number number: Sets the number of characters.

encryptkey=text

confirmencryptkey=text

BMC automatically sends a serial over LAN
data packet that contains the number of
characters as soon as this number of
characters (or greater) has been accepted
from the baseboard serial controller into
the BMC.

false: Disables IPMI over LAN.
text: Tex t us e d fo r e nc r y pti o n an d

confirmation of encryption.

NOTE: The text option is supported only on

PowerEdge x9xx systems.

gateway=Gateway Gateway: Sets a gateway address if you have

selected static as the IP address source for the
BMC LAN interface.

omconfig: Managing Components Using the Instrumentation Service 87

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

name=value pair 2 Description

enablenic=true | false true: Enables DRAC NIC.

(continued)

false: Disables DRAC NIC

NOTE: The enablenic option is supported on

PowerEdge x9xx systems that have DRAC 5
installed.

config=nic
(continued)

IP address=IP ip: Sets the IP address if you have selected

ipsource=static | dhcp |
systemsoftware

static as the IP address source for the BMC
LAN interface.

static: Static if the IP address of the BMC
LAN interface is a fixed, assigned IP address.

dhcp: DHCP if the source of the IP address
of the BMC LAN interface is the dynamic
host configuration protocol.

systemsoftware: System software if the source
of the IP address of the BMC LAN interface
is from the system software.

NOTE: Not all commands may be supported

on your system.

nicselection=nic1 |
teamednic1nic2 | dracnic

nic1: Enables NIC 1.

teamednic1nic2: Enables NIC teaming

functionality.

dracnic: Enables DRAC NIC if DRAC 5 is
installed.

NOTE: The nicselection option is supported

only on PowerEdge x9xx systems.

privilegelevel=administrator
| operator | user

subnet=Subnet subnet: Sets a subnet mask if you have

administrator: Sets the maximum privilege
level that can be accepted on a LAN channel
to Administrator.

operator: Sets the maximum privilege level
that can be accepted on a LAN channel
to Operator.

user: Sets the maximum privilege level that
can be accepted on a LAN channel to User.

selected static as the IP address source for the
BMC LAN interface.

88 omconfig: Managing Components Using the Instrumentation Service

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=nic
(continued)

config=serial baudrate=9600 | 19200 |

name=value pair 2 Description

vlanenable=true | false true: Enables the virtual LAN identification.

vlanid=number number: Virtual LAN identification in the

vlanpriority=number number: Priority of virtual LAN

38400 | 57600 | 115200

(continued)

false: Disables the virtual LAN identification.

range of 1 to 4094.

identification in the range of 0 to 7.
9600: Sets the connection speed to 9600 bits

per second.

19200: Sets the connection speed to 19200
bits per second.

38400: Sets the volatile and non-volatile
connection speed to 38400 bits per second.

57600: Sets the volatile and non-volatile
connection speed to 57600 bits per second.

115200: Sets the volatile and non-volatile
connection speed to 115200 bits per second.

NOTE: Baud rates of 9600 and 19200 are

supported on PowerEdge 1800, 1850, 2800, and
2850 systems.
Baud rates of 19200, 38400, and 57600 are
supported on PowerEdge x9xx systems.
Baud rate of 115200 is supported on certain
systems that have a DRAC 5 installed.
Baud rate of 19200, 57600, and 115200 are
supported on xx0x systems that have iDRAC
installed.

flowcontrol=none | rtscts none: No control over the flow of

communication through the serial port.

rtscts: RTS is ready to send and CTS is clear
to send.

omconfig: Managing Components Using the Instrumentation Service 89

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=serial

(continued)

name=value pair 2 Description

mode=directbasic |
directterminal |
directbasicterminal |
modembasic |
modemterminal |
modembasicterminal

(continued)

directbasic: Type of messaging used for IPMI
messaging over a serial connection.

directterminal: Type of messaging that uses
printable ASCII characters and allows a
limited number of text commands over a
serial connection.

directbasicterminal: Both basic and terminal
mode messaging over a serial connection.

modembasic: Type of messaging used for
IPMI messaging over a modem.

modemterminal: Type of messaging that uses
printable ASCII characters and allows a
limited number of text commands over
amodem.

modembasicterminal: Both basic and
terminal messaging over a modem.

NOTE: Not all commands may be supported

on the system.

privilegelevel=administrator
| operator | user

administrator: Sets the maximum privilege
level that can be accepted on a serial
connection, to Administrator.

operator: Sets the maximum privilege level
that can be accepted on a serial connection,
to Operator.

user: Sets the maximum privilege level that
can be accepted on a serial connection,
to User.

90 omconfig: Managing Components Using the Instrumentation Service

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=
serialoverlan

name=value pair 2 Description

enable=true | false true: Enables serial over LAN for the BMC.

baudrate=9600 | 19200 |
38400 | 57600 | 115200

(continued)

false: Disables serial over LAN for the BMC.
9600: Sets the volatile and nonvolatile

connection speed to 9600 bits per second.

19200: Sets the volatile and non-volatile
connection speed to 19200 bits per second.

38400: Sets the volatile and non-volatile
connection speed to 38400 bits per second.

57600: Sets the volatile and non-volatile
connection speed to 57600 bits per second.

115200: Sets the volatile and non-volatile
connection speed to 115200 bits per second.

NOTE: Baud rates of 9600 and 19200 are

supported on PowerEdge 1800, 1850, 2800, and
2850 systems.
Baud rates of 19200, and 57600 are supported
on PowerEdge x9xx systems.
Baud rate of 115200 is supported on certain
systems that have a DRAC 5 installed.
Baud rate of 19200, 57600, and 115200 are
supported on xx0x systems that have iDRAC
installed.

config=
settodefault

config=
terminalmode

privilegelevel=administrator
| operator | user

deletecontrol=outputdel |
outputbkspspbksp

administrator: Sets the maximum privilege
level that can be accepted on a serial over
LAN channel, to Administrator.

operator: Sets the maximum privilege level
that can be accepted on a serial over LAN
channel, to Operator.

user: Sets the maximum privilege level that
can be accepted on a serial over LAN
channel, to User.

Takes the default configuration settings.

outputdel: BMC outputs a <del> character
when <bksp> or <del> is received.

outputbkspspbksp: BMC outputs a
<bksp><sp><bksp> character when
<bksp> or <del> is received.

omconfig: Managing Components Using the Instrumentation Service 91

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=
terminalmode

(continued)

name=value pair 2 Description

echocontrol=enabled |
disabled

handshakingcontrol=enabled
| disabled

inputlinesequence=cr | null cr: The console uses <CR> as a new

lineediting=enabled |
disabled

newlinesequence=none | crlf
| null | cr | lfcr | lf

(continued)

enabled: Enables characters to be sent to
the screen.

disabled: Disables characters to be sent to
the screen.

enabled: Directs the BMC to output a
character sequence that indicates when its
input buffer is ready to accept
another command.

disabled: Does not direct the BMC to output
a character sequence that indicates when its
input buffer is ready to accept
another command.

line sequence.

null: The console uses <NULL> as a new
line sequence.

enabled: Enables line editing as a line
is typed.

disabled: Disables line editing as a line is
typed.

none: BMC does not use a
termination sequence.

crlf: BMC uses <CR-LF> as a new line
sequence when the BMC writes a new line to
the console.

null: BMC uses <Null> as a new line
sequence when the BMC writes a new line to
the console.

cr: BMC uses <CR> as a new line sequence
when the BMC writes a new line to
the console.

lfcr: BMC uses <LF-CR> as a new line
sequence when the BMC writes a new line to
the console.

lf: BMC uses <LF> as a new line sequence
when the BMC writes a new line to
the console.

92 omconfig: Managing Components Using the Instrumentation Service

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=user id=number enable=true |

name=value pair 2 Description

false

id=number
enableserialoverlan=true |
false

(continued)

id=number: ID (in numeric format) of the
user being configured.

enable=true: Enables user.

enable=false: Disables user.
id=number: ID (in numeric format) of the

user being configured.

enableserialoverlan=true: Enables serial
over LAN.

enableserialoverlan=false: Disables serial
over LAN.

NOTE: The enableserialoverlan option is

supported only on PowerEdge x9xx systems.

id=number name=text number: ID (in numeric format) of the user

id=number newpw=text

confirmnewpw=text

id=number
serialaccesslevel=
administrator | operator |
user | none

being configured.

name=text: Name of the user.
number: ID (in numeric format) of the user

being configured.

newpw=text: New password of the user.

confirmnewpw=text: Confirm the new

password.
id=number: ID (in numeric format) of the

user being configured.

serialaccesslevel=administrator: User with
an ID has access privileges of an
Administrator for the serial port channel.

serialaccesslevel=operator: User with an ID
has access privileges of an Operator for the
serial port channel.

serialaccesslevel=user: User with an ID has
access privileges of a User for the
serial port channel.

serialaccesslevel=none: User with an ID
does not have access privileges for the
serial port channel.

omconfig: Managing Components Using the Instrumentation Service 93

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

config=user

(continued)

name=value pair 2 Description

id=number lanaccesslevel=
administrator | operator |
user| none

id=user id
dracusergroup=admin |
poweruser | custom | none

(continued)

id=number: ID number of the user being
configured.

lanaccesslevel=administrator: User with an
ID has access privileges of an Administrator
for the LAN channel.

lanaccesslevel=operator: User with an ID
has access privileges of an Operator for the
LAN channel.

lanaccesslevel=user: User with an ID has
access privileges of a user for the
LAN channel.

lanaccesslevel=none: User with an ID does
not have access privileges for the
LAN channel.

id=user id: User ID of the user
being configured.

dracusergroup=admin: Enables the
Administrator user privileges.

dracusergroup=poweruser: Enables the
Power User privileges.

dracusergroup=custom: Enables the
Custom User privileges.

NOTE: See Table 4-12 for more information on

the name=value pair. dracusergroup=custom.

dracusergroup=none: Does not enable

user privileges.

94 omconfig: Managing Components Using the Instrumentation Service

Table 4-11. omconfig chassis remoteaccess/omconfig mainsystem

remoteaccess

name=value pair 1
config=

name=value pair 2 Description

id=user id
extimpiusergroup=admin |
poweruser | custom | none

NOTE: extimpiusergroup

user group is available only on
Dell xx0x modular systems.

(continued)

id=user id: User ID of the user
being configured.

extimpiusergroup=admin: Enables the
Administrator user privileges.

extimpiusergroup=poweruser: Enables the
Power User privileges.

extimpiusergroup=custom: Enables the
Custom User privileges.

NOTE: See Table 4-13 for more information on

the name=value pair. extimpiusergroup=
custom.

extimpiusergroup=none: Does not enable

user privileges.

Table 4-12. omconfig chassis remoteaccess config=user id=<user id>

dracusergroup=custom/omconfig mainsystem remoteaccess
config=user id=<user id> dracusergroup=custom

name=value pair 1 name=value pair 2 name=value pair 3 Description

config=user

(continued)

id=user id
dracusergroup=
custom

logindrac= true |
false

configuredrac= true
| false

configure users= true
| false

clearlogs= true |
false

executeservercomma
nds= true | false

accessconsoleredir=
true | false

accessvirtualmedia=
true | false

testalerts= true |
false

true/false: Enables/disables
logging into DRAC.

true/false: Enables/disables
configuration of DRAC.

true/false: Enables/disables
configuration of users.

true/false: Enables/disables
log clearance.

true/false: Enables/disables
execution of server commands.

true/false: Enables/disables
access to console redirection.

true/false: Enables/disables
access to virtual media.

true/false: Enables/disables
test alerts.

omconfig: Managing Components Using the Instrumentation Service 95

Table 4-13. omconfig chassis remoteaccess config=user id=<user id>

extimpiusergroup=custom/omconfig mainsystem remoteaccess config=
user id=<user id> extimpiusergroup=custom

name=value pair 1 name=value pair 2 name=value pair 3 Description

config=user

(continued)

id=user id
extimpiusergroup=custom

NOTE: extimpiusergroup

user group is available only on
Dell xx0x modular systems.

loginidrac= true |
false

configureidrac= true
| false

true/false:
Enables/disab les logging
into iDRAC.

true/false:
Enables/disables
configuration of
iDRAC.

omconfig chassis temps/omconfig mainsystem temps

Use the omconfig chassis temps or omconfig mainsystem temps command
to set warning thresholds for temperature probes. As with other components,
you can view both warning and failure threshold values, but you cannot set
failure threshold values. Your system's manufacturer sets the minimum and
maximum failure threshold values.

NOTE: Threshold values that you can set vary from one system configuration

to another.

Valid Parameters for Temperature Warning Thresholds

Table 4-14 shows the valid parameters for setting temperature warning
thresholds:

Table 4-14. omconfig chassis temps/omconfig mainsystem temps

name=value pair Description

index=<n> Number of the probe or probe index (must be specified).
warnthresh=default Sets the minimum and maximum warning threshold values to

minwarnthresh=<n> Sets the minimum warning threshold values (1 decimal place).
maxwarnthresh=<n> Sets the maximum warning threshold values (1 decimal place).

default.

96 omconfig: Managing Components Using the Instrumentation Service

Setting Minimum and Maximum Warning Threshold Values

If you want to set both the upper and lower temperature warning threshold
values to the recommended default value, type:

omconfig chassis temps index=0 warnthresh=default

or

omconfig mainsystem temps index=0 warnthresh=
default

You cannot default one value and set another. In other words, if you set the
minimum warning threshold value to the default value, you are also selecting
the default value for the maximum warning threshold value.

NOTE: The capabilities for managing sensors vary by systems.

Specify a Value for Minimum and Maximum Warning Thresholds

If you want to specify values for the temperature probe warning thresholds,
you must specify the number of the probe you are configuring and the
minimum and/or maximum warning threshold value. In the following
example, the probe that is being configured is probe 4:

omconfig chassis temps index=4 minwarnthresh=11.2
maxwarnthresh=58.7

or

omconfig mainsystem temps index=4 minwarnthresh=

11.2 maxwarnthresh=58.7

When you issue the command and the system sets the values you specify, the
following message appears:

Temperature probe warning threshold(s) set
successfully.

NOTE: In PowerEdge x8xx and x9xx systems, warning threshold for the

temperature probe can be set only for the ambient temperature.

omconfig chassis volts/omconfig mainsystem volts

Use the omconfig chassis volts or omconfig mainsystem volts command to
set voltage probe warning thresholds. As with other components, you can view
both warning and failure threshold values, but you cannot set failure
threshold values. Your system's manufacturer sets the minimum and
maximum values for the failure thresholds.

omconfig: Managing Components Using the Instrumentation Service 97

Valid Parameters for Voltage Warning Thresholds

Table 4-15 shows the valid parameters for setting voltage warning
threshold values.

NOTE: Threshold values that you can set vary from one system configuration

to another.

Table 4-15. omconfig chassis volts/omconfig mainsystem volts

name=value pair Description

index=<n> Probe index (must be specified).
warnthresh=default Sets minimum and maximum warning threshold values to

default.
minwarnthresh=<n> Sets minimum warning threshold value(3 decimal places).
maxwarnthresh=<n> sets maximum warning threshold value (3 decimal places).

Default Minimum and Maximum Warning Threshold Values

If you want to set both the upper and lower voltage warning threshold values
to the recommended default value, type:

omconfig chassis volts index=2 warnthresh=default

or

omconfig mainsystem volts index=2 warnthresh=
default

You cannot default one value and set another. In other words, if you default the
minimum warning threshold value, you are also selecting the default value for
the maximum warning threshold value.

NOTE: Systems that contain ESM3 capabilities do not allow you to set warning

threshold values to default values.

Specify a Value for Minimum and Maximum Warning Thresholds

If you want to specify values for the voltage probe warning thresholds, you
must specify the number of the probe you are configuring and the minimum
and/or maximum warning threshold values. In the following example, the
probe being configured is probe 0:

omconfig chassis volts index=0 minwarnthresh=1.900
maxwarnthresh=2.250
or
omconfig mainsystem volts index=0 minwarnthresh=

1.900 maxwarnthresh=2.250

98 omconfig: Managing Components Using the Instrumentation Service

When you issue the command and the system sets the values you specify, the
following message appears:

Voltage probe warning threshold(s) set
successfully.

NOTE: Minimum and maximum warning threshold values for the voltage cannot be

set on PowerEdge x8xx systems.

omconfig preferences

Use the omconfig preferences command to set system preferences. Use the
command line, to set the SNMP root password and specify the user levels able
to access Server Administrator. You can also configure the Active Directory
service and SNMP set operations.

omconfig preferences cdvformat

Use the omconfig preferences cdvformat to specify the delimiters for
separating data fields reported in the custom delimited format. The valid
values for delimiters are: exclamation, semicolon, at, hash, dollar, percent,
caret, asterisk, tilde, question, colon, comma, and pipe.

The following example shows how to set the delimiter for separating data
fields to asterisk:

omconfig preferences cdvformat delimiter=asterisk

omconfig preferences dirservice

You can use the omconfig preferences dirservice command to configure the
Active Directory service. The <productname>oem.ini file is modified to
reflect these changes. If the "adproductname" is not present in the
<productname>oem.ini file then a <computername>-<productname>
default value is used. <computername> refers to the name of the computer
running Server Administrator and <productname> refers to the name of the
product defined in omprv32.ini. For Server Administrator, the product name
is "omsa".

omconfig: Managing Components Using the Instrumentation Service 99

Therefore, for a computer named "myOmsa" running Server Administrator,
the default name would be "myOmsa–omsa". This is the name of Server
Administrator defined in Active Directory by using the snap–in tool. This
name must match the name for the application object in Active Directory in
order to find user privileges.

NOTE: This command is applicable only on systems running the Windows

operating system.

Table 4-16 shows the valid parameters for the command.

Table 4-16. Active Directory Service Configuration Parameters

name=value pair Description

prodname=<text> Specifies the product to which you want to apply the Active Directory

enable=<true | false> true: Enables Active Directory service authentication support and the

adprodname=<text> Specifies the name of the product as defined in the Active Directory

configuration changes. prodname refers to the name of the product
defined in omprv32.ini. For Server Administrator, it is "omsa".

Active Directory Login option on the login page.

false: Disables Active Directory service authentication support and the
Active Directory Login option on the login page. If the Active
Directory Login option is not present, you can only login to the local

machine accounts.

service. This name links the product with the Active Directory privilege
data for user authentication.

omconfig preferences snmp

Setting the SNMP root password allows administrators to restrict access to
SNMP set operations that allow important systems management
interventions. You can configure the SNMP root password normally (by
typing all of the parameters in one command line) or interactively.

Using the omconfig preferences snmp command, you can also configure
SNMP set operations.

NOTICE: Interactive mode is the more secure method of setting the SNMP root

password. In non-interactive mode, the values you enter for the newpw and
confirmnewpw options appear on your system’s monitor when you type them. In the
interactive mode, the values you type for passwords are masked.

100 omconfig: Managing Components Using the Instrumentation Service