MSTP/2/MSTPLOG_NEW_ROOT

Message

MSTP/2/MSTPLOG_NEW_ROOT: This bridge changed to be the root bridge. (ProcessID=[ProcessID], InstanceID=[InstanceID])

Description

After the network converged, the local bridge was elected as the new root bridge in the topology.

Parameters

Parameter Name	Parameter Meaning
ProcessID	Indicates the ID of an MSTP process.
InstanceID	Indicates the instance ID.

Possible Causes

Cause 1: The local bridge was added into a new network topology.

Cause 2: The priority of the local bridge was increased.

Cause 3: The root bridge in the original topology was faulty.

Cause 4: The priority of the root bridge in the original topology was reduced.

Procedure

Cause 1: The local bridge was added into a new network topology.

1. Run the display stp [ process ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the priority of the local bridge is the lowest on the network.

If the priority of the local bridge is the lowest on the network, go to Step 2.
If the priority of the local bridge is not the lowest on the network, go to Step 3.

2. Check whether the local bridge is specified as the root bridge in the Layer 2 network topology.

If the local bridge is specified as the root bridge, no action is required.
If the local bridge is not specified as the root bridge, go to Step 3.

3. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command to restore the default priority of the local bridge.

Cause 2: The priority of the local bridge was increased.

If the priority of the local bridge is the lowest on the network, go to Step 2.
If the priority of the local bridge is not the lowest on the network, go to Step 3.

2. Check whether the local bridge is specified as the root bridge in the Layer 2 network topology.

If the local bridge is specified as the root bridge, no action is required.
If the local bridge is not specified as the root bridge, go to Step 3.

3. Run the stp [ instance instance-id ] priority priority command in the system view to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command to restore the default priority of the local bridge.

Cause 3: The root bridge in the original topology was faulty.

1. Rectify the fault in the original network topology. Then, check whether the alarm is cleared.

If the alarm is cleared, no action is required.
If the alarm persists, go to Step 2.

2. Collect log information and configuration information, and then contact technical support personnel.

Cause 4: The priority of the root bridge in the original topology was reduced.

1. Run the stp [ instance instance-id ] priority priority command or the stp [ instance instance-id ] root primary command on the original root bridge to re-specify the original root bridge as the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 2.

2. Collect log information and configuration information, and then contact technical support personnel.