ISIS-STD/2/VERSION_SKEW:OID [oid] IS-IS received a PDU with incorrect ProtocolVersion. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduProtocolVersion=[integer], PduFragment=[opaque])
IS-IS received a PDU carrying an incorrect protocol version number.
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
NotificationSysLevelIndex |
IS-IS level of a device that sends the trap |
CircIfIndex |
Interface index |
PduProtocolVersion |
Protocol version contained in a PDU |
PduFragment |
64-byte PDU header |
1. If the board modifies the packet, route flapping may occur, and the CPU usage will increase.
2. If the trap was triggered by a device communication failure, neighbor relationships could not be established, and routes could not be learned from each other.
Cause 1: The IS-IS version numbers supported by the local wireless access controller and other wireless access controller devices were inconsistent.
Cause 2: The version number field was modified during packet transmission.
If the version field value is 1, go to Step 4.
If the version field value is not 1, 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 IS-IS version number can be changed, go to Step 3.
If the IS-IS version number cannot be changed, go to Step 4.
If the trap is cleared, go to Step 5.
If the trap is not cleared, go to Step 4.