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.


Failed to Discover BGP MPLS VPN Services After NE40E Is Added to eSight

Publication Date:  2019-07-04 Views:  102 Downloads:  0

Issue Description

eSight Network is deployed at a site. After NE40E is added to eSight and BGP MPLS VPN service discovery is performed, eSight cannot discover services.

Handling Process

Perform the following operations:

1. Verify that SNMP parameters are correct on eSight.

2. Verify that eSight is adapted to NE40E.

3. Verify that the license item for the BGP MPLS VPN service is available on eSight.

4. Prolong the timeout interval of the SNMP protocol.

After the preceding steps are performed, services still cannot be discovered. The collected information shows that:

Duplicate data exists on the device (peer neighbors learned by DCN-Serial6/0/22:0 and DCN-Serial1/0/0:0 are both eSight considers that the discovered VPN data is abnormal and discards the data.

The two neighbors in the following figure belong to the OSPF.

Process 65534 with Router ID 128.XX.XX.131

Root Cause

The DCN function is enabled on the NE by default. After the DCN function is disabled on NE40E, the problem is solved.

Disable the DCN globally.