The peer soo command configures the Site of Origin (SoO) attribute for EBGP peers in BGP VPN instances.
The undo peer soo command cancels this function.
By default, no SoO attribute is configured for EBGP peers in BGP VPN instances.
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 characters without any space. It is case-sensitive. |
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 address is a 32-digit hexadecimal number in the X:X:X:X:X:X:X:X format. |
site-of-origin |
Specifies the SoO attribute, which is a BGP extended community attribute and can be expressed in any of the following formats:
|
- |
Usage Scenario
When multiple CEs at a VPN site access different PEs, VPN routes sent from CEs to PEs may return to this VPN site after traveling through the backbone network. This may cause routing loops in the VPN site.
After the peer soo command is run on a PE to configure the SoO attribute for a specified CE, the PE adds the configured SoO attribute to the routes received from the CE and then advertises these routes to other PEs. Before advertising these routes to the connected CEs, the PE peers check the SoO attribute carried in these routes. If the PE peers find that this SoO attribute is the same as the locally configured SoO attribute, the PE peers do not advertise these routes to the connected CEs.
Prerequisites
The peer as-number command has been used to create a peer or peer group.
Precautions
The peer soo command is applicable to the scenarios where EBGP runs between PEs and CEs.