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-STD_1.3.6.1.2.1.138.0.13 isisRejectedAdjacency

ISIS-STD_1.3.6.1.2.1.138.0.13 isisRejectedAdjacency

Description

ISIS-STD/3/REJECT_ADJ:OID [oid] IS-IS failed to establish the adjacency with its peer. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduFragment=[opaque])

The local router received Hello packets sent from the neighboring router but failed to establish IS-IS neighbor relationships with it.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.13

Minor

environmentalAlarm(6)

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

PduFragment

64-byte PDU header

Impact on the System

The neighbor relationship cannot be established properly.

Possible Causes

Cause 1: The system ID or virtual system ID on the local router was the same as that on the neighboring router.

Cause 2: Hello packets failed authentication because the authentication mode or password on the local interface was different from that on the neighboring interface.

Cause 3: IS-IS Level-1 area addresses were different on the two ends of the link.

Cause 4: The local interface received Hello packets with the level mismatched that on the local interface.

Cause 5: On a broadcast network, the local interface received Hello packets from an interface that is not on the network segment where the local interface resides.

Cause 6: On a P2P network, when not configured with the isis peer-ip-ignore command, the local interface received Hello packets from an interface that is not on the network segment where the local interface resides.

Procedure

  1. Check the IfName field in the trap to identify the interface that receives packets.

    • If the interface is a broadcast interface, go to Step 2.

    • If the interface is a P2P interface, go to Step 7.

  2. Check the PduFragment field, and then identify the source router based on its system ID (six consecutive bytes beginning with the 10th byte). Run the display this command in the views of interfaces on the two ends of the link and in the IS-IS process view to check whether the IS-IS levels and interface levels on the two ends of the link are consistent.

    • If the IS-IS levels and interface levels on the two ends of the link are not consistent, go to Step 3.

    • If the IS-IS levels and interface levels on the two ends of the link are consistent, go to Step 6.

  3. Run the isis circuit-level command in the interface view to change the IS-IS levels and interface levels on the two ends of the link to be the same. Then check whether the trap is cleared.

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

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

  4. Run the display ip interface command to check whether the IP addresses of the source router interface and the local interface are on the same network segment.

    • If the IP addresses of the source router interface and the local interface are on the same network segment, go to Step 8.

    • If the IP addresses of the source router interface and the local interface are not on the same network segment, go to Step 5.

  5. Run the ip address command in the interface views of the source and local router devices to configure IP addresses of the interfaces to be on the same network segment. Then check whether the trap is cleared.

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

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

  6. Run the display this command in the interface views of the source and local router devices to check whether the isis peer-ip-ignore command is run on the interfaces.

    • If the isis peer-ip-ignore command is run on the interfaces, go to Step 10.

    • If the isis peer-ip-ignore command is not run on the interfaces, go to Step 7.

  7. Run the isis peer-ip-ignore or ip address command in the interface views of the source and local router devices to configure the IP addresses of the two interfaces to be on the same network segment. Then check whether the trap is cleared.

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

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

  8. Check whether the Level-1 area addresses on the two ends of the link are the same.

    • If the Level-1 area addresses on the two ends of the link are the same, go to Step 10.

    • If Level-1 area addresses on the two ends of the link are different, go to Step 9.

  9. Run the network-entity command in the IS-IS view to configure a new area address to ensure that the Level-1 area addresses on the two ends are the same. Then check whether the trap is cleared.

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

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

  10. Run the display current-configuration command to check whether the system ID of the source router is the same as the system ID or virtual system ID on the local router.

    • If they are the same, go to Step 11.

    • If they are different, go to Step 12.

  11. Run the network-entity command to change the system ID or virtual system ID on one router to ensure that the system IDs or virtual system IDs on the two ends are different. Then check whether the trap is cleared.

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

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

  12. Check whether IS-IS authentication modes and authentication passwords configured on two ends are the same.

    • If they are the same, go to Step 14.

    • If they are different, go to Step 13.

  13. Run the isis authentication-mode command in the views of interfaces on the two ends to change the authentication mode and authentication password to ensure that IS-IS authentication modes and authentication passwords of the interfaces are consistent. Alternatively, run the undo isis authentication-mode command in the views of interfaces on the two ends to disable IS-IS authentication (disabling IS-IS authentication degrades the system security). Then check whether the trap is cleared.

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

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

  14. Collect alarm information and configuration information, and then contact technical support personnel.
  15. End.

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 70021

Downloads: 45

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