-
This documentation has been moved
-
Quality of Service Overview
- Part 1: Classification
- Part 2: Congestion Management
- Part 3: Congestion Avoidance
-
Part 4: Policing and Shaping
-
Policing and Shaping Overview
-
Traffic Policing
-
Configuring Traffic Policing
-
Traffic Policing
-
Two-Rate Policer
-
Policer Enhancement---Multiple Actions
-
Percentage-Based Policing and Shaping
-
Modular QoS CLI (MQC) Three-Level Hierarchical Policer
-
ATM Policing by Service Category for SVC/SoftPVC
-
Modular QoS CLI (MQC) Unconditional Packet Discard
-
Control Plane Policing
-
Class-Based Policing
-
QoS: Percentage-Based Policing
-
- Packet Flow Regulation
-
- Part 5: Signalling
- Part 6: Link Efficiency Mechanisms
- Part 7: Quality of Service Solutions
- Part 8: Modular Quality of Service Command-Line Interface
- Part 9: Security Device Manager
- Part 10: AutoQoS
-
Feedback
Table Of Contents
IP to ATM Class of Service Mapping for SVC Bundles
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring Bundle-Level Parameters
Configuring an SVC Bundle Member Directly
Monitoring IP to ATM Class of Service Mapping for SVC Bundles
Example: IP to ATM Class of Service Mapping with Bundle Parameters Configured in Bundle Mode
IP to ATM Class of Service Mapping for SVC Bundles
Feature History
This feature module describes the IP to ATM Class of Service Mapping for SVC Bundles feature for Cisco IOS Release 12.2(4)T and includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
The IP to ATM Class of Service Mapping for SVC Bundles feature supports multiple switched virtual circuits (SVCs) to the same NSAP destination for different types of service (ToS). This feature is an extension of the feature described in the "Configuring IP to ATM Class of Service" module. The original feature was limited to permanent virtual circuits (PVCs) only. This feature is an extension because it applies to SVCs.
The PVC bundle feature requires that the user configure PVCs for different IP ToS. The PVCs have to be set up throughout the ATM network between endpoints. The IP to ATM Class of Service Mapping for SVC Bundles feature needs configuration only at the endpoints. The user does not configure SVCs; the software sets up SVCs in a bundle between endpoints. When the router receives the first IP packet for the destination that is configured in the SVC bundle, that event triggers the creation of the SVC.
A default SVC is used for non-IP traffic, IP traffic with no precedence, and IP traffic with the precedence bit set but for which no SVC exists. SVC setup for the specific IP precedence traffic is triggered when the first IP packet with that precedence bit set is received.
Benefits
Multiple SVCs with Different QoS Parameters
Users can have multiple SVCs, each with different QoS parameters, between SVC endpoints. This allows the customer to easily offer differentiated services between SVC nodes.
Reduced Configuration
SVC bundle configuration requires less configuration than a PVC configuration. The PVC bundle feature needs the configuration of PVCs in bundles throughout the ATM network. However, an SVC bundle needs configuration only at the endpoints and uses the User-Network Interface (UNI) to set up SVCs in the bundle between endpoints.
Restrictions
•
Related Features and Technologies
The SVC bundle feature is similar to the IP to ATM Class of Service feature, which is documented in the "Configuring IP to ATM Class of Service" module.
Related Documents
For related information on this feature, refer to the following documents:
•
•
•
•
•
Supported Platforms
•
Platform Support Through Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Feature Navigator. Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image.
To access Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register.
Feature Navigator is updated when major Cisco IOS software releases and technology releases occur. As of May 2001, Feature Navigator supports M, T, E, S, and ST releases. You can access Feature Navigator at the following URL:
http://www.cisco.com/go/fn
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
None
Prerequisites
Before configuring the IP to ATM Class of Service for SVC Bundles feature, you should read and understand the concepts in the following modules:
•
•
•
Configuration Tasks
The following sections describe configuration tasks for the IP to ATM Class of Service Mapping for SVC Bundles feature. Each task in the list is identified as either optional or required.
Note that the bundle members must be configured either directly, by bundle-level parameters, or by class. The bundle configuration should be the same on both ends (the end where the SVC is initiated and the end where it is terminated).
•
•
•
•
Creating an SVC Bundle
Router(config-if)# bundle svc bundle-name nsap destination-nsap-address
Creates or modifies an SVC bundle. The name must be the same on both sides of the VC.
Configuring Bundle-Level Parameters
Attaching a Class to a Bundle
Router(config-if-atm-svc-bundle)# class-bundle vc-class-name
(Optional) Configures a bundle with the bundle-level commands contained in the specified VC class.
Configuring an SVC Bundle Member Directly
Monitoring IP to ATM Class of Service Mapping for SVC Bundles
Configuration Examples
This section provides the following configuration examples:
•
Example: IP to ATM Class of Service Mapping with Bundle Parameters Configured in Bundle Mode
In this example, the bundle parameters are configured in bundle mode. Initially, the end station ID (ESI) address and an Integrated Local Management Interface (ILMI) PVC are configured.
The PVC helps in getting the prefix from the switch (for example, an LS 1010). The combined address is the NSAP address.
You also need to know the other NSAP address to configure the SVC bundle. The eight VC classes are configured with precedences and traffic parameters. The classes must be configured before you attach them to the specific members. The vc-class commands could also be configured in the bundle-member configuration. The configuration of the members must be the same at both ends (that is, where the bundle is initiated and where it is terminated).
vc-class atm sevenvbr-nrt 10000 5000 32precedence 7!vc-class atm sixubr 6000precedence 6!vc-class atm fiveubr 5000precedence 5bump explicit 7!vc-class atm fourubr 4000precedence 4!vc-class atm threeubr 3000precedence 3!vc-class atm twoubr 2000precedence 2!vc-class atm oneubr 1000precedence 1!vc-class atm zeroubr 500precedence other!no ip addressno ip mroute-cacheno atm ilmi-keepaliveatm voice aal2 aggregate-svc upspeed-number 0pvc qsaal 0/5 qsaal!pvc ilmi 0/16 ilmi!bundle-enable!interface ATM1/0.1 multipointip address 170.100.9.2 255.255.255.0atm esi-address 111111111111.11bundle svc test nsap 47.0091810000000003E3924F01.999999999999.99protocol ip 170.100.9.1broadcastoam retry 4 3 10encapsulation aal5snapoam-bundle managesvc-bundle sevenclass-vc sevensvc-bundle sixclass-vc sixsvc-bundle fiveclass-vc fivesvc-bundle fourclass-vc foursvc-bundle threeclass-vc threesvc-bundle twoclass-vc twosvc-bundle oneclass-vc onesvc-bundle zeroclass-vc zero!Example: IP to ATM Class of Service Mapping with Bundle Parameters Configured with the class-bundle Command
In this example, the bundle parameters are added to the bundle by using the class-bundle command. The class attached is named "sanjose".
vc-class atm sanjose !Here we are attaching this vc-class to the whole bundlebroadcastoam retry 4 3 10encapsulation aal5snapoam-bundle manage 3!vc-class atm medubr 10000precedence 4-5!vc-class atm highvbr-nrt 10000 5000 32precedence 6-7!vc-class atm lowubr+ 100000 5000precedence 0-3interface ATM1/0ip address 3.3.3.1 255.255.255.0atm idle-timeout 5atm esi-address 665544332211.22no atm ilmi-keepaliveatm voice aal2 aggregate-svc upspeed-number 0pvc 0/5 qsaal!pvc 0/16 ilmi!pvc 0/100!bundle svc svc-test nsap 47.0091810000000003E3924F01.998877665533.88class-bundle bundle-testprotocol ip 3.3.3.2svc-bundle highclass-vc highsvc-bundle medclass-vc medsvc-bundle lowclass-vc low!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 Quality of Service Solutions Command Reference at http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_book.html. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or a Cisco IOS master commands list.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011 Cisco Systems, Inc. All rights reserved.