MSTP/4/MSTPLOG_PROROOT_CHANGED

Message

MSTP/4/MSTPLOG_PROROOT_CHANGED: The root bridge of MSTP process changed. (ProcessID=[ProcessID], InstanceID=[InstanceID], RootPortName=[PortName], PreviousRootBridgeID=[PreRootBridgeID], NewRootBridgeID=[NewRootBridgeID], RootPwName=[PwName], PreHello=[PreHello], PreMessageAge=[PreMessAge], PreFwdly=[PreFwdly], PreRemainingHops=[PreMessHop], NewHello=[NewHello], NewMessageAge=[NewMessAge], NewFwdly=[NewFwdly], NewRemainingHops=[NewMessHop], Tag=[Tag])

Description

The root bridge in the MSTP process changed.

Parameters

Parameter Name	Parameter Meaning
ProcessID	Indicates the ID of an MSTP process.
InstanceID	Indicates the instance ID.
PortName	Indicates the name of the root port.
PreRootBridgeID	Indicates the bridge ID of the previous root bridge.
NewRootBridgeID	Indicates the ID of the new root bridge.
PwName	Indicates the PW name as the root port.
PreHello	Indicates the time of the Hello Timer before the root bridge changed.
PreMessAge	Indicates the aging time of the information before the root bridge changed.
PreFwdly	Indicates the forwarding delay timer before the root bridge changed.
PreMessHop	Indicates the number of hops of the spanning tree before the root bridge changed.
NewHello	Indicates the time of the Hello Timer after the root bridge changed.
NewMessAge	Indicates the aging time of the information after the root bridge changed.
NewFwdly	Indicates the forwarding delay timer after the root bridge changed.
NewMessHop	Indicates the number of hops of the spanning tree after the root bridge changed.
Tag	tag in an MSTP packet.

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 [ process ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] 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 log 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 [ process ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] 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 log information and configuration information, and then contact technical support personnel.