OSPF_1.3.6.1.2.1.14.16.2.16 ospfIfStateChange

Description

OSPF/2/IFCHG:OID [oid]: The status of the non-virtual interface changes. (IfIpAddress=[ipaddr], AddressLessIf=[integer], ProcessId=[integer], AreaId=[ipaddr], IfnetIndex=[integer], ProcessId=[integer], RouterId=[ipaddr], IfState=[integer], IfName=[octet], InstanceName=[octet], IfChgReason=[integer])

The status of the OSPF non-virtual-link interface changed. The possible cause was that the physical interface was Down.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.14.16.2.16	Major	environmentalAlarm (6)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
IfIpAddress	Indicates the IP address of the non-virtual-link interface.
AddressLessIf	Indicates the index of the interface.
ProcessId	Indicates the process ID.
AreaId	Indicates the area ID.
IfnetIndex	Indicates the Ifnet index of the interface.
ProcessId	Indicates the process ID.
RouterId	Indicates the router ID of the local switch.
IfState	Indicates the status of the interface. 1: Down 2: Loopback 3: Waiting 4: Point-to-Point 5: DR 6: Backup 7: DROther
IfName	Indicates the name of interface.
InstanceName	Indicates the instance name.
IfChgReason	Indicates the reason why the neighbor status changes: 1 (adjacencyHoldTimerExpired): indicates that the timer of the adjacent router times out. 2 (physicalInterfaceChange): indicates that the status of the physical interface on the router changes. 3 (ospfProtocolReason): indicates that an alarm is generated because of the OSPF protocol. 4 (bfdSessionStateChange): indicates that the BFD session is closed. 5 (configureChange): indicates that the OSPF configuration changes. 6 (peerRouterReason): indicates that an alarm is generated because of the neighboring router. 100 (alarmCleared): indicates that the alarm is cleared because services are restored or the neighbor is deleted.

Impact on the System

If the interface status becomes Down, services may be affected. If the interface status becomes DR, BDR, DRother, or P2P, services will not be affected.

Possible Causes

1. The status of the physical interface changed.

2. DR election occurred on the broadcast network.

Procedure

Run the display ospf interface command to check whether the interface is Down.
- If the interface is Down, go to Step 2.
- If the interface is in another state, services are not affected. Then, go to Step 4.
Run the display interface interface-type interface-number command to check whether the current interface is Up.
- If so, go to Step 3.
- If not, view the log file to check whether the shutdown command is run on the interface.
  - If the shutdown command is run on the interface, in the case of an incorrect operation, run the undo shutdown command on the interface; otherwise, go to Step 4.
  - If the shutdown command is not run on the interface, it indicates that the link is faulty. Thus, replace the link or go to Step 3.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None