ISIS/2/VERSION_SKEW:OID [oid] IS-IS received a PDU with incorrect ProtocolVersion. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduProtocolVersion=[integer], pduFragment=[opaque], ifName=[string])
The IS-IS version number of the received Hello packet was inconsistent with that of the Hello packet supported by the local switch.
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:
|
sysInstanceofCircIfIndex |
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. |
pduProtocolVersion |
Indicates the protocol version contained in a PDU. |
pduFragment |
Indicates the fragment of 64-byte PDU header. |
ifName |
Indicates the name of the interface. |
1. If the board modifies the packet, route flapping may occur, and the CPU usage will increase.
2. If the trap is generated because of intercommunication between switch devices, neighbors cannot be established, and routes cannot be learnt from each other.
1. The IS-IS version numbers supported by the local switch and other switch devices were inconsistent.
2. The version number field was modified during packet transmission.
If so, go to Step 4.
If not, go to Step 2.
Searching 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 |
If so, go to Step 3.
If not, go to Step 4.
If so, go to Step 5.
If not, go to Step 4.