MSTP/5/LOST_ROOT_PRIMARY

• Cause 1: This bridge receives BPDU packets of higher priority.

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 [process ] [instance instance-id] [interface interface-type interface-number | slot slot-id | vsi vsi-name pw ] [brief] command to check whether STP information of each port is consistent with protocol calculation results.

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

3. Deploy the network topology correctly 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 bridge priorities of other bridge is modified to be higher than the root bridge priority.

1. Run the display stp [process ] [instance instance-id] [interface interface-type interface-number | slot slot-id | vsi vsi-name pw ] [brief] 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.