Table of Contents

Resource Management Functions
Switch Feature Card Configuration Affects Resource Management
Configuring Global Resource Management

Configure the Default QoS Objective Table

Display the ATM QoS Objective Table

Configure the Connection Traffic Table

PVC Connection Traffic Rows
SVC Connection Traffic Rows

CTT Row Allocations and Defaults

Display the ATM Connection Traffic Table

Configure the Sustained Cell Rate Margin Factor

Display the SCR Margin Configuration

Configure the Threshold Group

Display the Threshold Group Configuration

Configuring the Physical Interface

Configure the Interface Output Pacing

Display the Output Pacing Configuration

Configure Controlled Link Sharing

Display the Controlled Link Sharing Configuration

Configure the Scheduler and Service Class

Display the Interface Service Class Information

Configuring the Physical and Logical Interface Parameters

Configure the Outbound Link Distance

Display the Interface Link Distance Configuration

Configure the Limits of Best-Effort Connections

Display the Interface Best-Effort Limit Configuration

Configure the Interface Maximum of Individual Traffic Parameters

Display the Interface Maximum Individual Traffic Parameter Configuration

Configure the ATM Default CDVT and MBS

Display the ATM CDVT and MBS Configuration

Configure Interface Service Category Support

Display the Service Category on an Interface

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:

• Resource Management Functions

• Switch Feature Card Configuration Affects Resource Management

• Configuring Global Resource Management

• Configuring the Physical Interface

• Configuring the Physical and Logical Interface Parameters

Resource Management Functions

The ATM switch router RM software provides the following functions:

• Network management interface---Includes operational configuration changes (take place immediately), proposed configuration changes (take place on restart), user interface, and status.

• Default quality of service (QoS) objective table management---Since User-Network Interface 3 (UNI 3) signalling does not provide information elements to signal QoS values, RM provides a table that contains default values for QoS.

• Connection Traffic Table (CTT) management---Rather than store traffic parameters for each connection in that connection's data structure, RM manages a table of connection traffic parameters, used by network and connection management.

• Hardware RM---The switch processor feature card provides functionality that include statistic collection, and traffic policing (UPC). See the section "Switch Feature Card Configuration Affects Resource Management" for detailed information.

• Resource Call Admission Control (RCAC)---Determines whether a virtual channel connection/virtual path connection (VCC/VPC) can be admitted (allowed to be set up), based on the available connection resources and requested traffic characteristics.

• Logical interface creation and deletion.

• Private Network-Network Interface (PNNI) metrics---RM supplies PNNI with link metrics for connection routing.

Switch Feature Card Configuration Affects Resource Management

The switch processor feature card available for the ATM switch router provides the required ATM Forum Traffic Management features as described in Table 8-1.

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

• Configure the Connection Traffic Table

• Configure the Sustained Cell Rate Margin Factor

• Configure the Threshold Group

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.

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

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 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.

The rows corresponding to various service categories support the following features:

• Non-zero minimum cell rate (MCR) for UBR+ service categories. UBR+ is a variant of UBR, in which peak cell rate (PCR), MCR, and cell delay variation tolerance (CDVT) are specified in the traffic contract, with a guarantee on MCR.

• Both CDVT and Maximum Burst Size (MBS) for VBR rows. Dual-leaky-bucket UPC is allowed.

• Whether SCR applies to either the CLP0 or CLP0+1 flow of cells. Only one or the other of these flows can be policed.

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.

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-3 describes the row-index range for both.

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

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:

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.

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:

Switch> show atm resource
Resource configuration:


 
  Sustained-cell-rate-margin-factor 85%
Abr-mode:   EFCI
    Service Category to Threshold Group mapping:
     cbr 1 vbr-rt 2 vbr-nrt 3 abr 4 ubr 5
    Threshold Groups:
 Module   Group Max    Max Q  Min Q  Q thresholds  Cell  Name
  ID            cells  limit  limit  Mark Discard  count
                instal instal instal
 ------------------------------------------------------------
  1        1    131071  63     63     25 %  87 %      0     cbr-default-tg
           2    131071  127    127    25 %  87 %      0     vbrrt-default-tg
           3    131071  511    31     25 %  87 %      0     vbrnrt-default-tg
           4    131071  511    31     25 %  87 %      0     abr-default-tg
           5    131071  511    31     25 %  87 %      0     ubr-default-tg
           6    131071  1023   1023   25 %  87 %      0     well-known-vc-tg
===========================================================
  2        1    131071  63     63     25 %  87 %      0     cbr-default-tg
           2    131071  127    127    25 %  87 %      0     vbrrt-default-tg
           3    131071  511    31     25 %  87 %      0     vbrnrt-default-tg
           4    131071  511    31     25 %  50 %      0     abr-default-tg
           5    131071  511    31     25 %  87 %      0     ubr-default-tg
           6    131071  1023   1023   25 %  87 %      0     well-known-vc-tg
===========================================================
  7        1    131071  63     63     25 %  87 %      0     cbr-default-tg
           2    131071  127    127    25 %  87 %      0     vbrrt-default-tg
           3    131071  511    31     25 %  87 %      0     vbrnrt-default-tg
           4    131071  511    31     25 %  87 %      0     abr-default-tg
           5    131071  511    31     25 %  87 %      0     ubr-default-tg
           6    131071  1023   1023   25 %  87 %      0     well-known-vc-tg
===========================================================
  8        1    131071  63     63     25 %  87 %      0     cbr-default-tg
           2    131071  127    127    25 %  87 %      0     vbrrt-default-tg
           3    131071  511    31     25 %  87 %      0     vbrnrt-default-tg
           4    131071  511    31     25 %  87 %      0     abr-default-tg
           5    131071  511    31     25 %  87 %      0     ubr-default-tg
           6    131071  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.

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.

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.

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:

• Maximum number of cells in threshold group

• Marking threshold percent full of per-VC queue

• Discard threshold percent full of per-VC queue

• Maximum (uncongested) per-VC queue limit in cells

• Minimum (congested) per-VC queue limit in cells

Each module has its own cell memory and threshold groups. There are 8 of these modules in a 20 gigabyte configuration. Each module has a 128 kbps cell memory, and the threshold groups can be configured per module. By default, all the threshold groups of all the modules are configured identically. Configuration parameter defaults are defined in Table 8-5.

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:
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:
 Module   Group Max    Max Q  Min Q  Q thresholds  Cell  Name
  ID            cells  limit  limit  Mark Discard  count
                instal instal instal
 ------------------------------------------------------------
  1        1    131071  63     63     25 %  87 %      0     cbr-default-tg
           2    131071  127    127    25 %  87 %      0     vbrrt-default-tg
           3    131071  511    31     25 %  87 %      0     vbrnrt-default-tg
           4    131071  511    31     25 %  87 %      0     abr-default-tg
           5    131071  511    31     25 %  87 %      0     ubr-default-tg
           6    131071  1023   1023   25 %  87 %      0     well-known-vc-tg
===========================================================
  2        1    131071  63     63     25 %  87 %      0     cbr-default-tg
           2    131071  127    127    25 %  87 %      0     vbrrt-default-tg
           3    131071  511    31     25 %  87 %      0     vbrnrt-default-tg
           4    131071  511    31     25 %  50 %      0     abr-default-tg
           5    131071  511    31     25 %  87 %      0     ubr-default-tg
           6    131071  1023   1023   25 %  87 %      0     well-known-vc-tg
===========================================================
<information deleted>

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 Output Pacing

• Configure Controlled Link Sharing

• Configure the Scheduler and Service Class

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.

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.

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:

• Maximum aggregate guaranteed cell rate on an interface, which limits the guaranteed bandwidth that can be allocated on an interface

• Maximum guaranteed cell rates on an interface per-service category

• Minimum guaranteed cell rates on an interface per-service category

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

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.

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.

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

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

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 combined result of the two schedulers is illustrated in Figure 8-1.

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.

Figure 8-2 shows the possible subset configurations.

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

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

• Configure the Limits of Best-Effort Connections

• Configure the Interface Maximum of Individual Traffic Parameters

• Configure the ATM Default CDVT and MBS

• Configure Interface Service Category Support

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.

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.

Example

The following example shows the configuration of the interface link distance with switch processor feature card 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
    Service Categories supported: cbr,vbr-rt,vbr-nrt,abr,ubr


 
  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,
                       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,
        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.

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.

Example

The following example shows the interface best-effort configuration with the switch processor feature card 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,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: 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:
    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:

• Maximum peak cell rate (PCR)

• Maximum sustained cell rate (SCR)

• Maximum cell delay variation tolerance (CDVT)

• Maximum burst size (MBS)

• Maximum minimum cell rate (MCR)

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.

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,000kbps:

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,000kbps:

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.

Example

The following example shows the interface maximum individual traffic configuration with switch processor feature card 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,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: 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:
    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.

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.

Examples

The following example shows the ATM CDVT and MBS configuration of an ATM VC:

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:

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.

Table 8-9 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.

The following restrictions apply to interface service category support:

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.

Example

The following example shows the service category configuration:

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

Posted: Thu Sep 2 10:23:44 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.