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-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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-STD_1.3.6.1.2.1.138.0.5 isisIDLenMismatch

ISIS-STD_1.3.6.1.2.1.138.0.5 isisIDLenMismatch

Description

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

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.5

Major

other(1)

Parameters

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

Impact on the System

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.

Possible Causes

Cause 1: The length of the System ID supported by the local router mismatched that of the System ID supported by another router.

Cause 2: The value of the System ID Length field was changed.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, check the pdu-fragment field value (in hexadecimal) and obtain the system ID of the source router. Check whether the length of the system ID is neither 0 nor 6.

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

    Table 39-7  Methods of identifying system IDs and types of IS-IS packets

    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.

  2. Change the System ID length of the source router to 6 and check whether the trap is cleared.

    • If the trap is cleared, go to Step 4.

    • If the trap is not cleared, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 132541

Downloads: 20

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