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, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

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-STD_1.3.6.1.2.1.138.0.9 isisAuthenticationTypeFailure

ISIS-STD_1.3.6.1.2.1.138.0.9 isisAuthenticationTypeFailure

Description

ISIS-STD/3/AUTHTYPE_FAIL:OID [oid] The authentication type of received PDU is different from local configuration. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduFrag=[opaque])

The authentication type contained in a received PDU was inconsistent with the locally configured one.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.9

Minor

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

CircIfIndex

Interface index

PduFrag

64-byte PDU header

Impact on the System

1. If Hello packets do not pass authentication, IS-IS neighbor relationships cannot be set up properly.

2. If LSPs or SNP packets do not pass authentication, LSDB synchronization will fail but IS-IS neighbor relationships will be set up properly.

Possible Causes

Cause 1: Authentication was configured on an interface or process of the local end, but the authentication type on the peer end was different from that on the local end.

Cause 2: Authentication was configured on an interface or process of the local end, but no authentication was configured on the peer end.

Procedure

  1. Obtain the IS-IS process number based on the SysInstance field and IS-IS level (1 indicates a Level-1 packet; 2 indicates a Level-2 packet; 3 indicates a P2P Hello packet) based on the SysLevel field. Based on the IS-IS packet format defined in ISO10589, check the IfName field in the trap to identify the interface that receives packets. Then, find the PduFrag field and obtain the system ID of the source router that sends the packets and packet type.

    • If the packet type is Hello, go to Step 2.
    • If the packet type is LSP or SNP, go to Step 4.
    Table 39-9  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. Run the display isis peer command on the source router to check the interface that sends packets. Enter the view of this interface, and run the display this command to check whether an interface authentication mode is configured. If an interface authentication mode is configured, check whether it is the same as the interface authentication mode of the local router.

    • If the interface authentication modes are the same, go to Step 6.

    • If the interface authentication modes are different, go to Step 3.

  3. Run the isis authentication-mode command in the interface view of the source router to configure the authentication mode to be the same as that of the local router, and ensure that the authentication passwords on the two ends are the same. Then check whether the trap is cleared.

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

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

  4. Run the display current-configuration configuration isis command on the source router to check whether an area authentication mode or a domain authentication mode is configured in the IS-IS process. If an area authentication mode or a domain authentication mode is configured, check whether the area or domain authentication mode is same as that of the local router, and ensure that the authentication passwords configured on the two ends are the same.

    • If the area or domain authentication modes are the same, go to Step 6.

    • If the area or domain authentication modes are different, go to Step 5.

  5. Run the area-authentication-mode command (for Level-1 packets) or the domain-authentication-mode command (for Level-2 packets) in the IS-IS view of the source router to configure the authentication mode to be the same as that of the local router. Then check whether the trap is cleared.

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

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

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

Translation
Download
Updated: 2019-05-07

Document ID: EDOC1100034065

Views: 132254

Downloads: 40

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