ATM QoS traffic descriptor profiles

This chapter provides information to configure QoS traffic descriptor profiles using the command line interface.

Topics in this chapter include:

ATM traffic descriptor profiles

This section provides a description of support for ATM QoS policy features. Each traffic descriptor defines the expected rates and characteristics of traffic.

ATM traffic management

The 7705 SAR supports the ATM Forum Traffic Management Specification Version 4.1.

This section contains the following topics related to the QoS features for ATM Permanent Virtual Connections (PVCs):

ATM service categories

The 7705 SAR supports the following service categories:

CBR – constant bit rate
rt-VBR – real-time variable bit rate
nrt-VBR –non-real-time variable bit rate
UBR/UBR+MIR – unspecified bit rate with minimum cell rate (UBR is a special case of UBR+MIR where MIR=0)

ATM traffic descriptors and QoS parameters

The following table shows the ATM traffic descriptors supported on the 7705 SAR.

Table 1. ATM traffic descriptors
Service category	Traffic descriptors
CBR	P0_1
CBR	PIR in kb/s (applies to CLP=0 and CLP=1 flows)
rt-VBR and nrt-VBR	P0_1 and S0_1
	PIR in kb/s (applies to CLP=0 and CLP=1 flows)
	SIR in kb/s (applies to CLP=0 and CLP=1 flows)
	MBS in cells (applies to CLP=0 and CLP=1 flows)
	P0_1 and S0
	PIR in kb/s (applies to CLP=0 and CLP=1 flows; non-conforming CLP=0 cells are discarded)
	SIR in kb/s (applies to CLP=0 flow only)
	MBS in cells (applies to CLP=0 flow only)
	P0_1 and S0_Tag
	PIR in kb/s (applies to CLP=0 and CLP=1 flows; non-conforming CLP=0 flows are tagged to CLP=1 flows)
UBR/UBR+MIR	P0_1
	PIR in kb/s (applies to CLP=0 and CLP=1 flows)
	MIR in kb/s (applies to CLP=0 and CLP=1 flows)

ATM policing

The policing option, when enabled, applies only to ingress traffic. Similarly, the shaping option, if enabled, applies only to egress traffic. For example, if a traffic descriptor has both policing and shaping enabled, the policing option is enforced for the ingress traffic, while the shaping option is enforced for the egress traffic. The following ATM service category conformance definitions are supported:

P0_1 – CBR
P0_1 and S0_1 – VBR.1
P0_1 and S0 – VBR.2
P0_1 and S0_Tag – VBR.3

P represents the peak rate, S represents the sustained rate, 0 or 1 represents the CLP value to which policing is applied if the cell is non-conforming, and Tag indicates that the CLP value has changed from 0 to 1. For example:

P0_1 – means that policing is applied to non-conforming peak rate cells with CLP values of 0 or 1
P0_1 and S0_Tag – means that policing is applied to non-conforming peak rate cells with CLP values of 0 or 1 and policing is applied to non-conforming sustained rate cells with a CLP value of 0 with the action to change the CLP value to 1

Shaping

ATM layer egress shaping is supported for CBR, rt-VBR, and nrt-VBR VCs. A CBR VC is shaped to a single leaky bucket with the parameter PIR from the traffic descriptor. An rt-VBR VC or an nrt-VBR VC is shaped to two leaky buckets with parameters PIR and SIR, BT from the traffic descriptor, where BT is the burst tolerance and is a function of the MBS parameters configured by the user. The traffic rates and shaping parameter that are configured in the sap-egress QoS policy are not used at ATM SAPs.

In order to enforce the SLA, ATM layer ingress policing is supported at ingress, so no shaping is needed. At ingress, after optional policing is applied, packet level queue-based soft-policing is supported per the service ingress QoS policy applied to the ATM SAP.

Note: Shaping to the specified traffic descriptor in the ATM traffic descriptor profile is always enabled for CBR and rt-VBR VCs.

ATM queuing and scheduling

The 7705 SAR provides a per-VC queuing architecture on the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, and 2-port OC3/STM1 Channelized Adapter card with atm/ima encapsulation. The 7705 SAR provides a per-VC queuing architecture on the 4-port OC3/STM1 Clear Channel Adapter card and 4-port DS3/E3 Adapter card with atm encapsulation. In the egress direction toward the ATM port, the scheduling priority at the ATM layer is as follows:

CBR VCs are always shaped and are scheduled with strict priority over all other service categories.
rt-VBR VCs are always shaped and are scheduled next with strict priority over nrt-VBR and UBR VCs.
nrt-VBR shaped VCs are scheduled next with strict priority over nrt-VBR unshaped VCs and UBR VCs.
nrt-VBR unshaped VCs and UBR VCs are scheduled as a common class. Scheduling among these VCs is done using a weighted round robin (WRR) scheduler, where the weight of each VC is determined by the configured SIR for nrt-VBR and by the MIR for UBR VCs. The scheduling is work-conserving, so each VC has access to excess bandwidth in proportion to its SIR/MIR. Under congestion, the performance of each VC degrades proportionally to the weight of the VC.

Congestion avoidance

Congestion and potential discards are performed on a per-forwarding class basis in the SAP queues in the CSM.

Basic configuration

This section contains the following topics related to creating and applying ATM QoS policies:

A basic ATM QoS traffic descriptor profile must conform to the following rules:

Each policy must have a unique policy ID.
Default values can be modified but parameters cannot be deleted.

Creating an ATM traffic descriptor profile QoS policy

Configuring and applying QoS policies and profiles other than the default policy is optional. To create an ATM QoS traffic descriptor profile, perform the following:

assign a policy ID (policy number) – the system does not dynamically assign an ID
include a description – provides a brief overview of policy features
configure traffic attributes of the ATM traffic profile
determine whether egress shaping should occur

Use the following CLI syntax to configure an atm-td-profile policy.

CLI syntax:

config>qos#
    atm-td-profile traffic-desc-profile-id
        description description-string
        descriptor-type {P0_1|P0_1andS0_Tag|P0_1andS0|P0_1andS0_1}
        [no] policing 
        service-category service-category
        [no] shaping
        traffic [sir sir-val] [pir pir-val] [mir mir-val] [mbs mbs-val][cdvt cdvt-val]

The following output displays an example of the command syntax.

Example:

*A:ALU-1# config qos
config>qos# atm-td-profile 3 create
config>qos>atm-td-profile$ description "ATM TD profile3"
config>qos>atm-td-profile$ service-category rt-vbr
config>qos>atm-td-profile$ descriptor-type P0_1andS0_1
config>qos>atm-td-profile$ policing
config>qos>atm-td-profile$ shaping
config>qos>atm-td-profile$ traffic sir 500 pir 500 mbs 500 cdvt 500
config>qos>atm-td-profile$ exit
config>qos# exit

The following output displays the profile configuration for ATM TD profile 3:

*A:ALU-1>config>qos# info
#--------------------------------------------------
echo "QoS Policy Configuration"
#--------------------------------------------------
... 
        atm-td-profile 3 create
            description "ATM TD profile3"
            service-category rt-vbr
            traffic sir 500 pir 500 mbs 500 cdvt 500
            policing
        exit
...
*A:ALU-1

Applying ATM traffic descriptor profile policies

ATM QoS traffic descriptor profiles are applied to ATM VLL (Apipe) SAPs. ATM QoS traffic descriptor profiles can also be applied on egress to ATM VCC SAPs that are members of a SAP aggregation group. You cannot apply ATM QoS traffic descriptor profiles on ingress to a SAP in a SAP aggregation group; the profile is set to the default (1).

ATM VLL (Apipe) SAPs

Use the following CLI syntax to apply ATM QoS traffic descriptor profile policies to Apipe SAPs on ingress and egress.

CLI syntax:

config>service>apipe>sap# atm
    egress
        traffic-desc traffic-desc-profile-id
    ingress
        traffic-desc traffic-desc-profile-id

Default ATM traffic descriptor profile policy values

The default ATM QoS traffic descriptor profile is 1. The default profile cannot be edited or deleted.

The following table shows the ATM TD profile defaults.

Table 2. ATM TD profile defaults
Field	Default
atm-td-profile traffic-desc-profile-id	1
description	Default Traffic Descriptor
descriptor-type	Based on service category: CBR: P0_1 UBR: P0_1 UBR+MIR: P0_1 rt-VBR or nrt-VBR: P0_1 and S0 _ 1
policing	No policing
service-category	UBR
traffic	No traffic
shaping	No shaping

The following output displays the default configuration:

A:ALU-1>config>qos# info detail
--------------------------------------------------
Echo "QoS Policy Configuration"
--------------------------------------------------
       atm-td-profile 1 create
           description "Default Traffic Descriptor"
           service-category ubr
           no traffic
           no policing
           descriptor-type P0_1
           no shaping
       exit
...

Service management tasks

This section describes the following ATM Traffic Descriptor Profile service management tasks:

Removing an ATM traffic descriptor profile from the QoS configuration

The default ATM traffic descriptor profile cannot be deleted.

To delete an ATM QoS traffic descriptor profile, enter the following command:

CLI syntax:

config>qos# no atm-td-profile traffic-desc-profile-id

Example:

config>qos# no atm-td-profile 3

Copying and overwriting an ATM traffic descriptor profile

You can copy an existing profile, rename it with a new profile ID value, or overwrite an existing profile ID. The overwrite option must be specified or an error occurs if the destination profile ID exists.

CLI syntax:

config>qos# copy atm-td-profile src-prof dst-prof [overwrite]

Example:

*A:ALU-1#>config>qos# copy atm-td-profile 2 3
A:ALU-48>config>qos# copy atm-td-profile 2 3 overwrite
A:ALU-48>config>qos#

Editing QoS policies

You can change existing policies and entries in the CLI. The changes are applied immediately to all services where this policy is applied. To prevent configuration errors, copy the policy to a work area, make the edits, and then write over the original policy.

ATM QoS policy command reference

Command hierarchies

Configuration commands

config
    - qos
        - [no] atm-td-profile traffic-desc-profile-id [create] 
            - description description-string 
            - no description
            - descriptor-type type
            - [no] policing
            - service-category service-category
            - [no] shaping
            - traffic [sir sir-val] [pir pir-val] [mir mir-val] [mbs mbs-val] [cdvt cdvt-val]
            - no traffic

Operational commands

config
    - qos
        - copy atm-td-profile src-prof dst-prof [overwrite]

Show commands

show
    - qos
        - atm-td-profile [traffic-desc-profile-id] [detail]
    - service
        - sap-using [ingress | egress] atm-td-profile td-profile-id
        - sap-using [ingress | egress] qos-policy qos-policy-id

Command descriptions

Configuration commands

Generic commands

description

Syntax

description description-string

no description

Context

config>qos>atm-td-profile

Description

This command creates a text description stored in the configuration file for a configuration context.

The no form of this command removes any description string from the context.

Default

n/a

Parameters

description-string: a text string describing the entity. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed within double quotes.

ATM QoS policy commands

atm-td-profile

Syntax

[no] atm-td-profiletraffic-desc-profile-id [create]

Context

config>qos

Description

This command is used to configure an ATM traffic descriptor profile as per ATM Forum Traffic Management Specification Version 4.1.

Traffic descriptor profiles are used to:

define traffic management capabilities for ATM PVCCs
calculate the total bandwidth consumed on a given port by all ATM PVCCs. The bandwidth taken by a PVCC is equal to:
PIR for CBR PVCCs
SIR for rt-vbr and nrt-vbr PVCCs
MIR for UBR PVCC
define ATM-level scheduling

The default traffic descriptor is preconfigured and non-modifiable. It cannot be deleted. All other traffic descriptor profiles must be explicitly created before use. The create keyword must follow each new profile configuration.

Any changes made to the existing profile, using any of the sub-commands, are applied immediately to all objects where this profile is applied (a small traffic interruption in data traffic will occur during the data plane reprogramming with the newly modified profile).

When many changes are required on a profile, it is recommended that the profile be copied to a work area profile ID. That work-in-progress profile can be modified until complete and then written over the original profile-id. Use the config>qos>copy command to maintain profiles in this manner.

The weight assigned to each non-shaped PVCC in the Deficit Round Robin Scheduler depends on the service category and traffic rates (see the traffic command for more details).

The no form of the command deletes a given traffic profile. The profile to be deleted must not be associated with any object (for example a SAP). If this condition is not met, the command will return an error.

Default

1 – the default traffic descriptor (UBR, no traffic, no shaping)

Parameters

traffic-desc-profile-id

the index identifier for a traffic descriptor profile

Values: 1 to 1000

create: keyword used to create an ATM traffic descriptor profile

descriptor-type

Syntax

descriptor-type type

Context

config>qos>atm-td-profile

Description

This command is used to specify the type of ATM traffic descriptor profile as per ATM Forum Traffic Management Specification Version 4.1.

Service category descriptor type default values defines the descriptor-type default values based on service category, and Traffic descriptor type parameters defines how the traffic parameters that are specified for the descriptor profiles are interpreted.

Note: Setting descriptor-type to a value that is not compatible with the service category as defined in the table results in an error message.

Table 3. Service category descriptor type default values
Service category	Default descriptor type
CBR	P0_1
UBR	P0_1
UBR with MIR	P0_1
rt-VBR or nrt-VBR	P0_1and S0_1

Table 4. Traffic descriptor type parameters
Descriptor type value	Rates interpretation	Applicable service categories
P0_1	PIR in kb/s; applies to CLP=0 and CLP=1 cell flows MIR in kb/s; applies to CLP=0 and CLP=1 cell flows	CBR, UBR, UBR with MIR
P0_1andS0	PIR in kb/s; applies to CLP=0 and CLP=1 cell flows; non-conforming CLP=0 cell flows are discarded SIR in kb/s; applies to CLP=0 cell flows only	rt-VBR and nrt-VBR
P0_1andS0_Tag	PIR in kb/s; applies to CLP=0 and CLP=1 cell flows; non-conforming CLP=0 cell flows are tagged to CLP=1 cell flows SIR in kb/s; applies to CLP=0 cell flows only	rt-VBR and nrt-VBR
P0_1andS0_1	PIR in kb/s; applies to CLP=0 and CLP=1 cell flows SIR in kb/s; applies to CLP=0 cell flows only	rt-VBR and nrt-VBR

Default

see Service category descriptor type default values

Parameters

type

the ATM traffic descriptor profile type

Values: P0_1, P0_1andS0_Tag, P0_1andS0, P0_1andS0_1

policing

Syntax

[no] policing

Context

config>qos>atm-td-profile

Description

This command determines whether ingress traffic is policed. Policing is valid for CBR, rt-VBR, nrt-VBR, and UBR. This policing is cell-based.

Default

disabled

service-category

Syntax

service-category service-category

Context

config>qos>atm-td-profile

Description

This command is used to configure an ATM service category attribute of an ATM traffic descriptor profile.

Default

ubr

Parameters

service-category

The following table describes the supported ATM service categories on the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, 4-port DS3/E3 Adapter card, 4-port OC3/STM1 Clear Channel Adapter card, and 2-port OC3/STM1 Channelized Adapter card.

Table 5. ATM service categories
Service category	Description
CBR	Constant bit rate
rt-VBR	Real-time variable bit rate
nrt-VBR	Non-real-time variable bit rate
UBR	Unspecified bit rate without minimum desired dell rate (defined by specifying service category to be ubr, and MIR of 0)
UBR (with MIR)	Unspecified bit rate with non-zero minimum desired cell rate (defined by specifying service category to be ubr, and MIR > 0)

Changing the service category of a profile will reset all traffic attributes to their defaults (see the traffic command) and will cause reprogramming of the data path (with a small impact on user traffic) and a reset of VC statistics for all VCs using this traffic descriptor profile.

shaping

Syntax

[no] shaping

Context

config>qos>atm-td-profile

Description

This command determines whether egress shaping should occur. Shaping is only applied in the egress direction.

Default

The default is determined by the service category. The following table describes the default shaping values.

Table 6. Default shaping values
Applicable service category	Default shaping value	Comments
UBR	Disabled	Shaping cannot be enabled
CBR	Enabled	Shaping cannot be disabled
rt-VBR	Enabled	Shaping cannot be disabled
nrt-VBR	Enabled	Shaping cannot be disabled

traffic

Syntax

traffic [sir sir-val [pir pir-val] [mir mir-val] [mbs mbs-val] [cdvt cdvt-val]

no traffic

Context

config>qos>atm-td-profile

Description

This command is used to configure traffic attributes of an ATM traffic profile as per ATM Forum Traffic Management Specification Version 4.1.

The traffic parameters of a traffic descriptor that are configurable depend on the service category of this traffic descriptor profile. (See the service-category command.)

The following table defines which traffic descriptor parameters are applicable for what service category and what the configuration rules are between the parameters. ‟Y” indicates that the parameter can be configured for a given service category and will be defaulted if not provided, and an ‟N/A” indicates that the parameter cannot be configured for a given service category (an error will be returned). If an applicable parameter is not specified, the current value will be preserved.

Table 7. Service category traffic descriptor parameters
Service category	SIR	PIR	MBS	MIR	CDVT
CBR	N/A	Y	N/A	N/A	Y
rt-VBR	Y	Y (must be ≥ SIR)	Y	N/A	Y
nrt-VBR	Y	Y (must be ≥ SIR)	Y	N/A	Y
UBR	N/A	Y	N/A	N/A	Y
UBR with MIR	N/A	Y (must be ≥ MIR	N/A	Y (non-zero MIR specified)	Y

When a traffic descriptor profile is used to define egress scheduling, the following describes how traffic rates are used to derive scheduling weight:

The scheduling weight applies only to unshaped nrt-VBR and UBR. The scheduling weight is a value from 1 to 8. The scheduling weight is determined by the SIR value for nrt-VBR, and by the MIR value for UBR. The conversion from SIR/MIR to weight is as follows:

Rate < 64K weight = 1
Rate < 128K weight = 2
Rate < 256K weight = 3
Rate < 512K weight = 4
Rate < 1024K weight = 5
Rate < 1536K weight = 6
Rate < 1920K weight = 7

Everything above 1920K will be assigned a weight of 8.

Since the 7705 SAR operates in cells/second with one cell granularity, PIR and SIR values programmed need to be converted to cells/second. When converting values to be used for the scheduler, the result is rounded up to the next cell when required by conversion.

When any of SIR, PIR, or MIR is greater than the physical maximum port/channel capacity for a given PVCC, then the maximum physical port/channel capacity is used in bandwidth accumulation and when configuring the hardware for that PVCC.

Hardware-enforceable MBS is in the inclusive range of 3 to 256 000 cells on all 7705 SAR ATM-capable adapter cards. Assigning an atm-td-profile with an MBS value outside of this range to a SAP is blocked. As well, once an atm-td-profile is assigned to a SAP, the CLI will block any change of the MBS value to a value outside of this range.

The no form of the command restores traffic parameters to their defaults for a given service category.

Default

The following table shows the ATM traffic parameter defaults.

Table 8. ATM traffic parameter defaults
Service category	Traffic parameter defaults
CBR:
PIR	0
CDVT	250
rt-VBR and nrt-VBR
PIR	4294967295
SIR	0
MBS	32
CDVT	250
UBR (note by default UBR is without MIR)
PIR	0
CDVT	250

Parameters

sir-val

the sustained information rate (including cell overhead) in kb/s

Values: 0 to 4294967295

pir-val

the peak information rate (including cell overhead) in kb/s

Values

0 to 4294967295

mir-val

the minimum desired information rate (including cell overhead) in kb/s

Values: 0 to 4294967295

mbs-val

the maximum burst size in cells

Values

0 to 4294967295 (this range applies if the atm-td-profile is not assigned to a SAP)

3 to 256000 (this range applies if the atm-td-profile is assigned to a SAP, as described above)

cdvt-val

the cell delay variation tolerance (CDVT) in microseconds

Default: CBR/RT-VBR/NRT-VBR/UBR = 250

Values: 0 to 4294967295

Operational commands

copy

Syntax

copy atm-td-profile src-prof dst-prof [overwrite]

Context

config>qos

Description

This command copies the source ATM traffic descriptor profile into the destination ATM profile. If the destination profile was already defined, the keyword overwrite must be appended for the copy to complete.

The copy command is a configuration level maintenance tool used to create new profiles using existing profiles. It also allows bulk modifications to an existing profile with the use of the overwrite keyword.

Parameters

src-prof dst-prof

indicates that the source profile ID and the destination profile ID are atm-td-profile IDs. Specify the source ID that the copy command will copy and specify the destination ID to which the command will duplicate the profile.

Values: 1 to 1000

overwrite

specifies that the existing destination profile is to be replaced. Everything in the existing destination profile will be overwritten with the contents of the source profile. If overwrite is not specified, an error will occur if the destination profile ID exists.

ALU-48>config>qos# copy atm-td-profile 2 10

MINOR: CLI destination (10) exists use {overwrite}.

ALU-48>config>qos# copy atm-td-profile 2 10 overwrite

ALU-48>config>qos#

Show commands

Note: The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration.

atm-td-profile

Syntax

atm-td-profile [traffic-desc-profile-id] [detail]

Context

show>qos

Description

This command displays ATM traffic descriptor profile information.

Parameters

traffic-desc-profile-id

displays the ATM traffic descriptor profile

Values: 1 to 1000

detail: displays detailed policy information including policy associations

Output

The following output is an example of ATM traffic descriptor profile information, and ATM traffic descriptor profile field descriptions describes the fields.

Output example

*A:ALU-1>show>qos# atm-td-profile 3 detail
===============================================================================
Traffic Descriptor Profile (3)
===============================================================================
-------------------------------------------------------------------------------
TDP-id Description
       Service Cat SIR         PIR         MIR         MBS         CDVT
-------------------------------------------------------------------------------
3      ATM TD profile3
       RT-VBR      500         500         -           500         500
-------------------------------------------------------------------------------
TDP details
-------------------------------------------------------------------------------
Shaping            : enabled
Policing           : enabled
Descriptor-Type    : P0_1andS0_1
-------------------------------------------------------------------------------
Entities using TDP-3
-------------------------------------------------------------------------------
===============================================================================
*A:ALU-1>show>qos#

Table 9. ATM traffic descriptor profile field descriptions
Label	Description
Maximum Supported Profiles	The maximum number of ATM traffic descriptor profiles that can be configured on this system
Currently Configured Profiles	The number of currently configured ATM traffic descriptor profiles on this system
TDP-Id	The ID that uniquely identifies the traffic descriptor policy
Description	A text string that helps identify the policy’s context in the configuration file
Service Category	The ATM service category
SIR	The sustained cell rate in kb/s
PIR	The peak cell rate in kb/s
MIR	The minimum desired cell rate in kb/s
MBS	The maximum burst size in cells
CDVT	The cell delay variation tolerance in microseconds
Shaping	Whether shaping is enabled or disabled for the traffic descriptor profile
Policing	Whether policing is enabled or disabled for the traffic descriptor profile
Descriptor Type	The descriptor type for the ATM TD profile
Entities using TDP-ID	The number of entities using the ATM traffic descriptor
-	The parameter is not applicable for the configured service category

sap-using

Syntax

sap-using [ingress | egress] atm-td-profile td-profile-id

sap-using [ingress | egress] qos-policy qos-policy-id

Context

show>service

Description

This command displays SAP information.

If no optional parameters are specified, the command displays a summary of all defined SAPs.

The optional parameters restrict output to only SAPs matching the specified properties.

Parameters

ingress: specifies matching an ingress policy

egress: specifies matching an egress policy

qos-policy-id

identifies the ingress or egress QoS policy for which to display matching SAPs or SAP aggregation groups. SAP aggregation groups are supported only on ATM VLLs.

Values: 1 to 65535, or qos-policy-name (up to 64 characters)

td-profile-id: displays SAPs using the specified traffic description

Output

The following output is an example of SAP information using the atm-td-profile parameter, and SAP field descriptions describes the fields.

Output example

*A:ALU-1>show>service# sap-using egress atm-td-profile 3
===============================================================================
Service Access Point Using ATM Traffic Profile 3
===============================================================================
PortId                          SvcId      Ing.  Ing.    Egr.  Egr.   Adm  Opr
                                           QoS   Fltr    QoS   Fltr
-------------------------------------------------------------------------------
No Matching Entries

The following output shows an example of SAPs and SAP aggregation groups that use the same QoS policy. SAPs that are members of a SAP aggregation group are not listed by their port identifiers but are listed under their respective group names. SAP field descriptions describes the fields.

Output example

*B:A:179_121# show service sap-using ingress qos-policy 1 
===============================================================================
Service Access Points Using Ingress Qos Policy 1
===============================================================================
PortId                         SvcId      Ing.  Ing.    Egr.  Egr.   Adm  Opr 
                                          QoS   Fltr    QoS   Fltr            
-------------------------------------------------------------------------------
1/1/3.1:0/100                   100        1     none    1     none   Up   Down
1/1/3.1:3/100                   100        1     none    1     none   Up   Down
1/2/5:200                       200        1     none    1     none   Up   Up  
1/1/9.1:3/300                   300        1     none    1     none   Up   Up  
bundle-ima-1/1.1:6/601          2001       1     none    1     none   Up   Up  
bundle-ima-1/1.1:6/602          2002       1     none    1     none   Up   Up
------------------------------------------------------------------------------- 
Number of SAPs: 6  
-------------------------------------------------------------------------------
==============================================================================
SAP Aggregation Groups Using Ingress Qos Policy 1
===============================================================================
Group Name                     SvcId      Ing.  Ing.    Egr.  Egr.   Adm  Opr
                                          QoS   Fltr    QoS   Fltr            
------------------------------------------------------------------------------- 
‟Group Name 1”                   2003      1     n/a    1      n/a    n/a  n/a 
sap:1/1/9.1:3/301                          atm          1524   1524   Up   Up
sap:1/1/9.1:3/302                          atm          1524   1524   Up   Up
sap:1/1/9.1:3/303                          atm          1524   1524   Up   Up 
‟Group Name 2”                   2004      1     n/a    1      n/a    n/a  n/a  
sap:1/1/9.1:3/304                          atm          1524   1524   Up   Up
sap:1/1/9.1:3/305                          atm          1524   1524   Up   Up
sap:1/1/9.1:3/306                          atm          1524   1524   Up   Up
-------------------------------------------------------------------------------
Number of SAP Aggregation Groups:2
-------------------------------------------------------------------------------

Table 10. SAP field descriptions
Label	Description
Service Access Points Using ATM Traffic Profile Service Access Points Using Ingress Qos Policy
PortId	The ID of the access port where the SAP is defined
SvcId	The service identifier
Ing.QoS	The SAP ingress QoS policy number specified on the ingress SAP
Ing.Fltr	The SAP ingress filter number specified on the ingress SAP
Egr.QoS	The SAP egress QoS policy number specified on the egress SAP
Egr.Fltr	The SAP egress filter number specified on the egress SAP
Adm	The administrative state of the SAP
Opr	The operational state of the SAP
Number of SAPs	The number of individual SAPs that use the specified QoS policy
SAP Aggregation Groups Using Ingress Qos Policy
Group Name	The SAP aggregation group name identifier
SvcId	The service identifier for the group
Ing.QoS	The ingress QoS policy number specified on the ingress SAP aggregation group
Ing.Fltr	The SAP ingress filter number specified on the ingress SAP
Egr.QoS	The egress QoS policy number specified on the egress SAP aggregation group
Egr.Fltr	The SAP egress filter number specified on the egress SAP
Adm	The administrative state of the SAP in the SAP aggregation group
Opr	The operational state of the SAP in the SAP aggregation group
Number of SAP Aggregation Groups	The number of SAP aggregation groups that use the specified QoS policy