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
•
Restrictions for the 4-Port ATM ISE Line Card
•
Information About the 4-Port ATM ISE Line Card
•
How to Perform a Basic Configuration of the 4-Port ATM ISE Line Card
•
How to Configure Layer 3 Terminated VCs on the 4-Port ATM ISE Line Card
•
How to Configure AToM VCs on the 4-Port ATM ISE Line Card
•
Troubleshooting ATM Errors on 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
Feature LimitationMaximum 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
Feature Layer 2 LimitationMaximum 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:
•
Traffic shaping on a per-VC and per-virtual path (VP) basis with a minimum granularity of 1 Kbps, in compliance with I.371 granularity definition.
•
Per-VC queueing using configurable per-VC queue limits or per-VC WRED.
•
A VC address can be any of the virtual path identifier (VPI) and virtual channel identifier (VCI) range. User-network interface (UNI) VPIs can be in the range of 0..255; network-to-network interface (NNI) VPIs can be in the range of 0..4095. VCIs can be in the range 0..65,535.
•
Per-VC statistics through hardware.
•
Per-port statistics through hardware.
•
AAL5 [I.362] [I.363] reassembly and segmentation.
•
Non-real-time variable bit rate (VBR-nrt) and real time variable bit rate (VBR-rt) traffic shaping with 99+ percent shaping accuracy.
•
Constant bit rate (CBR) traffic shaping with 99+ percent shaping accuracy.
•
Unspecified bit rate (UBR) with support for optional peak cell rate (PCR) parameter with 99+ percent shaping accuracy.
•
VP tunnel traffic shaping for the full range of VPI on UNI interfaces—up to 256 VP tunnels per port.
•
Maximum transmission unit (MTU) of up to 9180 bytes.
•
Each VC supports up to 9K MTU.
•
F4 and F5 flows of operation, administration, and maintenance (OAM) cells and OAM management specified as requirements by [UNI 3.x] [I.610].
Layer 3-Specific Features
•
Supports up to 2047 traffic-shaped VC connections per interface.1
•
Bidirectional OC-12c/STM-4c line rate for 64-byte packets (two cells) on all four ports. This is an aggregate line rate of approximately 2.8 million packets per second.
•
Bidirectional OC-3c/STM-1 full line rate for any packet size on all four ports.
•
Support for up to 120 distinct WRED profiles per interface. These profiles are configurable using Cisco IOS software.
•
ATM VC bundle management.
•
MPLS Traffic Engineering (TE), including Single Area (OSPF,ISIS), DS-TE (OSPF,ISIS), Autobandwidth, TE Metrics (OSPF,ISIS), TE Node Exclusion (OSPF,ISIS), Multiarea (OSPF,ISIS).
•
Support for thousands of ACL/xACL entries, including both ingress and egress for interfaces and subinterfaces.
•
Committed Access Rate (CAR), including CAR action continue, including both ingress and egress for interfaces and subinterfaces.
•
Policy-based routing (PBR) for interfaces and subinterfaces.
•
Border Gateway Protocol (BGP) policy accounting.
•
Unicast reversepath forwarding (uRPF) loose mode.
•
Sophisticated MQC classifications based on IP ACL/xACL, IP precedence/DSCP, MPLS EXP, QoS groups, and more.
•
IP and MPLS traffic marking
•
QoS Policy Propagation via BGP (QPPB)
•
Ingress IP-based traffic shaping.
•
Netflow, including sampled ingress/egress Netflow, aggregated Netflow, and MPLS-aware Netflow.
•
High Availability, including route processor redundancy (RPR), RPR+, and Stateful Switchover (SSO).
•
ATM OAM F5 continuity check.
•
MPLS virtual private network (VPN).
•
UNI 3.x and Interim Local Management Interface (ILMI).
•
Switched virtual circuit (SVC) support for point-to-point and point-to-multipoint connections.
•
Multicast packet replication.
•
ATM cell loss priority (CLP) bit setting.
•
MPLS VPN Inter-AS.
•
MPLS VPN carrier supporting carrier (CsC).
Layer 2-Specific Features
•
Supports up to 2047 traffic-shaped VC connections per interface.2
•
Any Transport over Multiprotocol Label Switching (MPLS) [AToM].
•
ATM OAM Emulation
•
Cell-based policing
•
Experimental bit marking
•
Cell packing for port, VC, and VP modes
•
Cell relay for port, VC, and VP modes
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 UNI and NNI Cell Support
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.
show version
2.
show interfaces
3.
enable
4.
configure terminal
5.
interface atmslot/port
6.
no shutdown
7.
Ctrl-Z
8.
copy running-config startup-config
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
•
Configuring ATM Shaping on Terminated VCs
•
Configuring OAM Management on Terminated VCs
•
Configuring Quality of Service on Terminated VCs
•
Configuring and Managing VC Bundles
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:
•
Quality of service (QoS)
•
ATM adaptation layer (AAL) mode
•
Encapsulation type (LLC/SNAP, IP MUX, and NLPID)
•
Peak and average transmission rates
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:
Command PurposeRouter# 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:
•
Constant bit rate (CBR)—Supports real-time applications that request a static amount of bandwidth that is continuously available for the duration of the connection. (See Step 5.)
•
Real-time variable bit rate (VBR-rt)—Supports real-time applications that have bursty transmission characteristics. (See Step 6.)
•
Non-real-time variable bit rate (VBR-nrt)—Supports non-real-time applications with bursty transmission characteristics that tolerate high cell delay, but require low cell loss. (See Step 7.)
•
Unspecified bit rate (UBR)—Supports non-real-time applications that tolerate both high cell delay and cell loss on the network. There are no network service-level guarantees for the UBR service category, and therefore it is a best-effort service. (See Step 8.)
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
For VBR connections in which the sustainable cell rate (SCR) is not equal to the PCR value, the CDVT is significantly lower.
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.
enable
2.
configure terminal
3.
interface atmslot/port.subinterface
4.
pvc vpi/vci
5.
cbr pcr
6.
vbr-rt pcr scr
7.
vbr-nrt pcr scr
8.
ubr pcr
DETAILED STEPS
Command or Action PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
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
cbr pcrRouter(config-if-vc)# cbr 155000Specifies CBR shaping.
The pcr value indicates the peak cell rate. The range is from 38 to 622,000 Kbps.
Note
Use either Step 5, Step 6, Step 7, or Step 8.
Step 6
vbr-rt pcr scr burstExample: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
vbr-nrt pcr scr mbsExample: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
ubr pcrExample: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.
enable
2.
configure terminal
3.
interface atmslot/port.subinterface [point-to-point | multipoint]
4.
pvc vpi/vci
5.
oam-pvc manage
6.
oam retry up-count down-count retry-frequency
7.
oam-pvc manage cc {end | segment} [direction {both | sink | source}] [keep-vc-up [end aisrdi failure | seg aisrdi failure]]
8.
oam retry cc {end | segment} [activation-count [deactivation-count [retry-frequency]]]
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 does not receive a loopback reply after a configured number of retries of sending end-to-end F5 OAM loopback cells.
•
The router receives a Virtual Circuit-Alarm Indication Signal (VC-AIS) cell.
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:
•
The router receives a configured number of successive end-to-end F5 OAM loopback cell replies.
•
The router does not receive VC-AIS cell for 3 seconds.
•
The router does not receive VC-RDI cell for 3 seconds.
Note the following regarding OAM management:
•
When OAM management is not enabled, loopback (LB) cells received by the PVC are looped back to the sender, and for any received F4/F5-AIS, F4/F5-RDI cells are transmitted via this PVC, but the PVC state is not changed.
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 a Per-VC Queue Limit
•
Configuring Per-VC MDRR and Low Latency Queueing
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.
enable
2.
configure terminal
3.
class-map class-map-name
4.
match access-group access-group
5.
exit
6.
policy-map policy-name
7.
class class-name
8.
police bps burst-normal burst-max conform-action action exceed-action action violate-action action
9.
exit
10.
exit
11.
interface atmslot/port.subifnum
12.
pvc vpi/vci
13.
service-policy {input | output} policy-name
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.
enable
2.
configure terminal
3.
policy-map policy-name
4.
class class-default
5.
queue-limit cells cells (for egress queue) or queue-limit packets packets (for ingress queue)
6.
exit
7.
exit
8.
interface atmslot/port.subifnum
9.
pvc vpi/vci
10.
service-policy {input | output} policy-name
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
•
Random-detect cannot be configured on a class that has priority configured.
•
No more than three different Random Early Detection (RED) profiles can be configured on one class of service (COS) queue.
SUMMARY STEPS
For precedence-based WRED use

