CloudEngine 8800, 7800, 6800, and 5800 V200R019C10 Alarm Handling
This document provides the explanations, causes, and recommended actions of alarms on the product.
OSPF_1.3.6.1.2.1.14.16.2.4 ospfIfConfigError
Trap Buffer Description
A packet is received on the non-virtual interface from a router whose configuration conflicts with the local configuration. (RouterId=[RouterId], IfIpAddress=[IfIpAddress], AddressLessIf=[AddressLessIf], Packettemp=[PacketSrc], ConfigErrorType=[ConfigErrorType], PacketType=[PacketType], ProcessId=[ProcessId], AreaId=[AreaId])
The configurations on the two interfaces for establishing an OSPF neighbor relationship were inconsistent with each other. The possible cause is that the hello, dead, or poll timer on one end was inconsistent with that on the peer end, or the interfaces were not configured on one area.
Trap Attributes
Trap Attribute | Description |
---|---|
Alarm or Event |
Event |
Trap Severity |
Warning |
Trap OID |
1.3.6.1.2.1.14.16.2.4 |
MIB |
OSPF-TRAP-MIB |
Alarm ID |
This is an event trap and does not involve alarm ID. |
Alarm Name |
This is an event trap and does not involve alarm name. |
Alarm Type |
This is an event trap and does not involve alarm type. |
Raise or Clear |
This is an event trap and does not involve alarm generation or clearance. |
Match trap |
- |
Trap Buffer Parameters
Parameter | Description |
---|---|
RouterId |
ID of the local device. |
IfIpAddress |
IP address of the non-virtual interface. |
AddressLessIf |
Interface index. |
PacketSrc |
Source IP address of the packet. |
ConfigErrorType |
Error type.
|
PacketType |
Packet type ID.
|
ProcessId |
Process ID of the local device. |
AreaId |
Area ID. |
VB Parameters
VB OID | VB Name | VB Index |
---|---|---|
1.3.6.1.2.1.14.1.1 |
ospfRouterId |
- |
1.3.6.1.2.1.14.7.1.1 |
ospfIfIpAddress |
ospfIfIpAddress ospfAddressLessIf |
1.3.6.1.2.1.14.7.1.2 |
ospfAddressLessIf |
ospfIfIpAddress ospfAddressLessIf |
1.3.6.1.2.1.14.16.1.4 |
ospfPacketSrc |
- |
1.3.6.1.2.1.14.16.1.2 |
ospfConfigErrorType |
- |
1.3.6.1.2.1.14.16.1.3 |
ospfPacketType |
- |
Impact on the System
Possible Causes
Cause 1: Interface parameters configured on the two interfaces for establishing the OSPF neighbor relationship were inconsistent. Cause 2. The link-layer protocol changed.
Procedure
1. Run the display ospf interface command to check whether the configurations on the two interfaces are consistent.
- If the configurations on the two interfaces are consistent, go to Step 3.
- If the configurations on the two interfaces are inconsistent, go to Step 2.
2. Do as follows based on the networking:
- If the networking allows you to modify the configurations on the two ends to be consistent, go to Step 3.
- If the networking does not allow you to modify the configurations on the two ends to be consistent, go to Step 4.
3. Modify the parameters of the hello, dead, and poll timers on one end to be consistent with that on the other end. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 5.
- If the alarm is not cleared, go to Step 4.
4. Contact contact technical support personnel.
5. End.