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.2 topologyChange

MSTP_1.3.6.1.2.1.17.0.2 topologyChange

Description

MSTP/1/TOPOC:OID [OID] Bridge topology change.

The topology calculated by the STP changes.

NOTE:

A topologyChange alarm is triggered if the status of an STP interface other than an edge interface changes from Blocking to Forwarding.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.17.0.2 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 network topology changes because a new link is added into the network topology.

2. The network topology changes because interfaces go Up or Down.

3. The network topology changes because a device changed the priority.

4. The network topology changes because a device changed the priority, or an interface changed its priority or cost, which caused a change in the blocked interface.

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 the required one.

    • If so, go to Step 3.

    • If not, go to Step 8.

  3. Run the display stp [ instance instance-id ] [ interface { interface-type interface-number [ to interface-number ] }&<1-10> ] [ brief ] command to check whether the interfaces are consistent with the STP calculation results.

    • If so, go to Step 10.

    • If not, go to Step 4.

  4. Check whether the interfaces enabled with the STP protocol go Up or Down in the network topology.

    • If so, go to Step 5.

    • If not, go to Step 6.

  5. Run the undo shutdown command in the interface view to check whether the alarm is cleared.

    • If so, go to Step 10.

    • If not, go to Step 6.

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

    • If so, go to Step 7.

    • If not, go to Step 9.

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

  8. Correctly deploy the network topology, and 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 3.

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

Related Information

None.

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000141873

Views: 148648

Downloads: 14

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