ISIS/2/ISIS_ID_LEN_MISMATCH

Message

ISIS/2/ISIS_ID_LEN_MISMATCH: 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])

Description

The length of the system ID in the header of the received PDU (including all types of IS-IS packets) does not match the length of the system ID of the local device.

Parameters

Parameter Name	Parameter Meaning
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

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.