Users Guide

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.
The following omconfig 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 configuration,
the error message states that the component is not present.
The following are examples of some 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:
13