The tunnel priority command configures priority-based load balancing for tunnels.
The undo tunnel priority command deletes the priority-based load balancing configuration.
By default, tunnels use the master/backup load balancing mode.
This command is supported only on the NetEngine 8000 F1A.
Usage Scenario
When the device functions as an LAC to connect to multiple LNSs, the device by default attempts to establish a connection with each LNS in the order in which the LNSs are configured, until an LNS responds to the connection request and a tunnel is established. The other LNSs then function as the backup LNSs. If you want multiple LNSs to load-balance traffic based on priorities, run the tunnel priority command.
The device preferentially establishes tunnels based on the LNS IP carried in the RADIUS No. 67 attribute (Tunnel-Server-Endpoint) and the priority delivered in the RADIUS No. 83 attribute (Tunnel-Preference). If the RADIUS attributes are not delivered, the device establishes tunnels based on the locally configured LNS IP and priority.Configuration Impact
After the tunnel priority command is run, the following situations are available:
The device establishes a tunnel with the LNS with the highest priority. If the LNS with the highest priority is unavailable, the device selects an LNS based on the LNS priorities in descending order. If multiple LNSs have the same priority, the device establishes tunnels with the LNSs, and load balancing is implemented between these tunnels.Precautions
Load balancing can be implemented for tunnels in an L2TP group based on the master/backup status, weight, or priority. If tunnels have been established in an L2TP group, the load balancing configurations cannot be changed.
The tunnel priority and tunnel-per-user commands are mutually exclusive. The tunnel priority and tunnel load-sharing commands are mutually exclusive.