Peer Vpn-Instance Enable - 3Com S7906E Command Reference Manual

Examples
# In BGP-VPNv4 subaddress family view, apply routing policy test-policy to peer group test to filter the
received routes.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] ipv4-family vpnv4
[Sysname-bgp-af-vpnv4] peer test route-policy test-policy import

peer vpn-instance enable

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: Name of the peer group, a case-sensitive string of 1 to 47 characters.
peer-address: IP address of the peer.
vpn-instance-name: Name of the VPN instance, a case-sensitive string of 1 to 31 characters.
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.
Note that:
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.
Examples
# Activate a nested VPN peer group named ebgp.
<Sysname> system-view
[Sysname] bgp 10
[Sysname-bgp] ipv4-family vpn-instance vpn1
[Sysname-bgp-vpn1] group ebgp external
1-46