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


To have a better experience, please upgrade your IE browser.


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_1. hwIsisSystemIdConflict

ISIS_1. hwIsisSystemIdConflict


ISIS/2/SYSTEM_ID_CONFLICT:OID [oid] System ID may conflict.(sysProcIndexofDyname=[integer], hwisisSysInstance=[integer], hwisisSysLevelIndex =[integer], OwnSystemId=[opaque], OwnDynamicName=[string], AdjSystemId=[opaque], AdjDynamicName=[string], LocalIP=[hwIsisLocalIP], AdjIP=[hwIsisAdjIP], RemoteIP=[hwIsisRemoteIP])

Intermediate System to Intermediate System (IS-IS) detected that system IDs conflicted.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


Index of the dynamic hostname of the local router


Conflicting system ID


Level of the process in which system IDs conflicted


System ID of the local router


Dynamic hostname of the local router


System ID of the neighbor


Dynamic hostname of the neighbor


Local IP address


IP address of a neighbor


IP address of the remote device with the conflicting system ID

Impact on the System

Link state protocol data units (LSPs) are frequently updated, and route flapping occurs.

Possible Causes

Two or more routers in the IS-IS area had the same system ID.


  1. View the OwnSystemId and hwisisSysInstance parameters in the alarm information to check whether the system ID of the local router is the same as the conflicting system ID.

    • If the system ID of the local router is the same as the conflicting system ID, change the system ID of the local router. Then check whether the alarm is cleared. If the alarm is cleared, go to step 4. If the alarm persists, go to step 3.

    • If the system ID of the local router is different from the conflicting system ID, go to step 2.

  2. Check the system IDs of other routers on the network, and change the system IDs that are the same as the conflicting system ID in the alarm information, or run the undo isis system-id auto-recover disable command to enable the device to automatically resolve IS-IS system ID conflicts.. Then check whether the alarm is cleared.

    • If the alarm is cleared, go to step 4.

    • If the alarm persists, go to step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 108286

Downloads: 68

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next