MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.4 hwMstpiPortRootGuarded
Description
MSTP/2/RGSUP:OID [oid] The ROOT-Protection port received superior message. (InstanceID=[INTEGER], PortInstanceID=[INTEGER], PortID=[INTEGER], IfIndex=[INTEGER], PortName=[STRING])
A switch with a higher priority outside the protection range of the root bridge attempted to become the root bridge.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.42.4.2.4 | Major | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
InstanceID |
Indicates the instance ID. |
PortInstanceID |
Indicates the instance ID of the port. |
PortID |
Indicates the port ID. |
IfIndex |
Indicates the interface index. |
PortName |
Indicates the port name. |
Possible Causes
Cause 1:
The port enabled with the root protection function received BPDUs of a higher priority than that of the bridge.
2:
The priority of some switch changed in the network.
Procedure
- View physical devices on the network to check whether new
physical connections enabled with STP are added.
If so, go to Step 2.
If not, go to Step 4.
- Check whether the added physical link is necessary.
If so, go to Step 3.
If not, go to Step 7.
- Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether
the interfaces are consistent with the STP calculation results.
If so, go to Step 11.
If not, go to Step 4.
- Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether
the priority of a bridge is change in the network topology.
If so, go to Step 5.
If not, go to Step 8.
- Check whether the operation of changing the priority is
correct.
If so, go to Step 8.
If not, go to Step 6.
- Run the stp priority command to re-set the priority of the
local bridge as required. Alternatively, run the undo stp priority command or the undo stp root command to restore the default value of
the priority of the local bridge. Then, check whether the alarm is
cleared.
If the alarm is cleared, go to Step 11.
If the alarm is not cleared, go to Step 8.
- Correctly deploy the network topology, and then check whether
the alarm is cleared.
If the alarm is cleared, go to Step 11.
If the alarm is not cleared, go to Step 8.
- Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether
an interface under the protection of the root bridge.
If so, go to Step 9.
If not, go to Step 10.
- Run the undo stp root-protection command in the
interface view to delete the configuration of the protection under
the root bridge. Then, check whether the alarm is cleared.
If the alarm is cleared, go to Step 11.
If the alarm is not cleared, go to Step 10.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
Previous
