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


To have a better experience, please upgrade your IE browser.


Alarm Handling

S9300, S9300E, and S9300X 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. hwMstpProNewPortLoopGuarded

MSTP_1. hwMstpProNewPortLoopGuarded


MSTP/4/PROLGEXP:OID [oid] The MSTP process's instance's LOOP-Protection port did not receive BPDU packets in prescriptive time. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

A port of MSTP process enabled with loop protection failed to receive BPDUs within a specified period, and was set to be in the Discarding state.


Alarm ID Alarm Severity Alarm Type Warning communicationsAlarm(2)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the MSTP process ID


Indicates the instance ID.


Indicates ID 1 of the port in the MSTP process.


Indicates ID 2 of the port in the MSTP process.


Indicates ID 3 of the port in the MSTP process.


Indicates ID 4 of the port in the MSTP process.


Indicates the port flag.


Indicates the port index.


Indicates the port state.


Indicates the port name.

Impact on the System

The interface will not forward data.

Possible Causes


The peer switch did not send the BPDUs to the local switch within the specified period. The possible cause was that the spanning tree function was disabled on the peer switch.


The links connected to the peer were congested. Check whether the traffic was normal.


  1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether STP is disabled on the interfaces that are directly connected.

    • If so, go to Step 3.

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

  2. Run the display this interface command in the interface view to check the percentage of the rate at which the interface receives packets to the total bandwidth and then determine whether congestion occurs.

    • If so, go to Step 4.

    • If not, go to Step 5.

  3. Run the stp enable command in the interface view to enable STP. Then, check whether the alarm is cleared.

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

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

  4. Repair the physical link and then check whether the alarm is cleared.

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

    • If not, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information


Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 184553

Downloads: 44

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