1. © 2001, Cisco Systems, Inc. IP over ATM

2. © 2001, Cisco Systems, Inc. QOS v1.0—10-2 Objectives Upon completing this module, you will be able to: List the requirements of IP QoS in combination with ATM QoS Describe the hardware and software requirements for advanced IP QoS mechanisms on ATM interfaces Describe per-VC queuing Describe and configure per-VC WRED Describe and configure VC bundling Describe and configure per-VC CBWFQ Describe RSVP-to-SVC mapping Monitor and troubleshoot IP QoS on ATM interfaces

3. Introduction to IP over ATM © 2001, Cisco Systems, Inc. QOS v1.0—10-3

4. © 2001, Cisco Systems, Inc. QOS v1.0—10-4 Objectives Upon completing this lesson, you will be able to: Describe the QoS problems related to use of ATM networks Describe the hardware and software requirements for advanced IP QoS mechanisms on ATM interfaces Describe per-VC queuing

5. © 2001, Cisco Systems, Inc. QOS v1.0—10-5 IP vs. ATM Technology Comparison IP Connectionless Per-packet QoS (IP Precedence) Small number of service classes IP Precedence and DSCP do not encode service parameters ATM Connection oriented Per-connection (virtual circuit) QoS Large number of QoS traffic classes (CBR, VBR, UBR, ABR) Rich traffic parameters (PCR, MCR, SCR, etc.) specified for each VC

6. © 2001, Cisco Systems, Inc. QOS v1.0—10-6 Integrating IP and ATM Overlay model (ATM forum): –ATM VCs are manually established between pairs of devices. –IP packets are sent across these VCs. –ATM switches are not IP-aware. Peer model (MPLS): –ATM switches are IP-aware on the control (but not data) plane. –ATM VCs are established on-demand based on IP routing tables.

7. © 2001, Cisco Systems, Inc. QOS v1.0—10-7 IP QoS and ATM Routers can be interconnected over an ATM backbone using different ATM services: –UBR–congestion management virtually impossible because routers are allowed to transmit packets at line speed –VBR–congestion management easier, but requires conservative setting of transmit rates –CBR–similar to VBR from IP perspective –ABR–pushes congestion back to the source, requiring dynamic adjustment to available bandwidth

8. © 2001, Cisco Systems, Inc. QOS v1.0—10-8 UBR Virtual Circuits Solution: –Set CLP on the router based on IP information to minimize the effect of cell drops No congestion: Router allowed to send at full speed No congestion: Router allowed to send at full speed Random CLP marking Random CLP marking Congestion Unintelligent drops based on CLP

9. © 2001, Cisco Systems, Inc. QOS v1.0—10-9 VBR Virtual Circuits Solution: –Set CLP on the router based on IP information –Use available IP QoS mechanisms to manage congestion at the source Router is sending at configured rate. Congestion! Congestion is possible. Unintelligent random drops

10. © 2001, Cisco Systems, Inc. QOS v1.0—10-10 CBR and ABR Virtual Circuits Solution: –Use available IP QoS mechanism to handle congestion at the source Router is sending at configured rate. Congestion!

11. © 2001, Cisco Systems, Inc. QOS v1.0—10-11 Congestion Management in ATM Networks Congestion management on routers should be performed on a per-VC basis. Design options: –Make sure there is no congestion in the ATM network (ABR, CBR, VBR) and use IP QoS mechanisms at the source (CBWFQ, WRED) –Mark less important packets with the CLP bit in case there is congestion in the ATM network (class-based policing, class-based marking) –Use multiple parallel (per-CoS) virtual circuits with ATM QoS (VC bundling)

12. © 2001, Cisco Systems, Inc. QOS v1.0—10-12 Per-VC Queuing Per-VC queuing is required in order to handle congestion on a per-VC basis. Per-VC queuing prevents head-of-line blocking by slow virtual circuits. ATM Port Adapter VC 1/50 VC 1/64 VC 1/76 VC 1/39 ATM Interface Cell queue VC 1/50 Cell queue VC 1/64 Cell queue VC 1/76 Cell queue VC 1/39 VIP Memory Frame queue VC 1/50 Frame queue VC 1/64 Frame queue VC 1/76 Frame queue VC 1/39 ATM Hardware Shaping Per-VC Queuing with Per-VC Congestion Management

13. © 2001, Cisco Systems, Inc. QOS v1.0—10-13 Summary Upon completing this lesson, you should be able to: Describe the QoS problems related to use of ATM networks Describe the hardware and software requirements for advanced IP QoS mechanisms on ATM interfaces Describe per-VC queuing

14. © 2001, Cisco Systems, Inc. QOS v1.0—10-14 Review Questions 1.What are the main differences between IP and ATM? 2.Which QoS services does ATM support? 3.How should congestion be handled when an ATM backbone is used? 4.Why is per-VC queuing so important?

15. © 2001, Cisco Systems, Inc. QOS v1.0—10-15 Per-VC WRED © 2001, Cisco Systems, Inc. QOS v1.0—10-15

16. © 2001, Cisco Systems, Inc. QOS v1.0—10-16 Objectives Upon completing this lesson, you will be able to: Describe per-VC WRED Configure per-VC WRED Monitor and troubleshoot per-VC WRED

17. © 2001, Cisco Systems, Inc. QOS v1.0—10-17 Per-VC WRED A single ATM VC is established over an ATM cloud between a pair of routers: –ABR, VBR, UBR, or CBR –Using UBR will not result in proper operation, as there is no ATM shaping in UBR All IP traffic toward a next-hop router is forwarded across a single ATM VC Congestion is managed entirely on the IP layer using WRED on each individual ATM VC, resulting in differentiated IP services

18. © 2001, Cisco Systems, Inc. QOS v1.0—10-18 Per-VC WRED: Intelligent IP Packet Discard VIP2-50PA-A3-XX Per-VC WRED: Intelligent Discard Per-VC Threshold Exceeded VC1 VC2 VC3 No Discard on PA No Discard on PA TrafficShapingTrafficShaping Per-VCQueuesPer-VCQueues

19. © 2001, Cisco Systems, Inc. QOS v1.0—10-19 Configuring Per-VC WRED Follow these configuration steps to enable per-VC WRED: –Create a Random Detect Group template with a WRED profile –Apply the WRED template to an ATM interface or to individual ATM VCs –Verify and monitor the operation of per-VC WRED

20. © 2001, Cisco Systems, Inc. QOS v1.0—10-20 random-detect-group name Router(config)# Creates a WRED template Create and Configure RED-group exponential-weighting-constant exp Router(cfg-red-group)# Defines WRED weighting constant Default: 9 precedence IP-prec min-threshold max-threshold prob-denominator Router(cfg-red-group)# Defines RED profile for specified precedence Default: as with per-interface WRED

21. © 2001, Cisco Systems, Inc. QOS v1.0—10-21 Apply WRED Group to an ATM PVC random-detect [attach random-detect-group] Router(config-if-atm-vc)# Enables WRED on a PVC using the selected WRED profile Default WRED parameters are used if the group name is omitted or refers to a nonexistent group Default: No WRED is used on the ATM PVC

22. © 2001, Cisco Systems, Inc. QOS v1.0—10-22 show queueing random-detect [interface intf [vc vpi vci ]] Router# Displays WRED parameters for an ATM (sub)interface or individual VC Monitoring and Troubleshooting Per-VC WRED show queueing interface interface [vc vpi vci] Router# Displays interface queues or individual per-VC queue

23. © 2001, Cisco Systems, Inc. QOS v1.0—10-23 WRED Case Study WRED is applied to ATM PVCs in a network with these IP Precedence definitions: IP Prec. Meaning 0High-loss, best-effort traffic 1Low-loss, best-effort traffic 2Premium traffic outside of the contract 3Premium traffic in the contract 4Unused 5Voice over IP 6Routing protocol traffic 7Routing protocol traffic The WRED queue length is 100 packets for PVCs with SCR > 10 Mbps, and 40 packets for slower PVCs.

24. © 2001, Cisco Systems, Inc. QOS v1.0—10-24 Case Study WRED Profile Packet Discard Probability Average Queue Size 0.1 RSVP 15102025303537 Precedence 2 Precedence 0 Precedence 3 Precedence 1 VoIP Routing

25. © 2001, Cisco Systems, Inc. QOS v1.0—10-25 Router Configuration Step #1: Configure WRED profile for slow PVCs random-detect-group slow-wred-profile precedence 0 10 25 10 precedence 1 20 40 10 precedence 2 15 25 10 precedence 3 25 40 10 precedence 4 1 10 10 precedence 5 35 40 10 precedence 6 30 40 10 precedence 7 30 40 10 random-detect-group slow-wred-profile precedence 0 10 25 10 precedence 1 20 40 10 precedence 2 15 25 10 precedence 3 25 40 10 precedence 4 1 10 10 precedence 5 35 40 10 precedence 6 30 40 10 precedence 7 30 40 10

26. © 2001, Cisco Systems, Inc. QOS v1.0—10-26 Router Configuration (cont.) Step #2: Configure WRED profile for fast PVCs random-detect-group fast-wred-profile precedence 0 25 62 10 precedence 1 50 100 10 precedence 2 37 62 10 precedence 3 62 100 10 precedence 5 87 100 10 precedence 4 1 10 10 precedence 6 75 100 10 precedence 7 75 100 10 random-detect-group fast-wred-profile precedence 0 25 62 10 precedence 1 50 100 10 precedence 2 37 62 10 precedence 3 62 100 10 precedence 5 87 100 10 precedence 4 1 10 10 precedence 6 75 100 10 precedence 7 75 100 10

27. © 2001, Cisco Systems, Inc. QOS v1.0—10-27 Router Configuration (cont.) Step #3: Apply WRED profile on various PVCs interface ATM11/0/0 ip address 17.1.0.1 255.255.255.0 atm pvc 50 0 50 aal5snap 25000 50000 10 inarp random-detect fast-wred-profile ! interface ATM11/0/0.100 point-to-point ip address 17.1.1.1 255.255.255.252 atm pvc 100 0 100 aal5snap 17000 34000 10 inarp random-detect fast-wred-profile ! interface ATM11/0/0.101 point-to-point ip address 17.1.1.5 255.255.255.252 atm pvc 101 5 101 aal5snap 2000 4000 10 inarp random-detect slow-wred-profile interface ATM11/0/0 ip address 17.1.0.1 255.255.255.0 atm pvc 50 0 50 aal5snap 25000 50000 10 inarp random-detect fast-wred-profile ! interface ATM11/0/0.100 point-to-point ip address 17.1.1.1 255.255.255.252 atm pvc 100 0 100 aal5snap 17000 34000 10 inarp random-detect fast-wred-profile ! interface ATM11/0/0.101 point-to-point ip address 17.1.1.5 255.255.255.252 atm pvc 101 5 101 aal5snap 2000 4000 10 inarp random-detect slow-wred-profile

28. © 2001, Cisco Systems, Inc. QOS v1.0—10-28 Summary Upon completing this lesson, you should be able to: Describe per-VC WRED Configure per-VC WRED Monitor and troubleshoot per-VC WRED

29. © 2001, Cisco Systems, Inc. QOS v1.0—10-29 Review Questions 1.What are the benefits of per-VC WRED? 2.What are the configuration steps needed to enable per-VC WRED?

30. © 2001, Cisco Systems, Inc. QOS v1.0—10-30 VC Bundling © 2001, Cisco Systems, Inc. QOS v1.0—10-30

31. © 2001, Cisco Systems, Inc. QOS v1.0—10-31 Objectives Upon completing of this lesson, you will be able to: Describe VC bundling Configure VC bundling Monitor and troubleshoot VC bundling

32. © 2001, Cisco Systems, Inc. QOS v1.0—10-32 VC Bundling VC bundling is a solution in which ATM QoS mechanisms are used. Classes of service are identified by IP Precedence. Each VC uses an ATM service based on the requirements of the class. Routers automatically map packets in VCs based on their IP Precedence value. Multiple parallel VCs are needed for each IP adjacency.

33. © 2001, Cisco Systems, Inc. QOS v1.0—10-33 VC Bundling Case Study ATM VCATM VC Type IP Prec. Control VC (routing updates)VBR6-7 VoiceCBR5 VPN trafficVBR4 Premium Internet trafficVBR2-3 Best-effort Internet trafficABR0-1 Control ( R outing) Voice VPN T raffic Premium Internet Best- E ffort Internet

34. © 2001, Cisco Systems, Inc. QOS v1.0—10-34 Control ( R outing) Voice VPN T raffic Premium Internet Best- E ffort Internet VC Bundling Routing Adjacency The whole bundle is treated as one routing adjacency and is covered by a single ATM map. Routing protocol packets are exchanged over the control VC as they are sent with IP Precedence 6. Each VC has its own hardware queue in the router, managed with WRED.

35. © 2001, Cisco Systems, Inc. QOS v1.0—10-35 VC Provisioning VCs are dimensioned based on expected load for the precedence level(s) transported on that VC More isolation between classes At the expense of: –Less statistical multiplexing –More complex provisioning/engineering

36. © 2001, Cisco Systems, Inc. QOS v1.0—10-36 VC Bundle Management The integrity of each individual VC is verified with end-to-end OAM cells. Control ( R outing) Voice VPN T raffic Premium Internet Best- E ffort Internet

37. © 2001, Cisco Systems, Inc. QOS v1.0—10-37 VC Bundle Management (cont.) Control ( R outing) Voice VPN T raffic Best- E ffort Internet Two ways of handling loss of VC in the bundle: –The whole bundle is declared down –Traffic from the lost VC is bumped onto another VC The IP routing model does not allow the traffic for a single precedence value to be rerouted over another path.

38. © 2001, Cisco Systems, Inc. QOS v1.0—10-38 VC Bumping VC bumping = possibility for traffic mapped to VC X to be forwarded onto VC Y, in case of failure of X. Traffic can be bumped based on implicit or explicit rules. An individual VC or a group of VCs can be protected.

39. © 2001, Cisco Systems, Inc. QOS v1.0—10-39 Implicit Bumping Control ( R outing) Voice VPN T raffic Best- E ffort Internet Traffic from the lost VC is bumped onto the VC carrying traffic with the next lower precedence.

40. © 2001, Cisco Systems, Inc. QOS v1.0—10-40 Reject Bumping Problem: Control traffic shall not be bumped onto voice VC (implicit rule). Solution #1: Voice VC can reject bumping; bumped traffic goes to next lower VC. Voice VPN T raffic Premium Internet Best- E ffort Internet Rejects bumping

41. © 2001, Cisco Systems, Inc. QOS v1.0—10-41 Voice VPN T raffic Premium Internet Best- E ffort Internet Explicit Bumping Problem: Control traffic shall not be bumped onto voice VC (implicit rule). Solution #2: Specify explicitly onto which VC the traffic will be bumped. Bump explicitly to Precedence 0

42. © 2001, Cisco Systems, Inc. QOS v1.0—10-42 Bundle Failure Scenarios Problem: Under default settings, the whole bundle is declared down if the lowest-precedence VC is lost. Solution: Be sure that the lowest-precedence VC is always bumped via the explicit bumping rule. Precedence 0 traffic cannot be implicitly bumped. Whole bundle is lost. Control ( R outing) VPN T raffic Premium Internet Voice When a bundle is declared down, no traffic is forwarded out of the bundle, even if some VCs are still up.

43. © 2001, Cisco Systems, Inc. QOS v1.0—10-43 Protected VC Problem: Voice traffic shall not be bumped onto data VC. Solution: Failure of the protected VC brings down the whole bundle; IP routing will find an alternate path. Voice VC is protected VC. Whole bundle is lost. Control ( R outing) VPN T raffic Premium Internet Best- E ffort Internet

44. © 2001, Cisco Systems, Inc. QOS v1.0—10-44 Protected Group Problem: If most of the VCs are lost, it does not make sense to bump traffic onto low-volume VCs. Solution: Failure of all VCs in a protected group will bring down the bundle. Whole bundle is lost. Control ( R outing) Voice All VCs in the protected group are lost.

45. © 2001, Cisco Systems, Inc. QOS v1.0—10-45 VC Bumping—Final Details If the VC that carries the bumped traffic fails, the traffic will follow the bumping rules specified for that VC. Traffic is restored to the original VC when the VC carrying the bumped traffic.

46. © 2001, Cisco Systems, Inc. QOS v1.0—10-46 Configuring VC Bundling Configuration steps: –Configure ATM interface –Configure VC bundle –Configure individual VCs in the bundle –Optionally, use VC-class object as VC parameter template

47. © 2001, Cisco Systems, Inc. QOS v1.0—10-47 VC Bundle Parameters Parameters configurable on the VC bundle or vc-class template applied to the bundle: –Layer 3 ATM maps –Encapsulation –Broadcast propagation –ATM Inverse ARP –OAM management –Global bumping rules

48. © 2001, Cisco Systems, Inc. QOS v1.0—10-48 Individual VC Parameters Parameters configurable on individual VCs in the bundle (or vc-class template): –IP Precedence mapping –VC protection mode –VC bumping rules –ATM VC mode and ATM QoS parameters –WRED group

49. © 2001, Cisco Systems, Inc. QOS v1.0—10-49 Configuring a Bundle-Wide VC Class class-vc vc-class-name oam-bundle [manage] [frequency] bump {implicit | explicit precedence-level | traffic} encapsulation atm-encap protocol atm-map-parameters … [no] broadcast inarp timeout class-vc vc-class-name oam-bundle [manage] [frequency] bump {implicit | explicit precedence-level | traffic} encapsulation atm-encap protocol atm-map-parameters … [no] broadcast inarp timeout Router(config)# Configures all parameters that can be specified on an ATM VC bundle in a VC class

50. © 2001, Cisco Systems, Inc. QOS v1.0—10-50 Configuring an ATM VC Bundle bundle bundle-name class vc-class-name oam-bundle [manage] [frequency] bump {implicit | explicit precedence-level | traffic} encapsulation atm-encap protocol atm-map-parameters … [no] broadcast inarp timeout bundle bundle-name class vc-class-name oam-bundle [manage] [frequency] bump {implicit | explicit precedence-level | traffic} encapsulation atm-encap protocol atm-map-parameters … [no] broadcast inarp timeout Router(config-if)# Configures an ATM VC bundle If a vc-class template is applied to the bundle, the bundle inherits parameters specified in the vc-class template Individual parameters specified in the vc-class template can be overwritten by bundle configuration commands

51. © 2001, Cisco Systems, Inc. QOS v1.0—10-51 oam-bundle [manage] [frequency] Router(config-atm-vc)# Enables VC management with end-to-end OAM cells Cells are sent, but the bundle is not managed if the manage keyword is omitted The frequency parameter specifies the cell generation rate in seconds Configuring OAM Management in the Bundle oam retry up-count down-count retry-frequency Router(config-atm-vc)# Specifies the OAM management-related thresholds The up-count and down-count parameters specify the number of consecutive cells that have to be received (or lost) before the VC is declared up or down The retry-frequency parameter specifies the cell send frequency during VC state change verification

52. © 2001, Cisco Systems, Inc. QOS v1.0—10-52 bump implicit Router(config-atm-vc)# Configures implicit bumping rules for the bundle or individual VC in the bundle If the VC fails, the traffic is bumped to the VC carrying lower-precedence traffic Configuring Traffic Bumping bump explicit precedence Router(config-atm-vc)# Configures explicit bumping rules for the bundle or individual VC in the bundle If the VC fails, the traffic is bumped to the VC currently carrying packets with specified IP Precedence

53. © 2001, Cisco Systems, Inc. QOS v1.0—10-53 no bump traffic Router(config-atm-vc)# Prevents the VC (or all VCs in a bundle) from accepting bumped traffic Configuring Traffic Bumping bump traffic Router(config-atm-vc)# Allows the VC (or all VCs in a bundle) to accept bumped traffic

54. © 2001, Cisco Systems, Inc. QOS v1.0—10-54 Configuring a VC-Wide VC Class class-vc vc-class-name precedence [other | range ] bump {implicit | explicit precedence-level | traffic} protect {group | vc } ubr | ubr+ | vbr-nrt atm-qos-parameters random-detect [attach group-name] class-vc vc-class-name precedence [other | range ] bump {implicit | explicit precedence-level | traffic} protect {group | vc } ubr | ubr+ | vbr-nrt atm-qos-parameters random-detect [attach group-name] Router(config)# Configures all parameters that can be specified on an ATM VC within the bundle in a VC class

55. © 2001, Cisco Systems, Inc. QOS v1.0—10-55 Configuring an ATM VC in a Bundle bundle bundle-name pvc name [vpi/]vci class vc-class-name precedence [other | range ] bump {implicit | explicit precedence-level | traffic} protect {group | vc} ubr | ubr+ | vbr-nrt atm-qos-parameters random-detect [attach group-name] bundle bundle-name pvc name [vpi/]vci class vc-class-name precedence [other | range ] bump {implicit | explicit precedence-level | traffic} protect {group | vc} ubr | ubr+ | vbr-nrt atm-qos-parameters random-detect [attach group-name] Router(config-if)# Configures an individual VC in an ATM VC bundle If a vc-class template is applied to the VC, the VC inherits parameters specified in the vc-class template Individual parameters specified in the vc-class template can be overwritten by bundle configuration commands Unspecified VC parameters are inherited from the bundle or from the ATM interface

56. © 2001, Cisco Systems, Inc. QOS v1.0—10-56 Map IP Precedence to an ATM VC precedence [other | range ] Router(config-atm-vc)# Maps packets with a specified range of IP Precedence into the configured ATM VC All the unmapped IP Precedence values are mapped to the VC specifying “other” Default: VC accepts all unspecified IP traffic

57. © 2001, Cisco Systems, Inc. QOS v1.0—10-57 VC Protection protect { group | vc } Router(config-atm-vc)# Configures the VC to be part of a protected group or to be individually protected A bundle is declared down if all VCs in the protected group are lost or if any individually protected VC is lost Only one protected group can be configured in a bundle Default: VC is not protected

58. © 2001, Cisco Systems, Inc. QOS v1.0—10-58 VC Inheritance Rules VC parameters are inherited in this order –Parameters specified on the individual VC –Parameters specified in the VC class applied to the individual VC –Parameters specified on the bundle to which the VC belongs –Parameters specified in the VC class applied to the bundle –Parameters specified on an interface or subinterface

59. © 2001, Cisco Systems, Inc. QOS v1.0—10-59 ATM VC Bundle Case Study IP traffic is transported across an international ATM PVC with these IP Precedence values: PrecedenceMeaning 0-1Best-effort Internet traffic 2-3Premium Internet traffic 4VPN traffic 5VoIP traffic 6-7Routing protocols Voice, VPN, and premium Internet traffic shall be transported across dedicated PVCs for easier provisioning.

60. © 2001, Cisco Systems, Inc. QOS v1.0—10-60 Case Study Step 1: Bundle Design Precedence 5 traffic (VoIP) is transported over a separate VC; no bumping is possible Precedence 2-3 traffic (premium Internet) is transported over a separate VC; can be bumped onto the best-effort VC Precedence 4 traffic (VPN) is transported over a separate VC; can be bumped onto best-effort VC Control traffic is transported over a separate VC; can be bumped onto the best-effort VC Best-effort VC can be bumped onto premium Internet VC WRED has to be deployed on all VCs to prevent bumped best-effort traffic from congesting the VC

61. © 2001, Cisco Systems, Inc. QOS v1.0—10-61 Router Configuration Case Study Step 2: Configuring VC Classes vc-class best_effortvc-class vpn precedence other precedence 4 bump explicitly 2 bump explicitly 0 protect group protect group! vc-class premiumvc-class voip precedence 2-3 precedence 5 bump implicitly no bump traffic protect group protect vc! vc-class bundlevc-class control encapsulation aal5snap precedence 6-7 broadcast bump explicitly 0 protocol ip inarp protect group oam-bundle manage 3 vc-class best_effortvc-class vpn precedence other precedence 4 bump explicitly 2 bump explicitly 0 protect group protect group! vc-class premiumvc-class voip precedence 2-3 precedence 5 bump implicitly no bump traffic protect group protect vc! vc-class bundlevc-class control encapsulation aal5snap precedence 6-7 broadcast bump explicitly 0 protocol ip inarp protect group oam-bundle manage 3

62. © 2001, Cisco Systems, Inc. QOS v1.0—10-62 Router Configuration (cont.) Case Study Step 3: Configuring the WRED Profile Guaranteed_BW_PVC random-detect-group guaranteed_bw_pvc precedence 0 20 40 10 precedence 1 25 40 10 precedence 2 35 40 10 precedence 6 30 40 10 precedence 7 30 40 10 random-detect-group guaranteed_bw_pvc precedence 0 20 40 10 precedence 1 25 40 10 precedence 2 35 40 10 precedence 6 30 40 10 precedence 7 30 40 10

63. © 2001, Cisco Systems, Inc. QOS v1.0—10-63 Router Configuration (cont.) Case Study Step 4: Configure the Bundle and Individual PVC interface ATM 5/1/0.22 point-to-point ip address 216.23.45.5 255.255.255.252 bundle SanFrancisco class bundle pvc-bundle SF-control 26 class control vbr-nrt 1000 1000 pvc-bundle SF-voip 25 class voip vbr 2000 2000 pvc-bundle SF-vpn 24 class vpn vbr-nrt 4000 4000 pvc-bundle SF-guaranteed 22 class guaranteed_bw random-detect attach guaranteed_bw_pvc vbr-nrt 8000 8000 pvc-bundle SF-best-effort 23 class best_effort random-detect interface ATM 5/1/0.22 point-to-point ip address 216.23.45.5 255.255.255.252 bundle SanFrancisco class bundle pvc-bundle SF-control 26 class control vbr-nrt 1000 1000 pvc-bundle SF-voip 25 class voip vbr 2000 2000 pvc-bundle SF-vpn 24 class vpn vbr-nrt 4000 4000 pvc-bundle SF-guaranteed 22 class guaranteed_bw random-detect attach guaranteed_bw_pvc vbr-nrt 8000 8000 pvc-bundle SF-best-effort 23 class best_effort random-detect

64. © 2001, Cisco Systems, Inc. QOS v1.0—10-64 Summary Upon completing this lesson, you should be able to: Describe VC bundling Configure VC bundling Monitor and troubleshoot VC bundling

65. © 2001, Cisco Systems, Inc. QOS v1.0—10-65 Review Questions 1.How does VC bundling classify IP packets? 2.Which QoS mechanisms are used in conjunction with VC bundling? 3.How many parallel VCs can be used for one IP adjacency? 4.How many IP Precedence values can map into one VC?

66. © 2001, Cisco Systems, Inc. QOS v1.0—10-66 Per-VC CB-WFQ © 2001, Cisco Systems, Inc. QOS v1.0—10-66

67. © 2001, Cisco Systems, Inc. QOS v1.0—10-67 Objectives Upon completing this lesson, you will be able to: Describe per-VC CBWFQ Configure per-VC CBWFQ Monitor and troubleshoot per-VC CBWFQ

68. © 2001, Cisco Systems, Inc. QOS v1.0—10-68 Per-VC CBWFQ Class-based weighted fair queuing (CBWFQ) can be used on ATM interfaces. QoS service policies can be applied to: –An interface –A subinterface –An individual virtual circuit Supported service policies are: –CBWFQ including WRED –CBLLQ –Class-based marking, including setting of ATM CLP bit –Class-based shaping –Class-based policing, including setting of ATM CLP bit

69. © 2001, Cisco Systems, Inc. QOS v1.0—10-69 Per-Interface CBWFQ CBWFQ can be applied to an entire interface. Interface ATM1/0/0 Subinterface ATM1/0/0.1 Subinterface ATM1/0/0.2 PVC 0/50 PVC 0/51 PVC 0/52 PVC 0/53 PVC 0/54 CBWFQ class-map HTTP match http ! policy-map LimitHTTP class HTTP police 256000 conform transmit exceed set-clp-transmit ! interface ATM5/0/0 service-policy output LimitHTTP ! class-map HTTP match http ! policy-map LimitHTTP class HTTP police 256000 conform transmit exceed set-clp-transmit ! interface ATM5/0/0 service-policy output LimitHTTP !

70. © 2001, Cisco Systems, Inc. QOS v1.0—10-70 Per-Subinterface CBWFQ CBWFQ can be applied to subinterfaces. Interface ATM1/0/0 Subinterface ATM1/0/0.1 Subinterface ATM1/0/0.2 PVC 0/50 PVC 0/51 PVC 0/52 PVC 0/53 PVC 0/54 CBWFQ class-map CorporateTrafficinterface ATM5/0/0.1 point-to-point match access-group 100 service-policy output Smart ! pvc Core 0/51 policy-map Smart vbr-nrt 10000 2000 class CorporateTraffic! bandwidth 10000 class class-default set atm-clp ! class-map CorporateTrafficinterface ATM5/0/0.1 point-to-point match access-group 100 service-policy output Smart ! pvc Core 0/51 policy-map Smart vbr-nrt 10000 2000 class CorporateTraffic! bandwidth 10000 class class-default set atm-clp !

71. © 2001, Cisco Systems, Inc. QOS v1.0—10-71 Per-Interface CBWFQ CBWFQ can be applied to an individual virtual circuit. Interface ATM1/0/0 Subinterface ATM1/0/0.1 Subinterface ATM1/0/0.2 PVC 0/50 PVC 0/51 PVC 0/52 PVC 0/53 PVC 0/54 CBWFQ

72. © 2001, Cisco Systems, Inc. QOS v1.0—10-72 Per-Interface CBWFQ Configuration Example class-map MatchCorporate match access-group 100 ! policy-map MARK class MatchCorporate police 2000000 conform-action transmit exceed-action set-clp-transmit ! interface ATM5/0/0 ip address 10.1.1.1 255.255.255.0 service-policy output MARK pvc 0/50 vbr-nrt 500 400 1000 inarp 1 broadcast ! access-list 100 permit ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255 class-map MatchCorporate match access-group 100 ! policy-map MARK class MatchCorporate police 2000000 conform-action transmit exceed-action set-clp-transmit ! interface ATM5/0/0 ip address 10.1.1.1 255.255.255.0 service-policy output MARK pvc 0/50 vbr-nrt 500 400 1000 inarp 1 broadcast ! access-list 100 permit ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255

73. © 2001, Cisco Systems, Inc. QOS v1.0—10-73 Per-VC CBWFQ Configuration Example class-map MatchCorporate match access-group 100 ! policy-map MARK class MatchCorporate police 2000000 conform-action transmit exceed-action set-clp-transmit ! interface ATM5/0/0 no ip address ! interface ATM5/0/0.1 point-to-point ip address 10.1.1.1 255.255.255.0 pvc 0/50 vbr-nrt 500 400 1000 inarp 1 service-policy output MARK broadcast ! access-list 100 permit ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255 class-map MatchCorporate match access-group 100 ! policy-map MARK class MatchCorporate police 2000000 conform-action transmit exceed-action set-clp-transmit ! interface ATM5/0/0 no ip address ! interface ATM5/0/0.1 point-to-point ip address 10.1.1.1 255.255.255.0 pvc 0/50 vbr-nrt 500 400 1000 inarp 1 service-policy output MARK broadcast ! access-list 100 permit ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255

74. © 2001, Cisco Systems, Inc. QOS v1.0—10-74 Monitoring and Troubleshooting Per-Interface CBWFQ show policy-map interface ATM-interface Router# Displays the service policy parameters and statistics for the selected interface or subinterface Router#show policy interface atm 5/0/0.1 ATM5/0/0.1 Service-policy output: Smart (1755) Class-map: CorporateTraffic (match-all) (1757/42) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: access-group 100 (1761) queue size 0, queue limit 2500 packets output 0, packet drops 0 tail/random drops 0, no buffer drops 0, other drops 0 Bandwidth: kbps 10000, weight 29... Router#show policy interface atm 5/0/0.1 ATM5/0/0.1 Service-policy output: Smart (1755) Class-map: CorporateTraffic (match-all) (1757/42) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: access-group 100 (1761) queue size 0, queue limit 2500 packets output 0, packet drops 0 tail/random drops 0, no buffer drops 0, other drops 0 Bandwidth: kbps 10000, weight 29...

75. © 2001, Cisco Systems, Inc. QOS v1.0—10-75 Monitoring and Troubleshooting Per-VC CBWFQ show queueing interface ATM-interface [vc [VPI/]VCI] Router# Displays CBWFQ parameters and statistics for the selected interface, subinterface, or VC. Router#show queueing interface atm5/0 Interface ATM5/0 VC 0/5 Queueing strategy: fifo Output queue 0/40, 0 drops per VC Interface ATM6/0 VC 0/16 Queueing strategy: fifo Output queue 0/40, 0 drops per VC Interface ATM6/0 VC 0/50 Queueing strategy: weighted fair Total output drops per VC: 0 Output queue: 0/512/64/0 (size/max total/threshold/drops) Conversations 0/1/32 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 225 kilobits/sec Router#show queueing interface atm5/0 Interface ATM5/0 VC 0/5 Queueing strategy: fifo Output queue 0/40, 0 drops per VC Interface ATM6/0 VC 0/16 Queueing strategy: fifo Output queue 0/40, 0 drops per VC Interface ATM6/0 VC 0/50 Queueing strategy: weighted fair Total output drops per VC: 0 Output queue: 0/512/64/0 (size/max total/threshold/drops) Conversations 0/1/32 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 225 kilobits/sec

76. © 2001, Cisco Systems, Inc. QOS v1.0—10-76 Summary Upon completing this lesson, you should be able to: Describe per-VC CBWFQ Configure per-VC CBWFQ Monitor and troubleshoot per-VC CBWFQ

77. © 2001, Cisco Systems, Inc. QOS v1.0—10-77 Review Questions 1.Where can CBWFQ be attached on ATM interfaces?

78. © 2001, Cisco Systems, Inc. QOS v1.0—10-78 RSVP to SVC Mapping © 2001, Cisco Systems, Inc. QOS v1.0—10-78

79. © 2001, Cisco Systems, Inc. QOS v1.0—10-79 Objectives Upon completing this lesson, you will be able to: Describe RSVP-to-SVC mapping Configure RSVP-to-SVC mapping Monitor and troubleshoot RSVP-to-SVC mapping

80. © 2001, Cisco Systems, Inc. QOS v1.0—10-80 RSVP-to-SVC Mapping RSVP-enabled flows have bandwidth and delay requirements. Pass-through RSVP could hamper the quality of service if an ATM interface or PVC is congested. RSVP-enabled flows can get their own VCs and queues to prevent congestion from affecting these flows. RSVP reservations are mapped to SVCs.

81. © 2001, Cisco Systems, Inc. QOS v1.0—10-81 RSVP-to-SVC Mapping (cont.) RSVP SVC RSVP triggers SVC creation. ATM SVC parameters are calculated from the parameters in the RSVP reservation request.

82. © 2001, Cisco Systems, Inc. QOS v1.0—10-82 ATM SVC Parameters SCR = BW RSVP. (53/48). (MPS + DLE + UCO)/MPS Data Link Encapsulation Overhead AAL5SNAP has 5 bytes of overhead. Data Link Encapsulation Overhead AAL5SNAP has 5 bytes of overhead. Minimum IP Packet Size Unused Cell Overhead Cell Overhead Bandwidth Requested by RSVP Sustained Cell Rate Peak cell rate uses the same formula except it is based on the line rate or the configured peak cell rate. Voice Data IP Header IP Header AAL5SNAP Header AAL5SNAP Header ATM Header ATM Header ATM Header ATM Header Voice Data Unused Cell 1Cell 2 5543548

83. © 2001, Cisco Systems, Inc. QOS v1.0—10-83 RSVP-to-SVC Mapping Optional QoS RSVP can mark conforming and exceeding packets with different IP Precedence or ToS values. Per-VC WRED can be used for differentiated dropping.

84. © 2001, Cisco Systems, Inc. QOS v1.0—10-84 Configuring RSVP-to-SVC Mapping These configuration steps are needed to enable RSVP-to-SVC mapping: –Enable RSVP –Enable SVC creation –Optionally, enable RSVP-based marking and WRED –Verify and monitor RSVP/ATM

85. © 2001, Cisco Systems, Inc. QOS v1.0—10-85 Enabling RSVP ip rsvp bandwidth reservable-bw max-flow-bw Router(config-if)# Enables RSVP reservation on an interface or subinterface The reservable-bw parameter specifies the total maximum amount of bandwidth that can be reserved by RSVP flows The max-flow-bw parameter specifies the maximum amount of bandwidth a that single flow can reserve

86. © 2001, Cisco Systems, Inc. QOS v1.0—10-86 Enabling Creation of SVCs ip rsvp svc-required Router(config-if)# Enables creation of SVC for RSVP reservation ATM QoS parameters are determined by using the parameters in the RSVP request ip rsvp atm-peak-rate-limit limit Router(config-if)# Sets the peak cell rate for all new SVCs Uses the line rate as the default

87. © 2001, Cisco Systems, Inc. QOS v1.0—10-87 RSVP-Based Marking and WRED ip rsvp precedence {conform | exceed} precedence Router(config-if)# Packets conforming to the reserved bandwidth are marked with conform precedence Packets exceeding the reserved bandwidth are marked with exceed precedence NetFlow has to be enabled random-detect attach random-detect-group Router(config-if)# Enables per-VC WRED Uses the WRED profiles specified in the WRED group random- detect-group CEF switching is required

88. © 2001, Cisco Systems, Inc. QOS v1.0—10-88 RSVP-to-SVC Mapping Example interface ATM2/1/0 ip address 10.1.1.1 255.255.255.0 ip rsvp bandwidth 10000 10000 ip rsvp svc-required ip route-cache flow ip rsvp precedence conform 5 exceed 0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi atm esi-address 111111111151.00 pvc pvc12 0/51 inarp 5 broadcast ! interface ATM2/1/0 ip address 10.1.1.1 255.255.255.0 ip rsvp bandwidth 10000 10000 ip rsvp svc-required ip route-cache flow ip rsvp precedence conform 5 exceed 0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi atm esi-address 111111111151.00 pvc pvc12 0/51 inarp 5 broadcast !

89. © 2001, Cisco Systems, Inc. QOS v1.0—10-89 Monitoring and Troubleshooting RSVP-to-SVC Mapping show ip rsvp interface [intf] Router# Displays RSVP-related interface information Router#show ip rsvp interface interface allocated i/f max flow max pct UDP IP UDP_IP UDP M/C Et4/0 0M 7M 5M 0 0 0 0 0 AT5/0/0 0M 10M 1M 0 0 0 0 0 Se5/1/0 0M 192K 192K 0 0 0 0 0 Router#show ip rsvp interface interface allocated i/f max flow max pct UDP IP UDP_IP UDP M/C Et4/0 0M 7M 5M 0 0 0 0 0 AT5/0/0 0M 10M 1M 0 0 0 0 0 Se5/1/0 0M 192K 192K 0 0 0 0 0

90. © 2001, Cisco Systems, Inc. QOS v1.0—10-90 Summary Upon completing this lesson, you should be able to: Describe RSVP-to-SVC mapping Configure RSVP-to-SVC mapping Monitor and troubleshoot RSVP-to-SVC mapping

91. © 2001, Cisco Systems, Inc. QOS v1.0—10-91 Review Questions 1.How does RSVP benefit from using SVCs? 2.What are the necessary configuration steps to enable RSVP-to-SVC mapping?

92. © 2001, Cisco Systems, Inc. QOS v1.0—10-92 Module Summary Upon completing this module, you should be able to: List the requirements of IP QoS in combination with ATM QoS Describe the hardware and software requirements for advanced IP QoS mechanisms on ATM interfaces Describe per-VC queuing Describe and configure per-VC WRED Describe and configure VC bundling Describe and configure per-VC CBWFQ Describe RSVP-to-SVC mapping Monitor and troubleshoot IP QoS on ATM interfaces

93. © 2001, Cisco Systems, Inc. IP QoS IP over ATM-93

94. © 2001, Cisco Systems, Inc. QOS v1.0—10-94 Blank for Pagination