cc/td/doc/product/atm/ls1010s/wa5/12
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring Resource Management

Configuring Resource Management

This chapter describes resource management (RM), which involves modeling and managing switch, interface, and connection resources. Such resources include equivalent bandwidth and buffering to support the provision of specified traffic classes.

This chapter includes the following sections:


Note For a complete description of the commands mentioned in this chapter, refer to the LightStream  1010 ATM Switch and Catalyst  8510 MSR Command Reference publication.

Resource Management Functions

The ATM switch RM software provides the following functions:

Processor Feature Card Configuration Affects Resource  Management

Two types of feature cards are available for the ATM switch: FC-PCQ and FC-PFQ. Each card provides the required ATM Forum Traffic Management features. FC-PCQ contains a subset of the FC-PFQ features, as described in Table 8-1.


Note To determine which feature card you have installed, enter the show hardware EXEC command. Either FC-PCQ or FC-PFQ displays in the Ctrlr-Type column.

Table 8-1: FC-PCQ and FC-PFQ Feature Comparison
Feature FC-PCQ FC-PFQ

Traffic classes

CBR1, VBR-RT2, VBR-NRT3, ABR4 (EFCI5 and RR6), UBR7

CBR, RT-VBR, NRT-VBR, ABR (EFCI and RR), UBR

Output queuing

Four classes per port

Per-VC or per-VP

Output scheduling

SP8

SP, RS9, and WRR10

Intelligent early packet discard

Multiple fixed thresholds

Multiple dynamic thresholds

Intelligent tail (partial) packet discard

Supported

Supported

Selective cell marking and discard

Multiple fixed thresholds

Multiple, weighted, dynamic thresholds

Shaping

Per-port (pacing)

Per-port pacing, per-CBR VC, per-CBR transit VP, per-shaped CBR VP tunnel (128 shaped VP tunnels total)

Policing (UPC11)

Dual mode, single leaky bucket

Dual leaky bucket

Point-to-multipoint VC (multicast)

One leaf per output port, per point-to-multipoint

Multiple leafs per output port, per point-to-multipoint

Network clock switch over

Automatic upon failure

Programmable clock selection criteria

Nondisruptive snooping

Per-port transmit or receive

Per-VC or per-VP

Hierarchical VP tunnel12

-

Maximum of 62 VP tunnels.

1CBR = constant bit rate.
2
RT-VBR = variable bit rate real-time.
3NRT-VBR = variable bit rate-non real-time.
4ABR = available bit rate.
5EFCI = explicit forward congestion indication.
6RR = relative rate.
7UBR = unspecified bit rate.
8SP = strict priority.
9
RS = rate scheduling.
10WRR = weighted round robin.
11UPC = usage parameter control.
12Available with FC-PFQ only.

Configuring Global Resource Management

Global RM configurations affect all interfaces on the switch. The following sections describe global RM tasks:

Configure the Default QoS Objective Table

Since UNI 3 signalling does not provide information elements (IEs) to signal QoS values, RM provides a table of default objective values for QoS for guaranteed service categories. These values are used as the criteria for connection setup requirements. They are either metric values (accumulated over multiple hops of a call) or attributes (a gating criterion that is not accumulated, but is checked at each interface). Maximum cell transfer delay and peak-to-peak cell delay variation are metrics, while cell loss ratio is an attribute.


Note Default objective values for QoS for guaranteed service categories can be configured for UNI  4.0 signalling.

Table 8-2 lists the default values of the QoS objective table.


Table 8-2: Default QoS Objective Table
Service
Category
Max Cell Transfer
Delay (clp01)
Peak-to-Peak Cell Delay Variation (clp01) Cell Loss
Ratio (clp0)
Cell Loss Ratio
(clp0+1)

cbr

Undefined

Undefined

Undefined

Undefined

vbr-rt

Undefined

Undefined

Undefined

Undefined

vbr-nrt

---

---

Undefined

Undefined

Row Contents

Each objective can have a defined or undefined value. If undefined, the objective is not considered in connection setup.

This table should be configured with the same values for an entire network.

To configure the default QoS objective table, perform the following tasks in global configuration mode:
Step Command Task
1

atm qos default {cbr | vbr-rt} max-cell-transfer-delay {microseconds | any}

Select the ATM QoS default CBR or VBR-RT maximum cell transfer delay.

2

atm qos default {cbr | vbr-rt} peak-to-peak- cell-delay variation {microseconds | any}

Select the ATM QoS default CBR or VBR-RT peak-to-peak cell delay variation.

3

atm qos default {cbr | vbr-rt | vbr-nrt} max-cell-loss-ratio [clp0 | clp1plus0] {loss-ratio-exponent| any}

Select the ATM QoS default CBR, VBR-RT, or VBR-NRT maximum cell loss ratio.

Example

The following example shows how to change the CBR maximum cell loss ratio objective for cell loss priority (CLP) = 0+1 to 10-12 cells per second:

Switch(config)# atm qos default cbr max-cell-loss-ratio clp1plus0 12

Display the ATM QoS Objective Table

To display the default QoS objective table, use the following EXEC command :
Command Task

show atm qos-defaults

Display the ATM QoS objective table configuration.

The per-service category, maximum cell transfer delay, peak-to-peak cell delay variation, and maximum cell loss ratio objectives are displayed.

Example

The ATM QoS objective table configuration is displayed in the following example:

Switch# show atm qos-defaults
Default QoS objective table:
    Max cell transfer delay (in microseconds): any cbr, any vbr-rt
    Peak-to-peak cell  delay variation (in microseconds): any cbr, any vbr-rt
    Max cell loss ratio for CLP0 cells: any cbr, any vbr-rt, any vbr-nrt
    Max cell loss ratio for CLP0+1 cells:  10**(-12) cbr, any vbr-rt, any vbr-nrt

Configure the Switch Oversubscription Factor

The switch oversubscription factor (OSF) is used in determining initial port maximum queue sizing for VBR-NRT and available bit rate/unspecified bit rate (ABR/UBR) queues.


Note This value can be changed at any time, but it is only used at start-up and when a module is hot-swapped from the chassis.

The size of the VBR-NRT queue and ABR-UBR queues is determined by the following equations, where the default size of the CBR and VBR queues vary by interface type, as listed in Table 8-3:

Default Size (VBR-NRT) = 0.25 * ((OSF * 2048) - DefaultSize(CBR) - DefaultSize 
(VBR-RT))
Default Size (ABR-UBR) = 0.75 * ((OSF * 2048) - DefaultSize(CBR) - DefaultSize 
(VBR-RT))

Table 8-3:
Interface Type Default Max Size CBR Queue Default Max Size Type
VBR-RT Queue

SONET

256

256

DS3/E3

256

512

Default
CBR and VBR Determined by Interface Type

To configure the OSF, use the following global configuration command:
Command Task

atm over-subscription-factor o-value

Configure the switch OSF from 1 to 32.


Note Over subscription factor configuration is only possible on switches with FC-PCQ installed.
Example

The following example shows how to set the switch over subscription factor to 16:

Switch(config)# atm over-subscription-factor 16

Display the OSF Configuration

To display the OSF configuration, use the following EXEC command:
Command Task

show atm resource

Display the OSF configuration.


Note The following examples differ depending on the feature card installed in your switch.
Examples

The following example shows the switch OSF configuration with FC-PCQ installed:

Switch> show atm resource
Resource configuration:

      Over-subscription-factor 16 Sustained-cell-rate-margin-factor 1% Abr-mode: relative-rate Atm service-category-limit (in cells): 64544 cbr 64544 vbr-rt 64544 vbr-nrt 64544 abr-ubr Resource state: Cells per service-category: 0 cbr 0 vbr-rt 0 vbr-nrt 0 abr-ubr

The following example shows the switch OSF configuration with FC-PFQ installed:

Switch> show atm resource
Resource configuration:

      Over-subscription-factor 8 Sustained-cell-rate-margin-factor 1% Abr-mode: relative-rate Service Category to Threshold Group mapping: cbr 1 vbr-rt 2 vbr-nrt 3 abr 4 ubr 5 Threshold Groups: Group Max Max Q Min Q Q thresholds Cell Name cells limit limit Mark Discard count instal instal instal --------------------------------------------------- 1 65535 63 63 25 % 87 % 0 cbr-default-tg 2 65535 127 127 25 % 87 % 0 vbrrt-default-tg 3 65535 511      31         25 % 87 % 0 vbrnrt-default-tg 4 65535  511      31         25 % 87 % 0 abr-default-tg 5 65535  511      31         25 % 87 % 0 ubr-default-tg 6 65535 1023 1023 25 % 87 % 0 well-known-vc-tg

Configure the Service Category Limit

The service category limit configuration restricts the number of cells admitted into the switch, as determined by the type of output queues.


Note Service category limit configuration is only possible on switches with FC-PCQ installed.
Caution Setting a service category limit to 0 causes the connection requests for the associated service categories to be rejected.

To configure the service category limits, use the following global configuration command:
Command Task

atm service-category-limit {cbr | vbr-rt | vbr-nrt | abr-ubr} l-value

Configure ATM service category limits for a specific output queue.


Note The atm service-category-limit command affects all connections, including those already established.
Example

The following example shows how to change the service category limit for the CBR cells within the switch fabric to 3000 cells:

Switch(config)# atm service category-limit cbr 3000

Display the Service Category Limit Configuration

To display the service category limit configuration, use the following EXEC command:
Command Task

show atm resource

Display the service category limits configuration.

Example

The following example shows the service category limits configuration:

Switch> show atm resource
Resource configuration:
    Over-subscription-factor 16  Sustained-cell-rate-margin-factor 1%
    Abr-mode:   relative-rate

      Atm service-category-limit (in cells): 3000 cbr 64544 vbr-rt 64544 vbr-nrt 64544 abr-ubr Resource state: Cells per service-category: 0 cbr 0 vbr-rt 0 vbr-nrt 0 abr-ubr

Configure the ABR Congestion Notification Mode

The ABR congestion notification mode changes the type of notification used on ABR connections to alert the end station of congestion. ABR mode configuration determines whether ABR uses explicit forward congestion indication (EFCI) marking, relative-rate marking, or both, for rate management on ABR connections.

The global configuration function is used to modify the ABR mode selection for all ABR  connections.

To configure the ABR mode, use the following global configuration command:
Command Task

atm abr-mode {efci | relative-rate | all}

Configure ABR congestion notification mode.


Note The atm abr-mode command affects all connections, including those already established.
Example

The following example shows how to configure the entire switch to set the EFCI bit whenever a cell arrives on a congested ABR connection:

Switch(config)# atm abr-mode efci

Display the ABR Congestion Notification Mode Configuration

To display the ABR congestion notification mode configuration, use the following EXEC command:
Command Task

show atm resource

Display the ABR congestion notification mode configuration.


Note The following examples differ depending on the feature card installed in your switch.
Examples

The following example shows the ABR mode configuration with FC-PCQ installed:

Switch> show atm resource
Resource configuration:
    Over-subscription-factor 16  Sustained-cell-rate-margin-factor 1%

      Abr-mode: efci Atm service-category-limit (in cells): 3000 cbr 64544 vbr-rt 64544 vbr-nrt 64544 abr-ubr Resource state: Cells per service-category: 0 cbr 0 vbr-rt 0 vbr-nrt 0 abr-ubr

The following example shows the ABR mode configuration with FC-PFQ installed:

Switch> show atm resource
Resource configuration:
    Over-subscription-factor 8  Sustained-cell-rate-margin-factor 1%

      Abr-mode: efci Service Category to Threshold Group mapping: cbr 1 vbr-rt 2 vbr-nrt 3 abr 4 ubr 5 Threshold Groups: Group Max Max Q Min Q Q thresholds Cell Name cells limit limit Mark Discard count instal instal instal --------------------------------------------------- 1 65535 63 63 25 % 87 % 0 cbr-default-tg 2 65535 127 127 25 % 87 % 0 vbrrt-default-tg 3 65535 511      31        25 % 87 % 0 vbrnrt-default-tg 4 65535 511        31          25 % 87 % 0 abr-default-tg 5 65535 511       31         25 % 87 % 0 ubr-default-tg 6 65535 1023 1023 25 % 87 % 0 well-known-vc-tg

Configure the Connection Traffic Table

A row in the CTT must be created for each unique combination of traffic parameters. Virtual path links (VPLs) and virtual channel links (VCLs) then specify traffic by specifying a row in the table per flow (receive and transmit). Many VCL/VPLs can refer to the same row in the traffic table.

Switches with FC-PFQ and software version 11.2(8) or later releases installed on the processor have more rows of various service categories that allow you to specify the following features:

If your switch has FC-PCQ installed on the processor you cannot take advantage of these new capabilities. CTT rows specifying these new parameters can be configured with FC-PCQ installed, with the following effect:

PVC Connection Traffic Rows

The CTT in a permanent virtual channel (PVC) setup requires storing PVC traffic values in a CTT data structure. Rows used for PVCs are called stable rows, and contain traffic parameters.

SVC Connection Traffic Rows

The CTT in a switched virtual circuit (SVC) setup provides a row identifier that Simple Network Management Protocol (SNMP) or the user interface can use to read or display SVC traffic parameters. A CTT row index is stored in the connection-leg data structure for each flow of the connection.


Note Rows cannot be deleted while in use by a connection.

CTT Row Allocations and Defaults

To make CTT management software more efficient, the CTT row-index space is split into rows allocated as a result of signalling and rows allocated from the CLI and SNMP. Table 8-4 describes the row-index range for both.


Table 8-4: CTT Row-Index Allocation
Allocated by Row-index range

ATOMMIB Traffic Descriptor Table /

CLI connection-traffic-table-row creation

1 through 1,073,741,823

Signalling VxL creation

1,073,741,824 through 2,147,483,647

Table 8-5 describes the well-known, predefined ATM CTT rows.


Table 8-5: Default ATM Connection Traffic Table Rows
CTT Row
Index
Service
Category
Peak-Cell-Rate
(CLP01)
Sustained-
Cell-Rate
(clp01)
Tolerance Use

1

UBR

7113539

---

None

Default PVP/PVC row index

2

CBR

424 kbps

---

None

CBR tunnel well-known (WK) VCs

3

VBR-RT

424 kbps

424 kbps

50

Physical interface/VBR-RT WK VCs

4

VBR-NRT

424 kbps

424 kbps

50

VBR-NRT tunnel WK VCs

5

ABR

424 kbps

---

None

---

6

UBR

424 kbps

---

None

UBR tunnel WK VCs

The atm connection-traffic-table-row command supports these service categories: CBR, VBR-RT, VBR-NRT, ABR, and UBR). To create or delete an ATM CTT row, perform the following tasks in global configuration mode:


Note Your CTT feature set will depend on the type feature card that is installed on the processor.

Step Command Task
1

atm connection-traffic-table-row [index row-index] {vbr-rt | vbr-nrt} pcr pcr_value {scr10 scr0} scr_value [mbs mbs_value] [cdvt cdvt_value]

Configure an ATM CTT VBR row.

2

atm connection-traffic-table-row [index row-index] cbr pcr pcr_value [cdvt cdvt_value]

Configure an ATM CTT CBR row.

3

atm connection-traffic-table-row [index row-index] abr pcr pcr_value [mcr mcr_value] [cdvt cdvt_value]

Configure an ATM CTT ABR row.

4

atm connection-traffic-table-row [index row-index] ubr pcr pcr_value [mcr mcr_value] [cdvt cdvt_value]

Configure an ATM CTT UBR row.

If you do not specify an index row number, the system software determines if one is free and displays it in the allocated index field if the command is successful.

Example

The following example shows how to configure an ATM CTT row with an ABR peak cell rate of 30,000 kilobits per second:

Switch(config)# atm connection-traffic-table-row abr pcr 30000
 Allocated index = 63999

Display the ATM Connection Traffic Table

To display the CTT configuration, use the following EXEC command:
Command Task

show atm connection-traffic-table [row row-index | from-row row-index]

Display the CTT configuration.

Example

The following example shows how to display the CTT configuration table:

Switch> show atm connection-traffic-table
Row      Service-category    pcr        scr/mcr       mbs         cdvt
1            ubr          7113539        none                     none
2            cbr              424                                 none
3            vbr-rt           424         424          50         none
4            vbr-nrt          424         424          50         none
5            abr              424           0                     none
6            ubr              424        none                     none
64000        cbr             1741                                 none
2147483645*  ubr                0        none                     none
2147483646*  ubr                1        none                     none
2147483647*  ubr          7113539        none                     none

Configure the Sustained Cell Rate Margin Factor

The sustained cell rate margin factor determines the aggressiveness of weighting sustainable cell rate (SCR) compared to peak cell rate (PCR). It uses the connection admission control algorithm in admitting VBR connections.

To configure the SCR for your switch, use the following global configuration command:
Command Task

atm sustained-cell-rate-margin-factor s-value

Configure the sustained cell rate margin factor.


Note The atm sustained-cell-rate-margin-factor command affects subsequent connections but not connections that are already established.
Example

The following example shows how to configure the SCR margin factor as 85 percent of maximum:

Switch(config)# atm sustained-cell-rate-margin-factor 85

Display the SCR Margin Configuration

To display the SCR margin factor configuration, use the following EXEC command:
Command Task

show atm resource

Display the SCR margin factor configuration.

Examples

The following example shows the SCR margin factor configuration with FC-PCQ installed:

Switch> show atm resource
Resource configuration:

       Over-subscription-factor 8 Sustained-cell-rate-margin-factor 85% Abr-mode: EFCI Atm service-category-limit (in cells): 3000 cbr 64512 vbr-rt 64512 vbr-nrt 64512 abr-ubr Resource state: Cells per service-category: 0 cbr 0 vbr-rt 0 vbr-nrt 0 abr-ubr

The following example shows the SCR margin factor configuration with FC-PFQ installed:

Switch> show atm resource
Resource configuration:

      Over-subscription-factor 8 Sustained-cell-rate-margin-factor 1% Abr-mode: relative-rate Service Category to Threshold Group mapping: cbr 1 vbr-rt 2 vbr-nrt 3 abr 4 ubr 5 Threshold Groups: Group Max Max Q Min Q Q thresholds Cell Name cells limit limit Mark Discard count instal instal instal --------------------------------------------------- 1 65535 63 63 25 % 87 % 0 cbr-default-tg 2 65535 127 127 25 % 87 % 0 vbrrt-default-tg 3 65535 511       31         25 % 87 % 0 vbrnrt-default-tg 4 65535  511       31         25 % 87 % 0 abr-default-tg 5 65535  511       31         25 % 87 % 0 ubr-default-tg 6 65535 1023 1023 25 % 87 % 0 well-known-vc-tg

Configure the Threshold Group

Threshold groups combine VCs/VPs to determine per-connection thresholds, based on the use of memory by the group.


Note You must have FC-PFQ installed on your processor to configure this feature. See the section "Processor Feature Card Configuration Affects Resource Management" for additional information.

The initial default configuration of per-VC queueing on the switch has all connections of a service category assigned to one threshold group. However, the assignment of service categories to threshold groups is configurable. A service category cannot be mapped to more than one threshold group. If you configure a service category to a threshold group more than once, the last configuration will be in effect. The default assigns each service category to a different threshold group. However, you can assign more than one service category to a threshold group.


Note The configuration of threshold groups is static, not dynamic.

As a threshold group congests (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value), the maximum number of cells per-queue shrinks from the threshold group max-queue-limit to min-queue-limit.


Note If the max- and min-queue-limits are equal, the queue size does not reduce as the group congests.

In the congestion range of 0 cells (uncongested) to 1/8th full, the connection queues are limited to max-queue-size. In the congestion range of 7/8ths full to completely full, the connection queues are limited to min-queue-size.

The switch hardware cannot provide all possible max-cell values in the range. Instead, the max-cell value used is the closest number of cells greater than that specified. The possible values are {(64*i)-1,  1<=i<=1024}.

Also, the switch hardware is not capable of providing all possible max-queue-limit values in the range. Instead, the max-queue-limit value used is the closest number of cells greater than that specified. The possible values are {(16*i)-1, 2<=i<=1024}. The hardware can support all values of min-queue-size (1-1023).

The threshold group configuration parameters are as follows:

Configuration parameter defaults are defined in Table 8-6.


Table 8-6:
Group Max
Cells
Max
Q Limit
Min
Q Limit
Mark
Threshold
Discard
Threshold
Use

1

131071

63

63

25%

87%

CBR

2

131071

127

127

25%

87%

VBR-RT

3

131071

511

31

25%

87%

VBR-NRT

4

131071

511

31

25%

87%

ABR

5

131071

511

31

25%

87%

UBR

6

131071

1023

1023

25%

87%

well-known VCs

Threshold Group Configuration Parameter Defaults

To configure the threshold groups, perform the following tasks in global configuration mode:
Step Command Task
1

atm threshold-group service {cbr | vbr-rt | vbr-nrt | abr | ubr} tg-num 1-6

Assign a service category to a  threshold group.

2

atm threshold-group 1-6 max-cells 0-131071

Configure the maximum number of cells queued for all connections that are members of the threshold group.

3

atm threshold-group 1-6 discard-threshold 0-100

Configure the threshold of per-connection queue-full at which the queue is considered full for CLP discard and EPD.

4

atm threshold-group 1-6 max-queue-limit 31- min (16383, max-cells)

Configure the largest per-vc queue limit that is applied to connections in the threshold group.

5

atm threshold-group 1-6 min-queue-limit
1 - min (1023, max-queue-limit)

Configure the smallest per-vc queue-limit that is applied to connections in the threshold group.

6

atm threshold-group 1-6 name tg-name

Configure the name associated with a threshold group.

7

atm threshold-group 1-6 marking-threshold 0-100

Configure the threshold of per-connection queue-full at which the queue is considered full for EFCI marking and ABR relative-rate marking.

Example

The following example shows how to configure ATM threshold group 5 with a maximum number of cells before the cells are discarded:

Switch(config)# atm threshold-group 5 max-cells 50000

Display the Threshold Group Configuration

To display the threshold group configuration, use the following EXEC command:
Command Task

show atm resource

Display the threshold group configuration.

Example

The following example displays the threshold group configuration:

Switch# show atm resource
Resource configuration:
    Over-subscription-factor 8  Sustained-cell-rate-margin-factor 1%
    Abr-mode:   relative-rate
    Service Category to Threshold Group mapping:
     cbr 1 vbr-rt 2 vbr-nrt 3 abr 4 ubr 5

      Threshold Groups: Group Max Max Q Min Q Q thresholds Cell Name cells limit limit Mark Discard count instal instal instal --------------------------------------------------- 1 65535 63 63 25 % 87 % 0 cbr-default-tg 2 65535 127 127 25 % 87 % 0 vbrrt-default-tg 3 65535 511      31        25 % 87 % 0 vbrnrt-default-tg 4 65535  511      31        25 % 87 % 0 abr-default-tg 5 65535  511      31        25 % 87 % 0 ubr-default-tg 6 65535 1023 1023 25 % 87 % 0 well-known-vc-tg

Configuring the Physical Interface

Physical interface RM configurations affect only specific interfaces on the switch. The following sections describe physical interface configuration RM tasks:

Configure the Interface Maximum Queue Size

Maximum queue size is used to determine the following:


Note Interface maximum queue size configuration is only possible on switches with FC-PCQ installed on your processor.

Because not all queue size values are supported by the switch fabric, the value installed is displayed, as well as the configuration value requested. The value installed is always greater than or equal to that requested.

To configure the maximum queue size, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port

Select the interface to be configured.

2

atm output-queue [force] {cbr | vbr-rt | vbr-nrt | abr-ubr} max-size size-number

Configure the ATM output queue maximum size.


Note The atm output-queue command affects all connections, including those already established.

This command is not applicable for subinterface level configuration. For other restrictions, see the LightStream  1010 ATM Switch and Catalyst  8510 MSR Command Reference publication.

If the interface status is up, the force parameter is required before the request is completed. If the request is forced, output on the interface is briefly disabled, cells on the output queue are discarded, and the queue size is changed to the new limit. Any impact on existing connections by the implicit change in guaranteed maximum CTD and peak-to-peak CDV is not considered before making the change. Subsequent setup of SVC connections will be affected.


Note The queue must be momentarily disabled to change the threshold.
Example

The following example shows how to configure the CBR ATM output queue maximum size to 30,000 cells:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm output-queue force cbr max-size 30000

Display the Output Queue Maximum Configuration

To display the output queue maximum size configuration, use the following EXEC command:
Command Task

show atm interface resource atm card/subcard/port

Display the output queue maximum size configuration.

Example

The following example displays the interface output queue maximum size configuration with FC-PCQ installed:

Switch> show atm interface resource atm 3/0/0
Resource Management configuration:
    Output queues:

                            Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none abr-ubr Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 abr-ubr Efci threshold: 25% cbr, 25% vbr-rt, 25% vbr-nrt, 25% abr, 25% ubr Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% abr, 87% ubr Abr-relative-rate threshold: 25% abr Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed Service Categories supported: cbr,vbr-rt,vbr-nrt,abr,ubr Link Distance: 0 kilometers Controlled Link sharing: Max aggregate guaranteed services: none RX, none TX Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX, none abr RX, none abr TX, none ubr RX, none ubr TX Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX, none abr RX, none abr TX, none ubr RX, none ubr TX Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX Minimum-cell-rate RX: none abr, none ubr Minimum-cell-rate TX: none abr, none ubr CDVT RX: none cbr, none vbr, none abr, none ubr CDVT TX: none cbr, none vbr, none abr, none ubr MBS: none vbr RX, none vbr TX Resource Management state: Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 abr-ubr Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 1 pvcs, 0 svcs

Configure the Interface Queue Thresholds per Service Category

The queue thresholds can be specified for the different levels of service and configured on each interface queue. The following queue thresholds can be configured:


Note Interface queue threshold per-service category configuration is only possible on switches with FC-PCQ installed on your processor.

These queue thresholds can be changed at any time. The result changes the threshold for all connections of that service category using the interface for output and for any subsequent connections.


Note The CLP and PD discard threshold and ABR relative rate threshold have finer granularity than the EFCI threshold.

To configure the output threshold, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port

Select the interface to be configured.

2

atm output-threshold {cbr | vbr-rt | vbr-nrt | abr | ubr} discard-threshold disc-thresh-num

Configure the ATM output discard threshold.

3

atm output-threshold {cbr | vbr-rt | vbr-nrt | abr | ubr} efci-threshold efci-thresh-number

Configure the ATM output threshold.

4

atm output-threshold abr relative-rate abr-thresh-number

Configure the ATM output threshold ABR.


Note These commands affect all connections, including those already established.

These commands are not applicable for subinterface level configurations. For other restrictions, see the LightStream  1010 ATM Switch and Catalyst  8510 MSR Command Reference publication.

Examples

The following example shows how to configure the interface output threshold CBR discard threshold to 87 percent of maximum size:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm output-threshold cbr discard 87

The following example shows how to configure the interface output discard threshold for CBR EFCI threshold to 50 percent of maximum size:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm output-threshold cbr efci 50

Display the Output Threshold Maximum Configuration

To display the output threshold maximum size configuration, use the following EXEC command:
Command Task

show atm interface resource atm card/subcard/port

Display the output threshold maximum size configuration.

Example

The following example shows the interface output threshold maximum size configuration with FC-PCQ installed:

Switch# show atm interface resource atm 3/0/0
Resource Management configuration:
    Output queues:
        Max sizes(explicit cfg): 30000  cbr, none vbr-rt, none vbr-nrt, none abr-ubr
        Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 abr-ubr

               Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% abr, 25% ubr                Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% abr, 87% ubr Abr-relative-rate threshold: 25% abr Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed Service Categories supported: cbr,vbr-rt,vbr-nrt,abr,ubr Link Distance: 0 kilometers Controlled Link sharing: Max aggregate guaranteed services: none RX, none TX Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX, none abr RX, none abr TX, none ubr RX, none ubr TX Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX, none abr RX, none abr TX, none ubr RX, none ubr TX Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX Minimum-cell-rate RX: none abr, none ubr Minimum-cell-rate TX: none abr, none ubr CDVT RX: none cbr, none vbr, none abr, none ubr CDVT TX: none cbr, none vbr, none abr, none ubr MBS: none vbr RX, none vbr TX Resource Management state: Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 abr-ubr Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 1 pvcs, 0 svcs

Configure the Interface Output Pacing

Output pacing is used to artificially reduce the output speed of an interface in kbps. Output pacing can be changed at any time or enabled or disabled. When an output pacing change request is made, RM determines whether the change will not provide the guaranteed bandwidth at the outbound port for the existing virtual channels/virtual paths (VCs/VPs). Guaranteed bandwidth is reserved for CBR and VBR connections.

To enable or change an interface output pacing rate, perform the following tasks, beginning in global configuration mode:
Command Task

interface atm card/subcard/port

Select the interface to be configured.

atm pacing kbps [force]

Configure the interface output pacing.

The force argument indicates that the change should be made even if it results in an output cell rate that does not provide sufficient bandwidth for guaranteed service on the interface transmit flow. The force argument has no effect on systems with FC-PFQ installed on the processor.


Note The atm pacing command affects all connections, including those already established.

This command does not apply to the CPU interfaces (atm0 and ethernet0) or subinterfaces. For other restrictions, see the LightStream  1010 ATM Switch and Catalyst  8510 MSR Command Reference publication.


Note With this release of the software, addressing the interface on the processor (CPU) has changed. The ATM interface is now called atm0, and the Ethernet interface is now called ethernet0. Old formats (atm 2/0/0 and ethernet 2/0/0) are still supported.
Example

The following example shows how to configure the interface output pacing to 10,000 kbps:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm pacing 10000

Display the Output Pacing Configuration

To display the output pacing configuration, use the following EXEC command:
Command Task

show atm interface resource atm card/subcard/port

Display the output pacing configuration.


Note The following example differs depending on the feature card installed on the processor.
Example

The following example shows the interface output pacing configuration:

Switch# show atm interface resource atm 0/0/0
Resource Management configuration:
    Service Classes:
        Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr
        Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5
        WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5

      Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed Link Distance: 0 kilometers Controlled Link sharing: Max aggregate guaranteed services: none RX, none TX Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX, Tolerance RX: none cbr, none vbr, none abr, none ubr Tolerance TX: none cbr, none vbr, none abr, none ubr Resource Management state: Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 147743 abr RX, 147743 abr TX, 147743 ubr RX, 147743 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 0 pvcs, 0 svcs

Configure Controlled Link Sharing

Resource management allows fine-tuning of the connection admission control functions on a per-interface and direction (receive and transmit) basis. The reservations are specified with the following three parameters:

The minimum and maximum parameter relationships are shown in Table 8-7.


Table 8-7: Connection Admission Control Parameter to Bandwidth Relationships
Service Category Value Service Category Bandwidth

Minimum CBR

+

Minimum VBR

<= 95 percent

Minimum CBR

<=

Maximum CBR

<= 95 percent

Minimum VBR

<=

Maximum VBR

<= 95 percent

Minimum CBR

<=

Maximum Aggregate

<= 95 percent

Minimum VBR

<=

Maximum Aggregate

<= 95 percent

Maximum CBR

<=

Maximum Aggregate

<= 95 percent

Maximum VBR

<=

Maximum Aggregate

<= 95 percent

To configure controlled link sharing, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port [.vpt #]

Select the interface to be configured.

2

atm cac link-sharing max-guaranteed-service-bandwidth {receive | transmit} percent

Configure controlled link sharing for the maximum guaranteed service bandwidth.

3

atm cac link-sharing max-bandwidth {abr | cbr | ubr | vbr} {receive | transmit} percent

Configure controlled link sharing for the maximum guaranteed service bandwidth by service category.

4

atm cac link-sharing min-bandwidth {cbr | vbr | abr | ubr} {receive | transmit} percent

Configure controlled link sharing for the minimum guaranteed service bandwidth by service category.


Note These commands affect subsequent connections but not connections that are already established.

For restrictions to these commands, see the LightStream  1010 ATM Switch and Catalyst  8510 MSR Command Reference   publication.

Example

The following example shows how to configure the controlled link sharing, maximum guaranteed service bandwidth, and receive configuration to 87 percent:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cac link-sharing max-guaranteed-service-bandwidth receive 87

Display the Controlled Link Sharing Configuration

To display the controlled link sharing configuration, perform the following task in user EXEC mode:
Command Task

show atm interface resource atm card/subcard/port

Display the controlled link sharing configuration.


Note The following example differs depending on the feature card installed on the processor.
Example

The following example displays the controlled link sharing configuration:

Switch# show atm interface resource atm 0/0/0
Resource Management configuration:
    Service Classes:
        Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr
        Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5
        WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5
    Pacing: disabled   0 Kbps rate configured, 0 Kbps rate installed
    Link Distance: 0 kilometers

     Controlled Link sharing:
             Max aggregate guaranteed services: none RX, none TX
             Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX
              Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX, Tolerance RX: none cbr, none vbr, none abr, none ubr Tolerance TX: none cbr, none vbr, none abr, none ubr Resource Management state: Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 147743 abr RX, 147743 abr TX, 147743 ubr RX, 147743 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 0 pvcs, 0 svcs

Configure the Scheduler and Service Class

A service class denotes one of the scheduling classes referred to as output virtual circuit (OVC) quality of Service (QoS) Classes. Up to eight service classes can be allocated to each physical interface (PIF) port. In scheduling the next cell to be transmitted from a port, the rate scheduler (RS) has first call on supplying an eligible cell. If RS does not have one, then SP/WRR scheduler chooses a service class with an OVC ready to transmit, and finally a VC within the service class is selected.


Note Scheduler and service class configuration is only possible on switches with FC-PFQ installed on your processor.

ATM service categories are mapped statically to service classes, as shown in Table 8-8, where service class 1 has the highest scheduling priority.


Table 8-8: ATM Service Category to Service Class
Service Category Service Class

CBR

1

VBR-RT

2

VBR-NRT

3

ABR

4

UBR

5

The first scheduling decision is made based on whether any rate-scheduled cell is ready (as decided by the timewheel rate scheduler for an interface). Whether a VC uses the rate scheduler is not user-configurable.

Table 8-9 lists the cell rates that are guaranteed by the rate scheduler for each service category.


Table 8-9: Rate Scheduler to Service Category
Service Category Cell Rate Guaranteed

CBR

PCR

VBR-RT

SCR

VBR-NRT

SCR

ABR

MCR (if specified)

UBR

MCR (if specified)

If the timewheel RS does not have an OVC ready to transmit, the strict priority/weighted-round-robin (SP/WRR) scheduler becomes active to pick out an OVC to transmit a cell. The SP/WRR uses the interface bandwidth left over after guaranteed cell service to transmit cells. Thus, an OVC of a service category, other than a CBR OVC, can be serviced by both the rate scheduler and the SP/WRR scheduler. A CBR OVC cannot be serviced by the SP/WRR scheduler because its PCR is already guaranteed by the rate scheduler. (Any additional cell transmission by the SP/WRR out of that OVC is likely to arrive too soon at the next switch and might be policed.)

The following service categories can be serviced by the SP/WRR scheduler:

The combined result of the two schedulers is illustrated in Figure 8-1.


Figure 8-1: Rate and SP/WRR Scheduling of Cells Through an Output Interface


Service classes scheduled by the SP/WRR can be further subdivided into two subsets, one of which is scheduled by strict priority (SP) between classes, the other WRR between classes. The SP subset can be any number of contiguous classes, starting with class 2.


Note Service class 1 serves CBR connections and is not allowed to be a member of the SP/WRR because its PCR is already guaranteed by the rate scheduler.

The WRR subset can be any number of contiguous classes, starting with the class one level lower in priority than the lowest priority class serviced by the SP. Each service class (other than service class 1) must be a member of a subset, and each subset can be null. For example, SP:{2}, WRR:{3,4,5}. The default configuration is SP:{}, WRR:{2,3,4,5}. This assignment of a service class to a subset is configurable.

Figure 8-2 shows the possible subset configurations.


Figure 8-2: Service Class Subset Configuration on SP/WRR


Each service class is assigned a weight for use if it is in the WRR subset. These weights are configurable, in the range of 1 to 15. The default weighting is {8,1,1,1} for classes {2,3,4,5}, respectively. The weighting will not be modified dynamically.

Within service classes, individual OVCs are also weighted, again in the range of 1 to 15. A standard weight (2) is assigned to all PVCs in a service class. Optionally, PVCs can be configured with a specific weight per half-leg (applying to the transmit OVC weight). SVCs take the value 2.

To configure the interface service class and WRR value, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port [.vpt #]

Select the interface to be configured.

2

atm service-class wrr-start  {2 | 3 | 4 | 5 |
none
}

Configure the weighted round robin starting service class.

3

atm service-class {2 | 3 | 4 | 5} wrr-weight 1 -15

Configure the weight given to each service class.

Examples

The following example shows how to configure ATM interface 0/1/0 with a WRR start value of 3:

Switch(config)# interface atm 0/1/0
Switch(config-if)# atm service-class wrr-start 3

The following example shows how to configure service class 3 on interface ATM 0/1/0 with a WRR weight of 5:

Switch(config)# interface atm 0/1/0
Switch(config-if)# atm service-class 3 wrr-weight 5

Display the Interface Service Class Information

To display the configuration of an interface in a service class, use the following EXEC command:
Command Task

show atm int resource {atm | atm-p} {card/subcard/port }

Display the configured membership of the interface in a service class.

Example

The following example shows the configuration of the interface in a service class:

Switch# show atm interface resource atm 0/0/0
Resource Management configuration:

      Service Classes: Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5 WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5 Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed Link Distance: 0 kilometers Controlled Link sharing: Max aggregate guaranteed services: none RX, none TX Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX, Tolerance RX: none cbr, none vbr, none abr, none ubr Tolerance TX: none cbr, none vbr, none abr, none ubr Resource Management state: Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 147743 abr RX, 147743 abr TX, 147743 ubr RX, 147743 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 0 pvcs, 0 svcs

Configuring the Physical and Logical Interface Parameters

The following sections describe interface configuration RM tasks for both physical and logical interface types:

Configure the Outbound Link Distance

Specifying the physical link distance for the next ATM hop in the outbound direction allows you to increase the propagation delay. Propagation delay is used in determining the connection admission control (CAC) maximum CTD provided on the output by a switch interface, which can affect the SVC connection requests accepted.

To configure the ATM link distance, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port [.vpt #]

Select the subinterface to be configured.

2

atm link-distance kilometers

Configure the subinterface link distance.


Note The atm link-distance command affects subsequent connections but not connections that are already established.
Example

The following example shows how to configure the interface link distance configuration to
150 kilometers:

Switch(config-if)# atm link-distance 150

Display the Interface Link Distance Configuration

To display the interface link distance configuration, use the following EXEC command:
Command Task

show atm interface resource atm card/subcard/port [.vpt #]

Display the interface link distance configuration.


Note The following example differs depending on the feature card installed on the processor.
Example

The following example shows the configuration of the interface link distance with FC-PFQ installed:

Switch# show atm interface resource atm 0/0/0
Resource Management configuration:
    Service Classes:
        Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr
        Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5
        WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5
    Pacing: disabled   0 Kbps rate configured, 0 Kbps rate installed

      Link Distance: 150 kilometers Controlled Link sharing: Max aggregate guaranteed services: none RX, none TX Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX, Tolerance RX: none cbr, none vbr, none abr, none ubr Tolerance TX: none cbr, none vbr, none abr, none ubr Resource Management state: Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 147743 abr RX, 147743 abr TX, 147743 ubr RX, 147743 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 0 pvcs, 0 svcs

Configure the Limits of Best-Effort Connections

Each interface can be configured to allow a specific number of best-effort ABR and UBR connections.

To configure the number of best-effort connections, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port [.vpt #]

Select the interface to be configured.

2

atm cac best-effort-limit conn-value

Configure the connection best-effort limit.


Note These commands affect subsequent connections but not connections that are already established.
Example

The following example shows how to configure the connection best-effort limit configuration to 2000:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cac best-effort-limit 2000

Display the Interface Best-Effort Limit Configuration

To display the interface best-effort configuration, use the following EXEC command:
Command Task

show atm interface resource atm card/subcard/port [.vpt #]

Display the subinterface best-effort configuration.


Note The following examples differ depending on the feature card installed on the processor.
Examples

The following example shows the interface best-effort configuration with FC-PCQ installed:

Switch> show atm interface resource atm 3/0/0
Resource Management configuration:
    Output queues:
        Max sizes(explicit cfg): 30000  cbr, none vbr-rt, none vbr-nrt, none abr-ubr
        Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 abr-ubr
        Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% abr, 25% ubr
        Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% abr, 87% ubr
        Abr-relative-rate threshold: 25% abr
    Pacing: enabled   10000 Kbps rate configured, 10000 Kbps rate installed
    Service Categories supported: cbr,vbr-rt,vbr-nrt,abr,ubr
    Link Distance: 150 kilometers
    Controlled Link sharing:
        Max aggregate guaranteed services: 87% Rx,  none TX
        Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX

      Best effort connection limit: enabled 2000 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX Minimum-cell-rate RX: none abr, none ubr Minimum-cell-rate TX: none abr, none ubr CDVT RX: none cbr, none vbr, none abr, none ubr CDVT TX: none cbr, none vbr, none abr, none ubr MBS: none vbr RX, none vbr TX Resource Management state: Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 abr-ubr Available bit rates (in Kbps): 135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 1 pvcs, 0 svcs

The following example shows the interface best-effort configuration of with FC-PFQ installed:

Switch# show atm interface resource atm 0/0/0
Resource Management configuration:
    Service Classes:
        Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr
        Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5
        WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5
    Pacing: disabled   0 Kbps rate configured, 0 Kbps rate installed
    Link Distance: 0 kilometers
    Controlled Link sharing:
        Max aggregate guaranteed services: none RX,  none TX
        Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX

      Best effort connection limit: disabled 0 max connections Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX, Tolerance RX: none cbr, none vbr, none abr, none ubr Tolerance TX: none cbr, none vbr, none abr, none ubr Resource Management state: Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 147743 abr RX, 147743 abr TX, 147743 ubr RX, 147743 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX

Best effort connections: 0 pvcs, 0 svcs

Configure the Interface Maximum of Individual Traffic Parameters

When a VCC is set up, you can specify per-flow (receive and transmit traffic) parameters. Traffic parameter limits may be configured independently by service category and traffic direction for the following:

To configure the traffic parameters, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port [.vpt #]

Select the interface to be configured.

2

atm cac max-peak-cell-rate {cbr | vbr | abr | ubr} {receive | transmit} rate

Configure the connection maximum PCR.

3

atm cac max-sustained-cell-rate {receive | transmit} rate

Configure the connection SCR.

4

atm cac max-cdvt {abr | cbr | ubr | vbr} {receive | transmit} cell-count

Configure the connection maximum CDVT.

5

atm cac max-mbs {receive | transmit} cell-count

Configure the connection maximum MBS.

6

atm cac max-min-cell-rate {abr | ubr} {receive | transmit} rate

Configure the connection maximum MCR per service category flow.


Note These commands cause subsequent connections but not connections that are already established.
Examples

The following example shows how to configure the maximum PCR for for CBR connections on interface 3/0/0, specified in receive mode, to 100,000 kbps:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cac max-peak-cell-rate cbr receive 100000

The following example shows how to configure the maximum SCR for connections on interface 3/0/0, specified in receive mode, to 60,000  kbps:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cac max-sustained-cell-rate receive 60000

The following example shows how to configure the maximum tolerance for CBR connections on interface 3/0/0, specified in receive mode, 75,000  kbps:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cac max-cdvt cbr receive 75000

Display the Interface Maximum Individual Traffic Parameter Configuration

To display the interface maximum individual traffic parameter configuration, use the following EXEC command:
Command Task

show atm interface resource

Display the controlled link sharing configuration.


Note The following examples differ depending on the feature card installed on the processor.
Examples

The following example shows the interface maximum individual traffic configuration with FC-PCQ installed:

Switch> show atm interface resource atm 3/0/0
Resource Management configuration:
    Output queues:
        Max sizes(explicit cfg): 30000  cbr, none vbr-rt, none vbr-nrt, none abr-ubr
        Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 abr-ubr
        Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% abr, 25% ubr
        Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% abr, 87% ubr
        Abr-relative-rate threshold: 25% abr
            Pacing: enabled   10000 Kbps rate configured, 10000 Kbps rate installed
    Service Categories supported: cbr,vbr-rt,vbr-nrt,abr,ubr
    Link Distance: 150 kilometers
    Controlled Link sharing:
        Max aggregate guaranteed services: 87% Rx,  none TX
        Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
    Best effort connection limit: enabled  2000 max connections

         Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: 60000 vbr RX, none vbr TX Minimum-cell-rate RX: none abr, none ubr Minimum-cell-rate TX: none abr, none ubr CDVT RX: 75000 cbr, none vbr, none abr, none ubr CDVT TX: none cbr, none vbr, none abr, none ubr MBS: none vbr RX, none vbr TX Resource Management state: Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 abr-ubr Available bit rates (in Kbps): 135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 1 pvcs, 0 svcs

The following example shows the interface maximum individual traffic configuration with FC-PFQ installed:

Switch# show atm interface resource atm 0/0/0
Resource Management configuration:
    Service Classes:
        Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr
        Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5
        WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5
       Pacing: disabled   0 Kbps rate configured, 0 Kbps rate installed
    Link Distance: 0 kilometers
    Controlled Link sharing:
        Max aggregate guaranteed services: none RX,  none TX
        Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX
    Best effort connection limit: disabled  0 max connections

          Max traffic parameters by service (rate in Kbps, tolerance in cell-times): Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr Sustained-cell-rate: none vbr RX, none vbr TX, Tolerance RX: none cbr, none vbr, none abr, none ubr Tolerance TX: none cbr, none vbr, none abr, none ubr Resource Management state: Available bit rates (in Kbps): 147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX, 147743 abr RX, 147743 abr TX, 147743 ubr RX, 147743 ubr TX Allocated bit rates: 0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX, 0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX Best effort connections: 0 pvcs, 0 svcs

Configure the ATM Default CDVT and MBS

You can change the default cell delay variation tolerance (CDVT) and maximum burst size (MBS) to request for UPC of cells received on the interface for connections that do not individually request a CDVT or MBS value. Use the atm  cdvt-default or atm mbs-default interface configuration commands. To reset the default CDVT for a particular service category to the default value, use the no form of this command.

You can specify CDVT or MBS for PVCs through a connection traffic table row. If no CDVT or MBS is specified in the row, then a per-interface, per-service category default is applied for purposes of UPC on the connection.


Note For signalled connections, CDVT or MBS cannot be signalled and the defaults specified on the interface apply.

To configure the default CDVT and MBS parameters, perform the following task, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port

Specify an ATM interface and enter interface configuration mode.

2

atm cdvt-default {cbr | vbr-rt | vbr-nrt | abr | ubr} num

Configure the ATM CDVT default.

3

atm mbs-default {vbr-rt | vbr-nrt} num

Configure the ATM MBS default.

Example

The following example shows how to change the default tolerance for received cells on VBR-RT connections:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cdvt-default vbr-rt 4000

Display the ATM CDVT and MBS Configuration

To display the ATM CDVT and MBS configuration, use the following EXEC commands:
Command Task

show atm vc

Display the ATM VC CDVT configuration.

show atm vp

Display the ATM VP CDVT configuration.


Note The following examples differ depending on the feature card installed on the processor.
Examples

The following example shows the ATM CDVT and MBS configuration of an ATM VC with FC-PCQ installed:

Switch# show atm vc interface atm 0/1/0 0 100
Interface: ATM0/1/0, Type: oc3suni
VPI = 0  VCI = 100
Status: UP
Time-since-last-status-change: 00:02:51
Connection-type: PVC
Cast-type: point-to-point
Packet-discard-option: disabled
Usage-Parameter-Control (UPC): drop
Number of OAM-configured connections: 0
OAM-configuration: disabled
OAM-states:  Not-applicable
Cross-connect-interface: ATM0/1/3, Type: oc3suni
Cross-connect-VPI = 0
Cross-connect-VCI = 100
Cross-connect-UPC: drop
Cross-connect OAM-configuration: disabled
Cross-connect OAM-state:  Not-applicable
Rx cells: 0, Tx cells: 0
Rx connection-traffic-table-index: 80001
Rx service-category: UBR (Unspecified Bit Rate)
Rx pcr-clp01: 80000
Rx scr-clp01: none
Rx mcr-clp01: none

Rx cdvt: 100
Rx mbs: none Tx connection-traffic-table-index: 80001 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 80000 Tx scr-clp01: none Tx mcr-clp01: none
Tx cdvt: 100
Tx mbs: none

The following example shows the ATM CDVT and MBS configuration of an ATM VC with FC-PFQ installed:

Switch# show atm vc interface atm 0/0/3 0 100
Interface: ATM0/0/3, Type: oc3suni
VPI = 0  VCI = 100
Status: UP
Time-since-last-status-change: 00:00:08
Connection-type: PVC
Cast-type: point-to-point
Packet-discard-option: disabled
Usage-Parameter-Control (UPC): pass
Wrr weight: 32
Number of OAM-configured connections: 0
OAM-configuration: disabled
OAM-states:  Not-applicable
Cross-connect-interface: ATM0/0/2, Type: oc3suni
Cross-connect-VPI = 0
Cross-connect-VCI = 100
Cross-connect-UPC: pass
Cross-connect OAM-configuration: disabled
Cross-connect OAM-state:  Not-applicable
Threshold Group: 2, Cells queued: 0
Rx cells: 0, Tx cells: 0
Tx Clp0:0,  Tx Clp1: 0
Rx Clp0:0,  Rx Clp1: 0
Rx Upc Violations:0, Rx cell drops:0
Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0
Rx connection-traffic-table-index: 9999
Rx service-category: VBR-RT (Realtime Variable Bit Rate)
Rx pcr-clp01: 40000
Rx scr-clp0 : 30000
Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)
Rx mbs: 1024 (from default for interface) Tx connection-traffic-table-index: 9999 Tx service-category: VBR-RT (Realtime Variable Bit Rate) Tx pcr-clp01: 40000 Tx scr-clp0 : 30000 Tx mcr-clp01: none
Tx cdvt: none
Tx mbs: none

The following example shows the ATM CDVT and MBS configuration of an ATM VP with FC-PCQ installed:

Switch# show atm vp interface atm 0/1/0 4
Interface: ATM0/1/0, Type: oc3suni
VPI = 4
Status: UP
Time-since-last-status-change: 00:00:11
Connection-type: PVP
Cast-type: point-to-point
Usage-Parameter-Control (UPC): pass
Number of OAM-configured connections: 0
OAM-configuration: disabled
OAM-states:  Not-applicable
Cross-connect-interface: ATM0/1/3, Type: oc3suni
Cross-connect-VPI = 4
Cross-connect-UPC: pass
Cross-connect OAM-configuration: disabled
Cross-connect OAM-state:  Not-applicable
Rx cells: 0, Tx cells: 0
Rx connection-traffic-table-index: 1
Rx service-category: UBR (Unspecified Bit Rate)
Rx pcr-clp01: 7113539
Rx scr-clp01: none
Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)
Rx mbs: none Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none
Tx cdvt: none
Tx mbs: none

The following example shows the ATM CDVT and MBS configuration of an ATM VP with FC-PFQ installed:

Switch# show atm vp interface atm0/0/3 4
Interface: ATM0/0/3, Type: oc3suni
VPI = 4
Status: UP
Time-since-last-status-change: 00:00:10
Connection-type: PVP
Cast-type: point-to-point
Usage-Parameter-Control (UPC): pass
Wrr weight: 32
Number of OAM-configured connections: 0
OAM-configuration: disabled
OAM-states:  Not-applicable
Cross-connect-interface: ATM0/0/2, Type: oc3suni
Cross-connect-VPI = 4
Cross-connect-UPC: pass
Cross-connect OAM-configuration: disabled
Cross-connect OAM-state:  Not-applicable
Threshold Group: 5, Cells queued: 0
Rx cells: 0, Tx cells: 0
Tx Clp0:0,  Tx Clp1: 0
Rx Clp0:0,  Rx Clp1: 0
Rx Upc Violations:0, Rx cell drops:0
Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0
Rx connection-traffic-table-index: 1
Rx service-category: UBR (Unspecified Bit Rate)
Rx pcr-clp01: 7113539
Rx scr-clp01: none
Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)
Rx mbs: none Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none
Tx cdvt: none
Tx mbs: none

Configure Interface Service Category Support

With interface service category support, you can configure which service categories call admission control will allow on an interface. You can configure interface service category support only on physical interfaces and shaped and hierarchical logical VP tunnel interfaces. The underlying VP for shaped and hierarchical VP tunnel logical interfaces must use the CBR service category. For shaped VP tunnels, only CBR VCs (by default) can migrate across the interface. However, the atm cac service-category command can be used to configure a service category other than CBR for VCs within a shaped VP tunnel. This configuration ensures that your switch shapes traffic according to the aggregate VP traffic contract prior to entry to a service provider network.

For physical interfaces and hierarchical VP tunnels, all service category VCs (by default) can migrate across the interface. However, the atm cac service-category command can be used to explicitly allow or prevent VCs of specified service categories to migrate across the interface.


Note Hierarchical VP tunnels cannot co-exist on a physical interface with tag switching.

Note For information on how to configure your physical and logical VP tunnel interfaces, see the chapter "Configuring ATM Interfaces".

Table 8-10 shows the service category of the shaped VP (always CBR), the service categories you can configure for transported VCs, and a suggested transit VP service category for the tunnel.


Table 8-10:
Shaped VP Tunnel Service Category VC Service Category Suggested Transit VP Service Category

CBR

CBR

CBR

CBR

VBR

CBR or VBR

CBR

ABR1

CBR or VBR

CBR

UBR

Any service category

1We recommend ABR only if the transit VP is set up so that congestion occurs at the shaped tunnel, not in the transit VP.
Service Category Support for Physical/Logical Interfaces

The following restrictions apply to interface service category support:

To configure a service category on an interface, perform the following tasks, beginning in global configuration mode:
Step Command Task
1

interface atm card/subcard/port [.vpt #]

Select the interface to be configured.

2

atm cac service-category {cbr | vbr-rt | vbr-nrt | abr | ubr} {permit | deny}

Configure the service category on the interface.

Example

The following example shows how to configure the ABR service category on ATM interface 3/0/0:

Switch(config)# interface atm 3/0/0
Switch(config-if)# atm cac service-category cbr deny
Switch(config-if)# atm cac service-category abr permit

Display the Service Category on an Interface

To display the service category configured on an interface, use the following EXEC command:
Command Task

show atm interface resource atm card/subcard/port[.vpt #]

Display the controlled link sharing configuration.


Note The following examples differ depending on the feature card installed on your processor.
Examples

The following example shows the service category configuration with FC-PCQ installed:

Switch> show atm interface resource atm 3/0/0
Resource Management configuration:
    Output queues:
        Max sizes(explicit cfg): none cbr, none vbr-rt, none vbr-nrt, none abr-ubr
        Max sizes(installed): 256 cbr, 512 vbr-rt, 4096 vbr-nrt, 11776 abr-ubr
        Efci threshold: 25% cbr, 25% vbr-rt, 25% vbr-nrt, 25% abr, 25% ubr
        Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% abr, 87% ubr
        Abr-relative-rate threshold: 25% abr
    Pacing: disabled   0 Kbps rate configured, 0 Kbps rate installed
    Service Categories supported: cbr,vbr-rt,vbr-nrt,ubr
    Link Distance: 0 kilometers
    Controlled Link sharing:
        Max aggregate guaranteed services: none RX,  none TX
        Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
    Best effort connection limit: disabled  0 max connections
    Max traffic parameters by service (rate in Kbps, tolerance in cell-times):
        Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr
        Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr
        Sustained-cell-rate: none vbr RX, none vbr TX
        Minimum-cell-rate RX: none abr, none ubr
        Minimum-cell-rate TX: none abr, none ubr
        CDVT RX: none cbr, none vbr, none abr, none ubr
        CDVT TX: none cbr, none vbr, none abr, none ubr
        MBS: none vbr RX, none vbr TX
Resource Management state:
    Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 abr-ubr
    Available bit rates (in Kbps):
        1466 cbr RX, 1466 cbr TX, 1466 vbr RX, 1466 vbr TX,
        0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX
    Allocated bit rates:
        0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
        0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX
    Best effort connections: 0 pvcs,  0 svcs

The following example shows the service category configuration with FC-PFQ installed:

Switch> show atm interface resource atm 3/0/0
Resource Management configuration:
    Service Classes:
        Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 abr, c5 ubr
        Scheduling: RS c1 WRR c2, WRR c3, WRR c4, WRR c5
        WRR Weight: 8 c2, 1 c3, 1 c4, 1 c5
    Pacing: disabled   0 Kbps rate configured, 0 Kbps rate installed
    Service Categories supported: cbr,vbr-rt,vbr-nrt,ubr
    Link Distance: 0 kilometers
    Controlled Link sharing:
        Max aggregate guaranteed services: none RX,  none TX
        Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
                       none abr RX, none abr TX, none ubr RX, none ubr TX
    Best effort connection limit: disabled  0 max connections
    Max traffic parameters by service (rate in Kbps, tolerance in cell-times):
        Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr
        Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr
        Sustained-cell-rate: none vbr RX, none vbr TX
        Minimum-cell-rate RX: none abr, none ubr
        Minimum-cell-rate TX: none abr, none ubr
        CDVT RX: none cbr, none vbr, none abr, none ubr
        CDVT TX: none cbr, none vbr, none abr, none ubr
        MBS: none vbr RX, none vbr TX
Resource Management state:
    Available bit rates (in Kbps):
        147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
        0 abr RX, 0 abr TX, 147743 ubr RX, 147743 ubr TX
    Allocated bit rates:
        0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
        0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX
    Best effort connections: 1 pvcs,  0 svcs

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.