ISIS-STD/2/SYSID_MISMATCH:OID [oid] The ID length of received PDU is different from local configuration. (NotificationSysLevelIndex=[integer], PduFieldLen=[integer], CircIfIndex=[integer], PduFrag=[opaque])
The length of the System ID contained in the received PDU (including all types of IS-IS packets) header mismatched that of the System ID on the local wireless access controller.
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
NotificationSysLevelIndex |
IS-IS level of a device that sends the trap |
PduFieldLen |
Length of the received PDU |
CircIfIndex |
Interface index |
PduFrag |
64-byte PDU header |
1. If the trap is triggered by a hardware fault on the board, route flapping may occur.
2. If the trap is triggered by communication between devices, neighbor relationships cannot be established, and routes cannot be learned from each other.
Cause 1: The length of the System ID supported by the local wireless access controller mismatched that of the System ID supported by another wireless access controller.
Cause 2: The value of the System ID Length field was changed.
If the length of the system ID is neither 0 nor 6, go to Step 2.
If the length of the system ID is 0 or 6, go to Step 3.
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 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. |
If the trap is cleared, go to Step 4.
If the trap is not cleared, go to Step 3.