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).
Common Configuration Errors

Common Configuration Errors

This section describes common faults caused by incorrect IS-IS configurations and provides the troubleshooting procedure.

Failed to Establish IS-IS Neighbor Relationships

Fault Symptom

IS-IS neighbor relationship fails to be established when the link is working properly.

Procedure

  1. Check whether devices on both ends of the link have the matching IS-IS levels.

    • Run the display current-configuration configuration isis | include is-level command to check the level configurations of IS-IS processes on both ends.
    • Run the display current-configuration interface interface-type interface-number | include isis circuit-level command to check the IS-IS level configuration of the specified interface.

    IS-IS neighbor relationship can be established when IS-IS interfaces on both ends of the link have the matching IS-IS levels.

    NOTE:

    If you cannot view the IS-IS level of an interface using the display current-configuration interface interface-type interface-number | include isis circuit-level command, the interface uses the default IS-IS level. To view the default IS-IS level, run the display default-parameter isis command to check the Circuit-Level field.

    Requirements on the IS-IS levels of interfaces on both ends of a link are as follows:
    • If the IS-IS level of the local interface is Level-1, the IS-IS level of the remote interface must be Level-1 or Level-1-2.

    • If the IS-IS level of the local interface is Level-2, the IS-IS level of the remote interface must be Level-2 or Level-1-2.

    • If the IS-IS level of the local interface is Level-1-2, the IS-IS level of the remote interface can be Level-1, Level-2, or Level-1-2.

    If the IS-IS levels of interfaces on both ends of a link do not match, perform either of the following operations to change the IS-IS level:
    • Run the is-level command in the IS-IS view to change the global IS-IS level.
    • Run the isis circuit-level command in the interface view to change the interface IS-IS level.

  2. Check whether devices on both ends of the link have the matching area addresses.

    Run the display current-configuration configuration isis command to check area address information.

    NOTE:

    If IS-IS Level-1 neighbor relationship needs to be established between devices on both ends, ensure that the two devices reside in the same area.

    A maximum of three area addresses can be configured for an IS-IS process. Devices on both ends can establish IS-IS Level-1 neighbor relationship when the two devices have a same area address.

    When IS-IS Level-2 neighbor relationship needs to established between the two devices, the two devices can have the same or different area addresses.

    If the area addresses of the two devices are different, run the network-entity command in the IS-IS view to set the same area address for the two devices.

  3. Check whether devices on both ends of the link have the authentication mode.

    Run the display current-configuration interface interface-type interface-number | include isis authentication-mode command to check the IS-IS authentication modes of the interfaces on both ends of the link.

    If the two interfaces use different authentication modes, run the isis authentication-mode command in the view of one interface to ensure that this interface has the same authentication mode and password as the other interface.

  4. Run:

    commit

    The configuration is committed.

A Device Cannot Learn IS-IS Routes from Its Neighbor

Fault Symptom

A device cannot learn IS-IS routes from its neighbor when its link is working properly.

Procedure

  1. Check whether IS-IS neighbor relationship has been established between the device and its neighbor.

    Run the display isis peer command on each device on the link to check whether IS-IS neighbor relationship has been established.

    If IS-IS neighbor relationship is not established, rectify the fault according to Failed to Establish IS-IS Neighbor Relationships.

  2. Check whether the IS-IS routing table of the device is correct.

    Run the display isis route command on the device to check the IS-IS routing table.

    1. If the IS-IS routing table contains specified routes, run the display ip routing-table ip-address [ mask | mask-length ] verbose command to check whether the IP routing table contains routes with higher protocol preference than IS-IS routes.
      NOTE:

      If the State field of a route displays Active Adv, the route is active. If there are routes that have the same prefix but are discovered by different routing protocols, routes with higher protocol preference are preferred as active routes.

    2. If the IP routing table contains routes with higher protocol preference than IS-IS routes, modify the configuration based on network planning.

  3. Check whether the device and its neighbor have the matching IS-IS cost style.

    Run the display current-configuration configuration isis command on the device and its neighbor to check the IS-IS cost style.

    NOTE:

    The device can learn IS-IS routes from its neighbor when it has the same IS-IS cost style as its neighbor.

    The IS-IS cost style of a device can be set as follows:
    • narrow: indicates that the device can receive and send packets with cost style narrow.

    • narrow-compatible: indicates that the device can receive packets with cost style narrow or wide but sends only packets with cost style narrow.

    • compatible: indicates that the device can receive and send packets with cost style narrow or wide.

    • wide-compatible: indicates that the device can receive packets with cost style narrow or wide but sends only packets with cost style wide.

    • wide: indicates that the device can receive and send packets with cost style wide.

    If the IS-IS cost styles of both ends are set to narrow and wide (or wide-compatible) respectively, the two ends cannot communicate.

    If the IS-IS cost styles of both ends are set to narrow-compatible and wide respectively, the two ends cannot communicate either.

    If the device and its neighbor have mismatching IS-IS cost styles, run the cost-style command on the device to modify the configuration.

  4. Run:

    commit

    The configuration is committed.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59713

Downloads: 3623

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