Cisco 10000 Series Router Quality of Service Configuration Guide
Configuring Quality of Service for PVC Bundles
Downloads: This chapterpdf (PDF - 736.0KB) The complete bookPDF (PDF - 21.32MB) | Feedback

Configuring Quality of Service for PVC Bundles

Table Of Contents

Configuring Quality of Service for PVC Bundles

PVC Bundles

Feature History for PVC Bundles

System Limits for PVC Bundles

Traffic Bumping

PVC Bundle Protection Rules

ATM PVC Selection

Feature History for ATM PVC Selection

Configuration Commands for ATM PVC Selection

bump Command

bundle Command

class-bundle Command

class-vc Command

mpls experimental Command

oam-bundle Command

precedence Command

protect Command

pvc-bundle Command

ATM Bundle Management

Bumping and ATM PVC Bundles

Prerequisites for ATM PVC Selection

Restrictions and Limitations for ATM PVC Selection

Configuring ATM Bundles

Creating an ATM Bundle Directly

Creating an ATM Bundle Using a VC Class

Adding an ATM PVC to a PVC Bundle

Configuring ATM Bundle Members

Configuring an ATM Bundle Member

Configuring an ATM Bundle Member Using a VC Class

Configuring a PVC Not to Accept Bumped Traffic

Verifying and Monitoring ATM PVC Bundles

Configuration Examples for Configuring ATM Bundles and PVC Selection

Configuration Example for ATM Bundle Configuration Using VC Classes

Configuration Example for MPLS EXP-Based ATM PVC Selection

Frame Relay PVC Selection

Feature History for Frame Relay PVC Selection

Configuration Commands for Frame Relay PVC Selection

bump Command (Frame Relay VC-bundle-member)

dscp Command (Frame Relay VC-bundle-member)

exp Command

frame-relay vc-bundle Command

precedence Command (Frame Relay VC-bundle-member)

protect Command (Frame Relay VC-bundle-member)

pvc Command (Frame Relay VC-bundle)

Service Levels and PVC Selection Criteria

Prerequisites for Frame Relay PVC Selection

Restrictions and Limitations for Frame Relay PVC Selection

Configuring Frame Relay Bundles

Creating a Frame Relay PVC Bundle

Adding a PVC to a Frame Relay PVC Bundle

Configuring Frame Relay Bundle Members

Configuration Examples for Configuring Frame Relay Bundles and PVC Selection

Configuration Example for Precedence-Based and DSCP-Based Frame Relay PVC Selection

Configuration Example for MPLS EXP-Based Frame Relay PVC Selection

Verifying and Monitoring Frame Relay PVC Selection

Verification Example for Monitoring PVC Bundles

Related Documentation


Configuring Quality of Service for PVC Bundles


Networks can span many geographical locations and can utilize the full spectrum of networking technologies available for both network access and the network core. In some networks the core connections are over existing low-speed Frame Relay or ATM networks. Because service providers have invested substantially in these networks, providers need a way to differentiate themselves from other providers and increase profitability while using these low-speed links. The Cisco 10000 series router offers advanced IP QoS as a solution.

The Cisco 10000 series router provides IP QoS over multiple ATM and Frame Relay PVCs combined into PVC bundles. By using PVC bundles and QoS-based PVC selection to carry packets, service providers can increase bandwidth between two routers when the connectivity is limited to low-speed switched circuits.

This chapter describes PVC bundles and QoS-based PVC selection over ATM and Frame Relay PVCs. It includes the following topics:

PVC Bundles

ATM PVC Selection

Frame Relay PVC Selection

Related Documentation

PVC Bundles

A PVC bundle is a group of permanent virtual circuits (PVCs) combined into a logical group with a single, virtual interface that connects to a peer system. PVC bundles enable service providers to offer different levels of service through the use of IP precedence, differentiated services code point (DSCP), and Multiprotocol Label Switching (MPLS) experimental (EXP) levels, and QoS features. Using the PVC bundle management software, you can create a bundle of PVCs between a pair of connected routers and assign different QoS characteristics to individual PVCs in the bundle. Each PVC in a bundle has its own traffic class and traffic parameters, and is configured to carry packets whose priority matches the configured range.

Using PVC bundles, you can do the following:

Create differentiated service by distributing IP precedence, DSCP, or MPLS EXP levels over different PVCs in the bundle.

Map a single precedence, DSCP, or MPLS EXP level or a range of levels to each discrete PVC in the bundle, thereby enabling individual PVCs in the bundle to carry packets marked with different levels.

Use Weighted Random Early Detection (WRED) to further differentiate service across traffic that has different precedence, DSCP, or MPLS EXP levels.

To determine which PVC in the bundle to use to forward an IP or MPLS packet, the router examines the packet's priority bits or Type of Service (ToS) field, or the packet's EXP bits. Each PVC in the bundle is configured to carry packets whose priority matches the configured precedence, DSCP, or MPLS EXP level. Combined with a queuing mechanism at the output interface, this offers a complete QoS solution for both data and voice, and allows for further granularization of data types to differentiate data priorities.

The router supports both ATM and Frame Relay PVC bundles.

Figure 19-1 shows a PVC bundle.

Figure 19-1 PVC Bundle

Feature History for PVC Bundles

Cisco IOS Release
Description
Required PRE

Release 12.0(26)S

PVC bundles over ATM and Frame Relay were introduced on the PRE1 and included support for IP precedence and DSCP-based PVC selection. The ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection feature and the Frame Relay PVC Bundles with QoS Support for IP and MPLS feature were also introduced.

PRE1


System Limits for PVC Bundles

Table 19-1 lists the system limits for PVC bundles.

Table 19-1 System Limits for PVC Bundles

Bundle
Type
Max. No. of Members
Per Bundle
Max. No. of Bundles
Per System

ATM

8

16,000

Frame Relay

8

16,000



Note IP precedence and MPLS EXP have eight levels that you can assign and DSCP has 64 levels. To include all DSCP values, you can assign a range of DSCP values (for example, 9-16) to a particular DLCI and assign the remaining DSCP values to another DLCI using the dscp other command.


Traffic Bumping

Traffic bumping provides a way to keep a PVC bundle up and traffic flowing even though some individual PVCs might be down. You can configure each PVC bundle member to bump traffic to another PVC in the bundle when the bundle member does down. You can also specify that a particular PVC can never accept bumped traffic from another PVC. The default is to accept bumped traffic.

You can specify traffic bumping as either implicit or explicit bumping. Implicit bumping diverts the traffic from a failed PVC to the PVC having the next lower service level. Explicit bumping forces the traffic to a specific PVC rather than allowing it to find a PVC carrying traffic of the next lower service level. The default is to perform implicit traffic bumping.

For example, consider a sample configuration with two PVCs: PVC1 and PVC2. You configure PVC1 to carry precedence level 3 traffic, PVC2 to accept bumped traffic and to carry precedence level 6 traffic, and PVC1 to bump its traffic to PVC2. If PVC1 goes down, the following occurs:

PVC2 takes over.

If PVC2 is already down or goes down later, the router selects an alternate PVC based on the bumping rule for PVC2.

If the router cannot find an alternate PVC for the bumped traffic, the entire PVC bundle goes down.

If a bundle member allows PVC bumping, the router selects the next lower precedence level PVC when a PVC goes down. You can specify only one precedence level for bumping. If the PVC that carries the bumped traffic fails, the router applies the bumping rules specified for the failed PVC to the traffic. When the original PVC is up again, the router restores traffic to the original PVC.

PVC Bundle Protection Rules

PVC bundle protection rules provide a way to force the PVC bundle down even though some individual PVCs are up and might be able to handle all of the traffic, though perhaps not in a satisfactory manner. The protection rules add flexibility for controlling the state of the PVC bundle.

You can configure a PVC bundle member as an individually protected PVC or as part of a PVC bundle protected group. Only one protected group can exist within a PVC bundle; however, many individually protected PVCs can exist.

When a bundle goes down, the router cannot forward traffic using the bundle, even if some of the PVCs in the bundle are still up. The entire bundle goes down when:

One individually protected PVC goes down

All of the PVCs in a protected group go down.

If you do not specify a protection rule, the PVC bundle goes down only when all of the PVCs go down. However, if a PVC that has no place to bump its traffic goes down, the router brings down the entire bundle despite any protection rules that have been set up.

ATM PVC Selection

The Cisco 10000 series router can forward packets to ATM bundle members based on the IP precedence level or Multiprotocol Label Switching (MPLS) experimental (EXP) level of the packets.

The ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection feature allows you to configure multiple PVCs with different QoS characteristics between any pair of ATM-connected routers and to configure a group of ATM PVCs with a single next-hop address. Packets are mapped to specific PVCs in the bundle on the basis of the precedence value or MPLS EXP value in the type of service (ToS) field of the IP header. Each packet is treated differently according to the QoS configured for each PVC.

The MPLS EXP-Based PVC Selection feature provides flexible PVC management within a PVC bundle by allowing traffic assigned to a failed PVC to be redirected to an alternate PVC within the bundle. It also allows you to configure the bundle to go down when certain PVCs go down. IP packets carrying different types of traffic can be transported on different PVCs within the same PVC bundle.

Using MPLS-based ATM PVC selection, you can do the following:

Map a single precedence level or MPLS EXP level, or a range of precedence or MPLS EXP levels, to each PVC in the bundle. This enables you to limit an individual PVC to carry only packets marked with a specific precedence or MPLS EXP level, or packets marked with different precedence or MPLS EXP levels. For unlabeled packets that do not specify a selection criteria, the router uses IP precedence level as the default selection criteria for packet forwarding.

Configure a PVC to support unmapped traffic. If the PVC fails, the router attempts to identify an alternate PVC. If the router cannot locate an alternate PVC, the router stops the PVC bundle.

Create differentiated service using PVC bundles by distributing MPLS EXP levels over the different PVC bundle members.

Use Weighted Random Early Detection (WRED) to further differentiate service across traffic that has different MPLS EXP levels.

The Cisco 10000 series router forwards non-IP packets using the PVC that is responsible for carrying precedence level 6 traffic. The router uses process-switching to forward locally generated packets as follows:

1. To determine which PVC in a bundle is used to forward a specific type of traffic, the ATM VC bundle management software matches MPLS EXP levels between packets and PVCs. Because all PVCs in a bundle share the same destination, the router forwards IP traffic to the next hop address for the bundle, but the PVC used to carry a packet depends on the value set for that packet in the MPLS EXP level of the type of service (ToS) byte of its header.

2. The ATM PVC bundle management software matches the MPLS EXP level of the packet to the MPLS EXP levels assigned to a PVC and sends the packet out on the appropriate PVC. The ATM PVC bundle management software also allows you to configure how traffic is redirected if a PVC goes down.

3. MPLS EXP-based PVC selection maps the IP precedence level in the IPv4 header to a PVC configured with the same value. The three precedence bits in the type of service (ToS) byte of the IP header defines the precedence levels for IP traffic. You can use a default PVC for all unspecified precedence levels.

4. After you define an ATM bundle and add PVCs to it, you can configure attributes and characteristics to discrete PVC bundle members, or you can apply them collectively at the bundle level. You can apply ATM traffic shaping to each PVC within a bundle.

Feature History for ATM PVC Selection

Cisco IOS Release
Description
Required PRE

Release 12.0(26)S

The ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection feature was introduced on the PRE1.

PRE1


Configuration Commands for ATM PVC Selection

This section describes the following configuration commands:

bump Command

bundle Command

class-bundle Command

class-vc Command

mpls experimental Command

oam-bundle Command

precedence Command

protect Command

pvc-bundle Command

bump Command

To configure the bumping rules for a PVC bundle or a specific PVC bundle member, use the bump command in VC class or bundle member configuration mode. To remove the explicit bumping rules and return to the default condition of implicit bumping, use the no form of the command.

bump {explicit precedence-level | implicit | traffic}
 
   
no bump {explicit precedence-level | implicit | traffic} 
 
   

Syntax Description

explicit precedence-level

Specifies the precedence level to which traffic on a VC or PVC is bumped when the VC or PVC goes down. Valid values are from 0 to 7.

implicit

Applies the implicit bumping rule, which is the default, to a single VC or PVC bundle member, or to all VCs in the bundle (VC-class mode). The implicit bumping rule stipulates that bumped traffic is to be carried by a VC or PVC with a lower precedence level.

traffic

Specifies that the VC or PVC accepts bumped traffic. By default, a PVC permits bumping and accepts bumped traffic.

To configure a PVC to reject bumped traffic from another bundle member, enter the no bump traffic command.


bump Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

Implicit bumping

Permit bumping (VCs accept bumped traffic)

Configuration Mode

VC-class configuration (for a VC class)

Bundle-vc configuration (for an ATM VC bundle member)

Usage Guidelines for the bump Command

If you configure implicit bumping, bumped traffic is sent to the PVC configured to handle the next lower precedence level. When the original PVC that bumped the traffic comes back up, the traffic that it is configured to carry is restored to it. If no other positive forms of the bump command are configured, the bump implicit command takes effect.

If you configure a PVC with the bump explicit command, you can specify the precedence level or MPLS EXP level to which traffic is bumped when that PVC goes down, and the traffic is directed to a PVC mapped with that precedence or MPLS EXP level. If the PVC that picks up and carries the traffic goes down, the traffic is subject to the bumping rules for that PVC. You can specify only one precedence level for bumping.

The PVC accepts bumped traffic by default. If the PVC has been previously configured to reject bumped traffic, you must use the bump traffic command to return the PVC to its default condition.

To configure a discrete PVC to reject bumped traffic when the traffic is directed to it, use the no bump traffic command.

bundle Command

To create a bundle or modify an existing bundle, use the bundle command in subinterface configuration mode. To remove the specified bundle, use the no form of the command. By default, no bundle is specified.

bundle bundle-name
 
   
no bundle bundle-name 

Syntax Description

bundle-name

Specifies the name of the bundle to create or modify. The bundle-name is limited to 16 alphanumeric characters.


bundle Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Usage Guidelines for the bundle Command

In the 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 bundle configuration mode are applied to all bundle members.

VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next highest precedence):

VC configuration in bundle-vc mode

Bundle configuration in bundle mode

Subinterface configuration in subinterface mode

To display the status of bundles, use the show atm bundle and show atm bundle statistics commands.

class-bundle Command

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 configuration mode. To remove the VC class parameters from a VC bundle, use the no form of the command.

class-bundle vc-class-name
 
   
no class-bundle vc-class-name 

Syntax Description

vc-class-name

Name of the VC class that you are assigning to your VC bundle.


class-bundle Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

No VC class is assigned to the VC bundle.

Usage Guidelines for the class-bundle Command

To use this command, you must first enter the bundle command to create the bundle and enter 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: broadcast, encapsulation, inarp, oam-bundle, oam retry, and protocol.

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.

class-vc Command

To assign a virtual circuit (VC) class to an ATM permanent virtual circuit (PVC) or PVC 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 you are assigning to your ATM PVC, SVC, or VC bundle member.


class-vc Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Configuration Modes

Interface-ATM-VC configuration (for ATM PVCs)

Bundle-vc configuration (for VC bundle members)

PVC-range configuration (for PVC ranges)

Usage Guidelines for the class-vc Command

To use this command for assigning a VC class to a VC bundle member, you must first use 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 the bundle member level.

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

mpls experimental Command

To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a virtual circuit (VC) class that can be assigned to a PVC bundle and thus applied to all PVC members of that bundle, use the mpls experimental command in vc-class configuration mode. To remove the MPLS EXP levels from the VC class, use the no form of the command.

To configure the MPLS EXP levels for a PVC member of a bundle, use the mpls experimental command in bundle-vc configuration mode. To remove the MPLS EXP levels from the PVC, use the no form of the command.

mpls experimental [other | range]
 
   
no mpls experimental 

Syntax Description

other

(Optional) Any MPLS EXP levels that are not explicitly configured.

range

(Optional) A single MPLS EXP level specified as a number from 0 to 7, or a range of levels specified as a hyphenated range.


mpls experimental Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

Defaults to other, that is, any MPLS EXP levels that are not explicitly configured.

Configuration Modes

VC-class configuration (for a VC class)

Bundle-vc configuration (for ATM VC bundle members)

Usage Guidelines for the mpls experimental Command

Assignment of MPLS EXP levels to VC bundle members allows you to create differentiated service because you can distribute the MPLS EXP levels over the different VC bundle members. You can map a single level or a range of levels to each discrete VC in the bundle, thereby enabling VCs in the bundle to carry packets marked with different levels. Alternatively, you can configure a VC with the mpls experimental other command to indicate that it can carry traffic marked with levels not specifically configured for it. Only one VC in the bundle can be configured with the mpls experimental other command to carry all levels not specified. This VC is considered the default VC.

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 MPLS EXP level):

VC configuration in bundle-vc mode

Bundle configuration in bundle mode (with the effect of assigned vc-class configuration)

Subinterface configuration in subinterface mode


Note If you are using an ATM interface, you must configure all MPLS EXP levels (ranging from 0 to 7) for the bundle. To do this, we recommend configuring one member of the bundle with the mpls experimental other command. The other keyword defaults to any MPLS EXP levels in the range from 0 to 7 that are not explicitly configured.


oam-bundle Command

To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for all permanent virtual circuit (PVC) members of a bundle or a VC class that can be applied to a PVC bundle, use the oam-bundle command in VC-class configuration mode. To remove OAM management from the bundle or class configuration, use the no form of the command.

oam-bundle [manage] [frequency]
 
   
no oam-bundle [manage] [frequency]

Syntax Description

manage

(Optional) Enables OAM management. If you omit this keyword, loopback cells are sent, but the bundle is not managed.

frequency

(Optional) Number of seconds between transmitted OAM loopback cells. Valid values are from 0 to 600 seconds. The default value is 10 seconds.


oam-bundle Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

End-to-end F5 OAM loopback cell generation and OAM management are disabled, but if OAM cells are received, they are looped back.

Configuration Modes

VC-class configuration (for a VC class)

Bundle configuration (for an ATM VC bundle)

Usage Guidelines for the oam-bundle Command

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 VC-class configuration mode, first enter the vc-class atm global configuration command.

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.

VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of next-highest precedence):

VC configuration in bundle-VC mode

Bundle configuration in bundle mode (with effect of assigned VC-class configuration)

precedence Command

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

To configure the precedence levels for a VC or permanent virtual circuit (PVC) member of a bundle, use the precedence command in bundle-vc configuration mode for ATM VC bundle members. To remove the precedence levels from the VC or PVC, use the no form of the command.

precedence [other | range]
 
   
no precedence 

Syntax Description

other

(Optional) Any precedence levels in the range from 0 to 7 that are not explicitly configured.

range

(Optional) A single precedence level specified either as a number from 0 to 7 or as a range of precedence levels, specified as a hyphenated range.


precedence Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

Defaults to other—that is, any precedence levels in the range from 0 to 7 that are not explicitly configured.

Configuration Modes

VC-class configuration (for a VC class)

Bundle-vc configuration (for ATM VC bundle members)

Usage Guidelines for the precedence Command

Assignment of precedence levels to VC or PVC bundle members allows you to create differentiated service because you can distribute the IP precedence levels over the various VC/PVC bundle members. You can map a single precedence level or a range of levels to each discrete VC/PVC in the bundle, thereby enabling VCs/PVCs in the bundle to carry packets marked with different precedence levels. Alternatively, you can use the precedence other command to indicate that a VC/PVC can carry traffic marked with precedence levels not specifically configured for other VCs/PVCs. Only one VC/PVC in the bundle can be configured using the precedence other command. This VC/PVC is the default VC/PVC.

To use this command in vc-class configuration mode, first enter the vc-class atm command in global configuration mode. The precedence 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 the precedence command to configure an individual bundle member in bundle-VC configuration mode, first enter the bundle command to enter bundle configuration mode. Next, use the pvc-bundle command to add a PVC to the bundle as a member of the bundle 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):

VC configuration in bundle-vc mode

Bundle configuration in bundle mode (with effect of assigned vc-class configuration)

Subinterface configuration in subinterface mode

protect Command

To configure a virtual circuit (VC) class with protected group or protected VC status for application to a VC bundle member, use the protect command in vc-class configuration mode. To remove the protected status from the VC class, use the no form of the command.

To configure a specific VC or permanent virtual circuit (PVC) as part of a protected group of the bundle or to configure it as an individually protected VC or PVC bundle member, use the protect command in bundle-vc configuration mode. To remove the protected status from the VC or PVC, use the no form of the command.

protect {group | vc}
 
   
no protect {group | vc} 

Syntax Description

group

Configures the VC or PVC bundle member as part of the protected group of the bundle.

vc

Configures the VC or PVC member as individually protected.


protect Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

The VC or PVC neither belongs to the protected group nor is it an individually protected VC or PVC.

Configuration Modes

VC-class configuration (for a VC class)

Bundle-vc configuration (for ATM VC bundle members)

Usage Guidelines for the protect Command

Use the protect command in vc-class configuration mode to configure a VC class to contain protected group or individual protected VC status. When the class is applied to the VC bundle member, that VC is characterized by the protected status. You can also apply this command directly to a VC in bundle-vc configuration mode.

When a protected VC goes down, it takes the bundle down. When all members of a protected group go down, the bundle goes down.

To use the protect command in vc-class configuration mode, first enter the vc-class atm global configuration command.

The protect 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 the protect command in bundle-vc configuration mode, first enter the bundle command to enact bundle configuration mode for the bundle containing the VC member to be configured. Then enter the pvc-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 guidelines (listed in order of next highest precedence):

VC configuration in bundle-vc mode

Bundle configuration in bundle mode (with effect of assigned vc-class configuration)

Subinterface configuration in subinterface mode

pvc-bundle Command

To add a permanent virtual circuit (PVC) to a bundle as a member of the bundle and enter bundle-vc configuration mode in order to configure that PVC bundle member, use the pvc-bundle command in bundle configuration mode. To remove the VC from the bundle, use the no form of the command.

pvc-bundle pvc-name [vpi/] [vci]
 
   
no pvc-bundle pvc-name [vpi/] [vci] 

Syntax Description

pvc-name

The name of the permanent virtual circuit (PVC) bundle.

vpi/

(Optional) ATM network virtual path identifier (VPI) for this PVC. The absence of the "/" and a vpi value defaults the vpi value to 0.

The vpi and vci arguments cannot both be set to 0; if one is 0, the other cannot be 0.

vci

(Optional) ATM network virtual channel identifier (VCI) for this PVC. The value range is from 0 to 1 less than the maximum value set for this interface by the atm vc-per-vp command. Typically, lower values 0 to 31 are reserved for specific traffic (F4 Operation, Administration, and Maintenance (OAM), Integrated Local Management Interface (ILMI), and so on) and should not be used.

The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single link, not throughout the ATM network, because it has local significance only.

The vpi and vci arguments cannot both be set to 0; if one is 0, the other cannot be 0.


pvc-bundle Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

No default behavior or values.

Configuration Modes

Bundle configuration

Usage Guidelines for the pvc-bundle Command

Each bundle can contain multiple VCs having different QoS attributes. This command associates a VC with a bundle, making it a member of that bundle. Before you can add a VC to a bundle, the bundle must exist. Use the bundle command to create a bundle. You can also use this command to configure a VC that already belongs to a bundle. You enter the command in the same way, giving the name of the VC bundle member.

The pvc-bundle command enters bundle-vc configuration mode, in which you can specify VC-specific and VC class attributes for the VC.

ATM Bundle Management

ATM PVC bundle management software allows you to configure multiple PVCs that have different QoS characteristics between any pair of ATM-connected routers. As shown in Figure 19-2, these PVCs are grouped in a bundle and are referred to as bundle members.

Figure 19-2 ATM VC Bundle

ATM PVC bundle management allows you to define an ATM PVC bundle and add PVCs to it. Each PVC of a bundle has its own ATM traffic class and ATM traffic parameters. You can apply attributes and characteristics to discrete PVC bundle members or you can apply them collectively at the bundle level.

Using PVC bundles, you can create differentiated service by flexibly distributing IP precedence levels or Multiprotocol Label Switching (MPLS) experimental (EXP) levels over the different PVC bundle members. You can map a single level or a range of levels to each discrete PVC in the bundle, thereby enabling individual PVCs in the bundle to carry packets marked with different precedence or MPLS EXP levels. You can use weighted random early detection (WRED) to further differentiate service across traffic that has different IP precedence or MPLS EXP levels, but that uses the same PVC in a bundle.

To determine which PVC in the bundle to use to forward a packet to its destination, the ATM PVC bundle management software matches precedence levels or MPLS EXP levels between packets and PVCs (see Figure 19-3). IP traffic is sent to the next hop address for the bundle because all PVCs in a bundle share the same destination, but the PVC used to carry a packet depends on the value set for that packet in the IP precedence bits or the MPLS EXP bits of the type of service (ToS) byte of its header. The ATM PVC bundle management software matches the IP precedence or MPLS EXP level of the packet to the IP precedence or MPLS EXP value or range of values assigned to a PVC, sending the packet out on the appropriate VC.

The ATM PVC bundle management software also allows you to configure how traffic is redirected when the PVC the packet was matched to goes down. Figure 19-3 shows how the ATM PVC bundle management software determines which PVC bundle member to use to carry a packet and how WRED is used to differentiate traffic on the same VC. In the figure PVC selection is based on IP precedence levels, but it can also be based on MPLS EXP levels.

Figure 19-3 ATM PVC Selection

Bumping and ATM PVC Bundles

The ATM Operation, Administration, and Maintenance (OAM) polling mechanisms maintain the integrity of the PVCs in an ATM PVC bundle. These mechanisms determine whether a PVC is unavailable or severely congested. If an individual circuit become unavailable, then the device consults a preset series of rules to determine the course of action to take next. You configure specific parameters to define these rules.

Figure 19-4 conceptualizes a failed PVC bundle member whose failure calls into effect the configured bumping rules.

Figure 19-4 PVC Bundle Member Circuit Failure Enacting Bumping Rules

In the event of failure, the router responds with one of two methods:

The first method dynamically assigns the traffic bound on the failed PVC to an alternative PVC, which is referred to as circuit bumping. Bumped traffic is then shared on an existing in-service PVC. Although not required, traffic is typically bumped from a higher class to a lower one. For example, if the premium, or first class, data circuit become unavailable, then all premium users share the second class or general circuit. Within this shared circuit, preference is given to the premium traffic.

The second method is to declare all circuits of the bundle to be down. In effect, the device is declaring the routed bundle inactive and asking the routing layer to search for an alternate.

The network configuration determines whether to bump traffic or whether to declare the bundle inactive.

Prerequisites for ATM PVC Selection

The Cisco 10000 series router must be running Cisco IOS Release 12.0(26)S or later.

To implement ATM PVC bundles between two routers, you must enable IP Cisco Express Forwarding (CEF) switching on the routers.

Restrictions and Limitations for ATM PVC Selection

PVCs

In Cisco IOS Release 12.0(26)S, the ATM implementation of VC bundles is restricted to PVCs.

You can configure a maximum of 8 PVCs in one PVC bundle.

A PVC can be a member of one and only one PVC bundle.

A PVC that is a bundle member cannot be used in any other capacity. For example, you cannot configure a PVC bundle member in a map statement.

The Cisco 10000 router does not support automapping of PVCs or variable bit rate-real-time (VBR-rt) for PVCs.

The Cisco 10000 router supports aal5snap and aal5mux encapsulation types for PVCs and multipoint and point-to-point subinterfaces.

VC Selection

You can map one or multiple precedence or MPLS EXP levels to a single PVC; however, you cannot map multiple PVCs to one precedence or MPLS EXP level.

A PVC bundle does not come up until you configure all of the precedence or MPLS EXP levels in the bundle.

If you attach a VC class with bundle attributes to a PVC that is not configured as a member of a PVC bundle, the Cisco 10000 router ignores the bundle attributes.

ATM Inverse ARP

You can enable or disable inverse ARP for the PVC bundle but not for individual PVCs in the bundle.

ATM inverse ARP for IP uses the PVC configured with precedence level 6.

Inverse ARP for protocols other than IP (for example, IPX) is disabled by default unless you explicitly configure it in the PVC bundle.

Packet Forwarding

The Cisco 10000 router does not support fast switching of IP packets.

Configuring ATM Bundles

You can configure ATM bundles either directly or by associating a VC class with the bundle.

To configure ATM bundles, perform the following configuration tasks:

Creating an ATM Bundle Directly

Creating an ATM Bundle Using a VC Class

Adding an ATM PVC to a PVC Bundle

Creating an ATM Bundle Directly

The router applies the parameters you configure in ATM bundle configuration mode to the PVC bundle and to all of the bundle members. These parameters supersede the parameters that you apply by associating a VC class with the bundle. Parameters that you apply to an individual PVC supersede the parameters that you apply to the bundle.

To create a PVC bundle directly, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface atm slot/module/port[.subinterface]

Creates or modifies an interface or subinterface. Enters interface or subinterface configuration mode.

Step 2 

Router(config-subif)# mpls ip

(Optional) Enables MPLS forwarding of IPv4 packets along normally routed paths. You must configure this command if you configure MPLS EXP-based PVC selection.

Step 3 

Router(config-subif)# bundle bundle-name

Creates or modifies the PVC bundle and enters ATM bundle configuration mode.

bundle-name is the name of the bundle.

Step 4 

Router(config-atm-vcb)# protocol protocol {protocol-address | inarp} [[no] broadcast]

Configures a static map for an ATM PVC or VC class, or enables Inverse Address Resolution Protocol (ARP) or Inverse ARP broadcasts on an ATM PVC.

protocol is the protocol carried on the VC (for example, ip).

protocol-address is the destination address that is being mapped to a PVC.

(Valid only for IP and IPX protocols on PVCs) inarp enables Inverse ARP on an ATM PVC. If you specify a protocol-address instead of inarp, Inverse ARP is automatically disabled for that protocol.

(Optional) [no] broadcast indicates that this map entry is used when the corresponding protocol sends broadcast packets to the interface. Pseudobroadcasting is supported. The broadcast keyword of the protocol command takes precedence if you previously configured the broadcast command on the ATM PVC.

Step 5 

Router(config-atm-vcb)# encapsulation [aal5snap | aal5mux ip]

Configures the ATM adaptation layer (AAL) and encapsulation type for the bundle.

Step 6 

Router(config-atm-vcb)# encapsulation {aal5mux protocol | aal5ciscoppp virtual-template number | aal5snap}

Configures the ATM adaptation layer (AAL) and encapsulation type for an ATM virtual circuit (VC).

aal5mux is the AAL and encapsulation type for multiplex (MUX)-type VCs. You must specify a protocol when using this encapsulation type.

protocol is the protocol type being used by the MUX-encapsulated VC.

aal5ciscoppp specifies the AAL and encapsulation type for Cisco PPP over ATM. Supported on ATM PVCs only.

virtual-template number is the number used to identify the virtual template.

aal5snap specifies the AAL and encapsulation type that supports Inverse ARP. Logical Link Control/Subnetwork Access Protocol (LLC/SNAP) precedes the protocol datagram.

Step 7 

Router(config-atm-vcb)# class class_name

(Optional) Attaches a VC class to the bundle.

class_name is the name of the VC class.

Step 8 

Router(config-atm-vcb)# inarp [minutes]

Configures the Inverse Address Resolution Protocol (ARP) time period for an ATM PVC, VC class, or VC bundle.

minutes is the number of minutes for the Inverse ARP time period.

Step 9 

Router(config-atm-vcb)# broadcast

Enables broadcast forwarding for all VC bundle members.

Step 10 

Router(config-atm-vcb)# oam retry up-count down-count retry-frequency

Configures parameters related to Operation, Administration, and Maintenance (OAM) management for each PVC in the bundle.

up-count is the number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to change a PVC connection state to up.

down-count is the number of consecutive end-to-end F5 OAM loopback cell responses that are not received in order to change a PVC state to down.

retry-frequency is the frequency (in seconds) that end-to-end F5 OAM loopback cells are transmitted when a change in the up/down state of a PVC is being verified. For example, if a PVC is up and a loopback cell response is not received after specifying retry-frequency, then loopback cells are sent at the retry-frequency to verify whether the PVC is down.

Step 11 

Router(config-atm-vcb)# oam-bundle [manage] [frequency]

Enables end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for all bundle members or a VC class that can be applied to a VC bundle

(Optional) manage enables OAM management. If you omit this keyword, loopback cells are sent, but the bundle is not managed.

(Optional) frequency is the number of seconds between transmitted OAM loopback cells. Valid values are from 0 to 600 seconds. The default is 10 seconds.

Step 12 

Router(config-atm-vcb)# ubr [pcr]

Configures unspecified bit rate (UBR) as the traffic shaping rule.

(Optional) pcr is the peak cell rate.

Step 13 

Router(config-atm-vcb)# ubr+ pcr [mcr]

Configures UBR plus (UBR+) as the traffic shaping rule.

pcr is the peak cell rate.

(Optional) mcr is the minimum cell rate.

Step 14 

Router(config-atm-vcb)# vbr-nrt pcr scr [mbs]

Configures variable bit rate-nonreal-time (VBR-nrt) as the traffic shaping rule.

pcr is the peak cell rate.

scr is the sustained cell rate.

(Optional) mbs is the maximum burst size.

Creating an ATM Bundle Using a VC Class

You can use a VC class to configure an ATM PVC bundle. The VC class contains multiple configuration parameters, including the method used for PVC selection. When you apply the VC class to the bundle, the VC class parameters apply to all of the members of a bundle.

The parameters that you apply manually to the PVC bundle supersede the parameters that you apply by associating a VC class with the bundle. Parameters that you apply to an individual PVC supersede the parameters that you apply to a bundle.

To create an ATM bundle using a VC class, perform the following configuration tasks:

Configuring a VC Class and Specifying the Basis for PVC Selection

Attaching a VC Class to an ATM Bundle

Configuring a VC Class and Specifying the Basis for PVC Selection

To configure a VC class and specify the basis for PVC selection, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# vc-class atm name

Creates or modifies a VC class and enters VC class configuration mode.

name is the name of the VC class.

Step 2 

Router(config-vc-c)# oam-bundle [manage] [frequency]

Enables end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for a VC class that can be applied to a VC bundle.

(Optional) manage enables OAM management. If you omit this keyword, loopback cells are sent, but the bundle is not managed.

(Optional) frequency is the number of seconds between transmitted OAM loopback cells. Valid values are from 0 to 600 seconds. The default is 10 seconds.

Step 3 

Router(config-vc-c)# mpls experimental [other | range]

(Optional) Configures Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a VC class that can be assigned to a VC bundle and thus applied to all VC members of that bundle. This command configures MPLS EXP-based PVC selection.

(Optional) other specifies any MPLS EXP levels that are not explicitly configured. This is the default setting.

(Optional) range specifies a single MPLS EXP level (2), or a range of levels (1-3). Valid values are from 0 to 7.

Step 4 

Router(config-vc-c)# precedence {level | other}

(Optional) Configures the precedence levels for a bundle member. This command configures precedence-based PVC selection.

level specifies the precedence level or levels for this bundle member. Valid values are from 0 to 7.

You can configure a PVC bundle member with a single precedence level (0), multiple individual precedence levels (0,2,3), a range of precedence levels (0-2), multiple ranges of precedence levels (0-2,4-5), or a combination of individual levels and level ranges (0,1,2-4,7).

Note This command is available when the PVC bundle match type is set to precedence.

other specifies that this bundle member handles all of the remaining precedence levels that are not explicitly configured on any other bundle members.

Note Critical non-IP traffic automatically uses precedence level 0.

Step 5 

Router(config-vc-c)# bump {explicit precedence-level | implicit | traffic}

(Optional) Configures the bumping rules for a VC class that can be assigned to a VC bundle or configures the bumping rules for a specific VC or PVC member of a bundle. The default is implicit bumping.

explicit precedence-level specifies the precedence level to which traffic on a VC or PVC is bumped when the VC or PVC goes down. Valid values are from 0 to 7.

implicit applies the implicit bumping rule, which is the default, to a single VC or PVC bundle member, or to all VCs in the bundle (VC-class mode). The implicit bumping rule stipulates that bumped traffic is to be carried by a VC or PVC with a lower precedence level.

traffic specifies that the VC or PVC accepts bumped traffic. By default, a PVC permits bumping and accepts bumped traffic.

Note To configure a PVC to reject bumped traffic from another bundle member, enter the no bump traffic command.

Step 6 

Router(config-vc-c)# protect {group | vc}

(Optional) Configures a specific VC or permanent virtual circuit (PVC) as part of a protected group of the bundle or configures it as an individually protected VC or PVC bundle member. By default, the PVC bundle member is not protected.

group configures the VC or PVC bundle member as part of the protected group of the bundle and specifies that the bundle goes down when the last PVC in the protected group goes down.

vc configures the bundle member as individually protected and specifies that the bundle goes down whenever the PVC goes down.

Attaching a VC Class to an ATM Bundle

To attach a VC class to an ATM bundle, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface atm slot/module/port.subinterface

Creates or modifies a subinterface. Enters subinterface configuration mode.

Step 2 

Router(config-subif)# bundle bundle-name

Activates the PVC bundle and enters ATM bundle configuration mode.

bundle-name is the name of the bundle to which you want to attach the VC class.

Step 3 

Router(config-atm-vcb)# class-bundle vc-class-name

Associates the VC class you specify with the PVC bundle. The router applies the parameters specified in the VC class to the bundle.

vc-class-name is the name of the VC class that you are attaching to the VC bundle.

Adding an ATM PVC to a PVC Bundle

To add an ATM PVC to a PVC bundle, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface atm slot/module/port.subinterface

Creates or modifies a subinterface. Enters subinterface configuration mode.

Step 2 

Router(config-subif)# bundle bundle-name

Creates or modifies the PVC bundle. Enters ATM bundle configuration mode.

bundle-name is the name of the bundle to which you want to add a PVC.

Step 3 

Router(config-atm-vcb)# pvc-bundle pvc_name [vpi/]{vci}

Adds the specified PVC to the bundle. Enters ATM bundle member configuration mode.

pvc-name is a name that you can use to refer to the PVC.

Configuring ATM Bundle Members

You can configure PVC bundle members manually or by associating VC classes to the bundle members.

The parameter values that you configure manually for an individual PVC supersede the parameter values applied to the ATM bundle. The parameter values that you configure manually for a PVC take precedence over the parameters applied using a VC class.

To configure ATM bundle members, perform the following configuration tasks:

Configuring an ATM Bundle Member

Configuring an ATM Bundle Member Using a VC Class

Configuring a PVC Not to Accept Bumped Traffic

Configuring an ATM Bundle Member

The parameter values that you configure manually for a PVC in ATM bundle member configuration mode take precedence over the values of these parameters that you set for the PVC in any other configuration mode, including a VC class applied in the ATM bundle member configuration mode.

To configure an ATM bundle member, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface atm slot/module/port.subinterface

Creates or modifies a subinterface. Enters subinterface configuration mode.

Step 2 

Router(config-subif)# bundle bundle-name

Creates or modifies the PVC bundle and enters ATM bundle configuration mode.

bundle-name is the name of the bundle.

Step 3 

Router(config-atm-vcb)# pvc-bundle pvc_name [vpi/]{vci}

Adds the specified VC to the bundle if it does not exist already and enters ATM bundle VC configuration mode.

pvc-name is a name that you can use to refer to the PVC.

vpi/ is the virtual path identifier (VPI). The slash is required.

vci is the virtual channel identifier (VCI).

Step 4 

Router(config-atm-vcb-vc)# bump {explicit level | implicit | traffic}

(Optional) Configures the bumping rules for the bundle member. The default is implicit bumping.

explicit level specifies the precedence, experimental (EXP), or differentiated services code point (DSCP) level to which traffic on the PVC is bumped if the PVC goes down. You can specify only one service level for bumping. For PVC bundles that use precedence or EXP mapping, valid values for level are from 0 to 7. For PVC bundles that use DSCP mapping, valid values are from 0 to 63.

Note When the PVC goes down, the router directs the traffic to a PVC mapped with the service level you configure in explicit level.

implicit applies the implicit bumping rule, which is the default, to a single bundle member. The implicit bumping rule stipulates that bumped traffic is to be carried by a PVC that has the lower precedence level.

traffic specifies that the PVC accepts bumped traffic. By default, a PVC accepts bumped traffic.

Note To configure a PVC to reject bumped traffic from another bundle member, enter the no bump traffic command.

Step 5 

Router(config-atm-vcb-vc)# mpls experimental [other | range]

(Optional) Configures Multiprotocol Label Switching (MPLS) experimental (EXP) levels for the bundle member. This command configures MPLS EXP-based PVC selection.

(Optional) other specifies any MPLS EXP levels that are not explicitly configured. This is the default setting.

(Optional) range specifies a single MPLS EXP level (2) or a range of levels (1-3). Valid values are from 0 to 7.

Step 6 

Router(config-atm-vcb-vc)# precedence [other | range]

(Optional) Configures the precedence levels for the VC bundle member. This command configures precedence-based PVC selection.

(Optional) other specifies any precedence levels that are not explicitly configured. Valid values are 0 to 7.

(Optional) range specifies a single precedence level. Valid values are from 0 to 7, specified either as a single number (3) or a range of precedence levels (2-4).

Step 7 

Router(config-atm-vcb-vc)# class class-name

Attaches a VC class to the PVC bundle member.

class-name is the name of the VC class.

Step 8 

Router(config-atm-vcb-vc)# protect {group | vc}

Configures the bundle member as part of the protected group of a bundle or as an individually protected VC in a bundle.

group configures the VC or PVC bundle member as part of the protected group of the bundle.

vc configures the VC or PVC member as individually protected.

Step 9 

Router(config-atm-vcb-vc)# ubr [pcr]

(Optional) Configures unspecified bit rate (UBR) as the traffic shaping rule for the VC.

(Optional) pcr is the peak cell rate (PCR).

Step 10 

Router(config-atm-vcb-vc)# ubr+ pcr [mcr]

(Optional) Configures UBR plus (UBR+) as the traffic shaping rule.

pcr is the peak cell rate (PCR)

(Optional) mcr is the minimum cell rate (MCR).

Step 11 

Router(config-atm-vcb-vc)# vbr-nrt pcr scr [mbs]

(Optional) Configures variable bit rate-nonreal-time (VBR-nrt) as the traffic shaping rule.

pcr is the peak cell rate (PCR).

scr is the sustaining cell rate (SCR).

(Optional) mbs is the maximum burst size (MBS).

Configuring an ATM Bundle Member Using a VC Class

To configure an ATM bundle member using a VC class, perform the following configuration tasks:

Configuring an ATM VC Class

Attaching a VC Class to an ATM Bundle Member

Configuring an ATM VC Class

To configure an ATM VC class and specify the basis for ATM PVC selection, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# vc-class atm name

Creates or modifies a VC class and enters VC class configuration mode.

name is the name of the VC class.

Step 2 

Router(config-vc-c)# oam-bundle [manage] [frequency]

Enables end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for a VC class that can be applied to a VC bundle.

(Optional) manage enables OAM management. If you omit this keyword, loopback cells are sent, but the bundle is not managed.

(Optional) frequency is the number of seconds between transmitted OAM loopback cells. Valid values are from 0 to 600 seconds. The default is 10 seconds.

Step 3 

Router(config-vc-c)# bump {explicit precedence-level | implicit | traffic}

(Optional) Configures the bumping rules for a VC class that can be assigned to a VC bundle or configures the bumping rules for a specific VC or PVC member of a bundle. The default is implicit bumping.

explicit precedence-level specifies the precedence level to which traffic on a VC or PVC is bumped when the VC or PVC goes down. Valid values are from 0 to 7.

implicit applies the implicit bumping rule, which is the default, to a single VC or PVC bundle member, or to all VCs in the bundle (VC-class mode). The implicit bumping rule stipulates that bumped traffic is to be carried by a VC or PVC with a lower precedence level.

traffic specifies that the VC or PVC accepts bumped traffic. By default, a PVC permits bumping and accepts bumped traffic.

Note To configure a PVC to reject bumped traffic from another bundle member, enter the no bump traffic command.

Step 4 

Router(config-vc-c)# protect {group | vc}

(Optional) Configures a specific VC or permanent virtual circuit (PVC) as part of a protected group of the bundle or configures it as an individually protected VC or PVC bundle member. By default, the PVC bundle member is not protected.

group configures the VC or PVC bundle member as part of the protected group of the bundle and specifies that the bundle goes down when the last PVC in the protected group goes down.

vc configures the bundle member as individually protected and specifies that the bundle goes down whenever the PVC goes down.

Step 5 

Router(config-vc-c)# mpls experimental [other | range]

(Optional) Configures Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a bundle member. This command configures MPLS EXP-based PVC selection.

(Optional) other specifies any MPLS EXP levels that are not explicitly configured. This is the default setting.

(Optional) range specifies a single MPLS EXP level (2) or a range of levels (1-3). Valid values are from 0 to 7.

Step 6 

Router(config-vc-c)# precedence [other | range]

(Optional) Configures the precedence levels for a VC bundle member. This command configures precedence-based PVC selection.

(Optional) other specifies any precedence levels that are not explicitly configured. Valid values are 0 to 7.

(Optional) range specifies a single precedence level. Valid values are from 0 to 7, specified either as a single number (3) or a range of precedence levels (2-4).

Step 7 

Router(config-vc-c)# ubr [pcr]

Configures unspecified bit rate (UBR) as the traffic shaping rule.

(Optional) pcr is the peak cell rate.

Step 8 

Router(config-vc-c)# ubr+ pcr [mcr]

Configures UBR plus (UBR+) as the traffic shaping rule.

pcr is the peak cell rate.

(Optional) mcr is the minimum cell rate.

Step 9 

Router(config-vc-c)# vbr-nrt pcr scr [mbs]

Configures variable bit rate-nonreal-time (VBR-nrt) as the traffic shaping rule.

pcr is the peak cell rate.

scr is the sustained cell rate.

(Optional) mbs is the maximum burst size.

Attaching a VC Class to an ATM Bundle Member

The parameters that you configure manually for a PVC in ATM bundle configuration mode supersede the parameters applied to the PVC using a VC class.

To attach a VC class to a bundle member, enter the following commands beginning in subinterface configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface atm slot/module/port.subinterface

Creates or modifies a subinterface. Enters subinterface configuration mode.

Step 1 

Router(config-subif)# bundle bundle-name

Creates or modifies the PVC bundle. Enters ATM bundle configuration mode.

bundle-name is the name of the bundle to which you want to attach the VC class.

Step 2 

Router(config-atm-vcb)# pvc-bundle pvc_name [vpi/]{vci}

Adds the specified PVC to the bundle if it does not exist already. Enters ATM bundle member configuration mode.

pvc-name is a name that you can use to refer to the PVC.

(Optional) vpi/ is the virtual path identifier (VPI). The slash is required.

(Optional) vci is the virtual channel identifier.

Step 3 

Router(config-atm-vcb-vc)# class-vc vc-class-name

Assigns a VC class to a PVC bundle member.

vc-class-name is the name of the VC class.

Configuring a PVC Not to Accept Bumped Traffic

To configure an individual PVC bundle member not to accept traffic that the router forwards to it when the original PVC carrying the traffic goes down, enter the following command in PVC bundle member configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface atm slot/module/port.subinterface

Creates or modifies a subinterface. Enters subinterface configuration mode.

Step 2 

Router(config-subif)# bundle bundle-name

Creates or modifies the PVC bundle. Enters ATM bundle configuration mode.

bundle-name is the name of the bundle to which you want to attach the VC class.

Step 3 

Router(config-atm-vcb)# pvc-bundle pvc_name [vpi/]{vci}

Adds the specified PVC to the bundle if it does not exist already. Enters ATM bundle member configuration mode.

pvc-name is a name that you can use to refer to the PVC.

(Optional) vpi/ is the virtual path identifier (VPI). The slash is required.

(Optional) vci is the virtual channel identifier.

Step 4 

Router(config-atm-vcb-vc)# no bump traffic

Configures the PVC not to accept any bumped traffic that would otherwise be redirected to it.

Verifying and Monitoring ATM PVC Bundles

To verify and monitor QoS for ATM PVC bundles, enter any of the following commands in privileged EXEC configuration mode:

Command
Purpose

Router# debug atm bundle adjacency events

Displays information about ATM bundle adjacency change events.

Router# debug atm bundle errors

Displays information about bundle errors.

Router# debug atm bundle events

Displays a record of bundle events.

Router# show atm bundle bundle-name

Displays the bundle attributes assigned to each PVC bundle member and the current working status of the PVC bundle members.

bundle-name is the name of the bundle whose member information is displayed. This is the bundle name specified by the bundle command when the bundle was created.

Router# show atm bundle bundle-name statistics [detail]

Displays statistics or detailed statistics about the specified VC bundle.

bundle-name specifies the name of the bundle whose member information is displayed. This is the bundle name specified by the bundle command when the bundle was created.

(Optional) detail displays detailed statistics.

Router# show atm map

Displays a list of all configured ATM static maps to remote hosts on an ATM network and on ATM bundle maps.

Router# show atm pvc [vpi/vci | name | interface atm interface-number] [ppp]

Displays all of the ATM PVCs and traffic information.

(Optional) vpi/vci are the ATM virtual path identifier (VPI) and virtual channel identifier (VCI) numbers. If you do not specify a value for vpi, the vpi value defaults to 0. The slash is required.

(Optional) name is the name of the PVC.

(Optional) interface-number displays all PVCs on the specified ATM interface.

(Optional) ppp displays each PVC configured for PPP over ATM.

Router# show atm vc [vcd] [interface interface-number]

Displays all ATM permanent virtual circuits (PVCs) and traffic information.

(Optional) vcd specifies which virtual circuit about which to display information.

(Optional) interface-number is the interface number or subinterface number of the PVC. Displays all PVCs on the specified interface or subinterface.


Configuration Examples for Configuring ATM Bundles and PVC Selection

This section provides the following configuration examples:

Configuration Example for ATM Bundle Configuration Using VC Classes

Configuration Example for MPLS EXP-Based ATM PVC Selection

Configuration Example for ATM Bundle Configuration Using VC Classes

Example 19-1 shows how to configure ATM bundles using VC classes. The sample configuration defines five VC classes: bundle-class, control-class, premium-class, priority-class, and basic-class. The VC class named bundle-class defines the parameters applicable to every VC in a bundle. The sample configuration also creates three bundles to which the VC classes are applied: new-york, san-francisco, and los-angeles.

Example 19-1 Configuring ATM Bundles Using VC Classes

/* This router uses IS-IS as the IP routing protocol. */
router isis
	net 49.0000.0000.0000.1111.00
 
   
/* The bundle-class defines the parameters applicable to every VC in a bundle. Any bundle 
that uses this class has aal5snap encapsulation, broadcast enabled, uses Inverse ARP to 
resolve IP addresses, and OAM enabled at the bundle class level in the inheritance 
chain.*/
vc-class atm bundle-class
	encapsulation aal5snap
	broadcast
	protocol ip inarp
	oam-bundle manage 3
	oam 4 3 10
 
   
/* The following VC classes define the parameters applicable to individual VCs in a 
bundle. */
 
   
/* The control-class carries precedence 7 traffic and takes the bundle down when it is 
down. It uses the implicit bumping rule. The QoS is set to vbr-nrt. */
vc-class atm control-class
	precedence 7
	protect vc
	vbr-nrt 10000 5000 32
 
   
/* The premium-class carries precedence 5 and 6 traffic, and does not allow other traffic 
to be bumped onto it. The precedence 7 VC is the alternate VC for the premium-class 
traffic when it does down. The premium-class belongs to the protected group of the bundle. 
The QoS type is vbr-nrt. */
vc-class atm premium-class
	precedence 6-5
	no bump traffic
	protect group
	bump explicitly 7
	vbr-nrt 20000 10000 32
 
   
/* The priority-class carries precedence 4-2 traffic and uses the implicit bumping rule. 
It allows bumped traffic and belongs to the protected group of the bundle. The QoS type is 
ubr+. */
vc-class atm priority-class
	precedence 4-2
	protect group
	ubr+ 10000 3000
 
   
/* The basic-class carries the traffic of the precedence levels that are not specified in 
the profile. It is part of the protected group. The QoS type is ubr. */
vc-class atm basic-class
	precedence other
	protect group
	ubr 10000
 
   
/* This subinterface has 3 bundles for connecting to its 3 neighbors. Bundle new-york and 
bundle san-francisco have 4 members and bundle los-angeles has 3 members. */
interface a1/0.1 multipoint
	ip address 10.16.0.1 255.255.255.0
	ip router isis
	bundle new-york
 
   
/* The following protocol commands enable IP and OSI traffic flows in the bundle. 
According to the inheritance rule, the protocol ip command takes precedence over the 
protocol ip inarp command in bundle-class. The protocol clns command is configured merely 
for using it for integrated IP routing. The OSI routing packets go on the highest 
precedence VC in the bundle while the OSI data packets, if any, use the lowest precedence 
VC in the bundle. Other protocols, such as IPX or AppleTalk, always use the lowest 
precedence VC in the bundle when they are configured. */
protocol ip 10.16.1.2 broadcast
protocol clns 49.0000.0000.0000.2222.00 broadcast
class bundle-class
 
   
/* The following commands create the PVCs of bundle new-york. */
pvc-bundle ny-control 207
	class control-class
pvc-bundle ny-premium 206
	class premium-class
pvc-bundle ny-priority 204
	class priority-class
pvc-bundle ny-basic 201
	class basic-class
 
   
bundle san-francisco
	protocol clns 40.0000.0000.0000.3333.00 broadcast
	inarp 1
	class bundle-class
	pvc-bundle sf-control 307
		class control-class
	pvc-bundle sf-premium 306
		class premium-class
	pvc-bundle sf-priority 304
		class priority-class
	pvc-bundle sf-basic 301
		class basic-class
 
   
bundle los-angeles
	protocol ip 10.16.1.4 broadcast
	protocol clns 49.0000.0000.0000.4444.000 broadcast
	inarp 1
	class bundle-class
	pvc-bundle la-high 407
		precedence 7-5
		protect vc
		class premium-class
	pvc-bundle la-mid 404
		precedence 4-2
		protect group
		class priority-class
	pvc-bundle la-low 401
		precedence other
		protect group
		class basic-class
 
   
/* PVC la-other is a standalone VC and does not belong to any of the bundles. */
pvc la-other 400
	no protocol ip inarp
	broadcast

Configuration Example for MPLS EXP-Based ATM PVC Selection

Example 19-2 shows how to configure MPLS experimental (EXP)-based ATM PVC selection. The sample configuration adds PVCs 0/306, 0/304, and 0/301 to the ATM PVC bundle named router2 and specifies the MPLS experimental bit values to map to each of the PVC bundle members.

Example 19-2 Configuring MPLS EXP-Based ATM PVC Selection

interface ATM1/0/0 point-to-point
	mpls label protocol ldp
	tag-switching ip
	bundle router2
		pvc-bundle atm-premium 0/306
			mpls experimental 5-7
		pvc-bundle atm-priority 0/304
			mpls experimental 3-4
		pvc-bundle atm-basic 0/301
			mpls experimental other

Frame Relay PVC Selection

The Cisco 10000 router can forward packets to Frame Relay bundle members based on the IP precedence level, differentiated services code point (DSCP) level, or the Multiprotocol Label Switching (MPLS) experimental (EXP) level of the packets.

The Frame Relay PVC Bundles with QoS Support for IP and MPLS feature allows you to configure multiple PVCs with different QoS characteristics between any pair of Frame Relay-connected routers and to configure a group of Frame Relay PVCs with a single next-hop address. Packets are mapped to specific PVCs in the bundle on the basis of the precedence level, differentiated services code point (DSCP) level, or MPLS EXP level in the type of service (ToS) field of the IP header. Each packet is treated differently according to the QoS configured for each PVC.

The Frame Relay PVC bundle management software provides flexible PVC management within a PVC bundle by allowing traffic assigned to a failed PVC to be redirected to an alternate PVC within the bundle. It also allows you to configure the bundle to go down when certain PVCs go down. IP packets carrying different types of traffic can be transported on different PVCs within the same PVC bundle.

To determine which PVC in a bundle is used to forward a specific type of traffic, the Frame Relay PVC bundle management software matches the IP precedence level, DSCP level, or MPLS EXP level in the IPv4 header to a PVC configured with the same value. The bundle management software sends the packet out on the PVC with the same value.

After you define a Frame Relay bundle and add PVCs to it, you can configure attributes and characteristics to discrete PVC bundle members, or you can apply them collectively at the bundle level. You can apply Frame Relay traffic shaping to each PVC within a bundle.

You can create differentiated service using PVC bundles by distributing IP precedence levels or DSCP values over the various bundle members. You can map a single precedence level or DSCP value or a range of precedence or DSCP levels to each PVC in the bundle. This enables you to either limit an individual PVC to carry only packets marked with a specific precedence or DSCP level, or enable a PVC to carry packets marked with different precedence or DSCP levels.

The bundle management software also allows you to configure how traffic is redirected if a PVC goes down. If this occurs, the router attempts to identify an alternate PVC. If the router cannot locate an alternate PVC, the router stops the PVC bundle.

The router forwards non-IP packets using the PVC that is responsible for carrying precedence level 6 or DSCP level 63 traffic. The router uses process-switching to forward locally generated packets.

Feature History for Frame Relay PVC Selection

Cisco IOS Release
Description
Required PRE

Release 12.0(26)S

The Frame Relay PVC Bundles with QoS Support for IP and MPLS feature was introduced on the PRE1.

PRE1


Configuration Commands for Frame Relay PVC Selection

This section describes the following configuration commands:

bump Command (Frame Relay VC-bundle-member)

dscp Command (Frame Relay VC-bundle-member)

exp Command

frame-relay vc-bundle Command

precedence Command (Frame Relay VC-bundle-member)

protect Command (Frame Relay VC-bundle-member)

pvc Command (Frame Relay VC-bundle)

bump Command (Frame Relay VC-bundle-member)

To configure the bumping rules for a Frame Relay permanent virtual circuit (PVC) bundle member, use the bump command in Frame Relay VC-bundle-member configuration mode.To specify that the PVC bundle member does not accept any bumped traffic, use the no bump traffic command. (The no bump explicit and no bump implicit commands have no effect.)

bump {explicit level | implicit | traffic}
 
   
no bump traffic 

Syntax Description

explicit level

Specifies the precedence, MPLS experimental (EXP), or differentiated services code point (DSCP) level to which traffic on a PVC is bumped when the PVC goes down. For PVC bundles that use precedence or MPLS EXP mapping, valid values for the level argument are from 0 to 7. For PVC bundles that use DSCP mapping, valid values are from 0 to 63.

implicit

Applies the implicit bumping rule, which is the default, to a single PVC bundle member. The implicit bumping rule stipulates that bumped traffic is to be carried by a PVC that has the lower precedence level.

traffic

Specifies that the PVC accepts bumped traffic (the default condition). The no form stipulates that the PVC does not accept any bumped traffic.


bump Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

Implicit bumping

Bumping permitted (PVCs accept bumped traffic)

Configuration Mode

Frame Relay VC-bundle-member configuration

Usage Guidelines for the bump Command

Use the bump command to configure bumping rules for a discrete PVC bundle member. To change the configured bumping rules for a PVC bundle member, override the current configuration with a new bump command entry.

To return to the default condition of implicit bumping, use the bump implicit command.

If you configure implicit bumping, bumped traffic is sent to the PVC configured to handle the next lower service level. When the original PVC that bumped the traffic comes back up, it resumes transmission of the configured service level. When the bump explicit command is not configured, the bump implicit command takes effect by default; however, the bump implicit command does not appear in the output of the show running-config and show startup-config commands.

If you configure a PVC with the bump explicit command, you can specify the service level to which traffic is bumped when that PVC goes down, and the traffic is directed to a PVC mapped with that level. If the PVC that picks up and carries the traffic goes down, the traffic is subject to the bumping rules for that PVC. You can specify only one service level for bumping.

The PVC accepts bumped traffic by default. If the PVC has been previously configured to reject bumped traffic, you must use the bump traffic command to return the PVC to its default condition.

To configure a discrete PVC to reject bumped traffic when the traffic is directed to it, use the no bump traffic command.


Note When no alternative PVC can be found to handle bumped traffic, even when there are no packets of that traffic type present, the bundle is declared down. In the case where default (implicit) bumping is used for all PVCs, the PVC that is handling the lowest service level can be configured to bump explicitly to a PVC handling a higher service level.


dscp Command (Frame Relay VC-bundle-member)

To configure the differentiated services code point (DSCP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the dscp command in Frame Relay VC-bundle-member configuration mode. To remove the DSCP level configuration from the PVC, use the no form of the command.

dscp {level | other}
 
   
no dscp level 

Syntax Description

level

Specifies the DSCP level or levels for this Frame Relay PVC bundle member. Valid values are from 0 to 63.

You can configure a PVC bundle member with a single DSCP level (9), multiple individual DSCP levels (25,35,45), a range of DSCP levels (25-35), multiple ranges of DSCP levels (25-35,45-55), or a combination of individual levels and level ranges (10,20,25-35,40,45-55,60).

Note This command is available when the PVC bundle match type is set to dscp. By default, the PVC members are configured to reject bumping when the match-type is dscp.

other

Specifies that this Frame Relay PVC bundle member handles all of the remaining DSCP levels that are not explicitly configured on any other bundle members.


dscp Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

DSCP levels are not configured.

Configuration Mode

Frame Relay VC-bundle-member configuration

Usage Guidelines for the dscp Command

Assignment of DSCP levels to PVC bundle members allows you to create differentiated service because you can distribute the DSCP levels over the various PVC bundle members. You can map a single DSCP level or range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different DSCP levels. Use the dscp other command to configure a PVC to carry traffic marked with DSCP levels not specifically configured on other PVCs. Only one PVC in the bundle can be configured with the dscp other command.

This command is available only when the match type for the PVC bundle is set to dscp using the match dscp command in Frame Relay VC-bundle configuration mode.

You can overwrite the DSCP level configuration on a PVC by re-entering the dscp command with a new level value.

There is no default value for this command.

When the PVC bundle is set to dscp using the match dscp command, all PVCs in the bundle are reset to remove any existing DSCP values. If one or more DSCP values are not specifically configured, the bundle does not come up.

Note, however, that a PVC may exist in a bundle but have no DSCP value associated with it. As long as all valid DSCP values are handled by one or more of the other PVCs in the bundle, the bundle can come up, but the PVC that has no DSCP value configured does not participate in it.

A DSCP level can be configured on one PVC-bundle member per bundle. If you configure the same DSCP level on more than one PVC within a bundle, the following message appears on the console:

%Overlapping diff-serv code points

exp Command

To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the exp command in Frame Relay VC-bundle-member configuration mode. To remove the EXP level configuration from the PVC, use the no form of the command.

exp {level | other}
 
   
no exp 

Syntax Description

level

Specifies the MPLS EXP level or levels for a Frame Relay PVC bundle member. Valid values are from 0 to 7. You can configure a PVC bundle member with a single MPLS EXP level (0), multiple individual MPLS EXP levels (0,2,3), a range of MPLS EXP levels (0-2), multiple ranges of MPLS EXP levels (0-2,4-5), or a combination of individual levels and level ranges (0,1,2-4,7).

other

Specifies that the Frame Relay PVC bundle member handles all of the remaining MPLS EXP levels that are not explicitly configured on any other bundle member PVCs.


exp Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

EXP levels are not configured.

Configuration Mode

Frame-Relay VC-bundle-member configuration

Usage Guidelines for the exp Command

Assignment of MPLS EXP levels to Frame Relay PVC bundle members allows you to create differentiated service because you can distribute the levels over the various PVC bundle members. You can map a single level or a range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different levels. Use the exp other command to indicate that a PVC can carry traffic marked with EXP levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the exp other command.

All MPLS EXP levels must be accounted for in the PVC bundle configuration, or the bundle does not come up. Note, however, that a PVC may be a bundle member but have no MPLS EXP level associated with it. As long as all valid MPLS EXP levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no MPLS EXP level configured does not participate in it.

The exp command is available only when tag-switching is configured on the interface with the tag-switching ip command.

You can overwrite the EXP level configuration on a PVC by re-entering the exp command with a new value.

The MPLS experimental bits are a bit-by-bit copy of the IP precedence bits. When Frame Relay PVC bundles are configured for IP precedence and tag-switching is enabled, the precedence command is replaced by the exp command. When tag-switching is disabled, the exp command is replaced by the precedence command.

frame-relay vc-bundle Command

To create a Frame Relay permanent virtual circuit (PVC) bundle if it does not already exist, and to enter Frame Relay VC-bundle configuration mode, use the frame-relay vc-bundle command in interface configuration mode. To remove a Frame Relay PVC bundle, use the no form of the command.

frame-relay vc-bundle vc-bundle-name
 
   
no frame-relay vc-bundle vc-bundle-name 

Syntax Description

vc-bundle-name

User-defined name of this Frame Relay PVC bundle.


frame-relay vc-bundle Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

A bundle is not created.

Configuration Mode

Interface configuration

Usage Guidelines for the frame-relay vc-bundle Command

Use this command to create a unique Frame Relay PVC bundle if one has not already been created using the frame-relay map command. Also, use this command to enter Frame Relay VC-bundle configuration mode so you can configure PVC bundle attributes and PVC bundle members.

precedence Command (Frame Relay VC-bundle-member)

To configure the precedence levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the precedence command in Frame Relay VC-bundle-member configuration mode. To remove the precedence level configuration from the PVC, use the no form of the command.

precedence {level | other}
 
   
no precedence 

Syntax Description

level

Specifies the precedence level or levels for this Frame Relay PVC bundle member. Valid values are from 0 to 7.

You can configure a PVC bundle member with a single precedence level (0), multiple individual precedence levels (0,2,3), a range of precedence levels (0-2), multiple ranges of precedence levels (0-2,4-5), or a combination of individual levels and level ranges (0,1,2-4,7).

Note This command is available when the PVC bundle match type is set to precedence.

other

Specifies that this Frame Relay PVC bundle member handles all of the remaining precedence levels that are not explicitly configured on any other bundle members.

Note Critical non-IP traffic automatically uses precedence level 0.


precedence Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

Precedence levels are not configured.

Configuration Mode

Frame Relay VC-bundle-member configuration

Usage Guidelines for the precedence Command

Assignment of precedence levels to PVC bundle members allows you to create differentiated service because you can distribute the IP precedence levels over the various PVC bundle members. You can map a single precedence level or a range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different precedence levels. Use the precedence other command to indicate that a PVC can carry traffic marked with precedence levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the precedence other command.

This command is available only when the match type for the PVC bundle is set to precedence using the match precedence command in Frame Relay VC-bundle configuration mode.

You can overwrite the precedence level configuration on a PVC by re-entering the precedence command with a new level value.

All precedence levels must be accounted for in the PVC bundle configuration, or the bundle does not come up. Note, however, that a PVC may be a bundle member but have no precedence level associated with it. As long as all valid precedence levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no precedence level configured does not participate in it.

A precedence level can be configured on one PVC bundle member per bundle. If you configure the same precedence level on more than one PVC within a bundle, the following message appears on the console:

%Overlapping precedence levels
 
   

When tag-switching is enabled on the interface by using the tag-switching ip command, MPLS and IP packets can flow across the interface, and PVC bundles that are configured for IP precedence mapping are converted to MPLS EXP mapping. The PVC bundle functionality remains the same with respect to priority levels, bumping, and so on, but the match precedence command is replaced by the match exp command, and each precedence command is replaced by the exp command. The result is that a bundle-member PVC previously configured to carry precedence level 1 IP traffic now carries EXP level 1 MPLS traffic.

When tag-switching is disabled, the match precedence and match dscp commands are restored, and the exp commands are replaced by precedence commands.

When tag-switching is enabled or disabled, PVC bundles configured for IP precedence mapping or MPLS EXP mapping stay up, and traffic is transmitted over the appropriate bundle-member PVCs.

protect Command (Frame Relay VC-bundle-member)

To configure a Frame Relay protected permanent virtual circuit (PVC) bundle member with protected group or protected PVC status, use the protect command in Frame Relay VC-bundle-member configuration mode. To remove the protected status from the PVC, use the no form of the command.

protect {group | vc}
 
   
no protect {group | vc} 

Syntax Description

group

Configures the PVC bundle member as part of a collection of protected PVCs within the PVC bundle and specifies that the PVC bundle goes down when the last PVC in the protected group goes down.

vc

Configures the PVC member as individually protected and specifies that the PVC bundle goes down whenever the PVC goes down.


protect Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

The PVC neither belongs to the protected group nor is an individually protected PVC.

Configuration Mode

Frame Relay VC-bundle-member configuration

Usage Guidelines for the protect Command

When an individually protected PVC goes down, it takes the bundle down. When all members of a protected group go down, the bundle goes down.

Despite any protection configurations, the PVC bundle goes down if a downed PVC has no PVC to which to bump its traffic or if the last PVC that is up in a PVC bundle goes down.

pvc Command (Frame Relay VC-bundle)

To create a permanent virtual circuit (PVC) that is a Frame Relay PVC bundle member, and to enter Frame Relay VC-bundle-member configuration mode, use the pvc command in Frame Relay VC-bundle configuration mode. To delete the PVC from the Frame Relay PVC bundle, use the no form of the command.

pvc dlci [vc-name]
 
   
no pvc dlci [vc-name]

Syntax Description

dlci

Data-link connection identifier (DLCI) number used to identify the PVC.

vc-name

(Optional) An alphanumeric name for the PVC.


pvc Command History

Cisco IOS Release
Description

Release 12.0(26)S

This command was introduced on the PRE1.


Defaults

No PVC is defined.

Configuration Mode

Frame Relay VC-bundle configuration

Usage Guidelines for the pvc Command

To use this command, you must first create a Frame Relay PVC bundle and enter Frame Relay VC-bundle configuration mode.

A PVC bundle must have at least one PVC for the bundle to come up. A PVC bundle cannot have more than eight PVCs. If you try to configure more than eight PVCs in a bundle, the following message appears on the console:

%FR vc-bundle contains 8 members. Cannot add another.
 
   

Dynamic PVCs can be specified as PVC bundle members; however, if a PVC has already been created by using some other configuration command, you cannot add it to a PVC bundle. If you try to add it to a bundle, the following message appears on the console:

%DLCI 200 is not a dynamic PVC. Cannot add to VC-Bundle.
 
   

If a PVC is already a member of a PVC bundle, any attempt to reuse that same PVC in a command that creates a PVC (for example, frame-relay interface-dlci, frame-relay local-dlci) results in the following error message:

%Command is inapplicable to vc-bundle PVCs.

Service Levels and PVC Selection Criteria

The DSCP and precedence bits classify the IP packet service levels. The Precedence field consists of the first three bits of the ToS octet in the IPv4 header. You can use these bits to define a maximum of eight service levels. When you use DSCP mapping, the DSCP octet replaces the ToS octet in the IPv4 header. The first six bits are used to define a maximum of 64 service levels.

Using precedence-based or DSCP-based mapping, the router maps each IPv4 packet to a specific PVC in the bundle, according to the value of the ToS or DSCP octet in the IP header. There is no special treatment for broadcast or multicast and IP routing packets; the only differentiation in treatment is a result of the ToS or DSCP octet settings.

Prerequisites for Frame Relay PVC Selection

The Cisco 10000 series router must be running Cisco IOS Release 12.0(26)S or later releases.

To implement Frame Relay PVC bundles between two routers, you must enable IP Cisco Express Forwarding (CEF) switching on the routers.

Restrictions and Limitations for Frame Relay PVC Selection

PVCs

In Cisco IOS Release 12.0(26)S, the Frame Relay implementation of VC bundles is restricted to PVCs.

You can configure a maximum of eight PVCs in a PVC bundle.

A PVC can be a member of one and only one PVC bundle.

A PVC that is a bundle member cannot be used in any other capacity. For example, you cannot configure a PVC bundle member in a map statement.

The Cisco 10000 router does not support variable bit rate-real-time (VBR-rt) for PVCs.

VC Selection

A PVC bundle does not come up until you configure all of the precedence or DSCP levels in the bundle.

You can map one or multiple precedence or DSCP levels to a single PVC; however, you cannot map multiple PVCs to one precedence or DSCP level.

The Cisco 10000 router does not support the auto-mapping of PVCs.

Packet Forwarding

The Cisco 10000 router does not support fast switching of IP packets.

Configuring Frame Relay Bundles

To configure Frame Relay bundles, perform the following configuration tasks:

Creating a Frame Relay PVC Bundle

Adding a PVC to a Frame Relay PVC Bundle

Creating a Frame Relay PVC Bundle

To create a Frame Relay PVC bundle, enter the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# interface serial slot/module/port.channel:controller-number

Specifies the interface that you want to add to the MLP bundle. Enters interface configuration mode.

slot/module/port identifies the line card. The slashes are required.

channel: is the channel group number. The colon is required.

controller-number is the member link controller number.

Step 2 

Router(config-if)# ip address ip-address mask [secondary]

Specifies a primary IP address for the interface.

ip-address is the IP address of the interface.

mask is the subnet mask for the IP address.

(Optional) secondary indicates that the address specified is the secondary IP address. If you omit the secondary keyword, the address you specify is the primary IP address.

Step 3 

Router(config-if)# encapsulation frame-relay [cisco | ietf]

Enables Frame Relay encapsulation for the interface.

(Optional) ietf sets the encapsulation method to comply with the Internet Engineering Task Force (IETF) standard (RFC 1490). Use this keyword when connecting to another vendor's equipment across a Frame Relay network.

(Optional) cisco indicates to use Cisco's own encapsulation, which is a 4-byte header, with 2 bytes to identify the data-link connection identifier (DLCI) and 2 bytes to identify the packet type. This is the default encapsulation type.

Step 4 

Router(config-if)# frame-relay map protocol protocol-address {dlci | vc-bundle vc-bundle-name} [broadcast] [ietf] [cisco]

(Optional) Maps between a next-hop protocol address and a data link connection identifier (DLCI) destination address, and creates a PVC bundle if it does not already exist.

protocol is ip or ipx.

protocol-address is the destination IP address.

dlci is the local DLCI number used to connect to the specified protocol address on the interface. Valid values are from 16 through 1007.

vc-bundle vc-bundle-name is the name of a specific Frame Relay PVC bundle configured on the interface.

(Optional) broadcast indicates to forward broadcasts to the specified address when multicast is not enabled (see the frame-relay multicast-dlci command for more information about multicasts).

(Optional) ietf is the Internet Engineering Task Force (IETF) form of Frame Relay encapsulation, based on RFC 1490 and RFC 2427. Use the ietf keyword when the router is connected to another vendor's equipment across a Frame Relay network.

(Optional) cisco is the Cisco-proprietary encapsulation method consisting of a four-byte header, with two bytes to identify the DLCI and two bytes to identify the packet type.

Note The frame-relay map command is required for multipoint interfaces if Inverse ARP is disabled or is not supported at the other end of the connection.

Step 5 

Router(config-if)# frame-relay vc-bundle vc-bundle-name

Creates a PVC bundle if it does not already exist. Enters Frame Relay VC bundle configuration mode.

vc-bundle-name is a name you assign to the Frame Relay PVC bundle to identify the bundle.

Configuration Example for Creating a Frame Relay PVC Bundle

Example 19-3 shows how to create a Frame Relay PVC bundle. In the example, the PVC bundle is named vermont.

Example 19-3 Creating a Frame Relay PVC Bundle

Router(config)# interface serial 0
Router(config-if)# encapsulation frame-relay
Router(config-if)# ip address 10.1.1.1
Router(config-if)# frame-relay vc-bundle vermont
 
   

Adding a PVC to a Frame Relay PVC Bundle

To add a PVC to a Frame Relay PVC bundle, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface serial slot/module/port.channel:controller-number

Creates or modifies a serial interface. Enters interface configuration mode.

slot/module/port identifies the line card. The slashes are required.

channel: is the channel group number. The colon is required.

controller-number is the member link controller number.

Step 2 

Router(config-if)# frame-relay vc-bundle vc-bundle-name

Creates or modifies a PVC bundle. Enters Frame Relay VC bundle configuration mode.

vc-bundle-name is a name you assign to the Frame Relay PVC bundle to identify the bundle.

Step 3 

Router(config-fr-vcb)# pvc dlci [vc-name]

Creates a PVC bundle member and enters Frame Relay VC bundle member configuration mode.

dlci is the local data-link connection identifier (DLCI).

vc-name is a name that identifies the PVC.

Configuration Example for Adding a PVC to a Frame Relay PVC Bundle

Example 19-4 shows how to add a PVC to a Frame Relay PVC bundle. In the example, the PVC named Bronze (DLCI 100) is added to the Frame Relay PVC bundle named Business.

Example 19-4 Creating a PVC Bundle Member

Router(config-if)# frame-relay vc-bundle Business
Router(config-fr-vcb)# pvc 100 Bronze

Configuring Frame Relay Bundle Members

You can configure a Frame Relay bundle member directly or by associating a Frame Relay map class to the bundle member. The parameter values that you apply directly to the bundle member supersede the parameter values that you apply using a map class.

To apply parameters to a PVC bundle, perform either of the following configuration tasks:

Configuring a Frame Relay Bundle Member Directly

Configuring a Frame Relay Bundle Member Using a Map Class

Configuring a Frame Relay Bundle Member Directly

You can configure a Frame Relay bundle member directly or by associating a Frame Relay map class to the bundle member. The parameter values that you apply manually to the bundle member supersede the parameter values that you apply using a map class.


Note We recommend that you configure a PVC bundle on the peer router, especially for applications that rely on communications on the same PVC (for example, TCP header compression).


To configure an individual Frame Relay bundle member directly, enter the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface serial slot/module/port.channel:controller-number

Creates or modifies a serial interface. Enters interface configuration mode.

slot/module/port identifies the line card. The slashes are required.

channel: is the channel group number. The colon is required.

controller-number is the member link controller number.

Step 2 

Router(config-if)# frame-relay vc-bundle vc-bundle-name

Creates or modifies a PVC bundle. Enters Frame Relay VC bundle configuration mode.

vc-bundle-name is a name you assign to the Frame Relay PVC bundle to identify the bundle.

Step 3 

Router(config-fr-vcb)# encapsulation [ietf | cisco]

(Optional) Overrides the encapsulation type you configured on the interface and configures the Frame Relay encapsulation type for the PVC bundle.

(Optional) ietf is the Internet Engineering Task Force (IETF) form of Frame Relay encapsulation, based on RFC 1490 and RFC 2427. Use the ietf keyword when the router is connected to another vendor's equipment across a Frame Relay network.

(Optional) cisco is the Cisco-proprietary encapsulation method consisting of a four-byte header, with two bytes to identify the DLCI and two bytes to identify the packet type.

Note This command is available only when the PVC bundle is configured on a point-to-point subinterface. The router does not support this command for multipoint interfaces.

Step 4 

Router(config-fr-vcb)# match {dscp | precedence}

Sets the type of matching to use between incoming packet headers and PVC bundle members. The default match type is precedence.

Note The Cisco 10000 series router uses the type of matching you specify to map each IPv4 packet to a specific PVC in the bundle, according to the value of the ToS or DSCP octet in the IP header.

Step 5 

Router(config-fr-vcb)# pvc dlci [vc-name]

Creates or modifies a bundle member. Enters Frame Relay VC bundle member configuration mode.

dlci is the local data-link connection identifier (DLCI).

(Optional) vc-name is a name that identifies the PVC.

Step 6 

Router(config-fr-vcb-vc)# precedence {level | other}

(Optional) Configures the precedence levels for a Frame Relay PVC bundle member. This command configures precedence-based PVC selection.

level specifies the precedence level or levels for this Frame Relay PVC bundle member. Valid values are from 0 to 7.

You can configure a PVC bundle member with a single precedence level (0), multiple individual precedence levels (0,2,3), a range of precedence levels (0-2), multiple ranges of precedence levels (0-2,4-5), or a combination of individual levels and level ranges (0,1,2-4,7).

Note This command is available when the PVC bundle match type is set to precedence.

other specifies that this Frame Relay PVC bundle member handles all of the remaining precedence levels that are not explicitly configured on any other bundle members.

Note Critical non-IP traffic automatically uses precedence level 0.

Step 7 

Router(config-fr-vcb-vc)# dscp {level | other}

(Optional) Configures the differentiated services code point (DSCP) levels for a Frame Relay PVC bundle member. This command configures DSCP-based PVC selection.

level specifies the DSCP level or levels for this Frame Relay PVC bundle member. Valid values are from 0 to 63.

You can configure a PVC bundle member with a single DSCP level (9), multiple individual DSCP levels (25,35,45), a range of DSCP levels (25-35), multiple ranges of DSCP levels (25-35,45-55), or a combination of individual levels and level ranges (10,20,25-35,40,45-55,60).

Note This command is available when the PVC bundle match type is set to dscp. By default, the PVC members are configured to reject bumping when the match-type is dscp.

other specifies that this Frame Relay PVC bundle member handles all of the remaining DSCP levels that are not explicitly configured on any other bundle members.

Step 8 

Router(config-fr-vcb-vc)# exp {level | other}

(Optional) Configures Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a Frame Relay PVC bundle member. This command configures MPLS EXP-based PVC selection.

level specifies the MPLS EXP level or levels for a Frame Relay PVC bundle member. Valid values are from 0 to 7. You can configure a PVC bundle member with a single MPLS EXP level (0), multiple individual MPLS EXP levels (0,2,3), a range of MPLS EXP levels (0-2), multiple ranges of MPLS EXP levels (0-2,4-5), or a combination of individual levels and level ranges (0,1,2-4,7).

other specifies that the Frame Relay PVC bundle member handles all of the remaining MPLS EXP levels that are not explicitly configured on any other bundle member PVCs.

Step 9 

Router(config-fr-vcb-vc)# bump {explicit level | implicit | traffic}

(Optional) Configures the bumping rules for a Frame Relay PVC bundle member. The default is implicit bumping.

explicit level specifies the precedence, MPLS experimental (EXP), or differentiated services code point (DSCP) level to which traffic on the PVC is bumped if the PVC goes down. You can specify only one service level for bumping. For PVC bundles that use precedence or MPLS EXP mapping, valid values for level are from 0 to 7. For PVC bundles that use DSCP mapping, valid values are from 0 to 63.

Note When the PVC goes down, the router directs the traffic to a PVC mapped with the service level you configure in explicit level.

implicit applies the implicit bumping rule, which is the default, to a single bundle member. The implicit bumping rule stipulates that bumped traffic is to be carried by a PVC that has the lower precedence level.

traffic specifies that the PVC accepts bumped traffic. By default, a PVC accepts bumped traffic.

Note To configure a PVC to reject bumped traffic from another bundle member, enter the no bump traffic command.

Step 10 

Router(config-fr-vcb-vc)# protect {group | vc}

(Optional) Specifies the protection rule for a PVC bundle member. By default, the PVC bundle member is not protected.

group configures the PVC bundle member as part of a collection of protected PVCs within the PVC bundle and specifies that the PVC bundle goes down when the last PVC in the protected group goes down.

vc configures the PVC member as individually protected and specifies that the PVC bundle goes down whenever the PVC goes down.

Step 11 

Router(config-fr-vcb-vc)# inarp

(Optional) Enables Inverse ARP for the PVC bundle member. By default, Inverse ARP traffic uses the PVC configured for precedence level 6 or DSCP level 63.

Configuration Example for Configuring a Frame Relay Bundle Member Directly

Example 19-5 shows how to configure a Frame Relay bundle member directly. In the example, a VC bundle named maine is created and precedence is set as the type of matching to use between incoming packet headers and PVC bundle members. The PVC named Premium (DLCI 100) has precedence, bump, protect, and inarp parameters applied to it. The PVC is a bundle member of the maine PVC bundle.

Example 19-5 Configuring a Frame Relay Bundle Member

Router(config-if)# frame-relay vc-bundle maine
Router(config-fr-vcb)# encapsulation ietf
Router(config-fr-vcb)# match precedence
Router(config-fr-vcb)# pvc 100 Premium
Router(config-fr-vcb-vc)# precedence 6-7
Router(config-fr-vcb-vc)# bump explicit 7
Router(config-fr-vcb-vc)# protect group
Router(config-fr-vcb-vc)# inarp

Configuring a Frame Relay Bundle Member Using a Map Class

You can use a Frame Relay map class to apply multiple attributes to PVC bundle members at the same time. The map class parameters apply to all of the PVC bundle members to which you associate the map class.

To configure a Frame Relay bundle member using a map class, enter the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface serial slot/module/port.channel:controller-number

Creates or modifies a serial interface. Enters interface configuration mode.

slot/module/port is the number that identifies the line card. The slashes are required.

channel: is the channel group number. The colon is required.

controller-number is the member link controller number.

Step 2 

Router(config-if)# frame-relay vc-bundle vc-bundle-name

Creates or modifies a PVC bundle. Enters Frame Relay VC bundle configuration mode.

vc-bundle-name is a name you assign to the Frame Relay PVC bundle to identify the bundle.

Step 3 

Router(config-fr-vcb)# pvc dlci [vc-name]

Creates a PVC bundle member and enters Frame Relay VC bundle member configuration mode.

dlci is the local data-link connection identifier (DLCI).

vc-name is a name that identifies the PVC.

Step 4 

Router(config-fr-vcb-vc)# class class-name

Associates a map class with a PVC bundle member.

class-name is the name of the map class.

Configuration Example for Configuring a Frame Relay Bundle Member Using a Map Class

Example 19-6 shows how to configure a bundle member using a map class. In the example, the PVC bundle named Gold is created. The map class named East is applied to the PVC bundle member named member1 (DLCI 100).

Example 19-6 Configuring a Frame Relay Bundle Member Using a Map Class

Router(config-if)# frame-relay vc-bundle Gold
Router(config-fr-vcb)# pvc 100 member1
Router(config-fr-vcb-vc)# class East

Configuration Examples for Configuring Frame Relay Bundles and PVC Selection

This section provides the following configuration examples:

Configuration Example for Precedence-Based and DSCP-Based Frame Relay PVC Selection

Configuration Example for MPLS EXP-Based Frame Relay PVC Selection

Configuration Example for Precedence-Based and DSCP-Based Frame Relay PVC Selection

Example 19-7 shows how to directly configure Frame Relay PVC selection based on the packet's precedence or DSCP level. The sample configuration creates two PVC bundles on a multipoint subinterface. The PVC bundle named new-york has four members and supports precedence mapping. The PVC bundle named san-jose has three members and supports DSCP mapping. The example uses arbitrary DSCP ranges.

Example 19-7 Configuring Precedence-Based and DSCP-Based PVC Selection

interface serial 0.1 multipoint
/* Create a VC bundle map entry for the next hop IP address*/
frame-relay map ip 10.16.0.2 vc-bundle new-york
frame-relay map ip 12.0.0.2 vc-bundle san-jose
frame-relay vc-bundle new-york
match precedence
/* Create the PVCs for VC bundle new-york*/
pvc 100 ny-control
class control
precedence 7
protect vc
pvc 101 ny-premium
class premium
precedence 5-6
protect group
no bump traffic
bump explicit 7
pvc 102 ny-priority
class priority
precedence 2-4
protect group
pvc 103 ny-basic
class basic
precedence other
protect group
frame-relay vc-bundle san-jose
match dscp
pvc 200
class control
dscp 63-60
no bump traffic
protect vc
pvc 201
class premium
dscp 31-24
protect group
pvc 202
class basic
dscp other
protect group

Configuration Example for MPLS EXP-Based Frame Relay PVC Selection

Example 19-8 shows how to configure MPLS experimental (EXP)-based Frame Relay PVC selection. The sample configuration adds PVCs 101 and 100 to the PVC bundle named router2 and configures the MPLS EXP levels for each PVC bundle member.

Example 19-8 Configuring MPLS EXP-Based Frame Relay PVC Selection

interface serial8/0/0
	encapsulation frame-relay
	mpls label protocol ldp
	tag-switching ip
	frame-relay vc-bundle router2
		pvc 101
			exp 0,2,7
		pvc 100
			exp other

Verifying and Monitoring Frame Relay PVC Selection

To verify and monitor the configuration and operation of Frame Relay PVC selection, enter any of the following commands in privileged EXEC configuration mode:

Command
Purpose

Router# debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]}

Displays information about an adjacent node that has one or more Frame Relay PVCs or PVC bundles.

pvc indicates to display information about the adjacent PVC only.

(Optional) dlci is the data-link connection identifier (DLCI) for a specific PVC.

vc-bundle indicates to display information regarding the adjacent PVC bundle and its members.

(Optional) vc-bundle-name is the name of the PVC bundle.

Router# debug frame-relay vc-bundle {detail | state-change} [vc-bundle-name]

Displays information about the Frame Relay PVC bundles configured on a router.

Use this command to monitor state changes and Inverse ARP activity for one or all of the PVC bundles and bundle members configured on a router.

detail indicates to display detailed information about the members of the specified bundle. If you do not specify a vc-bundle-name, detailed information about the members of all PVC bundles displays.

Note Using the detail keyword generates a large number of debug messages that can quickly fill up a log buffer.

state-change indicates to display information pertaining only to the state changes of the specified PVC bundle and PVC bundle members. If you do not specify a vc-bundle-name, state-change information for all PVC bundles and bundle members displays.

(Optional) vc-bundle-name specifies a particular PVC bundle.

Router# show frame-relay vc-bundle {vc-bundle-name] [detail]

Displays status, bumping information, protection information, and active and configured precedence or DSCP levels for the PVCs in a PVC bundle.

vc-bundle-name is the name of the Frame Relay PVC bundle.

detail displays output packet count information in addition to the other bundle member attributes for each PVC in the bundle.

Router# show frame-relay map

Displays the current Frame Relay map entries and information about the connections.

Router# show frame-relay pvc

Displays PVC statistics for the PVC-bundle members.

Router# show frame-relay ip rtp header-compression [interface type number]

Displays Frame Relay Real-Time Transport Protocol (RTP) header compression statistics.

(Optional) interface type number specifies the interface type and number.

Router# show frame-relay ip tcp header-compression [interface type number]

Displays statistics and TCP/IP header compression information for an interface.

(Optional) interface type number specifies the interface type and number.

Router# show adjacency [summary [type number]] [detail]

Displays information about the Cisco Express Forwarding (CEF) adjacency table or the hardware Layer 3-switching adjacency table.

(Optional) summary displays a summary of CEF adjacency information.

(Optional) type number specifies the type and number of the interface (for example, serial 1/0/0).

(Optional) detail displays the protocol detail and timer information.


Verification Example for Monitoring PVC Bundles

Example 19-9 shows sample out from the show frame-relay vc-bundle command.

Example 19-9 Sample Output for the show frame-relay vc-bundle Command

Router# show frame-relay vc-bundle new-york
 
   
new-york on serial 0.1 - Status: UP Match-type: Precedence
 
   
		Config.	Active	Bumping	PG/	CIR	
Name	DLCI	Level	Level	to/accept	PV	kbps	Status
 
   
ny-control	100	7	7	4/Yes	pv	56	up
ny-premium	101	6-5	6-5	7/No	pg	256	up
ny-priority	102	4-2	4-2	1/Yes	pg	512	up
ny-basic*	103	1-0	1-0	-/Yes	pg	256	up
 
   

* Indicates that this VC is responsible for carrying unmapped traffic.

Related Documentation

This section provides hyperlinks to additional Cisco documentation for the features discussed in this chapter. To display the documentation, click the document title or a section of the document highlighted in blue. When appropriate, paths to applicable sections are listed below the documentation title.

Feature
Related Documentation

ATM PVC bundles

ATM VC Bundle Management on Cisco 12000 Series 8-Port OC-3 STM-1 ATM Line Cards, Release 12.0(23)S feature module

Understanding and Configuring ATM PVC Bundles sample configurations

Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2

Part 7: Quality of Service Solutions > IP to ATM CoS Overview > VC Bundle Support and Bundle Management

ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection, Release 12.2(8)T feature module

ATM VC Bundle Management on Cisco 12000 Series 8-Port OC-3 STM-1 ATM Line Cards, Release 12.0(23)S feature module

IP to ATM Class of Service, Release 12.0(3)T feature module

Cisco IOS Quality of Service Solutions Command Reference, Release 12.2

Bumping and bundle protection

Understanding PVC Bundle Bumping and Protection tech note

Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2

Part 7: Quality of Service Solutions > IP to ATM CoS Overview > Bumping and ATM VC Bundles

PVC Bundle Protection tech note

Frame Relay PVC bundles

Frame Relay PVC Bundles with QoS Support for IP and MPLS, Release 12.2(13)T feature module

MPLS experimental (EXP)

Cisco 10000 Series Router Quality of Service Configuration Guide

Marking Traffic > MPLS Experimental Marking

ATM PVC Bundle Enhancement — MPLS EXP-Based PVC Selection, Release 12.2(8)T feature module

Cisco IP Solution Center Quality of Service User Guide, 3.0

Quality of Service Concepts > MPLS Experimental Values