OSPFV3/2/VNBRCHANGE:OID [oid] The status of the virtual neighbor has changed. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VNbrState=[integer], ChgReason=[integer])
The status of the OSPFv3 neighbor on the virtual link changed because the status of the virtual link interface changed.
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.147.0.3 | Major | processingErrorAlarm(4) |
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
AreaId |
Indicates the ID of the OSPFv3 area. The value is a decimal integer. |
VirtualNbrRouterId |
Indicates the Router ID of the virtual link neighbor. The value is a decimal integer. |
RouterId |
Indicates the Router ID of the local switch. The value is a decimal integer. |
VNbrState |
Indicates the state of the virtual link neighbor.
|
ChgReason |
Indicates the reason for change in the state
of virtual link neighbor.
|
This trap is generated when the status of the neighbor (a neighbor of a virtual link) 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.
1. The status of the interface of the virtual link changed.
2. The configured parameters (such as the Hello timer, dead timer, interface authentication, and network type) of the virtual link interface on the local end or remote end were modified.
3. OSPFv3 was restarted by using the reset ospfv3 command or the active/standby switchover was performed.
4. An error packet was received.
5. The overflow function was configured and the process entered the Overflow state.
6. Routes of the area configured with the virtual link were added or deleted.
7. The ping operation failed, which indicated that an error occurred during packet transmission.
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.
If the neighbor relationship is abnormal, check whether trap 1.3.6.1.4.1.2011.5.25.147.0.2 exists. If the trap exists, locate the fault according to the trap. If the trap does not exist, go to Step 6.
If the neighbor relationship is normal, go to Step 3.
If the route does not exist, go to Step 5.
If the route exists, go to Step 4.
If so, go to Step 6.
If not, go to Step 5.
If so, go to Step 7.
If not, go to Step 6.