Configuring BGP AS number substitution and SoO attribute
When CEs at different sites have the same AS number, configure the BGP AS number substitution feature to avoid route loss.
When a PE uses different interfaces to connect different CEs in a site, the BGP AS number substitution feature introduces a routing loop. To remove the routing loop, configure the SoO attribute on the PE.
For more information about the BGP AS number substitution feature and the SoO attribute, see "BGP AS number substitution and SoO attribute."
To configure BGP AS number substitution and SoO attribute:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP instance view. | bgp as-number [ instance instance-name ] | N/A |
3. Enter BGP-VPN instance view. | ip vpn-instance vpn-instance-name | N/A |
4. Enable the BGP AS number substitution feature. | peer { ipv4-address [ mask-length ] | group-name } substitute-as | By default, BGP AS number substitution is disabled. |
5. Enter BGP-VPN IPv4 unicast address family view. | address-family ipv4 [ unicast ] | N/A |
6. (Optional.) Configure the SoO attribute for a BGP peer or peer group. | peer { group-name | ipv4-address [ mask-length ] } soo site-of-origin | By default, the SoO attribute is not configured. |
For more information about the commands in this section, see Layer 3—IP Routing Command Reference.