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.3 hwMstpiBridgeLostRootPrimary

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.3 hwMstpiBridgeLostRootPrimary

Description

The originaMSTP/2/ROOT:OID [OID]: This bridge is no longer the root bridge of the instance [instance-id].

l switch lost its status as a root bridge. Another switch with a higher priority in the network replaced it and became the root bridge.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.42.4.2.3 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

instance-id

Indicates the instance ID.

Impact on the System

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

Possible Causes

1.

A new link was added to the network topology, and the network topology changed. In addition, the newly-added device became the root bridge through the stp root primary command, with the MAC address smaller than that of the previous root bridge.

2.

The priorities of some switches 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 9.

    • 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 9.

    • 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 the alarm is cleared, go to Step 9.

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

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

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

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

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

Related Information

None.

Translation
Download
Updated: 2019-09-24

Document ID: EDOC1000141873

Views: 158915

Downloads: 15

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