ISIS/2/ISIS_MAX_AREA_ADDRESSES_MISMATCH
Message
ISIS/2/ISIS_MAX_AREA_ADDRESSES_MISMATCH: The MaxAreaAddress field of received PDU is different from local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisPduMaxAreaAddress=[isisPduMaxAreaAddress], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])
Description
The maximum number of area addresses in the received Level-1 PDU header mismatched the maximum number of area addresses supported by the local device.
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
[isisSysInstance] |
ID of an IS-IS process |
[isisSysLevelIndex] |
IS-IS level |
[isisPduMaxAreaAddress] |
Maximum number of area addresses |
[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: If a hardware fault triggered the generation of this log, route flapping might occur and the CPU usage increased.
Cause 2: If communication between devices triggered the generation of this log, neighbor relationships could not be established, and routes could not be learned from each other.
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 the value of the isisPduMaxAreaAddress field and determine whether the number of maximum area addresses
is neither 0 nor 3.
If so, go to Step 2.
If not, go to Step 3.
Table 47-5 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 10th 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 maximum number of area addresses on the source
to 3 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 causes the packets
to be changed.
If so, go to Step 4.
If not, go to Step 5.
- Contact technical support personnel technical support personnel.
- End.
