MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21 hwMstpProNewPortRootGuarded

Trap Buffer Description

The root protection port of the instance of the MSTP process received a superior message. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

A designated port receives BPDUs with priorities higher than that of the local bridge when root bridge protection is enabled in the MSTP process.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	PROPORT_ROOT_GUARDED
Trap OID	1.3.6.1.4.1.2011.5.25.42.4.2.21
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
ProcessID	MSTP process ID.
InstanceID	Instance ID.
PortID1	Port ID 1 in the MSTP process.
PortID2	Port ID 2 in the MSTP process.
PortID3	Port ID 3 in the MSTP process.
PortID4	Port ID 4 in the MSTP process.
PortIDFlag	Port flag.
PortState	Port state.
IfIndex	Port index.
PortName	Port name.
PwName	PW name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1	hwMstpProNewPortState	hwMstpProID hwMstpInstanceID hwMstpPortId1 hwMstpPortId2 hwMstpPortId3 hwMstpPortId4 hwMstpPortIdFlag
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	-

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProID

hwMstpInstanceID

hwMstpPortId1

hwMstpPortId2

hwMstpPortId3

hwMstpPortId4

hwMstpPortIdFlag

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 actual network topology may not be the same as the expected one.

Possible Causes

Cause 1: The designated port configured with root protection receives BPDUs with higher priorities than that of the local bridge. Cause 2: The priority of a device in the network topology changed.

Procedure

Cause 1: The port enabled with the root protection function received BPDUs of a higher priority than that of the bridge.

1. Check whether the added physical link is the required one.

If the added physical link is the required one, go to Step 2.
If the added physical link is not the required one, go to Step 3.

2. Run the display stp command to check whether the STP information of each interface is consistent with STP calculation results.

If the STP information is consistent with STP calculation results, no action is required.
If the STP information is inconsistent with STP calculation results, go to Step 4.

3. Deploy the network topology correctly, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.

4. Run the display stp command to check whether a port is planned as a root protection port.

If a port is planned as a root protection port, go to Step 5.
If no port is planned as a root protection port, go to Step 6.

5. Run the undo stp root-protection command in the interface view to disable root protection. Then, check whether the alarm is cleared. If the alarm persists, go to Step 6.

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

Cause 2: The priority of some switch changed in the network.

1. Run the display stp command to check whether the priority change operation on the network topology is normal.

If the operation is normal, go to Step 3.
If the operation is abnormal, go to Step 2.

2. Run the stp [ instance ] priority command to re-set the priority of the local bridge as required. Alternatively, run the undo stp [ instance ] priority command or the undo stp [ instance ] root command to restore the default priority of the local bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Run the display stp command to check whether a port is planned as a root protection port.

If a port is planned as a root protection port, go to Step 4.
If no port is planned as a root protection port, go to Step 5.

4. Run the undo stp root-protection command in the interface view to disable root protection. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.

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