Configure BGP Route Import/Export Settings
In BGP, you can implement an inter-virtual-router route leak by importing or exporting routes using the route target extended community of the destination and source virtual routers respectively. You can use a route map to filter the desired route targets instead of leaking the entire routing table. You can also leak the routes of global virtual router to user-defined virtual routers and vice versa.
-
You can configure BGP to leak routes between two user-defined virtual routers using the route target extended communities:
-
Tag the routes with the route targets from the source virtual router using route target export.
-
Import the routes that are matching the route targets in to the destination virtual router using route target import.
-
Optionally, you can filter routes from source virtual router or to destination virtual router using export or import route maps respectively. You can configure route map with match extended community list for filtering the routes. Similarly, you can configure route map with set extended community route targets to tag the routes with the route target extended community.
-
-
To import routes from the global virtual router to a user-defined virtual router, specify the IPv4/IPv6 route map in Global Virtual Router Import Route Map to import to the user-defined virtual router.
-
To export routes from a user-defined virtual router to the global virtual router, in addition to exporting the route targets, you can also specify the Global Virtual Router Export Route Map to export from the user-defined virtual router.
Before you begin
Procedure
Step 1 | On the Device Management page, click Routing. | ||
Step 2 | (For a virtual-router-aware device) From the virtual routers drop-down, choose the virtual router for which you are configuring BGP. | ||
Step 3 | Choose or IPv6. | ||
Step 4 | (Supported only for only virtual routers) Click Route Import/Export. | ||
Step 5 | In the Route Targets Import field, enter the route target extended community that you want to match for the routes to be imported. On deployment, the routes of the destination virtual router that matches this value is imported to the source virtual router's BGP table.
| ||
Step 6 | In the Route Targets Export field, enter the route target extended community to tag the source virtual router's routes with the route target value. On deployment, the routes of the source virtual router are tagged with this value.
| ||
Step 7 | Route maps help you to narrow down the routes to be shared instead of leaking the entire routing table. Route map filtering is applied on the list of routes that are obtained with the specified route target values: | ||
Step 8 | To share the routes between a user-defined virtual router and global virtual router, specify the route map under the Global Virtual Router:
| ||
Step 9 | Follow the procedure ( Step 3 to Step 8) to configure relevant BGP route import and export settings for other virtual routers as well. | ||
Step 10 | Click Save and Deploy. |
When the packets flow into the ingress virtual router, BGP imports the routes from the destination virtual routers that have the matching route target value and if a route map is also configured, the routes are further filtered and used to identify the best path routes for routing the packets.