Brocade Web Tools Administrator's Guide - Supporting Fabric OS v5.3.0 (53-1000435-01, June 2007)

48 Web Tools Administrator’s Guide

Publication Number: 53-1000435-01

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.