Configuring Bgp As Number Substitution - 3Com S7906E Configuration Manual

If you start OSPF but do not configure the router ID, the system will automatically elect one.
However, the same election rules produce the same router ID. Therefore, you are recommended to
configure the router ID when starting an OSPF process. For the election rules, refer to OSPF
Configuration in the IP Routing Volume.
If you configure multiple OSPF VPN instances but do not configure the route tag, the system will
automatically create one based on the AS number configured. If you do not configure BGP, the tag
will be 0. However, the same calculation rule produces the same tag, and hence the same tag will
be created for multiple OSPF VPN instances on the same PE or PEs with the same AS number.
Therefore, you are recommended to configure different tags for different OSPF VPN instance.

Configuring BGP AS Number Substitution

Configuration Prerequisites
Before configuring BGP AS number substitution, complete these tasks:
Configuring basic MPLS L3VPN
Configuring CEs at different sites to have the same AS number
Configuration Procedure
When CEs at different sites have the same AS number, you need to configure the BGP AS number
substitution function to avoid route loss.
With the BGP AS number substitution function, when a PE advertises a route to a CE of the specified
peer, if an AS number identical to that of the CE exist in the AS_PATH of the route, it will be replaced
with that of the PE before the route is advertised.
Follow these steps to configure the BGP AS number substitution function:
To do...
Enter system view
Enter BGP view
Enter BGP VPN instance view
Enable the BGP AS number
substitution function
For information about the peer { ip-address | group-name } substitute-as command, refer to BGP
Commands in the IP Routing Volume.
Use the command...
system-view
bgp as-number
ipv4-family vpn-instance
vpn-instance-name
peer { ip-address |
group-name } substitute-as
1-43
Remarks
—
Required
Required
Required
Disabled by default