Table Of Contents
Software Configuration of ATM ISE Line Cards for Cisco 12000 Series Routers
Prerequisites for the 4-Port ATM ISE Line Card
Restrictions for the 4-Port ATM ISE Line Card
Information About the 4-Port ATM ISE Line Card
Features of the 4-Port ATM ISE Line Card
How to Perform a Basic Configuration of the 4-Port ATM ISE Line Card
Default Interface Configuration
Configuring UNI and NNI Cell Support
How to Configure Layer 3 Terminated VCs on the 4-Port ATM ISE Line Card
Configuring Layer 3 Terminated Virtual Circuits
Configuring ATM Shaping on Terminated VCs
Configuring OAM Management on Terminated VCs
Configuring Quality of Service on Terminated VCs
Configuring a Per-VC Queue Limit
Configuring Per-VC MDRR and Low Latency Queueing
Configuring and Managing VC Bundles
Applying Bundle-Level Parameters
Applying Parameters to Individual VCs
How to Configure AToM VCs on the 4-Port ATM ISE Line Card
Configuring Layer 2 AToM Virtual Circuits
Configuring ATM AAL5 over MPLS
Configuring ATM Cell Relay over MPLS on PVCs
Configuring ATM Cell Relay over MPLS on PVPs
Configuring ATM Cell Relay over MPLS on a Port
Configuring ATM Cell Packing over MPLS on PVCs
Configuring ATM Cell Packing over MPLS on PVPs
Configuring ATM Cell Packing over MPLS on a Port
Configuring OAM Emulation on AToM VCs
Configuring ATM Shaping on AToM VCs
Configuring Cell Relay over MPLS on PVCs
Configuring Cell Relay over MPLS on PVPs
Configuring Cell Packing over MPLS on PVCs
Configuring Cell Packing over MPLS on PVPs
Configuring AAL5 over MPLS on PVCs
Configuring Cell-Based Traffic Policing on AToM VCs
Configuring CBR or UBR.1 Policing
Attaching a Service Policy to a PVC
Configuring Experimental Mapping
Configuring Experimental Bits on PVCs
Configuring Experimental Bits on a Port
Troubleshooting ATM Errors on the 4-Port ATM ISE Line Card
Debugging Unexpected TX Drops on a VC
Using the class-map match-any and class-map match-all Commands
Attaching a Traffic Policy to a PVC
Software Configuration of ATM ISE Line Cards for Cisco 12000 Series Routers
This feature module describes the software configuration for the Cisco 4-Port ATM Internet Services Engine (ISE) line cards in the Cisco 12000 Series Router. The line card comes in two variations: OC-12c/STM-4c and OC-3c/STM-1; otherwise, the features are the same on both cards.
Feature History for the 4-Port ATM ISE Line Card
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for the 4-Port ATM ISE Line Card
•
•
•
•
•
•
Prerequisites for the 4-Port ATM ISE Line Card
There are no prerequisites for using the 4-port ATM ISE line card.
Restrictions for the 4-Port ATM ISE Line Card
Restrictions and limitations for the 4-Port ATM ISE line cards are listed in Table 1 and Table 2.
Table 1 Supported Values for 4-Port ATM ISE Line Card
Maximum number of cell packing or policing VCs1
508 per port2
Maximum number of active VCs3 :
Layer 2
Layer 3
10244 per port and card
20473 per port and cardRange of VPI5 values
Varies with vc-per-vp value.
In Release 12.0(25)S: up to 255
In Release 12.0(27)S:
UNI VPIs—up to 255; NNI VPIs—up to 4095Range of VCI6 values
Varies with vc-per-vp value, up to 65,535
1 VC=virtual circuit.
2 Hardware limitation.
3 Subject to overall system limitation and configuration.
4 If cell packing or policing are configured, the remaining 516 available VCs can be configured for cell relay over MPLS or AAL5 over MPLS.
5 VPI=virtual path identifier.
6 VCI=virtual channel identifier.
Table 2 Scalability Limitations for the 4-Port ATM ISE Line Card
Maximum number of AToM Tunnels per port
1024
Maximum number of AToM Tunnels per line card
1024
Maximum number of AToM Tunnels per router
2048
Maximum number of AToM Tunnels per port with features1
508
Maximum number of AToM Tunnels per port with cell packing
508
Maximum number of AToM Tunnels per line card with features1
1024
Maximum number of AToM Tunnels per line card with cell packing
1024
1 Includes features such as policing
Information About the 4-Port ATM ISE Line Card
The 4-Port ATM ISE line cards, which deliver line rate OC-12c/STM-4c or OC-3c/STM-1 bandwidth, provide enhanced Layer 2 and Layer 3 capabilities for high-speed customer aggregation, backbone connectivity, and peering solutions. These cards perform traffic shaping and per-virtual circuit (VC) queueing, and support per-VC Modified Deficit Round Robin (MDRR) with per-VC low latency queueing (LLQ). They also support Any Transport over MPLS (AToM), enhanced traffic policing, and the ability to configure both AToM VCs and terminated VCs on a single port.
MDRR is implemented on a per-VC basis with up to eight queues per VC, where one of the queues is a low latency queue (LLQ). Both per-VC Weighted Random Early Detection (WRED) and per-VC MDRR are performed in the hardware.
The 4-Port OC-12c/STM-4c ATM ISE line card provides the Cisco 12000 Series Router with four 622-Mbps ATM interfaces. The 4-Port OC-3c/STM-1 ATM ISE line card provides four 155-Mbps ATM interfaces. The cards communicate with the Cisco 12000 Series Router switch fabric.
Features of the 4-Port ATM ISE Line Card
The following are the features supported by the 4-Port ATM ISE line cards:
•
•
•
•
•
•
•
•
•
•
•
•
•
Layer 3-Specific Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Layer 2-Specific Features
•
•
•
•
•
•
•
How to Perform a Basic Configuration of the 4-Port ATM ISE Line Card
The 4-port ATM ISE line cards provide the ability to configure Layer 2 AToM VCs as well as Layer 3 terminated VCs. On any individual ATM interface, you can configure both AToM VCs and terminated VCs as required. The configurations of these are discussed in subsequent sections in this document. This section provides basic ATM interface configuration information and discusses those features that are applicable to both AToM VCs and terminated VCs.
Configuring ATM interfaces and virtual circuits is described in the following sections:
•
Configuring an ATM Interface
Use the show running-config command to display current port configuration information. On power up, the interface on a new 4-Port ATM ISE line card is shut down. To enable the interface, you must enter a no shutdown command in configuration mode.
Default Interface Configuration
When the 4-Port ATM ISE line card is enabled (taken out of shutdown) with no additional configuration commands applied, the default interface configuration file parameters, described in Table 3, are used.
Configuration Basics
After you verify that the new 4-Port ATM ISE line card is installed correctly, use the configure command to configure the new interface. Be prepared with the information that you will need, such as the interface IP address.
The Cisco 12000 Series Router identifies an interface address by its line card slot number and port number, in the format slot/port. Because each 4-Port ATM ISE line card contains four ATM interfaces, the port numbers are 0 to 3. For example, the slot/port address of an ATM interface on a 4-Port ATM ISE line card installed in line card slot 2 is 2/0 to 2/3.
Use the following procedure to create a basic configuration, including enabling an interface and specifying IP routing. You might also need to enter other configuration subcommands, depending on the requirements for your system configuration.
(For descriptions of configuration subcommands and the configuration options available, refer to the appropriate software publications in the "Related Documents" section.)
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuring UNI and NNI Cell Support
You can designate that the cell format for an interface be either User Network Interface (UNI) or Network Node Interface (NNI). The default setting is UNI. Use the atm maxvpi-bits command to change the maximum VPI range from 0..255 (UNI) to 0..4095 (NNI).
Router(config)# interface atm 2/2Router(config-if)# atm maxvip-bits 12To change the interface setting back to NNI, use the no form of this command: no maxvip-bits 12.
This configuration should be entered before the connection is added.
Troubleshooting Tips
To verify the operation of the interfaces configured on the 4-Port ATM ISE line card, use the following commands:
To display information about the current state of the ATM network, use the following commands:
How to Configure Layer 3 Terminated VCs on the 4-Port ATM ISE Line Card
The following configuration tasks are described in this section:
•
•
•
•
•
Configuring Layer 3 Terminated Virtual Circuits
A virtual circuit (VC) is a point-to-point connection between two ATM devices. A VC is established for each ATM end node with which the router communicates. The characteristics of the VC are established when it is created and include the following for the 4-Port ATM ISE line cards:
•
•
•
•
Permanent virtual circuits (PVCs) configured on the router remain active until the circuit is removed from the configuration. All virtual circuit characteristics apply to PVCs. When a PVC is configured, all configuration options are passed to the 4-Port ATM ISE line card. These PVCs are written to the nonvolatile RAM (NVRAM) as part of the configuration and are used when the Cisco IOS image is reloaded.
When you create a PVC, you create a virtual circuit descriptor (VCD) and attach it to the VPI and VCI. The VCD tells the card which VPI/VCI to use for a particular packet. The 4-Port ATM ISE line card requires this feature to manage the packets for transmission. The number chosen for the VCD is independent of the VPI/VCI used.
A permanent virtual path (PVP) is like a bundle of VCs, transporting all cells with a common VPI, rather than a specific VPI and VCI.
PVCs are created and configured using the pvc command in interface configuration mode. PVPs are created and configured using the atm pvp command in interface configuration mode.
The syntax of the pvc command is as follows:
pvc [name] vpi/vci
The syntax of the atm pvp command is:
atm pvp vpi
vpi is the ATM network VPI to use for this virtual circuit, in the range of 0 to 255 for UNI or 0 to 4095 for NNI; vci is the ATM network VCI to use for this virtual circuit, in the range of 0 to 655,535.
Troubleshooting Tips
To display information about the connected virtual circuits, use the following commands:
Router# show atm pvc
Displays current ATM PVC information.
Router# show atm vc
Displays current ATM VC information.
Configuring ATM Shaping on Terminated VCs
The 4-Port ATM ISE line cards support IP traffic shaping on terminated VCs. The following ATM shaping options are available:
•
•
•
•
To configure ATM shaping, perform the shaping commands in PVC mode. You should use only one of the shaping commands in Step 5 through Step 8, depending on the type of shaping to be configured.
Restrictions
CDVT
When traffic shaping is configured on a VC, the cell delay variation (CDV) is set for the VC. This value will change according to the shaping class defined. The cell delay variation tolerance (CDVT) values are shown in Table 4.
Note
Decreased VC Throughput
If you configure a VC on a 4-Port OC-12/STM-4 ATM ISE interface with a peak cell rate (PCR) or sustainable cell rate (SCR) greater than OC-6 (using the ubr, vbr-nrt, vbr-rt, or cbr commands), and attach a traffic policy with MDRR (configured using the bandwidth command) to the interface for specified traffic classes, when traffic on the interface from the specified classes is equal to or greater than the configured PCR or SCR values, frequent queueing and dequeueing changes occur between the MDRR queues and may cause a decreased VC throughput.
Decreased throughput is more likely to occur when the traffic consist of small packets and when a high amount of traffic is sent toward the high-priority queue. Such traffic will increase significantly the frequency of switches between queues, which may cause the nonpriority queues to lose their bandwidth. Therefore, when configuring a VC to more than OC-6, it is recommended to limit the high priority traffic using the police command.
SUMMARY STEPS
Use either Step 5, Step 6, Step 7 or Step 8 depending on the desired shaping.
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface atmslot/port.subinterface
Example:Router(config)# interface atm1/0.2
Specifies an ATM interface or subinterface to configure.
Configure subinterfaces so that you can take advantage of access list definitions for the IP traffic.
Step 4
pvc [name] vpi/vciExample:Router(config-if)# pvc 0/100Specifies a PVC with the specified VPI and virtual circuit identifier (VCI).
Step 5
Specifies CBR shaping.
The pcr value indicates the peak cell rate. The range is from 38 to 622,000 Kbps.
Note
Step 6
Router(config-if-vc)# vbr-rt 100000 40000 200000
Specifies VBR-rt shaping.
The pcr value indicates the peak cell rate, and its range is from 38 to 622,000 Kbps. The scr value indicates the sustainable cell rate, and its range is from 38 to pcr Kbps. The burst value indicates the burst size, in number of cells.
Step 7
Router(config-if-vc)# vbr-nrt 100000 40000 200000
Specifies VBR-nrt shaping.
The pcr value indicates the peak cell rate, and its range is from 38 to 622,000 Kbps. The scr value indicates the sustainable cell rate, and its range is from 38 to pcr Kbps. The mbs value indicates the maximum burst size, in number of cells.
Step 8
Router(config-if-vc)# ubr 100000
Specifies UBR shaping.
The pcr value indicates the peak cell rate, and its range is from 38 to 622,000 Kbps.
Configuring OAM Management on Terminated VCs
OAM may be enabled for PVC or SVC management on terminated VCs. To configure OAM management for an ATM Layer 3 PVC, perform the following procedure.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
OAM Management
By default, end-to-end F5 OAM loopback cell generation is turned off for each PVC. A PVC is determined as down when any of the following is true on that PVC:
•
•
The router receives a Virtual Circuit-Remote Detect Indicator (VC-RDI) cell.
A PVC is determined as up when all the following are true on that PVC:
•
•
•
Note the following regarding OAM management:
•
The 4-Port ATM ISE line card supports OAM management enabled mode for the entire range of VCs supported, while using the default frequency of 10 seconds on all VCs. The minimum OAM LB cell frequency of 1 second is currently permitted over no more then 50 PVCs (chassis performance limitation), and the default interval of 10 seconds is used for the rest of the PVCs.
OAM F5 Continuity Check
The 4-Port ATM ISE line card also provides OAM support for the use of F5 segment and end-to-end continuity check (CC) cells to detect connectivity failures at the ATM layer. It also generates various Simple Network Management Protocol (SNMP) notifications when CC cells indicate virtual circuit (VC) connectivity failure
ATM OAM F5 CC cells provide an in-service tool optimized to detect connectivity problems at the VC level of the ATM layer. CC cells are sent between a router designated as the source location and a router designated as the sink location. The local router can be configured as the source, the sink, or both.
The 4-Port ATM ISE line card implements two types of OAM cells: CC cells for fault management and CC cells for activation and deactivation. Fault management cells detect connectivity failures. Activation and deactivation cells initiate the activation or deactivation of continuity checking.
Configuring Quality of Service on Terminated VCs
Quality of Service (QoS) on terminated VCs is configured using the Modular QoS CLI (MQC). MQC allows users to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to classify traffic, and the QoS features in the traffic policy determine how to treat the classified traffic.
To configure and enable QoS on terminated VCs, you must define a traffic class, create a traffic policy, and attach this traffic policy to the PVC. See the "Configuring Modular QoS CLI" section for detailed instructions on how to complete these tasks.
The following tasks use the MQC to configure QoS on terminated VCs:
•
•
Configuring Traffic Policing
This task describes how to configure traffic policing using the MQC. Traffic policing can be configured for either ingress or egress traffic.
This task illustrates the use of the match access-group command. For information on other match options, refer to the "Configuring Modular QoS CLI" section.
When traffic policing is configured, packets coming into interface are evaluated by the token bucket algorithm to determine whether they conform to or exceed the specified parameters. The conform-action, exceed-action, and violate-action parameters in the police command determine what is done with the packets.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
The command syntax of the police command allows you to specify the action to be taken on a packet when you enable the action keyword. The actions resulting from the keyword choices are listed in Table 5.
Configuring a Per-VC Queue Limit
Use this task to configure a per-VC queue limit on a single egress or ingress queue.
Restrictions
A queue limit cannot be configured together with WRED.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Configuring Per-VC WRED
Use this task to configure DSCP-based or precedence-based WRED on a VC. WRED can be configured on both ingress or egress queues, where ingress queues are defined in terms of packets and egress queues are defined in terms of cells.
Restrictions
•
•
SUMMARY STEPS
For precedence-based WRED use Step 7; for DSCP-based WRED use Step 8 or Step 9.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Configuring Per-VC MDRR and Low Latency Queueing
This task configures egress MDRR.
Using egress MDRR, the 4-Port ATM ISE line card supports up to eight queues for classes of traffic per VC. One of the queues is always reserved for a special class called class-default. Up to seven of the classes are normal queues, including the class-default queue. The eighth class is always a low latency queue.
The class, class-default, is always configured, and it consumes one of the eight queues. If not configured explicitly, it is configured implicitly. When the bandwidth command is used, at least 1 percent of traffic must be reserved for the class-default queue. All packets that do not match any user-defined class on the policy map are considered to belong to class-default, and therefore enter the default queue.
The low latency queue, or priority queue, is also always created. All traffic sourced from the router (including ping traffic and multicast traffic) uses this queue, regardless of classification.
Bandwidth percentages are converted into weights in units of ATM cells. The weights are internally proportioned such that the bandwidth is divided accurately among VCs.
The following are recommendations for configuring per-VC MDRR on the 4-Port ATM ISE line card:
•
•
Note
If none of the classes is a priority class, the maximum number of classes that can be configured with the bandwidth command, excluding the class-default class, is six. When class-default is not specified, at least 1 percent must be allocated to this class.
If priority is not specified on any class, then any form of the bandwidth command can be used. If the priority command is configured without a police command (drop exceed-action), then the only form of the bandwidth command that is allowed on the other classes in the policy map is the bandwidth remaining command. If a police command is used on the priority queue, then all forms of the bandwidth commands are allowed.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Note
Note
Examples
Following are additional examples of configuring MDRR:
•
•
Configuring Per-VC MDRR and Low Latency Queueing with Queue Limits
In the following example, per-VC MDRR and LLQ are configured with nondefault queue limits.
Configure the policy map as shown in the example:
Router(config)# policy-map MDRRandQlimitRouter(config-pmap)# class class1Router(config-pmap-c)# priorityRouter(config-pmap-c)# class class2Router(config-pmap-c)# bandwidth remaining percent 50Router(config-pmap-c)# queue-limit 576 cellsRouter(config-pmap-c)# class class-defaultRouter(config-pmap-c)# queue-limit 576 cellsAfter the policy map has been created, configure it on the VC using the service-policy command.
Configuring Per-VC MDRR and Policed Low Latency Queueing
If the police command is used with the exceed-action set to drop on the priority queue, then the bandwidth command can be used with either a percent or kbps specified.
The following example uses the bandwidth percent command to guarantee bandwidth to nonpriority classes. Twenty percent of the VC rate is guaranteed to class2.
Router(config)# policy-map MDRR-POLICE-LLQRouter(config-pmap)# class class1Router(config-pmap-c)# priorityRouter(config-pmap-c)# police 64000000 conform-action transmit exceed dropRouter(config-pmap-c)# class class2Router(config-pmap-c)# bandwidth percent 20Router(config-pmap-c)# endRouter#The next example uses the bandwidth remaining percent command, and specifies that 20 percent of the remaining bandwidth is guaranteed to class2.
Router(config)# policy-map MDRR-POLICE-LLQRouter(config-pmap)# class class1Router(config-pmap-c)# priorityRouter(config-pmap-c)# police 64000000 conform-action transmit exceed dropRouter(config-pmap-c)# class class2Router(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# endRouter#After the policy map has been created, configure it on the VC using the service-policy command.
Configuring the set Commands
This task illustrates how to configure the toggling of various bits, such as the ATM CLP, the IP DSCP, the IP precedence, and the MPLS experimental. Setting of the ATM CLP bit is only supported on egress queues; setting of all other bits is supported on both ingress and egress queues.
In this task, use one of either Step 8, Step 9, Step 10, Step 11, or Step 12, depending on what bits you need to configure.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
class match-any class-name
Example:Router(config-pmap)# class match-any prec345
Specifies the user-defined name of the traffic class. The match-any keyword specifies a logical OR operator for all matching statements under this traffic class.
Step 4
match ip precedence numbers
Example:Router(config-cmap)# match ip precedence 3 4 5
Specifies up to eight IP precedence values used as match criteria.
Step 5
exit
Exits class-map mode.
Step 6
policy-map policy-name
Example:Router(config)# policy-map SET_ATM_CLP
Specifies the name of the traffic policy to configure.
Step 7
class prec345
Example:Router(config-pmap)# class prec345
Specifies the name of a predefined class, which was defined with the class-map command, to be included in the traffic policy.
Step 8
set atm-clp
Example:Router(config-pmap)# set atm-clp
Sets the ATM cell loss priority bit to 1.
Note
Step 9
set ip precedence
Specifies the IP precedence of packets within a traffic class. The IP precedence value can be any value between 0 and 7.
Step 10
set ip dscp ip-dscp-value
Example:Router(config-pmap-c)# set ip dscp 31
Specifies the IP DSCP of packets within a traffic class. The IP DSCP value can be any value between 0 and 63.
Step 11
set mpls experimental value
Designates the value to which the MPLS bits are set if the packets match the specified policy map.
Step 12
set qos-group value
Example:Router(config-pmap-c)# set qos-group 10
Specifies a QoS group value to associate with the packet. The QoS group value can be any value between 0 and 99.
Step 13
exit
Exits policy-map class mode.
Step 14
exit
Exits policy-map mode.
Step 15
interface atmslot/port.subifnum
Example:Router(config)# interface atm1/0.1
Specifies the ATM subinterface to configure.
Step 16
pvc vpi/vci
Example:Router(config-subif)# pvc 10/50
Specifies the ATM PVC to attach the policy map to.
Step 17
service-policy input policy-name
Example:Router(config-if-atm-vc)# service-policy output SET_ATM_CLP
Attaches the policy map to the PVC.
Examples
Following are examples of configuring the IP DSCP value and the ATM CLP bit:
•
•
•
•
Configuring the IP DSCP Value
This example marks packets of class1 by setting the IP differentiated services code point (DSCP):
Router(config)# policy-map QOS-SETRouter(config-pmap)# class class1Router(config-pmap-c)# set ip dscp 63Router(config-pmap-c)# class class2Router(config-pmap-c)# bandwidth percent 30Router(config-pmap-c)# exitRouter(config-pmap)#In the above example, class1 is configured with a nonqueueing feature. Traffic that is matched to class1 is considered to belong to this class for purposes of the nonqueueing feature, but for purposes of queueing, the packet will go into the default queue.
After the policy map has been created, configure it on the VC using the service-policy command.
Configuring the ATM CLP Bit on a Per-Queue Basis with Per-VC MDRR
This example configures the CLP bit setting on a per-queue basis. Precedence 0 and 1 go to the queue of class prec01 with CLP bit off; precedence 2 goes to the queue of class prec2 with the CLP on; precedence 3, 4, and 5 go to the queue of class prec345 with the CLP on; all other traffic goes to the queue of class-default with the CLP bit off.
Router(config)# class-map match-any prec01Router(config-cmap)# match ip prec 0 1Router(config)# class-map match-any prec2Router(config-cmap)# match ip prec 2Router(config)# class-map match-any prec345Router(config-cmap)# match ip prec 3 4 5Router(config)# policy-map SET_ATM_CLPRouter(config-pmap)# class prec01Router(config-pmap-c)# bandwidth percent 10Router(config-pmap-c)# class prec2Router(config-pmap-c)# bandwidth percent 10Router(config-pmap-c)# set atm-clpRouter(config-pmap-c)# class prec345Router(config-pmap-c)# bandwidth percent 10Router(config-pmap-c)# set atm-clpRouter(config-pmap-c)# exitAfter the policy map has been created, configure it on the VC using the service-policy command.
Configuring the ATM CLP Bit on Class-Default Queue with Per-VC MDRR
This example configures the CLP bit setting on part of the traffic of the class-default queue. Precedence 0, 1 go to the queue of class prec01 with the CLP bit off; precedence 3, 4, and 5 go to the queue of class class-default with the CLP on; all other traffic goes to the queue of class-default with the CLP bit off.
Router(config)# class-map match-any prec01Router(config-cmap)# match ip prec 0 1Router(config)# class-map match-any prec345Router(config-cmap)# match ip prec 3 4 5Router(config)# policy SET_ATM_CLPRouter(config-pmap)# class prec01Router(config-pmap-c)# bandwidth percent 10Router(config-pmap-c)# class prec345Router(config-pmap-c)# set atm-clpRouter(config-pmap-c)# exitAfter the policy map has been created, configure it on the VC using the service-policy command.
Configuring the ATM CLP Bit by Traffic Policing
This example uses traffic policing to mark packets by setting the ATM CLP bit:
Router(config)# policy-map POLIC_SET_ATM_CLPRouter(config-pmap)# class class1Router(config-pmap-c)# police 64000000 conform-action transmit exceed-action set-clp-transmitRouter(config-pmap-c)# exitAfter the policy map has been created, configure it on the VC using the service-policy command.
Troubleshooting Tips
Use the show class-map class-name command to display the information relating to a traffic class. Use the show policy-map command to display the configuration of a traffic policy and its associated traffic classes. Forms of these commands are listed in the table below.
Configuring and Managing VC Bundles
See the following sections for configuration tasks for the VC bundle management feature. Each task in the list is identified as either required or optional.
•
•
Creating a VC Bundle
To create a bundle and enter bundle configuration mode, in which you can assign attributes and parameters to the bundle and all its member VCs, use the following command in subinterface configuration mode:
Router (config-subif)# bundle bundle-name
Creates the VC bundle specified as bundle-name and enters bundle configuration mode.
Applying Bundle-Level Parameters
Bundle-level parameters can be applied either by assigning VC classes or by directly applying them to the bundle.
Parameters applied through a VC class assigned to the bundle are superseded by those applied at the bundle level. Bundle-level parameters are superseded by parameters applied to an individual VC.
The following sections describe applying bundle-level parameters:
•
•
•
Configuring Bundle-Level Parameters
Configuring bundle-level parameters is optional if a class is attached to the bundle to configure it.
To configure parameters that apply to the bundle and all its members, use the following commands in bundle configuration mode, as needed:
Configuring VC Class Parameters to Apply to a Bundle
Use of a VC class allows you to configure a bundle by applying multiple attributes to it at one time because you apply the class itself to the bundle. Use of a VC class allows you to generalize a parameter across all VCs, after which (for some parameters) you can modify that parameter for individual VCs. (See the "Applying Parameters to Individual VCs" section for more information.)
To configure a VC class to contain commands that configure VC members of a bundle when the class is applied to that bundle, use the following command in vc-class configuration mode. To enter vc-class configuration mode, use the vc-class atm command.
Router(config-vc-class)# oam-bundle [manage] [frequency]
Enables end-to-end F5 OAM loopback cell generation and OAM management for all VCs in the bundle.
In addition to the oam-bundle command, you can add the following commands to a VC class to be used to configure a bundle: bump, precedence, mpls experimental, and protect commands. For more information about these commands, refer to the ATM VC Bundle Management on Cisco 12000 Series 8-Port OC_3 STM-1 ATM Line Cards document.
Attaching a VC Class to a Bundle
To attach a preconfigured VC class containing bundle-level configuration commands to a bundle, use the following command in bundle configuration mode:
Router(config-if-atm-bundle)# class-bundle vc-class-name
Configures a bundle with the bundle-level commands contained in the specified VC class.
Parameters set through bundle-level commands contained in the VC class are applied to the bundle and all its VC members. Bundle-level parameters applied through commands configured directly on the bundle supersede those applied through a VC class.
Note that 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. For more information on bundle-vc configuration mode, see "Committing a VC to a Bundle" in the following section.
Committing a VC to a Bundle
To add a VC to an existing bundle and enter bundle-vc configuration mode, use the following command in bundle configuration mode:
Router(config-if-atm-bundle)# pvc-bundle pvc-name [vpi/] [vci]
Adds the specified VC to the bundle and enters bundle-vc configuration mode to configure the specified VC bundle member.
For information on how to create a bundle and configure it, see the "Creating a VC Bundle" section and the "Applying Bundle-Level Parameters" section.
Applying Parameters to Individual VCs
Parameters can be applied to individual VCs either by using VC classes or by directly applying them to the bundle members.
Parameters applied to an individual VC supersede bundle-level parameters. Parameters applied directly to a VC take precedence over the same parameters applied within a class to the VC at the bundle-vc configuration level.
The following should be noted regarding parameters applied to individual VCs:
•
•
The following sections describe applying parameters to individual VCs:
•
•
•
•
Configuring a VC Bundle Member Directly
Configuring VC bundle members directly is optional if a VC class is attached to the bundle member.
To configure an individual VC bundle member directly, use the following commands in bundle-vc configuration mode:
Parameters set directly for a VC at the bundle-vc configuration level take precedence over values for these parameters set for the VC at any other level, including application of a VC class at the bundle-vc configuration level.
Configuring VC Class Parameters to Apply to a VC Bundle Member
To configure a VC class to contain commands that configure a specific VC member of a bundle when the class is applied to it, use the following commands in bundle-vc configuration mode, as needed. To enter vc-class configuration mode, use the vc-class atm command in global configuration mode.
Applying a VC Class to a Discrete VC Bundle Member
To attach a preconfigured VC class containing bundle-level commands to a bundle member, use the following command in bundle-vc configuration mode:
Router(config-if-atm-member)# class-vc vc-class-name
Assigns a VC class to a VC bundle member.
Parameters that configure a VC that are contained in a VC class assigned to that VC are superseded by parameters that are directly configured for the VC through discrete commands entered in bundle-vc configuration mode.
Configuring a VC Not to Accept Bumped Traffic
To configure an individual VC bundle member not to accept traffic that otherwise might be directed to it if the original VC carrying the traffic goes down, use the following command in bundle-vc configuration mode:
Router(config-if-atm-member)# no bump traffic
Configures the VC not to accept any bumped traffic that would otherwise be redirected to it.
VC Bundle Examples
•
•
•
•
VC Bundle Configuration on an IP Subinterface Example
This example configures a VC bundle with eight member VCs on an IP subinterface.
interface ATM5/0.2 point-to-pointip address 1.5.0.1 255.255.255.0no ip directed-broadcastno atm enable-ilmi-trapbundle b502pvc-bundle 1/107precedence 7pvc-bundle 1/106precedence 6pvc-bundle 1/105precedence 5pvc-bundle 1/104precedence 4pvc-bundle 1/103precedence 3pvc-bundle 1/102precedence 2pvc-bundle 1/101precedence 1pvc-bundle 1/100precedence other!VC Bundle Configuration Using MPLS and Service Policies Example
This example configures a VC bundle with three member VCs on a MPLS-enabled subinterface. Each of the bundle members has the same traffic policy attached.
interface ATM5/1.1 point-to-pointip address 1.1.2.1 255.255.255.0no ip directed-broadcastno atm enable-ilmi-trapbundle b511oam retry 3 5 1oam-bundle managepvc-bundle 1/103service-policy out highmpls experimental 5-7pvc-bundle 1/102service-policy out highmpls experimental 2-4pvc-bundle 1/101service-policy out highmpls experimental 0-1!tag-switching ip!VC Bundle Configuration Using a VC Class Example
This example shows how to configure a VC bundle using VC classes.
interface ATM2/1.1 point-to-pointip address 2.1.2.1 255.255.255.0no ip directed-broadcastno atm enable-ilmi-trapbundle b211pvc-bundle lab-control 0/33class-vc control-classpvc-bundle lab-premium 0/34class-vc premium-classvbr-nrt 100000 100000 8000mpls experimental 0-6pvc-bundle lab-priority 0/35class-vc priority-classpvc-bundle lab-basic 0/36class-vc basic-class!tag-switching ipCLP Bit Setting on a Per-Experimental Basis with VC Bundling
CLP bit setting can be combined with VC bundling by configuring VC bundling on a group of VCs as desired, creating a policy map with CLP bit setting configured as desired, and then configuring the CLP bit setting.
This example configures VC bundling and CLP bit setting on a per-experimental basis. There are two VCs. Experimental 0 and 1 go to VC 1 with CLP on. Experimental 2 and 3 go to VC 1 with CLP off. Experimental 4 and 5 go to VC 2 with CLP on, and experimental 6 and 7 go to VC 2 with CLP off. This does not require a hierarchical policy, because there is only one queue per VC.
Note
class-map match-any exp01match mpls experimental 0 1class-map match-any exp45match mpls experimental 4 5policy set-clp-0145class exp01set atm-clpclass exp45set atm-clpinterface atm4/0.1 point-to-pointip address 4.0.1.1 255.255.255.0bundle my-paris2-bundlepvc-bundle 40/1precedence 0-3service-policy output set-clp-0145pvc-bundle 40/2precedence 4-7service-policy output set-clp-0145!tag-switching ipTroubleshooting Tips
To gather information on VC bundles so as to monitor them or to troubleshoot problems that pertain to their configuration or use, use the following commands in privileged EXEC mode, as needed:
Configuring Bridged PVCs
The purpose of bridged permanent virtual circuits (BPVCs) is to allow ATM interfaces in the Cisco high-end router to be used in an edge or aggregation role and connect to a Cisco Catalyst switch or to another remote device that supports bridged-format RFC 1483 PDUs only.
Note
To create a BPVC, perform the following steps:
Note
How to Configure AToM VCs on the 4-Port ATM ISE Line Card
This section describes how to configure AToM VCs in the following tasks:
•
•
•
•
Configuring Layer 2 AToM Virtual Circuits
A virtual circuit (VC) is a point-to-point connection between two ATM devices. A VC is established for each ATM end node with which the router communicates. Permanent virtual circuits (PVCs) configured on the router remain active until the circuit is removed from the configuration. All virtual circuit characteristics apply to PVCs. When a PVC is configured, all configuration options are passed to the 4-Port ATM ISE line card. These PVCs are written to the nonvolatile RAM (NVRAM) as part of the configuration and are used when the Cisco IOS image is reloaded.
A permanent virtual path (PVP) is like a bundle of VCs, transporting all cells with a common VPI, rather than a specific VPI and VCI.
PVCs are created and configured using the pvc command in interface configuration mode. PVPs are created and configured using the atm pvp command in interface configuration mode.
The syntax of the pvc command is as follows:
pvc [name] vpi/vci l2transport
The syntax of the atm pvp command is:
atm pvp vpi l2transport
vpi is the ATM network VPI to use for this virtual circuit, in the range of 0 to 255 for UNI or 0 to 4095 for NNI; vci is the ATM network VCI to use for this virtual circuit, in the range of 0 to 655,535.
The l2transport keyword indicates that the PVP or PVC is a switched PVP/PVC and not terminated. Once you enter this command, you enter l2transport submode.
Troubleshooting Tips
To display information about the connected virtual circuits, use the following commands:
Router# show atm pvc
Displays current ATM PVC information.
Router# show atm vc
Displays current ATM VC information.
Configuring AToM VCs
Any Transport over MPLS (AToM) encapsulates Layer 2 frames at the ingress PE and sends them to a corresponding PE at the other end of a pseudowire, which is a connection between the two PE routers. The egress PE removes the encapsulation and sends out the Layer 2 frame.
The successful transmission of the Layer 2 frames between PE routers is due to the configuration of the PE routers. You set up the connection, called a pseudowire, between the routers.
The 4-Port ATM ISE line cards provide a number of configuration options for ATM over MPLS:
•
–
•
–
–
•
–
•
–
–
–
•
–
Prerequisites
Before configuring AToM, ensure that the network is configured as follows:
•
•
•
Configuring ATM AAL5 over MPLS
ATM AAL5 over MPLS encapsulates ATM AAL5 SDUs in MPLS packets and forwards them across the MPLS network. Each ATM AAL5 SDU is transported as a single packet. Perform this task to enable ATM AAL5 over MPLS.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# pvc 1/200 l2transportRouter(config-atm-l2trans-pvc)# encapsulation aal5Router(config-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsConfiguring ATM Cell Relay over MPLS on PVCs
Perform this task to configure ATM Cell Relay on permanent virtual circuits (PVCs).
Restrictions
The cell relay function can only be configured when the ATM VC is configured for AAL0 encapsulation. It has no meaning if the VC is configured with AAL5 encapsulation.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# pvc 0/100 l2transportRouter(config-atm-l2trans-pvc)# encapsulation aal0Router(config-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsConfiguring ATM Cell Relay over MPLS on PVPs
Perform this task to configure ATM Cell Relay on permanent virtual paths (PVPs).
Restrictions
The cell relay function can only be configured when the ATM VP is configured for AAL0 encapsulation. It has no meaning if the VP is configured with AAL5 encapsulation.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# atm pvp vpi 1 l2transportRouter(config-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsConfiguring ATM Cell Relay over MPLS on a Port
Port mode cell relay allows a single cell coming into an ATM interface to be packed into an MPLS packet and transported over the MPLS backbone to an egress ATM interface.
To configure port mode, you issue the xconnect command from an ATM main interface and specify the destination address and the VC ID. The syntax and semantics of the xconnect command are the same as for all other transport types. Each ATM port is associated with one unique pseudowire VC label.
Perform this task to transport ATM over MPLS in port mode:
Restrictions
The cell relay function can only be configured when the ATM interface is configured for AAL0 encapsulation. It has no meaning if the interface is configured with AAL5 encapsulation.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# xconnect 10.0.0.1 123 encapsulation mplsConfiguring ATM Cell Packing over MPLS on PVCs
Perform this task to configure ATM cell packing on permanent virtual circuits (PVCs).
Restrictions
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# atm mcpt-timers 100 200 1000Router(config-if)# pvc 0/100 l2transportRouter(config-atm-l2trans-pvc)# encapsulation aal0Router(config-atm-l2trans-pvc)# cell-packing 10 mcpt-timer 1Router(config-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsConfiguring ATM Cell Packing over MPLS on PVPs
Perform this task to configure ATM cell packing on permanent virtual paths (PVPs).
Restrictions
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# atm mcpt-timers 100 200 1000Router(config-if)# atm pvp vpi 1 l2transportRouter(cfg-if-atm-l2trans-pvc)# cell-packing 10 mcpt-timer 1Router(cfg-if-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsConfiguring ATM Cell Packing over MPLS on a Port
Port mode cell packing allows multiple cells coming into an ATM interface to be packed into an MPLS packet and transported over the MPLS backbone to an egress ATM interface.
To configure port mode, you issue the xconnect command from an ATM main interface and specify the destination address and the VC ID. The syntax and semantics of the xconnect command are the same as for all other transport types. Each ATM port is associated with one unique pseudowire VC label.
Perform this task to configure cell packing ATM over MPLS in port mode.
Restrictions
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# no ip addressRouter(config-if)# no ip directed-broadcastRouter(config-if)# atm clock internalRouter(config-if)# atm mcpt-timers 100 200 1000Router(config-if)# no atm enable-ilmi-trapRouter(config-if)# no atm ilmi-keepaliveRouter(config-if)# cell-packing 10 mcpt-timer 1Configuring OAM Emulation on AToM VCs
If Operation, Administration, and Maintenance (OAM) Emulation is not configured, the OAM method is set to transparent pass-through on AToM VCs. OAM Emulation provides the ability to send a remote defect indication (RDI) in response to an alarm indication signal (AIS) without passing it along the MPLS network to the egress PE. It also allows for sending F5 loopback cells of loopback point (with loopback indication equal to 0) in response to F5 loopback cells of source point (with loopback indication equal to 1) without passing them along the MPLS network to the egress PE. In addition, it drops F5 continuity check cells without passing them along the MPLS network to the egress PE.
Restrictions
OAM Emulation can be enabled only on an AAL5 VC.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Note
Example
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# pvc 10/50 l2transportRouter(config-if-l2trans-pvc)# encapsulation aal5Router(config-if-l2trans-pvc)# oam emulation-enableRouter(config-if-l2trans-pvc)# oam-pvc manage 0Router(config-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsTroubleshooting Tips
To troubleshoot AToM VCs, use the following commands:
Configuring ATM Shaping on AToM VCs
The 4-Port ATM ISE line cards support both VP and VC traffic shaping for AToM. The following ATM shaping options are available:
•
•
•
vbr-nrt pcr scr.•
The following tasks illustrate how to configure the ATM shaping queue size and traffic shaping for CBR, UBR, VBR-rt and VBR-nrt classes of service on AToM VCs and VP tunnels in various transport modes.
•
•
•
•
•
Restrictions
When traffic shaping is configured on a VC, the cell delay variation (CDV) is set for the VC. This value will change according to the shaping class defined. The cell delay variation tolerance (CDVT) values are shown in Table 6.
Note
Configuring Cell Relay over MPLS on PVCs
This task illustrates the configuration of CBR traffic shaping in cell relay over MPLS VC mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# policy-map out_cbr
Router(config-pmap)# class class-defaultRouter(config-pmap-c)# queue-limit 200 cellsRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm1/0Router(config)# atm clock internalRouter(config-if)# pvc 21/21 l2transportRouter(config-atm-l2trans-pvc)# encapsulation aal0Router(cfg-if-atm-l2trans-pvc)# cbr 1000Router(config-pmap-c)# service-policy output out_cbrRouter(config-atm-vc)# xconnect 2.2.2.2. 121 encapsulation mplsConfiguring Cell Relay over MPLS on PVPs
This task illustrates the configuration of UBR traffic shaping in cell relay over MPLS in VP mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# policy-map out_ubrRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# queue-limit 100 cellsRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm1/0Router(config)# atm clock internalRouter(config-if)# atm pvp 100 l2transportRouter(config-if-vc)# ubr 2000Router(config-pmap-c)# service-policy output out_ubrRouter(config-atm-vc)# xconnect 2.2.2.2. 121 encapsulation mplsConfiguring Cell Packing over MPLS on PVCs
This task illustrates the configuration of VBR-RT traffic shaping in cell packing over MPLS VC mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# policy-map out_vbr-rtRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# queue-limit 300 cellsRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm1/0
Router(config)# atm clock internalRouter(config-if)# atm mcpt-timers 100 1000 5000Router(config-if)# pvc 21/21 l2transportRouter(config-atm-l2trans-pvc)# encapsulation aal0Router(config-atm-l2trans-pvc)# cell-packing 10 mcpt-timer 1Router(config-if-vc)# vbr-rt 2000 1000 100Router(config-pmap-c)# service-policy output out_vbr-rtRouter(config-atm-vc)# xconnect 2.2.2.2. 121 encapsulation mplsConfiguring Cell Packing over MPLS on PVPs
The following task illustrates the configuration of VBR-NRT traffic shaping in cell packing over MPLS in VP mode:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# policy-map out_vbr-nrtRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# queue-limit 400 cellsRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm1/0Router(config)# atm clock internalRouter(config-if)# atm pvp 100 l2transportRouter(config-atm-l2trans-pvc)# cell-packing 10 mcpt-timer 1Router(config-if-vc)# vbr-nrt 3000 2000 200Router(config-pmap-c)# service-policy output out_vbr-nrtRouter(config-atm-vc)# xconnect 2.2.2.2. 121 encapsulation mplsConfiguring AAL5 over MPLS on PVCs
This task illustrates the configuration of VBR-RT traffic shaping in AAL5 over MPLS VC mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Example
Router> enableRouter# configure terminalRouter(config)# policy-map out_vbr-rtTroubleshooting Tips
Use the following show commands to display the cell relay and cell packing counters for troubleshooting purposes:
See the "Troubleshooting ATM Errors on the 4-Port ATM ISE Line Card" section for more information on the output from these commands.
Configuring Cell-Based Traffic Policing on AToM VCs
Traffic policing is configured using the Modular QoS CLI. In order to configure traffic policing, you need to do the following:
•
•
•
For Layer 2 traffic, you can configure traffic policies that will guarantee a particular quality of service (QoS) traffic class. This is done using the police rate command in policy-map class configuration mode.
The supported policing configurations are shown in Table 7.
Table 7 Supported Policing Configurations
CBR
CLP(0+1)
Discard
N/A
N/A
VBR.1
CLP(0+1)
Discard
CLP(0+1)
Discard
VBR.2
CLP(0+1)
Discard
CLP(0)
Discard
VBR.3
CLP(0+1)
Discard
CLP(0)
Tagging
UBR.1
CLP(0+1)
Discard
N/A
N/A
1 GCRA=Generic Cell Rate Algorithm
If single-bucket policing is used, there is a single policy definition using the rate and burst tolerance parameters. For a two-bucket policer, the rate and burst tolerance are taken from the parent policy, and the SCR and ATM maximum burst size (MBS) values are taken from the child policy.
This section describes some of the most common tasks that are necessary to configure QoS traffic policing on AToM VCs. For more detailed information regarding MQC, see the "Configuring Modular QoS CLI" section.
•
•
Restrictions
The following restrictions apply to policing on the 4-port ATM ISE line card:
•
•
•
•
•
•
•
•
•
Configuring CBR or UBR.1 Policing
This task describes how to configure CBR or UBR.1 policing.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
policy-map policy-map-name
Example:Router(config)# policy-map cbr
Specifies the name of the service policy to configure.
Step 4
class class-default
Example:Router(config-pmap)# class class-default
Specifies the name of a predefined class, which was defined with the class-map command, to be included in the service policy. You can include the default class, class-default, in the service policy.
Step 5
police rate pcr cps delay-tolerance cdvt conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 100000 cps delay-tolerance 5 conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
After you configure the policy map, you must attach it to a PVC using the service-policy command as described in the "Attaching a Service Policy to a PVC" section.
Configuring VBR.1 Policing
This task describes how to configure VBR.1 policing.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
policy-map child-vbr1
Example:Router(config)# policy-map child-vbr1
Specifies the name of the child service policy to configure.
Step 4
class class-default
Example:Router(config-pmap)# class class-default
Specifies to configure the default class referred to as class-default.
Step 5
police rate scr cps atm-mbs mbs cells conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 200000 cps atm-mbs 1024 cells conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
Step 6
exit
Example:Router(config-pmap-c)# exit
Exits class mode.
Step 7
exit
Example:Router(config-pmap)# exit
Exits policy-map mode.
Step 8
policy-map vbr1
Example:Router(config)# policy-map vbr1
Specifies the name of the parent service policy to configure.
Step 9
class class-default
Example:Router(config-pmap)# class class-default
Specifies to configure the default class.
Step 10
set mpls experimental mpls-exp-value
Example:Router(config-pmap-c)# set mpls experimental 4
(Optional) Specifies the value used to set the MPLS EXP bits defined by the policy map. Valid values are numbers from 0 to 7.
Step 11
police rate pcr cps delay-tolerance cdvt conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 500000 cps delay-tolerance 1000 conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
Step 12
service-policy child-vbr1
Example:Router(config-pmap-c)# service-policy child-vbr1
Attaches the child service policy to the VBR1 policy map.
After you configure the policy map, you must attach it to a PVC using the service-policy command as described in the "Attaching a Service Policy to a PVC" section.
Configuring VBR.2 Policing
This task describes how to configure VBR.2 policing.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
class-map match-all class-map-name
Example:Router(config)# class-map match-all cpl0
Specifies the user-defined name of the traffic class. Use match-all to specify a logical AND operator for all matching statements under this traffic class.
Step 4
match not match-criteria
Example:Router(config-cmap)# match not atm clp
Specifies that CLP1 is used as an unsuccessful match criterion, meaning that CLP1 cells will pass and CLP0 cells will be discarded.
Step 5
exit
Example:Router(config-cmap)# exit
Exits class-map mode.
Step 6
policy-map child-vbr2
Example:Router(config)# policy-map child-vbr1
Specifies the name of the child service policy to configure.
Step 7
class class-map-name
Example:Router(config-pmap)# class clp0
Specifies to configure the class defined in Step 3.
Step 8
police rate scr cps atm-mbs mbs cells conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 100 cps atm-mbs 1024 cells conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
Step 9
exit
Example:Router(config-pmap-c)# exit
Exits class mode.
Step 10
exit
Example:Router(config-pmap)# exit
Exits policy map mode.
Step 11
policy-map vbr2
Example:Router(config)# policy-map vbr2
Specifies the name of the parent service policy to configure.
Step 12
class class-default
Example:Router(config-pmap)# class class-default
Specifies to configure the default class.
Step 13
set mpls experimental mpls-exp-value
Example:Router(config-pmap-c)# set mpls experimental 4
(Optional) Specifies the value used to set the MPLS EXP bits defined by the policy map. Valid values are numbers from 0 to 7.
Step 14
police rate pcr cps delay-tolerance cdvt conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 2500000 cps delay-tolerance 10 conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
Step 15
service-policy child-vbr2
Example:Router(config-pmap-c)# service-policy child-vbr2
Attaches the child service policy to the VBR1 policy map.
After you configure the policy map, you must attach it to a PVC using the service-policy command as described in the "Attaching a Service Policy to a PVC" section.
Configuring VBR.3 Policing
This task describes how to configure VBR.2 policing.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
class-map match-all class-map-name
Example:Router(config)# class-map match-all cpl0
Specifies the user-defined name of the traffic class. Use match-all to specify a logical AND operator for all matching statements under this traffic class.
Step 4
match not match-criteria
Example:Router(config-cmap)# match not atm clp
Specifies a single match criterion value to use as an unsuccessful match criterion.
Step 5
exit
Example:Router(config-cmap)# exit
Exits class-map mode.
Step 6
policy-map child-vbr3
Example:Router(config)# policy-map child-vbr1
Specifies the name of the child service policy to configure.
Step 7
class class-map-name
Example:Router(config-pmap)# class clp0
Specifies to configure the class defined in Step 3.
Step 8
police rate scr cps atm-mbs mbs cells conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 100000 cps atm-mbs 1024 cells conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
Step 9
exit
Example:Router(config-pmap-c)# exit
Exits class mode.
Step 10
exit
Example:Router(config-pmap)# exit
Exits policy map mode.
Step 11
policy-map vbr3
Example:Router(config)# policy-map vbr3
Specifies the name of the parent service policy to configure.
Step 12
class class-default
Example:Router(config-pmap)# class class-default
Specifies to configure the default class.
Step 13
set mpls experimental mpls-exp-value
Example:Router(config-pmap-c)# set mpls experimental 4
(Optional) Specifies the value used to set the MPLS EXP bits defined by the policy map. Valid values are numbers from 0 to 7.
Step 14
police rate pcr cps delay-tolerance cdvt conform-action transmit exceed-action drop
Example:Router(config-pmap-c)# police rate 250000 cps delay-tolerance 10 conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
Step 15
service-policy child-vbr3
Example:Router(config-pmap-c)# service-policy child-vbr3
Attaches the child service policy to the VBR1 policy map.
After you configure the policy map, you must explicitly attach it to a PVC using the service-policy command as described in the "Attaching a Service Policy to a PVC" section.
Attaching a Service Policy to a PVC
After you define a service policy with the desired QoS configuration, you must attach it to a PVC as described in this task.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Troubleshooting Tips
Use the following show commands to display the counters for conformance and drop cells for VP and VC connections:
Configuring Experimental Mapping
You can configure the experimental bits on PVCs, PVPs, and a port. The following tasks describe how to set the experimental bits in various situations:
•
•
Configuring Experimental Bits on PVCs
This task describes how to configure the experimental bits in the MPLS header on a PVC.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Configuring Experimental Bits on a Port
This task describes how to configure the experimental bits in the MPLS header on a port.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Troubleshooting ATM Errors on the 4-Port ATM ISE Line Card
The following sections provide information to help you troubleshoot ATM errors on the 4-port ATM ISE line cards:
•
Troubleshooting Commands
Use the following commands to troubleshoot ATM errors:
show interfaces atm
The most common symptoms of ATM-level errors are incrementing numbers in one of the error counters (displayed in boldface) in the show interfaces command:
Router# show interfaces atm1/1ATM1/1 is up , line protocol is upHardware is PM622 OC-12c ATM, address is 0008.200b.b0ab (bia 008.200b.b0ab)MTU 4470 bytes, sub MTU 4470, BW 622000 Kbit, DLY 80 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ATM, loopback not setEncapsulation(s): AAL5, PVC mode2047 maximum active VCs, 4 current VCCsVC idle disconnect time: 300 secondsLast input never, output 00:00:02, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 56 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outEach of the error counters is described in Table 8.
show controller traffic
Any packets received on nonexistence VCs will be displayed in the show atm traffic RP command.
router# show atm traffic3523 Input packets3510 Output packets0 Broadcast packets0 Packets received on non-existent VC0 Packets attempted to send on non-existent VC3507 OAM cells receivedF5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0F4 InEndloop: 3507, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 03507 OAM cells sentF5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutAIS: 0 F5 OutRDI: 0F4 OutEndloop: 3507, F4 OutSegloop: 0, F4 OutRDI: 0 F4 OutAIS: 00 OAM cell dropsshow controller atm
To display the ATM statistics on the line card, use the line card show controller atm privileged EXEC command. The available show controller atm counters are described in Table 9.
Router# exec slot 1 show controller atm 1 trafficVCID InPkts InBytes PktsInSW InOams OutPkts OutBytes1 78278986 4227058178 0 0 82600440 4460416714SAR Counters:tx_packets : 82600440 tx_bytes : 4460416714tx_total_resource_errs: 0 tx_total_other_errs : 0tx_wred_thresh_drops : 0 tx_wred_random_drops : 0rx_packets : 78278986 rx_bytes : 4227058178rx_total_resource_errs: 0 rx_total_other_errs : 0rx_buffer_exhaust_errs: 0 rx_CRC32_errors : 0rx_packet_abort_errs : 0 rx_trailer_len_errs : 0rx_mps_errors : 0 rx_reassembly_timeout: 0The following are per-SAR counters:Reassembly SAR:sys_rx_unopen_vc_cls : 89169 sys_tx_unopen_vc_cls : 0 sys_ecc_errors : 0 sys_ecc_and_addr : 0xFFFFFFF sys_ecc_or_addr : 0x00000000Segmentation SAR:sys_rx_unopen_vc_cls : 0 sys_tx_unopen_vc_cls: 0sys_ecc_errors : 0 sys_ecc_and_addr : 0xFFFFFFFFsys_ecc_or_addr : 0x00000000
Table 9 show controller atm Counters
tx_packets
A 64-bit counter of the number of packets transmitted on this interface, including OAM cells. This should be approximately the total number of packets on all the VCs on this interface. (If traffic stops for a few seconds, these numbers should be exactly equal.)
Packets output in the show interface command should have the same value, excluding OAM cells.
tx_bytes
A 64-bit counter of the bytes transmitted on this interface, including OAM cells and AAL5 header encapsulations (such as AAL5SNAP). This should be approximately the total number of bytes transmitted on each of the VCs.
Output bytes in the show interface command should have the same value, excluding OAM cells.
tx_total_resource_errs
The total number of packets that were not transmitted because of any resource exhaustion error. This does not necessarily imply an error, because this counter includes tx_wred_thresh_drops and tx_wred_random_drops, as well as packet drops due to complete buffer exhaustion on the SAR. This should be equal to the sum of the number of resource errors that occur on all the VCs.
Buffer exhaustion should not occur if you have not oversubscribed the queue thresholds on the interface. See the "Debugging Unexpected TX Drops on a VC" section.
tx_total_other_errs
The total number of packets that were not transmitted because of any error other than resource exhaustion, but not including no-vc drops. This includes malformed packets, CRC errors, and so on. This should be approximately the total number of tx_other_errors that occur on all the VCs on this interface.
tx_wred_thresh_drops
The total number of WRED maximum threshold drops on this interface. This counter is included in the tx_total_resource_errs counter.
tx_wred_random_drops
The total number of WRED random drops on this interface. This counter is included in the tx_total_resource_errs counter.
rx_packets
The total number of packets reassembled on this interface by the SAR, including OAM cells.
rx_bytes
The total number of bytes reassembled on this interface by the SAR, including AAL5 encapsulation bytes.
rx_total_resource_errs
The total number of packet reassemblies that failed due to resource exhaustion. This error includes rx_buffer_exhaust_errs.
This error is not likely to occur on the 4-port ATM ISE line card RX SAR, because it works in unidirectional mode with 64M buffers available only for reassemblies.
rx_total_other_errs
The total number of packet reassemblies that failed because of errors other than resource exhaustion (not including no-vc cells), including rx_crc32_errors, rx_packet_abort_errs, rx_trailer_len_errs, rx_mps_errors, and rx_reassembly_timeout.
Same value as Input Errors in the show interface command.
rx_buffer_exhast_errs
The total number of packet reassemblies that failed because of complete buffer exhaustion on the SAR. This is included in rx_total_resource_errs.
This error is not likely to occur on the 4-port ATM ISE line card RX SAR, because it works in unidirectional mode with 64M buffers available only for reassemblies.
Same value as Ignored in the show interface command.
rx_packet_abort_errs
The number of packet reassemblies that failed because of receiving a trailer length of 0. This is included in rx_total_other_errs.
Same value as Abort in the show interface command.
rx_mps_errors
The number of packet reassemblies that failed because of a packet size greater than the maximum allowed packet size. This is included in rx_total_other_errs.
Same value as Giants in the show interface command.
rx_crc32_errors
The number of packet reassemblies that failed because of an invalid AAL5 CRC32 trailer. This is included in rx_total_other_errs.
Same value as CRC in the show interface command.
rx_trailer_len_errs
The number of packet reassemblies that failed because of a packet whose AAL5 trailer had an invalid trailer length. This is included in rx_total_other_errs.
rx_reassembly_timeout
The number of packet reassemblies that failed because of timing out before receiving the last cell of a packet. This is included in rx_total_other_errs.
sys_rx_unopen_vc_cls
Packets received on nonexistent VC.
Also available in the show atm traffic command on the RP.
sys_ecc_errors
Total number of single bit errors detected on the reassembly SAR.
Note
Obtaining Per-VC Counters
To display per-VC counters, first you must determine what connection ID is associated with the VC. This procedure differs slightly, depending on the version of Cisco IOS you are running. The following procedure describes how to display the per-VC counters in Cisco IOS release 12.0(27)S or later.
Step 1
router# show atm pvcVCD/ Peak Avg/Min BurstInterface Name VPI VCI TYPE Encaps Kbps Kbps Cells Sts0/0.1 2 1 100 PVC SNAP 23000 N/A UPIn this example, the VCD for the VC whose VCI/VPI are 1/100 is 2.
Step 2
router# exec slot 0 show controller atm 0 traffic========= Line Card (Slot 0) =========VCID CONNID InPkts InBytes PktsInSW InOams OutPkts OutBytes2 1 0 0 0 0 0 0For the example above, the connID for VC 1/100 is 1.
Step 3
Router# exec slot 0 show controller atm 0 traffic 1========= Line Card (Slot 1) =======VCID: 2, CONNID: 1, VPI: 1, VCI: 100Rx Total Stats:rx_packets : 0 rx_bytes : 0rx_resource_err: 0 rx_other_err : 0rx_sw_packets : 0 rx_oam_cells : 0Tx Stats:COSQ #0 (ChID=010D)tx_packets : 0 tx_bytes : 0tx_resource_err: 0 tx_other_err : 0tx_queue_depth : 0 tx_avg_q_depth: 0.0000tx_random_drop : 0 tx_thresh_drop: 0COSQ #1 (ChID=010E)tx_packets : 0 tx_bytes : 0tx_resource_err: 0 tx_other_err : 0tx_queue_depth : 0 tx_avg_q_depth: 0.0000tx_random_drop : 0 tx_thresh_drop: 0COSQ #7 (ChID=010F)tx_packets : 0 tx_bytes : 0tx_resource_err: 0 tx_other_err : 0tx_queue_depth : 0 tx_avg_q_depth: 0.0000Tx Total Stats:tx_packets : 0 tx_bytes : 0tx_resource_err: 0 tx_other_err : 0Counters are available per queue opened on the specified VC. Each queue is linked to a class in the policy map attached to this VC. To associate a queue number to a class, use the command show policy interface (for example, show policy interface atm1/1.3).
Descriptions of the counters shown in this command are described in Table 9 and Table 10.
The following procedure describes how to display the per-VC counters in Cisco IOS releases 12.0(26)S and 12.0(25)S.
Step 1
router# show atm pvcVCD/ Peak Avg/Min BurstInterface Name VPI VCI TYPE Encaps Kbps Kbps Cells Sts0/0.1 2 1 100 PVC SNAP 23000 N/A UPIn this example, the VCD for the VC whose VCI/VPI are 1/100 is 2.
Step 2
Router# exec slot 0 show controller atm 0 traffic 2See the previous procedure for a description of the command output.
Debugging Unexpected TX Drops on a VC
Each interface is served by an egress SAR. All VCs transmitted by this interface share a pool of approximately 950,000 TX cell buffers available in the SAR.
Improper queueing configuration, using the queue-limit or random-detect commands, allows for long queues to build up in the SAR. In this case, if some VCs are oversubscribed, their queues might eventually exhaust the TX cell buffer pool. When no TX cell buffers are available, no VC can enqueue outbound packets, including such VCs that are not oversubscribed; that is, VC isolation is not maintained. This can be confirmed by checking the following counters while tx_resource_err is incrementing:
•
•
In a properly configured system, the tx_resource_err counter of a VC should only be incrementing when this specific VC is oversubscribed and dropping packets because the queue limit is being exceeded or because of WRED operation. This can be confirmed by checking the following counters while tx_resource_err is incrementing:
•
•
Note
Upgrading the FPGA Image
If the line card does not boot and you receive an error message indicating that there is a problem with the Field-Programmable Gate Array (FPGA) image (or if the line card alphanumeric LED display remains frozen in IOS STRT state), you need to upgrade the FPGA image using the update-fpga option in the diag command.
Note
When the Cisco IOS image boots, it verifies that a compatible FPGA image is running on the router. The major version number of the FPGA image must be the same as that expected by the Cisco IOS image; the minor version number on the FPGA image must be the same as or greater than the minor version number expected by the Cisco IOS image. For example, if the Cisco IOS image expects a minimum FPGA image of 03.02, the software will verify that the actual major version number of the FPGA image in the line card bootflash is 03, and that the minor version number is 02 or above.
Configuring Modular QoS CLI
The Modular QoS CLI (MQC) is a CLI structure that allows users to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to classify traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
Modular QoS CLI configuration includes the following three steps:
•
Defining a Traffic Class
The class-map command is used to create a traffic class. To create a traffic class containing match criteria, use the class-map command to specify the traffic class name, then use a match command in class map configuration mode.
The syntax of the class-map command is as follows:
class-map [match-any | match-all] class-name
no class-map [match-any | match-all] class-nameThe class-map match-all command is used when all the match criteria in the traffic class must be met for a packet to match the specified traffic class. The class-map match-any command is used when the first possible match criterion from a list of match criteria must be met for a packet to match the specified traffic class. If neither match-all nor match-any is specified, the traffic class will behave in a manner consistent with class-map match-all command.
For additional information on using the match-any and match-all options, see the "Using the class-map match-any and class-map match-all Commands" section.
Using the class-map match-any and class-map match-all Commands
This section illustrates the difference between the class-map match-any command and the class-map match-all command. The match-any and match-all options determine how packets are evaluated when multiple match criteria exist. Packets must either meet all of the match criteria (match-all) or one of the match criteria (match-any) in order to be considered a member of the traffic class.
The following example shows a traffic class configured with the class-map match-all command:
Router(config)# class-map match-all johnRouter(config-cmap)# match qos-group 4 Router(config-cmap)# match access-group 101If a packet arrives on a router with traffic class john configured on the interface, the packet is evaluated to see if it matches the IP protocol, QoS group 4, and access group 101. If both of these match criteria are met, the packet matches traffic class john.
The following example shows a traffic class configured with the class-map match-any command:
Router(config)# class-map match-any george Router(config-cmap)# match qos-group 4Router(config-cmap)# match access-group 101In traffic class george, the match criteria are evaluated consecutively until a successful match criterion is located. The packet is first evaluated to the see whether IP protocol can be used as a match criterion. If IP protocol can be used as a match criterion, the packet is matched to traffic class george. If IP protocol is not a successful match criterion, then QoS group 4 is evaluated as a match criterion. Each matching criterion is evaluated to see if the packet matches that criterion. Once a successful match occurs, the packet is classified as a member of traffic class george. If the packet matches none of the specified criteria, the packet is classified as a member of the default class.
Note that the class-map match-all command requires that all the match criteria must be met in order for the packet to be considered a member of the specified traffic class. However, only one match criterion must be met for the packet in the class-map match-any command to be classified as a member of the traffic class.
Creating a Traffic Policy
To configure a traffic policy, use the policy-map command to specify the traffic policy name, then use the following configuration commands to associate a traffic class, which was configured with the class-map command, with one or more QoS policies. The traffic class is associated with the traffic policy when the class command is used. The class command has to be issued immediately after entering policy map configuration mode. After entering the class command, you are automatically in policy map class configuration mode, which is where the QoS policies for the traffic policy are defined.
The QoS policies that can be applied in the traffic policy in policy map class configuration mode are detailed below.
The syntax of the policy-map command is:
policy-map policy-name
no policy-map policy-nameThe syntax of the class command is:
class class-name
no class class-nameIn addition to any user-defined classes, a pre-existing class named class-default exists. All packets that do not match any of the user-defined classes belong to class-default.
Commands for Egress Traffic
The following commands can be used to configure a traffic policy for egress traffic:
enable
Example:Router> enable
Enables privileged EXEC mode.
•
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
policy-map policy-name
Example:Router(config)# policy-map policy1
Specifies the name of the traffic policy to configure.
class class-name
Example:Router(config-pmap)# class class1
Router(config-pmap)# class class-default
Specifies the name of a predefined class, which was defined with the class-map command, to be included in the service policy. You can include the default class, class-default, in the traffic policy.
bandwidth {bandwidth-kbps | percent percent}
OR
bandwidth remaining percent percent
Example:Router(config-pmap-c)# bandwidth percent 20
Router(config-pmap-c)# bandwidth remaining percent 4
Specifies a minimum bandwidth guarantee to a traffic class.
A minimum bandwidth guarantee can be specified in kilobits per second (bandwidth-kbps) or as a percentage of the overall available bandwidth (percent percent). In this case, the bandwidth specified cannot exceed the available bandwidth remaining after the priority class is accounted for.
Alternatively, the minimum bandwidth guarantee can be based on the remaining bandwidth available (remaining percent percent). If there is no available bandwidth, then the class will receive no bandwidth, regardless of the percent specified.
police bps burst-normal burst-max conform-action action exceed-action action
Example:Router(config-pmap-c)# police 8000 2000 4000 conform-action transmit exceed-action drop
Specifies a bandwidth usage and conformance policy by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
priority
Specifies the class as the priority class.
In order to specify the maximum bandwidth allowed by the priority class, use the police command with the exceed-action set to drop. If no maximum bandwidth is specified for the priority class, remaining classes will not have a minimum bandwidth guarantee.
queue-limit cells cells
Example:Router(config-pmap-c)# queue-limit 576 cells
Specifies the maximum number of cells queued for a traffic class that has a bandwidth configuration or class default specified.
random-detect
Enables a weighted random early detection (WRED) drop policy for a traffic class that has a bandwidth configuration or class default specified.
random-detect dscp-based
Indicates that WRED is to use the DSCP value when it calculates the drop probability for the packet.
random-detect dscp dscpvalue min-threshold cells max-threshold cells [mark-probability-denominator]
Example:Router(config-pmap-c)# random-detect dscp 1 300 cells 700 cells 1
Specifies the minimum and maximum cell thresholds and, optionally, the mark-probability denominator for the DSCP value.
Note
random-detect precedence precedence min-threshold cells max-threshold cells [mark-prob-denominator
Example:Router(config-pmap-c)# random-detect precedence 4 500 cells 1100 cells 1
Specifies the minimum and maximum cell thresholds and, optionally, the mark-probability denominator for the precedence value.
Note
random-detect exponential-weighting-constant n
Example:Router(config-pmap-c)# random-detect exponential-weighting-constant 1
Configures a WRED exponential weighting constant on a per COS queue basis.
set atm-clp
Sets the ATM cell loss priority bit to 1.
set ip dscp ip-dscp-value
Example:Router(config-pmap-c)# set ip dscp 31
Specifies the IP DSCP of packets within a traffic class. The IP DSCP value can be any value between 0 and 63.
set ip precedence
Specifies the IP precedence of packets within a traffic class. The IP precedence value can be any value between 0 and 7.
set mpls experimental value
Designates the value to which the MPLS bits are set if the packets match the specified policy map.
Note
Note
Note
Note
Commands for Ingress Traffic
The following commands can be used to configure a traffic policy for ingress traffic:
enable
Example:Router> enable
Enables privileged EXEC mode.
•
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
policy-map policy-name
Example:Router(config)# policy-map policy1
Specifies the name of the traffic policy to configure.
class class-name
Example:Router(config-pmap)# class class1
Router(config-pmap)# class class-default
Specifies the name of a predefined class, which was defined with the class-map command, to be included in the traffic policy. You can include the default class, class-default, in the traffic policy.
police bps burst-normal burst-max conform-action action exceed-action action
Example:Router(config-pmap-c)# police 8000 2000 4000 conform-action transmit exceed-action drop
Specifies a bandwidth usage and conformance policy by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
police rate bps [burst mbs peak-rate peak] conform-action action exceed-action action violate-action action
Example:Router(config-pmap-c)# police rate 64000000 conform-action transmit exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. For a description of the conform-action and exceed-action keywords, see Table 5.
shape average mean-rate [burst-size [excess-burst-size]
Example:Router(config-pmap-c)# shape average 2000
Shapes ingress traffic to the indicated bit rate according to the algorithm specified.
queue-limit number-of-packets
Example:Router(config-pmap-c)# queue-limit 100
Specifies the maximum number of packets queued for a traffic class.
Note
random-detect
Enables a weighted random early detection (WRED) drop policy for a traffic class.
Note
random-detect dscp-based
Indicates that WRED is to use the DSCP value when it calculates the drop probability for the packet.
random-detect dscp dscpvalue min-threshold cells max-threshold cells [mark-probability-denominator]
Example:Router(config-pmap-c)# random-detect dscp 1 300 cells 700 cells 1
Specifies the minimum and maximum packet thresholds and, optionally, the mark-probability denominator for the DSCP value.
Note
random-detect precedence precedence min-threshold packets max-threshold packets [mark-prob-denominator
Example:Router(config-pmap-c)# random-detect precedence 4 500 packets 1100 packets 1
Specifies the minimum and maximum cell thresholds and, optionally, the mark-probability denominator for the precedence value.
Note
set ip dscp ip-dscp-value
Example:Router(config-pmap-c)# set ip dscp 31
Specifies the IP DSCP of packets within a traffic class. The IP DSCP value can be any value between 0 and 63.
set atm-clp
Sets the ATM cell loss priority bit to 1.
set ip precedence value
Example:Router(config-pmap-c)# set ip precedence 5
Specifies the IP precedence of packets within a traffic class. The IP precedence value can be any value between 0 and 7.
set mpls experimental [imposition | topmost] value
Example:Router(config-pmap-c)# set mpls experimental 4
Designates the value to which the MPLS experimental bits are set if the packets match the specified policy map.
set qos-group value
Example:Router(config-pmap-c)# set qos-group 45
Specifies a QoS group value to associate with the packet. The QoS group value can be any value between 0 and 99.
Attaching a Traffic Policy to a PVC
Use the service-policy interface configuration command to attach a traffic policy to a VC and to specify the direction in which the policy should be applied (either on packets coming into the interface or packets leaving the interface).
Use the no form of the command to detach a traffic policy from a VC. The service-policy command syntax is as follows:
service-policy {input | output} policy-map-name
no service-policy {input | output} policy-map-nameAdditional References
The following sections provide references related to the 4-port ATM ISE line card.
Related Documents
You can find additional information in the installation and configuration guide for your Cisco 12000 Series Router and in the Cisco IOS Release 12.0 documentation set.
Standards
MIBs
In addition to industry-standard Simple Network Management Protocol (SNMP) and other Management Information Bases (MIBs) supported on the Cisco 12000 Series Router, the 4-Port ATM ISE line card supports the following:
•
•
•
•
•
•
•
•
•
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.
police rate
To configure traffic policing, use the police rate command in policy-map class configuration mode. To remove traffic policing from the configuration, use the no form of this command.
police rate pcr cps delay-tolerance cdvt conform-action action exceed-action action violate-action action
police rate scr cps atm-mbs mbs cells conform-action action exceed-action action violate-action action
no police rate {pcr | scr}
Syntax Description
Defaults
Disabled
Command Modes
Policy-map class configuration
Command History
12.0(27)S
This command was introduced with the rate keyword. This command replaces the police command which was introduced in release 12.0(5)XE.
Usage Guidelines
Use the police command to mark a packet with different quality of service (QoS) values based on conformance to the service-level agreement.
Traffic policing will not be executed for traffic that passes through an interface.
Specifying Multiple Actions
The police command allows you to specify multiple policing actions. When specifying multiple policing actions when configuring the police command, note the following points:
•
•
Using the Police Command with the Traffic Policing Feature
The police rate command can be used with the Traffic Policing feature. The Traffic Policing feature works with a token bucket algorithm. Two types of token bucket algorithms are in Cisco IOS Release 12.1(5)T: a one-token bucket algorithm and a two-token bucket algorithm. A one-token bucket system is used when the violate-action option is not specified, and a two-token bucket system is used when the violate-action option is specified.
The token bucket algorithm for the police command that was introduced in Cisco IOS Release 12.0(5)XE is different from the token bucket algorithm for the police command introduced in Cisco IOS Release 12.1(5)T. For information on the token bucket algorithm introduced in Release 12.0(5)XE, refer to the Traffic Policing document for Release 12.0(5)XE. This document is available on the New Features for 12.0(5)XE feature documentation index (under Modular QoS CLI-related feature modules) at www.cisco.com.
The following are explanations of how the token bucket algorithms introduced in Cisco IOS Release 12.1(5)T work.
Token Bucket Algorithm with One Token Bucket
The one-token bucket algorithm is used when the violate-action option is not specified in the police rate command command-line interface (CLI).
The conform bucket is initially set to the full size (the full size is the number of bytes specified as the normal burst size).
When a packet of a given size (for example, "B" bytes) arrives at specific time (time "T") the following actions occur:
•
(time between packets <which is equal to T - T1> * policer rate)/8 bytes
•
•
Token Bucket Algorithm with Two Token Buckets
The two-token bucket algorithm is used when the violate-action option is specified in the police rate command CLI.
The conform bucket is initially full (the full size is the number of bytes specified as the normal burst size).
The exceed bucket is initially full (the full exceed bucket size is the number of bytes specified in the maximum burst size).
The tokens for both the conform and exceed token buckets are updated based on the token arrival rate, or committed information rate (CIR).
When a packet of given size (for example, "B" bytes) arrives at specific time (time "T") the following actions occur:
•
The token arrival rate is calculated as follows:
(time between packets <which is equal to T-T1> * policer rate)/8 bytes
•
•
•
Examples
The following example drops traffic that does not conform to the specified rate:
Router(config-pmap-c)# police rate 64000000 conform-action transmit exceed-action dropRelated Commands
random-detect dscp
To change the minimum and maximum cell thresholds for the differentiated services code point (DSCP) value, use the random-detect dscp command in interface configuration mode. To return the minimum and maximum packet thresholds to the default for the DSCP value, use the no form of this command.
random-detect dscp dscpvalue min-threshold cells max-threshold cells [mark-probability-denominator]
no random-detect dscp dscpvalue min-threshold max-threshold [mark-probability-denominator]
Syntax Description
Command Modes
Interface configuration
Command History
Usage Guidelines
The random-detect dscp command allows you to specify the DSCP value. The DSCP value can be a number from 0 to 63, or it can be one of the following keywords: ef, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, or cs7.
This command must be used in conjunction with the random-detect (interface) command.
Additionally, the random-detect dscp command is available only if you specified the dscp-based argument when using the random-detect (interface) command.
Examples
The following example enables WRED to use the DSCP value af22. The minimum threshold for DSCP value af22 is 28, the maximum threshold is 40, and the mark probability is 10.
random-detect dscp af22 28 cells 40 cells 10Related Commands
random-detect (interface)
Enables WRED.
random-detect exponential-weighting-constant
Configures the WRED exponential weight factor for the average queue size calculation.
Glossary
Note
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
1 Subject to overall system limitation and configuration.
2 Subject to overall system limitation and configuration.
