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

ISIS-STD_1.3.6.1.2.1.138.0.17 isisAdjacencyChange

Description

ISIS-STD/2/ADJ_CHANGE:OID [oid] The state of IS-IS adjacency changed. (NotificationSysLevelIndex=[integer], CircuitIfIndex=[integer], LspID=[opaque], AdjState=[integer])

The status of the IS-IS neighbor relationship changed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.17

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NotificationSysLevelIndex

IS-IS level of a device that sends the trap

CircuitIfIndex

Interface index

LspID

LSP ID

AdjState

Neighbor relationship status

Impact on the System

IS-IS may recalculate routes, which causes route flapping and interrupts IS-IS services.

Possible Causes

Cause 1: The IS-IS neighbor relationship went Up or Down.

Cause 2: IS-IS configurations were incorrect.

Cause 3: The system was busy.

Cause 4: A link fault occurred.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, check the LspID field value (in hexadecimal) and obtain the system ID of the source router. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 12.

    • If the neighbor relationship states on the two ends are different, go to Step 2.

  2. Download user logs from the source router, and check whether the neighbor relationship status changes because the interface status becomes Down.

    • If the neighbor relationship status changes because the interface status becomes Down, go to Step 3.

    • If the neighbor relationship status changes due to other reasons, go to Step 10.

  3. Search the logs for information about the local interface and check the interface status and MTU status on the interface. Ensure that both the interface status and MTU status on two ends are Up. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 4.

  4. Check the system IDs and ensure that the system IDs on the two ends are correct. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 5.

  5. Check the levels of IS-IS processes and ensure that levels on the two ends match. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 6.

  6. Check the area ID of the router and ensure that area IDs on the two ends are the same. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 7.

  7. Check that IP addresses of interfaces on the two ends belong to the same network segment. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 8.

  8. Check whether the authentication mode is configured on the two ends and ensure that the encryption authentication modes on the two ends are the same. If authentication is required, ensure that the authentication modes and passwords on the two ends are the same. Otherwise, authentication is disabled on the two ends (disabling authentication degrades the system security). Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 9.

  9. Check that interfaces on the two ends can transmit Hello packets properly, and then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 10.

  10. Run the display cpu-usage command to check whether the CPU usage remains 100% for a period of time.

    • If the CPU usage remains 100% for a period of time, go to Step 11.

    • If the CPU usage does not remain 100% for a period of time, go to Step 12.

  11. Run the isis timer hello command in the interface view to set a longer interval at which Hello packets are sent. The interval can be prolonged by 10s each time. Prolonging the interval at which Hello packets are sent slows down network fault detection and therefore slows down route convergence. Then check whether the neighbor relationship states on the two ends are the same.

    • If the neighbor relationship states on the two ends are the same, go to Step 13.

    • If the neighbor relationship states on the two ends are different, go to Step 12.

  12. Collect alarm information and configuration information, and then contact technical support personnel.
  13. End.

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 70246

Downloads: 45

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