A tunnel selector can apply a tunnel policy to routes, improving the flexibility of using tunnels.
In BGP/MPLS IP VPN networking, after a tunnel policy is applied to a VPN instance, all the routes of the VPN instance recurse to the same tunnel according to the tunnel policy. In inter-AS VPN Option B networking, ASBRs receive all VPNv4 or VPNv6 routes from PE peers. Currently, the system recurses VPNv4 or VPNv6 routes to LSPs. Sometimes, these VPNv4 or VPNv6 routes need to recurse to TE tunnels to guarantee bandwidth. If you do not want to create VPN instances on ASBRs, tunnel policies cannot be used.
Moreover, in inter-AS VPN Option C networking, a device cannot recurse labeled routes to TE tunnels to guarantee bandwidth or implement load balancing among BGP LSPs by default.
The tunnel selector addresses this issue.
A tunnel selector can apply a tunnel policy to VPNv4/VPNv6 routes or BGP-IPv4 labeled routes so that expected tunnels can be selected based on the tunnel policy.
Before configuring a tunnel selector, complete the following tasks:
Configure an RD filter if routes need to be filtered based on RDs.
Configure an ACL or IPv4 prefix list if routes need to be filtered based on the next hop IPv4 address.
Configure an IPv6 access control list (ACL6) or IPv6 prefix list if routes need to be filtered based on the next hop IPv6 address.