|
Contents
- BGP Event-Based VPN Import
- Finding Feature Information
- Prerequisites for BGP Event-Based VPN Import
- Information About BGP Event-Based VPN Import
- BGP Event-Based VPN Import
- Import Path Selection Policy
- Import Path Limit
- How to Configure BGP Event-Based VPN Import
- Configuring a Multiprotocol VRF
- Configuring Event-Based VPN Import Processing for BGP Paths
- Monitoring and Troubleshooting BGP Event-Based VPN Import Processing
- Configuration Examples for BGP Event-Based VPN Import
- Example: Configuring Event-Based VPN Import Processing for BGP Paths
- Additional References
- Feature Information for BGP Event-Based VPN Import
BGP Event-Based VPN Import
The BGP Event-Based VPN Import feature introduces a modification to the existing Border Gateway Protocol (BGP) path import process. The enhanced BGP path import is driven by events; when a BGP path changes, all of its imported copies are updated as soon as processing is available. Convergence times are significantly reduced because there is no longer any delay in the propagation of routes due to the software waiting for a periodic scanner time interval before processing the updates. To implement the new processing, new command-line interface (CLI) commands are introduced.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for BGP Event-Based VPN Import
Cisco Express Forwarding or distributed Cisco Express Forwarding must be enabled on all participating routers.
Information About BGP Event-Based VPN Import
BGP Event-Based VPN Import
The BGP Event-Based VPN Import feature introduces a modification to the existing BGP path import process. BGP Virtual Private Network (VPN) import provides importing functionality for BGP paths where BGP paths are imported from the BGP VPN table into a BGP virtual routing and forwarding (VRF) topology. In the existing path import process, when path updates occur, the import updates are processed during the next scan time which is a configurable interval of 5 to 15 seconds. The scan time adds a delay in the propagation of routes. The enhanced BGP path import is driven by events; when a BGP path changes, all of its imported copies are updated as soon as processing is available.
Using the BGP Event-Based VPN Import feature, convergence times are significantly reduced because provider edge (PE) routers can propagate VPN paths to customer edge (CE) routers without the scan time delay. Configuration changes such as adding imported route-targets to a VRF are not processed immediately, and are still handled during the 60-second periodic scanner pass.
Import Path Selection Policy
The BGP Event-Based VPN Import feature introduces three path selection policies:
- All--Import all available paths from the exporting net that match any Route Target (RT) associated with the importing VRF instance.
- Bestpath--Import the best available path that matches the RT of the VRF instance. If the bestpath in the exporting net does not match the RT of the VRF instance, a best available path that matches the RT of the VRF instance is imported.
- Multipath--Import the bestpath and all paths marked as multipaths that match the RT of the VRF instance. If there are no bestpath or multipath matches, then the best available path is selected.
Multipath and bestpath options can be restricted using an optional keyword to ensure that the selection is made only on the configured option. If the strict keyword is configured, the software disables the fall back safety option of choosing the best available path. If there are no paths appropriate to the configured option (bestpath or multipath) in the exporting net that match the RT of the VRF instance, then no paths are imported. This behavior matches the behavior of the software before the BGP Event-Based VPN Import feature was introduced.
When the restriction is not set, paths that are imported as the best available path are tagged. In show command output these paths are identified with the wording, "imported safety path."
The paths existing in an exporting net that are considered for import into a VRF instance may have been received from another peer router and were not subject to the VPN importing rules. These paths may contain the same route-distinguisher (RD) information because the RD information is local to a router, but some of these paths do not match the RT of the importing VRF instance and are marked as "not-in-vrf" in the show command output. Any path that is marked as "not-in-vrf" is not considered as a bestpath because paths not in the VRF appear less attractive than paths in the VRF.
Import Path Limit
To control the memory utilization, a maximum limit of the number of paths imported from an exporting net can be specified per importing net. When a selection is made of paths to be imported from one or more exporting net, the first selection priority is a bestpath, the next selection priority is for multipaths, and the lowest selection priority is for nonmultipaths.
How to Configure BGP Event-Based VPN Import
- Configuring a Multiprotocol VRF
- Configuring Event-Based VPN Import Processing for BGP Paths
- Monitoring and Troubleshooting BGP Event-Based VPN Import Processing
Configuring a Multiprotocol VRF
Perform this task to configure a multiprotocol VRF that allows you to share route-target policies (import and export) between IPv4 and IPv6 or to configure separate route-target policies for IPv4 and IPv6 VPNs. In this task, only the IPv4 address family is configured, but we recommend using the multiprotocol VRF configuration for all new VRF configurations.
Note | This task is not specific to the BGP Event-Based VPN Import feature. |
DETAILED STEPS
Configuring Event-Based VPN Import Processing for BGP Paths
Perform this task to reduce convergence times when BGP paths change by configuring event-based processing for importing BGP paths into a VRF table. Two new CLI commands allow the configuration of a maximum number of import paths per importing net and the configuration of a path selection policy.
This task assumes that you have previously configured the VRF to be used with the VRF address family syntax. To configure a VRF, see the "Configuring a Multiprotocol VRF" section earlier in this module.
Complete BGP neighbor configuration is also assumed. For an example configuration, see the "Example: Configuring Event-Based VPN Import Processing for BGP Paths" section in this module.
DETAILED STEPS
Monitoring and Troubleshooting BGP Event-Based VPN Import Processing
Perform the steps in this task as required to monitor and troubleshoot the BGP event-based VPN import processing.
Only partial command syntax for the show commands used in this task is displayed. For more details, see the Cisco IOS IP Routing: BGP Command Reference.
DETAILED STEPS
Configuration Examples for BGP Event-Based VPN Import
Example: Configuring Event-Based VPN Import Processing for BGP Paths
In this example, a VRF (vrf-A) is configured and VRF forwarding is applied to Fast Ethernet interface 1/1. In address family mode, the import path selection is set to all and the number of import paths is set to 3. Two BGP neighbors are configured under the IPv4 address family and activated under the VPNv4 address family.
vrf definition vrf-A rd 45000:1 route-target import 45000:100 address-family ipv4 exit-address-family ! interface FastEthernet1/1 no ip address vrf forwarding vrf-A ip address 10.4.8.149 255.255.255.0 no shut exit ! router bgp 45000 network 172.17.1.0 mask 255.255.255.0 neighbor 192.168.1.2 remote-as 40000 neighbor 192.168.3.2 remote-as 50000 address-family ipv4 vrf vrf-A import path selection all import path limit 3 exit-address-family address-family vpnv4 neighbor 192.168.1.2 activate neighbor 192.168.3.2 activate end
Additional References
Technical Assistance
Description | Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for BGP Event-Based VPN Import
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for BGP Event-Based VPN Import |
Feature Name |
Releases |
Feature Information |
---|---|---|
BGP Event-Based VPN Import |
12.2(33)SRE 15.0(1)M 15.0(1)S Cisco IOS XE 3.1.0SG 15.0(1)SY 15.1(1)SG Cisco IOS XE 3.3SG |
The BGP Event-Based VPN Import feature introduces a modification to the existing Border Gateway Protocol (BGP) path import process. The enhanced BGP path import is driven by events; when a BGP path changes, all of its imported copies are updated as soon as processing is available. Convergence times are significantly reduced because there is no longer any delay in the propagation of routes due to the software waiting for a periodic scanner time interval before processing the updates. To implement the new processing, new command-line interface (CLI) commands are introduced. The following commands were introduced or modified: bgp scan-time, import path limit, import path selection, maximum-paths eibgp, maximum-paths ibgp, show ip bgp vpnv4. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.