No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

ME60 V800R010C10SPC500 Feature Description - WAN Access 01

This is ME60 V800R010C10SPC500 Feature Description - WAN Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
BGP VPN Route Crossing

BGP VPN Route Crossing

Route crossing refers to the process of adding a BGP VPN route to the routing table of the local or remote VPN instance in a BGP/MPLS IP VPN scenario. Route crossing can be classified as local route crossing and remote route crossing based on the source of the BGP VPN route.
  • Remote route crossing: After a PE receives a BGP VPNv4 route from a remote PE, the local PE matches the export target (ERT) of the route against the import targets (IRTs) configured for local VPN instances. If the ERT matches the IRT of a local VPN instance, the PE converts the BGP VPNv4 route to a BGP VPN route and adds the BGP VPN route to the routing table of this local VPN instance.

  • Local route crossing: A PE matches the ERT of a BGP VPN route in a local VPN instance against the IRTs configured for other local VPN instances. If the ERT matches the IRT of a local VPN instance, the PE adds the BGP VPN route to the routing table of this local VPN instance. Locally crossed routes include both locally imported routes and routes learned from VPN peers.

After a PE receives VPNv4 routes destined for the same IP address from another PE or VPN routes from a CE, the local PE implements route crossing by following the steps in Figure 9-14.
Figure 9-14 Flowchart for BGP VPN route crossing

In Figure 9-15, PEs have the same VPN instance (vpna) and RTs (including the ERT and IRT). The RD configured for PE2 and PE3 is 2:2, and the RD configured for PE4 is 3:3. Site 2 has a route destined for 10.1.1.0/24. The route is sent to PE2, PE3, and PE4, who convert this route to multiple BGP VPNv4 routes and send them to PE1. On receipt of the BGP VPNv4 routes, PE1 implements route crossing as shown in Figure 9-16. The detailed process is as follows:
  1. After receiving the BGP VPNv4 routes from PE2, PE3, and PE4, PE1 adds them to the BGP VPNv4 routing table.

  2. PE1 converts the BGP VPNv4 routes to BGP VPN routes by removing their RDs, adds the BGP VPN routes to the routing table of the VPN instance, selects an optimal route from the BGP VPN routes based on BGP route selection policies, and adds the optimal BGP VPN route to the IP VPN instance routing table.

Figure 9-15 Route crossing networking

Figure 9-16 BGP VPN route crossing process

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059473

Views: 14313

Downloads: 10

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next