topic route-table unicast appear after adding new prefix in BGP export filter in General Topics

route-table unicast appear after adding new prefix in BGP export filter

ShanVD — Tue, 22 Sep 2020 14:55:45 GMT

Hi,

We have an existing BGP peer session to our service provider advertising a few prefixes which has been working fine. I have recently added a new prefix (/24) which statically routed to our internal switch, all our static routes are redistributed into BGP and they are learnt by our service provider router. I have added this new prefix onto our PA's existing BGP export filter list like other prefixes we currently advertise, for some strange reason, an additional config line "route-table unicast" is added to the end of the filter list when I do a "preview changes".

Any ideas? Will this break anything? Thanks.

Re: route-table unicast appear after adding new prefix in BGP export filter

rmfalconer — Tue, 22 Sep 2020 15:42:32 GMT

That's an expected part of the entry. When you create a static route, it can to be put in a routing table, unicast or multicast (or both).

If you look at your current static routes at the CLI or GUI, you should see this defined. Unicast is the default so you don't actually have to select anything when you create a static route.

So the filter list needs to know which route table to reference to find the matching prefix. Check your current export rules in the CLI and you should see the entry for the route table on each of them. It will look something like this:

set network virtual-router default protocol bgp policy export rules <rulename> match route-table unicast