Changing bottleneck detection parameters
When you enable bottleneck detection, you can configure switch-wide or port-specific alerting parameters. The alerting parameters indicate whether alerts are sent, and the threshold, time, and quiet-time options, as well as the sub-second latency criterion for ports.
Logging frame timeouts due to bottlenecking
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.
Excluding a port from bottleneck detection
When you exclude a port from bottleneck detection, no data is collected from the port and no alerts are generated for the port. All statistics history for the port is discarded. Alerting parameters for the port are preserved, so if you later include the port for bottleneck detection, the alerting parameters are restored. Per-port exclusions may be needed if, for example, a long-distance port is known to be a bottleneck because of credit insufficiency. In general, however, per-port exclusions are not recommended. For trunking, if you exclude a slave port from bottleneck detection, the exclusion has no effect as long as the port is a trunk slave. The exclusion takes effect only if the port becomes a trunk master or leaves the trunk.
Disabling bottleneck detection on a switch
When you disable bottleneck detection on a switch, all bottleneck configuration details are discarded, including the list of excluded ports and non-default values of alerting parameters.