ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch
Description
ISIS/2/MAXAREA_MISMATCH:OID [oid] The MaxAreaAddress field of received PDU is different from local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], pduMaxAreaAddress=[integer], sysInstanceofPduMaxAreaAddress=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])
The maximum number of area addresses supported in the header of the received Level-1 PDU mismatched with that supported by the local router.
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
sysInstance |
Indicates the ID of the IS-IS process. |
sysInstanceofLevel |
Indicates the ID of the IS-IS process. |
sysLevel |
Indicates the IS-IS level:
|
pduMaxAreaAddress |
Indicates the maximum number of area addresses. |
sysInstanceofPduMaxAreaAddress |
Indicates the ID of the IS-IS process. |
circIndex |
Indicates the index of the interface. |
ifIndex |
Indicates the index of the interface. |
circIfIndex |
Indicates the IF index of the interface. |
pduFrag |
Indicates the fragment of 64-byte PDU header. |
ifName |
Indicates the name of the interface. |
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 router devices, neighbors cannot be established, and routes cannot be learnt from each other.
Possible Causes
1. The maximum number of area addresses supported by the local router mismatch the number of area addresses supported by other router devices.
2. The maximum area address field was modified.
Procedure
- Based on the IS-IS packet format defined in ISO10589, search
for the pdu-fragment field (in hexadecimal) in the trap and
fetch the system ID of the source router. Then, find the value of the pdu-max-area field in the trap
and check 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 39-2 Methods of searching for system IDs and types of IS-IS packetsSearching for the Packet Type
Searching for the System ID
Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11
The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field
LSP: the 5th byte in the pdu-fragment field being 12 or 14
The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field
SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B
The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field
- Modify the maximum number of area addresses of the source router to 3. Then, check whether the trap is cleared.
If so, go to Step 4.
If not, go to Step 3.
- Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
- End.
Previous
