MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.28 hwMstpProRootLost
Description
MSTP/4/PROROOTLOST: OID [OID] The bridge loses the position of root bridge.(ProcessID=[ProcessID], InstanceID=[InstanceID])
The device in an MSTP process lost its root bridge role.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.42.4.2.28 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
ProcessID |
Process ID. |
InstanceID |
Instance ID. |
Impact on the System
The network topology will be changed, and traffic will be forwarded through a new path.
Possible Causes
After a root bridge was specified using the stp [ instance instance-id ] root primary command in the MSTP process or system view, a device whose priority changed to 0 became the new root bridge.
Procedure
- View physical devices on the network and check whether
a new STP-enabled physical link is added to the topology.
If such a link is added, go to Step 2.
If no such link is added, go to Step 5.
- Check whether the added physical link is the required one.
If the link is required, go to Step 3.
If the link is not required, go to Step 9.
- Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type
interface-number | slot slot-id ] [ brief ]
command to check whether the added device is the root bridge.
If the device is the root bridge, go to Step 4.
If the device is not the root bridge, go to Step 5.
- Check whether the priority of the added device is proper.
If the priority is proper, go to Step 8.
If the priority is improper, go to Step 9.
- Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type
interface-number | slot slot-id ] [ brief ]
command to check whether a device's priority is changed in the network
topology.
If a device's priority is changed, go to Step 6.
If no device's priority is changed, go to Step 10.
- Check whether the priority modification is proper.
If the modification is proper, go to Step 8.
If the modification is improper, go to Step 7.
- Run the stp [ instance instance-id ] priority priority command in the system view or MSTP process view of the device whose
priority has been changed to re-set its priority as needed. Alternatively,
run the undo stp [ instance instance-id ] priority or undo
stp [ instance instance-id ] root command to restore the default
priority. Check whether the alarm is cleared.
If the alarm is cleared, go to Step 11.
If the alarm persists, go to Step 9.
- Run the undo stp [ instance instance-id ] root command in the system view or
MSTP process view of the device that has lost the root bridge role.
Then check whether the alarm is cleared.
If the alarm is cleared, go to Step 11.
If the alarm persists, go to Step 10.
- Correct the network topology and check whether the alarm
is cleared.
If the alarm is cleared, go to Step 11.
If the alarm persists, go to Step 10.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.