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.


Log Reference

AR500, AR510, and AR530 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.

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/6/GET_IF_FAILSMB:ISIS [process-id] failed to obtain the interface according to the interface index on the slave board. (InterfaceIndex=[STRING], MessageType=[STRING])


The IS-IS process on the slave board failed to obtain the interface according to the interface index.


Parameter Name Parameter Meaning


Indicates the ID of an IS-IS process.


Indicates the interface index.


Indicates the message type of LSPs:
  • Self LSP: indicates the self-originated LSPs.

  • Other LSP: indicates other LSPs.

  • AdjDelete: indicates neighbor information is deleted.

  • AdjHello: indicates the Hello message received by the slave board.

  • CircDis: indicates DIS information.

Possible Causes

1. The current interface on the slave board was inconsistent with the interface on the main board.

2. The backup interface index was incorrect.


  1. Run the display rm interface command to check whether the interface index on the main board is the same as that in the log.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. (Restart with caution.) You can restart the interface if services are not affected.

    • If so, go to Step 3.

    • If not, go to Step 4.

  3. Collect log information and configuration information, and then contact technical support personnel.
  4. End.
Updated: 2019-05-29

Document ID: EDOC1000097294

Views: 97172

Downloads: 35

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next