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.


Configuration Guide - IP Unicast Routing

CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

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).
Improving the Maintainability of IS-IS

Improving the Maintainability of IS-IS


The administrator can improve the maintainability of IS-IS using either of the following methods:
  • Configuring IS-IS host name mapping: Through this function, the administrator can use a simple name to replace the system ID. After IS-IS host name mapping is configured, the dynamic name is displayed in the IS-IS information to replace the system ID when the display command is executed. This improves the maintainability of IS-IS networks.
  • Configuring IS-IS to add the POI TLV to a PURGE packet: When the value of the Remaining Lifetime field in an LSP packets is 0, this packet is invalid and called a PURGE packet. PURGE packets do not record information about the devices generating these packets. Therefore, when a network is faulty, the packet source cannot be located. To solve this problem, IS-IS can be configured to add the POI TLV to a PURGE packet so that the PURGE packet contains information about its generating device. If the dynamic host name function is configured locally, the host name TLV is also added to the PURGE packet to facilitate fault location.


  1. Run system-view

    The system view is displayed.

  2. Run isis [ process-id ]

    The IS-IS view is displayed.

  3. Configure IS-IS host name mapping.

    • Run is-name symbolic-name

      IS-IS dynamic host name mapping is configured and a host name is configured for the local device.

      This configuration is dynamic configuration. Therefore, the configured host name symbolic-name is advertised through an LSP to other IS-IS devices in the same area. When you use IS-IS display commands to view IS-IS information on other IS-IS devices, the system ID of the local device is replaced by the configured host name.

    • Run is-name map system-id symbolic-name

      IS-IS static host name mapping is configured and a host name is configured for the remote device.

      This configuration is static configuration and takes effect only on the local device. Therefore, the configured host name symbolic-name is not advertised through an LSP.

  4. (Optional) Run purge-originator-identification enable

    IS-IS is configured to add POI TLV to Purge packets. If a dynamic hostname has been configured for the local device, the hostname TLV is also added to the Purge packets.

  5. Run commit

    The configuration is committed.

Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 275416

Downloads: 161

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next