04-16-2020 07:03 AM
I'm having a mental block with this. I understand that RD will make routes unique when you have two customers:
Cust A:
RD: 1:1
1:1:10.0.0.0/8
Cust B:
RD: 2:2
2:2:10.0.0.0/8
I understand that RT will tell the router which route to import into that VRF and can be used a way to leak routes from one VRF to another.
I do not understand WHEN the router sends these attributes. Does it only send for a VPNv4 neighbor with send-community-extended? If I have configuration for ipv4 VRF CUST_A, the RD and RT attributes, will not be sent between these peers, correct?
In this case, I can have configuration like this:
vrf CUST_A
RD 1:1
(no route-target)
vrf CUST_B
RD 2:2
and each VRF will get their appropriate prefixes from the neighbor, as long as each vrf BGP peer IP is different.
Solved! Go to Solution.
04-16-2020 08:13 AM
In the context of MPLS VPN, the RD is prepended to the actual prefix being announced to create the VPNv4 prefix. The route target is used to control the prefix import/export process, as you mentioned. You need MP BGP VPNv4 to be configured for this to append.
If you can have VRF locally configured without the BGP VPNv4 component. This would generally be referred to as VRF lite.
Regards,
04-16-2020 08:20 AM
04-16-2020 08:13 AM
In the context of MPLS VPN, the RD is prepended to the actual prefix being announced to create the VPNv4 prefix. The route target is used to control the prefix import/export process, as you mentioned. You need MP BGP VPNv4 to be configured for this to append.
If you can have VRF locally configured without the BGP VPNv4 component. This would generally be referred to as VRF lite.
Regards,
04-16-2020 08:20 AM
04-16-2020 10:15 AM
Awesome, thank you guys! Yes, I know when the traffic is transported across the MPLS backbone, it will get to the 3 or POP and then underneath will be the VPN label, I have seen this in wireshark. I understand now that the router will ONLY send append the prefix with the RD and send the RT extended community to an address-family vpnv4 (or v6) neighbor. So, configuring RT for a VRF that will peer over address-family ipv4 vrf CUST_A is pointless.
Thank you both so much, I feel very confident now! :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide