Disabling bottleneck detection, Thresholds and event notification, Thresholds and event notification 7 – Brocade Network Advisor SAN User Manual v12.3.0 User Manual

Page 1159

Advertising
background image

Brocade Network Advisor SAN User Manual

1107

53-1003154-01

Thresholds and event notification

28

5. Select a device in the table, then click the Show affected VM button to identify virtual

machines with the same target ports aa the device port attached to the bottlenecked F_Port or
FL_Port.

Disabling bottleneck detection

Use this procedure to exclude specific ports from bottleneck detection or to disable bottleneck
detection on entire switches or fabrics.

It is not recommended to disable bottleneck detection on a port except under special
circumstances. For example, if a long-distance port is known to be a bottleneck because of credit
insufficiency, you could disable bottleneck detection on that port.

1. Select Monitor > Performance > Bottlenecks.

The Bottlenecks dialog box displays.

2. Select Disable.

3. Select one or more fabrics, switches, or ports from the Products/Ports list.

You can select fabrics or switches or ports, but you cannot select a mix of fabrics, switches,
and ports.

4. Click the right arrow to apply the settings in the Bottleneck Detection pane to the selected

elements in the Products/Ports list.

5. Click OK or Apply to save your changes.

Thresholds and event notification

Performance monitoring allows you to apply thresholds and event notification to real-time
performance data. A performance monitor process (thread) monitors the performance data against
the threshold setting for each port and issues an appropriate alert to notify you when the threshold
is exceeded. For information about configuring event notification, refer to

“Event notification”

on

page 1256.

NOTE

It is not necessary to configure event notification to receive events in the Master Log. If the threshold
is exceeded for a threshold, an event is automatically generated and displayed in the Master Log.

NOTE

If you set the threshold for a particular critical event to 100 percent, by the time you are notified, it
may be too late to prevent a failure. However, when you set the threshold to 85 percent, for example,
you may be able to prevent the failure from occurring.

Example

The values at 1 second, 3 seconds, and 5 seconds generate events because they exceed
boundaries. The value at 2 seconds does not generate an event because, although it crosses the
boundary, it remains in the buffer zone. The value at 6 seconds generates an event because it
crosses the lower boundary and returns to a value beyond the buffer zone. The example is shown
as a graph in

Figure 484

on page 1108.

Advertising