MSTP/4/PROLGEXP:OID [oid] The MSTP process's instance's LOOP-Protection port did not receive BPDU packets in prescriptive time. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])
A port of MSTP process enabled with loop protection failed to receive BPDUs within a specified period, and was set to be in the Discarding state.
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.42.4.2.23 | Warning | communicationsAlarm(2) |
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
ProcessID |
Indicates the MSTP process ID |
InstanceID |
Indicates the instance ID. |
PortID1 |
Indicates ID 1 of the port in the MSTP process. |
PortID2 |
Indicates ID 2 of the port in the MSTP process. |
PortID3 |
Indicates ID 3 of the port in the MSTP process. |
PortID4 |
Indicates ID 4 of the port in the MSTP process. |
PortIDFlag |
Indicates the port flag. |
IfIndex |
Indicates the port index. |
PortState |
Indicates the port state. |
PortName |
Indicates the port name. |
1.
The peer switch did not send the BPDUs to the local switch within the specified period. The possible cause was that the spanning tree function was disabled on the peer switch.
2.
The links connected to the peer were congested. Check whether the traffic was normal.
If so, go to Step 3.
If the alarm is not cleared, go to Step 2.
If so, go to Step 4.
If not, go to Step 5.
If the alarm is cleared, go to Step 6.
If the alarm is not cleared, go to Step 2.
If the alarm is cleared, go to Step 6.
If not, go to Step 5.