The tunnel binding command binds a specified tunnel to the destination IP address. Therefore, the tunnel can be used by a specified VPN.
The undo tunnel binding command cancels the binding.
By default, a tunnel is not bound to any IP address.
tunnel binding destination dest-ip-address te { tunnel interface-number } &<1-6> [ ignore-destination-check ] [ down-switch ]
undo tunnel binding destination dest-ip-address
Parameter | Description | Value |
---|---|---|
dest-ip-address | Specifies the destination address of the tunnel. | - |
interface-number | Specifies the interface number of the bound tunnel interface. | - |
ignore-destination-check | Specifies whether to ignore destination consistency check. If this parameter is enabled, a tunnel policy selects a TE tunnel for route iteration even if the destination address of that TE tunnel is different from the destination address specified in the tunnel policy. | - |
down-switch | Indicates that the tunnel switchover is enabled. After this parameter is configured, an available tunnel, with the priority as LSP, CR-LSP, is adopted when the bound TE tunnel fails. | - |
Usage Scenario
Only MPLS TE tunnels can be bound to VPNs. 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 tunnel-policy command is run to create a tunnel policy.
The mpls te reserved-for-binding command is run in the view of the tunnel interface to be bound to an MPLS TE tunnel.
Precautions
The tunnel binding command can be run repeatedly in the tunnel policy view so long as the value of dest-ip-address varies.
Apply the tunnel binding policy to the VPN instance so that the VPN instance can have its routes iterated to the bound MPLS TE tunnel.