Brocade Fabric OS Administrator's Guide Supporting Fabric OS v6.3.0 (53-1001336-02, November 2009)

438 Fabric OS Administrator’s Guide
53-1001336-02
Bottleneck detection
18
Virtual Fabrics considerations for bottleneck detection
If a port on which bottleneck detection is enabled is moved out of a logical switch, the bottleneck
detection configuration is retained by the logical switch. If the port is returned to the logical switch,
bottleneck detection is automatically enabled for the port with the same settings as before.
Access Gateway considerations for bottleneck detection
If you enable bottleneck detection on an F_Port to which an Access Gateway is attached, you do not
get information about which device is causing a bottleneck, because devices are not directly
connected to this port. To detect bottlenecks on an Access Gateway, enable bottleneck detection
on the Access Gateway to which the devices are actually connected.
Enabling bottleneck detection on a port
When you enable bottleneck detection, you also determine whether RASlog alerts are to be sent
when the bottleneck conditions at a port exceed a specified threshold.
1. Connect to the switch to which the target port belongs and log in as admin.
2. Enter the bottleneckmon
--enable command to enable bottleneck detection on an F_Port or
FL_Port.
bottleneckmon --enable
[ -alert ] [ -thresh threshold ] [ -time window ] [ -qtime quiet_time ]
[slot/]portlist [[slot/]portlist]...
If you do not specify the alert parameter, alerts are not sent, but you can view a history of
bottleneck conditions for the port as described in “Displaying history of bottlenecks on a port”
on page 440.
If you do not specify the alert parameter, the thresh, time, and qtime parameters are ignored.
NOTE
Best practice is to use the default values for the thresh (0.1), time (300), and qtime (300)
parameters. If you change the time parameter, you should use a setting that is 300 or higher.
Example of enabling bottleneck detection
(Preferred use case) The following example enables bottleneck detection on all F_ and FL_Ports in
the switch with RASlog alerts using default values for threshold and time.
switch:admin> bottleneckmon --enable -alert *
The following example enables bottleneck detection on ports 3–7 using default values for
threshold and time. No alerts will be delivered in bottleneck conditions, but you can view the
bottleneck history using the CLI.
switch:admin> bottleneckmon --enable 3-7
The following example enables bottleneck detection on port 4. A bottleneck condition is detected
when the port is bottlenecked 80% of the time over any period of 360 seconds, with a minimum of
300 seconds (default value) between alerts.
switch:admin> bottleneckmon --enable -alert -thresh 0.8 -time 360 4