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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document provides the explanations, causes, and recommended actions of alarms on the product.
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.13 isisRejectedAdjacency

ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

Description

IS-IS failed to establish the adjacency with its peer. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

IS-IS failed to establish a neighbor relationship.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

isisRejectedAdjacency

Trap OID

1.3.6.1.3.37.2.0.13

Alarm ID

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

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

This is an event trap and does not involve the matching trap.

Parameters

Parameter Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates a 64-byte PDU fragment.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

VB

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

isisPduFragment

isisSysInstance

Impact on the System

The neighbor relationship cannot be established.

Possible Causes

1. The system ID or virtual system ID of the local is the same as the system ID of the neighbor.

2. The authentication mode or the authentication password configured for the interface on the local was inconsistent with that configured on the neighbor. As a result, the authentication of the Hello packet failed.

3. The Level-1 area address of the IS-IS neighbor was inconsistent with the Level-1 area address of the local .

4. The local interface received a Hello packet whose level is inconsistent with the local level.

5. In a broadcast network, the local interface received a Hello packet sent by the adjacent interface whose IP address is on a different network segment.

6. In a P2P network, because the isis peer-ip-ignore is not configured, the local interface received a Hello packet sent by the adjacent interface whose IP address is on a different network segment.

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 in the trap, and then identify the source according to the consecutive six bytes beginning with the tenth byte, which indicates the system ID of the source . 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 both ends of the link are consistent.

    • If so, go to Step 6.

    • If not, go to Step 3.

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

    • If so, go to Step 15.

    • If not, go to Step 4.

  4. Run the display ip interface command to check whether the IP address of the interface on the source is on the same network segment as the IP address of the local interface.

    • If so, go to Step 8.

    • If not, go to Step 5.

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

    • If so, go to Step 15.

    • If not, go to Step 8.

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

    • If so, go to Step 10.

    • If not, go to Step 7.

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

    • If so, go to Step 15.

    • If not, go to Step 10.

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

    • If so, go to Step 10.

    • If not, 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 both ends are the same. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 10.

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

    • If so, go to Step 11.

    • If not, go to Step 12.

  11. (Run the undo network-entity command with caution.) Change the system ID or virtual system ID on one to ensure that the system IDs or virtual system IDs on both ends are different. Then, check whether the trap is cleared.

    • If so, go to Step 14.

    • If not, go to Step 12.

  12. Check IS-IS authentication modes and authentication passwords of interfaces on both ends are the same.

    • If so, go to Step 14.

    • If not, go to Step 13.

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

    • If so, go to Step 15.

    • If not, go to Step 14.

  14. Collect the trap information, log information, and configuration, and then contact technical support personnel technical personnel.
  15. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17158

Downloads: 25

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