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.17 hwMstpProRootChanged

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.17 hwMstpProRootChanged

Description

MSTP/4/PRORTCHANGED:OID [oid] The root bridge of MSTP process has changed. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID=[INTEGER], PreviousRootBridgeID=[STRING], NewRootBridgeID=[STRING])

The root bridge changed. That is, a device became the root bridge or was not the root bridge any more.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.42.4.2.17 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ProcessID

Indicates the ID of an MSTP process.

InstanceID

Indicates the instance ID.

PortID

Indicates the port ID.

PreviousRootBridgeID

Indicates the ID of the previous root bridge.

NewRootBridgeID

Indicates the ID of the new root bridge.

Impact on the System

If the root bridge is not a core node, it will affect the performance of the entire network.

Possible Causes

1.

A new device was added, which had the optimal bridge ID.

2.

The priorities of the devices in the current network were modified.

3.

The domain configuration was modified.

Procedure

  1. View physical devices on the network to check whether new physical links enabled with STP are added.

    • If so, go to Step 2.

    • If not, go to Step 3.

  2. Check whether the added physical link is required.

    • If so, go to Step 4.

    • If not, go to Step 5.

  3. Run the display stp [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the priority vector of the instance is changed or the domain configuration is modified.

    • If so, go to Step 5.

    • 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 bridge ID is optimal on the entire network.

    • If so, go to Step 6.

    • If not, go to Step 7.

  5. Correctly configure the device according to the topology, and then check whether the alarm is cleared.

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

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

  6. Check whether the bridge ID of the added device is the optimal one on the entire network.

    • If so, go to Step 8.

    • If not, go to Step 5.

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

Related Information

None.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141873

Views: 111992

Downloads: 14

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