MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.20 hwMstpProNewBridgeLostRootPrimary

Trap Buffer Description

MSTP process is no longer the root bridge of the instance. (ProcessID=[ProcessID],InstanceID=[InstanceID],proInstRootType=[proInstRootType])

The device in the MSTP process was no longer the root bridge.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	PROLOST_ROOT_PRIMARY
Trap OID	1.3.6.1.4.1.2011.5.25.42.4.2.20
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.
proInstRootType	Root type.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.42.4.1.28.1.6	hwMstpProInstanceRootType	hwMstpProID hwMstpInstanceID

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.28.1.6

hwMstpProInstanceRootType

hwMstpProID

hwMstpInstanceID

Impact on the System

The actual network topology may not be the same as the expected one.

Possible Causes

Cause 1: A new link was added to the network topology, and the network topology changed. Cause 2: The priorities of some devices changed on the network.

Procedure

Cause 1: A new link was added to the network topology, and the network topology changed.

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

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

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

If yes, no action is required.
If not, go to Step 4.

3. Correctly deploy the network topology and check whether the alarm is cleared.If the alarm persists, go to Step 4.

4. Collect alarm and configuration information, and contact technical support personnel.

Cause 2: The priorities of some switches 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, no action is required.
If the operation is abnormal, go to Step 2.

2. Run the stp [instance instance-id] priority priority command in the system view to reconfigure the priority of the local bridge as required. Alternatively, run the undo stp [instance instance-id] priority or undo stp [instance instance-id] root command to restore the default bridge priority. Check whether the alarm is cleared. If the alarm persists, go to Step 3.

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