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

S9300, S9300E, and S9300X V200R010C00

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

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.9 hwOspfv3RestartStatusChange

Description

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 switch changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.9 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

RouterId

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

State

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

RestartInterval

Indicates the interval of GR.

RestartExitReason

Indicates the cause why the switch 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 switch 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.

Procedure

  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

None

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 189526

Downloads: 44

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