OSPFV3/2/ospfv3NbrStateChange_active

Message

OSPFV3/2/ospfv3NbrStateChange_active: 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])

Description

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.

Parameters

Parameter Name	Parameter Meaning
RouterId	Router ID
NbrIfIndex	Indicates the IP address of the neighbor.
NbrIfInstId	Indicates the interface index.
NbrRtrId	It identifies the router ID of a neighbor.
NbrState	Indicates the neighbor status. The trap is a service restoration trap only when the value of Full. Otherwise, it is a fault trap. 1: Down 2: Attempt 3: Init 4: 2-Way 5: ExStart 6: Exchange 7: Loading 8: Full
IfName	Indicates the interface name.
NbrStateChangeReason	Indicates the reason why the neighbor status changes.
SubReason	Indicates the detailed reason.

Possible Causes

Cause 1: Adjacency holdTimer expired
Cause 2: Physical interface change
Cause 3: Protocol reason
Cause 4: BFD session state change
Cause 5: Configuration change
Cause 6: Peer router reason
Cause 7: Waiting for establishing neighbor

Procedure

Cause 1: Adjacency holdTimer expired
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 alarm information and configuration information, and then contact technical support personnel.

6. End.
Cause 2: Physical interface change
The same as Cause 1.
Cause 3: Protocol reason
The same as Cause 1.
Cause 4: BFD session state change
The same as Cause 1.
Cause 5: Configuration change
The same as Cause 1.
Cause 6: Peer router reason
The same as Cause 1.
Cause 7: Waiting for establishing neighbor
The same as Cause 1.