OSPF_1.3.6.1.2.1.14.16.2.5 ospfVirtIfConfigError

Description

OSPF/3/VIFCFGERR:OID [oid]: A packet is received on the virtual interface from a router whose configuration conflicts with the local configuration. (VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id], ConfigErrorType=[error-type], PacketType=[packet-type], InstanceName=[instance-name])

Configurations of the interfaces on the two ends of the virtual link were incorrect. The possible cause was that the configurations of the parameters conflicted.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.14.16.2.5	Minor	processingErrorAlarm (4)

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 ID of the local switch.
ConfigErrorType	Indicates the error type. 1: Bad Version 2: Area Mismatch 3: Unknown Nbma Neighbour 4: Unknown Virtual Neighbour 7: NetMask Mismatch 8: Hello Interval Mismatch 9: Dead Interval Mismatch 10: Option Mismatch 11: Mtu Mismatch 12: Duplicate RouterId
PacketType	Indicates the type of the packet. 1: Hello packet 2: DD packet 3: Request packet 4: Update packet 5: Acknowledgement packet 6: Update packet Retrans 7: Update packet flood
InstanceName	Indicates the instance name.

Impact on the System

This trap message is generated after the virtual interface receives a packet indicating parameters are incorrectly configured.

Possible Causes

The configurations of the interfaces on the two ends of the virtual link conflicted.

Procedure

Run the display ospf vlink and display current- configuration configuration commands to check whether the configurations of the two interfaces are consistent.
- If so, go to Step 3.
- If not, go to Step 2.
Perform the following operations according to the networking:
- If it is allowed to modify the configurations on the two interfaces to be consistent, run the following command to modify the configurations on the two interfaces to be consistent.
  
  vlink-peer router-id [ dead dead-interval | hello hello-interval | retransmit retransmit-interval | smart-discover | trans-delay trans-delay-interval | [ simple [ plain plain-text | [ cipher ] cipher-text ] | { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ] | authentication-null | keychain keychain-name ] ] ^*
  
  Then, check whether the tap is cleared.
  - If so, go to Step 4.
  - If not, go to Step 3.
- If it is not allowed to modify the configurations on the two interfaces to be consistent, go to Step 3.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None