
Fabric OS Administrator’s Guide
305
53-1002446-01
Changing bottleneck parameters
13
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.
The alerting parameters indicate whether alerts are sent, and the threshold, time, and quiet time
options.
For a trunk, you can change the parameters only on the master port.
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.
Enter the bottleneckmon
--
configclear command to remove any port-specific alerting and
sub-second latency criterion parameters and revert to the switch-wide parameters.
Example
The following example disables alerts on port 1, excludes ports 2, 3, and 4 from bottleneck
monitoring, and changes the alerting parameters on ports 2 and 3. The bottleneck
--
status
command shows the settings for these ports. Note that this example changes the alerting
parameters on ports 2 and 3, even though they are excluded from bottleneck detection.
switch:admin>
bottleneckmon --config -noalert 1
switch:admin>
bottleneckmon --exclude 2-4
switch:admin>
bottleneckmon --config -alert -lthresh .99 -cthresh .9 -time
4000 -qtime 600 2-3
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 alert parameters:
========================================
Port Alerts? LatencyThresh CongestionThresh Time(s) QTime(s)
================================================================
1 N
--
--
--
--
2 Y 0.990 0.900 4000 600
3 Y 0.990 0.900 4000 600
Excluded ports:
===============
Port
Summary of Contents for Fabric OS v7.0.1
Page 1: ...53 1002446 01 15 December 2011 Fabric OS Administrator s Guide Supporting Fabric OS v7 0 1 ...
Page 22: ...xxii Fabric OS Administrator s Guide 53 1002446 01 ...
Page 26: ...xxvi Fabric OS Administrator s Guide 53 1002446 01 ...
Page 30: ...xxx Fabric OS Administrator s Guide 53 1002446 01 ...
Page 38: ...xl Fabric OS Administrator s Guide 53 1002446 01 ...
Page 40: ...2 Fabric OS Administrator s Guide 53 1002446 01 ...
Page 214: ...176 Fabric OS Administrator s Guide 53 1002446 01 Management interface security 7 ...
Page 228: ...190 Fabric OS Administrator s Guide 53 1002446 01 Brocade configuration form 8 ...
Page 248: ...210 Fabric OS Administrator s Guide 53 1002446 01 Validating a firmware download 9 ...
Page 334: ...296 Fabric OS Administrator s Guide 53 1002446 01 Setting up TI over FCR sample procedure 12 ...
Page 360: ...322 Fabric OS Administrator s Guide 53 1002446 01 Encryption and compression example 14 ...
Page 404: ...366 Fabric OS Administrator s Guide 53 1002446 01 ...
Page 430: ...392 Fabric OS Administrator s Guide 53 1002446 01 Ports on Demand 18 ...
Page 502: ...464 Fabric OS Administrator s Guide 53 1002446 01 Buffer credit recovery 23 ...
Page 572: ...534 Fabric OS Administrator s Guide 53 1002446 01 Hexadecimal overview D ...
Page 584: ...546 Fabric OS Administrator s Guide 53 1002446 01 ...