tunnel binding

Function

The tunnel binding command binds a destination IP address to a specified tunnel so that services with the destination IP address can be carried over the tunnel.

The undo tunnel binding command unbinds a destination IP address from a tunnel.

By default, a TE tunnel is not bound to any IP address.

Format

tunnel binding destination dest-ip-address te { tunnel-name | tunnel-type tunnel-number } &<1-32> [ ignore-destination-check ] [ down-switch | include-ldp ]

tunnel binding destination dest-ip-address auto-tunnel { auto-tunnel-name } &<1-32> [ ignore-destination-check ] [ down-switch ]

tunnel binding destination dest-ip-address sr-te-policy group { sr-te-policy-group-id } [ ignore-destination-check ] [ down-switch ]

undo tunnel binding destination dest-ip-address

Parameters

Parameter	Description	Value
te	Specifies the type of tunnel to be bound as SR-MPLS TE.	-
tunnel-name	Specifies the number of a TE tunnel interface to be bound.	The value is a string of 1 to 63 case-sensitive characters, spaces not supported.
tunnel-type	Specifies the type of a TE tunnel interface to be bound.	-
tunnel-number	Specifies the number of a TE tunnel interface to be bound.	The value is a string of 1 to 63 case-sensitive characters, spaces not supported.
ignore-destination-check	Disables the function of checking whether the destination address of a tunnel interface is the same as that in a tunnel policy. After this parameter is specified, a tunnel can be selected even if its destination address is different from that in the tunnel policy.	-
down-switch	Enables tunnel switching.	-
include-ldp	Implements load balancing with LDP LSPs.	-
destination dest-ip-address	Specifies the destination IP address to which a TE tunnel is bound.	The value is in dotted decimal notation.
auto-tunnel auto-tunnel-name	Bind with an auto tunnel, specifies the name of auto-tunnel.	The value is a string of 1 to 37 characters.
sr-te-policy	Specifies an SR-MPLS TE tunnel policy to be bound.	-
group sr-te-policy-group-id	Specifies the ID of an SR-MPLS TE policy tunnel group to be bound. After SR-MPLS TE-policy group SR-MPLS TE-policy-group-id is specified in a tunnel policy, the tunnel policy cannot be applied to a tunnel selector using the apply tunnel-policy (tunnel selector view) command.	The value is an integer ranging from 1 to 4294967295.

Views

Tunnel policy view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
tunnel-policy	write

Usage Guidelines

Usage Scenario

A tunnel policy determines the selection of tunnels for VPN services. There are two types of tunnel policies, but only one policy type can be configured in the tunnel policy view at one time:

Tunnel type prioritizing policy: This policy specifies the sequence in which different types of tunnels are selected. The tunnel select-seq command is used to configure a tunnel type prioritizing policy.
Tunnel binding policy: This policy binds a tunnel to a VPN for service transmission. The tunnel binding command is used to configure a tunnel binding policy.
A tunnel binding policy takes effect only to RSVP-TE tunnels, SR-MPLS TE tunnels, auto tunnels or SR-MPLS TE policy tunnel groups. The tunnel binding command can specify the MPLS TE tunnels that are used for VPN binding, facilitating QoS deployment. If some VPN services have high requirements for QoS, run the tunnel binding command to use specific MPLS TE tunnels to transmit these VPN services.

Prerequisites

The mpls te reserved-for-binding command has been configured in the tunnel interface view before the SR-MPLS TE tunnel to be bound is configured.

Configuration Impact

If the tunnel select-seq command has been used for a tunnel policy to set the tunnel priorities and number of tunnels participating in load balancing, you cannot use the tunnel binding command for the tunnel policy. Similarly, if the tunnel binding command has been used for a tunnel policy, you cannot use the tunnel select-seq command for the tunnel policy.

Follow-up Procedure

After configuring a tunnel binding policy, associate it with a VPN instance so that the bound tunnel carries specific VPN services.

Precautions

Multiple tunnel binding commands can be configured for the same tunnel policy.

When TE tunnels or automatic tunnels are configured, a maximum of 32 tunnels can be used for load balancing.

If SR-MPLS TE Policy groups exist, only one SR-MPLS TE tunnel group ID can be used for binding. TE tunnels, automatic tunnels, and SR-MPLS TE Policy groups are mutually exclusive. In the same tunnel policy view, tunnels of different types cannot be bound to the same destination IP address.

After the down-switch command is configured, if the bound TE tunnel is unavailable, an available tunnel is selected in the sequence of LSP, CR-LSP, GRE, and Local_IfNet.

LSP tunnels include LDP LSPs, SR-MPLS BE tunnels, and BGP-LSP tunnels. The priority of LDP LSPs is higher than that of BGP LSPs, and the priority of BGP LSPs is higher than that of SR-MPLS BE tunnels.
CR-LSPs include RSVP-TE tunnels and SR-MPLS TE tunnels. A tunnel that goes up earlier has a higher priority.

Example

# Bind an SR-MPLS TE policy tunnel group to the destination IP address 10.2.2.9.

<HUAWEI> system-view
[~HUAWEI] tunnel-policy tnlpolicyname
[*HUAWEI-tunnel-policy-tnlpolicyname] tunnel binding destination 10.2.2.9 sr-te-policy group 1

# Bind autotunnel123 to the destination IP address 10.2.2.9.

<HUAWEI> system-view
[~HUAWEI] tunnel-policy tnlpolicyname
[*HUAWEI-tunnel-policy-tnlpolicyname] tunnel binding destination 10.2.2.9 auto-tunnel autotunnel123

# In the tunnel policy view, bind Tunnel 10 to destination IP address 10.2.2.9.

<HUAWEI> system-view
[~HUAWEI] interface Tunnel 10
[*HUAWEI-Tunnel10] quit
[*HUAWEI] tunnel-policy tnlpolicyname
[*HUAWEI-tunnel-policy-tnlpolicyname] tunnel binding destination 10.2.2.9 te Tunnel 10