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


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


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).


If multiple CEs in a VPN site access different PEs, VPN routes sent from CEs to PEs may return to this VPN site after traveling across the backbone network. This may cause routing loops in the VPN site.

After the SoO attribute is configured on a PE, the PE adds the SoO attribute to the route sent from a CE and then advertises the route to other PE peers. Before advertising the VPN route to the connected CE, the PE peers check the SoO attribute carried in the VPN route. If the PE peers find that this SoO attribute is the same as the locally configured SoO attribute, the PE peers do not advertise this VPN route to the connected CE.

On the network shown in Figure 5-40, CE1 and CE2 belong to the same VPN site and can advertise routes to each other. CE1 advertises the route destined for in the VPN site to PE1, and PE1 advertises the route to PE2 by using Multiprotocol Internal Border Gateway Protocol (MP-IBGP). PE2 then advertises the route to CE2 by using BGP. As a result, the route returns to the original VPN site from which the route is advertised, which may cause a routing loop in the VPN site.

Figure 5-40 Networking diagram for BGP SoO application

To avoid routing loops in a VPN site, you can configure an SoO attribute on PE1 for CE1. The SoO attribute identifies the site where the CE1 resides. The routes advertised by CE1 to PE1 then carry this SoO attribute, and PE1 advertises the routes with the SoO attribute to PE2 across the backbone network. Before advertising the received routes to its peer CE2, PE2 checks whether the routes carry the SoO attribute specified for the site where CE2 resides. If a route carries this SoO attribute, this route is advertised from the site where CE2 resides. PE2 then refuses to advertise such a route to CE2, avoiding routing loops in the site.

Updated: 2019-01-14

Document ID: EDOC1100058940

Views: 16773

Downloads: 34

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