OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.2 hwOspfv3NbrStateChange
Description
OSPFV3/2/NBRCHANGE:OID [oid] The status of the non-virtual neighbor has changed. (IfIndex=[integer], InstanceId=[integer], NbrRouterId=[gauge], RouterId=[gauge], NbrState=[integer], IfName=[octet], ChgReason=[integer])
The status of the OSPFv3 neighbor changed. A possible cause is that the status of the interface where the neighbor resided changed or the contents of the received Hello packets changed.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.147.0.2 | Major | processingErrorAlarm(4) |
Parameters
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
IfIndex |
Indicates the index of the interface. The value is a decimal integer. |
IfName |
Indicates the name of the interface. |
InstanceId |
Indicates the ID of the OSPFv3 instance. The value is a decimal integer. |
NbrRouterId |
Indicates the Router ID of the neighbor. The value is a decimal integer. |
RouterId |
Indicates the Router ID of the local router. The value is a decimal integer. |
NbrState |
Indicates the state of the neighbor.
|
ChgReason |
Indicates the reason for change in the state
of an OSPFv3 neighbor.
|
Impact on the System
This trap is generated when the status of the neighbor (not a neighbor of a virtual link) changes. This trap indicates that the status of the neighbor changes. If the neighbor changes from a lower status to a higher status, this trap message is informational only, and no action is required. If the neighbor changes from a higher status to a lower status, services may be interrupted.
Possible Causes
- The status of the interface where the neighbor resided changed.
- The configured parameters (such as the Hello timer, dead timer, interface authentication, and network type) of the interfaces on the local end or remote end were modified.
- OSPF was restarted by using the reset ospfv3 command or the active/standby switchover was performed.
- The ping operation failed, which indicated that an error occurred during packet transmission.
Procedure
- Run the display ipv6 interface and display ospfv3 peer commands to check the status of the interface where the neighbor
resides.
If the physical interface is Down, check the link and make the link Up, and then go to Step 2.
If the physical interface is Up, go to Step 2.
- Check whether packets are correctly forwarded and ping
the IP address of the remote interface.
If the ping fails, go to Step 5.
If the ping succeeds, go to Step 3.
- Run the display ipv6 interface command to check
whether the interface where the OSPFv3 neighbor resides 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.
- Run the display ospfv3 interface command to check whether the configurations of the two ends
are correct.
If so, go to Step 6.
If not, go to Step 5.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.