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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Maintaining IS-IS

Maintaining IS-IS

Resetting IS-IS

Context

To reset IS-IS, reset IS-IS data structure, neighbor relationship and packets

The IS-IS data structure cannot be restored after you reset it. All the previous structure information and the neighbor relationship are reset. Exercise caution when running this command.

The specified IS-IS neighbor relationship is deleted after you reset a specified IS-IS neighbor. Exercise caution when running this command.

Procedure

  • Reset IS-IS data structure.

    Run the reset isis all[ process-id | vpn-instance vpn-instance-name ] command to reset IS-IS data structure.

  • Reset IS-IS neighbor relationship.

    Run the reset isis peer system-id [ process-id | vpn-instance vpn-instance-name ] command to reset a specific IS-IS neighbor.

    After the IS-IS routing policy or the protocol changes, you can reset a specific IS-IS neighbor to validate the new configuration.

  • Reset IS-IS packets

    Run the reset isis error [ process-id | vpn-instance vpn-instance-name ] or reset isis error interface interface-type interface-number command to clear information about incorrect LSPs and Hello packets received by the specified interface or process.

    Run the reset isis statistics packet [ interface [ interface-type interface-number ] ] or reset isis process-id statistics packet command to clear IS-IS packet statistics on the specified interface or process.

Suppressing IS-IS

Context

By suppressing IS-IS, you can disable an IS-IS process temporarily without affecting the IS-IS configuration.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    isis [ process-id ]

    An IS-IS process is created, and the IS-IS view is displayed.

  3. Run:

    shutdown

    The IS-IS process is disabled temporarily.

    After the IS-IS process is disabled temporarily, you can still perform the IS-IS configuration but the configuration does not take effect. You can run the undo shutdown command to cancel the suppression.

  4. Run:

    commit

    The configuration is committed.

Improving the Maintainability of IS-IS

Context

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.

Procedure

  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.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59819

Downloads: 3623

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