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

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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.25 hwMstpProLoopbackDetected

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.25 hwMstpProLoopbackDetected

Description

MSTP/4/PROLBDETECTGED:OID [OID] The MSTP Process's Port has been set to discarding state because of detecting loopback. (ProcessID=[INTEGER], InstanceID=[INTEGER], PortID1=[INTEGER], PortID2=[INTEGER], PortID3=[INTEGER], PortID4=[INTEGER], PortIDFlag=[INTEGER], IfIndex=[INTEGER], PortState=[INTEGER], PortName=[STRING])

When port detected loopback, block the port and arise trap.

Attribute

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

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

ProcessID

Indicates the MSTP process ID

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the port index.

PortState

Indicates the port state.

PortName

Indicates the port name.

Impact on the System

After detecting a port blocked by local loopback, the system considers that a network storm occurs and blocks the local port to prevent the network storm from affecting services of the entire network. Services on the block port will be interrupted.

Possible Causes

When the STP port of the equipment receiving BPDU with the same designated bridge ID and designated port ID as this equipment and port, STP blocks this port and arises this trap for loopback detection will lead loop.

Procedure

  1. Check whether the port where the alarm is generated is configured with local loopback.

    • If so, go to Step 4.

    • If not, go to Step 2.

  2. Check whether there is a loop formed by a hub and devices, one of which is connected to the port.

    • If so, go to Step 5.

    • If not, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. Delete the local loopback configuration to solve the problem.
  5. Remove the self-loop network cable from the hub to solve the problem.
  6. End.

Related Information

None.

Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 119107

Downloads: 20

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