cc/td/doc/product/dsl_prod/ios_dsl/rel121
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring Resource Management

Resource Management Functions

Creating a Connection Traffic Table Row for PVC Traffic Parameters

Enabling and Disabling the clp-drop Flag

Queueing and Buffering

Configuring the Input Queue Discard Threshold

Configuring the Interface Queue Thresholds

Configuring Modem Port Input Maximum Queue Size

Configuring QoS Default Values

Configuring clp-drop Setting

Configuring the Default QoS Objective Table

Configuring the Connection Traffic Table

Configuring PVC Connection Traffic Rows

Configuring SVC Connection Traffic Rows

Configuring the Sustained Cell Rate Margin Factor

Configuring the Number of Best-Effort UBR Connections

Configuring the Maximum Value of Individual Traffic Parameters

Reserving Guaranteed Bandwidth for a Service Category

Display the Resource Management Configuration

Configuring the Allowed Service Categories

Configuring the Propagation Delay (Link Distance)

Configuring a CDVT and MBS Default

Configuring CAC Functions for Specific Interfaces and Directions

Configuring the Physical and Logical Interface Parameters

Configuring the Outbound Link Distance

Configuring the Limits of Best-Effort Connections

Configuring the Interface Maximum of Individual Traffic Parameters

Configuring the ATM Default CDVT and MBS

Display the ATM CDVT and MBS Configuration

Configuring Interface Service Category Support


Configuring Resource Management

This chapter describes resource management functions for Cisco DSLAMs with NI-2 cards. Resource management 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 contains these sections:

• Resource Management Functions

• Creating a Connection Traffic Table Row for PVC Traffic Parameters

• Enabling and Disabling the clp-drop Flag

• Queueing and Buffering

• Configuring QoS Default Values

• Configuring clp-drop Setting

• Configuring the Default QoS Objective Table

• Configuring the Connection Traffic Table

• Configuring the Number of Best-Effort UBR Connections

• Configuring the Maximum Value of Individual Traffic Parameters

• Reserving Guaranteed Bandwidth for a Service Category

• Configuring the Allowed Service Categories

• Configuring the Propagation Delay (Link Distance)

• Configuring a CDVT and MBS Default

• Configuring CAC Functions for Specific Interfaces and Directions

• Configuring the Physical and Logical Interface Parameters

Resource Management Functions

The DSLAM resource management software provides these functions:

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

•Default quality of service (QoS) objective table management—Because User-Network Interface 3 (UNI 3) signaling does not provide information elements to signal QoS values, resource management 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, resource management manages a table of connection traffic parameters, used by network and connection management.

•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—Resource management supplies PNNI with link metrics for connection routing.

Creating a Connection Traffic Table Row for PVC Traffic Parameters

To properly manage your connection resources, you must create a row in the Connection Traffic Table (CTT) for each unique combination of traffic parameters used on a PVC flow.

To create a row in the CTT for CBR and UBR traffic parameters, use these commands:

Step
Command
Task

1.

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

Selects the row-index, pcr-value, and cdvt-value.

2.

atm connection-traffic-table-row [index row-index] ubr pcr pcr-value [mcr mcr-value] [cdvt cdvt-value]

Selects the row-index, pcr-value, mcr-value, and cdvt-value.

3.

atm connection-traffic-table-row [index row-index]
pcr pcr-value [vbr-rt | vbr-nrt]
[scr10 scr0 scr-value] [mbs mbs-value] [cdvt cdvt-value]

Selects the row-index, pcr-value, scr-value, mbs-value, and cdvt-value.


Note The DSLAM does not distinguish between cells that have SCR = 10 and cells that have SCR = 0 with respect to the policing of incoming cells. Therefore there is effectively no difference in the configuration when SCR10 or SCR0 is chosen. This also applies to any values that display as the result of a show command.

Note No traffic shaping or policing is available in the downstream direction.

Example

This example creates the index row in the CTT for UBR traffic parameters with a row index of 15 and a pcr value of 424, and displays the results:

DSLAM# atm connection-traffic-table-row index 15 ubr pcr 424
DSLAM# 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
15           ubr 424 none none
64000 cbr 1741 none
2147483645* ubr 0 none none
2147483646* ubr 1 none none
2147483647* ubr 7113539 none none

Enabling and Disabling the clp-drop Flag

This section describes how to enable or disable the clp-drop flag for selected traffic parameters.

To enable or disable the clp-drop flag, follow these steps:

Step
Command
Task

1.

DSLAM# configure terminal

Go to the global command level.

2.

DSLAM(config)# atm clp-drop {cbr | vbr-rt | vbr-nrt | ubr} {off | on}

Enable or disable the clp-drop flag for selected traffic parameters.


When the clp-drop flag is enabled, the software drops cells when the specified service-category queues reach 50 percent of the discard threshold limit.

Example

This example enables the clp-drop flag for ubr traffic and displays the results:

DSLAM# configure terminal
DSLAM(config)# atm clp-drop ubr on
DSLAM(config)# exit
DSLAM# show atm resource
Resource configuration:
Over-subscription-factor 8 Sustained-cell-rate-margin-factor 64%
Abr-mode: relative-rate

Subtended Port Input queue Configuration:
Max sizes: 5000 cbr, 1024 vbr-rt, 8192 vbr-nrt, 8192 ubr
Discard threshold: 75% cbr, 50% vbr-rt, 50% vbr-nrt, 50% ubr

>CLP Drop configuration:
  cbr : off, vbr-rt : off, vbr-nrt : off, ubr : on

Queueing and Buffering

The DSLAM architecture has two stages of queueing and buffering that guarantee fairness across subtended interfaces:

•Upstream cells from the local modem shelves, as well as upstream cells from the subtended interfaces, are first queued in the input queues. There are separate sets of input queues for each of the 13 possible subtended shelves. The upstream cells are enqueued based on the shelf number they originated from.

•The input queues are then emptied to output queues in a manner that ensures fairness and the QoS guarantees. All downstream cells and all cells to and from the local management processor bypass the input queues and go directly to the output queues.

The sections that follow describe how to manage the sizes of these input queues.

Note Queue sizes are based on the number of cells, but the number of cells must be a power of 2.

Configuring the Input Queue Discard Threshold

This section describes how to set the input queue discard threshold value for subtended ports for selected traffic parameters.

Note Cisco recommends that you leave the input queue discard thresholds set to their default values, which are adequate for most configurations.

The atm input-threshold command controls the discard threshold settings for up to 52 input queues— one queue for each of four traffic types on each of up to 13 nodes in a subtending group:

(13 shelves)*(4 priorities) = 52 input queues

You can figure each priority differently, but all 13 of the potential shelves share the same queue size at any particular priority. Both the point at which all further cells are dropped, and the point at which EPD drops begin are based on the EPD setting.

The behavior of the input queues is affected not only by the input queue discard threshold settings, but also by the setting of the intelligent packet discard (PD) feature, which is controlled with the atm pvc command. The PD setting determines whether the system performs packet-based discards or cell-based discards:

•When PD is enabled, the system performs packet-based discards—that is, when discarding is triggered, the system drops data from the first cell dropped, up to the end of the current AAL5 packet.

This discard method includes policer and partial packet discard (PPD) drops, or entire AAL5 packets (for early packet discard (EPD) drops). The system accepts or rejects subsequent data on a packet-by-packet basis.

•When PD is disabled, the system performs cell-based discards—that is, when discarding, the system drops a cell at a time, and accepts or rejects subsequent data on a cell-by-cell basis. Cell-based discarding is the default behavior.

The PD setting applies to all discards, whether for reasons of queue exhaustion or policing. PD is disabled by default; use the command atm pvc vpi vci pd {on | off} to enable or disable it.

The input queue discard thresholds work as follows:

•If packet-based discard is in force (the PD feature is enabled), the input queue absorbs packets until the queue reaches the epd threshold. At that point, the queue absorbs the remainder of the current packet, as long as doing so does not cause the queue to fill completely. (The total queue size equals epd value plus drop value.)

After it reaches the epd threshold, the queue drops all subsequent packets until the queue's contents drop below the epd threshold. If the queue fills completely before the current packet finishes, then PPD occurs.

•If cell-based discard is in force (the PD feature is disabled), add the epd and drop threshold values to determine the input queue size. When the queue is full, it drops all subsequent cells until its contents fall below the combined threshold value.

If packet-based discard is in force, you can implicitly configure the input queue discard thresholds for either EPD or PPD. For EPD, configure a drop threshold value that is large enough to allow most packets to enter the queue. Appropriate values for this purpose vary by traffic type, but see the thresholds in the table of defaults, below, for examples of EPD settings. For PPD, configure a small drop threshold value. This forces the system to discard the remainder of the packet that fills up the queue.

To set input queue sizes, use the atm input-queue command, as described in the "Configuring Modem Port Input Maximum Queue Size" section.

The default input queue discard threshold varies by interface type and by traffic priority, as shown here:

Interface
Queue Segment
cbr
vbr-rt
vbr-nrt
ubr

DS3

epd

512 cells

512 cells

4096 cells

4096 cells

drop

512 cells

512 cells

4096 cells

4096 cells

Total queue

1024 cells

1024 cells

8192 cells

8192 cells

OC-3c

epd

2048 cells

2048 cells

8192 cells

8192 cells

drop

2048 cells

2048 cells

8192 cells

8192 cells

Total queue

4096 cells

4096 cells

16384 cells

16384 cells


To set the input queue EPD threshold value for subtended ports for selected traffic parameters, follow these steps:

Step
Command
Task

1.

DSLAM# configure terminal

Go to the global command level.

2.

DSLAM(config)# atm input-threshold {cbr |vbr-rt | vbr-nrt | ubr} {epd | drop} t-value

Set the input queue EPD threshold value (t-value) for the selected traffic parameters.


Example

This example shows you how to set the input queue EPD threshold CBR traffic for subtended ports to 32Kb and displays the results:

DSLAM# configure terminal
DSLAM(config)# atm input-threshold cbr epd 32000

DSLAM# show atm interface resource a0/2 !(Subtended Port output)
Resource Management configuration:
Output queues:
Max sizes(derived): 4096 cbr, 4096 vbr-rt, 32768 vbr-nrt, 32768 ubr
EPD threshold: 2048 cbr, 2048 vbr-rt, 16384 vbr-nrt, 16384 ubr
Drop threshold: 2048 cbr, 2048 vbr-rt, 16384 vbr-nrt, 16384 ubr
Subtended Input queues:
Max queue sizes(Derived): 1024 cbr, 1024 vbr-rt, 8192 vbr-nrt, 8192 ubr
        EPD threshold: 32000 cbr, 512 vbr-rt, 4096 vbr-nrt, 4096 ubr
Drop threshold: 512 cbr, 512 vbr-rt, 4096 vbr-nrt, 4096 ubr
Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,ubr
Link Distance: 0 kilometers
<output deleted>

Configuring the Interface Queue Thresholds

The atm output-threshold command controls the discard threshold settings for up to 1040 output queues. You can specify the output queue discard thresholds for the different levels of service and configure them on each interface queue. You can configure these queue thresholds:

•Output queue cell loss priority (CLP)

•Packet discard (PD) threshold

The command atm output-threshold works on the output queues. Unlike the input queues, each output port has a unique setting specific to one port. As with the input queue settings, each priority can be set independently, and you can set both an EPD threshold and a maximum queue size.

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 Cisco recommends that you leave the output queue discard thresholds set to their default values, which are adequate for most configurations.

The behavior of the output queue is controlled not only by the output queue discard threshold settings, but also by the setting of the intelligent packet discard (PD) feature, which is controlled with the atm pvc command.

The PD setting determines whether the system performs packet-based discards or cell-based discards:

•When PD is enabled, the system performs packet-based discards—that is, when discarding is triggered, the system drops data from the first cell dropped, up to the end of the current AAL5 packet.

This discard method includes policer and partial packet discard (PPD) drops, or entire AAL5 packets (for early packet discard (EPD) drops). The system accepts or rejects subsequent data on a packet-by-packet basis.

•When PD is disabled, the system performs cell-based discards—that is, when discarding, the system drops a cell at a time, and accepts or rejects subsequent data on a cell-by-cell basis. Cell-based discarding is the default behavior.

The PD setting applies to all discards, whether the discards occur for reasons of queue exhaustion or policing. PD is disabled by default; use the command atm pvc vpi vci pd {on | off} to enable or disable it.

The output queue discard thresholds work as follows:

•If packet-based discard is in force (the PD feature is enabled), the output queue absorbs packets until the queue reaches the epd threshold. At that point, the queue absorbs the remainder of the current packet, as long as doing so does not cause the queue to fill completely. (The total queue size equals epd value plus drop value.)

After it reaches the epd threshold, the queue drops all subsequent packets until the queue's contents drop below the epd threshold. If the queue fills completely before the current packet finishes, then PPD occurs.

•If cell-based discard is in force (the PD feature is disabled), simply add the epd and drop threshold values to determine the output queue size. When the queue is full, it drops all subsequent cells until its contents fall below the combined threshold value.

If packet-based discard is in force, you can implicitly configure the output queue discard thresholds for either EPD or PPD. For EPD, configure a drop threshold value that is large enough to allow most packets to enter the queue. Appropriate values for this purpose vary by traffic type, but see the thresholds in the table of defaults, below, for examples of EPD settings. For PPD, configure a very small drop threshold value. This forces the system to discard the remainder of the packet that fills up the queue.

The default output queue discard threshold varies by traffic priority, as shown here:

Queue Segment
cbr
vbr-rt
vbr-nrt
ubr

epd

128 cells

128 cells

1024 cells

1024 cells

drop

128 cells

128 cells

1024 cells

1024 cells

Total queue

256 cells

256 cells

2048 cells

2048 cells


To configure the output threshold, perform this task, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select the interface to be configured.

2.

atm output-threshold {cbr | vbr | abr-ubr} {epd | drop} disc-thresh-num

Set the atm output epd/drop threshold to the percentage disc-thresh-num.


Note These commands affect all connections, including those already established. These commands do not apply to subinterface level configurations.

Example

This example shows how to configure the interface output threshold CBR epd threshold to 87 percent of maximum size and displays the results:

Switch(config)# interface atm 0/1
Switch(config-if)# atm output-threshold cbr epd 87
Switch# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
        epd threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
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
<output deleted>

Configuring Modem Port Input Maximum Queue Size

The input queue for local modems (subscriber ports) can be further subdivided on a per-port basis. This ensures that no one modem can consume more than its allotted share of input buffer space. This buffer space can be uniquely set for priority. It can also be uniquely set for each of the up to 256 possible modem ports. However, it can not be uniquely set for each VC. All VCs at a particular priority per port are counted against the configured value.

Note Although it is not required, it is recommended that all modem ports be configured to the same value at the same priority.

The force argument indicates that the change should be made even if it results in the loss of data on the interface queue. (The queue must be momentarily disabled for the threshold to be changed.) This command without the force argument changes only the threshold if the interface is down. An error message appears and the command does not take effect if the interface is up and the force argument is not present.

To display both the configured and installed values of the maximum queue size, use the show atm interface resource command.

To configure the modem port input maximum queue size:

Step
Command
Task

1.

interface atm slot/port

Select the modem interface to be configured.

2.

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

Set traffic type and the size of the modem port input queue.


Example

This example shows you how to set the modem port input maximum for CBR traffic to 5000 for modem port 4/0 and displays the results:

Switch(config)# interface atm 4/0
Switch(config-if)# atm input-queue force cbr max-size 5000
Switch# show atm interface resource a4/0 !(Modem Port )
Resource Management configuration:
Output queues:
Max sizes(derived): 256 cbr, 256 vbr-rt, 2048 vbr-nrt, 2048 ubr
EPD threshold: 128 cbr, 128 vbr-rt, 1024 vbr-nrt, 1024 ubr
Drop threshold: 128 cbr, 128 vbr-rt, 1024 vbr-nrt, 1024 ubr
Input queues:
        Max sizes(explicit cfg): 5000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 1024 cbr, 1024 vbr-rt, 8192 vbr-nrt, 8192 ubr
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
<output deleted>

Configuring QoS Default Values

To configure QoS default values, follow these steps:

Step
Command
Task

1.

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

Selects the QoS default CBR or VBR-RT mctd.

2.

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

Selects the QoS default CBR or VBR-RT PpCDV.

3.

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

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


Note The DSLAM does not distinguish between cells that have CLP = 0 and cells that have CLP = 1+0 with respect to the policing of incoming cells. Therefore there is effectively no difference in the configuration when CLP0 or CLP1+0 is chosen. This also applies to any values that display as the result of a show command.

Note No traffic shaping or policing is available in the downstream direction.

The DSLAM uses these values to check the QoS parameter on the flow of a connection request, and when accumulating QoS metrics for PNNI.

Example

This example shows you how to set the QoS default to CBR, clp1plus0, with a loss-ratio exponent of 12 and displays the results:

DSLAM# atm qos default cbr max-cell-loss-ratio clp1plus0 12
DSLAM# 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

Configuring clp-drop Setting

To enable or disable the CLP-drop flag for a service category, use this command:

Command
Task

atm clp-drop [force] {vbr-nrt | ubr} {off | on}

Enables or disables the CLP drop flag for the specified service category.


When the switch enables the CLP-drop flag for a service category, it drops the cells when the service-category queue reaches 50 percent of the discard threshold limit. The default is off.

Example

This example enables the CLP-drop flag for VBR-NRT and displays the results:

DSLAM# atm clp-drop force vbr-nrt on

DSLAM# show atm resource
Resource configuration:
Over-subscription-factor 8 Sustained-cell-rate-margin-factor 1%
Abr-mode: relative-rate

Subtended Port Input queue Configuration:
EPD threshold: 512 cbr, 512 vbr-rt, 4096 vbr-nrt, 4096 ubr
Drop threshold: 512 cbr, 512 vbr-rt, 4096 vbr-nrt, 4096 ubr
Max queue sizes (Derived): 1024 cbr, 1024 vbr-rt, 8192 vbr-nrt, 8192 ubr

CLP Drop configuration:
              cbr : off, vbr-rt : off, vbr-nrt : on, ubr : off

Configuring the Default QoS Objective Table

Because UNI 3 signaling does not provide information elements (IEs) to signal QoS values, resource management provides a table of default objective values for QoS for guaranteed service categories. These values are used as the criteria for connection setup requirements. The values are either

•Metric values (accumulated over multiple hops of a call)

•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 You can configure objective values for QoS for guaranteed service categories for UNI 4.0 signaling.

Table 9-1 lists the default values of the QoS objective table.

Table 9-1 Default QoS Objective Table Row Contents

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

UBR

Undefined

Undefined

Undefined

Undefined


Note The DSLAM does not distinguish between CLP0, CLP01, and CLP0+1 with respect to the policing of incoming cells. Therefore there is effectively no difference in the configuration when CLP0, CLP01, or CLP0+1 is chosen. This also applies to any values that display as the result of a show command.

Note No traffic shaping or policing is available in the downstream direction.

You can assign each objective either a defined or an undefined value. If it is undefined, DSLAM does not consider the objective when it performs the connection setup.

Configure this table with the same values for an entire network.

To configure the default QoS objective table, perform these tasks in global configuration mode:

Step
Command
Task

1.

atm qos default {cbr | vbr-rt | ubr} 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 | ubr} 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 | ubr} 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.


Note The DSLAM does not distinguish between cells that have CLP=0 and cells that have CLP=1 with respect to the policing of incoming cells. Therefore there is effectively no difference in the configuration when CLP0 or CLP1plus0 is chosen. This also applies to any values that display as the result of a show command.

Note No traffic shaping or policing is available in the downstream direction.

Example

This 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 and displays the results:

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

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+1 cells: 10**(-12) cbr, any vbr-rt, any vbr-nrt

Configuring the Connection Traffic Table

You must create a row in the connection traffic table (CTT) 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). Several VCL/VPLs can refer to the same row in the traffic table.

CTT rows specifying these new parameters can be configured, with this effect:

•Non-zero MCR is not supported. The DSLAM rejects requests for connections specifying non-zero MCR.

•On VBR connections, the DSLAM uses only SCR and MBS for UPC.

The NI-2 module supports four traffic priorities. These four priorities are mapped to four classes of service as follows:

•Constant bit rate (CBR)—video and voice

•Variable bit rate with a remote terminal (VBR-rt)—voice

•Variable bit rate, no remote terminal (VBR-nrt)—voice

•Undefined/available bit rate (UBR/ABR)

Configuring PVC Connection Traffic Rows

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

Configuring SVC Connection Traffic Rows

To configure the connection traffic table in a switched virtual circuit (SVC) setup, you create a row identifier that Simple Network Management Protocol (SNMP) or the user interface uses to read or display SVC traffic parameters. The DSLAM stores a CTT row index in the connection-leg data structure for each flow of the connection.

Note You cannot delete rows while they are in use by a connection.

To make CTT management software more efficient, DSLAM splits the CTT row-index space into

•Rows allocated as a result of signaling

•Rows allocated from the command-line interface (CLI) and SNMP

Table 9-2 describes the row-index range for both row types.

Table 9-2 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

Signaling VxL creation

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


Table 9-3 describes the CTT rows predefined by the software.

Table 9-3 Default 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

UBR

424 kbps

—

None

UBR tunnel WK VCs


The atm connection-traffic-table-row command contains four variables—one for each service category (CBR, VBR-RT, VBR-NRT, and UBR). To create or delete a CTT row, perform these tasks in global configuration mode:

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] ubr pcr pcr_value [mcr mcr_value] [cdvt cdvt_value]

Configure an ATM CTT UBR row.


Note The DSLAM does not distinguish between cells that have SCR = 10 and cells that have SCR = 0 with respect to the policing of incoming cells. Therefore there is effectively no difference in the configuration when SCR10 or SCR0 is chosen. This also applies to any values that display as the result of a show command.

Note No traffic shaping or policing is available in the downstream direction.

These commands affect all connections, including those already established.

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

This example shows how to configure an ATM CTT row with cbr traffic and a peak cell rate of 30,000 kbps, and displays the results:

Switch# (config)# atm connection-traffic-table-row cbr pcr 30000
Allocated index = 64000
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            ubr 424 none none
64000 cbr            30000  none
2147483645* ubr 0 none none
2147483646* ubr 1 none none
2147483647* ubr 7113539 none none

Configuring the Sustained Cell Rate Margin Factor

The sustained cell rate margin factor determines the aggressiveness of weighting sustained 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 the DSLAM, use this global configuration command:

Command
Task

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

Configure the sustained cell rate margin factor as a percentage.


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

Example

This example shows how to configure the SCR margin factor as 64 percent of maximum and displays the results:

DSLAM(config)# atm sustained-cell-rate-margin-factor 64

DSLAM(config)# show atm resource
Resource configuration:
     Over-subscription-factor 8 Sustained-cell-rate-margin-factor 64%

Subtended Port Input queue Configuration:
Max sizes: 1024 cbr, 1024 vbr-rt, 8192 vbr-nrt, 8192 ubr
Discard threshold: 50% cbr, 50% vbr-rt, 50% vbr-nrt, 50% ubr

CLP Drop configuration:
cbr : off, vbr-rt : off, vbr-nrt : off, ubr : off

Configuring the Number of Best-Effort UBR Connections

To set the number of best-effort ubr connections:

Command
Task

atm cac best-effort-limit conn-value

Sets the number of best-effort UBR connections to conn-value.


Example

This example shows you how to set the number of best-effort UBR connections to 2000 and displays the results:

DSLAM(config)# atm cac best-effort-limit 2000

DSLAM(config)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% ubr
Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,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 ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

Configuring the Maximum Value of Individual Traffic Parameters

The atm cac commands allow you to tune parameters used in the Connection Admission Control (CAC) functions. Table 9-4 describes the three types of parameters, which are configured per interface. Changes made to these parameters only affect subsequent connection setups.

Table 9-4 Connection Admission Configuration

Parameter
Description

controlled link sharing

Specifies the minimum and maximum bandwidth that can be allocated to guaranteed service (CBR or VBR) connections. You can specify maxima for CBR, VBR, and the aggregate of CBR and VBR. You can specify minima for CBR and VBR. These parameters, for a direction, are interrelated as follows (assuming these parameters are defined):

•min(CBR) + min(VBR) <= 95%

•min(CBR) <= max(CBR) <= 95%

•min(VBR) <= max(VBR) <= 95%

•min(CBR) <= max(AGG) <= 95%

•min(VBR) <= max(AGG) <= 95%

•max(CBR) <= max(AGG) <= 95%

•max(VBR) <= max(AGG) <= 95%

traffic parameter limits

Specifies maximum traffic parameters (such as peak-cell-rate) that are allowed on VC setup. You can specify these independently by service category and traffic direction.

best-effort connection limits

A limit on the total number of ABR and UBR connections on the interface.


To set the maximum value of individual traffic parameters for an interface, apply these commands:

Command
Task

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

Sets the maximum peak cell rate.

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

Sets the maximum sustained cell rate.

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

Sets the maximum tolerance.

atm cac max-cvdt {cbr | vbr | ubr} {receive | transmit} rate

Sets the maximum cvdt value.

atm cac max-mbs {cbr | vbr | ubr} {receive | transmit} rate

Sets the maximum mbs value.

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

Sets the maximum and minimum cell rate values.


Example

This example sets a peak-cell-rate traffic parameter limit of 3001 kbps for ubr connections in the receive direction on the interface and displays the results:

Switch(config-if)# atm cac max-peak-cell-rate abr receive 3001

Switch(config-if)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% ubr
Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,ubr
Link Distance: 150 kilometers
Controlled Link sharing:
Max aggregate guaranteed services: 87% Rx, none TX
Max bandwidth: none cbr RX, 50 cbr TX, none vbr RX, none vbr TX,
none ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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, 3001 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

Reserving Guaranteed Bandwidth for a Service Category

To fine-tune connection admission control functions on a per-interface and direction basis, use these commands:

Command
Task

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

Reserves maximum guaranteed service bandwidth in the receive or transmit direction on a flow/interface basis by the amount percent.

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

Reserves maximum bandwidth in the receive or transmit direction for CBR, VBR, and UBR connections on a flow/interface basis by the amount percent.

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

Reserves minimum bandwidth in the receive or transmit direction for CBR, VBR, and UBR connections on a flow/interface basis by the amount percent.


Display the Resource Management Configuration

To display the resource management configuration, use this EXEC command:

Command
Task

show atm interface resource 0/1

Display the resource management configuration.


Example

This example reserves 50 percent as the minimum bandwidth for CBR in the transmit direction and displays the results:

DSLAM(config)# atm cac link-sharing min-bandwidth cbr transmit 50

DSLAM(config)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% ubr
Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,ubr
Link Distance: 150 kilometers
Controlled Link sharing:
Max aggregate guaranteed services: 87% Rx, none TX
        Max bandwidth: none cbr RX, 50 cbr TX, none vbr RX, none vbr TX,
none ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

Configuring the Allowed Service Categories

To set the service categories CAC allows on an interface, use these commands:

Step
Command
Task

1.

DSLAM(config)# interface atm 0/1

Select interface 0/1.

2.

DSLAM(config)# atm cac service-category {cbr | vbr | ...} {deny | permit}

Sets a service category CAC allows or denies on an interface.


Example

This example prohibits the service category cbr on the interface 0/1 and displays the results:

DSLAM(config)# interface atm 0/1
DSLAM(config)# atm cac service-category cbr deny
DSLAM# show running-config
Building configuration...
Current configuration:
!
! No configuration change since last restart
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service internal
!
hostname ni2-3
!
enable password lab
dmt-profile default
network-clock-select 1 ATM0/1
network-clock-select 2 system
ip subnet-zero
ip host-routing
ip domain-name cisco.com
ip name-server 171.69.204.11
!
atm address 47.0091.8100.0000.007b.f444.7801.007b.f444.7801.00
atm router pnni
no aesa embedded-number left-justified
node 1 level 56 lowest
redistribute atm-static
!
clock timezone EST -5
clock summer-time EDT recurring
!
process-max-time 200
!
interface ATM0/0
ip address 70.0.0.2 255.0.0.0
no ip directed-broadcast
map-group test
 atm cac service-category abr deny
atm maxvp-number 0
!
interface Ethernet0/0
<output deleted>

Configuring the Propagation Delay (Link Distance)

You can increase the propagation delay by specifying the link distance for the physical link of the next ATM host in the outbound direction.

To set the link distance, use these commands:

Step
Command
Task

1.

DSLAM(config)# interface atm 0/1

Select interface 0/1.

2.

DSLAM(config)# atm link-distance distance

Sets the link distance to the value distance.


Example

This example shows you how to set the link distance to 64 km and displays the results:

DSLAM(config)# atm link-distance 64
DSLAM# show atm interface resource atm 0/1
Resource Management configuration:
Service Classes:
Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, c4 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: 64 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX,
Tolerance RX: none cbr, none vbr, none ubr
Tolerance TX: none cbr, none vbr, none ubr
Resource Management state:
Available bit rates (in Kbps):
147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
147743 ubr RX, 147743 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 0 pvcs, 0 svcs

Configuring a CDVT and MBS Default

When the DSLAM does not specify a CDVT or MBS for PVCs through a connection traffic row, the software applies a per-interface, per-service-category default for UPC on the connection.

To set a per-interface, per-service-category CDVT or MBS default for UPC on a connection, use these commands:

Step
Command
Task

1.

DSLAM(config)# atm cdvt-default {cbr | vbr-rt | vbr-nrt | ubr} num

Sets the CDVT default for cbr, vbr-rt, vbr-nrt, or ubr to num.

2.

DSLAM(config)# atm mbs-default {vbr-rt | vbr-nrt} num

Sets the MBS default for vbr-rt or vbr-nrt to num.


Example

This example shows you how to set the MBS vbr-rt UPC default to 20 on interface 0/1 and displays the result:

DSLAM(config)# interface atm 0/1
DSLAM(config)# atm mbs-default vbr-rt 20

DSLAM(config)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none aubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
        Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,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 ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
                     MBS: none vbr RX, none vbr TX, 20 vbr-rt
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

Configuring CAC Functions for Specific Interfaces and Directions

Resource management lets you fine-tune the connection admission control functions on a per-interface and direction (receive and transmit) basis. You specify the reservations with these 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 connection admission control parameter to bandwidth relationships are shown in Table 9-5.

Table 9-5 Connection Admission Control Parameter to Bandwidth Relationships

Service Category
Value
Service Category
Bandwidth (Percent)

Minimum CBR

+

Minimum VBR

<= 95

Minimum CBR

<=

Maximum CBR

<= 95

Minimum VBR

<=

Maximum VBR

<= 95

Minimum CBR

<=

Maximum Aggregate

<= 95

Minimum VBR

<=

Maximum Aggregate

<= 95

Maximum CBR

<=

Maximum Aggregate

<= 95

Maximum VBR

<=

Maximum Aggregate

<= 95


To configure controlled link sharing, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

DSLAM(config)# interface atm slot/port [.vpt#]

Select the interface to be configured.

2.

DSLAM(config)# atm cac link-sharing max-guaranteed-service-bandwidth {receive | transmit} percent

Configure controlled link sharing for the maximum guaranteed service bandwidth.

3.

DSLAM(config)# atm cac link-sharing max-bandwidth {cbr | ubr | vbr} {receive | transmit} percent

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

4.

DSLAM(config)# atm cac link-sharing min-bandwidth {cbr | vbr | 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 Command Reference for Cisco DSLAMs with NI-2.

Examples

This example shows how to configure the controlled link sharing, maximum guaranteed service bandwidth, and receive configuration on interface 0/1 to 87 percent and displays the result:

DSLAM(config)# interface atm 0/1
DSLAM(config)# atm cac link-sharing max-guaranteed-service-bandwidth receive 87
DSLAM(config)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
        Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,ubr
Link Distance: 0 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 ubr RX, none ubr TX
        Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
none ubr RX, none ubr TX
Best effort connection limit: disabled 0 max connections

<output deleted>

This example displays the controlled link sharing configuration:

DSLAM(config)# show atm interface resource atm 0/0
Resource Management configuration:
Service Classes:
Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX,
Tolerance RX: none cbr, none vbr, none ubr
Tolerance TX: none cbr, none vbr, none ubr
Resource Management state:
Available bit rates (in Kbps):
147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
147743 ubr RX, 147743 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 0 pvcs, 0 svcs

Configuring the Physical and Logical Interface Parameters

This section describes interface configuration resource management tasks for both physical and logical interface types.

Configuring 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. DSLAM uses the propagation delay to determine 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 these tasks, beginning in global configuration mode:

Step
Command
Task

1.

DSLAM(config)# interface atm slot/port[.vpt#]

Select the subinterface to be configured.

2.

DSLAM(config)# 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.

Examples

This example shows how to configure the interface link distance configuration to
150 kilometers and displays the result:

DSLAM(config)# atm link-distance 150

DSLAM(config)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% ubr
Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt,87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,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 ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr,none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX:none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

This example shows you how to set configuration of the interface link distance:

DSLAM(config)# show atm interface resource atm 0/0
Resource Management configuration:
Service Classes:
Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX,
Tolerance RX: none cbr, none vbr, none ubr
Tolerance TX: none cbr, none vbr, none ubr
Resource Management state:
Available bit rates (in Kbps):
147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
147743 ubr RX, 147743 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 0 pvcs, 0 svcs

Configuring the Limits of Best-Effort Connections

You can configure each interface to allow a specific number of best-effort UBR connections.

To configure the number of best-effort connections, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

DSLAM(config)# interface atm slot/port[.vpt#]

Select the interface to be configured.

2.

DSLAM(config-if)# 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

This example configures the connection best-effort limit configuration for interface 0/1 to 2000 and displays the result:

DSLAM(config)# interface atm 0/1
DSLAM(config-if)# atm cac best-effort-limit 2000

DSLAM(config)# show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
    Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,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 ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

This example shows the interface best-effort configuration disabled:

Switch# show atm interface resource atm 0/0
Resource Management configuration:
Service Classes:
Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX,
Tolerance RX: none cbr, none vbr, none ubr
Tolerance TX: none cbr, none vbr, none ubr
Resource Management state:
Available bit rates (in Kbps):
147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
147743 ubr RX, 147743 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 0 pvcs, 0 svcs

Configuring the Interface Maximum of Individual Traffic Parameters

When a VCC is set up, you can specify per-flow (receive and transmit traffic) parameters. You can configure traffic parameter limits independently (by service category), as well as traffic direction for

•Maximum peak cell rate (PCR)

•Maximum sustained cell rate (SCR)

•Maximum cell delay variation tolerance (CDVT)

•Maximum burst size (MBS)

•Maximum or minimum cell rate (MCR)

To configure the traffic parameters, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port[.vpt#]

Select the interface to be configured.

2.

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

Configure the connection maximum PCR.

3.

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

Configure the connection maximum SCR.

4.

atm cac max-cdvt {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 {ubr} {receive | transmit} rate

Configure the connection MCR per service category flow.


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

Examples

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

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

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

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

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

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

This example shows the interface output pacing configuration for interface 0/1:

Switch> show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): 30000 cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 30208 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 ubr
Efci threshold: 50% cbr, 25% vbr-rt, 25% vbr-nrt, 25% ubr
Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
      Pacing: enabled 10000 Kbps rate configured, 10000 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt, 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 ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
               Sustained-cell-rate: 60000 vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
               CDVT RX: 75000 cbr, none vbr, none ubr
                CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 ubr
Available bit rates (in Kbps):
135302 cbr RX, 9499 cbr TX, 135302 vbr RX, 9499 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs

This example shows the interface output pacing configuration for the interface 0/0:

Switch# show atm interface resource atm 0/0
Resource Management configuration:
Service Classes:
Service Category map: c1 cbr, c2 vbr-rt, c3 vbr-nrt, 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX,
Tolerance RX: none cbr, none vbr, none ubr
Tolerance TX: none cbr, none vbr, none ubr
Resource Management state:
Available bit rates (in Kbps):
147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
147743 ubr RX, 147743 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 0 pvcs, 0 svcs

Configuring 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. To do so, 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 using 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 signaled connections, you cannot use CDVT or MBS and the defaults specified on the interface apply.

To configure the default CDVT and MBS parameters, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Specify an ATM interface and enter interface configuration mode.

2.

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

Configure the ATM CDVT default.

3.

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

Configure the ATM MBS default.


Example

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

Switch(config)# interface atm 0/1
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 these EXEC commands:

Command
Task

show atm vc

Display the ATM VC CDVT configuration.

show atm vp

Display the ATM VP CDVT configuration.


Examples

This example shows the ATM CDVT and MBS configuration of an ATM VC for interface 0/1, with VPI = 0:

Switch# show atm vc interface atm 0/1 0 100

Interface: ATM0/1, Type: suni-dual
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/0, Type: suni-dual
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

This example shows the ATM CDVT and MBS configuration of an ATM VP for interface 0/1, with VPI = 4:

Switch# show atm vp interface atm 0/1 4

Interface: ATM0/1, Type: suni-dual
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, Type: suni-dual
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

This example shows the ATM CDVT and MBS configuration of an ATM VP for interface 0/1, with VPI = 4:

Switch# show atm vp interface atm0/1 4
Interface: ATM0/1, Type: suni-dual
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/2, Type: suni-dual
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

Configuring Interface Service Category Support

With interface service category support, you can configure the service categories that CAC allows on an interface. You can configure interface service category support only on physical interfaces and shaped VP tunnel logical interfaces. The underlying VP for shaped VP tunnel logical interfaces must use the CBR service category. By default, only CBR user VCs can cross the interface. Using the service category support configuration commands, you can substitute another service category for CBR on the interface. This configuration ensures that your switch shapes traffic according to the aggregate VP traffic contract before it enters a service provider network.

Note No traffic shaping or policing is available in the downstream direction.

Table 9-6 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 9-6 Service Category Support for Shaped VP Tunnels

Shaped VP Tunnel Service Category
VC Service Category
Suggested Transit VP Service Category

CBR

CBR

CBR

CBR

VBR

CBR or VBR

CBR

UBR

Any service category


These restrictions apply to interface service category support:

•This configuration is allowed on physical interfaces and shaped VP tunnel logical interfaces.

•On shaped VP tunnel logical interfaces, only one service category is permitted at a time. To replace CBR with another service category on these interfaces, you must first deny the CBR service category, then permit the chosen service category. To deny a service category, you must delete all user VCs of that service category on the interface.

•For UBR, only zero MCR is supported on VCs on a shaped VP tunnel.

To configure a service category on an interface, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/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.


Note abr appears in this command syntax, but the current release does not support it.

Example

This example shows how to deny the UBR service category on ATM interface 0/1 and displays the result:

Switch(config)# interface atm 0/1
Switch(config-if)# atm cac service-category ubr deny

Switch> show atm interface resource atm 0/1
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): none cbr, none vbr-rt, none vbr-nrt, none ubr
Max sizes(installed): 256 cbr, 512 vbr-rt, 4096 vbr-nrt, 11776 ubr
        Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% ubr
Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed
     Service Categories supported: cbr,vbr-rt,vbr-nrt
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 ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr 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 ubr
Peak-cell-rate TX: none cbr, none vbr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none ubr
Minimum-cell-rate TX: none ubr
CDVT RX: none cbr, none vbr, none ubr
CDVT TX: none cbr, none vbr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 ubr
Available bit rates (in Kbps):
1466 cbr RX, 1466 cbr TX, 1466 vbr RX, 1466 vbr TX,
0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 ubr RX, 0 ubr TX
Best effort connections: 0 pvcs, 0 svcs

hometocprevnextglossaryfeedbacksearchhelp

Posted: Fri Dec 3 13:57:39 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.