Cisco IOS Software Releases 12.0 S

Table Of Contents

MPLS Quality of Service Multi-VC Mode on the Cisco 10000 Series Router

Feature Overview

Label Switched Paths

Class of Service Map

QoS for Label-Controlled ATM VCs

MPLS QoS Support in an MPLS Network

Benefits of MPLS QoS Multi-VC Mode

Restrictions for MPLS QoS Multi-VC Mode

Prerequisites for MPLS QoS Multi-VC Mode

Related Documents

Supported Standards, MIBs, and RFCs

Configuration Tasks

Configuring Multi-VC Mode in the Core of an ATM Network

Configuring Queueing Functions on Router Output Interfaces

Monitoring and Maintaining MPLS QoS Multi-VC Mode Configuration

Configuration Examples

Command Reference

mpls cos-map

mpls prefix-map

show mpls cos-map

show mpls prefix-map

debug mpls atm-cos

Glossary

MPLS Quality of Service Multi-VC Mode on the Cisco 10000 Series Router

---

This feature module describes the MPLS Quality of Service (QoS) Multi-VC Mode feature supported on the Cisco 10000 Series Router in Cisco IOS Release 12.0(28)S and later releases. This document contains the following topics:

• Feature Overview

• Configuration Tasks

• Monitoring and Maintaining MPLS QoS Multi-VC Mode Configuration

• Configuration Examples

• Command Reference

• Glossary

Feature History

Cisco IOS Release	Modification
12.0(28)S	This feature was introduced on the Cisco 10000 series router.

Feature Overview

The Multiprotocol Label Switching Quality of Service (MPLS QoS) Multi-Virtual Circuit (VC) Mode feature on the Cisco 10000 router provides multi-VC support on the performance routing engine (part number ESR-PRE1) and extends QoS functionality to Label-Controlled Asynchronous Transfer Mode (LC-ATM) and multi-VC subinterfaces in a service provider MPLS-enabled network. Such a network incorporates ATM interfaces:

•On the edge of the network, and

•Within the core of the network

The MPLS QoS multi-VC mode feature enables you to map the experimental (EXP) field values of an MPLS label to an ATM VC to create sets of labeled virtual circuits (LVCs). Each set, called an LVC Service Group, consists of multiple LVCs. Each LVC is treated as a member of the set. All members of a set are associated with a label-switched path (LSP) that is set up between a pair of ATM-connected routers in the user's networking environment. Each member of the set may have a different quality of service from other members of the set.

By using multi-VC sets, you can provide differentiated services to users of MPLS-enabled service provider networks. To provide this service differentiation:

1. The provider edge (PE) router in the service provider network sets an appropriate value in the EXP field in the header of each incoming packet as it is received.

2. A standard IP access list (ACL), together with a class of service (CoS) map and a prefix map, are used to specify the number of classes (and LVCs) per IP destination. For information on a CoS map, see the "Class of Service Map" section.

Each MPLS-enabled ATM interface in the service provider network (including each ATM edge interface and each ATM router or switch interface within the core of the network) provides QoS support in a manner similar to that provided for IP packet interfaces. IP packets transiting the service provider's MPLS-enabled network are treated with the same priorities as afforded ATM traffic. Accordingly, MPLS QoS multi-VC functionality is virtually indistinguishable from the QoS support provided for IP packet interfaces.

For more information, see the MPLS QoS Multi-VC Mode for PA-A3, Release 12.2(2)T feature module.

Label Switched Paths

IP packets travel through the core of an MPLS-enabled service provider network by means of multiple, label-switched paths (LSPs). In ATM networks, label virtual circuits (LVCs) are automatically established for each IP destination prefix. A standard IP access list (ACL) together with a class of service (CoS) map and a prefix map are used to specify the number of classes (and LVCs) per IP destination. For information on a CoS map, see the "Class of Service Map" section.

If there are multiple equal-cost paths through an ATM network from a P router within the core of the network to a destination, it is possible that each LVC relating to the same destination could take a different path through the network, since each LVC could be set up along an alternate equal-cost path. For example, if four equal-cost paths exist through the network, the first LVC would be set up along the first path, the second LVC would be set up along the second path, and so on. There is no guarantee, however, that each LVC is set up along a parallel path in the network, nor is there any requirement that each LVC be set up in this manner.

If multiple equal-cost paths exist through an ATM network from a PE router on the edge of the network to a destination, LVCs are established for all configured classes of service for each of the equal-cost paths. The configured load-balancing mechanism determines path selection for data forwarding.

Class of Service Map

A class of service (CoS) map is a template that maps EXP values to a VC number within an LVC service group. Cisco IOS software uses the CoS map to create a binding table that maps EXP values to actual VCs. Each LVC has a CoS map and a separate binding table.

You can specify a maximum of four LVCs for each service group. Table 1 shows the default CoS map. Based on this map, the binding table has four VCs named available, standard, premium, and control. The two least significant bits of the EXP field determine the LVC to which the IP packets are directed.

Table 1 Default CoS Map

EXP Values	VC Number	VC Name
0, 4	0	Available
1, 5	1	Standard
2, 6	2	Premium
3, 7	3	Control

You can configure a CoS map to limit the number of LVCs created and to redefine the mapping of the EXP bits. Table 2 shows a configured CoS map. Based on this map, the binding table has two VCs named available and premium.

Table 2 Configured CoS Map

EXP Values	VC Number	VC Name
0, 4	0	Available
1, 5	0	Available
2, 6	2	Premium
3, 7	2	Premium

QoS for Label-Controlled ATM VCs

The router dynamically creates label-controlled ATM virtual circuits (LC-ATM VCs), also referred to as LVCs. In Cisco IOS Release 12.0(28)S and later releases, the implementation of LC-ATM interfaces is expanded to provide QoS capability for LVCs.

The router treats LVCs like unspecified bit rate (UBR) permanent virtual circuits (PVCs). By default, the LVCs share the bandwidth on an ATM interface with UBR PVCs. You can configure the bandwidth on the LC-ATM subinterface using a nested policy map. For more information, see the "Allocating LVC Bandwidth Using Policy Maps" section.

Default Bandwidth for LVCs

The default bandwidth is the bandwidth an LC-ATM interface has when it first becomes active. LVCs and UBR PVCs share all available bandwidth.

Allocating LVC Bandwidth Using Policy Maps

The router allows you to configure bandwidth for an LC-ATM subinterface. Because the router does not support a default bandwidth for LVCs, you must use a nested policy map to configure the bandwidth. The router does not allow non-nested policy maps to be attached to an LC-ATM subinterface.

The nested policy map provides the bandwidth. The router treats the configured bandwidth like the SCR of the VBR PVCs, in that all LVCs on a specific LC-ATM subinterface use the aggregate bandwidth specified in the nested policy map. The available bandwidth for UBR PVCs is then reduced by the configured bandwidth amount.

MPLS QoS Support in an MPLS Network

MPLS QoS provides Cisco IOS IP QoS (Layer 3) functionality for MPLS devices, including label edge routers (LERs), label switching routers (LSRs), and Asynchronous Transfer Mode LSRs (ATM-LSRs). You can use MPLS QoS in an MPLS-enabled networking environment in several different ways. The method you choose depends on whether the core of the network contains LSRs or ATM label switching routers (ATM-LSRs). In either case, the same QoS services are provided, such as CAR, weighted random early detection (WRED), and class-based weighted fair queueing (CBWFQ).

For information about how you can deploy LSRs and ATM-LSRs to take advantage of QoS functions in an MPLS network, refer to the MPLS QoS Multi-VC Mode for PA-A3, Release 12.2(2)T feature module.

Benefits of MPLS QoS Multi-VC Mode

The MPLS QoS multi-VC mode feature has the following benefits:

•Ensures effective deployment of differentiated service classes in an MPLS-enabled ATM network

•Leverages the use of existing ATM infrastructures

Restrictions for MPLS QoS Multi-VC Mode

The MPLS QoS multi-VC mode feature has the following restrictions:

•A multi-VC service group can have up to four LVCs.

•The Cisco 10000 series router supports a maximum of 500 LVC service groups.

•The Cisco 10000 series router does not support available bit rate (ABR) for ATM VCs. Therefore, the router also does not support ABR LVCs.

•All LVCs and the control-VC share the same QoS policy. Any QoS policy changes are applied to the subinterface. All LVCs then automatically share the new policy.

Prerequisites for MPLS QoS Multi-VC Mode

The MPLS QoS multi-VC mode feature has the following requirements:

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

•The performance routing engine (PRE), part number ESR-PRE1, must be installed in the router's chassis.

•To use MPLS QoS to full advantage in your network, the following functionality must be supported:

–Multiprotocol Label Switching (MPLS)—The standardized label switching protocol defined by the Internet Engineering Task Force (IETF).

–Cisco Express Forwarding (CEF)—An advanced Layer 3 IP switching technology that optimizes performance and scalability in networks that handle large volumes of traffic and exhibit dynamic traffic patterns.

–Asynchronous Transfer Mode (ATM)—International standard for cell relay in which multiple service types (such as voice, video, or data) are conveyed in fixed-length cells. ATM signaling is required if you use ATM interfaces in your network.

•The following QoS features are required:

–MPLS QoS multi-VC mode to provide QoS functionality on ATM interfaces in a service provider MPLS-enabled network.

–Class-based weighted fair queueing (CBWFQ) to allocate bandwidth fairly to all network traffic.

–Weighted random early detection (WRED) to configure different discard priorities or classes of service using the MPLS experimental field in the MPLS packet header.

Related Documents

For more information about MPLS QoS multi-VC mode and MPLS functionality running on Cisco routers in an MPLS environment, refer to the following documents:

• MPLS QoS Multi-VC Mode for PA-A3, Release 12.2(2)T feature module

• MPLS Label Distribution Protocol, Release 12.1(8a)E feature module

• Multiprotocol Label Switching on Cisco Routers, Release 12.1(3)T feature module

• MPLS Class of Service Enhancements, Release 12.1(5)T feature module

• MPLS Virtual Private Networks (VPNs), Release 12.0(22)S feature module

• Quality of Service Solutions Configuration Guide, Release 12.2

Supported Standards, MIBs, and RFCs

No new or modified standards, MIBs, or RFCs are supported by this feature.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check verifies that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password are e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

Configuration Tasks

To configure the MPLS QoS multi-VC mode feature on the Cisco 10000 router, perform the following required configuration tasks:

• Configuring Multi-VC Mode in the Core of an ATM Network

• Configuring Queueing Functions on Router Output Interfaces

Configuring Multi-VC Mode in the Core of an ATM Network

To configure multi-VC mode in the core of an ATM network, perform the following required configuration tasks:

• Configuring Multi-VC Mode Using the Default CoS Map

• Configuring Multi-VCs Using a Specific CoS Map

Configuring Multi-VC Mode Using the Default CoS Map

To configure multi-VC mode in an MPLS-enabled network using the default CoS map, enter the following commands beginning in global configuration mode:

	Command	Purpose
Step 1	Router(config)# interface atm number [slot/module/port.subinterface-number] mpls	Configures an ATM MPLS interface or subinterface and enters interface or subinterface configuration mode.
Step 2	Router(config-if)# ip unnumbered type number	Enables IP processing on the interface without assigning an explicit IP address to the interface.
Step 3	Router(config-if)# mpls atm multi-vc	Enables ATM multi-VC mode on the interface. Configures the ATM interface to create one or more label virtual circuits (VCs) over which packets of different classes are sent. Note This command results in the creation of the default CoS map shown in Table 1.
Step 4	Router(config-if)# mpls ip	Enables MPLS forwarding of IP version 4 (IPv4) packets along normally routed paths.
Step 5	Router(config-if)# mpls label protocol {ldp | tdp | both}	Specifies the label distribution protocol to be used on the interface.

Configuring Multi-VCs Using a Specific CoS Map

To configure multi-VCs using a CoS map that you specify, enter the following commands beginning in global configuration mode:

	Command	Purpose
Step 1	Router(config)# mpls cos-map cos-map number	Creates a class of service (CoS) map that specifies how classes map to label virtual circuits (LVCs) when they are combined with a prefix map. Enters cos-map configuration submode.
Step 2	Router(config-tag-cos-map)# class class [available | standard | premium |control]	Maps traffic classes to LVCs. class is the precedence of identified traffic to classify traffic. The default values for assigning traffic classes to the CoS map range from 0 to 3: Class 0—Available Class 1—Standard Class 2—Premium Class 3—Control The two least significant bits of the EXP field in the packet header determine the class of a packet.
Step 3	Router(config-tag-cos-map)# exit	Exits the cos-map configuration submode.
Step 4	Router(config)# access-list access-list-number permit destination	Creates an access list to control traffic going to the specified destination address.
Step 5	Router(config)# mpls prefix-map prefix-map access-list access-list cos-map cos-map	Configures the router to use a specified QoS map when an MPLS destination prefix matches the specified access list.

Configuring Queueing Functions on Router Output Interfaces

To configure queueing functions on the router's output interfaces, see the "Creating a QoS Service Policy" c hapter in the Cisco 10000 Series Router Quality of Service Configuration Guide.

Monitoring and Maintaining MPLS QoS Multi-VC Mode Configuration

To monitor and maintain the configuration of MPLS QoS multi-VC mode on ATM interfaces, enter any of the following commands in privileged EXEC mode:

Command	Purpose
Router# show mpls interfaces [interface] [detail]	Displays information about one or more interfaces that have been configured for label switching. If you do not specify an interface, information about all interfaces that have been configured for label switching displays. detail displays detailed label switching information for the specified interface or for all interfaces if you do not specify an interface.
Router# show mpls cos-map [cos-map]	Displays the quality of service (QoS) map used to assign a quantity of label virtual circuits and the associated class of service (CoS) for those virtual circuits. cos-map is an optional number that specifies the QoS map to be displayed.
Router# show mpls prefix-map [prefix-map]	Displays the prefix map used to assign a QoS map to network prefixes that match a standard IP access list. prefix-map is an optional number that specifies the prefix map to be displayed.
Router# debug mpls atm-cos [bind | request]	Displays ATM label VC bind or request activity that is based on the configuration of a QoS map.

Configuration Examples

For an example of how to configure MPLS QoS multi-VC mode functionality, see the "Configuration Examples" s ection in the MPLS QoS Multi-VC Mode for PA-A3, Release 12.2(4)T3 feature module.

Command Reference

This section documents the commands used to configure the MPLS QoS multi-VC mode feature on the Cisco 10000 router. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.

•mpls cos-map

•mpls prefix-map

•show mpls cos-map

•show mpls prefix-map

•debug mpls atm-cos

mpls cos-map

To create a class map that specifies how classes map to label VCs when they are combined with a prefix map, use the mpls cos-map global configuration command.

mpls cos-map cos-map

Syntax Description

cos-map

Unique number for a QoS map (1 to 255).

Defaults

This command has no default behavior or values.

Command Modes

Global configuration

Command History

Release	Modification
12.0(5)T	This command was introduced.
12.0(10)ST	This command was modified to reflect MPLS IETF syntax and terminology.
12.2(2)T	This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(28)S	This command was introduced on the Cisco 10000 series router.

Examples

The following example shows how to create a class of service map:

Router(config)# mpls cos-map 55 

Router(config-mpls-cos-map)# class 1 premium 

Router(config-mpls-cos-map)# exit 

Router(config)# 

Related Commands

Command	Description
show mpls cos-map	Displays the QoS map used to assign a quantity of label VCs and the associated class of service for those label VCs.

mpls prefix-map

To configure a router to use a specified QoS map when a label destination prefix matches the specified access list, use the mpls prefix-map ATM subinterface submode command.

mpls prefix-map prefix-map access-list access-list cos-map cos-map

Syntax Description

prefix-map	A unique number for a prefix map.
access-list access-list	A unique number for a simple IP access list.
cos-map cos-map	A unique number for a QoS map.

Defaults

This command has no default behavior or values.

Command Modes

ATM subinterface submode

Command History

Release	Modification
12.0(5)T	This command was introduced.
12.0(10)ST	This command was modified to reflect MPLS IETF syntax and terminology.
12.2(2)T	This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(28)S	This command was introduced on the Cisco 10000 series router.

Usage Guidelines

This is a global command that links an access list to a QoS map.

Examples

In the following example, an access list is linked to a QoS map:

Router(config-subif)# mpls prefix-map 55 access-list 55 cos-map 55 

Related Commands

Command	Description
show mpls prefix-map	Shows the prefix map used to assign a QoS map to network prefixes that match a standard IP access list.

show mpls cos-map

To display the QoS map used to assign a quantity of label VCs and the associated class of service for those VCs, use the show mpls cos-map privileged EXEC command.

show mpls cos-map [cos-map]

Syntax Description

cos-map

An integer specifying the cos-map to be displayed.

Defaults

If you do not enter a specific cos-map, all cos-maps are displayed.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)T	This command was introduced.
12.0(10)ST	This command was modified to reflect MPLS IETF syntax and terminology.
12.2(2)T	This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(28)S	This command was introduced on the Cisco 10000 series router.

Examples

The following shows sample output from the show mpls cos-map command:

Router# show mpls cos-map 2

cos-map 2 class tag-VC

3 control

2 control

1 available

0 available

Table 3 describes the significant fields in the sample display shown above.

Table 3 show mpls cos-map Command Field Descriptions

Field	Description
cos-map	Configures a class map, which specifies how classes map to MPLS VCs when they are combined with a prefix map.
class	The IP precedence.
tag-VC	An ATM virtual circuit that is set up through ATM LSR label distribution procedures.

Related Commands

Command	Description
mpls cos-map	Creates a class map specifying how classes map to label VCs when they are combined with a prefix map.

show mpls prefix-map

To show the prefix map used to assign a QoS map to network prefixes that match a standard IP access list, use the show mpls prefix-map privileged EXEC command.

show mpls prefix-map [prefix-map]

Syntax Description

prefix-map

An integer specifying the prefix-map number to be displayed.

Defaults

If you do not enter a specific prefix-map, all prefix-maps are displayed.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)T	This command was introduced.
12.0(10)ST	This command was modified to reflect MPLS IETF syntax and terminology.
12.2(2)T	This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(28)S	This command was introduced on the Cisco 10000 series router.

Examples

The following is sample output from the show mpls prefix-map command:

Router# show mpls prefix-map 2 

prefix-map 2 access-list 2 cos-map 2 

Table 4 describes the fields in the sample output shown above.

Table 4 show mpls prefix-map Command Field Descriptions

Field	Description
prefix-map	Unique number of a prefix map.
access-list	Unique number of an access list.
cos-map	Unique number of a QoS map.

Related Commands

Command	Description
mpls prefix-map	Configures a router to use a specified QoS map when a label destination prefix matches the specified access-list.

debug mpls atm-cos

To display ATM label VC bind or request activity that is based on the configuration of a QoS map, use the debug mpls atm-cos ATM subinterface submode command.

debug mpls atm-cos [bind | request]

Syntax Description

bind	Specifies debug information about bind responses for a VC path.
request	Specifies debug information about bind requests for a VC path.

Defaults

This command has no default behavior or values.

Command Modes

ATM subinterface submode

Command History

Release	Modification
12.0(5)T	This command was introduced.
12.0(10)ST	This command was modified to reflect MPLS IETF syntax and terminology.
12.2(2)T	This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(28)S	This command was introduced on the Cisco 10000 series router.

Examples

The following command sequence demonstrates how to obtain sample output from the debug mpls atm-cos command.

1. Display the MPLS forwarding table to see which prefixes are associated with a single LVC, as shown below:

Router# show mpls forwarding

Local Outgoing Prefix Bytes tag Outgoing Next Hop 

tag tag or VC or Tunnel Id switched interface 

26 28 17.17.17.17/32 0 PO6/0 point2point 

27 Pop tag 11.11.11.11/32 1560 PO6/0 point2point 

28 27 16.16.16.16/32 0 PO6/0 point2point 

29 30 92.0.0.0/8 0 PO6/0 point2point 

30 Pop tag 95.0.0.0/8 2600 PO6/0 point2point 

31 2/34 10.10.10.10/32 0 AT2/0.1 point2point 

32 Pop tag 14.14.14.14/32 0 Fa5/0 91.0.0.1 

33 Pop tag 90.0.0.0/8 0 Fa5/0 91.0.0.1 

34 Pop tag 96.0.0.0/8 0 Fa5/0 91.0.0.1 

2/36 96.0.0.0/8 0 AT2/0.1 point2point 

35 35 93.0.0.0/8 0 PO6/0 point2point 

36 36 12.12.12.12/32 0 PO6/0 point2point 

37 37 15.15.15.15/32 0 PO6/0 point2point 

38 37 18.18.18.18/32 0 Fa5/0 91.0.0.1 

39 39 97.0.0.0/8 540 PO6/0 point2point 

40 40 98.0.0.0/8 0 PO6/0 point2point 

2. Enable debugging of request and bind events, as shown in the command sequence below:

Router# debug mpls atm-cos ? 

bind Bind response for VC path 

request Requests for VC binds path 

Router# debug mpls atm-cos request 

ATM TAGCOS VC requests debugging is on 

Router# debug mpls atm-cos bind 

ATM TAGCOS Bind response debugging is on 

3. Configure an MPLS ATM subinterface for multi-VC mode. The corresponding request and bind events are displayed, as shown below:

Router# config terminal 

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)# interface atm2/0.1 

Router(config-subif)# mpls atm multi-vc 

Router(config-subif)# end 

Router# 

19:59:14:%SYS-5-CONFIG_I:Configured from console by console 

Router# 

19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, available 

19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, standard 

19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, premium 

19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, control 

19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, available 

19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, standard 

19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, premium 

19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, control 

TAGCOS-REQ/TCATM:11.11.11.11/32,len=4352,band=1099528405504,class=0x700 

TAGCOS-REQ/TCATM:12.12.12.12/32,len=4352,band=2199040033280,class=0x700 

TAGCOS-REQ/TCATM:13.13.13.13/32,len=4352,band=3298551661056,class=0x700 

TAGCOS-REQ/TCATM:14.14.14.14/32,len=4352,band=4398063288832,class=0x700 

TAGCOS-REQ/TCATM:15.15.15.15/32,len=4352,band=5497574916608,class=0x700 

TAGCOS-REQ/TCATM:16.16.16.16/32,len=4352,band=6597086544384,class=0x700 

TAGCOS-REQ/TCATM:17.17.17.17/32,len=4352,band=7696598172160,class=0x700 

TAGCOS-REQ/TCATM:18.18.18.18/32,len=4352,band=8796109799936,class=0x700 

TAGCOS-REQ/TCATM:90.0.0.0/8,len=768,band=3940649674539009,class=0x2 

TAGCOS-REQ/TCATM:91.0.0.0/8,len=768,band=3940649674604545,class=0x2 

TAGCOS-REQ/TCATM:92.0.0.0/8,len=768,band=3940649674670081,class=0x2 

TAGCOS-REQ/TCATM:93.0.0.0/8,len=768,band=3940649674735617,class=0x2 

TAGCOS-REQ/TCATM:94.0.0.0/8,len=768,band=3940649674801153,class=0x2 

TAGCOS-REQ/TCATM:95.0.0.0/8,len=768,band=3940649674866689,class=0x2 

TAGCOS-REQ/TCATM:97.0.0.0/8,len=768,band=3940649674932225,class=0x2 

TAGCOS-REQ/TCATM:98.0.0.0/8,len=768,band=3940649674997761,class=0x2 

TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=41 - control 41,41,41,41 

TAGCOS-BIND:binding_ok 10.10.10.10/32, Inform TFIB pidx=0, in_tag=31, idx=0x80000000 

TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=42 - control 42,42,42,42 

TAGCOS-BIND:binding_ok 96.0.0.0/8, Inform TFIB pidx=1, in_tag=34, idx=0x80000001 

TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=43 - premium 43,43,43,41 

TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=44 - premium 44,44,44,42 

TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=45 - standard 45,45,43,41 

TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=46 - standard 46,46,44,42 

TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=47 - available 47,45,43,41 

TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=48 - available 48,46,44,42 

Router# 

Glossary

ATM edge LSR	A router that is connected to the ATM-LSR cloud through an LSC-ATM interface. The ATM edge LSR adds labels to unlabeled packets and strips labels from labeled packets.
ATM-LSR	A label switch router with a number of LSC-ATM interfaces. The router forwards ATM cells among these interfaces using labels carried in the VPI/VCI field.
CAR	Committed access rate (packet classification). CAR is the main feature supporting packet classification. CAR uses the type of service (ToS) bits in the IP header to classify packets. You can use the CAR classification commands to classify or reclassify a packet.
Class-based weighted fair queueing (CBWFQ)	CBWFQ extends standard WFQ functionality to provide support for user-defined traffic classes. For CBWFQ, you define traffic classes based on match criteria which include protocols, access control lists (ACLs), and input interfaces. Packets satisfying match criteria for a class constitute the traffic for that class. A queue is reserved for each class, and the traffic belonging to a class is directed to the queue for that class.
IP precedence	A 3-bit value in the ToS byte that is used for assigning precedence to IP packets.
label	A short, fixed-length construct that tells switching nodes how to forward data (packets or cells) in a network.
label-controlled ATM interface (LC-ATM interface)	An interface on a router or switch that uses label distribution procedures to negotiate label VCs.
label edge router (LER)	A router that performs label imposition at the point of ingress in a network.
label imposition	The process of adding the first label on a packet.
label switch	A node that forwards units of data (packets or cells) on the basis of labels carried in the packets or cells.
label switch path (LSP)	An LSP results from a series of hops (Router 0...Router n) through which a packet travels from R0 to Rn by means of label switching mechanisms. A label-switched path can be determined dynamically (based on normal routing mechanisms), or it can be defined explicitly.
label-switched path (LSP) tunnel	A configured connection between two routers, in which label switching techniques are used for packet forwarding.
label switching router (LSR)	A Layer 3 router that forwards packets based on the value of a label encapsulated in each packet.
label VC (LVC)	An ATM virtual circuit that is set up through ATM LSR label distribution procedures.
LBR	Label bit rate. A service category defined for label-VC traffic. Link and per-VC bandwidth sharing can be controlled by relative bandwidth configuration at the edge of the network and each switch along a label-VC. No ATM traffic-related parameters are specified.
LDP	Label Distribution Protocol. The protocol used to distribute label bindings to LSRs.
LFIB	Label forwarding information base. The data structure used by switching functions to switch labeled packets.
LIB	Label information base. A database used by an LSR to store labels learned from other LSRs, as well as labels assigned by the local LSR.
MPLS	Multiprotocol Label Switching. An emerging industry standard that defines support for MPLS forwarding of packets along normally routed paths (sometimes called MPLS hop-by-hop forwarding).
QoS	Quality of service. A feature that provides scalable, differentiated types of service across an MPLS network.
RED	Random early detection. A congestion avoidance algorithm in which a small percentage of packets are dropped automatically when congestion is detected in the network and before the queue in question overflows completely.
ToS bits	Type of service bits. A byte in the IPv4 packet header.
Weighted fair queueing (WFQ)	A queue management algorithm that provides a certain fraction of link bandwidth to each of several queues, based on a relative bandwidth applied to each of the queues.
Weighted random early detection (WRED)	A variant of RED in which the probability of a packet being dropped depends on either its IP precedence, CAR marking, or MPLS class of service (as well as other factors in the RED algorithm).