ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

Trap Buffer Description

IS-IS received a PDU with incorrect ProtocolVersion. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduProtocolVersion=[isisPduProtocolVersion], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

IS-IS received a Hello packet with the IS-IS version number not supported by the local device.

Trap Attributes

Trap Attribute Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

ISIS_VERSION_SKEW

Trap OID

1.3.6.1.3.37.2.0.11

MIB

ISIS-MIB

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Name

This is an event trap and does not involve alarm name.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

-

Trap Buffer Parameters

Parameter Description

isisSysInstance

ID of an IS-IS process.

isisSysLevelIndex

IS-IS level.

isisCircIndex

Circuit IfIndex of an interface.

isisCircIfIndex

Circuit IfIndex of an interface.

isisPduProtocolVersion

Version number.

isisPduFragment

64-byte PDU header.

ifIndex

IfIndex of an interface.

IfName

Interface name.

VB Parameters

VB OID VB Name VB Index

1.3.6.1.3.37.1.1.1.1.1

isisSysInstance

isisSysInstance

1.3.6.1.3.37.1.2.1.1.1

isisSysLevelIndex

isisSysInstance

isisSysLevelIndex

1.3.6.1.3.37.1.3.1.1.2

isisCircIfIndex

isisSysInstance

isisCircIndex

1.3.6.1.3.37.1.10.1.1.5

isisPduProtocolVersion

isisSysInstance

1.3.6.1.3.37.1.10.1.1.2

isisPduFragment

isisSysInstance

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

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 devices, neighbors cannot be established, and routes cannot be learnt from each other.

Possible Causes

Cause 1: The number of the IS-IS version supported by the local device was different from that supported by another device.

Cause 2: The value of the version number field was changed during the packet transmission.

Procedure

1. Based on the IS-IS packet format defined in ISO10589, check the isisPduFragment field (in hexadecimal) of the binary packet and obtain the system ID of the source device. Check whether the value of the isisPduProtocolVersion field is 1.

  • If so, go to Step 2.
  • If not, go to Step 4.

2. Check the logs and ping packets to determine whether a hardware fault on the board causes the packets to be changed.

  • If so, go to Step 3.
  • If not, go to Step 6.

3. Replace the board and then check whether the fault is rectified.

  • If so, go to Step 7.
  • If not, go to Step 6.

4. Check whether the IS-IS version number on the source device can be changed.

  • If so, go to Step 5.
  • If not, go to Step 6.

5. Change the IS-IS version number of the source device (The IS-IS version number cannot be changed on the Huawei device). Check whether the fault is rectified.

  • If so, go to Step 7.
  • If not, go to Step 6.

6. Collect log information and configuration information, and then contact technical support personnel.

7. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >