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

306 Fabric OS Administrator’s Guide
53-1002148-02
Changing bottleneck parameters
13
• Switch-wide parameters
• Per-port overrides, if any
• Excluded ports
Example
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
Per-port overrides for sub-second latency bottleneck criterion:
===============================================================
Slot Port TimeThresh SevThresh
=========================================
0 3 0.500 100.000
0 4 0.600 50.000
0 5 0.700 20.000
Per-port overrides for alert parameters:
========================================
Slot Port Alerts? LatencyThresh CongestionThresh Time (s)
QTime (s)
=============================================================================
=============
0 1 Y 0.990 0.900 3000 600
0 2 Y 0.990 0.900 4000 600
0 3 Y 0.990 0.900 4000 600
Excluded ports:
===============
Slot Port
============
0 2
0 3
0 4
Changing bottleneck parameters
When you enable bottleneck detection, you can configure switch-wide alerting and sub-second
latency criterion parameters that apply to every port on the switch. After you enable bottleneck
detection, you can change the alerting parameters on the entire switch or on individual ports. You
can change the sub-second latency criterion parameters on individual ports only. You can also
change the parameters on ports that have been excluded from bottleneck detection.