MSTP/2/hwMstpProRootLost_active

Procedure

• Cause 1: The bridge ID of new equipment is not optimal.

  1. Check whether the 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 on the newly added device 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 newly added device should be planned as the optimal ID on the entire network.

  • If the bridge ID should be planned as the optimal one on the entire network, no action is required.
  • If the bridge ID should not be planned as the optimal one on the entire network, go to Step 4.

  4. Perform configuration correctly based on the network topology and check whether the alarm is cleared. If the alarm persists, go to Step 5.

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

• Cause 2: Modify thr priority or domain configuration of the device in the original network.

  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 instance's priority vector or region configuration change is normal.

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

  2. Perform configuration correctly based on the network topology. If the alarm persists, go to Step 3.

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