246
To configure BGP AS number substitution and SoO:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a routing policy and enter
routing policy view
route-policy
route-policy-name
permit node
node-number
Optional
No routing policy is created by
default.
Specify an SoO attribute value
apply extcommunity soo
site-of-origin
additive
Optional
Not specified by default.
Return to system view
quit
—
Enter BGP view
bgp
as-number
—
Enter BGP VPN instance view
ipv4-family vpn-instance
vpn-instance-name
Required
Enable the BGP AS number
substitution function
peer
{
ip-address
|
group-name
}
substitute-as
Required
Disabled by default.
Apply the routing policy to routes
received from the specified peer
peer
{
ip-address
|
group-name
}
route-policy
route-policy-name
import
Optional
Not applied by default.
NOTE:
For more information about the
apply
extcommunity
,
peer
substitute-as
and
peer
route-policy
commands, see
Layer 3—IP Routing Command Reference.
Displaying and maintaining MPLS L3VPN
Resetting BGP connections
When BGP configuration changes, you can use the soft reset function or reset BGP connections to make
new configurations take effect. Soft reset requires that BGP peers have route refreshment capability
(supporting Route-Refresh messages).
NOTE:
Soft reset of BGP connections refers to updating BGP routing information without breaking BGP neighbor
relationships. Hard reset of BGP connections refers to updating BGP routing information by breaking and
then reestablishing BGP neighbor relationships.
To hard reset or soft reset BGP connections:
To do…
Use the command…
Remarks
Soft reset the BGP connections in a
specific VPN instance
refresh bgp vpn-instance
vpn-instance-name
{
ip-address
|
all
|
external
|
group
group-name
} {
export
|
import
}
Available in user view
Soft reset BGP VPNv4 connections
refresh bgp vpnv4
{
ip-address
|
all
|
external
|
group
group-name
|
internal
}
{
export
|
import
}
Available in user view