MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.6 hwMstpiPortLoopGuarded

Trap Buffer Description

The loop protection port did not receive BPDU packets within prescriptive time. (InstanceID=[InstanceID], PortIndex=[PortIndex], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

Specify that the root port has not received any BPDU packets for a long time when loop protection is enabled

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	PORT_LOOP_GUARDED
Trap OID	1.3.6.1.4.1.2011.5.25.42.4.2.6
MIB	HUAWEI-MSTP-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
InstanceID	Indicates the instance ID.
PortIndex	MSTP port index.
IfIndex	Indicates the interface index.
PortName	Indicates the port name.
PwName	Indicates the PW name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1	hwMstpInstanceID	hwMstpInstanceID
1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1	hwMstpiPortIndex	hwMstpInstanceID hwMstpiPortIndex
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex
1.3.6.1.4.1.2011.5.25.42.4.1.33	hwMstpPwName	-

Impact on the System

The interface will not forward data.

Possible Causes

Cause 1: The spanning tree function was disabled on the peer device. Cause 2: The links connected to the peer were congested.

Procedure

Cause 1: The spanning tree function was disabled on the peer device.

1. Run the display stp [ process ] [ instance ] [ interface | slot | vsi pw ] [ brief ] command to check whether STP is disabled on the interfaces that are directly connected.

If STP is disabled on the interfaces that are directly connected, go to Step 2.
If STP is enabled on the interfaces that are directly connected, go to Step 3.

2. Run the stp enable command in the interface view to enable STP. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.

Cause 2: The links connected to the peer were congested.

1. Check whether the link between the local device and the neighbor device is congested.

If the link is congested, go to Step 2.
If the link is not congested, go to Step 3.

2. Repair the physical link and then check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.