Filter
Top Products
382 Fabric OS Administrator’s Guide
53-1002745-02
Setting bottleneck detection alerts
13
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
Example of status output showing that only a congestion alert at the switch level has been set
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 - Congestion only
Congestion threshold for alert - 0.800
Averaging time for alert - 300 seconds
Quiet time for alert - 300 seconds
Per-port overrides for alert parameters:
========================================
Port Alerts? LatencyThresh CongestionThresh Time (s) QTime(s)
================================================================================
1 Y 0.100 0.800 300 300
2 C -- 0.800 600 600
3 L 0.100 -- 300 300
4N-- -- -- --
NOTE
If there are no per-port overrides, then that section is not displayed.
Setting bottleneck detection alerts
You can configure Fabric OS to log per-port alerts based on the latency and congestion history of
the port. Alerts are generated based on the number of affected seconds over a specified period of
time. If the number of affected seconds is higher than the threshold, an alert is generated.
This evaluation is done independently for latency and congestion.
The bottleneckmon -alert parameters described below determine whether an alert is generated
and what for.
For example, Figure 48 shows an interval of 12 seconds, in which 6 seconds are affected by a
congestion bottleneck and 3 seconds are affected by a latency bottleneck.