ISIS_1.3.6.1.3.37.2.0.5 isisIDLenMismatch

Trap Buffer Description

The ID length of received PDU is different from local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisPduFieldLen=[isisPduFieldLen], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The length of the system ID in the header of the received PDU does not match the length of the system ID of the local device.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Critical
Mnemonic Code	ISIS_ID_LEN_MISMATCH
Trap OID	1.3.6.1.3.37.2.0.5
MIB	ISIS-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
isisSysInstance	ID of an IS-IS process.
isisSysLevelIndex	IS-IS level.
isisPduFieldLen	Length of the received PDU.
isisCircIndex	Circuit index of an interface.
isisCircIfIndex	IfIndex of an interface.
isisPduFragment	64-byte PDU header.
ifIndex	IfIndex of an interface.
IfName	Interface name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.3.37.1.1.1.1.1	isisSysInstance	isisSysInstance
1.3.6.1.3.37.1.2.1.1.1	isisSysLevelIndex	isisSysInstance isisSysLevelIndex
1.3.6.1.3.37.1.10.1.1.3	isisPduFieldLen	isisSysInstance
1.3.6.1.3.37.1.3.1.1.2	isisCircIfIndex	isisSysInstance isisCircIndex
1.3.6.1.3.37.1.10.1.1.2	isisPduFragment	isisSysInstance
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex

Impact on the System

1. If the trap is triggered because of a hardware fault on the board, route flapping may occur.

2. If the trap is triggered because of intercommunication between devices, neighbors cannot be established, or routes cannot be learnt from each other.

Possible Causes

1: The system ID length supported by the local device does not match that supported by other devices.

2: The System ID Length field is modified.

Procedure

1. Based on the IS-IS packet format defined in ISO10589, check the isisPduFragment field value (in hexadecimal) and obtain the system ID of the source device. Check whether the length of the system ID is neither 0 nor 6.

If so, go to Step 2.
If not, go to Step 3.

2. Change the System ID length of the source device to 6 and check whether the fault is rectified.

If so, go to Step 6.
If not, go to Step 3.

3. Check the logs and ping packets to determine whether a hardware fault on the board changes the packets.

If so, go to Step 4.
If not, go to Step 5.

4. Replace the board and then check whether the fault is rectified.

If so, go to Step 6.
If not, go to Step 5.

5. Collect log information and configuration information, and then contact technical support personnel.

6. End.