CLI Guide

Severity
In the context of configuring events, severity determines how severe an event is, before Server Administrator notifies you of
the event for a component type. When there are multiple components of the same type in the same system chassis, you can
specify whether you want notification for event severity according to the number of the component by using the index=<n>
parameter. The following table displays the valid severity parameters.
Table 73. System Event Severity Parameters
Command Result Description
omconfig system events
type=<component name> severity=info
or omconfig servermodule events
type=<component name> severity=info
Enables notification for informational,
warning, and critical events.
Least restrictive form of event
notification.
omconfig system events
type=<component name>
severity=warning or omconfig
servermodule events type=<component
name> severity=warning
Enables notification for warning and
critical events.
Omits informational event notification,
for example, when a component returns
to normal status.
omconfig system events
type=<component name>
severity=critical or omconfig
servermodule events type=<component
name> severity=critical
Enables notification for critical events
only.
Restrictive form of event notification.
omconfig system events
type=<component name> severity=none
or omconfig servermodule events
type=<component name> severity=none
Disables event notification. No event notification.
Index
Index refers to the number of an event for a particular component. Index is an optional parameter. When you omit the index
parameter, events are configured for all components of the specified type, such as all fans. For example, when a system
contains more than one fan, you can enable or disable event notification for a particular fan. An example command is as follows:
omconfig system events type=fan index=0 severity=critical
or
omconfig servermodule events type=fan index=0 severity=critical
As a result of the example command, Server Administrator sends an SNMP trap only when the first fan in the system chassis
(index 0) has reached critical fan RPMs.
Omconfig System Webserver Or Omconfig Servermodule
Webserver
Use the omconfig system webserver or omconfig servermodule webserver command to start or stop the Web
server. The following table displays the valid parameters for the command.
Table 74. Valid Parameters Of Web Server Configuration
name=value pair Description
action=start Starts the Web server.
action=stop Stops the Web server.
action=restart Restarts the Web server.
114 Omconfig Managing Components Using The Instrumentation Service