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

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

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

This bridge changed to be the root bridge.

After the network converged, the local bridge was elected as the new root bridge in the topology.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

newRoot

Trap OID

1.3.6.1.2.1.17.0.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Trap Buffer

NA

VB

VB OID

VB Name

VB Index

None

None

None

Impact on the System

The topology changes, and traffic may be lost.

Possible Causes

Cause 1: The local bridge was added into a new network topology.

Cause 2: The priority of the local bridge was increased.

Cause 3: The root bridge in the original topology was faulty.

Cause 4: The priority of the root bridge in the original topology was reduced.

Procedure

  • Cause 1: The local bridge was added into a new network topology.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the priority of the local bridge is the lowest on the network.

      • If the priority of the local bridge is the lowest on the network, go to Step 2.

      • If the priority of the local bridge is not the lowest on the network, go to Step 3.

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

      • If the local bridge is specified as the root bridge, no action is required.

      • If the local bridge is not specified as the root bridge, go to Step 3.

    3. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command to restore the default priority of the local bridge.
  • Cause 2: The priority of the local bridge was increased.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the priority of the local bridge is the lowest on the network.

      • If the priority of the local bridge is the lowest on the network, go to Step 2.

      • If the priority of the local bridge is not the lowest on the network, go to Step 3.

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

      • If the local bridge is specified as the root bridge, no action is required.

      • If the local bridge is not specified as the root bridge, go to Step 3.

    3. Run the stp [ instance instance-id ] priority priority command in the system view to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command to restore the default priority of the local bridge.
  • Cause 3: The root bridge in the original topology was faulty.
    1. Rectify the fault in the original network topology. Then, check whether the alarm is cleared.

      • If the alarm is cleared, no action is required.

      • If the alarm persists, go to Step 2.

    2. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 4: The priority of the root bridge in the original topology was reduced.
    1. Run the stp [ instance instance-id ] priority priority command or the stp [ instance instance-id ] 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 persists, go to Step 2.
    2. Collect trap, log, and configuration information, and contact technical support personnel.
Translation
Download
Updated: 2019-03-20

Document ID: EDOC1000166558

Views: 203147

Downloads: 115

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