Per Session Shaping Inheritance; Interfaces Supporting Per Session Queuing And Shaping For Pppoe Over Vlans; Restrictions And Limitations For Per Session Queuing And Shaping For Pppoe Over Vlans - Cisco 10000 Series Configuration Manual

Shaping PPPoE Over VLAN Sessions Using RADIUS

Per Session Shaping Inheritance

Each PPPoE over VLAN session for which per session queuing and shaping is configured has its own
set of queues and its own VTMS link. Therefore, these PPPoE sessions do not inherit policies unless you
remove the service policy applied to the session or you do not configure a policy for the session.

Interfaces Supporting Per Session Queuing and Shaping for PPPoE Over VLANs

The router supports per session queuing and shaping on PPPoE terminated sessions and on an
IEEE 802.1Q VLAN tagged subinterfaces for outbound traffic only.
The router does not support per session queuing and shaping for PPPoE over VLAN sessions using
RADIUS on inbound interfaces.
Restrictions and Limitations for Per Session Queuing and Shaping for PPPoE
Over VLANs
•
•
•
•
•
•
•
Cisco 10000 Series Router Quality of Service Configuration Guide
17-36
The router does not support per session queuing and shaping for Layer 2 Access Concentrator (LAC)
sessions.
The QoS-related statistics available using the show policy-map interface command are not
available using RADIUS.
The router does not support using a virtual template interface to apply a service policy to a session.
You can only apply per session queuing and shaping policies as output service policies. The router
supports input service policies on sessions for other existing features, but not for per session queuing
and shaping for PPPoE over VLAN using RADIUS. For more information, see
"Regulating and Shaping Subscriber Traffic."
During periods of congestion, the router does not provide specific scheduling between the various
PPPoE sessions. If the entire port becomes congested, the scheduling that results has the following
effects:
– The amount of bandwidth that each session receives of the entire port's capacity is not typically
proportionally fair share.
The contribution of each class queue to the session's total bandwidth might not degrade
–
proportionally.
The PRE2 does not support ATM overhead accounting for egress packets with Ethernet
encapsulations. Therefore, the router does not consider ATM overhead calculations when
determining that the shaping rate conforms to contracted subscriber rates.
The router does not support the configuration of the policy map using RADIUS. You must use the
modular QoS command line interface (MQC) to configure the policy map on the router.
Chapter 17 Configuring Dynamic Subscriber Services
Chapter 18,
OL-7433-09