export route-policy (VPN instance view)

Usage Scenario

To advertise the routes of a VPN instance IPv4 address family in a way more precise than the way based on the extended community attribute, use the export route-policy. The export route-policy is used to filter the routing information and to set the routing attributes of the routes that pass the filtering.

The export route-policy command advertises the local routes of a VPN instance IPv4 address family to other VPN instances IPv4 address families. The peer route-policy command or the filter-policy command run in the BGP VPN instance IPv4 address family view filters the routes of a VPN instance IPv4 address family advertised to or received from CE neighbors.

By default, ERTs are added to VPN routes after these routes are matched against an export routing policy. If the export routing policy contains RT-related filtering rules, these rules cannot apply to these routes. If you want to apply the RT-related filtering rules defined in an export routing policy to VPN routes, run the add-ert-first command to configure the system to add ERTs to VPN routes before matching these routes against the export routing policy.

In local cross scenarios, you can run the export route-policy command to filter out locally crossed routes and set the attributes of these routes. Locally crossed routes include both locally imported routes and routes learned from VPN peers.

Prerequisites

If the export route-policy to be associated with a VPN instance IPv4 address family does not exist, configure the export route-policy first.

Configuration Impact

The current VPN instance IPv4 address family can be associated with only one export route-policy. If the export route-policy command is run more than once, the latest configuration overrides the previous one.