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, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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).
L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock

Description

L2IFPPI/4/MFLPIFBLOCK:OID [OID] Loop exists in vlan [INTEGER], Interface [OCTET] blocked, block-time is [GAUGE] for [OCTET], Mac Address is [OCTET].

MAC address flapping occurs and the interface is blocked.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.1 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid

Indicates the MIB object ID of the alarm.

INTEGER Indicates the VLAN ID.
OCTET1 Indicates the blocked interface name.
GAUGE Indicates the time when the interface is blocked.
OCTET3 Indicates the flapped MAC address.
OCTET2 Indicates the cause why the interface is blocked.

Impact on the System

Traffic cannot be received normally.

Possible Causes

Cause 1:

The interfaces where loops occur are added to the same VLAN.

Cause 2:

Cables are connected incorrectly.

Cause 3:

Loop detection and STP are enabled to remove loops on the network.

Procedure

  1. Check that cables are connected correctly. Then check whether the alarm is still reported.

    • If yes, go to step 2.
    • If not, go to step 9.

  2. Check whether the two interfaces that learn the same MAC address can be added to different VLANs according to the networking.

    • If yes, go to step 3.
    • If not, go to step 4.

  3. Modify the configuration and add the two interfaces that learn the same MAC address to different VLANs. Then check whether the alarm is still reported.

    • If yes, go to step 4.
    • If not, go to step 9.

  4. Check whether the ring network meets requirements.

    • If yes, go to step 7.
    • If not, go to step 5.

  5. Do as follows to remove loops:

    (1) Run the display loop-detect eth-loop [ vlan vlan-id ] command to view the blocked interface.

    (2) Run the display mac-address vlan vlan-id command to search an interface that learns the MAC address.

    (3) Shut down one interface according to the networking.

    (4) Run the reset loop-detect eth-loop vlan vlan-id { all | interface interface-type interface-number | mac-address mac-address } command to delete the blocked interface.

  6. Check whether the traffic transmission is normal.

    • If yes, go to step 9.
    • If not, go to step 7.

  7. Disable loop detection and enable STP. Then check whether the alarm is still reported.

    • If yes, go to step 8.
    • If not, go to step 9.

  8. Collect alarm information and configuration information, and then contact technical support personnel.
  9. End.
Translation
Download
Updated: 2019-05-07

Document ID: EDOC1100034065

Views: 131651

Downloads: 40

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