bandwidth-degradation
Syntax
bandwidth-degradation {
action (log-only | restart | offline | restart-then-offline);
no-fabric-switchover;
percentage (1-99);
}
Hierarchy Level
[edit chassis fpc slot-numberfabric]
Description
Configure a FPC to take a specific action once bandwidth degradation reaches a certain percentage to avoid causing a null route in the chassis.
This configuration statement is mutually exclusive with the
offline-on-fabric-bandwidth-reduction statement. If both
statements are configured, the commit check fails and returns an error.
MX Series devices will count fabric planes in the offline or
fault state as part of the bandwidth degradation percentage
calculation. On PTX Series devices, when a fabric plane is offline it won't be
counted in the bandwidth degradation percentage calculation.
Options
log-only |
A message gets logged in the chassisd and message files when the fabric degradation threshold is reached. No other actions are taken. |
restart |
The FPC with a degraded fabric plane is restarted once the threshold is reached. |
offline |
The FPC with a degraded fabric plane is taken offline once the threshold is reached. The FPC requires manual intervention to be brought back online. This is the default action if no action attribute configured. |
restart-then-offline |
The FPC with a degraded fabric plane is restarted once the threshold is reached, and if fabric plane degradation is detected again within 10 minutes, the FPC is taken offline. The FPC requires manual intervention to be brought back online. |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 15.1.