ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch

Trap Buffer Description

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])

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.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Critical
Mnemonic Code	ISIS_MAX_AREA_ADDRESSES_MISMATCH
Trap OID	1.3.6.1.3.37.2.0.6
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.
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.

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.4	isisPduMaxAreaAddress	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 by a hardware fault of the board, route flapping may occur and the CPU usage will increase.

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

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.