OSPF_1.3.6.1.2.1.14.16.2.1 ospfVirtIfStateChange

Description

OSPF/3/VIFCHG:OID [oid]: The status of the virtual interface changes. (VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id], VirtIfState=[neighbor-state], InstanceName=[instance-name])

The interface status of the OSPF virtual link changed. The possible cause was that the router ID of the neighbor changed after the virtual link was configured or the status of the physical interface of the virtual link changed.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.14.16.2.1	Minor	environmentalAlarm (6)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
VirtIfAreaId	Indicates the area ID.
VirtIfNeighbor	Indicates the router ID of the neighbor on the virtual link.
ProcessId	Indicates the process ID.
RouterId	Indicates the router ID of the local switch.
VirtIfState	Indicates the status of the neighboring interface. 1: Down 2: Loopback 3: Waiting 4: Point-to-Point 5: DR 6: Backup 7: DROther
InstanceName	Indicates the instance name.

Impact on the System

If the interface status of the virtual link changes from Down to P2P (Point-to-Point), this trap message is informational only, and no action is required. If the interface status of the virtual link changes from P2P to Down, the virtual link will be disconnected, the OSPF route calculation will be incorrect, and services may be interrupted.

Possible Causes

1. The status of the physical interface of the virtual link changed.

2. Router ID of the neighbor on the virtual link changed.

Procedure

Run the display ospf vlink command to check whether the interface status of the virtual link is P2P.
- If so, it indicates that this trap message is informational only, and no action is required. Go to Step 4.
- If not, go to Step 2.
Run the display ospf process-id routing router-id neighbor-router-id command to check whether the area has the route to the remote switch.
- If so, collect the configuration of the remote switch, and go to Step 3.
- If not, run the display ospf interface command to check whether the status of the local interface is Down.
  - If so, run the display rm interface or display ip interface command to check whether the local interface goes Down.
    - If so, collect interface information, and go to Step 3.
    - If not, collect log information, and go to Step 3.
  - If not, collect the configuration of the remote switch, and go to Step 3.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None