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
IP to ATM Class of Service Mapping with Bundle Parameters Configured in Bundle Mode Example
show atm bundle svc statistics
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 chapter "Configuring IP to ATM Class of Service" in the Cisco IOS Quality of Service Solutions Configuration Guide. 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" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.
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 following:
•
•
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
To create an SVC bundle and enter SVC-bundle configuration mode, in which you can assign bundle-level parameters to the bundle and all of its member SVCs, use the following command in interface configuration mode:
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
Configuring bundle-level parameters is optional if a VC class is attached to the bundle to configure it. To attach a class to a bundle, see the "Attaching a Class to a Bundle" section.
To configure parameters that apply to the bundle and all of its members, use the following commands in SVC-bundle configuration mode, as needed:
Attaching a Class to a Bundle
To attach a preconfigured VC class containing bundle-level configuration commands to a bundle, use the following command in SVC-bundle configuration mode:
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
Configuring SVC bundle members directly is optional if a VC class is attached to the bundle member.
Each SVC bundle can have a maximum of eight members. The number of members and the precedence values attached to them should be the same on both ends of the SVC (that is, where the SVC is initiated and where it is terminated).
To configure an individual SVC bundle member directly, use the following commands, as appropriate, starting in SVC-bundle configuration mode:
Monitoring IP to ATM Class of Service Mapping for SVC Bundles
Use the following commands to monitor SVC bundles:
Configuration Examples
This section provides the following configuration examples:
•
IP to ATM Class of Service Mapping with Bundle Parameters Configured in Bundle Mode Example
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!IP to ATM Class of Service Mapping with Bundle Parameters Configured with the class-bundle Command Example
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
This section documents the following new or revised commands that configure the IP to ATM Class of Service Mapping for SVC Bundles feature:
•
•
•
•
bump
To configure the bumping rules for a virtual circuit (VC) class that can be assigned to a VC bundle, use the bump command in vc-class configuration mode. To remove the explicit bumping rules for the VCs assigned to this class and default them to implicit bumping, use the no bump explicit command. To specify that the VC bundle members do not accept any bumped traffic, use the no bump traffic command.
To configure the bumping rules for a specific VC member of a bundle, use the bump configuration command in bundle-vc or SVC-bundle-member configuration mode. To remove the explicit bumping rules for the VC and let it default to implicit bumping, use the no bump explicit command. To specify that the VC does not accept any bumped traffic, use the no form of this command.
bump {implicit | explicit precedence-level | traffic}
no bump {explicit precedence-level | traffic}
Syntax Description
Defaults
Implicit bumping
Bump traffic (VCs accept bumped traffic)
Command Modes
VC-class configuration (for a VC class)
Bundle-vc configuration (for a VC bundle member)
SVC-bundle-member configuration (for an SVC bundle member)Command History
12.0(3)T
This command was introduced.
12.2(4)T
This command was made available in SVC-bundle-member configuration mode.
Usage Guidelines
Use the bump command
•
•
•
The effects of different bumping configuration approaches are as follows:
•
•
•
•
Note
To use this command in vc-class configuration mode, you must enter the vc-class atm global configuration command before you enter this command.
To use this command to configure an individual bundle member in bundle-vc configuration mode, first issue the bundle command to enter bundle configuration mode for the bundle to which you want to add or modify the VC member that is to be configured. Then use the pvc-bundle command to specify the VC to be created or modified and enter bundle-vc configuration mode.
This command has no effect if the VC class that contains the command is attached to a standalone VC; that is, if the VC is not a bundle member. In this case, the attributes are ignored by the VC.
VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next-highest precedence):
•
•
•
Examples
The following example configures the class called "five" to define parameters applicable to a VC in a bundle. If the VC goes down, traffic will be directed (bumped explicitly) to a VC mapped with precedence level 7.
vc-class atm fiveubr 5000precedence 5bump explicit 7Related Commands
bundle svc
To create or modify an SVC bundle, use the bundle svc command in interface configuration mode. To remove the specified bundle, use the no form of this command.
bundle svc bundle-name nsap nsap-address
no bundle svc bundle-name nsap nsap-address
Syntax Description
Defaults
No SVC bundle is created or modified.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command causes the system to enter SVC-bundle-configuration mode. The bundle name must be the same on both sides of the VC.
From SVC-bundle configuration mode, you can configure the characteristics and attributes of the bundle and its members, such as the encapsulation type for all virtual circuits (VCs) in the bundle, the bundle management parameters, the service type, and so on. Attributes and parameters you configure in SVC-bundle configuration mode are applied to all virtual circuit (VC) members of the bundle.
VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next-highest precedence):
•
•
•
To display the status of bundles, use the show atm bundle svc and show atm bundle svc statistics commands.
Examples
The following example configures an SVC bundle called "sanfrancisco".
interface ATM1/0.1 multipointip address 170.100.9.2 255.255.255.0atm esi-address 111111111111.11bundle svc sanfrancisco 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 zeroRelated Commands
class-bundle
To configure a virtual circuit (VC) bundle with the bundle-level commands contained in the specified VC class, use the class-bundle command in bundle or SVC-bundle configuration mode. To remove the VC class parameters from a VC bundle, use the no form of this command.
class-bundle vc-class-name
no class-bundle vc-class-name
Syntax Description
Defaults
No VC class is assigned to the VC bundle.
Command Modes
Bundle configuration
SVC-bundle configurationCommand History
12.0 T
This command was introduced, replacing the class command for configuring ATM VC bundles.
12.2(4)T
This command was made available in SVC-bundle configuration mode.
Usage Guidelines
To use this command, you must first enter the bundle or bundle svc command to create the bundle and enter bundle or SVC-bundle configuration mode.
Use this command to assign a previously defined set of parameters (defined in a VC class) to an ATM VC bundle. Parameters set through bundle-level commands that are contained in a VC class are applied to the bundle and its VC members.
You can add the following commands to a VC class to be used to configure a VC bundle: oam-bundle, broadcast, encapsulation, protocol, oam retry, and inarp.
Bundle-level parameters applied through commands that are configured directly on a bundle supersede bundle-level parameters applied through a VC class by the class-bundle command. Some bundle-level parameters applied through a VC class or directly to the bundle can be superseded by commands that you directly apply to individual VCs in bundle-vc configuration mode.
Examples
In the following example, a class called "class1" is created and then applied to the bundle called bundle1:
! The following commands create the class class1:vc-class atm class1encapsulation aal5snapbroadcastprotocol ip inarpoam-bundle manage 3oam 4 3 10! The following commands apply class1 to the bundle called bundle1:bundle bundle1class-bundle class1With hierarchy precedence rules taken into account, VCs belonging to the bundle "bundle1" will be characterized by these parameters: aal5snap, encapsulation, broadcast on, use of Inverse Address Resolution Protocol (Inverse ARP) to resolve IP addresses, and Operation, Administration, and Maintenance (OAM) enabled.
Related Commands
class-vc
To assign a virtual circuit (VC) class to an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), or VC bundle member, use the class-vc command in the appropriate configuration mode. To remove a VC class, use the no form of this command.
class-vc vc-class-name
no class-vc vc-class-name
Syntax Description
vc-class-name
Name of the VC class that you are assigning to your ATM PVC, SVC, or VC bundle member.
Defaults
No VC class is assigned to an ATM PVC, SVC, or VC bundle member.
Command Modes
Interface-ATM-VC configuration (for ATM PVCs and SVCs)
Bundle-vc configuration (for VC bundle members)
PVC-in-range configuration (for an individual PVC within a PVC range)
SVC-bundle-member configuration (for ATM SVCs)
Command History
Usage Guidelines
Use this command to assign a previously defined set of parameters (defined in a VC class) to an ATM PVC, SVC, or VC bundle member. To create a VC class that defines these parameters, use the vc-class atm command. Refer to the section "Configuring VC Classes" in the "Configuring ATM" chapter of the Cisco IOS Wide-Area Networking Configuration Guide for more information.
ATM PVCs and SVCs
To use this command for assigning a VC class to an ATM PVC or SVC, you must first issue the interface atm command in global configuration mode and then the pvc or svc command in interface configuration mode.
When you create a VC class for an ATM PVC or SVC, you can use the following commands to define your parameters: abr, broadcast, bump, encapsulation, idle-timeout, ilmi manage, inarp, oam-bundle, oam-pvc, oam retry, oam-svc, protocol, ubr, ubr+, and vbr-nrt.
Parameters that are configured for a PVC or SVC through commands entered in interface-ATM-VC configuration mode supersede VC class parameters assigned to an ATM PVC or SVC by the class-vc command.
ATM VC Bundle Members
To use this command for assigning a VC class to a VC bundle member, you must first issue the pvc-bundle command to enter bundle-vc configuration mode.
When you create a VC class for a VC bundle member, you can use the following commands to define your parameters: bump, precedence, protect, ubr, ubr+, and vbr-nrt. You cannot use the following commands in vc-class configuration mode to configure a VC bundle member: encapsulation, protocol, inarp, and broadcast. These commands are useful only at the bundle level, not at the bundle member level.
Parameters that are applied to an individual VC supersede bundle-level parameters. Parameters that are directly configured for a VC through discrete commands entered in bundle-vc configuration mode supersede VC class parameters assigned to a VC bundle member by the class-vc command.
Examples
The following sections show examples for applying the class-vc command to ATM PVC, SVC, and VC bundle members.
In the following example, a class called "classA" is first created and then applied to an ATM PVC:
! The following commands create the class classA:vc-class atm classAubr 10000encapsulation aal5mux ip! The following commands apply classA to an ATM PVC:interface atm 2/0pvc router5 1/32class-vc classAIn the following example, a class called "classA" is first created and then applied to the bundle member called "vcmember", a member of "bundle1":
! The following commands create the class classA:vc-class atm classAprecedence 6-5no bump trafficprotect groupbump explicitly 7vbr-nrt 20000 10000 32! The following commands create bundle1, add vcmember to bundle1, and then applies classA! to vcmember:bundle bundle1pvc-bundle vcmemberclass-vc classAWith hierarchy precedence rules taken into account, the VC bundle member "vcmember" will be characterized by these parameters:
•
•
•
•
Related Commands
debug atm bundle error
To display debug messages for SVC bundle errors, use the debug atm bundle error command in EXEC mode. To disable the debug output, use the no form of this command.
debug atm bundle error
no debug atm bundle error
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example provides output for the debug atm bundle error command:
Router# debug atm bundle errorRelated Commands
debug atm bundle events
To display SVC bundle events, use the debug atm bundle events command in EXEC mode. To disable the debug output, use the no form of this command.
debug atm bundle events
no debug atm bundle events
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example provides output for the debug atm bundle events command:
Router# debug atm bundle events01:14:35:BUNDLE EVENT(test):b_update_vc for four with bstate 1, vc_state401:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x01 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x02 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x04 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x08 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x10 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x20 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x40 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x80 0 -01:14:35:BUNDLE EVENT(test):bundle precedence updatedTable 1 describes the fields in the output.
Related Commands
encapsulation aal5
To configure the ATM adaptation layer (AAL) and encapsulation type for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), virtual circuit (VC) class, or VC bundle, use the encapsulation aal5 command in the appropriate command mode. To remove an encapsulation from a PVC, SVC, VC class, or VC bundle, use the no form of this command.
encapsulation aal5encap [virtual-template number]
no encapsulation aal5encap [virtual-template number]
Note
Syntax Description
Syntax Description
Defaults
The global default encapsulation is snap. See the "Usage Guidelines" section for other default characteristics.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle configuration (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
SVC-bundle configuration mode (for SVC bundles)
Command History
Usage Guidelines
A VC bundle can have only one encapsulation configured for it: either snap or mux.
An SVC bundle can have either snap or mux ip specified in the encapsulation aal5 command.
Use one of the mux encapsulation options to dedicate the specified PVC to a single protocol; use the snap encapsulation option to multiplex two or more protocols over the same PVC. Whether you select mux or snap encapsulation might depend on practical considerations, such as the type of network and the pricing offered by the network. If the pricing of the network depends on the number of PVCs set up, snap might be the appropriate choice. If pricing depends on the number of bytes transmitted, mux might be the appropriate choice because it has slightly less overhead.
To use this command to configure a VC bundle, first enter the bundle subinterface configuration command to create a new bundle or modify an existing one and to enter bundle configuration mode.
Note
When configuring Cisco PPP over ATM, specify the ciscoppp encapsulation for the encap argument and specify the virtual template number.
It is possible to implicitly create a virtual template when configuring Cisco PPP over ATM. In other words, if the parameters of the virtual template are not explicitly defined before you configure the ATM PVC, the PPP interface will be brought up using default values from the virtual template identified. However, some parameters (such as an IP address) take effect only if they are specified before the PPP interface comes up. Therefore, we recommend that you explicitly create and configure the virtual template before configuring the ATM PVC to ensure that such parameters take effect.
If you specify virtual template parameters after the ATM PVC is configured, you should enter a shutdown command followed by a no shutdown command on the ATM subinterface to restart the interface, causing the newly configured parameters (such as an IP address) to take effect.
If the encapsulation aal5 command is not explicitly configured on an ATM PVC, SVC, or VC bundle, the VC inherits the following default configuration (listed in order of precedence from lowest to highest):
•
•
•
•
When configuring a PVC range or an individual PVC within a PVC range, you have the following options:
•
•
•
Examples
The following example configures an ATM SVC called "chicago" with encapsulation auto. Encapsulation auto enables the SVC to use PPP and either aal5snap or aal5mux encapsulation.
svc chicagoencapsulation aal5autoThe following example configures an ATM PVC with VPI 0 and VCI 33 for a MUX-type encapsulation using IP:
pvc 0/33 encapsulation aal5mux ipThe following example configures a bundle called "chicago" for aal5snap encapsulation:
bundle chicago encapsulation aal5snapRelated Commands
idle-timeout
To configure the idle timeout parameter for tearing down an ATM switched virtual circuit (SVC), use the idle-timeout command in the appropriate command mode. To disable the timeout parameter, use the no form of this command.
idle-timeout seconds [minimum-rate]
no idle-timeout seconds [minimum-rate]
Syntax Description
Defaults
seconds: 300 seconds
minimum-rate: 0 kbpsCommand Modes
Interface-ATM-VC configuration (for ATM permanent virtual circuits [PVCs] or SVCs)
VC-class configuration (for virtual circuit [VC] classes)
SVC-bundle-member configuration (for ATM SVCs)
Command History
11.3
This command was introduced.
12.2(4)
This command was made available in SVC-bundle-member configuration mode.
Usage Guidelines
If, within the idle timeout period, both the input and output traffic rates are below the minimum rate, the SVC connection is torn down. The input and output traffic rates are set using the ubr, ubr+, or vbr-nrt command.
If the idle-timeout command is not explicitly configured on an ATM SVC, the SVC inherits the following default configuration (listed in order of next-highest precedence):
•
•
•
•
In SVC-bundle-member configuration mode, this command controls when the bundle members time out. When the bundle member times out, the SVC is torn down. Note that the bundle itself does not time out.
Examples
The following example configures an ATM SVC connection inactive after an idle period of 300 seconds. The SVC connection is also configured so that it is considered inactive if the traffic rate is less than 5 kbps.
idle-timeout 300 5Related Commands
oam-bundle
To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for all VC members of a bundle or a virtual circuit (VC) class that can be applied to a VC bundle, use the oam-bundle command in SVC-bundle configuration mode or vc-class configuration mode. To remove OAM management from the bundle or class configuration, use the no form of this command.
To enable end-to-end F5 OAM loopback cell generation and OAM management for all VC members of a bundle, use the oam-bundle command in bundle configuration mode. To remove OAM management from the bundle, use the no form of this command.
oam-bundle [manage] [frequency]
no oam-bundle [manage] [frequency]
Syntax Description
Defaults
End-to-end F5 OAM loopback cell generation and OAM management are disabled, but if OAM cells are received, they are looped back. The default value for the frequency argument is 10 seconds.
Command Modes
VC-class configuration (for a VC class)
Bundle configuration (for an ATM VC bundle)
SVC-bundle configuration (for an SVC bundle)
Command History
12.0(3)T
This command was introduced.
12.2(4)T
This command was made available in SVC-bundle configuration mode.
Usage Guidelines
This command defines whether a VC bundle is OAM-managed. If this command is configured for a bundle, every VC member of the bundle is OAM-managed. If OAM management is enabled, further control of OAM management is configured using the oam retry command.
This command has no effect if the VC class that contains the command is attached to a standalone VC; that is, if the VC is not a bundle member. In this case, the attributes are ignored by the VC.
To use this command in bundle configuration mode, enter the bundle subinterface configuration command to create the bundle or to specify an existing bundle before you enter this command.
To use this command in vc-class configuration mode, first enter the vc-class atm global configuration command.
VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of next-highest precedence):
•
•
Examples
The following example enables OAM management for a bundle called "chicago":
bundle chicago oam-bundle manageRelated Commands
precedence (VC bundle)
To configure precedence levels for a virtual circuit (VC) class that can be assigned to a VC bundle and thus applied to all VC members of that bundle, use the precedence command in vc-class configuration mode. To remove the precedence levels from the VC class, use the no form of this command.
To configure the precedence levels for a VC member of a bundle, use the precedence command in bundle-vc or SVC-bundle-member configuration mode. To remove the precedence levels from the VC, use the no form of this command.
precedence [other | range]
no precedence
Syntax Description
Defaults
Defaults to other—that is, any precedence levels in the range from 0 to 7 that are not explicitly configured.
Command Modes
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
SVC-bundle-member configuration (for an ATM SVC)
Command History
Usage Guidelines
Assignment of precedence levels to VC bundle members allows you to create differentiated service because you can distribute the IP Precedence levels over the various VC bundle members. You can map a single precedence level or a range of levels to each individual VC in the bundle, thereby enabling VCs in the bundle to carry packets marked with different precedence levels. Alternatively, you can configure a VC with the precedence other command to indicate that it can carry traffic marked with precedence levels not specifically configured for it. Only one VC in the bundle can be configured with the precedence other command to carry all precedence levels not specified. This VC is considered the default one.
To use this command in vc-class configuration mode, enter the vc-class atm global configuration command before you enter this command. This command has no effect if the VC class that contains the command is attached to a standalone VC; that is, if the VC is not a bundle member.
To use this command to configure an individual bundle member in bundle-vc configuration mode, first enter the bundle command to enact bundle configuration mode for the bundle to which you want to add or modify the VC member to be configured. Then use the pvc-bundle command to specify the VC to be created or modified and enter bundle-vc configuration mode.
VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next-highest precedence):
•
•
•
Examples
The following example configures a class called "control-class" that includes a precedence command that, when applied to a bundle, configures all VC members of that bundle to carry IP Precedence level 7 traffic. Note, however, that VC members of that bundle can be individually configured with the precedence command at the bundle-vc level, which would supervene.
vc-class atm control-classprecedence 7The following example configures permanent virtual circuit (PVC) 401 (with the name of "control-class") to carry traffic with IP Precedence levels in the range from 4 to 2, overriding the precedence level mapping set for the VC through vc-class configuration:
pvc-bundle control-class 401precedence 4-2Related Commands
protocol (ATM)
To configure a static map for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), or VC class or to enable Inverse Address Resolution Protocol (ARP) or Inverse ARP broadcasts on an ATM PVC, use the protocol command in the appropriate mode. To remove a static map or disable Inverse ARP, use the no form of this command.
To configure the destination network address of an SVC bundle, use the protocol command in SVC-bundle configuration mode.
protocol protocol {protocol-address | inarp} [[no] broadcast]
no protocol protocol {protocol-address | inarp} [[no] broadcast]
Syntax Description
Defaults
Inverse ARP is enabled for IP and IPX if the protocol is running on the interface and no static map is configured.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
SVC-bundle configuration (for an SVC bundle)
Command History
Usage Guidelines
Command Application
Use this command to perform one of the following tasks:
•
•
•
PVC range and PVC-in-range configuration modes support only the protocols that do not require static map configuration. Those protocol options are ip and ipx.
Default Configurations
If the protocol command is not explicitly configured on an ATM PVC or SVC, the VC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example creates a static map on a VC, indicates that 10.68.34.237 is connected to this VC, and sends ATM pseudobroadcasts:
protocol ip 10.68.34.237 broadcastThe following example enables Inverse ARP for IPX and does not send ATM pseudobroadcasts:
protocol ipx inarp no broadcastThe following example removes a static map from a VC and restores the default behavior for Inverse ARP (see the "Defaults" section for this command):
no protocol ip 10.68.34.237show atm bundle svc
To display the bundle attributes assigned to each bundle virtual circuit member and the current working status of the VC members, use the show atm bundle svc command in privileged EXEC mode.
show atm bundle svc [bundle-name]
Syntax Description
bundle-name
(Optional) Name of the SVC bundle to be displayed, as identified by the bundle svc command.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no bundle name is specified, all SVC bundles configured on the system are displayed.
Examples
The following example provides output for the show atm bundle svc command. The bundle named finance is configured on ATM interface 1/0.1 with eight members. All of the members are up except bundle member zero. Bundle member zero is the default member, which if initiated once will always be on and used as the default for all traffic.
Router# show atm bundle svc financefinance on ATM1/0.1:UPConfig Current Peak Avg/Min BurstVC Name VPI/VCI Preced. Preced. Kbps kbps Cells Stsseven 0/37 7 7 10000 5000 32 UPsix 0/36 6 6 6000 UPfive 0/40 5 5 5000 UPfour 0/41 4 4 4000 UPthree 0/42 3 3 3000 UPtwo 0/43 2 2 2000 UPone 0/44 1 1 1000 UPzero* 0Table 2 describes the fields in the display.
Related Commands
show atm bundle svc statistics
To display the statistics of an SVC bundle, use the show atm bundle svc statistics command in privileged EXEC mode.
show atm bundle svc bundle-name statistics
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example provides output for the show atm bundle svc statistics command using a bundle named sanjose:
Router# show atm bundle svc sanjose statisticsBundle Name:Bundle State:INITIALIZINGAAL5-NLPIDOAM frequency:0 second(s), OAM retry frequency:10 second(s)OAM up retry count:4, OAM down retry count:3BUNDLE is managed by.InARP frequency:15 minutes(s)InPkts:0, OutPkts:0, InBytes:0, OutBytes:0InPRoc:0, OutPRoc:0, Broadcasts:0InFast:0, OutFast:0, InAS:0, OutAS:0InPktDrops:0, OutPktDrops:0CrcErrors:0, SarTimeOuts:0, OverSizedSDUs:0,LengthViolation:0, CPIErrors:0Table 3 describes the fields in the display.
Related Commands
svc-bundle
To create or modify a member of an SVC bundle, use the svc-bundle command in SVC-bundle configuration mode. To remove an SVC bundle member from the bundle, use the no form of this command.
svc-bundle svc-handle
no svc-bundle svc-handle
Syntax Description
Defaults
No SVCs are members of an SVC bundle.
Command Modes
SVC-bundle configuration mode
Command History
Usage Guidelines
Using this command will cause the system to enter SVC-bundle member configuration mode, in which you can configure characteristics of the member such as precedence, Variable Bit Rate (VBR) traffic shaping, Unspecified Bit Rate (UBR) traffic shaping, UBR+ traffic shaping, an idle timeout, and bumping conditions.
Examples
The following example creates a member of an SVC bundle named five:
svc-bundle fiveubr
To configure unspecified bit rate (UBR) quality of service (QoS) and specify the output peak cell rate (PCR) for an ATM permanent virtual circuit (PVC), PVC range, switched virtual circuit (SVC), virtual circuit (VC) class, or VC bundle member, use the ubr command in the appropriate command mode. To remove the UBR parameter, use the no form of this command.
ubr output-pcr [input-pcr]
no ubr output-pcr [input-pcr]
Syntax Description
output-pcr
The output PCR in kbps.
input-pcr
(Optional for SVCs only) The input peak cell rate (PCR), in kilobits per second. If this value is omitted, the input-pcr will equal the output-pcr.
Defaults
UBR QoS at the maximum line rate of the physical interface.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
SVC-bundle-member configuration (for an SVC)
Command History
Usage Guidelines
To configure ATM SVCs with an output PCR and an input PCR that differ from each other, you must expressly configure an output value and an input value using the output-pcr and input-pcr arguments, respectively.
Configure QoS parameters using the ubr, ubr+, or vbr-nrt command. The last command you enter will apply to the PVC or SVC you are configuring.
If the ubr command is not explicitly configured on an ATM PVC, SVC, or VC bundle member, the VC inherits the following default configuration (listed in order of next-highest precedence):
•
•
•
•
To use this command in VC-class configuration mode, enter the vc-class atm global configuration command. This command has no effect if the VC class that contains the command is attached to a standalone VC; that is, if the VC is not a bundle member.
To use this command in bundle-vc configuration mode, first enter the bundle command to specify the bundle, and enter bundle configuration mode. Then enter the pvc-bundle configuration command to add the VC to the bundle as a member of it and enter bundle-vc configuration mode.
VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of next-highest precedence):
•
•
•
Examples
The following example specifies the output-pcr argument for an ATM PVC to be 100,000 kbps:
pvc 1/32ubr 100000The following example specifies the output-pcr and input-pcr arguments for an ATM SVC to be 10,000 kbps and 9,000 kbps, respectively:
svc lion nsap 47.0091.81.000000.0040.0B0A.2501.ABC1.3333.3333.05ubr 10000 9000Related Commands
ubr+
To configure unspecified bit rate (UBR) quality of service (QoS) and specify the output peak cell rate and output minimum guaranteed cell rate for an ATM permanent virtual circuit (PVC), PVC range, switched virtual circuit (SVC), virtual circuit (VC) class, or VC bundle member, use the ubr+ command in the appropriate command mode. To remove the UBR+ parameters, use the no form of this command.
ubr+ output-pcr output-mcr [input-pcr] [input-mcr]
no ubr+ output-pcr output-mcr [input-pcr] [input-mcr]
Syntax Description
Defaults
UBR QoS at the maximum line rate of the physical interface.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
SVC-bundle-member configuration (for an SVC)
Command History
Usage Guidelines
To configure ATM SVCs with an output PCR and an input PCR that differ from each other, you must expressly configure an output value and an input value using the output-pcr, output-mcr, input-pcr, and input-mcr arguments, respectively.
Configure QoS parameters using the ubr, ubr+, or vbr-nrt command. The last command you enter will apply to the PVC or SVC that you are configuring.
If the ubr+ command is not explicitly configured on an ATM PVC or SVC, the VC inherits the following default configuration (listed in order of precedence):
•
•
•
•
To use this command in VC-class configuration mode, enter the vc-class atm global configuration command before you enter the ubr+ command. This command has no effect if the VC class that contains the command is attached to a standalone VC; that is, if the VC is not a bundle member.
To use this command in bundle-vc configuration mode, first enter the bundle command to specify the bundle to which the VC member belongs, and enter bundle configuration mode. Then enter the pvc-bundle bundle configuration command to add the VC to the bundle as a member of it.
VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of next-highest precedence):
•
•
•
Examples
The following example specifies the output-pcr argument for an ATM PVC to be 100,000 kbps and the output-mcr to be 3000 kbps:
pvc 1/32ubr+ 100000 3000The following example specifies the output-pcr, output-mcr, input-pcr, and input-mcr arguments for an ATM SVC to be 10,000 kbps, 3000 kbps, 9000 kbps, and 1000 kbps, respectively:
svc lion nsap 47.0091.81.000000.0040.0B0A.2501.ABC1.3333.3333.05ubr+ 10000 3000 9000 1000Related Commands
vbr-rt
To configure the real-time variable bit rate (VBR) for voice connections on the Cisco MC3810, use the vbr-rt in the appropriate mode. To restore the default value, use the no form of this command.
vbr-rt peak-rate average-rate burst
no vbr-rt peak-rate average-rate burst
Syntax Description
Defaults
No VBR settings are configured.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
SVC-bundle-member configuration (for an SVC)
Command History
Usage Guidelines
This command applies to Voice over ATM on the Cisco MC3810.
The vbr-rt command configures traffic shaping between voice and data permanent virtual circuits (PVCs). Traffic shaping is required so that the carrier does not discard calls. To configure voice and data traffic shaping, you must configure the peak, average, and burst options for voice traffic. Configure the burst value if the PVC will be carrying bursty traffic. The peak, average, and burst values are needed so the PVC can effectively handle the bandwidth for the number of voice calls.
To calculate the minimum peak, average, and burst values for the number of voice calls, use the following formulas:
•
•
•
Note
Examples
The following example configures the traffic shaping rate for ATM PVC 20 on a Cisco MC3810. In the example, the peak, average and burst rates are calculated on the basis of a maximum of 20 calls on the PVC.
pvc 20encapsulation aal5mux voicevbr-rt 640 320 80Related Commands
