|
Table Of Contents
ATM Policing by Service Category for SVC/SoftPVC
Information About ATM Policing by Service Category for SVC/SoftPVC
How to Configure ATM Policing by Service Category for SVC/SoftPVC
Configuring ATM Policing by Service Category for SVC/SoftPVC
Verifying ATM Policing by Service Category for SVC/SoftPVC
Monitoring and Maintaining ATM Policing by Service Category for SVC/SoftPVC
Monitoring and Maintaining ATM Policing by Service Category for SVC/SoftPVC: Example
Configuration Examples for ATM Policing by Service Category for SVC/SoftPVC
Non-UBR Traffic Policing: Example
Feature Information for ATM Policing by Service Category for SVC/SoftPVC
ATM Policing by Service Category for SVC/SoftPVC
First Published: September 26, 2001Last Updated: January 20, 2009The ATM Policing by Service Category for SVC/SoftPVC feature enables you to specify which traffic to police, based on service category, on switched virtual circuits (SVCs) or terminating virtual circuits (VCs) on the destination end of a soft VC.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for ATM Policing by Service Category for SVC/SoftPVC" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Information About ATM Policing by Service Category for SVC/SoftPVC
•How to Configure ATM Policing by Service Category for SVC/SoftPVC
•Configuration Examples for ATM Policing by Service Category for SVC/SoftPVC
•Additional References, page 9
•Additional References, page 9
•Feature Information for ATM Policing by Service Category for SVC/SoftPVC
Information About ATM Policing by Service Category for SVC/SoftPVC
When configured, an ATM switch at the network side of a user-to-network (UNI) interface polices the flow of cells in the forward (into the network) direction of a virtual connection. These traffic policing mechanisms are known as usage parameter control (UPC). With UPC, the switch determines whether received cells comply with the negotiated traffic management values and takes one of the following actions on violating cells:
•Pass the cell without changing the cell loss priority (CLP) bit in the cell header.
•Tag the cell with a CLP bit value of 1.
•Drop (discard) the cell.
This feature enables you to select which traffic is affected by UPC and how it is affected. For example, you can configure your switch to pass all UBR traffic, but tag all other traffic types.
For more information about UPC, see the "Traffic and Resource Management" chapter in the Guide to ATM Technology.
How to Configure ATM Policing by Service Category for SVC/SoftPVC
The tasks in the following sections describe configuration for the ATM Policing by Service Category for SVC/SoftPVC feature. Each task in the list is identified as either required or optional:
•Configuring ATM Policing by Service Category for SVC/SoftPVC (Required)
•Verifying ATM Policing by Service Category for SVC/SoftPVC (Optional)
Configuring ATM Policing by Service Category for SVC/SoftPVC
The task in this section configures the ATM Policing by Service Category for SVC/SoftPVC feature, using the following commands beginning in global configuration mode.
SUMMARY STEPS
1. enable
2. configure terminal
3. Router(config)# interface atm slot/subslot/port
4. Router(config-if)# atm svc-upc-intent [{abr | cbr | vbr-rt | vbr-nrt | ubr}]{tag | pass | drop}
DETAILED STEPS
Verifying ATM Policing by Service Category for SVC/SoftPVC
Step 1 Enter the show atm vc or show atm vp EXEC command to display the UPC mode for a particular virtual circuit or VP.
Switch# show atm vc int atm 0/0/1 2 120Interface:ATM0/0/1, Type:oc3suniVPI = 2 VCI = 120Status:DOWNTime-since-last-status-change:1w1dConnection-type:PVCCast-type:point-to-multipoint-leafPacket-discard-option:disabledUsage-Parameter-Control (UPC):passWrr weight:2Number of OAM-configured connections:0OAM-configuration:disabledOAM-states: Not-applicableCross-connect-interface:ATM0/0/1, Type:oc3suni...Step 2 Enter the show atm interface EXEC command. If the UPC mode is not the same for all service categories, the "Svc Upc Intent" field displays "by sc."
Switch# show atm interface atm 8/0/1Interface: ATM8/0/1 Port-type: oc3suniIF Status: UP Admin Status: upAuto-config: enabled AutoCfgState: completedIF-Side: Network IF-type: NNIUni-type: not applicable Uni-version: not applicableMax-VPI-bits: 8 Max-VCI-bits: 14Max-VP: 255 Max-VC: 16383ConfMaxSvpcVpi:255 CurrMaxSvpcVpi:255ConfMaxSvccVpi:255 CurrMaxSvccVpi:255ConfMinSvccVci:35 CurrMinSvccVci:35Svc Upc Intent:by sc Signalling: EnabledATM Address for Soft VC:47.0091.8100.0000.0002.b9ae.9301.4000.0c84.0010.00Configured virtual links:PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns3 4 0 0 1 0 0 8 7Logical ports(VP-tunnels): 0Input cells: 3036674 Output cells: 30368165 minute input rate: 0 bits/sec, 0 cells/sec5 minute output rate: 0 bits/sec, 0 cells/secInput AAL5 pkts:1982638, Output AAL5 pkts:1982687, AAL5 crc errors:0
Troubleshooting Tips
If a VC is not configured with the appropriate UPC mode, make sure that the VC was set up after the atm svc-upc-intent command was configured. Changes to the UPC mode take effect after the VC is torn down and set up again.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface atm slot/subslot/port
4. atm svc-upc-intent [{abr | cbr | vbr-rt | vbr-nrt | ubr}] {tag | pass | drop}
5. Repeat Step 4 for each service category and UPC mode combination.
DETAILED STEPS
Monitoring and Maintaining ATM Policing by Service Category for SVC/SoftPVC
The task in this section enable you to monitor and maintain the ATM Policing by Service Category for SVC/SoftPVC feature.
SUMMARY STEPS
1. enable
2. configure terminal
3. show atm interface
4. show controllers atm slot/subslot/port
5. show atm vc [interface atm slot/subslot/port]
DETAILED STEPS
Monitoring and Maintaining ATM Policing by Service Category for SVC/SoftPVC: Example
Switch# show atm vc interface atm 3/0/1.51 51 16Interface: ATM3/0/1.51, Type: oc3suniVPI = 51 VCI = 16Status: DOWNTime-since-last-status-change: 2w0dConnection-type: PVCCast-type: point-to-pointPacket-discard-option: enabledUsage-Parameter-Control (UPC): passWrr weight: 32Number of OAM-configured connections: 0OAM-configuration: disabledOAM-states: Not-applicableCross-connect-interface: ATM2/0/0, Type: ATM Swi/ProcCross-connect-VPI = 0Cross-connect-VCI = 73Cross-connect-UPC: passCross-connect OAM-configuration: disabledCross-connect OAM-state: Not-applicableEncapsulation: AAL5ILMIThreshold Group: 6, Cells queued: 0Rx cells: 0, Tx cells: 0Tx Clp0:0, Tx Clp1: 0Rx Clp0:0, Rx Clp1: 0Rx Upc Violations:0, Rx cell drops:0Rx pkts:0, Rx pkt drops:0Rx connection-traffic-table-index: 6Rx service-category: UBR (Unspecified Bit Rate)Rx pcr-clp01: 424Rx scr-clp01: noneRx mcr-clp01: noneRx cdvt: 1024 (from default for interface)Rx mbs: noneTx connection-traffic-table-index: 6Tx service-category: UBR (Unspecified Bit Rate)Tx pcr-clp01: 424Tx scr-clp01: noneTx mcr-clp01: noneTx cdvt: noneTx mbs: noneNo AAL5 connection registeredConfiguration Examples for ATM Policing by Service Category for SVC/SoftPVC
This section provides the following configuration Non-UBR Traffic Policing: Example.
Non-UBR Traffic Policing: Example
In the following example, the UBR traffic on ATM 3/0/0 is passed while all other traffic is policed:
Router(config)# interface atm 3/0/0Router(config-if)# atm svc-upc-intent ubr passRouter(config-if)# atm svc-upc-intent cbr tagRouter(config-if)# atm svc-upc-intent vbr-rt tagRouter(config-if)# atm svc-upc-intent vbr-nrt tagRouter(config-if)# atm svc-upc-intent abr dropAdditional References
The following sections provide references related to the ATM Policing by Service Category for SVC/SoftPVC feature.
Related Documents
Standards
MIBs
MIB MIBs Link•None.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Asynchronous Transfer Mode Command Reference at http://www.cisco.com/en/US/docs/ios/atm/command/reference/atm_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
•atm svc-upc-intent
Feature Information for ATM Policing by Service Category for SVC/SoftPVC
Table 1 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Releases 12.2(1), 12.0(3)S, 12.2(33)SRA, 12.2(33)SXH, or later releases appear in the table.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Glossary
ABR—available bit rate. QoS class defined by the ATM Forum for ATM networks. ABR is used for connections that do not require timing relationships between source and destination. ABR provides no guarantees in terms of cell loss or delay, providing only best-effort service. Traffic sources adjust their transmission rate in response to information they receive describing the status of the network and its capability to successfully deliver data. Compare with CBR, UBR, and VBR.
CBR—constant bit rate. QoS class defined by the ATM Forum for ATM networks. CBR is used for connections that depend on precise clocking to ensure undistorted delivery. Compare with ABR, UBR, and VBR.
CLP—cell loss priority. Field in the ATM cell header that determines the probability of a cell being dropped if the network becomes congested. Cells with CLP = 0 are insured traffic, which is unlikely to be dropped. Cells with CLP = 1 are best-effort traffic, which might be dropped in congested conditions to free up resources to handle insured traffic.
PVC—permanent virtual circuit (or connection). Virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and tear down in situations where certain virtual circuits must exist all the time. In ATM terminology, called a permanent virtual connection. Compare with SVC. See also virtual circuit.
soft PVC—A PVC-SVC hybrid in which only the two terminating virtual connection links (VCLs) at either end are permanent and the rest of the VCLs are switched (SVC). Like the PVC, a soft PVC is permanent and the called party cannot drop the connection. Like the SVC, a soft PVC is automatically rerouted if a switch or link in the path fails.
SVC—switched virtual circuit. Virtual circuit that is dynamically established on demand and is torn down when transmission is complete. SVCs are used in situations where data transmission is sporadic. See also virtual circuit. Called a switched virtual connection in ATM terminology. Compare with PVC.
tagged traffic—ATM cells that have their CLP bit set to 1. If the network is congested, tagged traffic can be dropped to ensure the delivery of higher-priority traffic. Sometimes called DE traffic. See also CLP.
traffic policing—Process used to measure the actual traffic flow across a given connection and compare it to the total admissible traffic flow for that connection. Traffic outside of the agreed upon flow can be tagged (where the CLP bit is set to 1) and can be discarded en route if congestion develops. Traffic policing is used in ATM, Frame Relay, and other types of networks. Also known as admission control, permit processing, rate enforcement, and UPC. See also tagged traffic.
UBR—unspecified bit rate. QoS class defined by the ATM Forum for ATM networks. UBR allows any amount of data up to a specified maximum to be sent across the network but there are no guarantees in terms of cell loss rate and delay. Compare with ABR, CBR, and VBR.
UPC—usage parameter control. See traffic policing.
VBR—variable bit rate. QoS class defined by the ATM Forum for ATM networks. VBR is subdivided into a real time (RT) class and non-real time (NRT) class. VBR (RT) is used for connections in which there is a fixed timing relationship between samples. VBR (NRT) is used for connections in which there is no fixed timing relationship between samples but that still need a guaranteed QoS. Compare with ABR, CBR, and UBR.
virtual circuit—Logical circuit created to ensure reliable communication between two network devices. A virtual circuit is defined by a VPI/VCI pair, and can be either permanent (PVC) or switched (SVC). Virtual circuits are used in Frame Relay and X.25. In ATM, a virtual circuit is called a virtual channel. Sometimes abbreviated VC.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2001-2002, 2009 Cisco Systems, Inc. All rights reserved.