Fabric OS Administrator's Guide v7.0.0 (53-1002148-02, June 2011)

304 Fabric OS Administrator’s Guide
53-1002148-02
Enabling bottleneck detection on a switch
13
• You have a latency bottleneck on an ISL that is not at the edge of the fabric.
The sub-second latency criterion parameters are always applicable. These parameters affect alerts
and, even if alerting is not enabled, they affect the history of bottleneck statistics.
The sub-second latency criterion parameters are the following, with default values in parentheses:
• -lsubsectimethresh (0.8) is similar to the -lthresh alerting parameter, except on a sub-second
level. The default value of 0.8 means that at least 80% of a second must be affected by latency
for the second to be marked as affected.
• -lsubsecsevthresh (50) specifies the factor by which throughput must drop in a second for that
second to be considered affected by latency. The default value of 50 means that the observed
throughput in a second must be no more than 1/50th the capacity of the port for that second
to be counted as an affected second. 1/50th of capacity means 2% of capacity, which means
98% loss of throughput.
Sub-second latency criterion parameters apply only to latency bottlenecks and not congestion
bottlenecks.
When you enable bottleneck detection, you can specify switch-wide sub-second latency criterion
parameters. After you enable bottleneck detection, you can change the sub-second latency
criterion parameters only on a per-port basis. You cannot change them on the entire switch, as you
can with alerting parameters, unless you disable and then re-enable bottleneck detection.
Changing the sub-second latency criterion parameters on specific ports causes an interruption in
the detection of bottlenecks on those ports, which means the history of bottlenecks is lost on these
ports. Also note the following behaviors if you change the sub-second latency criterion parameters:
• Traffic through these ports is not affected.
• History of latency bottlenecks and congestion bottlenecks is lost on these ports. Other ports
are not affected, however.
• The interruption occurs whether you set or clear per-port overrides on the sub-second latency
criterion parameters.
• Because of the interruption, you can never have an alert for a port such that the alert spans
periods of time with different sub-second latency criteria on that port.
Enabling bottleneck detection on a switch
Enabling bottleneck detection enables both latency and congestion detection.
Bottleneck detection is enabled on a switch basis. It is recommended that you enable bottleneck
detection on every switch in the fabric. If you later add additional switches, including logical
switches, to the fabric, be sure to enable bottleneck detection on those switches as well.
When you enable bottleneck detection on a switch, the settings are applied to all eligible ports on
that switch. If ineligible ports later become eligible or, in the case of a logical switch, if ports are
moved to the logical switch, bottleneck detection is automatically applied to those ports.
You can later override these settings on a port basis, as described in “Changing bottleneck
parameters” on page 306.
1. Connect to the switch and log in as admin.
2. Enter the bottleneckmon
--enable command to enable bottleneck detection on all eligible
ports on the switch.