The tnl-policy command associates the IPv4 or IPv6 address family of a VPN instance with a tunnel policy.
The undo tnl-policy command dissociates the IPv4 or IPv6 address family of a VPN instance from a tunnel policy.
By default, a VPN instance enabled with the IPv4 or IPv6 address family has routes iterated to LDP LSPs without performing load balancing.
| Parameter | Description | Value |
|---|---|---|
| policy-name | Specifies the name of a tunnel policy to be associated with a VPN instance. | The value is a string of 1 to 39 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
VPN instance view, VPN instance IPv4 address family view or VPN instance IPv6 address family view
Prerequisites
The route-distinguisher command is run to configure an RD for the VPN instance enabled with the IPv4 or IPv6 address family.
Configuration Impact
If the tunnel policy associated with a VPN instance enabled with the IPv4 or IPv6 address family cannot match an existing tunnel on the network, the routes in the VPN instance enabled with the IPv4 or IPv6 address family will have routes iterated to tunnels based on the default tunnel policy. If the iteration fails, services will be interrupted.
Precautions
If the address family of a VPN instance changes or the associated tunnel policy is deleted, VPN services will be interrupted for a short time even if tunnels matching the tunnel policy are available on the network. Therefore, use the tnl-policy command with caution.
# Associate the IPv4 address family of the VPN instance named vpn2 with the tunnel policy named po1.
<sysname> system-view
[sysname] tunnel-policy po1
[sysname-tunnel-policy-po1] tunnel select-seq lsp load-balance-number 1
[sysname-tunnel-policy-po1] quit
[sysname] ip vpn-instance vpn2
[sysname-vpn-instance-vpn2] ipv4-family
[sysname-vpn-instance-vpn2-af-ipv4] route-distinguisher 22:33
[sysname-vpn-instance-vpn2-af-ipv4] tnl-policy po1