MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.17 hwMstpProRootChanged

Trap Buffer Description

The root bridge of MSTP process changed. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID=[PortID])

Specify that the root bridge has changed

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	PROROOT_CHANGED
Trap OID	1.3.6.1.4.1.2011.5.25.42.4.2.17
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	Indicates the ID of an MSTP process.
InstanceID	Indicates the instance ID.
PortID	Indicates the port ID.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.42.4.1.28.1.5	hwMstpProInstanceRootPort	hwMstpProID hwMstpInstanceID

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.28.1.5

hwMstpProInstanceRootPort

hwMstpProID

hwMstpInstanceID

Impact on the System

If the root bridge is not a core node, it will affect the performance of the entire network.

Possible Causes

Cause 1: A new device, which had the optimal bridge ID, was added. Cause 2: The priorities of the devices or the domain configuration on the current network were modified.

Procedure

Cause 1: A new device, which had the optimal bridge ID, was added.

1. Check whether the added physical link is required.

If the added physical link is necessary, go to Step 2.
If the added physical link is unnecessary, go to Step 3.

2. Run the display stp command to check whether the bridge ID is optimal on the entire network.

If the bridge ID is optimal on the entire network, go to Step 3.
If the bridge ID is not optimal on the entire network, go to Step 5.

3. Check whether the bridge ID of the added device should be the optimal one on the entire network.

If the bridge ID of the added device should be the optimal one on the entire network, the alarm will be cleared.
If the bridge ID of the added device should not be the optimal one on the entire network, go to Step 4.

4. Correctly configure the device according to the topology, and 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.

Cause 2: The priorities of the devices or the domain configuration on the current network were modified.

1. Run the display stp command to check whether the operation of changing the vectors of the instance or the domain configuration is correct. If the operation is incorrect, go to Step 2.

2. Correctly configure the device according to the topology, 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.