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. hwOspfv3RestartStatusChange

OSPFV3_1. hwOspfv3RestartStatusChange


OSPFV3/3/RESTARTSTATUSCHANGE:OID [oid] The graceful restart status of the router has changed. (RouterId=[gauge], State=[integer], RestartInterval=[integer], RestartExitReason=[integer])

The GR status of the router changed.


Alarm ID Alarm Severity Alarm Type Minor processingErrorAlarm(4)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the Router-ID of the local node. The value is a decimal integer.


Indicates the restart status.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full


Indicates the interval of GR.


Indicates the cause why the router exits from the GR.
  • 1: None
  • 2: In progress
  • 3: Completed
  • 4: Time out
  • 5: Topology change

Impact on the System

This trap indicates that a router enters the GR state or exists from the GR state. GR failure will affect the normal forwarding of routes.

Possible Causes

1. OSPFv3 exited from GR.

2. The GR period exceeded the set value.

3. OSPFv3 GR is reset.


  1. Run the display ospfv3 graceful-restart-information command to check the cause of becoming the GR and the current GR status.
  2. Perform the following operations as required:

    • If the active/standby switchover is performed manually or the OSPFv3 process is restarted in GR mode, go to Step 4.

    • If this trap is generated without any manual operation, go to Step 3.

    • If the reset ospfv3 graceful-restart command is executed, go to Step 4.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 100487

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next