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 V200R002C50

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.17 isisAdjacencyChange

ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange

Description

ISIS adjacency state change. (SysInstance=[IsisSysInstance], SysLevel=[IsisSysLevelIndex], CircIndex=[IsisCircIndex], CircIfIndex=[IsisCircIfIndex], LspId=[IsisPduLspId], AdjState=[IsisAdjState], IfIndex=[IfIndex], IfName=[IfName], Reason=[HwIsisAdjChgReason], SubReason=[HwIsisAdjChgSubReason])

The IS-IS adjacency state changed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

isisAdjacencyChange

Trap OID

1.3.6.1.3.37.2.0.17

Alarm ID

0x0001009e

Alarm Type

communicationsAlarm

Raise or Clear

None

Match trap

Generate-alarm trap and clear-alarm trap use the same trap name, which is ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange. The two traps are distinguished by the Reason parameter. When the Reason parameter is The alarm was cleared, the trap indicates that an alarm has been cleared. The other values of the Reason parameter indicate that an alarm has been generated.

Parameters

Parameter Description

SysInstance

IS-IS process ID.

SysLevel

Level of the adjacency of which the status changes.

CircIndex

Index of IS-IS interface.

CircIfIndex

Index of IS-IS interface.

LspId

LSP ID.

AdjState

State of IS-IS adjacency.

IfIndex

IF index of the interface.

IfName

Name of the interface.

Reason

Reason for the status change of the IS-IS adjacency:

  • The adjacency HoldTimer expired.

  • The physical interface went Down.

  • Protocol reason.

  • BFD detected that the neighbor went Down.

  • Configurations changed.

  • Peer router reason.

  • The alarm was cleared.

SubReason

Detailed reason for the status change of the IS-IS adjacency:
  • The neighbor went Up.

  • The neighbor was deleted.

  • The IS-IS interface was deleted or disabled.

  • The IS-IS interface was in silent status

  • Incorrect packets were received.

  • Authentication failed.

  • A system ID conflict occurred.

  • The number of area addresses reached the upper limit.

  • No matching Level-1 area address was available.

  • Adjacency HoldTimer Expired.

  • The IS-IS interface went Down.

  • Protocol types did not match.

  • The memory was insufficient.

  • The BFD session went Down.

  • IS-IS was shut Down.

  • The handshake mode was changed.

  • The neighbor was reset.

  • The IS-IS interface type was changed.

  • IS-IS was reset.

  • The last network entity was deleted.

  • The undo isis command was run.

  • Levels did not match.

  • The IIH packet did not contain the local SNPA address.

  • The neighbor did not go Up after three-way handshake.

  • No matching MT ID was available.

  • The CircuitId was changed.

  • During three-way handshake, the received Hello packet did not contain the local system ID.

  • Other errors occurred.

  • Checksum errors occurred.

  • IS-IS was associated with multicast.

  • The topology was suppressed.

  • The alarm timed out.

  • Configurations were changed.

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

isisPduLspId

isisSysInstance

1.3.6.1.3.37.1.10.1.1.9

isisAdjState

isisSysInstance

Impact on the System

IS-IS may re-calculate routes, which causes route flapping and interrupts the IS-IS service.

Possible Causes

Cause 1: The adjacency HoldTimer expired.

Cause 2: The physical interface went Down.

Cause 3: Protocol reason.

Cause 4: BFD detected that the neighbor went Down.

Cause 5: Configurations changed.

Cause 6: Peer router reason.

Cause 100: The alarm was cleared.

Procedure

  • Cause 1: The adjacency HoldTimer expired.
    1. Run the ping command to check whether the link between local and the remote router works properly.

      • If so, go to step 2.
      • If not, go to step 4.

    2. Run the display current-configuration configuration isis command to check whether the IS-IS configurations of the remote router are correct.

      • If so, go to step 3.
      • If not, go to step 5.

    3. Run the display cpu command to check whether the CPU usage is overhigh.

      • If so, go to step 6.
      • If not, go to step 7.

    4. Check the link between local and the remote router, and go to step 7.
    5. Modify the configurations based on the IS-IS protocol, and then check whether the neighbor is Up.

      • If so, go to step 8.
      • If not, go to step 7.

    6. Run the display current-configuration command to check the router configurations. Delete unnecessary configurations, and then check whether the neighbor is Up.

      • If so, go to step 8.
      • If not, go to step 7.

    7. Collect alarm information and configuration information, and then contact technical support personnel.
    8. End.
  • Cause 2: The physical interface went Down.
    1. Run the display isis interface command to check whether the router interface is Down.

      • If so, go to step 2.
      • If not, go to step 3.

    2. Modify the configurations, and then check whether the interface goes Up.

      • If so, go to step 4.
      • If not, go to step 3.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
  • Cause 3: Protocol reason.
    1. Run the display current-configuration command to check whether the local configurations are correct.

      • If so, go to step 3.
      • If not, go to step 2.

    2. Modify the local configurations, and then check whether the neighbor goes Up.

      • If so, go to step 6.
      • If not, go to step 5.

    3. Run the display cpu command to check whether the CPU usage is overhigh.

      • If so, go to step 4.
      • If not, go to step 5.

    4. Delete unnecessary configurations, and then check whether the neighbor is Up.

      • If so, go to step 6.
      • If not, go to step 5.

    5. Collect alarm information and configuration information, and then contact technical support personnel.
    6. End.
  • Cause 4: BFD detected that the neighbor went Down.
    1. Run the ping command to check whether the link between local and the remote router works properly.

      • If so, go to step 3.
      • If not, go to step 2.

    2. Check the link configuration.
    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
  • Cause 5: Configurations changed.
    1. Check whether a modified configuration affects the neighbor relationship establishment.

      • If so, go to step 2.
      • If not, go to step 4.

    2. Check whether the configuration modification is expected.

      • If so, go to step 5.
      • If not, go to step 3.

    3. Restore the configurations, and then check whether the neighbor is Up.

      • If so, go to step 5.
      • If not, go to step 4.

    4. Collect alarm information and configuration information, and then contact technical support personnel.
    5. End.
  • Cause 6: Peer router reason.
    1. Check whether the remote router is faulty.

      • If so, go to step 2.
      • If not, go to step 3.

    2. Rectify the faults of the remote router, and then check whether the neighbor is Up.

      • If so, go to step 4.
      • If not, go to step 3.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
Translation
Download
Updated: 2019-03-20

Document ID: EDOC1000166558

Views: 193800

Downloads: 113

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