230
•
The address spaces of sub-VPNs of a VPN cannot overlap.
•
Do not assign nested VPN peers addresses that public network peers use.
•
Nested VPN does not support multihop EBGP. A provider PE and a provider CE must use the
addresses of the directly connected interfaces to establish a neighbor relationship.
To configure nested VPN:
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 VPNv4 address
family view.
address-family vpnv4
N/A
4.
Enable nested VPN.
nesting-vpn
By default, nested VPN is
disabled.
5.
Return to BGP instance view.
quit
N/A
6.
Enter BGP-VPN instance
view.
ip vpn-instance
vpn-instance-name
N/A
7.
Specify the peer CE or the
peer group of the peer CE.
peer
{
group-name
|
ipv4-address
[
mask-length
] }
as-number
as-number
By default, no peer is specified.
8.
Create the BGP-VPN VPNv4
address family and enter its
view.
address-family vpnv4
By default, the BGP-VPN VPNv4
address family is not created.
9.
Enable BGP VPNv4 route
exchange with the peer CE
or the peer group of the peer
CE.
peer
{
group-name
|
ipv4-address
[
mask-length
] }
enable
By default, BGP does not
exchange VPNv4 routes with any
peer.
10.
(Optional.) Configure the
SoO attribute for the BGP
peer or peer group.
peer
{
group-name
|
ipv4-address
[
mask-length
] }
soo
site-of-origin
By default, the SoO attribute is not
configured.
Configuring multirole host
To configure the multirole host feature, perform the following tasks on the PE connected to the CE in
the site where the multirole host resides:
•
Configure and apply PBR.
•
Configure static routes.
Configuring and applying PBR
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a policy node and
enter policy node view.
policy-based-route
policy-name
{
deny
|
permit
}
node
node-number
By default, no policy nodes exist.
