FSP_1.3.6.1.4.1.2011.5.25.183.1.22.59 hwStackPortErrorDown

Description

FSP/3/PORTERRDOWN: OID [OID] STACK port [STRING] trigger error down. (ErrorDownType=[STRING])

An error-down event occurred on a stack port.

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.183.1.22.59	Minor	communicationsAlarm (2)

Name	Meaning
OID	Indicates the MIB object ID of the alarm.
STACK port	Indicates the local port name.
Error down type	Indicates the error-down event type.

The stack may split because the port is unavailable.

Cause 1: The stack port receives CRC error packets.

Cause 2: The stack port frequently alternates between Up and Down states.

Cause 3: The rate of the optical module installed in the port is different from the rate of the port.

Run the display stack port brief command to check the stack port error-down reason.
- If the reason is Link-flapping trigger error down, rectify the fault according to An Ethernet Interface Frequently Alternates Between Up and Down States.
- If the reason is CRC trigger error down or Runts trigger error down, go to step 2.
- If the reason is Media mismatch trigger error down, go to step 4.
Replace the optical module and run the display interface interface-type interface-number command to check whether the number of CRC error packets received by the interface keeps increasing.
- If so, go to step 3.
- If not, the alarm handling ends.
Replace the fiber and run the display interface interface-type interface-number command to check whether the number of CRC error packets received by the interface keeps increasing.
- If so, collect alarm information and configuration information, and then contact technical support personnel.
- If not, the alarm handling ends.
Replace the optical module with the one matching the port rate. For details about the optical module matching the port, see service port stacking support in the "Stack Configuration Notes". After the corresponding optical module has been replaced, check whether this alarm is still displayed:
- If so, Collect alarm information and configuration information, and then contact technical support personnel.
- If not, the alarm handling ends.