Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™,
PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell
Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD
is a registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc.
Microsoft®, Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks
or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat
Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are
registered trademarks of Novell Inc. in the United States and other countries. Oracle® is a registered trademark of Oracle Corporation
and/or its affiliates. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in
the United States and/or other countries. VMware
trademarks of VMware, Inc. in the United States or other countries.
Corporation.
2012 - 12
®
,
Virtual SMP
®
®
,
vMotion
®
is a registered trademark of International Business Machines
IBM
,
vCenter
®
and
vSphere
®
are registered trademarks or
®
®
Rev. A00
Contents
Notes, Cautions, and Warnings...................................................................................................2
What's New In This Release..................................................................................................................................11
Accessing The Windows Command Prompt To Run CLI Commands.....................................................................13
Scripting And Comparing Using CLI........................................................................................................................14
2 Using The omhelp Command...................................................................................................17
Example Help Commands.......................................................................................................................................17
3 omreport: Viewing System Status Using The Instrumentation Service...........................19
Conventions For Parameter Tables........................................................................................................................19
Command Summary Of The omreport Command...................................................................................................19
Help With The omreport Command........................................................................................................................22
4 Omconfig: Managing Components Using The Instrumentation Service..........................59
Conventions For Parameter Tables........................................................................................................................59
Help With The Omconfig Command........................................................................................................................62
Example Command For Adding Owner Information.......................................................................................120
Adding Service Contract Information...................................................................................................................120
Example Command For Adding Service Information......................................................................................120
Adding Support Information.................................................................................................................................121
Example Command For Adding Support Information.....................................................................................121
Adding System Information..................................................................................................................................122
Example Command For Adding System Information......................................................................................122
Syntax Of Command Elements..............................................................................................................................126
User Privileges For Omreport Storage And Omconfig Storage............................................................................127
Omreport Physical Disk Status.............................................................................................................................129
omreport Virtual Disk Status.................................................................................................................................130
Omreport Temperature Probe Status.............................................................................................................131
Omreport Fan Status......................................................................................................................................132
Omreport Power Supply Status......................................................................................................................133
Omreport Global Information................................................................................................................................135
Omconfig Physical Disk Commands.....................................................................................................................137
Omconfig Convert RAID To Non-RAID...........................................................................................................145
Omconfig Convert Non-RAID To RAID...........................................................................................................145
Omconfig Virtual Disk Commands........................................................................................................................146
Omconfig Fast Initialize Virtual Disk...............................................................................................................149
Omconfig Format Virtual Disk.........................................................................................................................151
Omconfig Global Commands.................................................................................................................................174
Omconfig Global Enable Smart Thermal Shutdown.......................................................................................175
Omconfig Global Disable Smart Thermal Shutdown......................................................................................175
Omconfig Global Rescan Controller...............................................................................................................176
Omconfig Set Hot Spare Protection Policy....................................................................................................176
9 Working With CLI Command Results...................................................................................179
Output Options For Command Results..................................................................................................................179
Writing Command Output To A File.......................................................................................................................180
Saving Command Results To A File That Is Overwritten................................................................................180
Append Command Results To An Existing File...............................................................................................181
Selecting A Format For The CLI Command Output...............................................................................................182
List (lst)...........................................................................................................................................................182
Custom Delimited Format (cdv)......................................................................................................................183
10
1
Introduction
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 manage their entire network by providing a comprehensive one-to-one systems
management.
In the context of Server Administrator, a system refers to a stand-alone system, a system with attached network storage
units in a separate chassis, or a 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.
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: The CLI does not use the Server Administrator Web server. For concerns on encryption, from the CLI, run
the omconfig system webserver action=stop command to turn off the Web server. The Web server starts
automatically after a reboot, so you must run this command each time the system is rebooted. . For more
information, see
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 terms used in this document, see the
omconfig system webserver or omconfig servermodule webserver.
Glossary
at dell.com/support/manuals.
What's New In This Release
The release highlights of OpenManage Server Administrator are:
•Availability of OMSA on supported 64-bit Windows operating systems.
NOTE: On systems prior to 12G , OMSA (64–bit) does not support information collection for DRAC5 using
SNMP and does not display few of the DRAC5 information on OMSA GUI and CLI.
•Added support for DIMM ranking in memory module. For more information, see omreport chassis memory.
•Added support for granular install options on systems running Windows operating systems. For more
information, see
•Added support for displaying the license details of the installed hardware devices including the iDRAC license.
For more information, see omreport licenses.
•Added support for viewing and selecting the format for alert messages. The enhanced alert messages, available
in iDRAC7, is introduced in OMSA. For more information, see omreport preferences messages and omconfig
preferences messages.
•Improved online help interface with Search capabilities for OMSA.
Dell OpenManage Server Administrator Installation Guide
at dell.com/support/manuals.
11
•Added support for the following features in Storage Management:
– Tape drive report that helps to enumerate all the supported tape drives connected to the server. For
more information, see omreport storage tape.
– Physical disk firmware report on the Graphical User Interface (GUI) that helps users to identify the disks
for which a new firmware version is available. You can generate this report at controller or system level
to get a consolidated information of the firmware versions of all physical disks attached to the server.
– Simplified and reduced the number of screens in the Virtual Disk Creation Wizard for better user
experience.
NOTE: For more information, see the
Guide
at dell.com/support/manuals.
•Added support for enhanced messaging, which includes unique system identifiers (system service tag, chassis
service tag, and system FQDN) and message identifier (Message ID) for enhanced SNMP trap varbinds. You can
associate an event to the respective server using the unique system identifiers. For more information, see the
Dell Event Message Reference Guide
•Added support for the following operating systems:
– Microsoft Windows Server 2012
– Red Hat Enterprise Linux 6.3
– Red Hat Enterprise Linux 6.3 Hypervisor
NOTE: This operating system supports OMSA on RHEL 6.3 as a hypervisor and it is not the RHEL
KVM hypervisor.
– Citrix XenServer 6.1
– VMware ESXi 4.1 U3
– VMware ESX 4.1 U3
NOTE: The VIB or supplemental pack for XenServer and VMware ESXi is available at support.dell.com.
NOTE: Dell PowerEdge
•Added support for Internet Explorer 10.
•Added support for the Mozilla Firefox 15 and 16.
•Added support for the following Network Interface Cards (NICs), Converged Network Adapters (CNAs), and
Fibre Channels (FCs):
yx2x
(12G) does not support Microsoft Windows 2003.
Dell OpenManage Server Administrator Storage Management User’s
at dell.com/support/manuals.
– QLogic QLE2660 Single Port FC16 HBA
– QLogic QLE2662 Dual Port FC16 HBA
– QLogic QME2662 Dual Port FC16 HBA Mezzanine
– Emulex LPm16002 Dual Port FC16 HBA Mezz
– Intel I350 2 x 1Gb BT + X520 2 x 10Gb SFP+ Rack NDC
•PowerEdge OEM Ready server models installed with OMSA 7.2 displays generic Server Administrator branding.
For more information on PowerEdge OEM Ready, see dell.com/oem.
•Deprecated support for Red Hat Enterprise Linux 6.2
NOTE: For the supported operating systems list, For the supported operating systems list, see the Dell Systems
Software Support Matrix Version 7.2 at dell.com/support/manuals → Product Type → Software, Monitors,
Electronics & Peripherals → Software → Enterprise System Management .
NOTE: CLI commands are not supported on systems running the VMware ESXi operating system.
12
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:
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.
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 actions that the system must perform when a certain warning or failure event
occurs. You can also use the
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:
omconfig command to assign specific values to the system's asset information parameters,
•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.
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 <package name> /s [/f command. For more information on the corresponding CLI
syntax, see the
Utility User’s Guide
Related Links: Working With CLI Command Results
Dell Update Packages for Operating Systems User’s Guide
at dell.com/support/manuals.
or the
Dell OpenManage Server Update
CLI Error Checking And Error Messages
When you type CLI commands, the CLI checks these commands for the 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 type a successful omconfig command, data for that component is displayed.
13
The following omconfig command examples displays valid CLI commands and their success messages:
Table 1. Commands And Messages
CommandMessage
omconfig chassis temps index=0
warnthresh= default
omconfig system assetinfo
info=depreciation 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.
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 duration=6
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.
The following are examples of some failure messages:
Command
Message
Revised command
When you type the revised command with three decimal points, you receive another error 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.
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 specifies the warning thresholds for each
major component of a system and also specifies a set of actions that the administrator wants each system to take in
case of a warning or failure event. In 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
14
implementation of new system administration policies easier across many existing systems that require reconfiguration.
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 are executed, 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.
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
In this example, 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:
In each chapter of this document, command syntax and other information about the commands are formatted using any
of the following fields as appropriate:
The omhelp command and its equivalent, <
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.
command
> -?, accesses the detailed help-text interface of Command Line
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
•about
•preferences
•chassis
•system
When you type omconfig system -?, the CLI help lists all the subcommands available for omconfig system:
•alertaction
•alertlog
•assetinfo
•cmdlog
•esmlog
•events
•platformevents
•pedestinations
•recovery
•shutdown
•thrmshutdown
•webserver
omconfig:
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.
17
When you type omconfig system assetinfo -?, the help that displays provides information about assigning
values for the name and option fields. Partial results for the request omconfig system assetinfo -? are as follows:
assetinfo Set asset information.
For one info value, specify one or more optional parameter(s).
The following table displays 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.
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. The following table lists the
systems on which the omreport commands are applicable:
Table 3. System Availability For The omreport Command
Command Level 1Command Level 2 Applicable To
omreportmodularenclosure Blade systems
servermoduleBlade systems
mainsystemBlade systems
systemRack and Tower systems
chassisRack and Tower systems
preferencesBlade or Rack, 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.
The symbol |, often called
or disable the component or feature, but you cannot simultaneously enable and disable the component or feature.
pipe
, is the logical
exclusive or
operator. For example, enable | disable means you can enable
Command Summary Of The omreport Command
Depending on the system configuration, the results of the omreport command vary from one system to another. Data
displays for installed components only.
19
NOTE: When a system includes an external chassis, the displayed results vary by operating system. On SUSE Linux
Enterprise Server and Red Hat Enterprise Linux systems, the 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.
The following table provides a high-level summary of the omreport command. The column titled Command level 1
displays 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.
The following table lists the omreport commands available for about, system, and main system chassis.
Table 4. Command Level 1, Level 2, And Level 3 For omreport
Command
Level 1
Command Level 2Command Level 3User
Privilege
Use
Required
omreportmodularenclosureU, P, ADisplays the information for all the modular
chassis.
aboutU, P, ADisplays the version number and properties for
Server Administrator.
details=trueU, 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.
fansU, P, ADisplays the status and thresholds for system
fans.
firmwareU, P, ADisplays the name and version of the firmware.
frontpanelU, P, ADisplays whether the 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.
fruU, P, ADisplays the Field Replaceable Unit (FRU)
information.
20
Command
Level 1
Command Level 2Command Level 3User
Privilege
Required
hwperformance U, P, ADisplays the status and cause for the system’s
infoU, P, ADisplays a status summary for main system
intrusionU, P, ADisplays the status of the system’s intrusion
ledsU, P, ADisplays the properties you have set for light-
memoryU, P, ADisplays properties of the system's memory
nicsU, P, ADisplays the NIC and Team interface properties.
portsU, P, ADisplays the properties for the system’s parallel
processorsU, P, ADisplays properties of the system’s processors,
Use
performance degradation.
chassis components.
sensor(s).
emitting diodes to flash under various alert
conditions.
arrays.
and serial ports, such as I/O address, IRQ level,
connector type, and maximum speed.
including speed, manufacturer, and processor
family.
pwrmanagementU, P, ADisplays power inventory details such as system
idle power, system maximum potential power,
and power budget information.
pwrmonitoringU, P, ADisplays properties of power consumption.
pwrsuppliesU, P, ADisplays the properties of power supplies.
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
licensesU, P, ADisplays the digital licenses of the installed
storageU, P, ASee Using The Storage Management Service.
system or
servermodule
U, P, ADisplays the system’s virtual flash (vFlash) and
secure digital (SD) card details.
hardware devices of the system.
U, P, ADisplays a high-level summary of system
components.
21
Command
Level 1
Command Level 2Command Level 3User
Privilege
Required
alertactionU, P, ADisplays the warning and failure threshold
alertlogU, P, AAllows the administrator to display the alert log.
assetinfoU, P, ADisplays the cost of ownership information for
cmdlogU, P, AAllows the administrator to display the command
esmlogU, P, AAllows the administrator to display the hardware
eventsU, P, ADisplays the system’s Simple Network
operatingsystemU, P, ADisplays the name and version of the operating
pedestinationsU, P, ADisplays the destinations to send the configured
platformeventsU, P, ADisplays the system’s response for each listed
Use
values, as well as actions configured when an
essential component detects a warning or failure
state.
the system.
log.
log.
Management Protocol (SNMP) event settings.
system.
alerts for platform events.
platform event
recoveryP, ADisplays how the system is configured to
respond to a hung operating system.
shutdownP, ADisplays how to perform the shutdown action.
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 server.
messagesADisplays the configured alert message format.
Related Links:
omreport: 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.
22
Use omreport <command level 2> -? to get help on the level 2 about, chassis, 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
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
CMC Information
Attribute : Product
Value : Chassis Management Controller (CMC)
Attribute : Description
Value : The system component provides a complete set
of remote managementfunctions 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
23
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
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. Type:
omreport chassis
or
omreport mainsystem
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
24
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: Input Source Line 1, upon redundancy
AC Power Lines
Status: Ok
Location: AC Power Line 1
AC Present : Power Present
Active Source : Active
Status : Ok
Location : AC Power Line 2
AC Present : Power Present
Active Source : Not Active
Server Administrator reports values for the
: 2
restoration, return to Line 1
Redundancy Status and Redundancy Mode fields.
25
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
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 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
To view all available boot devices, alias names, and boot order sequences, type:
omreport chassis biossetup attribute=bootorder
NOTE: The bootorder attribute is applicable only on systems prior to 12G. To list the device boot order, type
omreport chassis biossetup and serach the list under BIOS Boot Settings or UEFI Boot Settings
depending on the BIOS boot setting.
NOTE: On Linux systems, user or user groups upgraded to administrator or administrator groups cannot view the
boot order sequence.
BIOS Setup Parameters On Systems Prior To PowerEdge
The following table displays the available BIOS setup parameters on systems prior to PowerEdge
NOTE: All the BIOS Setup parameters are not displayed. Only those BIOS setup properties configured during
system boot are displayed.
yx2x
Systems
yx2x
systems.
26
Table 5. BIOS Setup Parameters On Systems Prior To Dell PowerEdge
yx2x
Systems
ParameterDescription
BootsequenceDisplays the device used to boot the system.
NumlockDisplays whether the keypad is used as number keys.
Embedded Video ControllerDisplays whether the Embedded Video Controller option is enabled or disabled.
Boot ModeDisplays whether the boot mode is configured to BIOS or Unified Extensible Firmware
Interface (UEFI).
Processor C1-EDisplays the Processor C1-E status.
CPU Execute DisableDisplays whether the Execute Disable (XD) option is enabled or disabled.
Processor C State ControlDisplays whether the Processor C State Control option is enabled or disabled.
Processor CMPDisplays the number of cores enabled per processor.
User accessible USB PortsDisplays whether the user-accessible USB port is enabled or disabled.
CPU Virtualization TechnologyDisplays the additional hardware capabilities provided by Virtualization Technology.
AC Power Recovery ModeDisplays the system state when input power is restored after an outage.
Embedded SATA ControllerDisplays whether the embedded SATA controller is set to ATA mode, RAID mode, or
is disabled.
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 enabled or disabled.
Dual NIC (3/4)Displays whether NIC 3 and NIC 4 with PXE/iSCSI is enabled or disabled.
NIC 1Displays whether the first NIC is enabled (with or without PXE/iSCSI) or disabled
during system boot.
NIC 2Displays whether the second NIC is enabled (with or without PXE/iSCSI) or disabled
during system boot.
NIC 3Displays whether the third NIC is enabled (with or without PXE/iSCSI) or disabled
during system boot.
NIC 4Displays whether the fourth NIC is enabled (with or without PXE/iSCSI) or disabled
during system boot.
Trusted Cryptographic Module
Displays whether TCM is on or off.
(TCM)
Trusted Platform Module
(TPM) Security
Displays whether TPM is off, on with pre-boot measurements, or on without pre-boot
measurements.
Internal USB Port (number)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.
Operating System Watchdog
Displays whether the operating system watchdog timer is enabled or disabled.
Timer
27
ParameterDescription
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 HypervisorDisplays whether the embedded hypervisor is enabled or disabled.
IDEDisplays whether the drive is enabled or disabled.
IDE Primary Drive 0Displays whether the device is automatically detected and enabled or if the device is
IDE Primary Drive 1Displays whether the device is automatically detected and enabled or if the device is
IntrusionDisplays whether the intrusion check is enabled or disabled during system boot.
MouseDisplays whether the mouse is enabled or disabled.
Optical Drive ControllerDisplays whether the optical drive controller is enabled or disabled.
Parallel port addressDisplays whether the address is located on LPT1, LPT2, and LPT3, or if it is disabled.
Parallel port modeDisplays the setting associated with the parallel port.
Primary SCSIDisplays whether the device is on or off.
RAID on motherboardDisplays whether RAID-on-motherboard is detected as a RAID device, a SCSI device,
RAID Channel ADisplays whether RAID-on-motherboard Channel A is detected as a RAID device or a
Displays whether DBS is enabled or disabled on the system.
disabled.
disabled.
or if the device is disabled during system boot.
SCSI device.
RAID Channel BDisplays whether RAID-on-motherboard Channel B is detected as a RAID device or a
SCSI device.
Serial Port 1Displays whether serial port 1 is mapped to a COM port, COM port 1, COM port 3,
COM1 BMC, BMC Serial, BMC NIC, BMC RAC, or is disabled.
Serial Port 2Displays whether serial port 2 is mapped to a COM port, COM port 2, 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 CommunicationsDisplays whether COM port 1 and COM port 2 are off or on with or without console
redirection.
28
ParameterDescription
Console Redirection After Boot Displays whether console redirection after system reboot is enabled or disabled.
External Serial ConnectorDisplays whether the external serial connector is mapped to Serial Device 1, Serial
Device 2, or a Remote Access Device.
Console Redirection Failsafe
Baud Rate
Serial Address SelectDisplays port address for the serial devices.
Displays the setting for console redirection failsafe baud rate.
BIOS Setup Groups On PowerEdge yx2x Systems
The following table lists the available groups of the BIOS setup parameters on PowerEdge
NOTE: Based on the hardware configuration, the attributes may vary in a specific group.
Table 6. 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 ManagementSets up the Embedded Server Management options.
Integrated DevicesControls the devices integrated on the system board.
Memory SettingsControls the system memory settings.
Miscellaneous SettingsControls some miscellaneous system settings.
One-Time BootSupports one-time boot to a specified device.
Processor SettingsControls the processor(s) settings of the system.
yx2x
systems.
SATA SettingsControl the embedded SATA ports settings.
Serial CommunicationControls the Serial Communication options.
Slot DisablementControls the system slots that are present on the system.
System InformationDisplays the information that uniquely identifies the system.
System Profile SettingsControls 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 uefi.
Omreport Chassis Currents Or Omreport Mainsystem Currents
This command is no longer available through Server Administrator.
29
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
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 Lifecycle Controller 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
30
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 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 chassis hwperformance
Server Administrator displays a summary of the system’s hardware performance degradation information.
NOTE: This command is applicable only to selected Dell
Depending on the system’s configuration, you may notice the following output:
Hardware Performance
Index: 0
Probe Name: System Board Power Optimized
Status: Normal
Cause: [N/A]
yx0x
systems that support PMBus.
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
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 Lifecycle Controller 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
31
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
A message that resembles the following is displayed:
Intrusion Information
Health : Ok
Index : 0
Status : OK
Probe Name : Intrusion
State : 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 : Off
Flash chassis identify LED timeout value : 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
32
The index parameter is optional. If you do not specify the index, Server Administrator displays information for all
memory modules on the system as follows:
The following is an example output:
Memory Information
Health : Ok
Attributes of Memory Array(s)
Location : System Board or Motherboard
Use : System memory
Installed Capacity : 65536 MB
Maximum Capacity: 786432 MB
Slots Available : 24
Slots Used : 8
Error Correction : Multibit ECC
Total of Memory Array(s)
Total Installed Capacity : 65536 MB
Total Installed Capacity Available
to the OS
Total Maximum Capacity : 786432 MB
: 64386 MB
Details of Memory Array 1
Index : 0
Status : Ok
Status : Ok
Status : Ok
Connector Name : DIMM_A1
Type : DDR3 - Synchronous Registered
(Buffered)
Size : 8192 MB
Index : 1
Status : Ok
Connector Name : DIMM_A2
Type : DDR3 - Synchronous Registered
(Buffered)
Size : 8192 MB
Index : 2
Status : Ok
33
Connector Name : DIMM_A3
Type : DDR3 - Synchronous Registered
(Buffered)
Size : 8192 MB
Index : 3
Status : Ok
Connector Name : DIMM_A4
Type : DDR3 - Synchronous Registered
(Buffered)
Size : 8192 MB
If you specify the index, Server Administrator displays a summary for a specific memory module displaying the health,
status, device name, type, speed, rank, and failures. A rank is a row of dynamic random access memory (DRAM) devices
comprising 64 bits of data per Dual Inline Memory Module (DIMM). The possible values of rank are single, dual,
quad, octal,
server.
The following is an example output if you specify the index:
Memory Device Information
Health : Ok
and hexa. The rank displays the rank of the DIMM and helps in the easy service of DIMMs on the
Status : Ok
Device Name : DIMM_A1
Size : 8192 MB
Type : DDR3 Synchronous Registered (Buffered)
Speed : 0.75 ns
Rank : Dual
Failures : None
NOTE: To maintain consistency across the commands, the output format of this command and the subsequent
command levels has changed. Change the user scripts as applicable.
Omreport Chassis Nics Or Omreport Mainsystem Nics
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 chassis nics index=n
34
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, Vendor, 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 name, IPv4 Addresses, IPv6 Addresses, Physical Interface Receive Statistics,
Physical Interface Transmit Statistics, Interface Receive Statistics, and Interface Transmit Statistics.
NOTE: The Fibre Channel over Ethernet (FCoE) and iSCSI over Ethernet (iSoE) features of Converged Network
Adapter (CNA) cards are not supported on VMware ESX and VMware ESXi systems.
To view Team interface properties, type:
omreport chassis nics config=team index=n
or
omreport mainsystem nics config=team index=n
NOTE: This command is applicable only if Team interface is configured in the system. Team interface 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, Vendor,
Description, and Redundancy Status.
If you specify the index, Server Administrator displays the Team interface details for the specific NIC and the values for
the following fields: Team Interface, Interface, IPv4 Addresses, IPv6 Addresses , Team Interface Receive Statistics ,
Team Interface Transmit Statistics , Interface Receive Statistics, and Interface Transmit Statistics.
Omreport Chassis Ports 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.
NOTE: CMC USB ports attached with blade servers are not enumerated by OMSA.
Server Administrator displays values for the following fields: Port Type, External Name, Base I/O Address, IRQ Level,
Connector Type, and Maximum Speed. The following table provides the description of the fields:
Table 7. Fields and Description
FieldDescription
Port TypeDetailed 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
Base I/O
Address
IRQ LevelHardware interrupt on a system. The hardware interrupt signals the system's CPU that an event has
Connector
Type
Name of the port, such as serial or parallel, USB, mouse, keyboard, and so on.
Starting I/O address expressed in hexadecimal.
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.
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
35
FieldDescription
connect a different device type to a system. Examples include DB-9 Male, AT, Access Bus, PS/2, and so
on.
Maximum
Speed
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.
The following table provides the description of the fields.
Table 8. Fields and Description
FieldDescription
IndexProcessor number
StatusCurrent status of the processor.
Connector NameName or number of the device that occupies the processor slot in the system.
Processor BrandType of processor made by a manufacturer such as Intel Itanium, Intel Pentium III, Intel Xeon, or
AMD Opteron.
Processor Version Model and stepping number of the processor.
Current SpeedActual processor speed in MHz at system boot time.
StateWhether the processor slot is enabled or disabled.
Core CountNumber 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 table lists the fields that are defined for the capabilities present on a particular microprocessor:
Table 9. Microprocessors and Fields
MicroprocessorFields
Intel Processor
36
•64-bit Support
•Hyperthreading (HT)
•Virtualization Technology (VT)
•Demand-Based Switching (DBS)
MicroprocessorFields
•Execute Disable (XD)
•Turbo Mode
AMD Processor
•64-bit Support
•AMD-V
•AMD PowerNow!
•No Execute (NX)
The following fields are defined for a cache present on a particular microprocessor. If the cache is internal to the
processor, the fields do not appear in the cache report:
•Speed
•Cache Device Supported Type
•Cache Device Current Type
•External Socket Name
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.
The following table displays the fields that are displayed for each cache on a particular processor:
Table 10. Fields And Description
FieldDescription
StatusReports whether a specific cache on the processor is enabled or disabled.
LevelRefers 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).
SpeedRefers to the rate at which the cache can forward data from the main memory to
the processor.
Max SizeMaximum amount of memory that the cache can hold in kilobytes.
Installed SizeActual size of the cache.
TypeIndicates whether the cache is primary or secondary.
LocationLocation of the cache on the processor or on a chipset outside the processor.
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.
37
FieldDescription
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
Cache Device Supported TypeType of static random access memory (SRAM) that the device can support.
Cache Device Current TypeType of the currently installed SRAM that the cache is supporting.
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.
External Socket Name Silk Screen
Name
Error Correction TypeIdentifies the type of error checking and correction (ECC) that this memory can
Name printed on the system board next to the socket.
perform. Examples are correctable ECC or uncorrectable ECC.
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 and the subsequent
command levels has changed. So, you may have to change the user scripts as applicable.
NOTE: The omreport chassis pwrmanagement or omreport mainsystem pwrmanagement command is applicable
on PowerEdge
supplies and not systems that have a fixed, non-redundant power supply installed.
The output of the omreport chassis pwrmanagement or omreport mainsystem pwrmanagement command lists each of
the valid parameters. The following table lists the available settings.
Table 11. Valid Parameters Of Omreport Chassis Pwrmanagement Or Omreport Mainsystem Pwrmanagement
yx1x
systems that support Power Management Bus (PMBus) and that have hot-swappable power
name=value pairDescription
unit=<watt | btuphr>
config=budget
config=profile
38
Displays power in the user-specified units.
Displays power budget information.
Displays power profiles information.
NOTE: On PowerEdge 12G systems, profile
option is SysProfile and is grouped under
System Profile Settings of the BIOS setup group. For
more information, see BIOS Setup Settings On
PowerEdge yx2x systems.
For each power management profile in the system, values display for the following fields: Maximum Performance, Active
Power Controller, OS Control, and Custom.
The Custom attributes are: CPU Power and Performance Management, Memory Power and Performance Management,
and Fan Power and Performance Management.
The following is an example output:
Power Inventory and Budget
Power Inventory
System Idle Power : 92 W
System Maximum Potential Power : 344 W
Power Budget
Attribute : Enable Power Cap
Values : Enabled
Attribute : Power Cap
Values : 400 W (56%)
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.com/support/manuals.
Dell License Manager Guide
at
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
•Failure Threshold
•Amperage: Location and Reading
•Power Tracking Statistics
•Energy Consumption
•Measurement Start Time
•Measurement Finish Time
•Reading
•System Peak Power
•System Peak Amperage
39
NOTE: The omreport chassis pwrmonitoring or omreport mainsystem pwrmonitoring command is applicable from
PowerEdge
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 License Manager Guide
NOTE: To maintain consistency across the commands, the output format of this command and the subsequent
command levels has changed. So, you may have to change the user scripts as applicable.
An example output reporting power statistics in Watts is as follows:
Power Consumption Information
Power Consumption
Index : 1
Status : Ok
Probe Name : System Board Pwr Consumption
Reading : 539W
Warning Threshold : 994W
Failure Threshold : 1400 W
Amperage
PS1 Current 1 : 1.2 A
Power Headroom
System Instantaneous Headroom : 300 W
System Peak Headroom : 340 W
Power Tracking Statistics
Statistic : Energy consumption
Measurement Start Time : Thu May 28 11:03:20 2011
Measurement Finish Time : Fri May 28 11:05:46 2011
Reading : 5.9 KWH
Statistics : System Peak Power
Measurement Start Time : Mon May 18 16:03:20 2011
Peak Time : Wed May 27 00:23:46 2011
Peak Reading : 630 W
Statistics : System Peak Amperage
Measured Since : Mon May 18 16:03:20 2011
Read Time : Tue May 19 04:06:32 2011
Peak Reading : 2.5 A
yx0x
system onwards that support PMBus and that have hot-swappable power supplies and not
at dell.com/support/manuals.
: Power Management features are only available for PowerEdge systems that have hot-swappable power
NOTE
supplies and not systems that have a fixed, non-redundant power supply installed.
40
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 remote access
controller if DRAC is installed. Type:
omreport chassis remoteaccess
or
omreport mainsystem remoteaccess
NOTE: To maintain consistency across the commands, the output format of this command and the subsequent
command levels has changed. So, you may have to change the user scripts as applicable.
The output of the omreport chassis remoteaccess or omreport mainsystem remoteaccess command lists each of the
valid parameters as displayed in the following table:
Table 12. 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=serialoverlanReports BMC/iDRAC or remote access information on a serial over LAN connection.
config=terminalmodeReports terminal mode settings for the serial port.
41
name=value pairDescription
config=userReports information on BMC/iDRAC or remote access users.
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: Critical
Attribute : Redundancy
Value : Lost
Internal SD Modules Status
Status : OK
Connector Name : System Board SD Status 1
State : Present
Storage Size : 512 MB
Status : OK
Connector Name : System Board SD Status 2
State : Present
Storage Size : 512 MB
VFlash Media Details
Connector Name : System Board SD Status 1
Type : vFlash SD Card
State : Present
Available Size : 472 MB
Storage Size : 512 MB
42
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. Type:
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.
For each slot in the system, values display for the following fields given in the following table:
Table 13. Valid Parameters Of Omreport Chassis Slots Or Omreport Mainsystem Slots
FieldDescription
IndexNumber of the slot in the system.
Slot IDSilk screen name printed on the system's motherboard next to the slot. Alphanumeric text uniquely
identifies each slot in the system.
AdapterName 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
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 the 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
43
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 Licenses
Use the omreport licenses command to view the digital licenses of the hardware devices installed on the system. Type:
omreport licenses
The following is an example output from the omreport licenses command:
Omreport System Commands Or Omreport Servermodule
Commands
Use the omreport system or omreport servermodule commands to view logs, threshold values, cost of ownership
information, and information about how shutdown actions and recovery actions are configured.
Omreport System 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. Type:
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:
44
SEVERITY
Ok : Main System Chassis
: COMPONENT
Critical
: Storage
Commands For Viewing Logs
Use the omreport system or omreport servermodule command to view the following 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
retain the log information for future reference, save a copy of the log before clearing. For more information about
clearing logs, see Commands For 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
or omconfig system cmdlog action=clear. If you need to
To view the contents of the ESM log, type:
omreport system esmlog
or
omreport servermodule esmlog
Overall Health Status Of The ESM Log
When you 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.
45
The omreport system alertaction or omreport servermodule alertaction command is useful for
actions have been specified for components. To
alertaction or omconfig servermodule alertaction command. For more information, see omconfig: Managing Components
Using The Instrumentation Service.
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.
set
an alert action for a component, use the omconfig system
viewing
which alert
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
•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
46
•Virtual Disk Failure
•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
assetinfo or omconfig servermodule assetinfo command. For more information, see Omconfig System Or Servermodule
Assetinfo Editing Cost Of Ownership Values.
set
any of these fields, use the omconfig system
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. Type:
omreport system events
or
omreport servermodule events
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. 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
---------------------
47
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.
Omreport System Events Type Or Omreport Servermodule Events Type
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. Type:
omreport system events type=fans
or
omreport servermodule events type=fans
This command displays a summary of each component in the system for which events are generated.
The following table displays 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.
Table 14. Valid Parameters Of Omreport System Events Type Or Omreport Servermodule Events Type
name=value pairDescription
type=accordsReports events for AC power cords
type=batteryReports events for batteries
type=fanenclosuresReports events for fan enclosures
type=fansReports events for fans
type=intrusionReports events for chassis intrusion
type=logReports 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
The following is an example output:
Current SNMP Trap Configuration
------System
------Settings
Enable: Informational, Warning, and Critical
Disable: None
----------Fans Group
----------
48
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. Type:
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.
Destination Configuration Settings For The Omreport System Pedestinations Or Omreport Servermodule
Pedestinations
The actual number of destinations that you can configure on a system using omreport system pedestinations or
omreport servermodule pedestinations may differ.
The following table displays the available settings.
Table 15. Settings For The Omreport System Pedestinations Or Omreport Servermodule Pedestinations
OutputAttributesDescription
Destination List
Destination Number:
Destination1
Destination Number:
Destination 2
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.
49
OutputAttributesDescription
Destination Configuration
Settings
Destination Number:
Destination 3
Destination Number:
Destination 4
Destination Number:
Destination 5
Destination Number:
Destination 6
Destination Number:
Destination 7
Destination Number:
Destination 8
attribute=communitystring
destination 3: Displays the third destination.
Example:
201:202:203:204: IPv4 address of the third destination.
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:7334: IPv6 address of the
fifth destination.
destination 6: Displays the sixth destination.
Example:
2001:0db8:85a3:0000:0000:8a2e:0370:7334: IPv6 address of the
sixth destination.
destination 7: Displays the seventh destination.
Example:
210.211.212.213: IP address of the seventh destination.
destination 8: Displays the eighth destination.
Example:
210.211.212.213: IP 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 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. You can also view the number of seconds that must elapse before an operating
system is considered hung.
50
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 summarycommand to view a comprehensive summary of
software and hardware components currently installed on the system. Type:
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.
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
not resemble the hardware and software configuration of the 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 : 7654321
Express Service Code : 15608862073
Chassis Lock : Present
Chassis Asset Tag : c
Remote Access Information
Remote Access Device : iDRAC7 Express
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 Capacity :2048 MB
Memory Available to the OS :2048 MB
52
Total Maximum Capacity :786432 MB
Memory Array Count : 1
Memory Array 1
Location : System Board or Motherboard
Use : System Memory
Installed Capacity : 2048 MB
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
Firmware Information
Name :iDRAC7
Version : 1.00
---------------
Network Data
---------------
Network Interface 0
IP Address : 10.94.22.111
Subnet Mask : 255.255.254.0
53
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
----------------
Storage Enclosure
--------------
Storage Enclosure
Name : Backplane
Hardware Information Using Omreport System Summary Or Omreport Servermodule Summary
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
Remote Access
Information
Processor
•Chassis Model
•Chassis Service Tag
•Express Service Code
•Chassis Lock
•Chassis Asset Tag
•Remote Access Device
•vFlash Media
•vFlash Media Size
The following are listed for each processor in the system:
•Processor Brand
•Processor Family
•Processor Version
•Current Speed
•Maximum Speed
54
•External Clock Speed
•Voltage
Memory
Memory Array
BIOS
Firmware
•Total Installed Capacity
•Memory Available to the Operating System
•Total Maximum Capacity
•Memory Array Count
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
•Manufacturer
•BIOS Version
•Release Date
•Name
•Version
Network Data
The following details are listed for each NIC and Team interface, if Team interface is configured in the system:
•IP Address
•Subnet Mask
•Default Gateway
•MAC Address
Storage Enclosures
The following details are listed for each storage enclosure attached to the system:
•Name
•Service Tag
Omreport System Thrmshutdown Or Omreport Servermodule Thrmshutdown
Use the omreport system thrmshutdown or omreport servermodule thrmshutdown command to view the properties
configured for a thermal shutdown action.
55
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. Type:
omreport system version
or
omreport servermodule version
NOTE: If iDRAC is installed, Server Administrator displays the Lifecycle Controller 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
configuration of the system:
Version Report
--------------------Main System Chassis
--------------------Name : BIOS
Version : 0.3.5
partial
command results are unique and may not resemble the results for the
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 : PERC H310 Mini
Version : 20.10.1-0025
Omreport Preferences Commands
Use the omreport preferences command to view the URL details of the Server Administrator Web server, key sign
algorithm, and message format.
56
Omreport Preferences Messages
Use the omreport preferences messages to view the configured alert message format.
The following table lists the available attributes of omreport preferences messages.
Table 16. Valid Parameters Of Omreport Preferences Messages
name=value pairDescription
attribute=formatReports the currently configured alert message format.
Type:
omreport preferences messages attribute=format
The output that is displayed is as follows:
Event Message Format : enhanced
Omreport Preferences Webserver
Use the omreport preferences webserver command to view the URL details and current key sign algorithm.
The following table lists the available attributes of omreport preferences webserver.
Table 17. Valid Parameters Of Omreport Preferences Webserver
name=value pairDescription
attribute=getcurlReports the URL information of the Web server.
attribute=getsignalgorithmReports the current key sign algorithm.
57
58
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 more 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.
Often, you must use the omreport commands 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.
The following table displays the system availability for the omconfig command:
Table 18. 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.
The symbol |, often called
or disable the component or feature, but you cannot simultaneously enable and disable the component or feature.
pipe
, is the logical
exclusive or
operator. For example, enable | disable means you can enable
omconfig Command Summary
The following table provides a high-level summary of the omconfig command. The columns titled
Command level 3
list the major arguments that are used with omconfig.
User privilege required
Command level 2
refers to the type of
and
59
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.
NOTE: Although the following table lists all possible omconfig commands, the commands available on the system
depend on the system configuration. If you try to get help or run 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.
Sets warning threshold values to the default or a
specific value.
61
Command
Level 1
Command Level 2Command Level 3User
Privilege
Required
Use
NOTE: You cannot change threshold values on
ESM3 and PowerEdge
x8xx
systems.
voltsP, A
storageFor more information, see Using The Storage
Sets warning threshold values to the default or a
specific value.
NOTE: You cannot change threshold values on
ESM3 and PowerEdge
Management Service.
x8xx
systems.
Help With The Omconfig Command
The following table lists the usage of omconfig commands.
Table 20. Usage Of Omconfig Commands
Command UsageDescription
omconfig -?To display the list of the available commands for omconfig.
omconfig <command
level 2> -?
omconfig chassis -?To display the help for omconfig chassis command.
omconfig system -?To display the help for omconfig system command.
omconfig preferences -?To display the available commands for omconfig preferences, such as cdvformat, which is
omconfig preferences
cdvformat -?
To display the help for about, chassis, preferences, and system’s level 2 commands.
the custom delimiter format (cdv).
To display the list of delimiter values for the cdv.
omconfig system
<command level 3> -?
omconfig system
alertaction -?
omconfig system
shutdown -?
omconfig system
alertaction -? | more
omconfig system
alertaction -? -outa
alert.txt
more alert.txtTo read the help for the alertaction command on Microsoft Windows, Red Hat Enterprise
62
To display the list of the parameters you must use to execute a particular omconfig system
command.
To display the list of valid parameters for omconfig system alertaction.
To display the list of valid parameters for omconfig system shutdown.
To display the list of valid parameters for omconfig system alertaction and to scroll the
command output one screen at a time. Here, | 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.
Here, -outa directs the output of the command to a file called alert.txt .
Linux, or SUSE Linux Enterprise Server operating systems.
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 rights reserved.
Company : Dell Inc.
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 output may change depending on the
configuration of the system and the version of Server Administrator.
Contains:Broadcom SNMP Agent 10.xx.xx
: Dell OpenManage Server Administrator
Common Storage Module 3.x.x
Data Engine 5.x.x
Hardware Application Programming Interface 5.x.x
Instrumentation Service 6.x.x
Instrumentation Service Integration Layer 1.x.x
Intel SNMP Agent 1.xx.x
OpenManage Inventory Collector 6.x.x
OpenManage Tools 6.x.x
Remote Access Controller 4 Data Populator 4.x.x
Remote Access Controller 4 Managed Node 4.6.3
Secure Port Server 1.x.x
Server Administrator Framework 6.x.x
Agent for Remote Access 1.x.x
Storage Management 3.x.x
Sun Java Runtime Environment 1.x.xx
Omconfig Chassis Or Omconfig Mainsystem
Use the omconfig chassis or omconfig mainsystem commands 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 the system configuration permits
63
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.
BIOS Setup Settings On Systems Prior To PowerEdge
The following table displays the name=value pairs that you can use with omconfig chassis biossetup or omconfig
mainsystem biossetup command on systems prior to PowerEdge
Table 21. BIOS Setup Settings on systems prior to PowerEdge yx2x systems
NOTE: On Linux systems, user or
user groups upgraded to
administrator or administrator
groups cannot configure this
BIOS setup setting.
attribute=bootmodesetting=uefi | bios
attribute=bootordersequence=aliasname1,
aliasname2,..... aliasnameN
attribute=hddordersequence=aliasname1,
aliasname2,..... aliasnameN
•uefi: 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.
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.
attribute=cstatessetting=enabled | disabled
attribute=conredirectsetting=enabled | disabled
•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.
•enabled: Redirects the BIOS
screen output over serial port
1. Keyboard and text output
are redirected over serial port
2.
•disabled: Turns off the BIOS
console redirection.
•enabled: Enables the intrusion
check during system boot. If
the system also has bezel
intrusion checking, then the
intrusion option checks for
removal of the bezel of the
system.
•disabled: Disables the
intrusion check during system
boot.
•enabled: Enables the internal
USB port.
•disabled: Disables the internal
USB port.
•on: Enables the mouse.
•off: Disables the mouse.
•enabled: Enables the first NIC
during system boot.
•enabledwithpxe: Enables the
first NIC during system boot
(with PXE on if the system has
PXE).
•disabled: Disables the first
NIC during system boot.
•enabledonly: Enables the first
NIC during system boot (with
PXE off if the system has PXE).
•enablednonepxe: Enables the
first NIC during system boot
(with PXE off if the system has
PXE).
•enabledwithiscsi: Enables the
first NIC during system boot
(with iSCSI on if the system
has iSCSI).
•backonly: Enables only the
user-accessible USB port(s)
located at the back of the
system.
•off: Disables the useraccessible USB port(s).
•enabled: Enables the USB
port(s).
•disabled: Disables the USB
port(s).
NOTE: Depending on the system's
hardware you can configure
either usb or usbb.
•enabled: Enables the USB
port(s) during system boot,
without BIOS support.
•enabledwithbios: Enables the
USB port(s) during system
boot, with BIOS support.
•disabled: Disables the USB
port(s) during system boot.
NOTE: Depending on the system's
hardware you can configure
either usb or usbb.
attribute=cstatessetting=enabled | disabled
•enabled: Enables the
processor to go into a deep
sleep state when the system
is not utilized.
•disabled: Disables the
processor from going into a
deep sleep state when the
system is not utilized.
BIOS Setup Settings On PowerEdge yx2x systems
The following table lists the BIOS setup attributes supported on PowerEdge
the attributes are grouped. Based on the hardware configuration, the possible attributes may vary in a specific group.
The omconfig chassis biossetup command does not display the read-only attributes.
NOTE: If you have configured the setup password, then, always set the same when you configure any BIOS
settings.
Table 22. BIOS Setup Settings On PowerEdge yx2x Systems
CAUTION: Clearing the TPM will cause loss of all
keys in the TPM. This could affect booting of the
operating system.
setting=Yes | No
Omconfig Chassis Currents Or Omconfig Mainsystem Currents
NOTE: This command is no longer available through Server Administrator.
Omconfig Chassis Fans Or Omconfig Mainsystem Fans
Use the omconfig chassis fans or omconfig mainsystem fans command to set fan probe warning thresholds. As with
other components, you can view both warning and failure threshold values, but you cannot set failure thresholds. The
system manufacturer sets the minimum and maximum failure thresholds.
Valid Parameters For Fan Warning Thresholds
The following table shows the valid parameters for setting fan warning thresholds:
Table 23. omconfig chassis fans or omconfig chassis fans
name=value pairDescription
index= <n>Number of the probe or probe index (must specify).
warnthresh=defaultSets minimum and maximum warning thresholds to
default.
minwarnthresh=<n>Minimum warning threshold.
maxwarnthresh=<n>Maximum warning threshold.
Default Minimum And Maximum Warning Thresholds
NOTE: Systems that contain ESM3, ESM4, and BMC capabilities do not allow you to set warning threshold values
to default values.
To set both the upper and lower fan warning threshold values to the recommended default value, type:
You cannot default one value and set another. In other words, if you default the minimum warning threshold value, you
are also selecting the default value for the maximum warning threshold value.
80
Specifying A Value For Minimum And Maximum Warning Thresholds
If you prefer to specify values for the fan probe warning thresholds, you must specify the number of the probe you are
configuring and the minimum and/or maximum warning threshold values. In the following example, the probe that is
being configured is probe 0. The first command sets only the minimum threshold; the second sets the minimum and
maximum thresholds:
When you issue the command and the system sets the values you specify, the following message is displayed:
Fan probe warning threshold(s) set successfully.
NOTE: You cannot set the minimum and maximum warning thresholds for the fan probe on PowerEdge
x9xx
systems.
Omconfig Chassis Frontpanel Or Omconfig Mainsystem Frontpanel
Use the omconfig chassis frontpanel or omconfig mainsystem frontpanel command to:
•configure the power button and the Nonmasking Interrupt (NMI) button
•configure the LCD to display:
– No information
– Custom information
– Default system information
– Service tag, system name
– Remote access MAC addresses
– System power
– Remote access IP address
– Ambient temperature of the system
– Remote access IPv4 address
– Remote access IPv6 address
•Specify and configure the LCD line number
•View the encryption state report of the LCD
•Configure LCD to indicate an active remote session when the Kernel-based Virtual Machine (KVM) is available
x8xx
and
NOTE: You can configure the Power and NMI buttons only if they are present on the system.
The following table displays the valid parameters for the command:
81
Table 24. Valid Parameters Of Omconfig Chassis Frontpanel Or Omconfig Mainsystem Frontpanel
name=value pair 1name=value pair 2 Description
lcdindex=<
config=none | default |
custom
text=<
nmibutton=enable | disable NA
powerbutton=enable |
disable
config=sysnameNASets the name of the system.
config=syspowerNASets the system power information.
config=servicetagNASets the system service tag information.
config=remoteaccessipv4NASets the remote access IPv4 information.
config=remoteaccessipv6NASets the remote access IPv6 information.
config=remoteaccessmacNASets the remote access MAC address.
config=ipv4idracSets IPv4 DRAC information.
index
custom text
>NASpecifies the LCD line number.
NA
>NASets the custom text for LCD when config=custom.
NA
•none: Sets the LCD text to none.
•default: Sets the LCD text to default.
•custom: Sets the LCD text to custom.
•enable: Enables the NMI button on the system.
•disable: Disables the NMI button on the system.
•true: Enables the Power button on the system.
•false: Disables the Power button on the system.
config=ipv6idracSets IPv6 DRAC information.
config=macidracNASets the DRAC’s MAC address.
config=ambienttempNASets the system temperature in centigrade.
security=modifyNAAllows you to modify the LCD text.
security=viewNAProvides read-only access to the LCD text.
security=disabledNAProvides limited access to the LCD text.
remoteindication=trueNALCD flashes when the system detects an active remote session.
NOTE: The options ipv4idrac, ipv6idrac, and macidrac are deprecated.
Omconfig Chassis Info Or Omconfig Mainsystem Info
Use the omconfig chassis info or omconfig mainsystem info command to enter an asset tag name and a chassis name
for the system. For a blade systems, enter asset tag names for modular components as well. The following table displays
the valid parameters for the command:
82
Table 25. Valid Parameters Of Omconfig Chassis Info Or Omconfig Mainsystem Info
name=value pairDescription
index=<n>Number of the chassis whose asset tag or name you are setting.
tag=<
text
>Asset tag in the form of alphanumeric text. Letters or numbers should not exceed 10
characters.
name=<
text
>Name of the chassis.
In the following example, the asset tag for the main system chassis is being set to buildsys:
omconfig chassis info index=0 tag=buildsys
or
omconfig mainsystem info index=0 tag=buildsys
Index 0 always defaults to the main system chassis. The following command omits index=n, but accomplishes the same:
omconfig chassis info tag=buildsys
or
omconfig mainsystem info tag=buildsys
An acceptable command, when executed, results in the following message:
Chassis info set successfully.
For some chassis, you can assign a different name. You cannot rename the main system chassis. In the following
example, the command renames chassis 2 from storscsi1 to storscsia:
omconfig chassis info index=2 name=storscsia
or
omconfig mainsystem info index=2 name=storscsia
As with other commands, the CLI issues an error message if you do not have a chassis 2 (the main chassis=0). The CLI
allows you to issue commands only for the system configuration you have.
Omconfig Chassis Leds Or Omconfig Mainsystem Leds
Use the omconfig chassis leds or omconfig mainsystem leds command to specify when to flash a chassis fault LED or
chassis identification LED. This command also allows you to clear the LED of the system hard drive. The following table
displays the valid parameters for the command.
Table 26. Valid Parameters Of Omconfig Chassis Leds Or Omconfig Mainsystem Leds
name=value pair 1name=value pair 2Description
index=<n>NANumber of the chassis where the LED resides
(defaults to chassis 0, main system chassis).
led=faultseverity=warning | criticalSelect to flash the LED either when a warning event
occurs or when a critical event occurs.
led=hdfaultaction=clearSets the number of faults for the hard drive back to
zero (0).
83
name=value pair 1name=value pair 2Description
led=identifyflash=off | on time-out=<n>Sets the chassis identification LED to off or on. Set the
time-out value for the LED to flash to a number of
seconds.
Omconfig Chassis Memorymode Or Omconfig Mainsystem Memorymode
Use the omconfig chassis memorymode or omconfig mainsystem memorymode command to specify the redundancy
mode to use for the system memory in case of memory errors.
Redundant memory enables a system to switch to other available memory modules if unacceptable errors are detected
in the modules that the system is currently using. The omconfig chassis memorymode or omconfig mainsystem
memorymode command allows you to disable redundancy; when you disable redundancy, you instruct the system not to
switch to other available memory modules when the memory module the system is using begins to encounter errors. To
enable redundancy, choose among spare, mirror, raid, and DDDC.
Spare mode disables a bank of system memory in which a correctable memory event is detected, enables the spare
bank, and copies all the data from the original bank to the spare bank. Spare bank requires at least three banks of
identical memory; the operating system does not recognize the spare bank.
Mirror mode switches to a redundant copy of memory when an uncorrectable memory event is detected. After
switching to the mirrored memory, the system does not switch back to the original system memory until the next reboot.
The operating system does not recognize half of the installed system memory in this mode.
RAID mode provides an extra level of memory checking and error recovery at the expense of some memory capacity.
The DDDC mode enables double device data correction. This ensures data availability after hard failure of x4 DRAM.
NOTE: This command is applicable only on systems prior to PowerEdge 12G systems. On PowerEdge 12G systems,
memorymode is grouped under Memory Settings of the BIOS setup group. For more information, see BIOS Setup
Groups On PowerEdge yx2x Systems.
To configure the attribute on systems prior to PowerEdge 12G, see the following table. The table displays the valid
parameters for the command.
Table 27. Valid Parameters Of Omconfig Chassis Memorymode Or Omconfig Mainsystem Memorymode
name=value pair 1Description
index=<n>Number of the chassis where the memory module resides
(the default is chassis 0, the main system chassis).
spare: Disables the memory module that has a correctable
memory event and copies the failing module’s data to a
spare bank.
mirror: Switches the systems to a mirrored copy of the
memory if the failing module has an uncorrectable
memory event. In the mirror mode, the operating system
does not switch back to the original module until the
system reboot.
disabled: Indicates that the system is not to use other
available memory modules if uncorrectable memory
events are detected.
raid5: Method of system memory configuration. This is
logically similar to the RAID-5 mode used in hard drive
storage systems. This memory mode provides an extra
level of memory checking and error recovery at the
84
name=value pair 1Description
expense of some memory capacity. The RAID mode
supported is RAID level 5 striping with rotational parity.
dddc: The dddc mode enables double device data
correction. This ensures data availability after hard failure
of x4 DRAM.
opmode=mirror | optimizer | advecc
mirror: Switches the systems to a mirrored copy of the
memory if the failing module has an uncorrectable
memory event. In the mirror mode, the operating system
does not switch back to the original module until the
system reboots.
optimizer: Enables the DRAM controllers to operate
independently in 64-bit mode and provide optimized
memory performance.
advanced ECC (advecc): Enables the two DRAM
controllers to combine in 128-bit mode and provide
optimized reliability. Memory that are not teamed by the
controllers is not reported to the operating system.
Omconfig Chassis Pwrmanagement Or Omconfig Mainsystem Pwrmanagement
Use the omconfig chassis pwrmanagement or omconfig mainsystem pwrmanagement command to configure power cap
and manage profiles that control power utilization.
NOTE: This command is valid only on systems prior to PowerEdge
The following table displays the valid parameters for the command:
Table 28. Valid Parameters Of Omconfig Chassis Pwrmanagement Or Omconfig Mainsystem Pwrmanagement
NOTE: From PowerEdge
system onwards, power budget
requires license to configure
power cap. If the appropriate
license is not installed or has
expired, the system displays an
error message. For more
information, see
watt: Configure the unit in Watts.
btuphr: Configure the unit in BTU/hr.
percent: Configure the unit in
percentage.
maxperformance: Sets the processor
to the highest supported processor
state. It offers maximum performance
mode with minimal power economy.
at dell.com/support/
yx2x
Dell License
85
name=value pair 1name=value pair 2Description
NOTE: This option is supported on
systems prior to PowerEdge
systems.
yx2x
cpupowermode=min | max |
systemdbpm | osdbpm
apc: Active Power Control (apc)
enables the demand-based power
management controlled by BIOS.
osctrl: OS Control (osctrl) enables the
demand-based power management
controlled by the operating system.
custom: This profile allows you to
configure individual BIOS settings. It
offers added control by displaying the
underlying BIOS settings.
min: Sets the CPU power consumption
to minimum.
max: Sets the CPU power
consumption to maximum.
systemdbpm: Sets the mode to system
demand based power management.
osdbpm: Sets the mode to operating
system demand based power
management.
NOTE: These options are
applicable only when a custom
profile is selected.
memorypowermode=min | 800 | 1067 |
1333 | max
fanmode=min | max
NOTE: Reboot the system for the power profiles setup options to take effect.
min: Sets the mode to minimum power
utilization.
800 | 1067 | 1333: Set the mode to 800,
1067, or 1333 MHz.
max: Sets the mode to maximum
performance.
NOTE: These options are
applicable only when a custom
profile is selected.
min: Sets the fanmode to minimum
power utilization.
max: Sets the fanmode to maximum
power utilization.
NOTE: These options are
applicable only when a custom
profile is selected.
Omconfig Chassis Pwrmonitoring Or Omconfig Mainsystem Pwrmonitoring
Use the omconfig chassis pwrmonitoring or omconfig mainsystem pwrmonitoring command to configure power
consumption information.
The following table displays the valid parameters for the command:
86
Table 29. Valid Parameters Of Omconfig Chassis Pwrmonitoring Or Omconfig Mainsystem Pwrmonitoring
name=value pair 1name=value pair 2Description
index=<n>NANumber of the probe or probe index
(must specify).
config=probewarnthresh=settodefaultSets the minimum and maximum
warning thresholds values to default.
warnthresh=<n >Sets a value for the warning
threshold.
unit=watt | btuphr
config=resetreadingtype=energy | peakpower
watt: Displays the unit in Watts.
btuphr: Displays the unit in BTU/hr.
energy: Resets the system energy
reading.
peakpower: Resets the system peak
power.
NOTE: This command is applicable only on selected Dell
NOTE: Power monitoring requires license to configure the power budget information. If the appropriate license is
not installed or has expired, the system displays an error message. For more information, see
Manager
at dell.com/support/manuals.
yx0x
systems that support PMBus.
Dell License
Default Warning Thresholds
NOTE: Sensor managing capabilities vary across systems.
To set both the upper and lower power consumption probe warning threshold values to the recommended default value,
type:
You cannot default one value and set another. If you default the minimum warning threshold value, you are also
selecting the default value for the maximum warning threshold value.
Specify A Value For Warning Thresholds
If you prefer to specify values for the power consumption probe warning thresholds, you must specify the number of the
probe you are configuring and the warning threshold value. Configure the values to display either in BTU/hr or Watts. In
the following example, the probe that is being configured is probe 4:
When you issue the command and the system sets the values you specify, the following message is displayed:
Power consumption probe warning threshold(s) set successfully.
Omconfig Chassis Remoteaccess Or Omconfig Mainsystem Remoteaccess
Use the omconfig chassis remoteaccess or omconfig mainsystem remoteaccesscommand to configure:
87
•Remote access on a local area network (LAN).
•The serial port for BMC or RAC, whichever is installed.
•The BMC or RAC on a serial over LAN connection.
•Terminal settings for the serial port.
•Advanced settings for a serial over LAN connection.
•Information on a BMC or RAC user.
•Information on IPv6 and IPv4 interfaces.
NOTE: Enter the user ID to configure user information.
Type:
omconfig chassis remoteaccess
or
omconfig mainsystem remoteaccess
The output of the omconfig chassis remoteaccess or omconfig mainsystem remoteaccess command lists each of the
available configurations. The following table displays the valid parameters:
Table 30. Valid Parameters Of Omconfig Chassis Remoteaccess Or Omconfig Mainsystem Remoteaccess
name=value pair 1
config=
config=additionalipv4=enable | disable
config=advsolcharaccuminterval=number
name=value pair 2Description
ipv6=enable | disable
charsendthreshold=number
enableipmi= true | false
enablenic=true | false
enable: IPv4 stack to load on iDRAC.
disable: IPv4 stack to flush on iDRAC.
enable: Enables IPv6 stack to load on iDRAC.
disable: Disables IPv6 stack to unload on iDRAC.
NOTE: This option requires license to enable or
disable ipv6. If the appropriate license is not
installed or has expired, the system displays an
error message. For more information, see
License Manager
number: Sets the character accumulate interval in 5
millisecond intervals.
number: Sets the number of characters. BMC
automatically sends a serial over LAN data packet that
contains the number of characters as soon as this
number of characters (or greater) has been accepted
from the baseboard serial controller into the BMC.
true: Enables IPMI over LAN.
false: Disables IPMI over LAN.
true: Enables DRAC NIC.
false: Disables DRAC NIC
NOTE: The enablenic option is supported on
PowerEdge
installed.
sharedwithfailoveronall: Configures the new NIC
selection option.
nic1: Enables NIC 1.
teamednic1nic2: Enables NIC teaming functionality.
name=value pair 1
config=
name=value pair 2Description
dracnic: Enables DRAC NIC if DRAC 5 is installed.
NOTE: The nicselection option is supported only
on PowerEdge
PowerEdge
failovernw replaces nicselection.
x9xx
to
yx1x
systems. From
yx2x
systems onwards, primarynw and
primarynw=dedicated | lom1 | lom2 |
lom3 | lom4
failovernw=none | lom1 | lom2 | lom3 |
lom4 | all
dedicated: Configures dedicated port as primary
network for remote access.
NOTE: This option requires license to configure
primarynw as dedicated. If the appropriate license
is not installed or has expired, the system displays
an error message. For more information, see
License Manager
lom 1: Configures lom1 port as the primary network for
remote access.
lom 2: Configures lom2 port as the primary network for
remote access.
lom 3: Configures lom3 port as the primary network for
remote access.
lom 4: Configures lom4 port as the primary network for
remote access.
NOTE: The primarynw option is supported from
PowerEdge
primarynw is set to dedicated, then set failovernw
to none.
none: Configures the failover network to none.
lom 1:Configures the failover network to lom 1.
lom 2: Configures the failover network to lom 2.
lom 3: Configures the failover network to lom 3.
lom 4: Configures the failover network to lom 4.
all: Configures the failover network to all loms.
NOTE: The failovernw option is supported on
PowerEdge
primarynw and failovernw to set the nicselection.
The primarynw and failovernw options cannot
have the same value.
NOTE: Failovernw requires license to configure
the ports. If the appropriate license is not installed
or has expired, the system displays an error
message. For more information, see
Manager
at dell.com/support/manuals.
yx2x
systems onward. If the
yx2x
systems onward. Configure both
Dell License
at dell.com/support/manuals.
Dell
ipaddress=IP
subnet=SubnetSets a subnet mask if you have selected static as the
gateway=Gateway
Sets the IP address if you have selected static as the
IP address source for the BMC LAN interface.
IP address source for the BMC LAN interface.
Sets a gateway address if you have selected static as
the IP address source for the BMC LAN interface.
89
name=value pair 1
config=
name=value pair 2Description
ipsource=static | dhcp |
systemsoftware
static: Static if the IP address of the BMC LAN
interface is a fixed, assigned IP address.
dhcp: DHCP if the source of the IP address of the BMC
LAN interface is the dynamic host configuration
protocol.
systemsoftware: System software if the source of the
IP address of the BMC LAN interface is from the
system software.
NOTE: All commands may not be supported on the
system.
ipaddressv6=<
prefixlength= length
gatewayv6=<
ipsourcev6=static | auto
altdnsserverv6Validates the address of the alternate DNS server for
dnssourcev6=static | auto
vlanenable=true | false
vlanid=number
vlanpriority=number
privilegelevel=administrator | operator
| user
encryptkey=text
confirmencryptkey=text
IPv6 address
value
>Validates the IPv6 gateway.
>
Validates the IPv6 address for configuration.
static: IPv6 address source is set to static.
auto: IPv6 address source is set to auto.
configuration.
static: DNS source is set to static.
auto: DNS source is set to auto.
true: Enables the virtual LAN identification.
false: Disables the virtual LAN identification.
number: Virtual LAN identification in the range of 1 to
4094.
number: Priority of virtual LAN identification in the
range of 0 to 7.
administrator: Sets the maximum privilege level that is
accepted on a LAN channel, to Administrator.
operator: Sets the maximum privilege level that is
accepted on a LAN channel, to Operator.
user: Sets the maximum privilege level that is accepted
on a LAN channel, to User.
text: Text used for encryption and confirmation of
encryption.
NOTE: The text option is supported only on
PowerEdge
NOTE:
extipmiusergroup user
group is available only
on the Dell
systems.
yx0x
blade
loginidrac=true | falsetrue or false: Enables or
disables logging into iDRAC.
configureidrac=true | falsetrue or false: Enables or
disables configuration of
iDRAC.
Omconfig Chassis Temps Or Omconfig Mainsystem Temps
Use the omconfig chassis temps or omconfig mainsystem temps command to set warning thresholds for temperature
probes. As with other components, you can view both warning and failure threshold values, but you cannot set failure
threshold values. The system manufacturer sets the minimum and maximum failure threshold values.
NOTE: Threshold values that you can set vary from one system configuration to another.
Valid Parameters For Temperature Warning Thresholds
The following table displays the valid parameters for setting temperature warning thresholds:
Table 33. Valid Parameters For Omconfig Chassis Temps Or Omconfig Mainsystem Temps
name=value pairDescription
index=<n>Number of the probe or probe index (specify).
warnthresh=defaultSets the minimum and maximum warning threshold values to default.
minwarnthresh=<n>Sets the minimum warning threshold values (one decimal place).
maxwarnthresh=<n>Sets the maximum warning threshold values (one decimal place).
Setting Minimum And Maximum Warning Threshold Values
To set both the upper and lower temperature warning threshold values to the recommended default value, type:
omconfig chassis temps index=0 warnthresh=default
or
omconfig mainsystem temps index=0 warnthresh=default
You cannot default one value and set another. In other words, if you set the minimum warning threshold value to the
default value, you are also selecting the default value for the maximum warning threshold value.
NOTE: The capabilities for managing sensors vary by systems.
Specify A Value For Minimum And Maximum Warning Thresholds
To specify values for the temperature probe warning thresholds, you must specify the number of the probe you are
configuring and the minimum and/or maximum warning threshold value. In the following example, the probe that is being
configured is probe 4:
omconfig chassis temps index=4 minwarnthresh=11.2 maxwarnthresh=58.7
95
or
omconfig mainsystem temps index=4 minwarnthresh=11.2 maxwarnthresh=58.7
When you issue the command and the system sets the values you specify, the following message is displayed:
Temperature probe warning threshold(s) set successfully.
NOTE: On PowerEdge
ambient temperature.
x8xx
and
x9xx
systems, you can set the temperature probe warning threshold only for
Omconfig Chassis Volts Or Omconfig Mainsystem Volts
Use the omconfig chassis volts or omconfig mainsystem volts command to set voltage probe warning thresholds. As
with other components, you can view both warning and failure threshold values, but you cannot set failure threshold
values. The system manufacturer sets the minimum and maximum values for the failure thresholds.
Valid Parameters For Voltage Warning Thresholds
The following table displays the valid parameters for setting voltage warning threshold values.
NOTE: Threshold values that you can set vary from one system configuration to another.
Table 34. Valid Parameters Of Omconfig Chassis Volts Or Omconfig Mainsystem Volts
name=value pairDescription
index=<n>Probe index (specify).
warnthresh=defaultSets minimum and maximum warning threshold values to default.
minwarnthresh=<n>Sets minimum warning threshold value (three decimal places).
maxwarnthresh=<n>Sets maximum warning threshold value (three decimal places).
Specify A Value For Minimum And Maximum Warning Thresholds
To specify values for the voltage probe warning thresholds, you must specify the number of the probe you are
configuring and the minimum and/or maximum warning threshold values.
In the following example, the probe being configured is probe 0:
When you issue the command and the system sets the values you specify, the following message is displayed:
Voltage probe warning threshold(s) set successfully.
NOTE: On PowerEdge
voltage.
x8xx
systems, you cannot set the minimum and maximum warning threshold values for the
Omconfig Preferences
Use the omconfig preferences command to set system preferences. Use the command line to set the SNMP root
password and specify the user levels able to access Server Administrator. You can also configure the Active Directory
service and SNMP set operations.
96
Omconfig Preferences Cdvformat
Use the omconfig preferences cdvformat to specify the delimiters for separating data fields reported in the custom
delimited format. The valid values for delimiters are: exclamation, semicolon, at, hash, dollar, percent, caret, asterisk,
tilde, question, colon, comma, and pipe.
The following example shows how to set the delimiter for separating data fields to asterisk:
omconfig preferences cdvformat delimiter=asterisk
Omconfig Preferences Dirservice
Use the omconfig preferences dirservice command to configure the Active Directory service. The
<productname>oem.ini file is modified to reflect these changes. If the "adproductname" is not present in the
<productname>oem.ini file then a <computername>-<computername> refers to the name of the computer running
Server Administrator and <productname> refers to the name of the product defined in omprv32.ini. For Server
Administrator, the product name is "omsa".
Therefore, for a computer named "myOmsa" running Server Administrator, the default name is "myOmsa–omsa". This is
the name of Server Administrator defined in Active Directory by using the snap-in tool. This name must match the name
for the application object in Active Directory in order to find user privileges.
NOTE: This command is applicable only on systems running the Windows operating system.
The following table displays the valid parameters for the command:
Table 35. Valid Parameters Of Omconfig Preferences Dirservice
name=value pairDescription
prodname=<text>Specifies the product to which you want to apply the Active Directory configuration changes.
prodname refers to the name of the product defined in omprv32.ini. For Server Administrator, it
is "omsa".
enable=<true | false>
adprodname=<text> Specifies the name of the product as defined in the Active Directory service. This name links the
true: Enables Active Directory service authentication support and the Active Directory Login
option on the login page.
false: Disables Active Directory service authentication support and the Active Directory Login
option on the login page. If the Active Directory Login option is not present, you can only login to
the local machine accounts.
product with the Active Directory privilege data for user authentication.
Omconfig Preferences Messages
Use the omconfig preferences messages command to select the format of alert messages. The default format is
traditional, which is the legacy format.
The following table lists the parameters you can use with this command.
Table 36. Valid Parameters Of Configuring Preferences Messages
name=value pair 1name=value pair 2Description
attribute=formatsetting=traditional | enhanced
traditional: Sets the alert message to traditional format.
97
name=value pair 1name=value pair 2Description
enhanced: Sets the alert message to Enhanced Event
Messaging format. This is similar to the format available in
iDRAC7.
For example, to set the message format to traditional use the following command:
omconfig preferences messages format=traditional
Omconfig Preferences Snmp
Setting the SNMP root password allows administrators to restrict access to SNMP set operations that allow important
systems management interventions. You can configure the SNMP root password normally (by typing all of the
parameters in one command line) or interactively.
Using the omconfig preferences snmp command, you can also configure SNMP set operations.
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.
CAUTION: Interactive mode is the more encrypted method of setting the SNMP root password. In non-interactive
mode, the values you enter for the
type them. In the interactive mode, the values you type for passwords are masked.
The parameters for configuring the SNMP root password are the same whether you configure it interactively or
iteratively.
NOTE: If you specify setting=rootpw but do not specify the other name=value pair parameters, you enter interactive
mode, and the command line prompts you for the remaining values.
newpw
and
confirmnewpw
options appear on the system’s monitor when you
The following table displays the valid parameters for the command.
Table 37. SNMP Root Password Parameters
name=value pairDescription
setting=rootpwRequired
oldpw=<
newpw=<
confirmnewpw=<
When you type omconfig preferences snmp setting=rootpw, the system prompts you to supply values
for the required parameters.
When you type omconfig preferences snmp, you must supply all the parameters in the initial command line. For
example:
NOTE: After executing the command to enable or disable SNMP set operations, restart services for the change to
take effect. On systems running supported Microsoft Windows operating systems, restart the Windows SNMP
Service. On systems running supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating
systems, restart Server Administrator services by running the srvadmin-services.sh restart command.
Omconfig Preferences Useraccess
Depending on the policies of your organization, you may want to restrict the access that some user levels have to Server
Administrator. The omconfig preferences useraccess command allows you to grant or withhold the right of users and
power users to access Server Administrator.
The following table displays the valid parameters for the command:
Table 39. Enabling User Access For Administrators, Power Users, And Users
CommandResultDescription
omconfig preferences useraccess
enable=user
omconfig preferences useraccess
enable=poweruser
omconfig preferences useraccess
enable=admin
Grants Server Administrator access to
Users, Power Users, and
Administrators.
Grants Server Administrator access to
Power Users and Administrators.
Grants Server Administrator access to
Administrators
only
.
Least restrictive form of user access.
Excludes user level access only.
Most restrictive form of user access.
Omconfig Preferences Webserver
Use the omconfig preferences webserver command to set the encryption levels of the Server Administrator Web server
and configure the URL launch point in the Server Administrator Web server environment.
The following table displays the name=value pairs you can use with this command:
Table 40. Valid Parameters Of Omconfig Preferences Webserver
Use the omconfig system or omconfig servermodule commands to clear logs, determine how various shutdown actions
occur, set initial values or edit values for cost of ownership information, and determine how to respond to a hung
operating system.
Omconfig System Alertaction Or Omconfig Servermodule Alertaction
You can use the omconfig system alertaction or omconfig servermodule alertaction command to determine how Server
Administrator responds when a component has a warning or failure event.
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.
Defining Alert Actions
An alert action is an action that you specify for the system to take when specified conditions are met. Alert actions
determine in advance what actions to take for warning or failure events on intrusion, fans, temperatures, voltages,
power supplies, memory, and redundancy.
For example, if a fan probe on the system reads a fan RPM of 300 and your minimum warning threshold value for that fan
probe is 600 RPM, then the system generates a fan probe warning. Alert action settings determine how users are
notified of this event. You can also configure alert actions for temperature, voltage, and probe readings that fall within
the warning or failure range.
Syntax For Setting Alert Actions
Setting an alert action requires two name=value pairs. The first name=value pair is the event type. The second
name=value pair is the action to take for this event. For example, in the command:
omconfig system alertaction event=powersupply broadcast=true