Configuring Qos For L2Tp Sessions; Providing Qos For L2Tp Overview; Sample Scheduler Hierarchies For L2Tp - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

CHAPTER 22

Configuring QoS for L2TP Sessions

Providing QoS for L2TP Overview

Sample Scheduler Hierarchies for L2TP

Copyright © 2010, Juniper Networks, Inc.
This chapter provides information for configuring QoS for L2TP sessions.
QoS topics are discussed in the following sections:
Providing QoS for L2TP Overview on page 187
Sample Scheduler Hierarchies for L2TP on page 187
Configuring QoS for an L2TP Session on page 189
Configuring QoS for Tunnel-Server Ports for L2TP LNS Sessions on page 192
QoS and L2TP TX Speed AVP 24 Overview on page 193
Monitoring QoS Configurations for L2TP on page 194
The JunosE Software supports QoS queues and scheduler nodes for L2TP session
interfaces. L2TP QoS provides per–L2TP session queuing and allows QoS profiles to be
dynamically attached to L2TP session interfaces on E Series Broadband Services Routers.
The routers can be configured as either an LAC or LNS.
The dynamic attachment process uses RADIUS and AAA, enabling a QoS profile to be
attached to a dynamic L2TP session interface when the newly created interface has the
QoS-Profile-Name [26-26] RADIUS VSA associated with it. L2TP QoS support gives you
the ability to shape tunneled users through L2TP interfaces.
L2TP QoS profiles are attached at the L2TP session interface, except on the LNS with
nonmultilink interfaces. On the LNS with nonmultilink interfaces, L2TP QoS profiles are
attached at the IP interface. The queues and scheduler node are built at the L2TP client
interface on the line module.
The figures in this section show the different scheduler hierarchies that you can build for
QoS over L2TP. The type of networking architecture in which the QoS profile is used
determines the actual hierarchy that is built.
Figure 52 on page 188 through Figure 56 on page 189 show scheduler hierarchies for different
networking architectures.
187