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

Announcements

ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

Reply
Highlighted
L0 Member

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

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.


Accepted Solutions
Highlighted
L4 Transporter

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

View solution in original post


All Replies
Highlighted
L4 Transporter

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

View solution in original post

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!