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

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

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).
OSPFV3_1. hwOspfv3PeerFlappingSuppressStatusChange

OSPFV3_1. hwOspfv3PeerFlappingSuppressStatusChange


OSPFV3/2/NBRDAMP_SUPPRESS: OID [oid] The status of peer flapping suppress is changed.(ProcessId=[integer], RouterId=[integer], AreaId=[integer], ifName=[octet], SuppressStatus=[integer], SuppressReason=[integer])

The status of OSPFv3 neighbor relationship flapping suppression changed.


Alarm ID Alarm Severity Alarm Type Major communicationsAlarm


Name Meaning


Indicates the MIB object ID of the alarm.


Process ID


Router ID


Area ID


Interface name


Suppression status


Suppression causes are as follows:

  • 1: The interval between two successive neighbor status changes from Full to a non-Full state was longer than the resume interval.
  • 2: A configuration was changed. For example, the OSPFv3 process was reset.
  • 3: An interface was forced to exit from OSPFv3 neighbor relationship flapping suppression using the reset ospfv3 suppress-flapping peer command.
  • 4: The OSPFv3 neighbor relationship flapped frequently.
  • 5: OSPFv3 neighbor relationship flapping suppression exited from Hold-down mode and began to work in Hold-max-cost mode.

Impact on the System

Services may be interrupted if OSPFv3 neighbor relationship flapping suppression persists on the interface.

Possible Causes

OSPFv3 neighbor relationship flapping suppression started, or the interface exited from the suppression.


  1. Run the display interface command multiple times to check whether interface flapping frequently occurs.

    • If frequent interface flapping occurs, this trap message is informational only and no action is required.
    • If no frequent interface flapping occurs, go to Step 2.

  2. Run the reset ospfv3 process-id suppress-flapping peer [ interface-type interface-number ] [ notify-peer ] command to force the interface to exit from OSPFv3 neighbor relationship flapping suppression.
  3. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 103623

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next