ISIS/2/ISIS_ID_LEN_MISMATCH
Message
ISIS/2/ISIS_ID_LEN_MISMATCH: The ID length of the received PDU is different from the 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 contained in the received PDU (including all types of IS-IS packets) header mismatched that of the System ID on 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] |
Circuit IfIndex of an interface |
[isisPduFragment] |
64-byte PDU header |
[ifIndex] |
IfIndex of an interface |
[IfName] |
Interface name |
Possible Causes
Cause 1: The length of the System ID supported by the local mismatched that of the System ID supported by another .
Cause 2: The value of the System ID Length field was changed.
Procedure
- 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 . 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.
Table 47-4 ISISCOMM/2/Methods of identifying system IDs and types of IS-IS packetsIdentifying the Packet Type
Identifying the System ID
Hello: A Hello packet is identified when the 5th byte in the isisPduFragment field is 0f, 10, or 11.
The six consecutive bytes beginning with the tenth byte in the isisPduFragment field constitute a System ID.
LSP: An LSP is identified when the 5th byte in the isisPduFragment field is 12 or 14.
The six consecutive bytes beginning with the 13th byte in the isisPduFragment field constitute a System ID.
SNP: An SNP is identified when the 5th byte in the isisPduFragment field is 18, 19, 20, or 21.
The six consecutive bytes beginning with the 11th byte in the isisPduFragment field constitute a System ID.
- Change the System ID length of the source to 6 and check
whether the fault is rectified.
If so, go to Step 6.
If not, go to Step 3.
- Check the logs and ping packets to determine whether a
hardware fault on the device changes the packets.
If so, go to Step 4.
If not, go to Step 5.
- Contact technical support personnel technical support personnel.
- End.
