Hi Guys,
My 10 cents here.
Robo,
After I read all sorts of articles relating to VRF lite, VRF route leaks are not easily perform by export map with additive keyword. it can accept the RT exchange between VRFs via the first RT or original RT. As it is a form of VRF-lite, the extended communities are not exchanged by MPLS Core ( it is lack of "neighb xxxx send-community extended/both" under AF vpnv4 pointing towards core), the 2nd additive extended community RT should not be exported successfully. However, I have my half "successful" example there..... why....?
This is not true. whether its a VRF-Lite or a full blown L3 MPLS VPN, the way the communites work in BGP are the same. Allow me to explain a bit here.
With VRF-Lite although you dont have VPNV4 peering with another BGP speaker the route-targets still end up in the sAFI table(vpnv4) as these RT's are extended communities and must be available in MP-BGP to be picked up by other VRF's by using import option.
You would use the "neighb xxxx send-community" only when you have vpnv4 bgp peers . but in this since we are talking about VRF-Lite this is not needed unless these prefixes need to be transported to a another router elsewhere.
I have labbed this for you to show what I mean and pasting it here
R1#sh run
hostname R1
ip cef
ip vrf A
rd 100:1
route-target export 100:1
route-target import 100:1
route-target import 300:3
!
ip vrf B
rd 200:1
export map B-to-A
route-target export 200:1
route-target import 200:1
!
interface Loopback1
ip address 1.1.1.1 255.255.255.255
!
interface Loopback22
ip vrf forwarding B
ip address 22.22.22.22 255.255.255.255
!
interface GigabitEthernet2/0.10
encapsulation dot1Q 10
ip vrf forwarding A
ip address 10.1.1.1 255.255.255.0
!
interface GigabitEthernet2/0.20
encapsulation dot1Q 20
ip vrf forwarding B
ip address 20.1.1.1 255.255.255.0
!
router bgp 6500
no synchronization
bgp log-neighbor-changes
no auto-summary
!
address-family ipv4 vrf B
redistribute connected
no synchronization
exit-address-family
!
address-family ipv4 vrf A
redistribute connected
no synchronization
exit-address-family
access-list 10 permit 22.22.22.22
route-map B-to-A permit 10
match ip address 10
set extcommunity rt 300:3 additive
!
end
R1# sh ip bgp vpnv4 vrf B 22.22.22.22
BGP routing table entry for 200:1:22.22.22.22/32, version 8
Paths: (1 available, best #1, table B)
Not advertised to any peer
Local
0.0.0.0 from 0.0.0.0 (1.1.1.1)
Origin incomplete, metric 0, localpref 100, weight 32768, valid, sourced, best
Extended Community: RT:200:1 RT:300:3 <<< Has the additive RT added
mpls labels in/out 18/nolabel(B)
R1#
R1#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
22.0.0.0/32 is subnetted, 1 subnets
B 22.22.22.22 is directly connected, 00:12:58, Loopback22 << imported here
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.1.0 is directly connected, GigabitEthernet2/0.10
R1#
R1#sh ip route vrf B
Routing Table: B
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
20.0.0.0/24 is subnetted, 1 subnets
C 20.1.1.0 is directly connected, GigabitEthernet2/0.20
22.0.0.0/32 is subnetted, 1 subnets
C 22.22.22.22 is directly connected, Loopback22 <<<< Exporting this prefix
R1#
R1#sh route-map
route-map B-to-A, permit, sequence 10
Match clauses:
ip address (access-lists): 10
Set clauses:
extended community RT:300:3 additive <<< Additive keyword for exporting this to vpnv4 table
Policy routing matches: 0 packets, 0 bytes
R1#sh ip access-lists
Standard IP access list 10
10 permit 22.22.22.22 (2 matches)
R1#
BTW: Robo , I am just going thru your config now.
HTH
Kishore
