In a stack system, if a stack port continuously receives CRC error packets or flaps between Up and Down states, the corresponding stack link cannot forward traffic normally, thereby affecting network services. The stack port error-down function can shut down a stack port and switch traffic to other stack links if the rate of received CRC error packets or the number of Up/Down transitions on the stack port reaches the specified threshold. This reduces the impact of a stack port error-down event on network services. Additionally, the system generates stack port error-down alarms to help in fault location.
When one end is a stack port and the other end is a service port, the system does not set the stack port to error-down state or generate an error-down alarm even if this stack port continuously receives CRC error packets.
By default, the stack port error-down function is enabled.
Run the stack port { crc | link-flap } trigger { threshold threshold | interval interval } * command to set the stack port error-down alarm threshold and check interval.
By default, the stack port error-down alarm threshold is 10 times per minute, and the check interval is 3 minutes. That is, the system will set a stack port to error-down state and generate an error-down alarm in the following condition: The stack port receives 10 CRC error packets per minute or alternates between Up and Down states 10 times per minute, and this condition lasts for 3 minutes.
Run the stack port { crc | link-flap } trigger error-down auto-recovery-interval auto-recovery-interval command to set the stack port error-down alarm clearance interval.
By default, the alarm clearance interval is 0, which means that a stack port error-down alarm will not be cleared automatically after it is printed.