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
Knowledge Base

NE40E-X8 and Ventor ASR9000 Fail to Learn Routes from Each Other After an EBGP Peer Relationship Is Set Up

Publication Date:  2019-07-17  |   Views:  331  |   Downloads:  0  |   Document ID:  EKB1100015041

Contents

Issue Description

A Huawei NE40E-X8 and a Ventor ASR9000 are interconnected through bundled interfaces, and MP-EBGP runs between the two devices. The EBGP peer relationship can be properly set up, but neither the NE40E-X8 or ASR9000 can learn routes from the peer. No logs or alarms are generated.

The configuration of the ASR9000 is as follows (sensitive information such as the IP address have been changed):

vrf vpn1
 address-family ipv4 unicast
  import route-target
   1:1

 !
  export route-target
   1:1

interface Bundle-Ether101
 description link-to-NE40E_A1
 mtu 1530
 ipv4 address x.x.1.10 255.255.255.252

interface Loopback0
 ipv4 address x.x.0.231 255.255.255.255
!
interface Loopback1
 vrf vpn1
 ipv4 address x.x.1.231 255.255.255.255

 neighbor x.x.1.9
  remote-as 64530
  address-family ipv4 unicast
  !
  address-family vpnv4 unicast

 vrf vpn1
  rd 1:1
  address-family ipv4 unicast
   redistribute connected


The configuration of the NE40E-X8 is as follows:

ip vpn-instance VPN1
 ipv4-family
  route-distinguisher 1:1
  vpn-target 1:1 export-extcommunity
  vpn-target 1:1 import-extcommunity

#

interface Eth-Trunk2
 description Eth-Trunk2_<SPZW_Ventor_A1>_port-channel0
 ip address x.x.1.9 255.255.255.252
 mode lacp-static
 mpls
#

interface LoopBack0
 ip address x.x.0.1 255.255.255.255
#
interface LoopBack1
 ip binding vpn-instance VPN1
 ip address x.x.0.21 255.255.255.255

bgp 64530
 router-id x.x.0.1
 peer 200.0.1.10 as-number 64520
 #
 ipv4-family unicast
  undo synchronization
  peer x.x.1.10 enable
 #
 ipv4-family vpnv4
  undo policy vpn-target
  auto-frr
  peer x.x.1.10 enable

 ipv4-family vpn-instance VPN1
  network x.x.0.21 255.255.255.255 

Handling Process

1. Ping the IP address of the direct connect interfaces on the two devices. The ping operation succeeds.

2. Check BGP peer information on the two devices. It is found that the BGP peer relationship is properly set up between the two devices.

3. Check the BGP routing table and VPNv4 routing table on the two devices. It is found that both of the devices fail to learn routes from the peer device.

4. Obtain packet header information on the interconnection link. It is found that the NE40E-X8 has sent BGP routes to the ASR9000 but the ASR9000 has not sent BGP routes to the NE40E-X8. This indicates that the ASR9000 has not sent BGP route updates to the NE40E and the ASR9000 has received BGP routes from the NE40E-X8 but does not accepted the routes.

Root Cause

According to the ASR9000 configuration and the description of BGP in ASR9000 product documents, it is found that the high-end Ventor router ASR9000 is designed for BGP (regardless of common BGP or MP-BGP). By default, the ASR9000 does not send or receive BGP route updates. The ASR9000 can send and receive BGP routes only after the associated rules are configured.

Solution

Configure rules for sending and receiving BGP routes on the ASR9000. To allow the ASR9000 to send and receive all routes, perform the following configurations:

route-policy BGP
  pass
end-policy

 neighbor x.x.1.9
  remote-as 64530
  address-family ipv4 unicast
   route-policy BGP in
   route-policy BGP out
  !
  address-family vpnv4 unicast
   route-policy BGP in
   route-policy BGP out
  !