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

Feature Description - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Feature Description - VPN
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).
Application of MCEs on a Campus Network

Application of MCEs on a Campus Network

Networking Description

BGP/MPLS IP VPN, which can isolate users on a campus network, is complicated to deploy and expensive to maintain. Since the number of users to be isolated on a campus network is small, you can use the MCE multi-hop technology instead.

Figure 5-46 Networking diagram for MCEs on a campus network

As shown in Figure 5-46, devices at the access layer of the campus network are configured to function as MCEs. These MCEs connect to multiple VPNs and carry VPN routes. VPN routes can be exchanged between local and remote MCEs without using the carrier network. This networking mode offers the following benefits:
  • Simplified configuration

    MPLS or MP-BGP does not need to be configured.

  • Reduced costs

    PEs and Ps do not need to be deployed.

Feature Deployment

Routing protocols are deployed on the MCE multi-hop network as follows:
  1. The link between MCE1 and MCE2 is bound to a VPN and a routing protocol is configured on both ends of the link.

  2. Each link between an MCE and a site is bound to a VPN and a routing protocol is configured on both ends of these links.

  3. The route import function is configured on MCEs, if the routing protocol running between MCEs and sites is different than that running between the MCEs.

Route Transmission

Routes are transmitted as follows on the MCE multi-hop network for Site 1 and Site 2 to learn the routes of each other:
  1. Site 1 sends its VPN routes to MCE1. Upon receipt, MCE1 adds these routes to its VPN routing and forwarding table.

  2. MCE1 sends received routes to MCE2.

  3. Upon receipt, MCE2 determines whether the export RTs of these routes match its import RTs. If yes, MCE2 adds these routes to its VPN routing and forwarding table and sends them to Site 2.

Packet Forwarding

Packets are transmitted as follows on the MCE multi-hop network:
  1. Site 2 sends a packet destined for Site 1 to MCE2 after searching its local routing and forwarding table.

  2. Upon receipt, MCE2 searches the corresponding VPN routing and forwarding table based on the inbound interface of the packet and forwards the packet to MCE1.

  3. Upon receipt, MCE1 searches the corresponding VPN routing and forwarding table based on the inbound interface of the packet and forwards the packet to Site 1.

  4. Upon receipt, Site 1 checks the destination address of the packet and processes this packet normally after finding that the destination address is itself.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058940

Views: 16698

Downloads: 34

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