Users Guide

Fabric OS Administrator’s Guide 435
53-1002920-02
Changing bottleneck detection parameters
15
Setting a latency alert only
Entering the bottleneckmon --enable -alert=latency command enables a congestion alert. This
example enables a latency alert and shows its values.
switch:admin> bottleneckmon --enable -alert=latency
switch:admin> bottleneckmon --status
Bottleneck detection - Enabled
==============================
Switch-wide sub-second latency bottleneck criterion:
====================================================
Time threshold - 0.800
Severity threshold - 50.000
Switch-wide alerting parameters:
================================
Alerts - Latency only
Latency threshold for alert - 0.100
Averaging time for alert - 300 seconds
Quiet time for alert - 300 seconds
Changing bottleneck detection parameters
When you enable bottleneck detection, you can configure switch-wide or port-specific alerting
parameters. The alerting parameters indicate whether alerts are sent, and the threshold, time, and
quiet-time options, as well as the sub-second latency criterion for ports.
After you enable bottleneck detection, you can change the alerting parameters for the entire switch
or only for individual ports. For example, you can change the latency threshold for only port 47
without affecting any other port. You can also change the parameters on ports that have been
excluded from bottleneck detection. For a trunk, you can change the parameters only on the
master port.
Alert-related parameters can only be specified with --config when -alert is specified.
This is because -noalert is assumed if -alert is not specified, and -noalert cancels all alert-related
parameters. As long as you want alerts, you must include the exact form of alert (-alert,
-alert=congestion, or -alert=latency) in every --config operation, even if alerts are already enabled.
The retention of settings applies only to the --config command, not to --enable.
An --enable operation behaves as if there is no pre-existing user configuration. If the --enable
command does not include -alert, but does specify alert-related parameters, that command will
fail.
NOTE
Entering the --config command changes only those settings specified in the command; all others are
left alone. The only exceptions are the -alert (restores alerts using recorded values) or -noalert
(disables all alerts) switches. If you want alerts, you must specify what you want as the -alert value
for every bottleneckmon - -config -alert command.
Use the following procedure to configure the bottleneck detection parameters.
1. Connect to the switch and log in using an account with admin permissions.
2. Enter the bottleneckmon --config command to set the alerting and sub-second latency
criterion parameters.