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

IS-IS Neighbor Relationships Fail to Be Established Between a Huawei NE40E-X3 and a ZTE M6000

Publication Date:  2019-07-17 Views:  66 Downloads:  0

Issue Description

Two routers are interconnected over transport devices.

A Huawei NE40E is interconnected with a other vendordevice M6000 over a level-3 MPLS VPN. IS-IS is used as the IGP.

It is found that the routing table does not contain the routes sent from the peer device through IS-IS.


Configuration of the NE40E:

version:V300R006C01SPC003

isis 100

 is-level level-2

 cost-style wide-compatible

 timer lsp-generation 1 50 50 level-2

 network-entity XX.XXXX.XXXX.XXXX

 is-name HWne40E-X3

 log-peer-change

 maximum load-balancing 8

 set-overload on-startup


Configuration of the M6000:

 Version information: M6000v2.00.20(1.21.2)

<isis>

router isis 100

  area XX

  system-id XXXX.XXXX.XXXX

  metric-style wide

  redistribute connected

  interface gei-0/2/0/12

    ip router isis

    ignore-mtu

  $

  interface loopback1

    ip router isis

!</isis>

Handling Process

1. Check that the local and peer devices can properly ping each other.

2. Run the display isis peer command to check that no neighbor relationship exists between the local and peer devices.

3. Run the display isis lsdb command to check that no topology information exists.

4. Check that the configurations are correct.

5. Enable the debugging function and obtain Hello packets of IS-IS to check whether the problem is caused by protocol incompatibility.

Root Cause

The data packet comparison shows that this problem is caused by a metric type inconsistency of IS-IS.

IS-IS has two metric types: narrow and wide. The default metric type of the NE40E is wide, and the default metric type of the M6000 is narrow. A device using the IS-IS with the metric type of narrow cannot communicate with a device using the IS-IS with the metric type of wide.

Solution

Two methods are available:

1. Change metric-style to narrow for IS-IS on the NE40E. This change, however, is not recommended because the specifications of the transmitted routes are high and the routes of the narrow type have poor compatibility.

2. (Recommended) Change metric-style to wide for IS-IS on the M6000. This method provides good compatibility.

Related configuration:

router isis 100

metric-style wide

END