qos10g10.ppt

IP over ATM 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 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 IP vs. ATMTechnology 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 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. 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 UBR Virtual Circuits VBR Virtual Circuits CBR and ABR Virtual Circuits Congestion Management in ATM Networks Congestion management on routers should be performed on a per-VC basis. Design options: Make sure there