Admission Control Mechanism For Mpls Ds Te


Published on

Published in: Education, Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Admission Control Mechanism For Mpls Ds Te

  1. 1. Simulation and analysis of an admission controlmechanism for MPLS DS-TE<br />By: Omer Mahmoud, Farhat Anwar , Momoh Jimoh E. Salami<br />2008 Elsevier<br />Presenter : Nageeb Yahya Alsurmi<br /> GS21565<br />Lecturer :Assoc. Prof. Dr Mohamed Othman<br />Date : 15-07-2009<br />UPM University<br />SKR 5306 Advanced Computer Network<br />
  2. 2. MPLS DS-TE<br /> Outline<br />Introduction<br />Problem Statement<br />Objective<br />QoS – DiffServ<br />MPLS DS-TE<br />Admission Control Mechanism <br />Methodlogy<br />Simulation Setup<br />Performance metrics<br />Simulation results and analysis<br />Conclusion<br />References<br />
  3. 3. MPLS DS-TE<br />Introduction<br />The internet architecture was originally designed to provide IP based ‘‘best-effort” services to all its applications.<br />The Internet is currently a Single Queue Best Effort network<br /><ul><li>Internet2 Project Abilene is DiffServ multi-priority QoS testbed</li></ul>“Best-effort” service describes a network service which attempts to deliver traffic to its destination, but which does not provide any guarantees of delivery, without any commitments for delay, jitter, loss, and throughput (bandwidth)<br />It is inadequate for new classes of emerging applications with real time data such as audio and video streaming<br />In contrast, Quality of Service (QoS) provides a high data throughput (bandwidth) and low-latency. <br />
  4. 4. Introduction<br />In order to provide a low-delay, low-jitter and low-loss service (QoS) the network must be engineered (MPLS TE) to remove all points of congestion (Admission Control) on the end-to-end path for that service; in order to assure different SLAs (Service Level Agreements) for different classes of traffic (hence minimizing cost).<br />QoS—quality of service. A measure of performance for a transmission system that reflects its transmission quality and service availability. <br />MPLS DS-TE<br />
  5. 5. Introduction ….(cont…)<br />Proplem Statement<br />When DiffServ traffic flows via an MPLS domain, a DiffServ QoS might not be maintained.To preserve this QoS an arrangement is essential so that multiple DiffServ domains can be connected through MPLS backbone network for allocating and controlling the bandwidth within MPLS domains.<br />MPLS DS-TE<br />
  6. 6. Introduction ….(cont…)<br />The Objective<br />Improving the Admission control mechanism whereby DiffServ expedited forwarding (EF) per-hop behavior can be admitted to an MPLS TE tunnel to ensure stable performance for the traffic in the MPLS Domain.<br />MPLS DS-TE<br />
  7. 7. MPLS DS-TE<br />QoS<br />IP QoS<br />IntServ<br />DiffServ<br />MPLS<br />statistical QoS<br />classify packets<br />guaranteed QoS<br />Intserv provides QoS by reserving the resourcesin the network from the source to destination using resource reservation signaling protocol (RSVP)<br />DiffServ provides a spectrum of services , classifying, managing network traffic, mark packets as belonging to a specific class and assign relative prioritiesto packets to reflect the differential level of treatment to be afforded that packet.<br />MPLS provides QoS by using switching mechanism unlike conventional IP routing mechanism ,MPLS uses label information to identify packets and forwards packets based on label information which is faster than if compared with packet’s IP destination address routing.<br />
  8. 8. MPLS DS-TE<br />QoS architectures<br />The component of QoS feature that recognizes and distinguishes between different traffic streams.<br />Without classification, all packets are treated the same.<br />DiffServ provides a scalable means of service differentiation in the Internet. It classifies all the traffic into categories or classes in order to provide differential treatment between these classes.<br />DiffServ can be used to provide low-latency, guaranteed service (GS) to critical network traffic such as voice or video while providing simple best-effort traffic guarantees to non-critical services such as web traffic or file transfers.<br />DSCP: Differentiated Services Code Point marking each packet on the network with a DSCP code and appropriating to it the corresponding level of service.<br />
  9. 9. MPLS DS-TE<br />DiffServ Model<br />Differentiated IP Services<br />Platinum Class Low Latency<br />Voice<br />E-Commerce<br />Guaranteed: Latency <br />and Delivery<br />Gold<br />Application Traffic<br />Traffic<br />Classification<br />E-mail, WebBrowsing<br />Guaranteed Delivery<br />Silver<br />Voice<br />Best Effort Delivery<br />Bronze<br />
  10. 10. MPLS DS-TE<br />MPLS<br />MPLS is a method of forwarding packets that integrates layer 2 and layer 3 functionalities. MPLS uses a technique known as label switching to forward data through the network.<br />One of the significant initial applications of MPLS is its ability to use traffic engineering (TE).<br />TE: is the process of controlling how traffic flows through a network so as to optimize resource utilization and network performance.<br />TE algorithms calculate explicit routes to<br /> one or more nodes in the network called <br /> tunnel.<br />MPLS is more suitable for use as a<br /> backbone ,it offers more flexible bandwidth<br /> management capabilities.<br />
  11. 11. MPLS Applications<br />MPLS Applications<br /><ul><li> MPLS VPN – Layer-3
  12. 12. Detailed Overview
  13. 13. IOS Examples
  14. 14. MPLS Layer-2 Transport
  15. 15. PWE3/AToM
  16. 16. Application Example
  17. 17. MPLS TE Traffic Engineering
  18. 18. Fast-ReRoute for Bandwidth Protection
  19. 19. MPLS QoS
  20. 20. Diffserv over MPLS
  21. 21. Diffserv TE (DS-TE)
  22. 22. Guaranteed Bandwidth
  23. 23. Service Applications ,
  24. 24. Useful Implementations Combining Multiple MPLS Services
  25. 25. IP version 6 (IPv6) Transport Methods over MPLS
  26. 26. 6PE/6VPE (IPv6 Edge and VPN Support)</li></ul>MPLS DS-TE<br />Combining TE, TE-FRR, and DS-TE, high-availability for low-latency<br /> applications (e.g. Voice and Virtual Leased Line)<br />
  27. 27. MPLS DS-TE (TE aware DiffServ )<br />The basic functions provided by DS-TE are:<br /><ul><li> separate bandwidth reservations for different sets of traffic classes.
  28. 28. admission-control procedures applied on a per-class basis.</li></ul>DS-TE is more than MPLS TE + MPLS DiffServ<br />DS-TE makes MPLS TE aware of DiffServ:<br /><ul><li> DS-TE establishes separate tunnels for different classes
  29. 29. DS-TE takes into account the “bandwidth” available to each class (e.g. to queue)
  30. 30. DS-TE takes into account separate engineering constraints for each class
  31. 31. e.g. I want to limit Voice traffic to 70% of link max, and the rest for other traffics.
  32. 32. DS-TE ensures specific QoS level of each DiffServ class is achieved</li></ul>MPLS DS-TE<br />
  33. 33. MPLS DS-TE<br />MPLS DS-TE with DiffServ Network<br />Find Route and Set-Up Tunnel for 5 Mb/sof EFFrom POP1 to POP4<br />Find Route and Set-Up Tunnel for<br />3 Mb/sof EFFrom POP2 to POP4<br />POP 1<br />POP 4<br />CORE<br />POP 2<br />POP<br />POP<br />POP<br />Find Route and Set-Up Tunnel for 15 Mb/s of BEFrom POP1 to POP4<br />Find Route and Set-Up Tunnel for 7 Mb/s of BEFrom POP2 to POP4<br />
  34. 34. MPLS DS-TE<br />Traffic admission control<br />Admission control is the process of determining whether a new traffic flow, stream or logical connection may be accepted, taking into account resource and policy constraints.<br />Admission control is to ensure that there is sufficient link or class capacity available at the required service level to accept a new request.<br />In case there is no admission control ,For real time traffic , if there is an VoIP application requests a 500kb/s as bandwidth to be reserved but the available is 200kb/s , then how will be the Quality of voice ?? The stream progress will be degraded.<br />The Admission control with DiffServ has the solution for this isuue, by classifying the traffic to service classes and allocating with reserving a resources in MPLS network with regard to the classes. <br />The Bandwidth agent BA is the controller of Admission control is not only allocation of the traffic to service classes within its domain but also to send the configuration parameters to the edge routers. <br />The BA first authenticates each requester and then decides whether there is sufficient bandwidth to meet the particular service request.<br />
  35. 35. MPLS DS-TE<br />When is Admission Control Needed<br /> Admission Control is only practically useful if the following four conditions are met :<br />Without admission control, the offered load may exceed the available capacity.<br />Network working case conditions. If there were insufficient bandwidth to support the peak call load in normal working case conditions,then AC would be required to cover both working and failure cases.<br />Single network element failure conditions : during network failures, AC provides the capability to reject new or rerouted service requests so that those already granted admission continue to maintain their committed service<br />Multiple network elementfailure conditions<br />
  36. 36. MPLS DS-TE<br />IP admission control taxonomy<br />IP admission control taxonomy :<br />
  37. 37. MPLS DS-TE<br />Traffic admission control Mechanism<br />There are two domains, each one have a Bandwidth Agent (BA) for Admission control.<br />BA Can manage the requested resources in its domain.<br />the traffic is traversing<br /> more than one domain, the BAs within these domains would communicate before admitting the traffic in order to ensure the availability of the<br /> requested resources.<br />
  38. 38. Admission Control Mechanism (Cont..)<br />The BA first authenticates each requester and then decides whether there is sufficient bandwidth to meet the particular service request.<br />The BA also maintains agreement with BAs in neighboring domains<br />For flows that request service to a destination in a different domain, the BA cheeks to see that the requested flow conforms to the prearranged allocation through the appropriate next-hop domain.<br />The BA then informs the appropriate <br /> neighboring bandwidth agent of the new<br /> rate allocation and notifies its border router<br /> to handle the new flow accordingly.<br />MPLS DS-TE<br />
  39. 39. MPLS DS-TE<br />Admission Control Mechanism (Cont..)<br />BAs communicate with edge routers using the common open policy service (COPS) protocol . Communication is achieved by three kinds of COPS messages: request (REQ), decision (DEC) and report (RPT).<br />DiffServ edge router (DER) sends a REQ<br /> message requesting resource to maintain<br /> QoS parameter for its flow in MPLS domain.<br />MPLS edge router (MER) forwards the REQ <br />to the BA. The BA then replies by sending a DEC.<br />the MPLS edge router communicates the<br />decision to DER. Then the DER sends (ACK) to<br /> indicate its position (e.g. acceptance).<br />Then the MER replies by sending the configuration result (i.e. success or failure) to the BA via a Report message<br />Whenever there is a change in the resource availability, the BA may initiate the admission control process by informing the MER through a DEC message containing the updated parameters.<br />
  40. 40. MPLS DS-TE<br />Methodology<br />Simulation Setup<br />The performance of the proposed mechanism has been evaluated by NS-2 network simulator.<br />It consists of two edge routers (R1 and R3) and one core router (R2) representing the simulated MPLS domain. <br />The edge routers are capable of mapping incoming EF flows to specific MPLS tunnels.<br /> Four flows (F1, F2, F3 and F4) <br /> are transmitted from sources <br /> S1 and S2 to the destination D<br />80% bandwidth of the link is <br /> dedicated to tunnel 1<br />20% bandwidth of the link is <br /> dedicated to tunnel 2<br />F1= 500kb/s, F2=500kb/s, <br />F3=300kb/s, F4=500kb/s<br />S1= 1500kb/s<br />S2= 300kb/s<br />
  41. 41. MPLS DS-TE<br />The QoS for the flow is maintained using multiple queues which are implemented in the routers of the MPLS domain<br />There are four simulation scenario to investigate impact of the proposed mechanism.<br />Performance metrics:<br />Throughput<br />Delay<br />Jitter<br />Packet Losses<br />
  42. 42. Simulation results and analysis<br />Simulation scenario 1- Ideal state (one queue / two Queues)<br />ideal situation where resources (bandwidth) are adequate to accommodate all incoming traffic. <br />Used for comparison with other scenarios.<br />The link bandwidth between routers is set to 2 Mbps.<br />It is observed that all the traffic<br /> (flow F1, F2, F3 and F4) achieve the required maximum throughput for both queuing arrangements<br />MPLS DS-TE<br />
  43. 43. MPLS DS-TE<br />Results – scenario2<br />Scenario 2 (single Queue, single tunnel) – congested network<br />represents a situation where resources (bandwidth) are inadequate<br /> to accommodate all incoming traffics<br />Set link bandwidth between routes to 1.5 Mb/s<br />Use one Queue<br />It is also observed that the <br /> achieved throughput is less <br /> than the required maximum<br /> throughput<br />This is due to packet loss in the<br /> routers as a result of congestion<br />
  44. 44. MPLS DS-TE<br />Results – scenario3<br />Scenario 3 (two Queues, two tunnels) – congested network<br />The same as scenario 2 Two queues for all routers.<br /> link bandwidth = 1.5Mb/s.<br />(F1,F2,F4) use Tunnel 1 and Q1 with 80% utilization of 1.5mb/s= 1.2mb/s.<br />F3 use Tunnel 2 and Q2 with 20% utlization of 1.5mb/s = 300Kb/s.<br />flow F3 has achieved the maximum throughput.<br />Flow (F1,F2,F4) resulting Packet losses and this leads to lower throughput.<br />
  45. 45. MPLS DS-TE<br />Results – scenario4<br />Scenario 4 (two Queues, two tunnels) – congested network with delay:<br />This is similar to scenario 3 except that flow F2 starts to<br /> generate traffic 10 s later than the remaining flows (F1, F3,F4).<br />flows F1, F3 and F4 achieve the maximum throughput for the first 10 s. After that decreased when F2 starts to generate traffic.<br />while F3 remains unaffected<br />and maintains its throughput<br />
  46. 46. MPLS DS-TE<br />Result Analysis -Delay, jitter and losses<br />scenario 2 and 3 are used to study the effect of<br /> the proposed mechanism on the delay,<br /> jitter and packet losses of the traffic flows.<br />all the flows in scenario 2 suffer from long delay,<br />high-jitter and losses due to inadequate<br /> resources in the tunnel. This is because all the flows<br /> are competing for the available bandwidth on<br /> equal basis.<br />in scenario 3 shows that by utilizing separate queues<br /> selected flows will be protected and achieve stable<br /> performance .<br />These results show that delay, jitter, and throughput<br /> for flow F3 has improved when separate queue (Q2)<br /> is dedicated and 100% throughput is achieved.<br />
  47. 47. MPLS DS-TE<br />Conclusion<br />Traffic flows crossing an MPLS domain are adversely affected by inadequate resource in MPLS tunnels especially flows with high QoS parameters such as DiffServ EF.<br />An improved admission control mechanism has been proposed<br /> which enables tunnel differentiation by employing multiple queues to improve the situation.<br />This allows QoS to be preserved in transit MPLS network leading to end to end QoS when handling DiffServ EF traffic.<br />
  48. 48. MPLS DS-TE<br />References<br />[1] R. Braden, D. Clark, S. Shenker, Integrated services in the internet architecture: an overview, RFC 1633, 1994.<br />[2] S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss, An architecture for differentiated services, RFC 2475, 1998.<br />[3] E. Rosen, A. Viswanathan, R. Callon, Multiprotocol label switching architecture, RFC 3031, 2001.<br />[4] J. Wroclawski, The use of RSVP with IETF integrated services, RFC 2210, 1997.<br />[5] F. Le Faucheur, W. Lai, Requirements for support of differentiated services-awareMPLS traffic engineering, IETF, RFC 3564, July 2003.<br />[6] F. Le Faucheur, Protocol extensions for support of DiffServ-aware MPLS traffic, IETF, RFC 4124, June 2005.<br />[7] F. Le Faucheur, W. Lai, Maximum allocation bandwidthconstraintsmodel for DiffServ-aware MPLS traffic engineering, IETF, RFC4125, June 2005.<br />[8] B. Davie, A. Charny, J.C.R. Bennet, K. Benson, J.Y. Le Boudec, W. Courtney, S. Davari, V. Firoiu, D. Stiliadis, An expedited forwarding PHB (per-hop behavior), RFC 3246, 2002.<br />
  49. 49. Any Questions @ MPLS DS-TE Admission Control <br />Ada Soalan !!!!<br />Thank You !<br />Terima Kasiiih….:)<br />