ISIS-STD/3/AREA_MISMATCH:OID [oid] IS-IS received a level-1 Hello PDU whose area address is different from the local area address. (CircIfIndex=[integer], PduFragment=[opaque])
The area address contained in a received Level-1 Hello packet was different from the local one.
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
CircIfIndex |
Interface index |
PduFragment |
64-byte PDU header |
1. If the trap is triggered by a hardware fault on a board, route flapping may occur, and the CPU usage will increase.
2. If the trap is triggered by incorrect configurations, IS-IS neighbor relationships cannot be established, and routes cannot be learned from each other.
Cause 1: Configurations were incorrect.
Cause 2: The area address field was modified.
If the area addresses are the same, go to Step 3.
If the area addresses are different, go to Step 2.
Identifying 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 PduFragment 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. |
If the trap is cleared, go to Step 4.
If the trap is not cleared, go to Step 3.