Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc.
is strictly forbidden.
Trademarks used in this text: Dell™, PowerEdge™, and OpenManage™ are trademarks of Dell Inc.
Microsoft
or registered trademarks of Microsoft Corporation in the United States and/or other countries. SUSE™
is a registered trademark of Novell Inc. in the United States and other countries. Red Hat
Hat Enterprise Linux
countries. Intel
Intel Corporation in the United States and other countries. AMD
AMD PowerNow!™ are trademarks of Advanced Micro Devices Inc. VMware
trademark and ESX Server™ is a trademark of VMware Inc in the United States and/or other jurisdictions.
Citrix
Systems, Inc. in the United States and/or other countries.
Other trademarks and trade names may be used in this publication to refer to either the entities claiming
the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and
trade names other than itsown.
®
, Windows®, Active Directory®, MS-DOS®, and Windows Server® are either trademarks
®
®
are registered trademarks of Red Hat, Inc. in the United States and other
®
, Pentium®, and Itanium® are registered trademarks and Intel386™ is a trademark of
®
, Xen®, XenServer®, and XenMotion® are either registered trademarks or trademarks of Citrix
Dell OpenManage Server Administrator (OMSA) provides a comprehensive,
one-to-one systems management solution through either an integrated Web
browser-based graphical user interface (GUI) or a command line interface
(CLI). Server Administrator is designed for system administrators to manage
systems locally and remotely on a network. It allows system administrators to
focus on managing their entire network by providing a comprehensive one-toone systems management.
In the context of Server Administrator, a system refers to a stand-alone
system, a system with attached network storage units in a separate chassis, or
a Blade system consisting of one or more server modules in a modular
enclosure.
Server Administrator provides easy-to-use management and administration of
local and remote systems through a comprehensive set of integrated
management services. Server Administrator is the sole installation on the
system being managed and is accessible both locally and remotely from the
Server Administrator home page. Server Administrator enables you to access
remotely monitored systems by dial-in, LAN, or wireless connections.
The configuration features enable Server Administrator to perform essential
tasks described in detail in the following sections. This CLI guide documents
all the commands that apply to Server Administrator and Storage
Management.
Introduction15
The reporting and viewing features enable retrieval of the overall health status
for systems on the network. You can view information about voltage,
temperature, fan's revolutions per minute (RPM), memory functioning, and
many other critical details at the component level. You can also see a detailed
account of the cost of ownership (COO) about the system, retrieve version
information about the BIOS, firmware, operating system, and all installed
software.
NOTE: Use the CLI instead of the Server Administrator home page, and turn the
Server Administrator Web server off for concerns on encryption. The CLI does not use
the Web server. Run the omconfig system webserver action=stop command to turn off
the Web server. The Web server starts automatically after a reboot, so run this
command each time a system starts up. See "omconfig system webserver or omconfig
servermodule webserver" on page 169 for more information.
NOTE: After installing Dell OpenManage Server Administrator, ensure that you log
out and log in to reset the path to access Dell OpenManage CLI utilities.
NOTE: For information on the terms used in this document, see the Glossary at
support.dell.com/manuals.
What's New in This Release
The release highlights of OpenManage Server Administrator are:
•Support for the following operating systems:
–Red Hat Enterprise Linux 5.8 (64-bit and 32-bit)
–Red Hat Enterprise Linux 6.2 (64-bit)
–VMware ESXi 5.0 Update 1
•Support for the following Dell PowerEdge systems: M820, T420, and T320
•Support for PowerEdge
custom branding. For more information, see
•Support for the following Network Interface Cards (NICs), Converged
Network Adapters
–Brocade 10Gb CNA (BR1020 and BR1741M-k)
–Emulex Single Port FC16 HBA
–Emulex Dual Port FC16 HBA
–Qlogic QLE2460 Single Port FC4 Adapter
OEM Ready
server models that allow reseller
dell.com/oem
(CNAs), and Fibre Channels (FCs):
16Introduction
–Qlogic QLE2462 Dual Port FC4 Adapter
–Brocade BR815- Single Port FC8 Adapter
–Brocade BR825- Dual Port FC8 Adapter
–Qlogic QLE2562 Dual Port FC8 Adapter
–Emulex LPe-12002 Dual Port FC8 Adapter
–Qlogic QME2572 Dual Port FC8 Mezz
–Emulex Lpe-1205-M Dual Port FC8 Mezz
–Qlogic QLE2560 Single Port FC8 Adapter
–Emulex LPe-12000 Single Port FC8 Adapter
–Broadcom 57810 Dual Port 10GbE KR Blade Converged
Mezzanine Card
–Broadcom 57810 Dual Port 10Gb Base-T
–Broadcom 57810 Dual Port 10GbE SFP
–Qlogic QME8252-K Mezz
–Qlogic P3+ Dual Port 10Gb SFP+/DA
•Support for the following Web browsers: Mozilla Firefox 10, 11, and 12
browsers
•Deprecated support for the following operating systems:
–RedHat Enterprise Linux 5 SP7 (32-bit and 64-bit)
–RedHat Enterprise Linux 6 SP1 (64-bit)
–
VMware ESXi 5.0
NOTE: For the supported operating systems list, see the Dell Systems Software
Support Matrix. To access this document, go to support.dell.com/manuals, click
Software, and select the product.
NOTE: CLI commands are not supported on systems with VMware ESXi operating
system.
Introduction17
Accessing the Windows Command Prompt to Run
CLI Commands
If you are running the Microsoft Windows operating system, use the 32-bit
command prompt to run a Server Administrator CLI command. Access the
32-bit command prompt using one of the following methods:
•Click
•Click
Start Programs Accessories Command Prompt
Start
NOTE: Do not type command in the Run dialog box to launch a command line
window; this activates the MS-DOS emulator command.com, which has
environment variable limitations that can cause subtle problems with CLI.
Run
and type
cmd.exe
Primary CLI Commands
The commands that carry out the functions of Server Administrator are:
•
omconfig
•
omhelp
•
omreport
The omconfig command writes values that you assign to an object's
properties. You can specify values for warning thresholds on components or
prescribe action that the system must perform when a certain warning or
failure event occurs. You can also use the omconfig command to assign
specific values to the system's asset information parameters, such as the
purchase price of the system, the system's asset tag, or the system's location.
The omhelp command displays short text help for CLI commands.
The shorthand equivalent of omhelp is the command for which you want
help followed by -?. For example, to display help for the omreport command,
type one of the following commands:
omhelp omreport
omreport -?
The omreport command displays reports of the management information of
the system.
NOTE: For an overall summary of the CLI commands, type omhelp.
18Introduction
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" on
omreport"omreport: Viewing System Status
NOTE: The omupdate commands are no longer supported in Server Administrator
and are replaced by Dell Update Package or the Server Update Utility commands. To
update the different components, download the Dell Update Package and run the
Section TitleRelated Sections
"omconfig system or
Using the Instrumentation Service"
on page 89
page 25
Using the Instrumentation Service"
on page 29
servermodule assetinfo: Editing
Cost of Ownership Values" on
page 175
<package name> /s [/f]command. For more information on the
corresponding CLI syntax, see the Dell Update Packages for Operating Systems User’s
Guide or the Dell OpenManage Server Update Utility User’s Guide at
support.dell.com/manuals.
Additional useful topic about the CLI include:
•"Working With CLI Command Results" on page 285
CLI Error Checking and Error Messages
When you type CLI commands, the CLI checks these commands for correct
syntax. If you type a command and the command is executed successfully,
a message is displayed, stating that the command is successful.
Success Messages
When you run a successful omconfig command, data for that component is
displayed.
The following table provides examples of valid omconfig commands and their
success messages.
Introduction19
Table 1-2. Commands and Messages
CommandMessage
omconfig chassis temps
index=0 warnthresh=
default
Temperature probe warning
threshold value(s) set
successfully.
BIOS setup configured
successfully. Change will
take effect after the next
reboot.
omconfig system assetinfo
info=depreciation
Asset information set
successfully.
duration=6
NOTE: Due to limitations, some commands do not alter the system settings even
though the commands are executed successfully. This is an expected behavior.
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 required to execute the command successfully.
If you execute a command for a component or feature that is not present in
the system configuration, the error message states that the component is not
present.
Command:
omconfig chassis volts index=3 minwarnthresh=
3.3000
20Introduction
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.
When you type the revised command with three decimal points, you receive
another error message:
Error! This voltage probe min warning threshold
must be between 11.400 and 12.480.
Revised command:
omconfig chassis volts index=3 minwarnthresh=
11.500
Message:
Voltage probe warning threshold(s) set
successfully.
Scripting and Comparing Using CLI
The Server Administrator CLI allows administrators to write batch programs
for 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.
Introduction21
A similar scenario is used to populate a large number of newly acquired systems
with detailed asset information. Much of the information are the same, such as
the manufacturer or lessor of the system, whether support for the system is
outsourced, name of the company providing insurance for the system,
method of depreciation, and so on. Any variable that is common to all systems
is scripted, sent to all managed systems, and executed. Asset information that
is unique to a system is 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 the 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
highest system usage compared with the same measurements at times of
lowest system usage. Command results are routed to a file for later analysis.
Reports can help administrators gain information that are used to adjust
usage patterns, to justify purchasing new system resources, or to focus on the
health of a problem component.
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 display a
very brief summary. The summary shows version information for the systems
management software installed on the system; for example,
Server Administrator 1.x.
22Introduction
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, the following command
displays a list of alert actions that are configured for components on a system.
omreport system alertaction
The most complex commands have all three command levels and can
have multiple name=value pairs. The following is an example of two
name=value pairs:
omconfig system assetinfo info=depreciation
duration=3
The following is an example of nine name=value pairs:
omconfig system assetinfo info=acquisition
purchasecost=
purchasedate=<mmddyy> ponum=
<n> waybill=<n> installdate=<mmddyy>
<n> signauth=<text>
expensed=<yes | no> costcenter=<text>
In each chapter of this document, command syntax and other information
about the commands are formatted using any of the following fields as
appropriate:
command
level 1
command
level 2
command
level 3
name=value
pair 1
name=value
pair 2
Introduction23
24Introduction
2
Using the omhelp Command
The omhelp command and its equivalent, <command>-?, accesses
the detailed help text interface of command line interface (CLI). You can get
help at several levels of detail.
Each fully-qualified CLI command may have a variable number of distinct
parts: the command (command level 1), one or more subcommands
(command level 2 and command level 3, if present), and one or more name=
value pair(s.)
By appending -? (space-dash-question mark) to any command, you can get
help for that command.
Example Help Commands
When you type omconfig -?, you get general help about the omconfig
command. The help at this level lists the available subcommands for
omconfig:
•about
•preferences
•chassis
•system
When you type omconfig system -?, CLI help lists all the
subcommands available for omconfig system:
•alertaction
•alertlog
•assetinfo
•cmdlog
•esmlog
•events
•platformevents
•pedestinations
Using the omhelp Command25
•recovery
•shutdown
•thrmshutdown
•webserver
Figure 2-1 shows the levels of help for a command.
Figure 2-1. Different Levels of Help for a Command
Also parse the omconfig system assetinfo command as follows:
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 the 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 is
displayed 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.
26Using the omhelp Command
For one info value, specify one or more optional parameter(s.) Table 2-1 lists
the optional parameters for info=acquisition:
omreport: Viewing System Status
Using the Instrumentation Service
The omreport command allows you to see detailed information about
the system components. You can also retrieve summaries for many system
components at one time, or 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. The fields are defined
only if they have a special or less familiar use.
As with all other components, use omreport to view component status, and
omconfig to manage a component. For information on configuring
components for management, see "omconfig: Managing Components Using
the Instrumentation Service" on page 89.
Use the omreport commands to get information you need to execute an
omconfig command. For example, to edit the minimum temperature for a
warning event on a temperature probe, you must know the index of the probe
you want to configure. Use omreport chassis temps to display a list of probes
and their indexes.
The omreport commands available on the system depend on the system
configuration. Table 3-1 lists the systems on which the omreport commands
are applicable.
Table 3-1. System Availability for the omreport Command
Command Level 1 Command Level 2Applicable To
omreportmodularenclosureBlade systems
servermoduleBlade systems
mainsystemBlade systems
systemRack and Tower systems
chassisRack and Tower systems
preferencesBlade or Rack, and Tower systems
omreport: Viewing System Status Using the Instrumentation Service29
Conventions for Parameter Tables
When listing the parameters for a command, the parameters are listed in
alphabetical order instead of the order in which they appear in the command
line interface (CLI).
The symbol |, often called pipe, is the logical exclusive or operator.
For example, enable | disable means enable or disable the component or
feature.
Command Summary of the omreport Command
Although this chapter lists all possible omreport commands, the commands
available on the system depend on the system configuration. The results of
the omreport command may vary from one system to another. The omreport
command displays data for the installed components only.
NOTE: When a system includes an external chassis, the displayed results vary by
operating system. On SUSE Linux Enterprise Server and Red Hat
systems, omreport commands display external chassis information in a separate
section after the main chassis information. On Microsoft Windows systems, data
about the external chassis does not appear in the omreport output.
Enterprise Linux
Table 3-2 provides a high-level summary of the omreport command. The
column titled Command level 1 shows the omreport command at its most
general use. 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 to view reports.
User privilege required refers to the type of privilege you need to run the
command, where U=User, P=Power User, and A=Administrator. Use is
a very general statement about the actions performed using omreport. More
details about the syntax and use of the command appear later in this section.
Tab le 3 -2 l is ts 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" on
page 29.
30omreport: 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 2Command
Level 3
User
Privilege
Required
Use
modularenclosureU, P, ADisplays the
information for all the
modular chassis.
aboutU, P, ADisplays the version
number and properties
for Server
Administrator.
details=true U, P, ADisplays the
information for all the
Server Administrator
programs installed.
chassis or
mainsystem
U, P, ADisplays the general
status of all the main
components.
acswitchU, P, ADisplays the failover
settings where
redundant AC power
lines are supported in a
system.
batteriesU, P, ADisplays the properties
set for batteries.
biosU, P, ADisplays the BIOS
information such as
manufacturer, version,
and release date.
biossetupADisplays the BIOS
setup properties
configured during
system boot.
omreport: Viewing System Status Using the Instrumentation Service31
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport
(continued)
Command
Level 1
Command Level 2Command
Level 3
fansU, P, ADisplays the status and
firmwareU, P, ADisplays the name and
frontpanelU, P, ADisplays whether the
fruU, P, ADisplays the Field
hwperformance U, P, ADisplays the status and
infoU, P, ADisplays a status
intrusionU, P, ADisplays the status of
User
Privilege
Required
Use
thresholds for system
fans.
version of the firmware.
front panel button
settings, such as the
Power button and/or
Nonmasking Interrupt
(NMI) button
(if present on the
system), are enabled or
disabled. It also displays
the front panel
encryption access
information and the
front panel LCD
information.
Replaceable Unit
(FRU) information.
cause for the system’s
performance
degradation.
summary for main
system chassis
components.
the system’s intrusion
sensor(s.)
32omreport: 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 2Command
Level 3
ledsU, P, ADisplays the properties
memoryU, P, ADisplays properties of
nicsU, P, ADisplays the NIC and
portsU, P, ADisplays the properties
processorsU, P, ADisplays properties of
pwrmanagement U, P, ADisplays power
pwrmonitoringU, P, ADisplays properties of
pwrsuppliesU, P, ADisplays the properties
User
Privilege
Required
Use
you have set for
light-emitting diodes to
flash under various alert
conditions.
the system's memory
arrays.
Team interface
properties.
for the system’s parallel
and serial ports, such as
I/O address, IRQ level,
connector type, and
maximum speed.
the system’s processors,
including speed,
manufacturer, and
processor family.
inventory details such
as system idle power,
system maximum
potential power, and
power budget
information.
power consumption.
of power supplies.
omreport: Viewing System Status Using the Instrumentation Service33
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport
(continued)
Command
Level 1
Command Level 2Command
Level 3
User
Privilege
Required
Use
remoteaccessU, P, ADisplays general
information on remote
access.
slotsU, P, ADisplays the properties
of the system’s
expansion slots and
other slot types.
tempsU, P, ADisplays the status and
thresholds for the
system temperature
sensors.
voltsU, P, ADisplays the status and
thresholds for the
system voltage sensors.
removableflash
media
U, P, ADisplays the system’s
virtual flash (vFlash)
and secure digital (SD)
card details.
storageU, P, ASee "Using the Storage
Management Service"
on page 195.
system or
servermodule
U, P, ADisplays a high-level
summary of system
components.
alertactionU, P, ADisplays the warning
and failure threshold
values, as well as
actions configured
when an essential
component detects
a warning or
failure state.
34omreport: Viewing System Status Using the Instrumentation Service
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport
destinations to send the
configured alerts for
platform events.
response for each listed
platform event.
system is configured to
respond to a hung
operating system.
perform the shutdown
action.
omreport: Viewing System Status Using the Instrumentation Service35
Table 3-2. Command Level 1, Level 2, and Level 3 for omreport
(continued)
Command
Level 1
Command Level 2Command
Level 3
User
Privilege
Required
Use
summaryU, P, ADisplays the key facts
for all system
components, including
main system chassis,
software, and storage.
thrmshutdownP, ADisplays how to
perform the shutdown
action, if any, when a
temperature warning or
failure condition is
detected.
versionU, P, ADisplays a summary for
all updatable
components on the
system.
preferenceswebserverU, P, ADisplays the URL
information of the
Server Administrator
Web ser v er.
36omreport: Viewing System Status Using the Instrumentation Service
Help With the omreport Command
Use the omreport -? command to get a list of the available commands
for omreport.
Use omreport
and system commands. The following information on omreport system -? also
applies to get help for the omreport chassis command.
To see a list of valid commands for omreport system, type:
omreport system -? | more
<command level 2> -?
to get help on the level 2 about, chassis,
omreport modularenclosure
Use the omreport modularenclosure command to view details of the
Blade system. Type:
omreport modularenclosure
NOTE: This CLI command is available when Dell OpenManage Server
Administrator is installed on Dell Blade systems.
Server Administrator displays information related to the modular enclosure
and chassis management controller CMC (if available):
NOTE: The output varies depending on the configuration of the system.
Modular Chassis Information
Chassis Information
Attribute: Model
Value: Modular Server Enclosure
Attribute: Lock
Value: true
Attribute: Service Tag
Value: 8RLNB1S
Attribute: Express Service Code
Value: 18955029124
omreport: Viewing System Status Using the Instrumentation Service37
CMC Information
Attribute: Product
Value: Chassis Management Controller (CMC)
Attribute: Description
Value: The system component provides a
complete set of remote management
functions for Dell systems.
Attribute: Version
Value: 3.20
Attribute: IP Address
Value: 101.102.103.104
Attribute: IP Address Source
Value: Dynamic Source
Attribute: IP Address Type
Value: IPv4
Attribute: Remote Connect Interface
Value: Launch CMC Web Interface
omreport about
Use the omreport about command to learn the product name and version
number of the systems management application installed on the system. The
following is an example output from the omreport about command:
Product name : Dell OpenManage Server Administrator
Version:x.x.x
Copyright:Copyright (C) Dell Inc. xxxx-xxxx. All
rights reserved.
Company:Dell Inc.
For details about the environment for Server Administrator, type:
omreport about details=true
38omreport: Viewing System Status Using the Instrumentation Service
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 following output is an
example, and can change depending on the system’s configuration and the
version of Server Administrator installed on the system:
Contains: Instrumentation Service 7.x.x
Storage Management 4.x.x
Sun Java Runtime Environment 1.x.x_xx
Secure Port Server 7.x.x
Server Administrator Core Files 7.x.x
Instrumentation Service Integration Layer
7.x.x
Server Administrator Common Framework 7.x.x
Common Storage Module 4.x.x
Data Engine 7.x.x
Instrumentation Service 7.x.x
omreport chassis or 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 or omreport mainsystem
Ty p e :
omreport chassis
or
omreport mainsystem
omreport: Viewing System Status Using the Instrumentation Service39
Server Administrator displays a general status for the main system chassis or
main system components.
Health
Main System Chassis
SEVERITY: COMPONENT
Ok: Fans
Critical: Intrusion
Ok: Memory
Ok: Power Supplies
Ok: Temperatures
Ok: Voltages
omreport chassis acswitch or omreport mainsystem acswitch
Use the omreport chassis acswitch or omreport mainsystem acswitch
command if the system has redundant AC power lines that are configured in a
failover arrangement. Type:
omreport chassis acswitch
or
omreport mainsystem acswitch
Server Administrator displays the following output:
AC Failover Switch
AC Switch Redundancy
Redundancy Status: Full
Number of devices
required for full
redundancy
Redundancy Mode:
Redundancy
Configuration
AC Power Lines
Status: Ok
Location: AC Power Line 1
:2
: Input Source Line 1, upon
redundancy restoration,
return to Line 1
40omreport: Viewing System Status Using the Instrumentation Service
AC Present: Power Present
Active Source: Active
Status: Ok
Location: AC Power Line 2
AC Present: Power Present
Active Source: Not Active
Server Administrator reports values for the Redundancy Status and
Redundancy Mode fields.
omreport chassis batteries or 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 the
system.
omreport chassis bios or omreport mainsystem bios
Use the omreport chassis bios or 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
the system.
omreport: Viewing System Status Using the Instrumentation Service41
omreport chassis biossetup or omreport mainsystem biossetup
Use the omreport chassis biossetup or omreport mainsystem biossetup
command to view BIOS setup parameters that are normally available only
during system boot. Type:
omreport chassis biossetup
or
omreport mainsystem biossetup
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
To view the BIOS Setup parameters in short form, type:
omreport chassis biossetup display=shortnames
Table 3-3 lists the available BIOS setup parameters on systems prior to
PowerEdge yx2x systems.
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 on Systems Prior to Dell PowerEdge yx2x
System
ParametersDescription
BootsequenceDisplays the device used to boot the system.
NumlockDisplays whether the keypad is used as number keys.
Embedded Video
Controller
Boot ModeDisplays whether the boot mode is configured to BIOS or
Processor C1-EDisplays the Processor C1-E status.
CPU Execute DisableDisplays whether the Execute Disable (XD) option is
Processor C State
Control
Processor CMPDisplays the number of cores enabled per processor.
Displays whether the Embedded Video Controller option is
enabled or disabled.
Unified Extensible Firmware Interface (UEFI.)
enabled or disabled.
Displays whether the Processor C State Control option is
enabled or disabled.
42omreport: Viewing System Status Using the Instrumentation Service
Table 3-3. BIOS Setup Parameters on Systems Prior to Dell PowerEdge yx2x
(continued)
System
ParametersDescription
User accessible USB
Ports
CPU Virtualization
Te ch n ol o gy
AC Power Recovery
Mode
Embedded SATA
Controller
SATA Port 0Displays the state of SATA port 0.
SATA Port 1Displays the state of SATA port 1.
Dual NIC (1/2)Displays whether NIC 1 and NIC 2 with PXE/iSCSI is
Dual NIC (3/4)Displays whether NIC 3 and NIC 4 with PXE/iSCSI is
NIC 1 Displays whether the first NIC is enabled (with or without
NIC 2Displays whether the second NIC is enabled (with or
NIC 3Displays whether the third NIC is enabled (with or without
NIC 4Displays whether the fourth NIC is enabled (with or
Trusted Cryptographic
Module (TCM)
Tru s te d Pl atf or m
Module (TPM)
Security
Internal USB Port
(number)
Operating System
Wat chd og T i me r
Displays whether the user-accessible USB port is enabled or
disabled.
Displays the additional hardware capabilities provided by
Virtualization Technology.
Displays the system state when input power is restored after
an outage.
Displays whether the embedded SATA controller is set to
ATA mode, RAID mode, or is disabled.
enabled or disabled.
enabled or disabled.
PXE/iSCSI) or disabled during system boot.
without PXE/iSCSI) or disabled during system boot.
PXE/iSCSI) or disabled during system boot.
without PXE/iSCSI) or disabled during system boot.
Displays whether TCM is on or off.
Displays whether TPM is off, on with pre-boot
measurements, or on without pre-boot measurements.
Displays whether the internal USB is enabled or disabled.
NOTE: Server Administrator may not display the USB
sequence number if there is only one USB port on the system.
Displays whether the operating system watchdog timer is
enabled or disabled.
omreport: Viewing System Status Using the Instrumentation Service43
Table 3-3. BIOS Setup Parameters on Systems Prior to Dell PowerEdge yx2x
(continued)
System
ParametersDescription
HT AssistDisplays the status of the probe filter chipset option.
Internal SD CardDisplays whether the internal SD card is enabled or
disabled.
BezelDisplays whether the bezel removal intrusion check during
system reboot is enabled or disabled.
Console RedirectionDisplays whether the BIOS screen is redirected over a
particular serial port or if it is turned off.
DisketteDisplays whether the diskette is disabled, auto enabled, or
read-only.
Demand Based Power
Management (DBS)
Embedded Hypervisor Displays whether the embedded hypervisor is enabled or
IDEDisplays whether the drive is enabled or disabled.
IDE Primary Drive 0Displays whether the device is automatically detected and
IDE Primary Drive 1Displays whether the device is automatically detected and
IntrusionDisplays whether the intrusion check is enabled or disabled
MouseDisplays whether the mouse is enabled or disabled.
Optical Drive
Controller
Parallel port addressDisplays whether the address is located on LPT1, LPT2, and
Parallel port modeDisplays the setting associated with the parallel port.
Primary SCSIDisplays whether the device is on or off.
RAID on motherboard Displays whether RAID-on-motherboard is detected as a
Displays whether DBS is enabled or disabled on the system.
disabled.
enabled or if the device is disabled.
enabled or if the device is disabled.
during system boot.
Displays whether the optical drive controller is enabled or
disabled.
LPT3, or if it is disabled.
RAID device, a SCSI device, or if the device is disabled
during system boot.
44omreport: Viewing System Status Using the Instrumentation Service
Table 3-3. BIOS Setup Parameters on Systems Prior to Dell PowerEdge yx2x
(continued)
System
ParametersDescription
RAID Channel ADisplays whether RAID-on-motherboard Channel A is
detected as a RAID device or a SCSI device.
RAID Channel BDisplays whether RAID-on-motherboard Channel B is
detected as a RAID device or a SCSI device.
SATA
Serial Port 1Displays whether serial port 1 is mapped to a COM port, a
COM port 1, a COM port 3, a COM1 BMC, a BMC Serial,
a BMC NIC, a BMC RAC, or is disabled.
Serial Port 2Displays whether serial port 2 is mapped to a COM port, a
COM port 2, a COM port 4, or is disabled.
SpeakerDisplays whether the speaker is on or off.
USB or USBBDisplays whether the USB port is enabled or disabled.
Secondary SCSIDisplays whether the device is enabled or disabled.
Serial Communications Displays whether COM port 1 and COM port 2 are off or on
with or without console redirection.
Console Redirection
After Boot
External Serial
Connector
Console Redirection
Failsafe Baud Rate
Serial Address SelectDisplays port address for the serial devices.
Displays whether console redirection after system reboot is
enabled or disabled.
Displays whether the external serial connector is mapped to
Serial Device 1, Serial Device 2, or a Remote Access Device.
Displays the setting for console redirection failsafe baud
rate.
To view all available boot devices, alias names, and boot order sequences,
type:
omreport chassis biossetup attribute=bootorder
NOTE: In Linux systems, user or user groups upgraded to administrator or
administrator groups cannot view the boot order sequence.
Table 3-4 lists the available groups of the BIOS setup parameters on
PowerEdge yx2x systems.
omreport: Viewing System Status Using the Instrumentation Service45
NOTE: Based on the hardware configuration, the attributes may vary in a specific
group.
Table 3-4. BIOS Setup Groups on PowerEdge yx2x Systems
GroupDescription
BIOS Boot SettingsControls the system boot settings when bootmode is set to
bios.
Boot SettingsControls the system boot settings when bootmode is set to
bios.
Embedded Server
Management
Integrated DevicesControls the devices integrated on the system board.
Memory SettingsControls the system memory settings.
Miscellaneous Settings Controls some miscellaneous system settings.
One-Time BootSupports one-time boot to a specified device.
Processor Settings Controls the processor(s) settings of the system.
SATA SettingsControl the embedded SATA ports settings.
Serial Communication Controls the Serial Communication options.
Slot DisablementControls the system slots that are present on the system.
System InformationDisplays the information that uniquely identifies the
System Profile Settings Controls the power management settings.
System SecurityControls the security features of the system.
UEFI Boot SettingsControls the system boot settings when boot mode is set to
Sets up the Embedded Server Management options.
system.
uefi.
omreport chassis currents or omreport mainsystem currents
This command is no longer available through Server Administrator.
46omreport: Viewing System Status Using the Instrumentation Service
omreport chassis removableflashmedia or omreport mainsystem
removableflashmedia
Use the omreport chassis removableflashmedia or omreport mainsystem
removableflashmedia to view the removable flash media details on the
system along with its health status. Type:
omreport chassis removableflashmedia
or
omreport mainsystem removableflashmedia
Server Administrator displays a summary of the system’s removable flash
media information.
NOTE: If the vFlash or SD card size is less than 1 GB, the size is displayed in MB.
Depending on the configuration of the system, you may notice the following
output:
Removable Flash Media Information
Health : Critical
Internal Dual SD Module Redundancy:
Attribute
Value
Internal SD Modules Status
Status
Connector Name
State
Storage Size
omreport: Viewing System Status Using the Instrumentation Service47
: Redundancy
: Lost
: OK
: System Board SD Status 1
: Present
: 512 MB
Critical
Status
: OK
Connector Name
State
Storage Size
VFlash Media Details
Connector Name
Type
State
Available Size
Storage Size
: System Board SD Status 2
: Present
: 512 MB
: System Board SD Status 1
: vFlash SD Card
: Present
: 472 MB
: 512 MB
omreport chassis fans or 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 are present on the system. If you specify the index, Server
Administrator displays a summary for a specific fan probe.
omreport chassis firmware or omreport mainsystem firmware
Use the omreport chassis firmware or omreport mainsystem firmware
command to view current firmware properties. When you type:
omreport chassis firmware
or
omreport mainsystem firmware
48omreport: Viewing System Status Using the Instrumentation Service
Server Administrator displays a summary of the system’s firmware properties.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
NOTE: If iDRAC is installed, Server Administrator displays the Life Cycle Controller
(LCC) version. If BMC is installed, Server Administrator displays the Unified Server
Configurator (USC) version.
omreport chassis frontpanel or 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 the system, check 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 the system, check whether the NMI button
is enabled or not. Use the NMI button to troubleshoot software and device
errors when using certain operating systems.
The Front Panel LCD Security Access displays if the front panel encryption
access information is set to View, Modify, or Disable.
The Front Panel LCD Information displays information such as service tag,
remote indication status, and so on.
omreport chassis fru or 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 the 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: Viewing System Status Using the Instrumentation Service49
omreport chassis hwperformance or 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 the system’s hardware
performance degradation information.
NOTE: This command is applicable only to selected Dell yx0x systems that support
PMBus.
Depending on the system’s configuration, you may notice the following
output:
Hardware Performance
Index
Probe Name
Status
Cause
: 0
: System Board Power Optimized
: Normal
: [N/A]
omreport chassis info or omreport mainsystem info
Use the omreport chassis info or omreport mainsystem info command to see
a summary of installed component versions. Type:
omreport chassis info index=n
or
omreport mainsystem info index=n
50omreport: Viewing System Status Using the Instrumentation Service
The index parameter specifies a chassis number and is optional. If you do not
specify the index, Server Administrator displays summary chassis information
for each chassis. If you specify the index, Server Administrator displays
summary information for a specific chassis.
NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC
is installed, Server Administrator displays the USC version.
Depending on the system’s configuration, you may notice the following
output:
Index: 0
Chassis Name: Main System Chassis
Host Name: WIN-27C02UQFV6L
iDRAC7 Version: 1.00
Chassis Model: PowerEdge R720
Chassis Lock: Present
Chassis Service Tag: 7654321
Express Service Code: 15608862073
Chassis Asset Tag: c
omreport chassis intrusion
Use the omreport chassis intrusion command to find out whether the cover
of the 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
omreport: Viewing System Status Using the Instrumentation Service51
A message that resembles the following is displayed:
Intrusion Information
Health
Index
Status
Probe Name
State
: Ok
: 0
: OK
: Intrusion
: Chassis is closed
omreport chassis leds or omreport mainsystem leds
Use the omreport chassis leds or omreport mainsystem leds command to find
out whether clear hard drive fault is supported and what severity level lights
up the LED. Type:
omreport chassis leds index=n
or
omreport mainsystem leds index=n
The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of LED information for chassis 0. If you
specify the index, Server Administrator displays a summary for a specific
chassis.
The following is an example output:
Main System Chassis
Flash chassis identify LED state
Flash chassis identify LED timeout
value
52omreport: Viewing System Status Using the Instrumentation Service
: Off
: 300
omreport chassis memory or omreport mainsystem memory
Use the omreport chassis memory or omreport mainsystem memory to view
details for each memory module slot in the system. If the system supports
redundant memory, this command also displays the status, state, and type of
memory redundancy implemented on the system. Type:
omreport chassis memory index=n
or
omreport mainsystem index=n
The index parameter is optional. If you do not specify the index, Server
Administrator displays information for all memory modules on the system.
If you specify the index, Server Administrator displays a summary for a
specific memory module.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
Output for an occupied memory slot may resemble the following:
Use the omreport chassis nics or omreport mainsystem nics command to
view NIC and Team interface details. On XenServer, the command displays
all the installed NICs, regardless of driver installation.
NOTE: The order in which devices are detected is not guaranteed to match the
physical port ordering of the device.
To view NIC properties, type:
omreport chassis nics index=n
or
omreport mainsystem nics index=n
54omreport: Viewing System Status Using the Instrumentation Service
The index parameter is optional. If you do not specify the index, Server
Administrator displays properties of all NICs on the system and the values for
the following fields: Index (NIC card number), Interface Name, Ven do r,
Description, Connection Status, and Slot.
If you specify the index, Server Administrator displays properties for a specific
NIC and the values for the following fields: Physical Interface, Interface
NOTE: The Fibre Channel over Ethernet (FCoE) and iSCSI over Ethernet (iSoE)
features of Converged Network Adapter (CNA) cards are not supported on VMware
ESX and VMware ESXi systems.
To view Team interface properties, type:
omreport chassis nics config=team index=n
or
omreport mainsystem nics config=team index=n
NOTE: This command is applicable only if Team interface is configured in the
system. Team interface is configured using NIC vendor tools, such as Broadcom.
The index parameter is optional. If you do not specify the index, Server
Administrator displays details of all the Team interfaces on the system and
the values for the following fields: Index (NIC card number), Interface Name, Ve nd or, Description, and Redundancy Status.
If you specify the index, Server Administrator displays the Team interface
details for the specific NIC and the values for the following fields: Team
Interface, Interface, IPv4 Addresses, IPv6 Addresses, Team Int erf ace Re ce ive Statistics, Team Interface Transmit Statistics, Interface Receive Statistics,
and Interface Transmit Statistics.
omreport chassis ports or omreport mainsystem ports
Use the omreport chassis ports or omreport mainsystem ports command to
view properties of the system’s parallel and serial ports.
Server Administrator displays values for the following fields: Port Type,
External Name, Base I/O Address, IRQ Level, Connector Type, and
Maximum Speed.
omreport: Viewing System Status Using the Instrumentation Service55
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.
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 or omreport mainsystem processors
Use the omreport chassis processors or omreport mainsystem processors
command to view properties of the system’s processors.
Server Administrator displays values for the following fields: Index, Status, Connector Name, Processor Brand, Processor Version, Current Speed, State,
and Core Count.
Index is the processor number.
Status is the current status of the processor.
Connector Name is the name or number of the device that occupies the
processor slot in the system.
Processor Brand is the type of processor made by a manufacturer such as
Intel Itanium, Intel Pentium III, Intel Xeon, or AMD Opteron.
Processor Version is the model and stepping number of the processor.
56omreport: Viewing System Status Using the Instrumentation Service
Current Speed is the actual processor speed in MegaHertz at system boot
time.
State is whether the processor slot is enabled or disabled.
Core Count is the number of processors integrated into one chip.
Capabilities and Cache Properties of a Specific Processor
To view the cache properties of a processor on a given connector, type:
omreport chassis processors index=n
or
omreport mainsystem processors index=n
The index parameter is optional. If you do not specify the index, Server
Administrator displays properties for all processors. If you specify the index,
Server Administrator displays properties for a specific processor.
The following fields are defined for the capabilities present on a particular
microprocessor:
For Intel Processor
•64-bit Support
•Hyperthreading (HT)
•Virtualization Technology (VT)
•Demand-Based Switching (DBS)
•Execute Disable (XD)
•Turbo Mode
For AMD Processor
•64-bit Support
•AMD-V
•AMD PowerNow!
•No Execute (NX)
omreport: Viewing System Status Using the Instrumentation Service57
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
NOTE: Due to the limitations of certain operating systems (for example, VMware
ESXi), certain features are not available with this release of OpenManage Server
Administrator.
Fields Reported for Each Cache on a Particular Processor
The following fields are displayed for each cache on a particular processor:
Status reports whether a specific cache on the processor is enabled or
disabled.
Level refers to a primary or secondary cache. Primary-level cache is a memory
bank built into the processor. Secondary-level cache is a staging area that
feeds the primary cache. A secondary-level cache is built into the processor or
resides in a memory chipset outside the processor. The internal processor
cache is referred to as a Level 1 (or L1). L2 cache is the external cache in a
system with an Intel Pentium processor, and it is the second level of cache
that is accessed. The names L1 and L2 are not indicative of where the cache is
physically located (internal or external), but describe which cache is accessed
first (L1, therefore internal).
Speed refers to the rate at which the cache can forward data from the main
memory to the processor.
Max Size is the maximum amount of memory that the cache can hold in
kilobytes.
Installed Size is the actual size of the cache.
Ty p e indicates whether the cache is primary or secondary.
Location is the location of the cache on the processor or on a chipset outside
the processor.
58omreport: Viewing System Status Using the Instrumentation Service
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 store at any
location in the cache.
•A
n
-way set-associative cache directly maps n specific lines of memory to
the same
n
lines of cache. For example, line 0 of any page in memory is
stored in line 0 of cache memory.
Cache Device Supported Type is the type of static random access memory
(SRAM) that the device can support.
Cache Device Current Type is the type of the currently installed SRAM that
the cache is supporting.
External Socket Name Silk Screen Name is the name printed on the system
board next to the socket.
Error Correction Type identifies the type of error checking and correction
(ECC) that this memory can perform. Examples are correctable ECC or
uncorrectable ECC.
This report shows cache information for each cache present on the
microprocessor.
omreport: Viewing System Status Using the Instrumentation Service59
omreport chassis pwrmanagement or omreport mainsystem
pwrmanagement
Use the omreport chassis pwrmanagement or omreport mainsystem
pwrmanagement command to view the power budget cap and power
management profiles of the system. The values display either in Watts or
BTU/Hr based on the configuration. Type:
omreport chassis pwrmanagement
or
omreport mainsystem pwrmanagement
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
NOTE: The omreport chassis pwrmanagement or omreport mainsystem
pwrmanagement command is applicable from PowerEdge yx1x system onwards
that support Power Management Bus (PMBus) and that have hot-swappable power
supplies and not systems that have a fixed, non-redundant power supply installed.
For each power management profile in the system, values display for the
following fields:
Maximum Performance, Active Power Controller, OS Control, and Custom.
Custom attributes are:
CPU Power and Performance Management, Memory Power and
Performance Management, and Fan Power and Performance Management.
60omreport: Viewing System Status Using the Instrumentation Service
The following is an example output:
Power Inventory and Budget
Power Inventory
System Idle Power
System Maximum Potential Power
: :0 W
0 W
Power Budget
Enable Power Cap
Attribute
Values
Attribute
Values
NOTE: Power budget requires license to report the details. If the appropriate
license is not installed or has expired, the system does not display the power budget
details. For more information, see The Dell Licensing Management Guide at
support.dell.com/manuals.
:
Enabled
:
Power Cap
:
400 W (56%)
:
omreport chassis pwrmonitoring or omreport mainsystem
pwrmonitoring
Use the omreport chassis pwrmonitoring or omreport mainsystem
pwrmonitoring command to view the properties of the system’s power
consumption. The values display either in Watts or BTU/Hr based on the
configuration. Type:
omreport chassis pwrmonitoring
or
omreport mainsystem pwrmonitoring
For each power monitoring profile in the system, values display for the
following fields:
•Power Consumption Status
•Probe Name
•Reading
•Warning Threshold
omreport: Viewing System Status Using the Instrumentation Service61
•Failure Threshold
•Amperage: Location and Reading
•Power Tracking Statistics
•Energy Consumption
•Measurement Start Time
•Measurement Finish Time
•Reading
•System Peak Power
•System Peak Amperage
NOTE: The omreport chassis pwrmonitoring or omreport mainsystem
pwrmonitoring command is applicable from PowerEdge yx0x system onwards that
support PMBus and that have hot-swappable power supplies and not systems that
have a fixed, non-redundant power supply installed.
NOTE: Power monitoring requires license to report the details. If the appropriate
license is not installed or has expired, the system does not display the power
consumption details of the system. For more information, see The Dell Licensing Management Guide at support.dell.com/manuals.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
Table 3-5. omreport chassis pwrmonitoring or omreport mainsystem pwrmonitoring
name=value pairDescription
config=statsReports power statistics in Watts.
62omreport: Viewing System Status Using the Instrumentation Service
The following is an example output:
Power Consumption Information
Power Consumption
Index
Status
Probe Name
Reading
Warning Threshold
Failure Threshold
Amperage
PS1 Current 1
Power Headroom
System Instantaneous
Headroom
System Peak Headroom
: 1
: Ok
: System Board Pwr
Consumption
: 539W
: 994W
: 1400 W
: 1.2 A
: 300 W
: 340
omreport: Viewing System Status Using the Instrumentation Service63
Power Tracking Statistics
Statistic
Measurement Start Time
Measurement Finish
: Energy consumption
: Thu May 28 11:03:20 2011
: Fri May 28 11:05:46 2011
Time
Reading
Statistics
Measurement Start Time
Peak Time
Peak Reading
Statistics
Measured Since
Read Time
Peak Reading
NOTE: Power Management features are only available for PowerEdge systems
that have hot-swappable power supplies and not systems that have a fixed, nonredundant power supply installed.
: 5.9 KWH
: System Peak Power
: Mon May 18 16:03:20 2011
: Wed May 27 00:23:46 2011
: 630 W
: System Peak Amperage
: Mon May 18 16:03:20 2011
: Tue May 19 04:06:32 2011
: 2.5 A
64omreport: Viewing System Status Using the Instrumentation Service
omreport chassis pwrsupplies or omreport mainsystem pwrsupplies
Use the omreport chassis pwrsupplies or omreport mainsystem pwrsupplies
command to view properties of the system’s power supplies. Type:
omreport chassis pwrsupplies
or
omreport mainsystem pwrsupplies
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
For each power supply profile in the system, values display for the following
fields:
•Status
•Location
•Type
•Rated Input Wattage (in Watts)
•Maximum Output Wattage
•Online Status
•Power Monitoring Capable
omreport chassis remoteaccess or omreport mainsystem remoteaccess
Use the omreport chassis remoteaccess or omreport mainsystem
remoteaccess command to view general information on baseboard
management controller or integrated Dell remote access controller
(BMC/iDRAC) and
Ty p e :
omreport chassis remoteaccess
remote access controllerif DRAC is installed.
or
omreport mainsystem remoteaccess
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
omreport: Viewing System Status Using the Instrumentation Service65
The output of the omreport chassis remoteaccess or omreport mainsystem
remoteaccess command lists each of the valid parameters. Table 3-6 lists the
available settings.
Table 3-6. Valid parameters of omreport chassis remoteaccess or omreport
mainsystem remoteaccess
name=value pairDescription
config=additionalReports the current state of IPv4 and IPv6 addresses on
iDRAC.
config=advsolReports advanced BMC/iDRAC or remote access information
on a serial over local area network (LAN) connection.
config=nicReports BMC/iDRAC or remote access information for the
LAN.
config=serialReports 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
config=userReports information on BMC/iDRAC or remote access users.
Reports terminal mode settings for the serial port.
omreport chassis slots or omreport mainsystem slots
Use the omreport chassis slots or omreport mainsystem slots command to
view properties of the system’s slots.
Ty p e :
omreport chassis slots index=n
or
omreport mainsystem slots index=n
The index parameter is optional. If you do not specify the index, Server
Administrator displays properties for all of the slots in the system. If you
specify the index, Server Administrator displays properties for a specific slot.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
66omreport: Viewing System Status Using the Instrumentation Service
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 the 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, iDRAC Enterprise, or HBA.
Data Bus Width is the width, in bits, of the information pathway between
the components of a system. The range of the data bus width is from 16 to 64
bits.
omreport chassis temps or omreport mainsystem temps
Use the omreport chassis temps or omreport mainsystem temps command to
view properties of the system’s temperature probes. Type:
omreport chassis temps index=n
or
omreport mainsystem temps index=n
The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of status, readings, and thresholds set for
any temperature probes that are present on the system. If you specify the
index, Server Administrator displays a summary for a specific
temperature probe.
omreport chassis volts or omreport mainsystem volts
Use the omreport chassis volts or omreport mainsystem volts command to
view properties of the system’s voltage probes. Type:
omreport chassis volts index=n
or
omreport mainsystem volts index=n
The index parameter is optional. If you do not specify the index, Server
Administrator displays a summary of status, readings, and thresholds set for
any voltage probes that are present on the system. If you specify the index,
Server Administrator displays a summary for a specific voltage probe.
omreport: Viewing System Status Using the Instrumentation Service67
omreport system Commands or omreport
servermodule Commands
Use the omreport system or omreport servermodule command to view logs,
threshold values, cost of ownership information, and information about how
shutdown actions and recovery actions are configured.
omreport system or omreport servermodule
Use the omreport system or omreport servermodule command to see a
general status of the components of the system. When you specify a level 3
command, such as omreport system shutdown or omreport servermodule shutdown, you 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 the system has both a main system chassis or 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
68omreport: Viewing System Status Using the Instrumentation Service
Commands for Viewing Logs
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), you must clear the log
and resolve the issue. To clear the log, type: omconfig system alertlog action=clear or omconfig system cmdlog action=clear . If you
need to retain the log information for future reference, save a copy of the log before
clearing. See "Commands for Clearing Logs" on page 161 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
omreport: Viewing System Status Using the Instrumentation Service69
Overall Health Status of the ESM Log
When you run the omreport system esmlog or omreport servermodule
esmlog command, the ESM log is displayed. 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 is displayed:
Health: Non-Critical
If a caution is displayed, resolve all warning and critical severity conditions,
and then clear the log.
omreport system alertaction or 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 the system components. Alert actions
determine how Server Administrator responds when a component has a
warning or failure event.
The omreport system alertaction or omreport servermodule alertaction
command is useful for viewing which alert actions have been specified for
components. To set an alert action for a component, use the omconfig system alertaction or omconfig servermodule alertaction command. For more
information, see "omconfig: Managing Components Using the
Instrumentation Service" on page 89.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
NOTE: Due to the limitations of certain operating systems (for example, VMware
ESXi), certain features are not available with this release of OpenManage Server
Administrator.
Components and Events Having View Alert Actions
View alert action properties for the following components and events, if the
components or events are present on the system:
•Battery Warning
•Battery Failure
•Chassis Intrusion
70omreport: Viewing System Status Using the Instrumentation Service
•Current Probe Warning
•Current Probe Failure
•Fan Warning
•Fan Failure
•Memory Pre-failure
•Memory Failure
•System Power Probe Warning
•System Power Probe Detects a Failure
•System Peak Power
•Power Supply Warning
•Power Supply Failure
•Degraded Redundancy
•Lost Redundancy
•Temperature Warning
•Temperature Failure
•Voltage Warning
•Voltage Failure
•Processor Warning
•Processor Failure
•Hardware Log Warning
•Hardware Log Full
•Watchdog Asr
•Storage System Warning
•Storage System Failure
•Storage Controller Warning
•Storage Controller Failure
•Physical Disk Warning
•Physical Disk Failure
•Virtual Disk Warning
•Virtual Disk Failure
omreport: Viewing System Status Using the Instrumentation Service71
•Enclosure Warning
•Enclosure Failure
•Storage Controller Battery Warning
•Storage Controller Battery Failure
•Removable Flash Media Present
•Removable Flash Media Removed
•Removable Flash Media Failure
NOTE: Storage Controller Battery Warning and Storage Controller Battery Failure
events are not available on Blade systems.
NOTE: System Power Probe Warning is not applicable to Blade systems.
omreport system assetinfo or omreport servermodule assetinfo
Use the omreport system assetinfo or omreport servermodule assetinfo
command to see cost of ownership data for the system, such as acquisition,
depreciation, and warranty information. To set any of these fields, use the
omconfig system assetinfo or omconfig servermodule assetinfo command.
For more information, see "omconfig system or servermodule assetinfo:
Editing Cost of Ownership Values" on page 175.
omreport system events or omreport servermodule events
Use the omreport system events or omreport servermodule events command
to view the currently enabled or disabled SNMP traps. This command
displays a summary of each component in the system for which events are
generated. For each component, the report shows which severities are set to
report and which severities are set not to report. Type:
omreport system events
or
omreport servermodule events
72omreport: Viewing System Status Using the Instrumentation Service
The following is an example output for a few components:
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, Warning, and Critical
--------------------Removable Flash Media
--------------------Settings
Enable: Informational, Warning and Critical
Disable: None
The full report lists the settings for all components in the system for which
events are generated.
To view the status for components of a specific type, use the omreport system events type=<component name> or omreport servermodule event type=
<
component name> command. This command displays a summary of each
component in the system for which events are generated. Table 3-7 lists the
events displayed for various component types.
NOTE: Due to the limitations of certain operating systems (for example, VMware
ESXi), certain features are not available with this release of OpenManage Server
Administrator.
omreport: Viewing System Status Using the Instrumentation Service73
Table 3-7. System Events by Component Type
name=value pairDescription
type=accordsReports events for AC power cords
type=batteryReports events for batteries
type=fanenclosuresReports events for fan enclosures
type=fans Reports events for fans
type=intrusionReports events for chassis intrusion
type=log Reports events for logs
type=memoryReports events for memory
type=powersuppliesReports events for power supplies
type=redundancyReports events for redundancy
type=systempowerReports events for system power
type=tempsReports events for temperatures
type=removableflashmediaReports events for removable flash media
type=voltsReports events for voltages
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:
Current SNMP Trap Configuration
-------
System
-------
Settings
Enable: Informational, Warning, and Critical
Disable: None
74omreport: Viewing System Status Using the Instrumentation Service
----------Fans Group
---------Settings
Enable: Informational, Warning, and Critical
Disable: None
----------Individual Objects
----------System Board Fan1 RPM Settings
Index:0
Enable: Informational, Warning, and Critical
Disable: None
System Board Fan2 RPM Settings
Index:1
Enable: Informational, Warning, and Critical
Disable: None
omreport system operatingsystem or omreport servermodule
operatingsystem
Use the omreport system operatingsystem or omreport servermodule
operatingsystem command to display information about the operating
system.
omreport system pedestinations or omreport servermodule
pedestinations
Use the omreport system pedestinations or omreport servermodule
pedestinations command to view destinations where alerts are sent for
platform events. Depending on the number of destinations displayed,
configure a separate IP address for each destination address.
omreport: Viewing System Status Using the Instrumentation Service75
Ty p e :
omreport system pedestinations
or
omreport servermodule pedestinations
The output of the omreport system pedestinations or omreport
servermodule pedestinations command lists each of the valid parameters.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
NOTE: The actual number of destinations you can configure on the system may
differ. Table 3-8 lists the available settings.
Table 3-8. Settings for the omreport system pedestinations or omreport servermodule
pedestinations
OutputAttributesDescription
Destination List
Destination Number:
Destination1
Destination Number:
Destination 2
Destination Number:
Destination 3
destination 1: Displays the first
destination.
Example:
101.102.103.104: IPv4 address of the
first destination.
destination 2: Displays the second
destination.
Example:
110.120.130.140: IPv4 address of the
second destination.
destination 3: Displays the third
destination.
Example:
201:202:203:204: IPv4 address of the
third destination.
76omreport: Viewing System Status Using the Instrumentation Service
Table 3-8. Settings for the omreport system pedestinations or omreport servermodule
pedestinations
OutputAttributesDescription
Destination
Configuration
Settings
(continued)
Destination Number:
Destination 4
Destination Number:
Destination 5
Destination Number:
Destination 6
Destination Number:
Destination 7
Destination Number:
Destination 8
attribute=
communitystring
destination 4: Displays the fourth
destination.
Example:
210.211.212.213: IPv4 address of the
fourth destination.
destination 5: Displays the fifth
destination.
Example:
2001:0db8:85a3:0000:0000:8a2e:0370:7
334: IPv6 address of the fifth
destination.
destination 6: Displays the sixth
destination.
Example:
2001:0db8:85a3:0000:0000:8a2e:0370:7
334: IPv6 address of the sixth
destination.
destination 7: Displays the seventh
destination.
Example:
210.211.212.213: IPv4 address of the
seventh destination.
destination 8: Displays the eighth
destination.
210.211.212.213: IPv4 address of the
eighth destination.
communitystring: Displays the text
string that acts as a password and is used
to authenticate SNMP messages sent
between the BMC and the destination
management station.
omreport: Viewing System Status Using the Instrumentation Service77
omreport system platformevents or omreport servermodule
platformevents
Use the omreport system platformevents or omreport servermodule
platformevents command to view how the system responds for each listed
platform event.
NOTE: To maintain consistency across the commands, the output format of this
command has changed. Change the user scripts as applicable.
omreport system recovery or 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. Also view the number of seconds that must elapse before an operating
system is considered hung.
omreport system shutdown or omreport servermodule shutdown
Use the omreport system shutdown or omreport servermodule shutdown
command to view any pending shutdown actions for the system. If properties
for shutdown are configured, executing this command displays these
properties.
NOTE: Due to the limitations of certain operating systems (for example, VMware
ESXi), certain features are not available with this release of OpenManage Server
Administrator.
omreport system summary or 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 the system.
Ty p e :
omreport system summary
or
omreport servermodule summary
NOTE: If the vFlash or SD card size is less than 1 GB, the size is displayed in MB.
NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC
is installed, Server Administrator displays the USC version.
78omreport: Viewing System Status Using the Instrumentation Service
The output that is displayed in the CLI window depends on the systems
management software, operating system, and hardware components and
options installed on the system. The following partial command results are
unique and may not resemble the hardware and software configuration of the
system:
System Summary
----------------Software Profile
----------------Systems Management
Name: Dell OpenManage Server
Administrator
Version: x.x.x
Description: Systems Management Software
Contains: Common Storage Module 4.x.x
: Data Engine 7.x.x
: Hardware Application Programming
Interface 7.x.x
: Instrumentation Service 7.x.x
: Instrumentation Service
Integration Layer 7.0.0
: OpenManage Inventory Collector
7.x.x
: Remote Access Controller Data
Populator 7.x.x
: Remote Access Controller Managed
Node 7.x.x
: Secure Port Server 7.x.x
: Server Administrator Common
Framework 7.x.x
omreport: Viewing System Status Using the Instrumentation Service79
: Server Administrator Core files
7.x.x
: Storage Management 4.x.x
: Sun Java Runtime Environment
1.x.x
Operating System
Name: Microsoft Windows Server 2008
R2, Enterprise x64 Edition
Version: Version 6.1 <Build 7600> <x64>
Server Full Installation
System Time: Fri May 20 18:02:52 2XXX
System Bootup Time : Wed May 18 18:37:58 2XXX
---------System
-------------System
Host Name: WIN-27C02UQFV6L
System Location: Please set the value
Life Cycle
Controller
: [N/A]
-----------Main System
Chassis
----------Chassis
Information
Chassis Model: PowerEdge R720
Chassis Service
Tag
80omreport: Viewing System Status Using the Instrumentation Service
: 7654321
Express Service
: 15608862073
Code
Chassis Lock: Present
Chassis Asset Tag : c
Remote Access
Information
Remote Access
: iDRAC7 Express
Device
vFlash Media: Absent
Processor 1
Processor Brand: Genuine Intel (R) CPU @ 1.60GHz
Processor Version : Model 45 Stepping 2
Voltage: 1200 W
Memory
Total Installed
: 2048 MB
Capacity
Memory Available
: 2048 MB
to the OS
Total Maximum
: 786432 MB
Capacity
Memory Array Count : 1
Memory Array 1
Location : System Board or Motherboard
Use: System Memory
Installed Capacity : 2048 MB
omreport: Viewing System Status Using the Instrumentation Service81
Maximum Capacity: 786432 MB
Slots Available: 24
Slots Used: 1
Slot PCI1
Adapter: [Not Occupied]
Type: PCI E Gen 3 X16
Data Bus Width: 8x or x8
Speed: [Not obtained, see card
documentation]
Slot Length: Long
Voltage Supply: 3.3 Volts
Slot PCI2
Adapter: [Not Occupied]
Type: PCI E Gen 3 X16
Data Bus Width: 8x or x8
Speed: [Not obtained, see card
documentation]
Slot Length: Long
Voltage Supply: 3.3 Volts
BIOS Information
Manufacturer: Dell Inc.
Version: 0.3.5
Release Date: 05/16/2011
82omreport: Viewing System Status Using the Instrumentation Service
Firmware
Information
Name: iDRAC7
Version: 1.00
--------------Network Data
--------------Network Interface
0
IP Address: 10.94.22.111
Subnet Mask: 255.255.254.0
Default Gateway: 10.94.22.1
MAC Address: 14-FE-B5-FF-AF-D0
Network Interface
1
IP Address: [No Value]
MAC Address: 14-FE-B5-FF-AF-D1
Network Interface
2
IP Address: [No Value]
MAC Address: 14-FE-B5-FF-AF-D2
omreport: Viewing System Status Using the Instrumentation Service83
The system summary hardware information includes data values for installed
components of the following types present in the system:
System Attributes
•Host Name
•System Location
•Life Cycle Controller
Main System Chassis or Main System
Chassis
•Chassis Model
•Chassis Service Tag
•Express Service Code
•Chassis Lock
•Chassis Asset Tag
Remote Access Information
•Remote Access Device
•vFlash Media
•vFlash Media Size
Processor
The following are listed for each processor in the system:
•Processor Brand
•Processor Family
•Processor Version
84omreport: Viewing System Status Using the Instrumentation Service
•Current Speed
•Maximum Speed
•External Clock Speed
•Voltage
Memory
•Total Installed Capacity
•Memory Available to the Operating System
•Total Maximum Capacity
•Memory Array Count
Memory Array
The following details are listed for each memory board or module in the
system (for example, the system board or the memory module in a given
slot number):
•Location
•Use
•Installed Capacity
•Maximum Capacity
•Slots Available
•Slots Used
•ECC Type
BIOS
•Manufacturer
•BIOS Version
•Release Date
Firmware
•Name
•Version
omreport: Viewing System Status Using the Instrumentation Service85
Network Data
The following details are listed for each NIC and Team interface, if Team
interface is configured in the system:
•IP Address
•Subnet Mask
•Default Gateway
•MAC Address
Storage Enclosures
The following details are listed for each storage enclosure attached to the
system:
•Name
•Service Tag
omreport system thrmshutdown or 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 is displayed:
omreport system version or 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 the system.
86omreport: Viewing System Status Using the Instrumentation Service
Example Command Output
Ty p e :
omreport system version
or
omreport servermodule version
NOTE: If iDRAC is installed, Server Administrator displays the LCC version. If BMC
is installed, Server Administrator displays the USC version.
The output that is displayed in the CLI window depends on the version of the
BIOS, RAID controllers, and firmware installed on the system. The following
partial command results are unique and may not resemble the results for the
configuration of the system:
Version Report
--------------------Main System Chassis
--------------------Name : BIOS
Version : 0.3.5
Name : iDRAC7
Version : 1.00
--------------------Software
--------------------Name: Microsoft Windows Server 2008 R2,
Enterprise x64 edition
Version: Version 6.1 (Build 7600) (x64)
Server Full Installation
Name : Dell Server Administrator
Version: 7.x.x
omreport: Viewing System Status Using the Instrumentation Service87
-----------------------------------Name: PERC H310 Mini
Version: 20.10.1-0025
omreport preferences Commands
Use the omreport preferences command to view the URL information of the
Server Administrator Web server.
Table 3-9 lists the available attributes.
Table 3-9. Attributes of omreport preferences webserver
name=value pairDescription
attribute=geturlReports the URL information of the Web server.
attribute=getsignalgorithmReports the current key sign algorithm.
88omreport: 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 perform other systems management tasks.
Examples of omconfig capabilities include:
•Administrator privilege to clear command, alert, and hardware logs
•Administrator privilege to configure and execute system shutdown
•Power user and administrator privilege to specify values for warning events
on fans, voltage probes, and temperature probes
•Power user and administrator privilege to set alert actions in case of a
warning or failure event from intrusion, fans, voltage probes, and
temperature probes
For information on using the omconfig command to view and manage cost of
ownership information (assetinfo), see "omconfig system or servermodule
assetinfo: Editing Cost of Ownership Values" on page 175.
Often, you must use the omreport command to get the information required to
execute an omconfig command. For example, to edit the minimum
temperature for a warning event on a temperature probe, you must know the
index of the probe. Use the omreport chassis temps or omreport mainsystem temp command to display a list of probes and their indexes. For more
information on using the omreport command, see "omreport: Viewing System
Status Using the Instrumentation Service" on page 29.
omconfig: Managing Components Using the Instrumentation Service89
Table 4-1. System Availability for the omconfig Command
Command Level 1Command Level 2Applicable to
omconfigservermoduleBlade systems
mainsystemBlade systems
systemRack and Tower systems
chassisRack and Tower systems
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 (CLI).
The symbol |, often called pipe, is the logical exclusive or operator. For
example, enable | disable means you can enable or disable the component or
feature, but you cannot simultaneously enable and disable the component or
feature.
omconfig Command Summary
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
are used with omconfig. User privilege required refers to the type of privilege you
need to run the command, where U=User, P=Power User, and A=
Administrator. Use is a very general statement about the actions that are
performed using omconfig. More information about the syntax and use of the
omconfig command appear later in this section.
NOTE: Although the table lists all possible omconfig commands, the commands
available on the system depend on the system configuration. If you try to get help or
execute a command for a component not installed on the system, Server
Administrator displays a message that the component or feature is not found on
the system.
NOTE: When CSIOR (Collect System Inventory on Restart) is disabled, omconfig
does not allow to configure the BIOS settings.
90omconfig: Managing Components Using the Instrumentation Service
threshold values on ESM3
and PowerEdge x8xx
systems.
storageSee "Using the Storage
Management Service" on
page 195.
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 Service95
Use a command of the form omconfig system <command level 3>-? to get a
list of the parameters you must use to execute a particular omconfig system
command. For example, the following commands produce a list of valid
parameters for omconfig system alertaction and omconfig system shutdown:
omconfig system alertaction -?
omconfig system shutdown -?
In case of the omconfig system alertaction command, you can use various
options to prevent all of the CLI help from scrolling, before you can read it.
To scroll the 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 create 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 Microsoft Windows, Red
Hat Enterprise Linux, or SUSE Linux Enterprise Server operating systems,
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 the system. The
following is an example output of the omconfig about command:
Product
name
Version: 7.x.x
Copyright: Copyright (C) Dell Inc. xxxx-xxxx. All
Company: Dell Inc.
96omconfig: Managing Components Using the Instrumentation Service
: Dell OpenManage Server Administrator
rights reserved.
For more details about the environment for Server Administrator, type:
omconfig about details=true
Server Administrator includes a number of services, each having a version
number of its own. The Contains field reports version numbers for the services
and provides other useful details. The following is an example output of the
omconfig about command. The output may change depending on the
configuration of the system and the version of Server Administrator.
Contains: Broadcom SNMP Agent 10.xx.xx
Common Storage Module 3.x.x
Data Engine 5.x.x
Hardware Application Programming Interface
5.x.x
Instrumentation Service 6.x.x
Instrumentation Service Integration Layer
4.6.3
Secure Port Server 1.x.x
Server Administrator Framework 6.x.x
Agent for Remote Access 1.x.x
Storage Management 3.x.x
Sun Java Runtime Environment 1.x.xx
omconfig: Managing Components Using the Instrumentation Service97
omconfig chassis or omconfig mainsystem
Use the omconfig chassis or omconfig mainsystem command to:
•Set to default or assign specific values for fan, voltage, and temperature
probes
•Configure BIOS behavior during system start up
•Clear memory error counts
•Enable or disable power button control features if system configuration
permits
Use the omconfig chassis -? or omconfig mainsystem -? command to view a
list of all omconfig chassis or omconfig mainsystem commands.
omconfig chassis biossetup or omconfig mainsystem biossetup
Use the omconfig chassis biossetup or omconfig mainsystem biossetup
command to configure system BIOS settings that are normally available only
in the BIOS setup boot time settings of the system.
CAUTION: Changing certain BIOS setup options may disable the system or
require you to reinstall the operating system.
NOTE: Reboot the system for the BIOS setup options to take effect.
NOTE: Not all BIOS setup options are available on every system.
NOTE: Due to the limitations of certain operating systems (for example, VMware
ESXi), certain features are not available with this release of OpenManage Server
Administrator.
NOTE: When CSIOR (Collect System Inventory on Restart) is disabled, you cannot
configure the BIOS settings using omconfig command.
98omconfig: Managing Components Using the Instrumentation Service
Table 4-3 lists the name=value pairs you can use with this command on
systems prior to PowerEdge yx2x systems.
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge
immediate: System returns to previous
state immediately.
timedelay <value>: System is turned
on based on user specified time delay.
enabled: Enables the bezel removal
intrusion check during system boot.
disabled: Disables the bezel removal
intrusion check during system boot.
Instructs the BIOS which device is used
to boot the system, and the order in
which the boot routine checks each
device.
NOTE: On Linux systems, user or user
groups upgraded to administrator or
administrator groups cannot configure
this BIOS setup setting.
attribute=
bootmode
setting=uefi | biosuefi: Enables the system to boot to
operating systems that support Unified
Extensible Firmware Interface (UEFI).
bios: Enables the system to boot to
operating systems that do not support
UEFI.
yx2x
Systems
omconfig: Managing Components Using the Instrumentation Service99
Table 4-3. BIOS Setup Settings on Systems Prior to PowerEdge
(continued)
yx2x
Systems
name=value pair 1
attribute=
attribute=
bootorder
attribute=
hddorder
attribute=cstates setting=enabled |
name=value pair 2
setting=
sequence=aliasname1,
aliasname2,.....
aliasnameN
sequence=aliasname1,
aliasname2,.....
aliasnameN
disabled
Description
Configures the boot sequence according
to the set aliasnames. To view the set
alias names, run the command
omreport chassis
biossetup attribute=
bootorder
.
NOTE: On Linux systems, user or user
groups upgraded to administrator or
administrator groups cannot configure
this BIOS setup setting.
Configures the BIOS setup hard disk
sequence according to the set
aliasnames. Changes takes effect after
rebooting the system. To view the set
alias names, run the command
omreport chassis
biossetup attribute=
bootorder
.
NOTE: On Linux systems, user or user
groups upgraded to administrator or
administrator groups cannot configure
this BIOS setup setting.
enabled: Enables the processor to go into a
deep sleep state when the system is not
utilized.
disabled: Disables the processor to go
into a deep sleep state when the system
is not utilized.
100omconfig: Managing Components Using the Instrumentation Service
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.