[no] atm-td-profile traffic-desc-profile-id [create]
config>qos
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.
1 — the default traffic descriptor (UBR, no traffic, no shaping)
the index identifier for a traffic descriptor profile
keyword used to create an ATM traffic descriptor profile
descriptor-type type
config>qos>atm-td-profile
This command is used to specify the type of ATM traffic descriptor profile as per ATM Forum Traffic Management Specification Version 4.1.
Table: Service Category Descriptor Type Default Values defines descriptor-type default values based on service category.
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 |
the ATM traffic descriptor profile type
[no] policing
config>qos>atm-td-profile
This command determines whether ingress traffic is policed. Policing is valid for CBR, rt-VBR, nrt-VBR, and UBR. This policing is cell-based.
disabled
service-category service-category
config>qos>atm-td-profile
This command is used to configure an ATM service category attribute of an ATM traffic descriptor profile.
ubr
Table: ATM Service Categories 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.
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 Cell 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.
[no] shaping
config>qos>atm-td-profile
This command determines whether egress shaping should occur. Shaping is only applied in the egress direction.
The default is determined by the service category. Table: Default Shaping Values describes 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 [sir sir-val [pir pir-val] [mir mir-val] [mbs mbs-val] [cdvt cdvt-val]
no traffic
config>qos>atm-td-profile
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.)
Table: Service Category Traffic Descriptor Parameters 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.
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.
Table: ATM Traffic Parameter Defaults shows the 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 |
the Sustained Information Rate (including cell overhead) in kb/s
the Peak Information Rate (including cell overhead) in kb/s
the Minimum Desired Information Rate (including cell overhead) in kb/s
the Maximum Burst Size in cells
the Cell Delay Variation Tolerance (CDVT) in microseconds