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

CloudEngine 12800 and 12800E V200R003C00

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

OSPFV3_1. ospfv3NbrStateChange


The status of the non-virtual neighbor has changed. (RouterId=[RouterId], NbrIfIndex=[NbrIfIndex], NbrIfInstId=[NbrIfInstId], NbrRtrId=[NbrRtrId], NbrState=[NbrState], IfName=[IfName], Reason=[NbrStateChangeReason], SubReason=[SubReason])

The OSPFv3 neighbor status changes. The possible causes are that the status of the interface on the neighbor router changes and the contents of Hello packets change.




Alarm or Event


Trap Severity


Mnemonic Code


Trap OID

Alarm ID


Alarm Type


Raise or Clear


Match trap

The fault trap and service restoration trap are in the same format except that the value of NbrState is different. The trap is a service restoration trap only when the value of 8: Full. Otherwise, it is a fault trap.


Parameter Description


Indicates the router ID.


Indicates the IP address of the neighbor.


Indicates the interface index.


Indicates the router ID of the neighbor.


Indicates the neighbor status.

  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: ExStart
  • 6: Exchange
  • 7: Loading
  • 8: Full


Indicates the interface name.


Indicates the reason why the neighbor status changes:

  • 1 (adjacencyHoldTimerExpired): The timer of the adjacent router timer times out.
  • 2 (physicalInterfaceChange): The status of the router physical interface on the router changes.
  • 3 (ospfProtocolReason): An OSPF protocol error occurs.
  • 4 (bfdSessionStateChange): The BFD session is closed.
  • 5 (configureChange): The OSPF configuration changes.
  • 6 (peerRouterReason): An alarm is generated because of the neighboring router.
  • 100 (alarmCleared): The alarm is cleared because services are restored, OSPFv3 is disabled, or the neighbor is deleted.


Indicates the detailed reason.



VB Name

VB Index







Impact on the System

Whenever the non-virtual neighbor status changes, the trap will be sent. If the neighbor changes from a lower state to a higher state, this trap message is informational only and no action is required. If the neighbor changes from a higher state to a lower state, services may be interrupted.

Possible Causes

Cause 1: The status of the interface on the neighbor router changes.

Cause 2: Interface configurations on the local and remote devices are changed. The configurations include the Hello or Dead timer, interface authentication, and network type.

Cause 3: The reset ospfv3 command is used to restart the OSPF or perform a active/standby switchover.

Cause 4: A packet transmission error occurs and ping fails.


  1. Run the display ipv6 interface and display ospfv3 peer commands to check the interface status of the neighbor router.

    • If the physical interface is Down, check whether the link is functioning properly. If the link is functioning properly, go to Step 2.

    • If the physical interface is Up, go to Step 2.

  2. Ping the peer IP address to check whether packets are forwarded correctly.

    • If the ping fails, go to Step 5.

    • If the ping succeeds, go to Step 3.

  3. Run the display ipv6 interface command on the neighbor device to check whether the OSPFv3 neighbor interface is in the Up state.

    • If the interface is in the Down state, go to Step 5.

    • If the interface is in the Up state, go to Step 4.

  4. Run the display ospfv3 interface command to check whether configurations on both ends are correct.

    • If they are correct, go to Step 6.

    • If they are incorrect, go to Step 5.

  5. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  6. End.
Updated: 2019-05-05

Document ID: EDOC1100004139

Views: 172664

Downloads: 26

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next