326
Default level
2: System level
Parameters
group-name
: Specifies the name of the peer group, which is a case-sensitive string of 1 to 47 characters.
ip-address
: Specifies the IP address of the peer.
route-policy-name
: Specifies the name of the routing policy, which is a case-sensitive string of 1 to 19
characters.
export
: Applies the filtering policy to routes to be advertised.
Examples
# In BGP-VPNv4 subaddress family view, configure peer 1.1.1.1 as a UPE, and specify the system to
advertise routes permitted by the routing policy
hope
to 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] peer 1.1.1.1 as-number 200
[Sysname-bgp] ipv4-family vpnv4
[Sysname-bgp-af-vpnv4] peer 1.1.1.1 enable
[Sysname-bgp-af-vpnv4] peer 1.1.1.1 upe
[Sysname-bgp-af-vpnv4] peer 1.1.1.1 upe route-policy hope export
peer vpn-instance enable
Description
Use the
peer
vpn-instance
enable
command to activate a nested VPN peer or peer group, and enable
the capability of exchanging BGP-VPNv4 routes with the peer or peer group.
Use the
undo peer
vpn-instance
enable
command to disable the capability of exchanging BGP-VPNv4
routes with a nested VPN peer or peer group.
By default, nested VPN peers/peer groups can exchange only IPv4 routes. They cannot exchange BGP-
VPNv4 routes.
This configuration takes effect only after the nested VPN function is enabled.
Before specifying a nested VPN peer or peer group, be sure to configure the corresponding CE peer or
peer group using the
peer as-number
command in BGP-VPN instance view.
Deleting the VPN instance to which a peer belongs will also delete the configuration of this command.
Syntax
peer
{
group-name
|
peer-address
}
vpn-instance
vpn-instance-name
enable
undo peer
{
group-name
|
peer-address
}
vpn-instance
vpn-instance-name
enable
View
BGP-VPNv4 subaddress family view
Default level
2: System level
Parameters
group-name
: Specifies the name of the peer group, which is a case-sensitive string of 1 to 47 characters.
