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.


Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs 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).



OSPF/6/OSPFV2_PEER_FLAPPING_SUPPRESS_STATUS: The status of peer flapping suppress is changed. (ProcessId=[ProcessId], AreaId=[AreaId], ifAreaId=[ifAreaId], ifIndex=[ifIndex], ifName=[ifName], SuppressStatus=[SuppressStatus], SuppressReason=[SuppressReason])


The status of OSPF neighbor relationship flapping suppression changed on the local interface.


Parameter Name Parameter Meaning


Process ID


Area ID


Area to which the interface belongs


Interface index


Interface index


Interface name


Suppression status are as follows:

  • 1: OSPF neighbor relationship flapping suppression is not started yet.
  • 2: OSPF neighbor relationship flapping suppression works in Hold-down mode.
  • 3: OSPF neighbor relationship flapping suppression works in Hold-max-cost mode.


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 OSPF process was reset.
  • 3: An interface was forced to exit from OSPF neighbor relationship flapping suppression using the reset ospf suppress-flapping peer command.
  • 4: The OSPF neighbor relationship flapped frequently.
  • 5: OSPF neighbor relationship flapping suppression exited from Hold-down mode and began to work in Hold-max-cost mode.

Possible Causes

OSPF neighbor relationship flapping suppression started on the local interface, or the interface exited from the suppression.


  1. Check whether frequent interface flapping 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 ospf process-id suppress-flapping peer [ interface-type interface-number ] [ notify-peer ] command to force the interface to exit from OSPF neighbor relationship flapping suppression.
  3. End.
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 170163

Downloads: 110

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next