Filter
Top Products
Fabric OS Administrator’s Guide 383
53-1002745-02
Setting bottleneck detection alerts
13
FIGURE 48 Affected seconds for bottleneck detection
The -time parameter specifies the time window. For this example, -time equals 12 seconds.
The -cthresh and -lthresh parameters specify the thresholds on number of affected seconds that
trigger alerts for congestion and latency bottlenecks, respectively. This example uses the default
values for these parameters, where -cthresh = 0.8 (80%) and -lthresh = 0.1 (10%).
For this time window, 50% of the seconds (6 out of 12 seconds) are affected by congestion. This is
below the threshold of 80%, so an alert would not be generated for a congestion bottleneck.
For the same time window, 25% of the seconds (3 out of 12 seconds) are affected by latency.
This exceeds the threshold of 10%, so an alert would be generated for a latency bottleneck.
Setting both a congestion alert and a latency alert
Entering the bottleneckmon --enable -alert command enables both alerts using the default alert
values.
Example of setting an alert for both congestion and latency
This example enables both alerts and shows their values.
switch:admin> bottleneckmon --enable -alert
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 - Yes
Latency threshold for alert - 0.100
Congestion threshold for alert - 0.800
Averaging time for alert - 300 seconds
Quiet time for alert - 300 seconds