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.2.1.17.0.1 newRoot

MSTP_1.3.6.1.2.1.17.0.1 newRoot

Description

MSTP/1/NEWRT:OID [oid] This bridge has changed to be the root bridge.

After the network converges, the local bridge is elected as the new root bridge in the topology.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.17.0.1 Critical communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Impact on the System

The topology changes, and traffic may be lost.

Possible Causes

1. The local bridge is added into a new network topology.

2. The priority of the local bridge is increased.

3. The root bridge in the original topology is faulty.

4. The priority of the root bridge in the original topology is reduced.

Procedure

  1. Check whether the local bridge is added as a new node into a Layer 2 network topology.

    • If so, go to Step 2.

    • If not, go to Step 5.

  2. Run the display stp [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the priority of the local bridge is the lowest in the network. The lower the priority of the local bridge is, the more possibly the bridge becomes the root bridge.

    • If so, go to Step 3.

    • If not, go to Step 5.

  3. Check whether the local bridge is specified as the root bridge in the Layer 2 network topology.

    • If so, go to Step 10.

    • If not, go to Step 4.

  4. Run the stp priority command to re-set the priority of the local bridge as required. Alternatively, run the undo stp priority command to restore the default priority of the local bridge. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 10.

    • If the alarm is not cleared, go to Step 5.

  5. Check whether a fault occurs in the original network topology.

    • If so, go to Step 6.

    • If not, go to Step 7.

  6. Rectify the fault in the original network topology. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 10.

    • If the alarm is not cleared, go to Step 7.

  7. Check whether the priority of the root bridge in the original topology is lowered.

    • If so, go to Step 8.

    • If not, go to Step 9.

  8. Run the stp priority command or the stp root primary command on the original root bridge to re-specify the original root bridge as the root bridge. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 10.

    • If the alarm is not cleared, go to Step 9.

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

Related Information

None.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141873

Views: 111221

Downloads: 14

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