cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
12535
Views
0
Helpful
16
Replies

BGP VPNv4 route reflector not reflecting VRF routes

aprasad11
Level 1
Level 1

Hi Guys,

I have a question regarding VPNv4 route reflector.

I have router R1, R2 and R3. R2 is the vpnv4 route reflector.

I have created a vrf which has same RD, same Export and Import route targets in all 3 routers.

All routers are sending and receiving communities.

R2 who is the route reflector learns all VPNv4 routes from R1 and R3 but R3 does not pass R1 routes to R3

Should the VPNv4 route reflector be reflecting these routes between R1 and R2 ?

1 Accepted Solution

Accepted Solutions

Hi

it was a pleasure, please keep me posted.

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

View solution in original post

16 Replies 16

Hi

May I know your configuration? the route-reflector configuration should be under the Address family for the specific VRF. If the 3 routers are iBGP they should exchange prefixes. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Hi Julio,

i am not peering with other routers in VRF instead peering them with VPNv4.

Attached is my config.

Thank you

Could you please execute this command on R2

show bgp vpnv4 unicast all summary

Are these routers PE? usually Router-reflector is not need for a MPLS L3VPN environment, may I know the reason for this configuration?

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Yes all routers are PE except R2 who is only the router reflector.

The reason is i will add more PE routers later into the network and do not want a full mesh network instead peer all routers to the RR.

Below is your show result

show bgp vpnv4 unicast all summary
BGP router identifier 10.151.80.225, local AS number 3999
BGP table version is 6, main routing table version 6
3 network entries using 456 bytes of memory
3 path entries using 240 bytes of memory
2/2 BGP path/bestpath attribute entries using 304 bytes of memory
1 BGP extended community entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1024 total bytes of memory
BGP activity 3/0 prefixes, 3/0 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.151.80.227 4 38198 112 115 6 0 0 01:38:47 1
10.151.80.229 4 38198 111 114 6 0 0 01:38:38 1

Hi

The issue can be on the labeling, probably the prefixes from R1 and R3 are losing the MPLS Labels. 

Have you configured LDP on the interfaces between the 3 routers?




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Here my example where Router 1 is the RR Server:

R2 ---- R1 ---- R3

Router 1  (RR Server)

interface Loopback100
ip address 1.1.1.1 255.255.255.255
!
interface FastEthernet0/0
ip address 10.0.12.1 255.255.255.0
duplex auto
speed auto
mpls ip
!
interface FastEthernet0/1
ip address 10.0.13.1 255.255.255.0
duplex auto
speed auto
mpls ip
!
router ospf 100
mpls ldp autoconfig
log-adjacency-changes
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 100
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 2.2.2.2 remote-as 100
neighbor 2.2.2.2 update-source Loopback100
neighbor 3.3.3.3 remote-as 100
neighbor 3.3.3.3 update-source Loopback100
!
address-family vpnv4
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 send-community extended
neighbor 2.2.2.2 route-reflector-client
neighbor 3.3.3.3 activate
neighbor 3.3.3.3 send-community extended
neighbor 3.3.3.3 route-reflector-client
exit-address-family
!
ip forward-protocol nd
!

mpls ldp router-id Loopback100

Router 2

ip vrf A
rd 1:1
route-target export 1:1
route-target import 1:1

interface Loopback0
ip vrf forwarding A
ip address 2.2.2.2 255.255.255.255
!
interface Loopback100
ip address 2.2.2.2 255.255.255.255
!
interface FastEthernet0/0
ip address 10.0.12.2 255.255.255.0
duplex auto
speed auto
mpls ip
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
router ospf 100
mpls ldp autoconfig
log-adjacency-changes
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 100
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 1.1.1.1 remote-as 100
neighbor 1.1.1.1 update-source Loopback100
!
address-family vpnv4
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 send-community extended
exit-address-family
!
address-family ipv4 vrf A
no synchronization
network 2.2.2.2 mask 255.255.255.255
exit-address-family
!

mpls ldp router-id Loopback100

Router 3

ip vrf A
rd 1:1
route-target export 1:1
route-target import 1:1

interface Loopback0
ip vrf forwarding A
ip address 3.3.3.3 255.255.255.255
!
interface Loopback100
ip address 3.3.3.3 255.255.255.255
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
ip address 10.0.13.3 255.255.255.0
duplex auto
speed auto
!
router ospf 100
mpls ldp autoconfig
log-adjacency-changes
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 100
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 1.1.1.1 remote-as 100
neighbor 1.1.1.1 update-source Loopback100
!
address-family vpnv4
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 send-community extended
exit-address-family
!
address-family ipv4 vrf A
no synchronization
network 3.3.3.3 mask 255.255.255.255
exit-address-family

mpls ldp router-id Loopback100




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

thanks for sharing this .. 

Were you able to see 2.2.2.2 route in R3 VRF A?

Thanks 

Hi,

Yes, Im able. Please let me share the routing table from both routers. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

R2#sh ip route vrf A

Routing Table: A
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

2.0.0.0/32 is subnetted, 1 subnets
C 2.2.2.2 is directly connected, Loopback0
3.0.0.0/32 is subnetted, 1 subnets
B 3.3.3.3 [200/0] via 3.3.3.3, 00:00:06
R2#

R3#sh ip route vrf A

Routing Table: A
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

2.0.0.0/32 is subnetted, 1 subnets
B 2.2.2.2 [200/0] via 2.2.2.2, 00:00:08
3.0.0.0/32 is subnetted, 1 subnets
C 3.3.3.3 is directly connected, Loopback0
R3#

I recommend verify the MPLS Labels, Route-targets and the information you are advertising, remember if you are going to advertise a prefix from BGP the subnet mask must be the same on the routing table. 

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Thanks Julio.. I will check all this soon and revert.

Hi

it was a pleasure, please keep me posted.

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

thanks Julio was able to make this work

It was a pleasure my friend,

have a great day

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Thank you for your reply.

Below is my mpls forwarding table

R3

show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 Pop Label 10.151.80.227/32 0 Et0/0 202.1.1.1
17 Pop Label 10.151.80.225/32 0 Et0/3 10.151.80.33
18 Pop Label 10.151.80.4/30 0 Et0/3 10.151.80.33
Pop Label 10.151.80.4/30 0 Et0/0 202.1.1.1
19 Pop Label 3.3.3.3/32[V] 0 aggregate/ICT

R1

show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 Pop Label 10.151.80.225/32 0 Et0/3 10.151.80.6
17 Pop Label 10.151.80.32/30 0 Et0/3 10.151.80.6
Pop Label 10.151.80.32/30 0 Et0/0 202.1.1.2
18 Pop Label 10.151.80.229/32 0 Et0/0 202.1.1.2
19 Pop Label 1.1.1.1/32[V] 0 aggregate/ICT

R2

show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 Pop Label 10.151.80.227/32 0 Et0/1 10.151.80.5
17 Pop Label 10.151.80.229/32 542 Et0/0 10.151.80.34
18 Pop Label 202.1.1.0/30 0 Et0/1 10.151.80.5
Pop Label 202.1.1.0/30 0 Et0/0 10.151.80.34
19 Pop Label 2.2.2.2/32[V] 0 aggregate/ICT
20 19 1.1.1.1/32[V] 0 Et0/1 10.151.80.5
21 19 3.3.3.3/32[V] 0 Et0/0 10.151.80.34

Review Cisco Networking for a $25 gift card