CLI Guide
omcong command to assign specic values to the system's asset information parameters, such as the purchase price of the system, the
system's asset tag, or the system's location.
The omhelp command displays short-text help for CLI commands. The shorthand equivalent of omhelp is the command for which you want
help followed by -?. For example, to display help for the omreport command, type one of the following commands:
• omhelp omreport
• omreport -?
The omreport command displays reports of the management information of the system.
NOTE: For an overall summary of the CLI commands, type omhelp.
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 dierent components, download the Dell Update Package and run the
<package name> /s [/f command. For more information on the corresponding CLI syntax, see the
Dell Update Packages
for Operating Systems User’s Guide
or the
OpenManage Server Update Utility User’s Guide
at dell.com/support/manuals.
Related Links: Working With CLI Command Results
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 omcong command, data for that component is displayed.
The following omcong command examples displays valid CLI commands and their success messages:
Table 1. Commands And Messages
Command Message
omconfig chassis temps index=0 warnthresh=
default
Temperature probe warning threshold value(s)
set successfully.
omconfig chassis biossetup attribute=numlock
setting=on
BIOS setup configured successfully. Change will
take effect after the next reboot.
omconfig system assetinfo info=depreciation
duration=6
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 conguration, the error message states that the
component is not present.
The following are examples of some failure messages:
Introduction
11