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 router.

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	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 on the board 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

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 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.

2. Change the maximum number of area addresses on the source device to 3 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 causes the packets to be changed.

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.