VRF routes are learned but bgp adjacency remains in the idle state

[r-karamad]

Hello, i have a problem with configuring MPLS L3 VPN on ASR9006.

I see on PE routers that VRF routes are learned but when i check the adjacency state, it's in the idle state.

RP/0/RSP0/CPU0:PE_SDG#sho route vrf INTERNET 
...

C    172.20.50.36/30 is directly connected, 1d02h, TenGigE0/0/0/1
L    172.20.50.37/32 is directly connected, 1d02h, TenGigE0/0/0/1
B    192.168.172.0/25 [200/0] via 172.20.50.6 (nexthop in vrf default), 00:24:01

RP/0/RSP0/CPU0:PE_SDG#sho bgp vrf INTERNET summary 
...
BGP is operating in STANDALONE mode.

Process       RcvTblVer   bRIB/RIB   LabelVer  ImportVer  SendTblVer  StandbyVer
Speaker              88         88         88         88          88          88

Neighbor             Spk    AS        MsgRcvd     MsgSent   TblVer  InQ   OutQ    Up/Down   St/PfxRcd
172.20.50.6         0        100       0                  0               0           0      0           00:00:00    Idle

This is my VRF and BGP configuration on both sides:

RP/0/RSP0/CPU0:GW_NZ#sho run vrf
Sun Jul 12 07:34:33.152 UTC
vrf INTERNET
 address-family ipv4 unicast
  import route-target
   100:10
  !
  export route-target
   100:10
  !
 !
!

RP/0/RSP0/CPU0:GW_19dey#sho run router bgp
Sun Jul 12 07:35:13.268 UTC
router bgp 100
 address-family ipv4 unicast
 !
 address-family vpnv4 unicast
 !
 neighbor-group INTERNAL
  remote-as 100
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
  address-family vpnv4 unicast
   route-reflector-client
  !
 !
 neighbor 172.20.50.14
  use neighbor-group INTERNAL
 !
 vrf INTERNET
  rd 100:10
  address-family ipv4 unicast
   redistribute connected
  !
  neighbor 172.20.50.14
   remote-as 100
   update-source Loopback0
   address-family ipv4 unicast
   !
  !
 !
!

RP/0/RSP0/CPU0:PE_SDG#sh run vrf 
Sun Jul 12 08:37:38.512 UTC
vrf INTERNET
 address-family ipv4 unicast
  import route-target
   100:10
  !
  export route-target
   100:10
  !
 !
!

RP/0/RSP0/CPU0:PE_SDG#sho run router bgp
Sun Jul 12 08:38:16.363 UTC
router bgp 100
 address-family ipv4 unicast
 !
 address-family vpnv4 unicast
 !
 neighbor 172.20.50.6
  remote-as 100
  update-source Loopback0
  address-family ipv4 unicast
  !
  address-family vpnv4 unicast
  !
 !
 vrf INTERNET
  rd 100:10
  address-family ipv4 unicast
   redistribute connected
  !
  neighbor 172.20.50.6
   remote-as 10
   update-source Loopback0
   address-family ipv4 unicast
   !
  !
 !
!

Thanks in advance.

[Fredrik Lönnman]

Since the neighbor is IDLE, the prefix has to come from somewhere else but pointing to that next hop. You can probably figure this out via the output from show bgp vpnv4 unicast vrf INTERNET 192.168.172.0/25

[r-karamad]

Thank you for the answer.

I use "show bgp vrf X summary" for checking MP-BGP adjacency while this command is used for checking CE-PE BGP adjacency.

[Florian Frotzler]

Hi,

The configuration is clearly wrong, the neighbor statement is the same for the global peering as well es the VRF peering. So I think either this is a copy/paste error or the concept of VPNv4 was misunderstood. While the peering IP address and the remote AS might in theory be overlapping, at least the update source interface is clearly wrong as loopback0 cannot be in the global table and the VRF at the same time.

Florian