No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

S600-E V200R010C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21 hwMstpProNewPortRootGuarded

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21 hwMstpProNewPortRootGuarded

Description

MSTP/4/PRORGSUP:OID [oid] The MSTP process's instance's ROOT-Protection port received superior message. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

An MSTP process 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.21 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ProcessID

Indicates the MSTP process ID

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the port index.

PortState

Indicates the port state.

PortName

Indicates the port name.

Impact on the System

The actual network topology may not be the same as the expected one.

Possible Causes

1.

In the MSTP process, the port configured with the root protection function received BPDUs of a higher priority than that of the bridge.

2.

The priorities of some MSTP processes changed in the network.

Procedure

  1. 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.

  2. Check whether the added physical link is necessary.

    • If so, go to Step 3.

    • If not, go to Step 7.

  3. Run the display stp [ 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.

  4. Run the display stp [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the priority of a bridge is changed in the network topology.

    • If so, go to Step 5.

    • If not, go to Step 8.

  5. Check whether the operation of changing the priority is correct.

    • If so, go to Step 8.

    • If not, go to Step 6.

  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 so, go to Step 11.

    • If not, go to Step 8.

  7. Correctly deploy the network topology, and then check whether the alarm is cleared.

    • If so, go to Step 11.

    • If not, go to Step 8.

  8. Run the display stp [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether an interface is under the protection of the root bridge.

    • If so, go to Step 9.

    • If not, go to Step 10.

  9. Run the undo stp root-protection command in the interface view to disable the protection under the root bridge. Then, check whether the alarm is cleared.

    • If so, go to Step 11.

    • If not, go to Step 10.

  10. Collect alarm information and configuration information, and then contact technical support personnel.
  11. End.

Related Information

None.

Translation
Download
Updated: 2019-09-24

Document ID: EDOC1000141873

Views: 157603

Downloads: 15

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next