HP StorageWorks 2/32 Brocade Web Tools Administrator's Guide - Supporting Fabr - Page 70

Monitoring events, Icon and Level, Description

Page 70 highlights

3 Monitoring events To initiate a CP failover 1. Open the High Availability window as described in "Launching the High Availability Module" on page 45. 2. Verify that the HA Status field displays Non-Disruptive Failover Ready or Disruptive Failover Ready. 3. Click Initiate Failover. The Warning dialog box displays. 4. Click Yes to initiate a nondisruptive failover. 5. When prompted, close the Web Tools Switch Explorer window and all associated windows, and relaunch Web Tools. Monitoring events Web Tools displays fabric-wide and switch-wide events. Event information includes sortable fields for the following: • Switch name • Message number • Time stamp • Indication of whether the event is from a logical switch or a chassis • The number of successive events of the same kind • Severity level • Unique message identifier (in the form moduleID-messageType) • Detailed error message for root cause analysis There are four message severity levels: Critical, Error, Warning, and Info. Table 4 lists the event message severity levels displayed on the Switch Events tab and in the Fabric Events window, and explains what qualifies event messages to be certain levels. On the Switch Events tab and in the Fabric Events window, you can click the Filter button to launch the Filter Events dialog box. The Filter Events dialog box allows you to define which events should be displayed on the Switch Events tab or in the Fabric Events window. For more information on filtering events, see "Filtering Fabric and Switch Events" on page 51. TABLE 4 Event Severity Levels Icon and Level Description Critical Critical-level messages indicate that the software has detected serious problems that will eventually cause a partial or complete failure of a subsystem if not corrected immediately; for example, a power supply failure or rise in temperature must receive immediate attention. Error Error-level messages represent an error condition that does not impact overall system functionality significantly. For example, error-level messages might indicate timeouts on certain operations, failures of certain operations after retries, invalid parameters, or failure to perform a requested operation. 48 Web Tools Administrator's Guide Publication Number: 53-1000435-01

  • 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
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266

48
Web Tools Administrator’s Guide
Publication Number: 53-1000435-01
Monitoring events
3
To initiate a CP failover
1.
Open the High Availability window as described in
“Launching the High Availability Module”
on
page 45.
2.
Verify that the HA Status field displays
Non-Disruptive Failover Ready
or
Disruptive Failover
Ready
.
3.
Click
Initiate Failover
.
The Warning dialog box displays.
4.
Click
Yes
to initiate a nondisruptive failover.
5.
When prompted, close the Web Tools Switch Explorer window and all associated windows, and
relaunch Web Tools.
Monitoring events
Web Tools displays fabric-wide and switch-wide events. Event information includes sortable fields
for the following:
Switch name
Message number
Time stamp
Indication of whether the event is from a logical switch or a chassis
The number of successive events of the same kind
Severity level
Unique message identifier (in the form
moduleID
-
messageType
)
Detailed error message for root cause analysis
There are four message severity levels: Critical, Error, Warning, and Info.
Table 4
lists the event
message severity levels displayed on the Switch Events tab and in the Fabric Events window, and
explains what qualifies event messages to be certain levels.
On the Switch Events tab and in the Fabric Events window, you can click the
Filter
button to launch
the Filter Events dialog box. The Filter Events dialog box allows you to define which events should
be displayed on the Switch Events tab or in the Fabric Events window. For more information on
filtering events, see
“Filtering Fabric and Switch Events”
on page 51.
TABLE 4
Event Severity Levels
Icon and Level
Description
Critical
Critical-level messages indicate that the software has detected serious
problems that will eventually cause a partial or complete failure of a subsystem
if not corrected immediately; for example, a power supply failure or rise in
temperature must receive immediate attention.
Error
Error-level messages represent an error condition that does not impact overall
system functionality significantly. For example, error-level messages might
indicate timeouts on certain operations, failures of certain operations after
retries, invalid parameters, or failure to perform a requested operation.