CLI Guide

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 conguration, the error message states that
the component is not present.
The following are examples of some failure messages:
Table 2. Failure messages
Command
omconfig chassis volts index=3
minwarnthresh=3.3000
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.
Revised command
omconfig chassis volts index=3
minwarnthresh=3.300
When you type the revised command with three decimal points, you receive another error message:
Table 3. Error messages for commands with three decimals
Message
Error! This voltage probe min warning
threshold must be between 11.400 and 12.480.
Revised command
omconfig chassis volts index=3
minwarnthresh=11.500
Message
Voltage probe warning threshold(s) set
successfully.
Scripting And Comparing Using CLI
The Server Administrator CLI allows administrators to write batch programs for the operating system. For an enterprise with many
systems, an administrator could write a conguration script that species the warning thresholds for each major component of a
system and also species 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 conguring any
number of new systems acquired by a company and makes implementation of new system administration policies easier across many
existing systems that require re-conguration.
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
11