08-25-2017 12:18 PM - edited 03-05-2019 09:02 AM
I will try to keep this as simple as possible. I'm configuring route injection at a site, taking a /24 and injecting /32's. Individual tunnel peerings with one /24 origin each has been successful. The problem arises with the peering to our colocation facility. This single peering is receiving all the /24 advertisements from the individualy peered sites. This has failed. Reasoning seems to be that once the first /24 in the configurations hits the route-map, the route map stops processing there. So the question is, is there a way to do multiple /24 to /32 injects on one inject configuration? Or do I have to do seperate injects for each /24 I receive from this tunnel peering? Continue clause does bot work on the aggregated route-map. I also tried doing one 10.80.0.0 /16 prefix, but that didn't work as well.
Basically it will process the first in the list (10.80.69.0/24) and stop there. Any workarounds? Thanks.
ip prefix-list COLO_ITSP_FULL permit 10.80.69.0/24
ip prefix-list COLO_ITSP_FULL permit 10.80.89.0/24
ip prefix-list COLO_ITSP_FULL permit 10.80.88.0/24
ip prefix-list COLO_ITSP_FULL permit 10.80.80.0/24
ip prefix-list COLO_ITSP_FULL permit 10.80.30.0/24
ip prefix-list COLO_ITSP_FULL permit 10.80.223.0/24 le 25
ip prefix-list COLO_ITSP_INJECT permit 10.80.69.10/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.10/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.12/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.14/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.16/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.17/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.18/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.89.19/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.88.10/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.88.12/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.80.10/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.80.12/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.80.14/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.80.16/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.30.141/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.30.142/32
ip prefix-list COLO_ITSP_INJECT permit 10.80.223.20/32
ip access-list standard COLO_SOURCE
permit host 10.90.100.18
route-map COLO_ITSP_AGGREGATED permit 10
match ip address prefix-list COLO_ITSP_FULL
match ip route-source COLO_SOURCE
route-map COLO_ITSP_SPECIFIC permit 15
set ip address prefix-list COLO_ITSP_INJECT
router bgp x.x.x.x
bgp inject-map COLO_ITSP_SPECIFIC exist-map COLO_ITSP_AGGREGATED copy attributes
Solved! Go to Solution.
08-25-2017 02:01 PM
Hello,
unless something has changed in this feature, you can only specify one aggregate route in your exist-map. That is probably why it stops after the first line.
So yes, you need one exist-map/inject-map configs for each aggregate, you cannot do it in a single one.
08-25-2017 02:01 PM
Hello,
unless something has changed in this feature, you can only specify one aggregate route in your exist-map. That is probably why it stops after the first line.
So yes, you need one exist-map/inject-map configs for each aggregate, you cannot do it in a single one.
08-26-2017 06:23 PM - edited 08-26-2017 06:27 PM
OK, thanks. Just wanted to make sure there wasn't a workaround. The good news is I did not have to do the full configs as I could pull prefix-lists from the previous individual site peerings. Just had to do a new aggragated route-map with a new source, and a new exist/inject command in BGP configs. Wasn't so bad. Thanks again.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: