ASR9K Route leaking between GRT and VRF

Youn88 · ‎05-31-2021

Hello,

I would like to leak a prefix (loopback) from the GRT to a VRF than advertise it in the L3VPN but it doesn't work:

asr9901-1:

interface Loopback36
ipv4 address 36.36.36.36 255.255.255.255

RP/0/RSP0/CPU0:asr9901-1#show route 36.36.36.36
Mon May 31 14:46:24.133 GMT+1

Routing entry for 36.36.36.36/32
Known via "local", distance 0, metric 0 (connected)
Installed May 31 14:11:36.427 for 00:34:48
Routing Descriptor Blocks
directly connected, via Loopback36
Route metric is 0
No advertising protos.

RP/0/RSP0/CPU0:asr9901-1(config)#prefix-set only_prefix_36.36.36.36
RP/0/RSP0/CPU0:asr9901-1(config-pfx)#36.36.36.36/32

RP/0/RSP0/CPU0:asr9901-1(config)#route-policy rpl_only_36.36.36.36
RP/0/RSP0/CPU0:asr9901-1(config-rpl)#if destination in only_prefix_36.36.36.36 then
RP/0/RSP0/CPU0:asr9901-1(config-rpl-if)#pass
RP/0/RSP0/CPU0:asr9901-1(config-rpl-if)#else
RP/0/RSP0/CPU0:asr9901-1(config-rpl-else)#drop
RP/0/RSP0/CPU0:asr9901-1(config-rpl-else)#endif
RP/0/RSP0/CPU0:asr9901-1(config-rpl)#end-policy

RP/0/RSP0/CPU0:asr9901-1(config)#vrf equi_asr9k_
RP/0/RSP0/CPU0:asr9901-1(config-vrf)#address-family ipv4 unicast
RP/0/RSP0/CPU0:asr9901-1(config-vrf-af)#import from default-vrf route-policy rpl_only_36.36.36.36

Vérification:

RP/0/RSP0/CPU0:asrhaut9901-1#show route vrf equi_asr9k 36.36.36.36
Mon May 31 14:44:18.678 GMT+1

% Network not in table

RP/0/RSP0/CPU0:asrhaut9901-1#show bgp vpnv4 unicast vrf equi_asr9k advertised neighbor 13.13.13.13 summary
Mon May 31 14:52:44.051 GMT+1
Network Next Hop From AS Path
Route Distinguisher: 1:1
10.10.10.11/32 4.4.4.4 Local i
11.11.11.0/24 4.4.4.4 Local ?
11.11.11.12/32 4.4.4.4 Local ?
20.20.20.0/24 4.4.4.4 100.11.11.2 41127 41127i
88.88.88.88/32 4.4.4.4 Local i
100.7.7.0/30 4.4.4.4 Local ?
100.11.11.0/24 4.4.4.4 Local ?
177.77.77.77/32 4.4.4.4 Local ?

Why the prefix 36.36.36.36 don't appear in VRF equi_asr9k ?

smilstea · ‎05-31-2021

Can you check your vrf BGP table that the route is there before we check if its advertised?

As for why its not advertised you need the advertise-as-vpn keyword.

Also in the above you added a '_' to the end of the vrf name, so please double check the vrf config that it was the proper import statement.

https://community.cisco.com/t5/xr-os-and-platforms/asr9k-leak-bgp-route-between-vrf-and-global/td-p/2490736

https://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4-3/routing/configuration/guide/b_routing_cg43xcrs/b_routing_cg43xcrs_chapter_010.html#concept_9961DC067F854EEDA4AA461A9EBE2DBD

Sam