Table Of Contents

Per-Session QoS

Contents

Prerequisites for Per-Session QoS

Restrictions for Per-Session QoS

Restrictions for Per-Session QoS (Cisco 7600 Series Routers)

Information About Per-Session QoS

Benefits of Per-Session QoS

Policy Maps and QoS Features

Hierarchical Policy Maps

Per-Session QoS and Virtual Templates

Per-Session QoS and the ISG Framework

How to Configure Per-Session QoS

Configuring Per-Session QoS Using a RADIUS Server

Adding the Cisco QoS AV Pairs to the Service Profile on the RADIUS Server

Defining an ISG Policy Map to Start the QoS Service on the RADIUS Server

Reviewing Session Statistics and Verifying the Policy Map Configuration

Configuring Per-Session QoS Using the ISG Framework

Configuring a Local Service Profile

Defining an ISG Policy Map to Start the QoS Service

Starting the Session and Verifying the Policy Map Configuration

Configuration Examples for Per-Session QoS

Adding the Cisco QoS AV Pairs to the Service Profile on the RADIUS Server: Example

Configuring a Local Service Profile: Example

Defining an ISG Policy Map to Start the QoS Service: Example

Verifying the Per-Session QoS Configuration: Examples

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

Feature Information for Per-Session QoS

Glossary

Per-Session QoS

---

First Published: March 20, 2006

Last Updated: January 14, 2008

The Per-Session QoS feature is one of two features bundled with the QoS: Broadband Aggregation Enhancements—Phase 1 feature. The Per-Session QoS feature provides the ability to apply quality of service (QoS) features (such as traffic classification, shaping, queueing, and policing) on a per-session basis. The Per-Session QoS feature can be configured either using a RADIUS server or using the framework available on the Intelligent Service Gateway (ISG).

---

Note The Per-Session QoS feature can also be configured using a virtual template (for PPP sessions only). Using a virtual template is considered a "legacy" method but is still an available option for those familiar with virtual templates. For more information about using virtual templates to configure this feature, see the "Per-Session QoS and Virtual Templates" section.

---

Finding Feature Information in This Module

Your Cisco IOS software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your Cisco IOS software release. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Per-Session QoS" section.

Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Prerequisites for Per-Session QoS

•Restrictions for Per-Session QoS

•Information About Per-Session QoS

•How to Configure Per-Session QoS

•Configuration Examples for Per-Session QoS

•Additional References

•Command Reference

•Feature Information for Per-Session QoS

•Glossary

Prerequisites for Per-Session QoS

•The PPP or IP sessions are enabled.

---

Note This document uses the generic term PPP to cover all protocol types. Examples of protocols include PPP over Ethernet (PPPoE) and PPP over ATM (PPPoA). The specific protocol supported varies by platform. For example, the Cisco 7600 series router does not support PPPoA or PPP over Ethernet over ATM (PPPoEoA). For information about the Cisco 7600 series router, see the Cisco 7600 Series Cisco IOS Configuration Guide for the Cisco IOS release you are using.

---

•Layer 2 Tunneling Protocol (L2TP) resequencing is disabled.

---

Note This prerequisite does not apply to the Cisco 7600 series router. L2TP is not supported on the Cisco 7600 series router.

---

•Traffic classes and policy maps have been configured with the QoS feature (for example, traffic policing or traffic shaping) to be applied to the network traffic. Depending on the needs of your network, multiple traffic classes and policy maps may be required.

RADIUS-Server-Specific Prerequisites

Only if you are using a RADIUS server the following prerequisites apply:

•Authentication, authorization, and accounting (AAA) must be enabled.

•The RADIUS server must be configured.

•The service profile on the RADIUS server must be created.

Restrictions for Per-Session QoS

This feature does not support the following:

•L2TP sequencing.

•Packet dropping (packet discarding). That is, this feature does not allow you to discard packets using the drop command.

•The Multilink PPP (MLPPP) protocol. That is, multilink bundles are not supported in either a PPP Termination and Aggregation (PTA) configuration or an L2TP configuration.

---

Note MLPPP is supported on the Cisco 7600 series router.

---

•ATM interfaces (that is, PPPoA sessions) for Cisco IOS Release 12.2(33)SRC.

Restrictions for Per-Session QoS (Cisco 7600 Series Routers)

The following restrictions apply to the Cisco 7600 series router only.

QoS Features Supported

•Queueing features are not supported in the ingress (incoming) direction of a router in an IP session. This means that traffic shaping, priority queueing such as low latency queueing (LLQ), class-based weighted fair queueing (CBWFQ), and weighted random early detection (WRED) are not supported. Features that can be configured are traffic policing and traffic marking in either the class-default class or any of the user-defined classes, as shown in the following example:

 policy-map sess_ingress

  class c1

   police 2000000

   set ip precedence 4

  class class-default

   police 5000000

   set ip precedence 1 

---

Note This restriction does not apply at the subinterface level in the ingress direction. That is, LLQ and traffic shaping are supported in the ingress direction. CBWFQ and WRED are not supported. For more information, see the "IP Subscriber Awareness over Ethernet module.

---

Functionality Supported in Egress Policy Maps

•A policy map (in the egress direction) used in an IP session can have only packet marking enabled in the user-defined class. No other QoS features (for instance, traffic policing, LLQ, WRED, or traffic shaping) can be enabled. This means that the simplified configuration shown below would not be supported.

policy-map sess_egress

 class c1

  police/priority/bandwidth/wred/shape

The simplified configuration shown below would be supported.

policy-map sess_egress

 class c1

  set <name> <value>

However, all QoS features can be configured in the class-default class, as illustrated below.

policy-map sess_egress

 class class-default

  police/priority/bandwidth/wred/shape/set

•A hierarchical policy map (in the egress direction) on a IP session is supported, but the child policy map must be attached to the class class-default of the parent policy map as illustrated in the simplified configuration below.

policy-map sess_egress

 class class-default

  <Queueing feature like traffic shaping or bandwidth remaining ratio>

  service-policy child

---

Note None of the restrictions that apply to a "flat" policy map (that is, a policy map not in a hierarchical policy map structure) in the egress or outgoing direction on a session apply to the child policy map. A simplified configuration illustrating this point is shown below.

---

 policy-map child

  class voip

   police 9000

   priority level 1

  class iptv

   police 4193000

   priority level 2

   set cos 4

  class gaming

   bandwidth 1000 (kbps)

  class class-default

   set cos 1

Fields Used for Classifying Traffic (Ingress and Egress Direction)

Traffic in both the ingress and egress direction can be classified (matched) on the basis of characteristics or attributes such as the following:

•Ip precedence value

•Differentiated services code point (DSCP) value

•Class of service (CoS) value and CoS-inner value (of a Layer 2 QinQ packet)

•Access control list (ACL) number

•VLAN and inner-VLAN numbers

Combinations of these characteristics or attributes are allowed with the following restrictions:

•A combination of the CoS-inner setting and ACL number is not supported.

•While the command-line interface (CLI) does allow a configuration that contains two match cos commands, the match-any keyword must be used with the class-map command to make such a configuration meaningful.

•The match vlan and match vlan-inner commands are supported at the main interface level only.

Fields Used for Marking Traffic (Ingress and Egress Direction)

Traffic in both the ingress and egress direction can be marked on the basis of characteristics or attributes such as the following:

•Ip precedence value

•DSCP value

•CoS value

•CoS-inner value (in the egress direction only)

If a set command is specified, note the following points:

•Specifying both set cos 4 and set cos 5 in the same traffic class causes the show policy-map command to display only set cos 5 in the show command output.

•Specifying both the set ip prec 5 command and the set dscp cs6 command in the same class causes the show policy-map command to display only set dscp cs6 in the show command output.

Information About Per-Session QoS

To configure the Per-Session QoS feature, you should understand the following concepts:

•Benefits of Per-Session QoS

•Policy Maps and QoS Features

•Per-Session QoS and Virtual Templates

•Per-Session QoS and the ISG Framework

Benefits of Per-Session QoS

The ability to apply QoS features on a per-session basis helps the Internet service provider (ISP) to adhere to the Service Level Agreement (SLA) established for handling traffic. Applying QoS on a per-session basis provides a higher degree of granularity for managing traffic on the network.

Policy Maps and QoS Features

A policy map specifies the QoS feature to be applied to network traffic. Examples of QoS features that can be specified in a policy map include traffic classification, shaping, queueing, and policing, among others. Each QoS feature is configured using the appropriate QoS commands.

Policy maps (including hierarchical policy maps) are created using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).

Hierarchical Policy Maps

Policy maps can be configured in a hierarchical structure. That is, policy maps can be configured in levels subordinate to one another. The policy map at the highest level is referred to as the "parent" policy map. A subordinate policy map is referred to as a "child" policy map.

A typical hierarchical policy map structure consists of a parent policy map and one child policy map. Configure the child policy map first; then configure the parent policy map. Both types of policy maps are configured in the same manner.

The parent policy map typically contains one class—the class called class-default. The child policy map can contain multiple classes.

---

Note Before configuring the policy map, create the traffic classes and specify the match criteria used to classify traffic. To create traffic classes and specify match criteria, use the MQC.

---

The following restrictions apply to hierarchical policy maps:

•Specify CBWFQ in the child policy map only. CBWFQ cannot be specified in the parent policy map.

•Traffic shaping can be specified in either the parent policy map or the child policy map.

However, for this feature, you must specify traffic shaping in the parent policy map. Specifying traffic shaping in the child policy map is optional.

---

Note The restrictions related to policy maps and the Cisco 7600 series router are different from those listed above. For more information about the restrictions specific to the Cisco 7600 series router, see the "Restrictions for Per-Session QoS (Cisco 7600 Series Routers)" section.

---

Per-Session QoS and Virtual Templates

As mentioned earlier, you can configure the Per-Session QoS feature using a virtual template.

---

Note Using virtual templates to configure the Per-Session QoS feature applies to PPP sessions only.

---

A virtual template is a logical interface that is configured with generic configuration information for a specific purpose or with configuration information common to specific users, plus router-dependent information. The template takes the form of a list of Cisco IOS interface commands that are applied to virtual access interfaces, as needed.

A virtual template is configured (defined) on an interface. When a session is enabled (that is, when a packet arrives at the interface), the virtual template inherits the QoS features specified in the policy map for use during the session.

First, you configure the policy map (using the MQC) and then associate the policy map with the virtual template. For more information about policy maps and the MQC, see the "Applying QoS Features Using the MQC" module.

After configuring the policy maps (as many as needed) and associating the policy maps with the virtual template on the interface, you may want to verify the configuration. To verify the per-session QoS configuration, use the show policy-map session [uid uid-number] command. This command allows you to see whether the policy maps are configured the way that you intended.

Per-Session QoS and the ISG Framework

QoS features can be applied on a per-session basis using the ISG framework in a number of ways, including the following:

•Enabling the QoS feature when it is triggered by specific events configured in the ISG policy map (for instance, at the start of a session or at a predetermined expiration interval).

•Using the Change of Authorization (CoA).

•Using the Transparent Auto Logon (TAL).

•Downloading the service profile at the time of authentication.

This feature module documents the procedure for applying per-session QoS when it is triggered at the start of a session (the first method listed above). For information about the other methods listed, see the "ISG RADIUS Interface" chapter of the Cisco IOS ISG RADIUS CoA Interface Guide, Release 12.2SB.

How to Configure Per-Session QoS

The tasks for configuring per-session QoS vary according to the configuration method that you are using. You can choose to configure the feature either using a RADIUS server or using the ISG framework.

Choose one of the following:

•To configure the feature using a RADIUS server, see the "Configuring Per-Session QoS Using a RADIUS Server" section.

•To configure per-session QoS using the ISG framework, see the "Configuring Per-Session QoS Using the ISG Framework" section.

---

Note For information about configuring the feature using a virtual template, see the "Per-Session QoS and Virtual Templates" section.

---

Configuring Per-Session QoS Using a RADIUS Server

This section contains the following tasks:

•Adding the Cisco QoS AV Pairs to the Service Profile on the RADIUS Server

•Defining an ISG Policy Map to Start the QoS Service on the RADIUS Server

•Reviewing Session Statistics and Verifying the Policy Map Configuration

Adding the Cisco QoS AV Pairs to the Service Profile on the RADIUS Server

To configure per-session QoS on the RADIUS server, you must add two Cisco QoS AV pairs to the service profile on the RADIUS server. To add the Cisco QoS AV pairs to the service profile, complete the following steps on the RADIUS server.

Cisco AV Pairs and VSAs

Cisco AV pairs are part of vendor-specific attributes (VSAs) that allow a policy map to be applied to the router. Cisco AV pairs are a combination of an attribute and a value. The purpose of the Cisco VSA (attribute 26) is to communicate vendor-specific information between the router and the RADIUS server. The Cisco VSA encapsulates vendor-specific attributes that allow vendors such as Cisco to support their own extended attributes.

For this configuration, one of two Cisco AV pairs can be used (formatted as shown below):

•lcp:interface-config=service-policy output/input <policy name>

This Cisco AV pair is considered a "legacy" AV pair. It is of earlier origin but is still an available choice.

•ip:sub-qos-policy-in/out=<policy name>

This Cisco AV pair takes advantage of more recent technology and is the recommended choice. This Cisco AV pair is the one shown in the configuration task and example.

The Cisco AV pair is added to the service profile on the RADIUS server. Each entry establishes an attribute that the user can access.

In a user file, the data to the left of the equal sign (=) is an attribute defined in the dictionary file, and the data to the right of the equal sign is the configuration data.

The Cisco AV pair identifies the policy map that was used to configure the specific QoS features. When the router requests the policy map name (specified in the Cisco AV pair), the policy map is pulled to the router from the RADIUS server when the session is established. The Cisco AV pair applies the appropriate policy map (and, therefore, the QoS feature) directly to the router from the RADIUS server.

Prerequisites

Before adding the Cisco QoS AV pairs to the service profile, you must create traffic classes and configure policy maps used to enable the QoS feature you want to use. To create traffic classes and policy maps, use the MQC. For more information about the MQC, see the "Applying QoS Features Using the MQC" module.

SUMMARY STEPS

1. ip:sub-qos-policy-in/out=<policy name>

DETAILED STEPS

	Command or Action	Purpose
Step 1	ip:sub-qos-policy-in/out=<policy name> Example: cisco-avpair="ip:sub-qos-policy-in=res_ingress" cisco-avpair="ip:sub-qos-policy-out=res_hsi_voip_ parent1"	Enter the Cisco QoS AV pair for policy maps on the RADIUS server in the service profile. When the router requests the service definition from the RADIUS server, the information in the service profile is used. •Add the Cisco QoS AV pairs to the service profile.

Defining an ISG Policy Map to Start the QoS Service on the RADIUS Server

Next, you need to define the ISG policy map to start the QoS service at the start of the session when the service profile is defined on the RADIUS server. To perform this task, complete the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type control policy-map-name

4. class type control always event session-start

5. action-number service-policy type service name service-name

6. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type control policy-map-name Example: Router(config)# policy-map type control TEST	Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy. •Enter the type and control keywords and the name of the policy map. Note Using the control keyword enters control policy-map configuration mode.
Step 4	class type control always event session-start Example: Router(config-control-policymap)# class type control always event session-start	Specifies a control class (or event) for which actions may be configured in policy map. Enters control policy-map class control configuration mode.
Step 5	action-number service-policy type service name service-name Example: Router(config-control-policymap-class-control)# 1 service-policy type service name QoS_Service	Applies the specified service at the start of the session. •Enter the action number, the name keyword, and the name of the service.
Step 6	end Example: Router(config-control-policymap-class-control)# end	(Optional) Returns to privileged EXEC mode.

Reviewing Session Statistics and Verifying the Policy Map Configuration

The last task is to review the output of the show subscriber session command and/or the output of the show policy-map session command. These two show commands allow you to review the statistics of the session and verify the policy map configuration.

SUMMARY STEPS

1. enable

2. show subscriber session uid uid-number

3. show policy-map session uid uid-number

4. exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	show subscriber session uid uid-number Example: Router# show subscriber session uid 401	Displays information about subscriber sessions on an ISG by the unique ID. •Enter the uid keyword and unique identifier.
Step 3	show policy-map session uid uid-number Example: Router# show policy-map session uid 401	Displays the information about the session identified by the unique ID. •Enter the uid keyword and unique identifier.
Step 4	exit Example: Router# exit	(Optional) Exits privileged EXEC mode.

What to Do Next

Proceed to the "Configuration Examples for Per-Session QoS" section.

Configuring Per-Session QoS Using the ISG Framework

This section contains the following tasks:

•Configuring a Local Service Profile

•Defining an ISG Policy Map to Start the QoS Service

•Starting the Session and Verifying the Policy Map Configuration

Configuring a Local Service Profile

The first task is to configure and define a local service profile for use with the policy map. To configure a local service profile for use with the policy map, complete the following steps.

Prerequisites

Before configuring the local service profile, you must create traffic classes and configure policy maps used to enable the QoS feature that you want to use. To create traffic classes and policy maps, use the MQC. For more information about the MQC, see the "Applying QoS Features Using the MQC" module.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service policy-map-name

4. service-policy input policy-map-name

5. service-policy output policy-map-name

6. exit

7. aaa authorization subscriber-service default local group name

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type service policy-map-name Example: Router(config)# policy-map type service QoS_Service	Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy. •Enter the type and service keywords and the name of the policy map. Note Using the service keyword enters service policy-map configuration mode.
Step 4	service-policy input policy-map-name Example: Router(config-service-policymap)# service-policy input res_ingress	Attaches the specified policy map to the input interface or input VC. •Enter the name of the policy map.
Step 5	service-policy output policy-map-name Example: Router(config-service-policymap)# service-policy output res_hsi_voip_iptv_parent1	Attaches the specified policy map to the output interface or output VC. •Enter the name of the policy map.
Step 6	exit Example: Router(config-service-policymap)# exit	Returns to global configuration mode.
Step 7	aaa authorization subscriber-service default local group name Example: Router(config)# aaa authorization subscriber-service default local group group1	Specifies one or more authentication, authorization, and accounting (AAA) authorization methods for ISG to use in providing subscriber service. •Enter the default keyword, the local keyword, the group keyword, and the group name. Note The local keyword must be entered after the default keyword.
Step 8	end Example: Router(config)# end	(Optional) Returns to privileged EXEC mode.

Defining an ISG Policy Map to Start the QoS Service

Next, you need to define the ISG policy map to initiate the QoS service at the start of the session. To perform this task, complete the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type control policy-map-name

4. class type control always event session-start

5. action-number service-policy type service name service-name

6. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type control policy-map-name Example: Router(config)# policy-map type control TEST	Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy. •Enter the type and control keywords and the name of the policy map. Note Using the control keyword enters control policy-map configuration mode.
Step 4	class type control always event session-start Example: Router(config-control-policymap)# class type control always event session-start	Specifies a control class (or event) for which actions may be configured in an ISG control policy. Enters control policy-map class control configuration mode.
Step 5	action-number service-policy type service name service-name Example: Router(config-control-policymap-class-control)# 1 service-policy type service name QoS_Service	Activates an ISG service. •Enter the action number, the name keyword, and the name of the service.
Step 6	end Example: Router(config-control-policymap-class-control)# end	(Optional) Returns to privileged EXEC mode.

Starting the Session and Verifying the Policy Map Configuration

The last task is to start a session by sending traffic in the ingress (incoming) direction and then reviewing the output of the show subscriber session command and/or the output of the show policy-map session command.

SUMMARY STEPS

1. enable

2. show subscriber session uid uid-number

3. show policy-map session uid uid-number

4. exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	show subscriber session uid uid-number Example: Router# show subscriber session uid 401	(Optional) Displays information about subscriber sessions on an ISG by the unique ID. •Enter the uid keyword and unique identifier.
Step 3	show policy-map session uid uid-number Example: Router# show policy-map session uid 401	(Optional) Displays information about the session identified by the unique ID. •Enter the uid keyword and unique identifier.
Step 4	exit Example: Router# exit	(Optional) Exits privileged EXEC mode.

Configuration Examples for Per-Session QoS

This section contains the following examples:

•Adding the Cisco QoS AV Pairs to the Service Profile on the RADIUS Server: Example

•Configuring a Local Service Profile: Example

•Defining an ISG Policy Map to Start the QoS Service: Example

•Verifying the Per-Session QoS Configuration: Examples

Adding the Cisco QoS AV Pairs to the Service Profile on the RADIUS Server: Example

The following is an example of a service profile in which the Cisco QoS AV pairs have been added. Cisco AV pairs are needed only if you are configuring the Per-Session QoS feature using a RADIUS server.

cisco-avpair = "ip:sub-qos-policy-in=res_ingress"

cisco-avpair = "ip:sub-qos-policy-out=res_hsi_voip_iptv_parent1"

Configuring a Local Service Profile: Example

The following is an example of a local service profile configuration. Configuring a local service profile is needed only if you are configuring the Per-Session QoS feature using the ISG framework.

Router> enable

Router# configure terminal

Router(config)# policy-map type service QoS_Service

Router(config-service-policymap)# service-policy input res_ingress

Router(config-service-policymap)# service-policy output res_hsi_voip_iptv_parent1

Router(config-service-policymap)# exit

Router(config)# aaa authorization subscriber-service default local group group1

Router(config)# end

Defining an ISG Policy Map to Start the QoS Service: Example

The following is an example an ISG policy map configured to initiate the QoS service at the start of a session.

Router> enable

Router# configure terminal

Router(config)# policy-map type control TEST

Router(config-control-policymap)# class type control always event session-start

Router(config-control-policymap-class-control)# 1 service-policy type service name 
QoS_Service

Router(config-control-policymap-class-control)# end

Verifying the Per-Session QoS Configuration: Examples

The following is an example of the output of the show subscriber session command.

Router# show subscriber session uid 2

Unique Session ID: 2

Identifier: 

SIP subscriber access type(s): IP

Current SIP options: Req Fwding/Req Fwded

Session Up-time: 00:00:20, Last Changed: 00:00:20

Policy information:

  Authentication status: unauthen

  Active services associated with session:

    name "QoS_Service", applied before account logon

  Rules, actions and conditions executed:

    subscriber rule-map TEST

      condition always event session-start

        1 service-policy type service name QoS_Service

Session inbound features:

 Feature: QoS Policy Map

  Input Policy Map: res_ingress

Session outbound features:

 Feature: QoS Policy Map

  Output Policy Map: res_hsi_voip_iptv_parent1

Configuration sources associated with this session:

Service: QoS_Service, Active Time = 00:00:22

Interface: GigabitEthernet3/1/3.100, Active Time = 00:00:22

The following is an example of the output of the show policy-map session command.

Router# show policy-map session uid 2

 SSS session identifier 2 -

  Service-policy input: res_ingress

  Counters last updated 00:00:00 ago

    Class-map: voip (match-all)

      126126 packets, 9585576 bytes

      30 second offered rate 1114000 bps, drop rate 1114000 bps

      Match: ip precedence 5 

      police:

          cir 9000 bps, bc 1500 bytes

        conformed 40 packets, 3040 bytes; actions:

          transmit

        exceeded 126086 packets, 9582536 bytes; actions:

          drop

        conformed 0 bps, exceed 1114000 bps

      QoS Set

        cos 5

          Packets marked 126126

    Class-map: class-default (match-any)

      262772 packets, 133488176 bytes

      30 second offered rate 15550000 bps, drop rate 15502000 bps

      Match: any 

      police:

          cir 2000000 bps, bc 62500 bytes

        conformed 784 packets, 398272 bytes; actions:

          transmit

        exceeded 261988 packets, 133089904 bytes; actions:

          drop

        conformed 44000 bps, exceed 15502000 bps

      QoS Set

        cos 1

          Packets marked 262772

 SSS session identifier 2 -

  Service-policy output: res_hsi_voip_iptv_parent1

    Class-map: class-default (match-any)

      0 packets, 0 bytes

      30 second offered rate 0 bps, drop rate 0 bps

      Match: any 

      Queueing

      queue limit 2000 packets

      (queue depth/total drops/no-buffer drops) 0/0/0

      (pkts output/bytes output) 0/0

      bandwidth remaining ratio 5 

      bandwidth remaining 0%

      shape (average) cir 8000000, bc 32000, be 32000

      target shape rate 8000000

      Service-policy : hsi_voip_iptv

        queue stats for all priority classes:

          priority level 1

          queue limit 2 packets

          (queue depth/total drops/no-buffer drops) 0/0/0

          (pkts output/bytes output) 0/0

        queue stats for all priority classes:

          priority level 2

          queue limit 1048 packets

          (queue depth/total drops/no-buffer drops) 0/0/0

          (pkts output/bytes output) 0/0

        Class-map: voip (match-all)

          0 packets, 0 bytes

          30 second offered rate 0 bps, drop rate 0 bps

          Match: ip precedence 5 

          Priority: Strict, b/w exceed drops: 0

          Priority Level: 1 

          police:

              cir 9000 bps, bc 1500 bytes

            conformed 0 packets, 0 bytes; actions:

              transmit

            exceeded 0 packets, 0 bytes; actions:

              drop

            conformed 0 bps, exceed 0 bps

          QoS Set

            cos 5

              Packets marked 0

        Class-map: iptv (match-all)

          0 packets, 0 bytes

          30 second offered rate 0 bps, drop rate 0 bps

          Match: ip precedence 6 

          Priority: Strict, b/w exceed drops: 0

          Priority Level: 2 

          police:

              cir 4193000 bps, bc 131031 bytes

            conformed 0 packets, 0 bytes; actions:

              transmit

            exceeded 0 packets, 0 bytes; actions:

              drop

            conformed 0 bps, exceed 0 bps

          QoS Set

            cos 4

              Packets marked 0

        Class-map: class-default (match-any)

          0 packets, 0 bytes

          30 second offered rate 0 bps, drop rate 0 bps

          Match: any 

          queue limit 949 packets

          (queue depth/total drops/no-buffer drops) 0/0/0

          (pkts output/bytes output) 0/0

          QoS Set

            cos 1

              Packets marked 0

Additional References

The following sections provide references related to the Per-Session QoS feature.

Related Documents

Related Topic	Document Title
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples	Cisco IOS Quality of Service Solutions Command Reference
QoS features such as traffic classification and traffic policing	"Quality of Service Overview" module
Class maps, policy maps, hierarchical policy maps, and MQC	"Applying QoS Features Using the MQC" module
RADIUS servers and AAA	"Configuring Authentication" module
RADIUS accounting	"Configuring Accounting" module
ISG policies and session maintenance	"Configuring ISG Policies for Session Maintenance" module
Classification, policing, and marking on Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC)	"QoS: Classification, Policing, and Marking on LAC" module
LLQ, traffic shaping, CBWFQ, and WRED support on a 7600 series router	"IP Subscriber Awareness over Ethernet" module

Standards

Standard	Title
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.	—

MIBs

MIB	MIBs Link
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.	To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs

RFCs

RFC	Title
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.	—

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport

Command Reference

This feature uses no new or modified commands.

Feature Information for Per-Session QoS

Table 1 lists the release history for this feature.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

---

Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

---

Table 1 Feature Information for Per-Session QoS

Feature Name	Releases	Feature Information
Per-Session QoS	12.2(28)SB 12.2(33)SRC	The Per-Session QoS feature provides the ability to apply quality of service (QoS) features (such as traffic classification, shaping, queueing, and policing) on a per-session basis. In Release 12.2(28)SB, this feature was introduced on the Cisco 7200 series router. In Release 12.2(33)SRC, support was added for the Cisco 7600 series router.

Glossary

L2TP—Layer 2 Tunneling Protocol. An IETF standards track protocol defined in RFC 2661 that provides tunneling of PPP. Based upon the best features of L2F and PPTP, L2TP provides an industry-wide interoperable method of implementing a virtual private dialup network (VPDN).

LAC—L2TP access concentrator. A node that acts as one side of an L2TP tunnel endpoint and that is a peer to the L2TP network server (LNS). The LAC sits between an LNS and a remote system and forwards packets to and from each. Packets sent from the LAC to the LNS require tunneling with the L2TP protocol. The connection from the LAC to the remote system is either local or a PPP link.

LNS—L2TP network server. A node that acts as one side of an L2TP tunnel endpoint and that is a peer to the L2TP access concentrator (LAC). The LNS is the logical termination point of a PPP session that is being tunneled from the remote system by the LAC.

PPP—Point-to-Point Protocol. A protocol that provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. PPP is designed to work with several network layer protocols, such as IP, Internetwork Packet Exchange (IPX), and AppleTalk Remote Access (ARA).

PPPoA—Point-to-Point Protocol over ATM. A feature that allows a PPP session to be initiated on a simple bridging ATM connected client. PPPoA provides the ability to connect a network of hosts over a simple bridging access device to a remote access concentrator or aggregation concentrator.

PPPoE—Point-to-Point Protocol over Ethernet. A feature that allows a PPP session to be initiated on a simple bridging Ethernet connected client. PPPoE provides the ability to connect a network of hosts over a simple bridging access device to a remote access concentrator or aggregation concentrator.

PTA—PPP Termination and Aggregation. A network architecture that indicates that after a PPP session is terminated, the network traffic is aggregated. For an ISP, the aggregated traffic either remains in the ISP network or routes to the Internet. For a wholesale provider, the aggregated IP traffic will be forwarded to different destinations or domains depending on the service selected.

QoS—quality of service. A measure of performance for a transmission system that reflects its transmission quality and service availability.

SLA—Service Level Agreement. A contract between wholesale service providers and retail service providers.

SSS—Subscriber Service Switch. A switch that provides flexibility on where and how many subscribers are connected to available services and how those services are defined. The primary focus of SSS is to direct PPP from one point to another using a Layer 2 subscriber policy. The policy will manage tunneling of PPP in a policy-based bridging fashion.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0804R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2006-2008 Cisco Systems, Inc. All rights reserved.