ISIS-STD_1.3.6.1.2.1.138.0.6 isisMaxAreaAddressesMismatch
Description
ISIS-STD/2/MAXAREA_MISMATCH:OID [oid] The MaxAreaAddress field of received PDU is different from local configuration. (NotificationSysLevelIndex=[integer], PduMaxAreaAddress=[integer], CircIfIndex=[integer], PduFrag=[opaque])
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
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
NotificationSysLevelIndex |
IS-IS level of a device that sends the trap |
PduMaxAreaAddress |
Maximum number of area addresses contained in a received PDU header |
CircIfIndex |
Interface index |
PduFrag |
64-byte PDU header |
Impact on the System
1. If the trap is triggered by a hardware fault on the board, route flapping may occur and the CPU usage increases.
2. If the trap is triggered by communication between devices, neighbor relationships cannot be established, and routes cannot be learned from each other.
Possible Causes
Cause 1: The maximum number of area addresses supported by the local router mismatched that supported by another router.
Cause 2: The maximum area address field was modified.
Procedure
- Based on the IS-IS packet format defined in ISO10589, check
the pdu-fragment field value (in hexadecimal) and obtain the
system ID of the source router. Check the pdu-max-area field value and determine whether
the maximum number of area addresses is neither 0 nor 3.
If the maximum number of area addresses is neither 0 nor 3, go to Step 2.
If the maximum number of area addresses is 0 or 3, go to Step 3.
Table 39-8 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 pdu-fragment field is 0f, 10, or 11.
The six consecutive bytes beginning with the 10th byte in the pdu-fragment field constitute a System ID.
LSP: An LSP is identified when the 5th byte in the pdu-fragment field is 12 or 14.
The six consecutive bytes beginning with the 13th byte in the pdu-fragment field constitute a System ID.
SNP: An SNP is identified when the 5th byte in the pdu-fragment field is 18, 19, 1A, or 1B.
The six consecutive bytes beginning with the 11th byte in the pdu-fragment field constitute a System ID.
- Change the maximum number of area addresses on the source router to 3 and check whether the trap is cleared.
If the trap is cleared, go to Step 4.
If the trap is not cleared, go to Step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.