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 V200R005C10

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.4 hwMstpiPortRootGuarded

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.4 hwMstpiPortRootGuarded

Description

The root protection port received a superior message. (InstanceID=[InstanceID], PortIndex=[PortIndex], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port that has root protection enabled received BPDUs with higher priorities.

Attribute

Attribute Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiPortRootGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.4

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.

Parameters

Parameter Description
InstanceID Indicates the instance ID.
PortIndex Indicates the port ID.
IfIndex Indicates the interface index.
PortName Indicates the port name.
PwName Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1

hwMstpInstanceID

hwMstpInstanceID

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1

hwMstpInstanceID

hwMstpiPortIndex

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

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

Possible Causes

Cause 1: The port that has root protection enabled received BPDUs of higher priorities than that of the bridge.

Cause 2: The priorities of some switches changed on the network.

Procedure

  • Cause 1: The port that has root protection enabled received BPDUs of higher priorities than that of the bridge.
    1. Check whether the added physical link is necessary.

      • If the added physical link is necessary, go to Step 2.
      • If the added physical link is unnecessary, go to Step 3.

    2. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the interfaces are consistent with the STP calculation results.

      • If the interfaces are consistent with the STP calculation results, no action is required.
      • If the interfaces are inconsistent with the STP calculation results, go to Step 4.

    3. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether an interface is under the protection of the root bridge.

      • If an interface is under the protection of the root bridge, go to Step 5.
      • If no interface is under the protection of the root bridge, go to Step 6.

    5. Run the undo stp root-protection command in the interface view to delete the configuration of the protection under the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 6.
    6. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The priorities of some switches changed on the network.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the operation of changing the priority is correct.

      • If the operation is correct, go to Step 3.
      • If the operation is incorrect, go to Step 2.

    2. 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 or the undo stp [ instance instance-id ] root command to restore the default value of the priority of the local bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether an interface is under the protection of the root bridge.

      • If an interface is under the protection of the root bridge, go to Step 4.
      • If no interface is under the protection of the root bridge, go to Step 5.

    4. Run the undo stp root-protection command in the interface view to delete the configuration of the protection under the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17650

Downloads: 25

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