No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

Description

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 router.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.11

Major

environmentalAlarm(6)

Parameters

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:
  • 1: Level-1

  • 2: Level-2

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.

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

Possible Causes

1. The IS-IS version numbers supported by the local router and other router devices were inconsistent.

2. The version number field was modified during packet transmission.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (in hexadecimal) in the trap and fetch the system ID of the source router. Check whether the value of version field on the source router is as 1.

    • If so, go to Step 4.

    • If not, go to Step 2.

    Table 40-5  Methods of searching for system IDs and types of IS-IS packets

    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

  2. Check whether the IS-IS version number of the source router can be modified.

    • If so, go to Step 3.

    • If not, go to Step 4.

  3. Modify the IS-IS version number of the source router. The Huawei router does not support the modification of the IS-IS version number through a command. Then check whether the trap is cleared.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
  5. End.

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 81313

Downloads: 49

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next