Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 400)

Port Alerts? LatencyThresh CongestionThresh Time (s) QTime (s)
=================================================================================
46 N -- -- -- --
47 L 0.750 -- 250 150
Example 6: Clearing bottleneck detection override values from ports.
The following example removes any changed bottleneck detection parameter values from ports 46 and
47. The “Per-port overrides for alert parameters” section of the output is not displayed because there
are no per-port overrides.
switch123:admin> bottleneckmon --configclear 46-47
switch123: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.200
Congestion threshold for alert - 0.700
Averaging time for alert - 200 seconds
Quiet time for alert - 150 seconds
Adjusting the frequency of bottleneck alerts
Depending on the circumstances, a problematic switch or port may be triggering alerts more frequently
than desired. The -qtime parameter can be used to throttle alerts by specifying the minimum number
of seconds between consecutive alerts. Thresholds are configured separately for each type of
bottleneck and statistical data are collected independently for each condition. This parameter applies
individually to each type of bottleneck detection, so there can be one latency alert and one congestion
alert in one quiet time.
Example: Setting quiet time.
The following example sets a latency threshold of 0.8 for a time window of 30 seconds, and specifies
that an alert should be sent when 80 percent (0.8) of the one-second samples over any period of 30
seconds is affected by latency bottleneck conditions; the system then waits 60 seconds before issuing
the next alert (assuming that there is one).
switch:admin> bottleneckmon --enable -lthresh 0.8 -time 30 -qtime 60 -alert=latency
Logging frame timeouts due to bottlenecking
In Fabric OS 7.3.0 and later, when a syslog IP address is correctly configured and enabled and audit
logging is also enabled, an entry for each frame discard on supported devices is registered in the audit
log. These frame discards cannot generate a RASLog entry.
Support for frame discard logging is provided for the following devices:
• Brocade 6505, 6510, 6520, and DCX 8510-4 and DCX 8510-8 switches
• CR16-4, CR16-8, FC8-32E, FC8-48E, FC16-32, FC16-48, FC16-64 blades
The following steps illustrate how to configure frame discard logging for these devices.
1. Enter syslogdipAdd syslog_server_ip_address to specify the syslog server IP address.
2. Enter auditCfg --enable to enable audit logging.
Adjusting the frequency of bottleneck alerts
400 Fabric OS Administrators Guide
53-1003130-01