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.


Command Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.

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

peer soo


The peer soo command configures the Site of Origin (SoO) attribute for an EBGP peer in a BGP VPN instance.

The undo peer soo command deletes the SoO.

By default, no SoO attribute is configured for an EBGP peer in a BGP VPN instance.


CE6810LI series do not support this command.


peer { group-name | ipv4-address | ipv6-address } soo site-of-origin

undo peer { group-name | ipv4-address | ipv6-address } soo


Parameter Description Value
group-name Specifies the name of a BGP peer group. The name is a string of 1 to 47 case-sensitive characters except spaces. When double quotation marks are used to include the string, spaces are allowed in the string.
ipv4-address Specifies the IPv4 address of a BGP peer. It is in dotted decimal notation.
ipv6-address Specifies the IPv6 address of a BGP peer. The value is a 32-digit hexadecimal number, in the format X:X:X:X:X:X:X:X.
Site-of-origin Specifies the SoO attribute, which is a BGP extended community attribute and can be expressed in any of the following formats:
  • 2-byte AS number: 4-byte user-defined number, for example, 1:3. The AS number ranges from 0 to 65535. The user-defined number ranges from 0 to 4294967295. The AS number and the user-defined number cannot both be 0. That is, a SoO cannot be 0:0.

  • IPv4-address: 2-byte user-defined number, for example, The IP address ranges from to The user-defined number ranges from 0 to 65535.

  • Integral 4-byte AS number:2-byte user-defined number, for example, 65537:3. An AS number ranges from 65536 to 4294967295. A user-defined number ranges from 0 to 65535. The AS number and user-defined number cannot be both 0s. That is, a SoO cannot be 0:0.

  • 4-byte AS number in dotted notation:2-byte user-defined number, for example, 0.0:3 or 0.1:0. A 4-byte AS number in dotted notation is in the format of x.y, where x and y are integers that range from 0 to 65535 and from 0 to 65535, respectively. A user-defined number ranges from 0 to 65535. The AS number and user-defined number cannot be both 0s. That is, a SoO cannot be 0.0:0.



BGP-VPN instance IPv4 address family view, BGP-VPN instance IPv6 address family view, BGP multi-instance VPN instance IPv4 address family view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In a BGP/MPLS IP VPN scenario, if the ASs to which two VPN sites belong use private AS numbers, the AS numbers of the two VPN sites may be the same. As a result, different sites of the same VPN cannot communicate. The peer substitute-as command can be used to enable AS number substitution on PEs to address this problem.

Enabling AS number substitution will cause another problem. Several CEs at a VPN site may establish EBGP connections with different PEs of a BGP/MPLS IP VPN backbone network, and a routing protocol has been configured on the CEs. If AS number substitution is enabled on PEs, the AS numbers carried by VPN routes of this site will be replaced on the PEs. As a result, routes advertised from a CE to a PE may be re-advertised to this VPN site after the routes traverse the backbone network, causing a routing loop. The peer soo command can be run on the PEs to address this problem.

After the peer soo command is run on a PE to configure the SoO attribute for a specified CE, the PE adds the attribute to a route sent from the CE and advertises the route to the remote PE. The remote PE checks the SoO attribute of the route before sending it to its attached CE. If the SoO attribute is the same as the local SoO attribute on the remote PE, the remote PE does not send the route to its attached CE, preventing a routing loop in a VPN site.


The peer soo command is used only in the scenarios where PEs and CEs establish EBGP peer relationships.


# Configure the SoO attribute for EBGP peers in a BGP VPN instance.

<HUAWEI> system-view
[~HUAWEI] bgp 100
[*HUAWEI-bgp] ipv4-family vpn-instance vpna
[*HUAWEI-bgp-vpna] peer soo
Related Topics
Updated: 2019-03-21

Document ID: EDOC1000166501

Views: 87850

Downloads: 400

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next