Dell External OEMR 2970 User Guide - Page 96

omconfig system webserver, When you omit the index parameter

Page 96 highlights

Severity In the context of configuring events, severity determines how severe an event must be 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 also specify whether you want to be notified for event severity according to the number of the component by using the index= parameter. Table 4-26 shows the valid severity parameters. Table 4-26. System Event Severity Parameters Command Result Description omconfig system events type= Enables notification for Least restrictive form of event severity=info informational, warning, notification. and critical events. omconfig system events type= Enables notification for Omits informational event severity=warning warning and critical notification, for example, when a events. component returns to normal status. omconfig system events type= Enables notification for Restrictive form of event severity=critical critical events only. notification. omconfig system events type= Disables event severity=none 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. When a system contains more than one fan, for example, 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 As a result of the example command, Server Administrator will send an SNMP trap only when the first fan in the system chassis (index 0) has reached critical fan RPMs. omconfig system webserver Use the omconfig system webserver command to start or stop the Web server. Table 4-27 shows the valid parameters for the command. Table 4-27. Web Server Configuration Parameters name=value pair action=start action=stop action=restart Description Starts the Web server. Stops the Web server. Restarts the Web server. 96 omconfig: Managing Components Using the Instrumentation Service

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

96
omconfig: Managing Components Using the Instrumentation Service
Severity
In the context of configuring events, severity determines how severe an event must be 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 also specify whether you want to be notified for event
severity according to the number of the component by using the index=
<n>
parameter. Table 4-26 shows
the valid severity parameters.
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. When a system contains more than one fan, for example, 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
As a result of the example command, Server Administrator will send an SNMP trap only when the first
fan in the system chassis (index 0) has reached critical fan RPMs.
omconfig system webserver
Use the
omconfig system webserver
command to start or stop the Web server. Table 4-27 shows the valid
parameters for the command.
Table 4-26.
System Event Severity Parameters
Command
Result
Description
omconfig system 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
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
Enables notification for
critical events only.
Restrictive form of event
notification.
omconfig system events type=<
component
name
>
severity=none
Disables event
notification.
No event notification.
Table 4-27.
Web Server Configuration Parameters
name=value pair
Description
action=start
Starts the Web server.
action=stop
Stops the Web server.
action=restart
Restarts the Web server.