P. 1
Luan Van Tot Nghiep

Luan Van Tot Nghiep

|Views: 286|Likes:

More info:

Published by: Vuong Hoai Phong Nguyen on Dec 22, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

07/03/2014

pdf

text

original

Sections

  • Architecture of subject
  • Relation Words
  • Multiprotocol Label Switching
  • Actuality of MPLS at VietNam
  • Advantage of MPLS:
  • Disadvantage of MPLS:
  • Icon use in subject
  • SYSTEM OF HUTECH UNIVERSITY
  • 1.1. Description about network system of Hutech University
  • 1.2. Important problem and solution
  • 1.3. Task of Subject
  • CHAPTER 2: QOSOVER MPLSNETWORK
  • PART 1: OVERVIEW ABOUT MPLS
  • 2.1. Architecture of MPLS packet
  • 2.1.1. Label
  • 2.1.2. Experimental
  • 2.1.3. Bottom of Stack
  • 2.1.4. Time to Live
  • 2.2. Operating of MPLS network
  • 2.2.1. MPLS domain
  • 2.2.2. Ingress and Egress node
  • 2.2.3. Label Switch Router
  • 2.2.4. Label Switch Path
  • 2.2.5. ForwardingEquivalentClass
  • 2.2.6. Label Distribution Protocol
  • 2.3. Command for configure MPLS
  • PART 2: OVERVIEW ABOUT QOS
  • 2.4. Architectures of QoS
  • 2.4.1. IntServ model
  • 2.4.2. DiffServ model
  • 2.4.3.Difference between InServ model and DiffServ model
  • 2.5. Classification
  • 2.7.2. Priority Queuing
  • 2.7.3. Custom Queuing
  • 2.7.4. Weighted Fair Queuing
  • 2.7.5. Class-Based Weighted Fair Queuing
  • 2.7.6. Low-Latency Queuing
  • 2.8. Relation about IPP, DSCP and MPLS EXP
  • 2.8.1. IPP
  • 2.8.2. DSCP
  • 2.8.3. MPLS EXP
  • 2.9. DiffServ with IP packets
  • 2.10. DiffServ with MPLS packets
  • 2.11. DiffServ Tunneling Modes for MPLS networks
  • 2.11.2.Short-Pipe Model
  • 2.12.Steps implement QoS over MPLS
  • CHAPTER 3: NETWORK DESIGN AND IMPLEMENT
  • 3.1.BUILING SOLUTION FOR HUTECH NETWORK
  • 3.1.1. Real model of Hutech network
  • 3.1.2. Solution model for Hutech network
  • 3.2. Building simulation model to resolve for Hutech network
  • 3.2.1.Simulation model
  • 3.2.2.Implement QoS over MPLS in simulation model
  • 3.3. Get Result
  • GET RESULT AND DEFINE OF DEVELOP IN SUBJECT

Supervisor: Nguyễn Đức Quang

QoS over MPLS for Hutech network

Table of Contents
Architecture of Subject.......................................................................................4 Relation Words ...................................................................................................5 Multiprotocol label switching ............................................................................6 Actuality of MPLS at VietNam..........................................................................6 Advantage of MPLS ...........................................................................................8 Disadvantage of MPLS.......................................................................................8 Icon use in subject ..............................................................................................9

CHAPTER 1: INTRODUCTION ABOUT NETWORK SYSTEM OF HUTECH UNIVERSITY .................................... 10
1.1. Description about network system of Hutech University. ..........................11 1.2. Important problem and solution. .................................................................11 1.3. Task of subject.............................................................................................12

CHAPTER 2: QOS OVER MPLS NETWORK......................... 13 Part 1: Overview about MPLS .................................................... 14
2.1. Architecture of MPLS packet......................................................................15 2.1.1. Label. ..................................................................................................15 2.1.2. Experimental. ......................................................................................15 2.1.3. Bottom of Stack. .................................................................................15 2.1.4. Time to Live........................................................................................16 2.2. Operating of MPLS network. ......................................................................16 2.2.1. MPLS domain. ....................................................................................16 2.2.2. Ingress and egress node. .....................................................................17 2.2.3. Label Switch Router. ..........................................................................17 2.2.4. Label Switch Path. ..............................................................................18 2.2.5. Forwarding Equivalent Class..............................................................18

Student: Trần Quang Hải Đăng

-1-

Supervisor: Nguyễn Đức Quang

QoS over MPLS for Hutech network

2.2.6. Label Distribution Protocol. ...............................................................19 2.3. Command for configure MPLS ...................................................................20

Part 2: Overview about QoS ....................................................... 22
2.4. Architecture of QoS.....................................................................................23 2.4.1. IntServ model......................................................................................23 2.4.2. DiffServ model....................................................................................25 2.4.3. Different between IntServ model and DiffServ model.......................27 2.5. Classification. ..............................................................................................27 2.6. Marking. ......................................................................................................27 2.7. Queuing tools...............................................................................................28 2.7.1. First In-First Out Queuing. .................................................................29 2.7.2. Priority Queuing..................................................................................31 2.7.3. Custom Queuing. ................................................................................32 2.7.4. Weighted Fair Queuing.......................................................................33 2.7.5. Class-Based Weighted Fair Queuing..................................................38 2.7.6. Low-latency Queuing. ........................................................................41

Part 3: QoS over MPLS............................................................... 44
2.8. Relation about IPP, DSCP and MPLS EXP. ...............................................45 2.8.1. IPP.......................................................................................................45 2.8.2. DSCP...................................................................................................46 2.8.3. MPLS EXP..........................................................................................47 2.9. DiffServ with IP packets. ............................................................................48 2.10. DiffServ with MPLS packets. ...................................................................50 2.11. DiffServ Tunneling Modes for MPLS networks.......................................52 2.11.1. Pipe Model. .......................................................................................52 2.11.2. Short-Pipe Model. .............................................................................54 2.11.3. Uniform Model. ................................................................................55 2.12. Steps implement QoS over MPLS.............................................................57

Student: Trần Quang Hải Đăng

-2-

Supervisor: Nguyễn Đức Quang

QoS over MPLS for Hutech network

CHAPTER 3: NETWORK DESIGN AND IMPLEMENT ....... 58
3.1. Building solution for Hutech network.........................................................60 3.1.1. Real model of Hutech network. ..........................................................60 3.1.2. Solution model for Hutech network....................................................61 3.2. Building simulation model to resolve for Hutech network. ........................62 3.2.1. Simulation model. ...............................................................................62 3.2.2. Implement QoS over MPLS in simulation model. .............................64 3.3. Get Result. ...................................................................................................72

Get Result and Define of develop in Subject.............................. 74
References .........................................................................................................75 Index ...................................................................................................................76

Student: Trần Quang Hải Đăng

-3-

Chapter 3: Network design and implement. Part 1: Overview about MPLS. architecture MPLS packet. Student: Trần Quang Hải Đăng -4- . relative about IPP. steps implement QoS over MPLS network. DiffServ with IP packet and MPLS packet. Part 3: QoS over MPLS. classification. get result and define of develop in subject. operation of MPLS network.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Architecture of subject Subject includes three chapters: Chapter 1: Introduction about network system of Hutech University. Deploy QoS over MPLS. solution to resolve. command line for configure MPLS operation. architecture of QoS. problem of Hutech network system. Part 2: Overview about QoS. Chapter 2: Chapter 2 includes three parts. DiffServ tunneling mode. DSCP and MPLS EXP. marking and queuing tool.

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Relation Words IPP DSCP MPLS EXP QoS LSP LSR IntServ DiffServ LLQ FIFO CQ WFQ CBWFQ LDP : IP Precedence (value support implement QoS) : Differentiated Services Code Point : Multiprotocol Label Switching : Experimental : Quality of Service : Label Switched Path : Label Switched Router :Iintegrated services : Differentiated Services : Low-latency Queuing : First In – First Out : Custom Queuing : Weighted Fair Queuing : Class-Based Weighted Fair Queuing : Label Distribution Protocol Student: Trần Quang Hải Đăng -5- .

customs. or OSI model). Dong A bank…). LSRs edge will be invested and extended at places have large demand as Hai Phong. treasury. there are a lot of home companies in finance field. Binh Duong. Actuality of MPLS at VietNam -With VietNam. electricity are taked part and create competition environment with high QoS and cheap. bank use this service (Bao Viet insurance company. MPLS allows most packets to be forwarded at the layer 2 (switching) level rather than at the layer 3 (routing) level. Khanh Hoa…at medium. -VPN/MPLS technology officially deployed. VNPT established an axle MPLS network with three LSR core. not including companies and foreign office representative. the technique is expected to be readily adopted as networks begin to carry more and different mixtures of traffic. thus saving the time needed for a router to look up the address to the next node to forward the packet to. Beside that. With VoIP project is deploying.Present. arrange state as Ministry of Finance. MPLS involves setting up a specific path for a given sequence of packets. Ba Ria – Vung Tau…at south. Viettel. For these reasons. applied and test successfully and inserted to exploited from 2003 by VDC. VPN MPLS solution of VDC Student: Trần Quang Hải Đăng -6- . identified by a label put in each packet. . Next. Quang Ninh at north. insurance. FPT Telecom. tax associated together by VPN/MPLS. In addition to moving traffic faster overall. Asynchronous Transport Mode (ATM). MPLS makes it easy to manage a network for quality of service (QoS).Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Multiprotocol Label Switching Multiprotocol Label Switching (MPLS) is a standards-approved technology for speeding up network traffic flow and making it easier to manage. Da Nang. MPLS is called multiprotocol because it works with the Internet Protocol (IP). 2004. and frame relay network protocols. With reference to the standard model for a network (the Open Systems Interconnection. MPLS deployment are building in communication network at VNPT head of company VietNam. Dong Nai.

security.000 1.000 1.000 3.000 5.694.682.000 1.000 1.000 4.000 3.114.600.000 3. .VPN/VNN MPLS solution of VDC apply and deploy to rely on pass and device technology of Cisco.171.000 5.000 1 2 3 4 5 64 Kbps 128Kbps<speed <=896kbps 1Mbps<speed<= 2Mbps 2Mbps<speed<= 10Mbps 10Mbps<speed<=155Mbps Price for setup. slow late and intergrate with each apply as Data.000 10.000 2.000 5.000 5.000 -7Price for all (VND/port /month) 958.442.224.394.000 1.112.000.000.705.000 1 2 3 4 5 6 7 8 9 10 11 12 64Kbps 128Kbps 192Kbps 156Kbps 384Kbps 512Kbps 768Kbps 896Kbps 1024Kbps 1536Kbps 2048Kbps 4Mbps Student: Trần Quang Hải Đăng .000.000.000. Voice.447. link to network VPN/VNN(VND/ch annel/time) 2.000 20.000 5.000 11.886.000 3.000 3.994.000 20.941.000 875.104.561.500.000 2.370.000.928.000 10. with target create a network solution safe.000 Price for month: (Upcountry price + Service price MPLS/VNN) Order Speed Price for channel TDNH (VND/port /month) 609.000 2.000.558.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network saved up technology information IT Week 14 gold cup and extended to exploited on all 64 provinces of all the country with trade name VPN/VNN.000 2.000 5.415.978.000 1. Video… Price for first setup: include price for setup and link to MPLS/VNN Order Speed Price for channel TDNH (VND/channel/time) 1.000 2.000.000.000 2.

661. Disadvantage of MPLS: -VietNam has limit human resource for control MPLS network system.758.000 18. -Flexible (Easy for wire-open).536. -Easy for administrator control.000 25.964.529.400 24.000 Advantage of MPLS: -Security (absolute security in core MPLS network and local loop network).000 63.034. Student: Trần Quang Hải Đăng -8- .Supervisor: Nguyễn Đức Quang 13 14 15 16 17 6Mbps 8Mbps 10Mbps 34Mbps 45Mbps QoS over MPLS for Hutech network 15.000 33.000 42. -Device support MPLS network is limit.914.173.000 20.

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Icon use in subject Student: Trần Quang Hải Đăng -9- .

10 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network CHAPTER 1: INTRODUCTION ABOUT NETWORK SYSTEM OF HUTECH UNIVERSITY Student: Trần Quang Hải Đăng .

the number of branch and department are growing a lot.1. In addition. 1. Important problem and solution. -Faculty of build. Network diagram Figure 1. include type of faculty: -Faculty of information technology. branch 1 at Binh Thanh distinct.11 - . Web Server. For this reason. Description about network system of Hutech University. FTP Server. -Faculty of foreign language.1. Up to this time.Network diagram of Hutech University. and the last branch at Thu Duc distinct. -Faculty of economy. network system of Student: Trần Quang Hải Đăng .2. Hutech University include three branches. In every branch. branch 2 at Phu Nhuan distinct. Mail Server. -Faculty of electron. Hutech University is carrying to enlarge infrastructure. every branch has SQL server. Three branches join together by Frame-Relay technology.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 1.

With Hutech’s problem. so obstruct at any time in network system. Task of Subject. This network system can’t satisfy need to communication information between branches. high effect. and the best solution is QoS over MPLS. we will build technology QoS over MPLS for Hutech network. To make good that problem. solution for Hutech University network system must a new technology.3. We have too much solutions.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Hutech University is old and stunted. Network system has limit bandwidth and old technology. low cost. Model solution for Hutech network: Figure 1. voice traffic… To limit obstruct. We design and implement to preference for important traffic.2 – Solution model for Hutech network Student: Trần Quang Hải Đăng . 1.12 - . example video traffic.

13 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network CHAPTER 2: QOS OVER MPLS NETWORK Student: Trần Quang Hải Đăng .

14 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network PART 1: OVERVIEW ABOUT MPLS Student: Trần Quang Hải Đăng .

implement quality of service is use IP Precedence or DSCP. transport packets must use IP source and IP destination. three bits used for quality of services.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2.15 - . if label is bottom of stack.048.3. From bit 20 to bit 22 is exp field. However. 2. if label isn’t bottom of stack it has value 0.1. but with MPLS network is use Experimental. 16 value labels first aren’t use.MPLS label architecture.1. their value between 0 to 220–1 and it has 1. Bit 23 BoS (Bottom of Stack) in MPLS header.1. 2. packets are transport by label. but with MPLS network. it has value 1. Architecture of MPLS packet. Label include 20 bit in header MPLS. 2. Label. Routers use label instead for IP address.2 – Label of Stack. In IP network. Figure 2. Figure 2.575 labels. MPLS label is a field with 32 bit with hard architecture. Bottom of Stack. In IP network.2. Student: Trần Quang Hải Đăng .1.1. Experimental.1 . Exp bit similar Precedence bit in IP header.

2. 2. With case packet through from MPLS network to IP network. when transport packets. So TTL field make avoid look. MPLS domain. packet is disposition label and operation is call disposition. Operating of MPLS network. core network operate complete in MPLS network. If router can’t finds the destination of packet but router is forwarding that packet. In case imposition with packet through from IP network to MPLS network. Student: Trần Quang Hải Đăng .1.16 - . this action will loop.Imposition and Disposition. With cord network. every router in MPLS network is use label for forward packets to exactly destination. packet is imposition label and that operation is call imposition. Figure 2. router in edge network must do two tasks. This field similar TTL field in IP header.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network In MPLS network. From bit 24 to bit 31 are used for TTL (Time to Live) field.2. router operate in core network will assign label to packet and forward that packet to next router. 2. router is use label table. MPLS domain include two parts: -Core network (core). two tasks are imposition label and disposition label from packet.1. router will drop it. When packet through every router it’s drop 1. Time to Live. With edge network. -Edge network (edge).4.3 . 2. When TTL field has value 0.

It must be able to pop one or more labels (remove one or more labels from the top of the label stack) before switching the packet out. the LSR pushes one or more labels onto the label stack and switches out the packet. When packet goes from IP network to MPLS network. the top label of the label stack is swapped with a new label and the packet is switched on the outgoing data link. When packet goes from MPLS network to IP network. An LSR that pushes labels onto a packet that was not labeled yet is called an imposing LSR because it is the first LSR to impose labels onto the packet. 2. Label Switch Router.17 - . switch the packet. packet will unassigned label. remove the label(s). push. packet will assign label.2. And operation is call egress.3. insert a label (stack) in front of the packet. This simply means that when a labeled packet is received. An LSR that removes all labels from Student: Trần Quang Hải Đăng . One that is doing imposition is an ingress LSR.2. An LSR can do the three operations: pop. An LSR must also be able to swap a label. Both ingress and egress node are edge router. If the received packet is already labeled. Egress LSRs receive labeled packets.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2. It is capable of understanding MPLS labels and of receiving and transmitting a labeled packet on a data link. perform an operation on it. and send them on a data link. Three kinds of LSRs exist in an MPLS network: Ingress LSRs receive a packet that is not labeled yet. An LSR must also be able to push one or more labels onto the received packet. And operation is call ingress.2. If the packet is not labeled yet. and send the packet on the correct data link. Ingress and Egress node. and send it on a data link. or swap. the LSR creates a label stack and pushes it onto the packet. Intermediate LSRs receive an incoming labeled packet. Ingress and egress LSRs are edge LSRs. A label switch router (LSR) is a router that supports MPLS.

A label switched path (LSP) is a sequence of LSRs that switch a labeled packet through an MPLS network or part of an MPLS network.Label Switch Path 2. and they could belong to a different FEC.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network the labeled packet before switching out the packet is a disposing LSR. -Multicast packets belonging to a certain group Student: Trần Quang Hải Đăng .4. 2. the forwarding treatment could be different. Figure 2. All the LSRs in between the ingress and egress LSRs are the intermediate LSRs. The first LSR of an LSP is the ingress LSR for that LSP.2. not all packets that have the same label belong to the same FEC.18 - . whereas the last LSR of the LSP is the egress LSR.2. A Forwarding Equivalence Class (FEC) is a group or flow of packets that are forwarded along the same path and are treated the same with regard to the forwarding treatment.4. Label Switch Path. Forwarding Equivalent Class. However. because their EXP values might differ. This is logical because the ingress LSR classifies and labels the packets. The router that decides which packets belong to which FEC is the ingress LSR.5. All packets belonging to the same FEC have the same label. Following are some examples of FECs: -Packets with Layer 3 destination IP addresses matching a certain prefix. One that does disposition is an egress LSR. Basically. the LSP is the path through the MPLS network or a part of it that packets take.

2. pop) is known to each LSR by looking into the LFIB. or statically assigned label bindings. -Layer 2 frames carried across an MPLS network received on one VC or (sub)interface on the ingress LSR and transmitted on one VC or (sub)interface on the egress LSR. All packets on the ingress LSR for which the destination IP address points to a set of BGP routes in the routing table—all with the same BGP next-hop address—belong to one FEC. 2. Resource Reservation Protocol (RSVP). all LSRs must run a label distribution protocol and exchange label bindings.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network -Packets with the same forwarding treatment. all directly connected LSRs must establish an LDP peer relationship or LDP session between them. A label mapping or binding is a label that is bound to a FEC.19 - . When all the LSRs have the labels for a particular Forwarding Equivalence Class (FEC). based on the precedence or IP DiffServ Code Point (DSCP) field. the packets can be forwarded on the LSP by means of label switching the packets at each LSR. MP-BGP. Because RSVP distributes the labels only for MPLS traffic engineering and MP-BGP distributes the labels only for BGP routes. push. Label Distribution Protocol. you are left with LDP for distributing all the labels for interior routes. The LFIB (which is the table that forwards labeled packets) is fed by the label bindings found in the LIB.6. The LIB is fed by the label bindings received by LDP. Therefore. It means that all packets that enter the MPLS network get a label depending on what the BGP next hop is. To get packets across a label switched path (LSP) through the MPLS network. all with the same BGP next hop. The LDP peers exchange the label mapping messages across this LDP session. This last example of a FEC is a particularly interesting one. -Packets with Layer 3 destination IP addresses that belong to a set of Border Gateway Protocol (BGP) prefixes. The label operation (swap. The Student: Trần Quang Hải Đăng .

The second step is for them to establish a session across a TCP connection. Across this TCP connection. LDP provides the means to notify the LDP neighbor of some advisory and error messages by sending notification messages. Command for configure MPLS. 2. or retract label bindings. These label mapping messages are used to advertise. Command used for configure MPLS operate Command used for verify MPLS operate Student: Trần Quang Hải Đăng . LDP advertises the label mapping messages between the two LDP peers. they should discover each other by means of Hello messages. LDP has four major functions: -The discovery of LSRs that are running LDP -Session establishment and maintenance -Advertising of label mappings -Housekeeping by means of notification When two LSRs are running LDP and they share one or more links between them. change.20 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network FEC is the set of packets that are mapped to a certain LSP and are forwarded over that LSP through the MPLS network.3.

21 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Student: Trần Quang Hải Đăng .

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network PART 2: OVERVIEW ABOUT QOS. Student: Trần Quang Hải Đăng .22 - .

and calculate features for control and manage transmit information among nodes into network.23 - . 2. Integrated services (IntServ) defines a different model for QoS than does DiffServ. make lists sequencing and tools for transmit information on network). There are three part for enforce QoS : -QoS in a environment single network (as arrange sequence. Architectures of QoS.1. The original work grew out of the experiences of the IETF in multicasting the audio and video for IETF meetings in the early to mid-1990s.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2.4. IntServ defines a signaling process by which an individual flow can request that the network reserve the bandwidth and delay needed for the flow. administer. Student: Trần Quang Hải Đăng . Figure 2.5.IntServ model. -The technique transmit signal for regulate QoS among factors into network.4. IntServ model. -The policy QoS.

IntServ uses Resource Reservation Protocol for signaling to reserve the bandwidth. waiting on the confirmation to flow back to the originator (Hannah).Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network IntServ admission control decides when a reservation request should be rejected. but implementing a guarantee for delay is a little more difficult. Each router holds the bandwidth temporarily. At each router along the route. and none of the flows would get the requested service. was developed to provide an Internet-scale QoS model. IntServ has some obvious disadvantages. eventually too much traffic would perhaps be introduced into the network. but the configuration can quickly become an administrative problem because Student: Trần Quang Hải Đăng . Therefore.24 - . which brings up two issues—whether the hosts can be trusted by the network and whether the hosts actually support RSVP. and it has several advantages. When each router sees the reserve RSVP command flow back to the originator. each router completes the reservation. IntServ expects the hosts to signal for service guarantees. In fact. the network may no longer be able to support the reservation. or links fail and routing convergence occurs. routers can be configured to reserve bandwidth on behalf of hosts. the originator of the flow (Hannah) begins signaling. If all requests were accepted. If the network changes. IntServ actually predates DiffServ. “Can I support this request?” If the answer is yes. With a full IntServ implementation (more on that later). DiffServ. What does it mean for the router to “reserve” something? In effect. the router asks itself. the router reserves the correct queuing preferences for the flow. to some degree. Alternatively. because IntServ scales poorly. RSVP continues signaling for the entire duration of the flow. for instance. IOS. it forwards the request to the next router. IntServ RFCs actually define the term “guarantee” as a relatively loose goal. just reserves the queuing preference. such that the appropriate amount of bandwidth is allocated to the flow by the queuing tool. RSVP reserves the bandwidth when the flow initializes and continues to ensure that the flow can receive the necessary amount of bandwidth. and it is up to the actual implementation to decide how rigorous or general to make the guarantees. RSVP can also request a certain (low) amount of delay.

Also IntServ works best when all intermediate networks support IntServ. information packages classified become a lot of priority group from low to high according to feature of each service.2. which service has priority higher will provided resource at regime better. Activity of DiffServ Activity of DiffServ can describle as follows: First. Instead of perform through QoS and unity on all line as IntServ model. The DiffServ model can flexible high and extend large. the Diffserv model perform QoS individually on each router. 2. so DiffServ unnecessary signal to follow each flow therefore economize bandwidth and can extend. approprivate with large network model. the resource will be returned for system and used by other services.4. device will provide authority used resource more priority. Student: Trần Quang Hải Đăng . Salient features in manage resources of DiffServ model implemented at: -The DiffServ model don’t implement to signal. -The DiffServ model manage resource effectly because it don’t reserve resources for any of a services.25 - . shake hand when establish flow therefore it is losed bandwidth for signal. resource will used by lower group if higher group don’t use. Services devided follow sequence priority. The DiffServ model designed to repair limits of IntServ model. when haven’t flow.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network additional configuration would need to be added for each reserved flow. DiffServ model.

structure press header will economize bandwidth.26 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Video packet Voice packet Figure 2. This event will cause late and Student: Trần Quang Hải Đăng . First. When package come to these interfaces. packages will marked for differentiate. -Press header: Header hold large part in a package but don’t have real information.DiffServ Model Data packet Solution QoS follow DiffServ performed follow steps: Mark and classify package. package will classified follow each queue rely on priority. -Avoid obstructed: Structure reject package before obstructe. -Put threshold: Structure put upper threshold. after that arranged in group conformably. - Fragmentate: data packages often have large length. Mark and arrange will helf for perform QoS at after steps: -Manage obstructed: Structure manage obstruct to performed on interfaces of network device.6 . under threshold for bandwidth. specific is bandwidth will ensured a under threshold minimum and when larger than upper threshold package can be rejected or move to queue.

the IOS must determine which packets have RTP headers. many of you will already know something about several of the QoS tools Student: Trần Quang Hải Đăng . To put one packet into a different queue than another packet.3.4.Compare IntServ model and DiffServ model 2. the IOS must somehow differentiate between the two packets. Classification. If an IOS QoS feature needs to treat two packets differently. To perform header compression on Real Time Protocol (RTP) packets. you must use classification. have a lot of flow network Resource wasted high Don’t manage resource Resource wasted little because Manage resource to rely on marked before that priority of each flow Tabel 2.1.Difference between InServ model and DiffServ model. IntServ DiffServ Use signal protocol RSVP for fight Don’t use protocol resource Use for small network and little flow Use for large network and small network network. but not on other packets.27 - . Almost every QoS tool uses classification to some degree. the IOS must differentiate between Voice over IP (VoIP) and data packets.5.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network obstructed. Because most QoS tools need to differentiate between packets. most QoS tools have classification features. To shape data traffic going into a Frame Relay network. In fact. Structure fragmentate will mince these packages become smaller packages for avoid obstructed. 2. so that the voice traffic gets enough bandwidth.

as opposed to allowing or denying (dropping) a packet. or until the classification logic is complete. Marking is used to establish information in heading package class two or class three. For instance. -If the packet was not matched. Most classification and marking tools.6. and so on. MPLS EXP bit. if ACL 102 permits a packet. group QoS. Because most QoS tools classify traffic. traffic shaping could be called classification and traffic shaping. until it is matched. Some gait description flow are used for mark as: class of service (CoS). generally operate on packets that are entering or exiting an interface. DSCP. If ACL 101 permits a packet. Similarly. Marking. IP priority. Student: Trần Quang Hải Đăng . classification and marking logic for ingress packets can be described as follows: -For packets entering an interface.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network described in this book. but the action is marking. and you will realize that you already know how to perform classification using some of those tools. however. and then mark a potentially different field with a potentially different value. and so on. The logic works something like an ACL. 2. In one way of thinking. compare it to criteria 2. queuing could instead be called classification and queuing. many QoS tools enable you to classify using access control lists (ACLs). if they match criteria 1. More generally. the names of most QoS tools never evolved to mention the classification function of the tool. mark a field with a value. a queuing tool might put the packet into one queue.28 - . because the queuing feature must somehow decide which packets end up in each queue. -Keep looking for a match of the packet. policing could be called classification and policing. it is placed in a second queue. Marking accept network devices classify package or frame rely on gait specific description flow. like the other types of QoS tools.

2. Then QoS technical can apply compatible for right ensure with manage QoS policies. 2.First-in. First In – First Out Queuing. first-out (FIFO) .1. other field are not. Queuing tools. the way is use algorithm queue for arrange traffic and determine some methods for decentralization priority of traffic. Marking is element useful because it accept network device recognize easily packages or frames follow specific classes.29 - . The first reason that a router or switch needs output queues is to hold a packet while waiting for the interface to become available for sending the packet.Custom queuing (CQ) . And making on WAN same. IOS of Cisco support some tool following: . We can mark a lot of field correlative for each specific request.Low Latency Queuing (LLQ) Every algorithm was design for solve problem when transmit messages in network. Some choose inner mark to grill with all device inner local network while other ones only use on base hardware default.7. Some field are used a lot of.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Mark package or frame and classify accept network device discriminate easily packages or frame marked. and it is effect for network.Weighted fair queuing (WFQ) .7. Student: Trần Quang Hải Đăng . We have one way for control information overflow.Priority queuing (PQ) . Marking include organize some bits inner a data-link class or network header with purpose helpful for QoS tools of other device can classify rely on some value marked.

Student: Trần Quang Hải Đăng . namely classification and scheduling. FIFO Queuing does not need the two most interesting features of the other queuing tools. if follow queue packet 1 can pass first and next are three packets 2. packets may experience more delay and jitter. If you configure a longer FIFO queue. Queue has three packets 4. fewer packets will be dropped. less delay occurs. like reordering packets. which is configurable. If the queue is less likely to fill. With a shorter queue. The only really interesting part of FIFO Queuing is the queue length.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Whereas the other queuing tools in this chapter also perform other functions.7 – FIFO Queue. 1. 3. FIFO Queuing uses tail drop to decide when to drop or enqueue packets. 2. and how the queue length affects delay and loss. 3. However. more packets can be in the queue. FIFO Queuing just provides a means to hold packets while they are waiting to exit an interface. FIFO Queuing uses a single queue for the interface. 4. Because there is only one queue. Figure 2. with a longer queue. These facts are true for any queuing method. Also there is no need for scheduling logic to pick which queue from which to take the next packet. but the single FIFO queue fills more quickly. there is no need for classification to decide the queue into which the packet should be placed.30 - . which in turn causes more tail drops of new packets. which means that the queue will be less likely to fill. including FIFO.

and Low. called High. and minimal jitter. PQ schedules traffic such that the higher-priority queues always get serviced. when congested. packets in the lower queues take significantly longer to be serviced than under lighter loads.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2.31 - . the complete logic of the scheduler can be easily represented. when the link is congested. In fact. Normal. PQ can set the queue length to a value of zero.2. can be changed—in fact. if the appropriate queue is full.7. Most of the rest of the details about PQ can be easily understood. which means the queue length is infinite. The lower queues suffer. Figure 2. as mentioned earlier. user applications may stop working if their packets are placed into lower-priority queues. with the side effect of starving the lower-priority queues. It uses a maximum of four queues. The only drop policy is tail drop—in other words. Priority Queuing’s most distinctive feature is its scheduler. Medium. With a maximum of four queues. The PQ scheduler has some obvious benefits and drawbacks. The length of each queue. which of course affects packet loss and delay. In fact. Priority Queuing. Packets in the High queue can claim 100 percent of the link bandwidth. PQ classifies packets based on the content of the packet headers. the packet is dropped. after classifying the packet. Student: Trần Quang Hải Đăng .8 – Priority Queue. with minimal delay. however.

Student: Trần Quang Hải Đăng . The negative part of CQ. one web browser. even running one FTP connection. and CQ can share information of network with different applications by small traffic and delay time can agree.7. size of queue with every class of packet and process of packet are use round-robin algorithm. It has 16 queues available. or make sure for transmit information will be ok with bandwidth we issue and establish. CQ was design for some applications or associates.3. 2. where in the network has obstructed network. If we use particularity of CQ algorithm support by Cisco for make sure about bandwidth. making PQ impractical for most applications today. CQ addresses the biggest drawback of PQ by providing a queuing tool that does service all queues. bandwidth must be balance with every application and user. Custom Queuing. In environment like that. and two VoIP calls when creating the output for this section of the book.32 - . However. Custom Queuing (CQ) followed PQ. implying 16 classification categories.and jitter-sensitive traffic. even during times of congestion. For instance.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network PQ works great for QoS policies that need to treat one type of traffic with the absolute best service possible. which is plenty for most applications. is that CQ’s scheduler does not have an option to always service one queue first (like PQ’s High queue) so CQ does not provide great service for delay. PQ’s service for the lower queues degrades quickly. the TCP connections for the FTP and HTTP traffic frequently timed out. Requests of guest will be arrange by set up some tools. one NetMeeting call. as compared to PQ.

). So. Similar PQ. Router will do that. arrange information into queue form queue 1 to queue 16. The other large difference between WFQ versus PQ and CQ is the scheduler. example test keepalive always send update connection….9 – Classification and move packet into SNA queue. Algorithm will arrange messages into 1 of 17 queues (queue 0 store message of system of system. Weighted Fair Queuing differs from PQ and CQ in several significant ways. In figure 3. The first and most obvious difference is that WFQ does not allow classification options to be configured! WFQ classifies packets based on flows. which simply Student: Trần Quang Hải Đăng . arrange every byte. and router use roundrobin algorithm.7. and the same source and destination port numbers. and we issue remain bandwidth for another protocol. That function is make sure not application can operate can use resource highest than system issue. 2. We can provide a haft of bandwidth for transmit data in SNA system. CQ is configuring static and don’t automatic update if network has change.4. example IP or IPX.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Figure 2.7. A flow consists of all packets that have the same source and destination IP address.33 - .3. packing of SNA system need ensure some small amount of service. Weighted Fair Queuing. no explicit matching is configured.

WFQ use algorithm different with algorithm every queue tools.8 kbps. Student: Trần Quang Hải Đăng . every traffic row can have 12. rows issue number IP Precedence + 1. WFQ can describe like this: -Every rows have the same priority of packet will be have the same bandwidth. and it don’t care rows have how many byte in every traffic row. that different is control more traffic. traffic has IP Precedence has value 7. if the row has precedence highest with has bandwidth high. classifies traffic into flows. so delay time will be big. -TCP destination port or UDP destination port. Example. lower-precedence flows. -TCP source port or UDP source port. and this traffic has bandwidth high bandwidth of IP Precedence has value 0. However. These queues more than every different queue tools. or just WFQ.34 - . Also because WFQ is flow based. -If row has different precedence. For do that. higher-precedence flows over large-volume. router has total different queues. and each flow uses a different queue. -Transport protocol. Flows are identified by at least five items in an IP packet: -IP source. -IP destination. And goal second of WFQ is provide enough bandwidth for traffic rows have high precedence. if WFQ is controlling 10 queues with different IP Precedence in port has 128 kbps. WFQ will priority for rows have traffic small and priority high. Flow-Based WFQ. -Value Precedence of IP packet. Example. Because WFQ classification packet to rely on row of different traffic and then it move that row into different queue. -Finally.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network favors low-volume.

and it call SN.35 - . Syntax to calculate one after another number SN of packet in flow traffic like this: SN= SN number before +( weight*length of new packet). Mechanism WFQ issues every packet with one after another index SN when packet goes into WFQ queue. Weight like this: Weight=32384 / (IP_Precedence+1) Student: Trần Quang Hải Đăng . WFQ use regulator time so simple. include length and priority of packet.10 – Model of operation WFQ Time process WFQ To get purpose issue bandwidth. Regulator time use packet has one after another index low sequence number. when it transmit packet in the next hardware queue. Process issue one after another SN is a part important in mechanism regulator time of WFQ.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Figure 2. Regulator time WFQ calculates one after another numbers SN by parameters of flow traffic.

packets have high priority. In figure 2.Describe calculator SN (Sequence Number) After one after number SN was issue. next work chooses which the packet will be removed in regulator time device.36 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Syntax reference to length of new packet. the first packet in a flow traffic is don’t has one after number SN of the first packet if it was use that syntax. and it will have low SN. and it use one after number SN follow a new next flow. Calculator one after another number so easy. However.11. By consider length of packet. describe how two packets issue two one after another. Figure 2. It will take packet has low SN in queue.11. weight of flow traffic and value of SN before. and packets have big size and one after another SN number low more than packets have small size. and calculator one after another SN number may be has a high SN number for packets. syntax will calculator and result is a biggest SN number than packets in queue has biggest packet. Syntax describe one after another SN of the end packet will move into hardware queue. Student: Trần Quang Hải Đăng . It will issue (IPP+1). Include one after another SN number of packet before it moves in queue.

However. number and length of queue. That decide don’t belong to one queue. -First.37 - . hold-queue limit is a local number. Different way. but if traffic through router still crush. WFQ will consider the best limit of all packets in queue. packet will be drop. If the length of queue longer than CDT. packet will be drop. Before packets move into queue. Packet with one after another number in queues of WFQ will be drop. WFQ consider length of queue and packets are move in queue. CDT limits the number of packets in each individual queue. Figure 2.12 – Describe process of WFQ The hold-queue size limits the total number of packets in all of the flow or conversation queues. and limit call is hold-queue limit. In operator of router. If CDT packets are already in the queue into which a packet Student: Trần Quang Hải Đăng .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Policy to reject packet of WFQ. router must reject packet to avoid obstructed. congestive discard threshold will test with the true length of queue. WFQ use second process and call modified tail drop for choose what packet will reject. and calculates by total WFQ queue. If packet goes to queue and hold-queue is limit. but new packet will not drop. it belong to queue system of WFQ. -Second. although traffic match in queue.

Like the other queuing tools with WFQ in the name. in that it can be used to reserve minimum bandwidth for each queue. but it differs from WFQ in that it does not keep up with flows for all the traffic. To help overcome confusion. but one class queue. the actual value can only be a power of 2 between 16 and 4096. WFQ can be configured for a maximum of 4096 queues. WFQ instead discards the packet with the larger SN! It’s like going to Disneyland.7. At the end of this section. WFQ considers discarding the new packet. Class-Based Weighted Fair Queuing. however. and you will have to come back later. 2. Normally. CBWFQ is like WFQ in that CBWFQ can actually use WFQ inside one particular queue. getting in line. The IOS restricts the values because WFQ performs a hash algorithm to classify traffic. with a maximum and default queue length of 64.5. the features of CBWFQ are covered in the next several pages. the new packet is discarded. All 64 queues can be configured.38 - . inclusive. CBWFQ uses features that are similar to some other queuing tools. called class-default. but it differs from CQ in that you can configure the actual percentage of traffic. and completely different from others. and the hash algorithm only works when the number of queues is one of these valid values. rather than a byte count. so you cannot ride the ride. though!) In short. some summary tables list the key features and compare CBWFQ to some of the other queuing tools. but interestingly. CBWFQ is like CQ. If the explicitly configured classification does not match Student: Trần Quang Hải Đăng .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network should be placed. Finally. (Hopefully Disney would not take you out of the line and send you to the bit bucket. Many people find it difficult to keep the details memorized. WFQ can discard a packet in another flow when the queue for a different flow has exceeded CDT but still has lower sequence numbers. If a packet with a larger SN has already been enqueued in a different queue. CBWFQ supports 64 queues. is automatically configured. You can configure the CDT to a value between 1 and 4096. inclusive. and then being told that a bunch of VIPs showed up.

for the traffic you know about. You are allowed to change the configuration details regarding this default class. CBWFQ and LLQ support 64 queue or classes. different is command for bandwidth and priority. include NBAR. For the traffic you cannot characterize. Maximum queue can change. CB and LLQ configuration are similar.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network a packet. and fairly assign the rest of the bandwidth with WFQ. where you can dynamically apply some fairness to the default traffic by using WFQ. IOS places the packet into the class-default class. You may recall that WFQ is actually a very good default choice for queuing. both CBWFQ and LLQ are use the same syntax of MQC when configure. and reserve the right amount of bandwidth for the class. rather than a byte count. Because two tools are using MQC. but this one class always exists. with CBWFQ. CBWFQ provides a great advantage by allowing WFQ to be used in the classdefault queue. So. Cisco creates CBWFQ and LLQ. so class-map for classification and policy map create group traffic in one gate. and many low-volume flows are also interactive flows. with maximum value and default length by router. but it differs from WFQ in that it does not keep up with flows for all the traffic. because it treats low-volume flows well. in that it can be used to reserve minimum bandwidth for each queue. CBWFQ uses features that are similar to some other queuing tools. CBWFQ is like CQ.39 - . CBWFQ is like WFQ in that CBWFQ can actually use WFQ inside one particular queue. but it differs from CQ in that you can configure the actual percentage of traffic. this mean it has option for classification. makes CBWFQ a very powerful queuing tool. Student: Trần Quang Hải Đăng . WFQ also treats packets with high precedence well. Add. Queue exist when it don’t be configure. The capability to reserve bandwidth for some packets. CBWFQ can configure for default group. you let it default into the class-default queue. and completely different from others. you classify it.

.13 – Operation of class-based WFQ (CBWFQ) . Features of CBWFQ Regulator time of CBWFQ make sure little ratio of bandwidth in every queue. every queue will has a hundred percent bandwidth.Tail drop is mechanism to default reject CBWFQ.40 - . it will use bandwidth in little time. If all queues have big amount of packets.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Structure of CBWFQ Figure 2.CBWFQ support multi diagram class for classification traffic in correlative queue. However. Feature CBWFQ Classification Describe Classifies based on anything that MQC commands can match Drop policy Tail drop or WRED. queues are empty and some queues need bandwidth. configurable per queue. Student: Trần Quang Hải Đăng .

Supervisor: Nguyễn Đức Quang Number of queues 64

QoS over MPLS for Hutech network

Maximum queue length

Can change by type of router and memory. FIFO on 36 queues; FIFO or WFQ on class-default queue.

Scheduling inside a single queue

Scheduling among all queues

The result of the scheduler provides a percentage guaranteed bandwidth to each queue.

Table 2.2 – Feature WFQ.

2.7.6. Low-Latency Queuing.
Low Latency Queuing sounds like the best queuing tool possible, just based on the name. What packet wouldn’t want to experience low latency? As it turns out, for delay (latency) sensitive traffic, LLQ is indeed the queuing tool of choice. LLQ is simple to understand and simple to configure, assuming you already understand CBWFQ. LLQ is not really a separate queuing tool, but rather a simple option of CBWFQ applied to one or more classes. CBWFQ treats these classes as strict-priority queues. In other words, CBWFQ always services packets in these classes if a packet is waiting, just as PQ does for the High queue. LLQ introduces some new lingo that you may find a little tricky. From one perspective, something like PQ has been added to CBWFQ, so you can expect to read or hear phrases that refer to the low-latency queue as “the PQ.” Someone might say, “What did you put in the PQ?” What he really wants to know is what type of packets you classified and placed into the queue in which you enabled the LLQ feature of CBWFQ. In addition, the queue in which LLQ is enabled is sometimes just called “the LLQ.” Therefore, if you use CBWFQ, and use the Student: Trần Quang Hải Đăng - 41 -

Supervisor: Nguyễn Đức Quang

QoS over MPLS for Hutech network

priority command to enable LLQ in one of the classes, you are really using LLQ, and that one class with the priority command is “the LLQ” or “the PQ.” LLQ search and action similar CBWFQ, different LLQ is permit some of lowlatency queues. LLQ similar PQ, LLQ always serve packets in first queue. Sometime, LLQ can use in different way. If policy has little LLQ, this policy is doing LLQ, and queue can call LLQ. Sometime LLQ is similar PQ. When LLQ add into queue with delay time lower than CBWFQ, it can prevent die of queue PQ. In figure 3.7.6, describe operate of algorithm LLQ. Note, although one component run PQ algorithm is show, but this component was control by bandwidth.

Figure 2.14 - Describe operate of LLQ LLQ can permit queue configure same with PQ. So have a question “What queue is serving first?” Actually, LLQ put packets from LLQ queues in inside queue. So,

Student: Trần Quang Hải Đăng

- 42 -

Supervisor: Nguyễn Đức Quang

QoS over MPLS for Hutech network

packets in priority different queues are serving, after that queues don’t priority are serving. When we control bandwidth of class, we must correct to change different LLQ. Example, we must correct to change voice data and video data, we can put traffic data has low delay, and we must apart from voice data and video data.

Student: Trần Quang Hải Đăng

- 43 -

44 - . Student: Trần Quang Hải Đăng .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network PART 3: QOS OVER MPLS.

16 . In type of service field. IP precedence value 0 Binary value 000 Priority Routine Student: Trần Quang Hải Đăng .45 - . from bit 3 to bit 5 are use. And they used for implement quality of service. And they become DSCP.8. they have 6 bit for quality of service and increase 64 level. Figure 2. IPP. DSCP and MPLS EXP. Example TCP or UDP. too little. But three bit is enough for eight levels. Figure 2.1. Relation about IPP.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2. 64 level enough for implement quality of service. So IETF discovery to make bit used for quality of service can increase.Type of Service (byte) From bit 0 to bit 2: these are three precedence bit. And that field used for implement quality of service. show service of packet. 2.15 – Architecture of IP header In IP header has type of service field.8.

DSCP value DSCP 0 DSCP 8 DSCP 16 DSCP 24 DSCP 32 DSCP 40 DSCP 48 DSCP 56 DSCP 10 DSCP 12 Student: Trần Quang Hải Đăng Binary 000000 001000 010000 011000 100000 101000 110000 111000 001010 001100 . DSCP.Describe IPP value 2.Supervisor: Nguyễn Đức Quang 1 2 3 4 5 6 7 001 010 011 100 101 110 111 QoS over MPLS for Hutech network Priority Immediate Flash Flash override Critical Internetwork Control Network Control Table 2. and through a DiffServ domain. With EF: lose packet is hard possible. And we have two types forwarding in model DSCP: expedited forwarding (EF) and assured forwarding (AF).DSCP byte.46 - Name Default CS1 CS2 CS3 CS4 CS5 CS6 CS7 AF11 AF12 . DSCP is a part wire-open of IP Precedence.3.17. With AF: Define services forwarding will make sure. Figure 2.2.8. and end-to-end service must through DiffServ domain. bandwidth make sure.

18 – MPLS header Exp bits in MPLS header are similar Precedence bits in IP header.3. In IP header has ToS field. 2. And three bit Exp is used for implement quality of service in MPLS network. and three Exp bit are similar Precedence in IP header.8.47 - .Supervisor: Nguyễn Đức Quang DSCP 14 DSCP 18 DSCP 20 DSCP 22 DSCP 26 DSCP 28 DSCP 30 DSCP 34 DSCP 36 DSCP 38 DSCP 46 001110 010010 010100 010110 011010 011100 011110 100010 100100 100110 101110 QoS over MPLS for Hutech network AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF Table 2. MPLS header has three MPLS bit. and ToS has three bit used for implement quality of service in IP network.4. Student: Trần Quang Hải Đăng . Figure 2.DSCP value CS: Class selector EF: Expedited forwarding AF: Assured forwarding. In MPLS network. MPLS EXP.

20 shows how the TOS field is divided.IP header field Figure 2. however. Therefore. DiffServ with IP packets. DiffServ ended up with six bits.9. The four TOS bits were deprecated. the IETF decided to dedicate more bits for QoS.20 – The TOS Byte of the IP Header Defining the Precedence Bits The usage of the precedence bits for QoS is now widely used throughout the world for many networks. providing more than enough levels of QoS. is that only three exist. which means you can have only eight levels of service. Refer to Figure 2. Student: Trần Quang Hải Đăng .21 shows you which bits of the TOS byte are used for DiffServ.48 - . and three of them were assigned to DiffServ QoS. Figure 2. Figure 2.19 to refresh your memory about what the IP header looks like.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2. in addition to the three precedence bits. Figure 2. The drawback of the precedence bits.19.

each with three drop precedence.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Figure 2. AF23. Name AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 DSCP (Binary) 001010 001100 001110 010010 010100 010110 011010 011100 011110 100010 100100 100110 DSCP(Decimal) 10 12 14 18 20 22 26 28 30 34 36 38 Table 2. denotes class 2 and drop precedence 3. Four classes exist for the traffic. relative to the other packets with lower drop precedence when congestion occurs. with I being 1 to 4 for the class and j being 1 to 3 for the drop precedence. end-toend service through a DiffServ domain. assured bandwidth. The first three bits of the six-bit DSCP field define the class. and the last bit is reserved. for example. low latency. EF is a low loss. and three levels exist for drop precedence. AF classes are noted as Afij.21-The TOS Byte of the IP Header Defining the DSCP Two types of forwarding classes within the DiffServ model are defined: expedited forwarding (EF) and assured forwarding (AF). The higher the drop precedence inside a class. AF defines different services of forwarding assurances through a DiffServ domain.5 . the next two bits define the drop precedence. the more likely the packet is to be dropped.Recommended Values for the Four AF Classes Student: Trần Quang Hải Đăng .49 - . low jitter. Four classes of AF are defined.

and traffic conditioning and that you can use low-latency queuing (LLQ). With an E-LSP. In figure 2.Four AF Classes and Three Drop Precedence 2. you can call the label switched path (LSP) an E-LSP. congestion avoidance. indicating that the label implicitly holds part of the QoS information. They are called experimental. classStudent: Trần Quang Hải Đăng . congestion management.50 - . but only the drop precedence. An LSP is a signaled path through the network between two routers. the EXP bits hold both the class and the drop precedence information. when you are using MPLS. you have another option for implementing QoS for the labeled packets. However. there are three EXP. If you use these three bits for QoS. With an L-LSP. The LSR needs only to look at the EXP bits of the top label to determine how to treat this packet.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Drop precedence Low Medium High Class 1 001010 001100 001110 Class 2 010010 010100 010110 Class 3 011010 011100 011110 Class 4 100010 100100 100110 Table 2. bits. then you need one label per class for each flow of traffic between the two endpoints of the LSP. You can use these bits in the same way that you use the three precedence bits in the IP header. You can use the label on top of the packet to imply part of the QoS for that packet. it needs only to look up the top label in its label forwarding table (LFIB) to decide where to forward the packet. DiffServ with MPLS packets.6. The same is true for the QoS treatment. whereas the label indicates the class. Remember that QoS constitutes traffic marking. or experimental. When an LSR forwards a labeled packet. indicating that the label switching router (LSR) will use the EXP bits to schedule the packet and decide on the drop precedence. However. the signaling protocol has to be able to signal a different label for the same LSP or prefix. Therefore. Such an LSP is called an L-LSP. but they are really used only for QoS.10.18. the EXP bits still hold part of the QoS.

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network based weighted fair queueing (CBWFQ). You can use the same features to implement QoS based on the EXP bits for labeled packets. straightforward way of configuring the different QoS building blocks on the router. weighted random early detection (WRED). and shaping to implement this for IP packets.51 - .Imposition. The preferred way to configure MPLS QoS in Cisco IOS is by means of the Modular Quality of Service Command Line Interface (MQC). Disposition and Swap of MPLS labels Student: Trần Quang Hải Đăng . policing. MQC is an easy. Imposition Swap and Imposition Disposition Figure 2. WRED has been modified to look at the EXP bits to determine the drop precedence of labeled packets when being queued. For example.22.

In the Pipe model. this does not always apply to all tunneling modes. Diffserv Tunneling Modes introduces a new Per−Hop−Behavior (PHB). DiffServ Tunneling Modes for MPLS networks. Uniform. The tunneling mode is defined at the edge of the network.52 - .11. On an intermediate LSR (a P router). the LSP DiffServ information of the outgoing label is derived from the LSP DiffServ information of the incoming label.11. normally in the PE label switch routers (LSRs) (both ingress and egress). The Tunneled DiffServ information is the QoS information that needs to get across the MPLS network transparently. Short-Pipe. You may need to make changes in the P routers. It may be necessary to copy the MPLS EXP value from the top label that is being popped to the newly exposed label. Pipe Model. The LSP DiffServ information is the QoS (the value of the EXP bits) of the MPLS packets transported on the LSP from the ingress LSR to the egress LSR. 2. the following rules apply: The LSP DiffServ information is not necessarily (but might be) derived from the Tunneled DiffServ information on the ingress LSR. which allows differentiated QoS in a provider’s network. you must also consider what occurs when the topmost label is removed from a packet due to Penultimate−Hop−Popping (PHP). The Tunneled Diffserv information is the QoS of the labeled packets or the precedence/DSCP of the IP packets coming into the ingress LSR of the MPLS network. The MPLS network support of Diffserv specification defines these tunneling modes: Pipe. whereas the LSP DiffServ information is the QoS information that all LSRs in this MPLS network use when forwarding the labeled packet.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2. Student: Trần Quang Hải Đăng .1.

the Pipe model becomes a bit easier to explain. and the EXP bits are not propagated to the IP precedence. the EXP bits are propagated from incoming label to outgoing label.23 . The Tunneled DiffServ information is the precedence bits or the DSCP of the IP packet. Figure 2. the forwarding treatment of the packet is based on the MPLS PHB (EXP bits). The rules for the Pipe model now translate into the following: The EXP bits can be copied from the IP precedence or set through configuration on the ingress LSR. and the LSP DiffServ information is not propagated to the Tunneled DiffServ information. This is called the IP PHB (per-hop behavior) hereafter. Student: Trần Quang Hải Đăng . The forwarding treatment op MPLS packets is based on the EXP bits. the forwarding treatment of the packet is based on the LSP DiffServ information. On the egress LSR. The forwarding treatment (classifying and discard behavior) of IP packets is based on the precedence bits or DSCP in the IP header. This is called the MPLS PHB (per-hop behavior) hereafter.53 - . On a P router. The LSP DiffServ information is the EXP bits value of the labels in the MPLS network.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network On the egress LSR.Pipe model If the MPLS network is receiving IP packets on the ingress LSR and the MPLS network is using E-LSPs only.

The forwarding treatment on the egress LSR is different for the Short Pipe model. the third bullet becomes this: Student: Trần Quang Hải Đăng . The short-pipe model shares the same ability of the pipe model to allow an MPLS network to be transparent from the DiffServ point of view. Therefore. Short-Pipe Model. however. The LSP egress uses the tunneled PHB marking to infer the packet PHB and serve the packet consequently. an MPLS network may implement LSPs using the short-pipe model regardless of whether LSRs perform PHP. on how the LSP egress infers the packet PHB.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2. The Short Pipe model is similar to the Pipe model. The short-pipe model represents a small variation of the pipe model. with one difference. even if an LSR re-marks the LSP PHB marking. It also guarantees that there are no changes to the tunneled PHB marking. The short-pipe model differs. Given this difference with the pipe model.11.24 – Short pipe model.54 - .2. Figure 2.

and the LSP DiffServ information is not propagated to the Tunneled DiffServ information. the forwarding treatment of the packet is based on the Tunneled DiffServ information. the forwarding treatment of the packet is based on the IP PHB (IP precedence).3. but it does switch the packets through the MPLS network. In the Uniform model. This only changes the outer QoS information. This change in the LSP DiffServ information is not Student: Trần Quang Hải Đăng . Uniform Model. Notice the change in the first bullet: The LSP DiffServ information must be derived from the Tunneled DiffServ information on the ingress LSR. of course. that third bullet becomes this: On the egress LSR. On an intermediate LSR (a P router). The MPLS network does not have an impact on the QoS information. On the egress LSR. or the LSP DiffServ information. If the MPLS network is receiving IP packets on the ingress LSR. the LSP DiffServ information of the outgoing label is derived from the LSP DiffServ information of the incoming label.55 - . The Uniform model is quite different from the Pipe or Short Pipe model. the Tunneled DiffServ information is derived from the LSP DiffServ information.11. You can instruct the router to change the EXP bits of the top label(s) through configuration (by using MQC in Cisco IOS) anywhere in the MPLS cloud.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network On the egress LSR. This means that a packet belongs to the same QoS class at any time. On the egress LSR. 2. the following rules apply: The LSP DiffServ information must be derived from the Tunneled DiffServ information on the ingress LSR. and the EXP bits are not propagated to the IP precedence. the LSP DiffServ information must be propagated to the Tunneled DiffServ information. The QoS information is always present in the topmost label or in the IP header if the packet is not labeled.

however. Student: Trần Quang Hải Đăng . In this model. The LSP becomes an integral part of the DiffServ domain of the packet as opposed to the transparent transport that the pipe and short-pipe models provided.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network propagated down to the Tunneled DiffServ information in the Pipe model and Short Pipe model on the egress LSR.25 – Uniform model The uniform model makes the LSP an extension of the DiffServ domain of the encapsulated packet. It is. This model proves useful when an MPLS network connects other DiffServ domain and all networks (including the MPLS network) need to behave as a single DiffServ domain. Figure 2. a packet only has a single meaningful PHB marking (which resides in the most recent encapsulation).56 - . This propagation implies that any packet re-marking is reflected on the packet marking when it leaves the LSP. propagated on the egress LSR when you are using the Uniform model. LSRs propagate the packet PHB to the exposed encapsulation when they perform a pop operation.

Router(config)#policy-map IN Router(config-pmap)#class ftpinput Router(config-pmap-c)#set ip dscp af11 Step 4: Create class output and match exp value correlative with precedence value or DSCP value. Router(config)#class-map match-any ftpinput Router(config-cmap)#match access-group 100 Router(config)#class-map match-any httpinput Router(config-cmap)#match access-group 101 Step 3: Marking for class.12.57 - . Router(config)#access-list 100 permit tcp any any eq 20 Router(config)#access-list 101 permit tcp any any eq 80 Step 2: Create class input for every traffic after we classification. Steps implement QoS over MPLS. Step 1: Used ACL for classification traffic after we determine traffic in network.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 2. Router(config)#class-map match-any ftpoutput Router(config-cmap)#match mpls experimental topmost 1 Step 5: Create policy bandwidth for every class output Router(config)#policy-map OUTPUT Router(config-pmap)#class ftpoutput Router(config-pmap-c)#bandwidth 10 Step 6: Apply interface Router(config)#interface serial 1/1 Router(config-if)#service-policy input INPUT Student: Trần Quang Hải Đăng .

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network CHAPTER 3: NETWORK DESIGN AND IMPLEMENT Student: Trần Quang Hải Đăng .58 - .

Because cost for lease-line very high and bandwidth isn’t enough. type of connect between routers use FrameRelay. To settle that problem. include three branches: -Branch 1 in Binh Thanh district.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Before design and implement network for Hutech. Mail server and SQL server. branch 3 connect to branch 1. Three branches connect together. switch for LAN network. branch 3 in Phu Nhuan district. video device. video device and SQL server. so obstruct always occur. Student: Trần Quang Hải Đăng . we introduce about main model of Hutech. switch for connect LAN network. traffic data always hold bandwidth about 50 percent. To troubleshoot this problem. And result we show detail after. video device and SQL server. Before we don’t apply QoS over MPLS for Hutech network. we carry traffic. -Branch 3 similar branch 2.59 - . this branch connect with branch 1. we apply technology QoS over MPLS for hutech network. in this branch include one router to connect branch 1. switch for LAN network. -Branch 2 in Thu Duc district. So other bandwidth doesn’t enough for traffic video. include one router. In this model. In this model. both traffic are ftp and video. in this branch includes one router connect to branch 2 in Thu Duc district and branch 3 in Phu Nhuan district. we have solution can make Hutech network better. Web server. And solutions we show are QoS over MPLS.

use ADSL technology. In branch DH KTCN 1.60 - .1 – Hutech network Explain about connection in Hutech network: Router KTCN 3 connects to Router KTCN 1.BUILING SOLUTION FOR HUTECH NETWORK 3.1.1. Figure 3. Student: Trần Quang Hải Đăng . Real model of Hutech network. type of connect is Frame-Relay technology. type of connect is Frame-Relay technology.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 3.1. Router KTCN 1 connects to Router KTCN 2 . Router KTCN 1 connects to internet.

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 3. Solution model for Hutech network.61 - .2. type of connect is MPLS technology. Student: Trần Quang Hải Đăng .1. Router KTCN 1 connects to Router KTCN 2 .Solution model for Hutech network Explain about connection in solution model: Router KTCN 3 connects to Router KTCN 1. type of connect is MPLS technology. Figure 3.2.

123-18.3 – Simulation model Device description Three routers. Router KTCN 2: -Cisco router 7200. Student: Trần Quang Hải Đăng .BIN Two PCs: one PC is client.123-18. -Ram of router: 96Mb. Simulation model. Figure 3. we use Dynamip software to simulation router. -IOS router: c7200-jk9o3s-mz. Video device: we use webcam to simulation camera.2.123-18. Building simulation model to resolve for Hutech network. 3. -Ram of router: 96Mb.2.BIN. Router KTCN 1: -Cisco router 7200.62 - . -IOS router: c7200-jk9o3s-mz. another PC is server.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 3.1. -Ram of router: 96Mb. -IOS router: c7200-jk9o3s-mz.BIN Router KTCN 3: -Cisco router 7200.

168.1/24 -Serial 1/0: assign IP 10.1. default-gateway: 192. -Fastethenet 0/0: assign IP 192.1.2. interface S1/0 of router KTCN 1 connect to interface S1/0 of router KTCN 2. -Fastethenet 0/0: assign IP 172.0 for connect to FTP server. -Serial 1/1: assign IP 10.168.168. default-gateway: 172.2/24.2. -Run Netflow software for monitor traffic in network.2.Supervisor: Nguyễn Đức Quang Software of PC QoS over MPLS for Hutech network Client: Assign IP 172.1. -Run FTP service.1. -Serial 1/0: assign IP 10. -Serial 1/0: assign IP 10.1 -Window XP.1.1/24 Router KTCN 2: interface S1/1 of router KTCN 2 connect to interface S1/0 of router KTCN 3.1. -Install software LEADTOOLSMultimedia for simulation video traffic.2.168.1.2/16. Description about connection in simulation model Router KTCN 1: interface Fastethenet 0/0 connect to Server PC.1.63 - .1 -Window XP.1.1/16.1/24.1.2/24. Router KTCN 3: interface Fastethenet 0/0 of router KTCN 3 connect to client PC. -Install Total Command 7. In router KTCN 3 we add command to configure Netflow operation.2/24. Student: Trần Quang Hải Đăng .168. Server: Assign IP 192.168.

1.168.255.255.2.255.255.2. KTCN1(config)#ip cef KTCN1(config)#interface serial1/0 KTCN1(config-if)#mpls ip KTCN1(config-if)#mpls label protocol ldp KTCN1(config-if)#tag-switching ip Student: Trần Quang Hải Đăng .255.2.168.1. KTCN1 KTCN3(config)#interface fastethenet0/0 KTCN3(config-if)#ip address 172.255.0 KTCN1(config)#interface fastethenet0/0 KTCN1(config-if)#ip address 192.1 255.1.64 - .1. KTCN3 Note: Two routers KTCN1 and KTCN3 have only MPLS on interface serial 1/0.0 Active MPLS on router KTCN1.1 255.0.255.2.1.1.2.2 255.Implement QoS over MPLS in simulation model.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 3.2.1 255.0 KTCN3(config)#interface serial1/0 KTCN3(config-if)#ip address 10.0 KTCN1(config)#interface serial1/0 KTCN1(config-if)#ip address 10.1 255. with router KTCN2 both interface serial1/0 and serial1/1 have MPLS.2 255.0 KTCN2(config)#interface serial1/1 KTCN2(config-if)#ip address 10.255. KTCN2.0 KTCN2(config)#interface serial1/0 KTCN2(config-if)#ip address 10.255. Assign IP address for interfaces in router KTCN3.255. KTCN2.255.

65 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network KTCN2(config)#ip cef KTCN2(config)#interface serial1/0 KTCN2(config-if)#mpls ip KTCN2(config-if)#mpls label protocol ldp KTCN2(config-if)#tag-switching ip KTCN2(config)#interface serial1/1 KTCN2(config-if)#mpls ip KTCN2(config-if)#mpls label protocol ldp KTCN2(config-if)#tag-switching ip KTCN3(config)#ip cef KTCN3(config)#interface serial1/0 KTCN3(config-if)#mpls ip KTCN3(config-if)#mpls label protocol ldp KTCN3(config-if)#tag-switching ip Note: #ip cef //active cisco express forwarding #mpls label protocol ldp //distribution label by ldp #tag-switching ip //active switch ip on MPLS Configure QoS over MPLS Router KTCN1 (router KTCN1 must imposition label and disposition) Classification flow traffic from server to client by access-list KTCN1(config)#access-list 100 petmit tcp any any eq 20 KTCN1(config)#access-list 100 petmit tcp any any eq 21 KTCN1(config)#access-list 101 petmit tcp any any Student: Trần Quang Hải Đăng .

KTCN1(config)#class-map match-any ftp-in KTCN1(config-cmap)#match access-group 100 KTCN1(config-cmap)#match not access-group 101 KTCN1(config-cmap)#match protocol ftp KTCN1(config)#class-map match-anh video-in KTCN1(config-cmap)#match access-group 101 KTCN1(config-cmap)#match not access-group 100 Note: #class-map match-any ftp-in //create class ftp #match access-group 100 // match traffic ftp into class ftp-in #match protocol ftp // match protocol ftp into class ftp-in Marking for every class KTCN1(config)#policy-map IN KTCN1(config-pmap)#class ftp-in KTCN1(config-pmap-c)#set ip dscp AF13 KTCN1(config-pmap)#class video-in KTCN1(config-pmap-c)#set ip dscp CS4 Note: #policy-map IN // create policy #set ip dscp AF13 //marking class ftp-in with dscp AF13. similar with CS4 Student: Trần Quang Hải Đăng .66 - .Supervisor: Nguyễn Đức Quang Note: QoS over MPLS for Hutech network #access-list 100 // used for classification ftp traffic #access-list 101 //used for classification video traffic Create class input for classification traffic.

Supervisor: Nguyễn Đức Quang Create class output after we marking QoS over MPLS for Hutech network KTCN1(config)#class-map match-any mpls-ftp-out KTCN1(config-cmap)#match mpls experimental topmost 1 KTCN1(config)#class-map match-any mpls-video-out KTCN1(config-cmap)#match mpls experimental topmost 4 Note: #match mpls experimental topmost 1// match MPLS EXP value 1 in the topmost label #match mpls experimental topmost 4// match MPLS EXP value 4 in the topmost label Create policy for traffic output KTCN1(config)#policy-map OUT KTCN1(config-pmap)#class mpls-ftp-out KTCN1(config-pmap-c)#bandwidth percent 20 KTCN1(config-pmap)#class mpls-video-out KTCN1(config-pmap-c)#priority percent 70 KTCN1(config-pmap)#class class-default KTCN1(config-pmap-c)#fari-queue Note: #bandwidth percent 20// active CBWFQ and class mpls-ftp-out has 20 percent total bandwidth #priority percent 70// active LLQ and class mpls-video-out has 70 percent total bandwidth #fair-queue //active WFQ Student: Trần Quang Hải Đăng .67 - .

Supervisor: Nguyễn Đức Quang Apply into interface QoS over MPLS for Hutech network KTCN1(config)#interface fastethernet0/0 KTCN1(config-ig)#service-policy input IN KTCN1(config)#interface serial 1/0 KTCN1(config-ig)#service-policy output OUT Router KTCN2 (Forwarding packet) Copy down MPLS EXP value KTCN2(config)#class-map match-any mpls-ftp-in KTCN2(config-cmap)#match mpls experimental topmost 1 KTCN2(config)#class-map match-any mpls-video-in KTCN2(config-cmap)#match mpls experimental topmost 4 KTCN2(config)#policy-map IN KTCN2(config-pmap)#class mpls-ftp-in KTCN2(config-pmap-c)#set qos-group mpls experimental topmost KTCN2(config-pmap)#class mpls-video-in KTCN2(config-pmap-c)#set qos-group mpls experimental topmost #match mpls experimental topmost 1// match MPLS EXP value 1 in the topmost label #set qos-group mpls experimental topmost // Sets a group ID that can be used later to classify packets Student: Trần Quang Hải Đăng .68 - .

69 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network KTCN2(config)#class-map match-any mpls-ftp-out KTCN2(config-cmap)#match qos-group 1 KTCN2(config)#class-map match-any mpls-video-out KTCN2(config-cmap)#match qos-group 4 KTCN2(config)#policy-map OUT KTCN2(config-pmap)#class mpls-ftp-out KTCN2(config-pmap-c)#bandwidth percent 20 KTCN2(config-pmap)#class mpls-video-out KTCN2(config-pmap-c)#priority percent 70 KTCN2(config-pmap)#class class-default KTCN2(config-pmap-c)#fari-queue Apply interface KTCN2(config)#interface serial1/0 KTCN2(config-if)#service-policy input IN KTCN2(config)#interface serial1/1 KTCN2(config-if)#service-policy output OUT Router KTCN3 (Copy down MPLS EXP to IP Precedence or DSCP) Copy down MPLS EXP value KTCN3(config)#class-map match-any mpls-ftp-in KTCN3(config-cmap)#match mpls experimental topmost 1 KTCN3(config)#class-map match-any mpls-video-in KTCN3(config-cmap)#match mpls experimental topmost 4 Student: Trần Quang Hải Đăng .

70 - .Supervisor: Nguyễn Đức Quang KTCN3(config)#policy-map IN KTCN3(config-pmap)#class mpls-ftp-in QoS over MPLS for Hutech network KTCN3(config-pmap-c)#set qos-group mpls experimental topmost KTCN3(config-pmap)#class mpls-video-in KTCN3(config-pmap-c)#set qos-group mpls experimental topmost #match mpls experimental topmost 1// match MPLS EXP value 1 in the topmost label #set qos-group mpls experimental topmost // Sets a group ID that can be used later to classify packets KTCN3(config)#class-map match-any mpls-ftp-out KTCN3(config-cmap)#match qos-group 1 KTCN3(config)#class-map match-any mpls-video-out KTCN3(config-cmap)#match qos-group 4 KTCN3(config)#policy-map OUT KTCN3(config-pmap)#class mpls-ftp-out KTCN3(config-pmap-c)#bandwidth percent 20 KTCN3(config-pmap)#class mpls-video-out KTCN3(config-pmap-c)#priority percent 70 KTCN3(config-pmap)#class class-default KTCN3(config-pmap-c)#fari-queue Apply interface KTCN3(config)#interface serial1/0 KTCN3(config-if)#service-policy input IN KTCN3(config)#interface fastethernet0/0 KTCN3(config-if)#service-policy output OUT Student: Trần Quang Hải Đăng .

71 - .1.Supervisor: Nguyễn Đức Quang Configure Netflow operate in router KTCN3 KTCN3(config)#interface fastethernet0/0 KTCN3(config-if)#ip route-cache flow QoS over MPLS for Hutech network KTCN3(config)#ip flow-export destination 192.168.222 9996 KTCN3(config)#ip flow-export source fastethernet0/0 KTCN3(config)#ip flow-export version 5 KTCN3(config)#ip flow-cache timeout active 1 KTCN3(config)#ip flow-cache timeout inactive 15 KTCN3(config)#snmp-server communication ktcn3 Student: Trần Quang Hải Đăng .

4 – Get result before implement QoS In figure 3.4. we can see ftp-data traffic more than TCP_App (video traffic) Student: Trần Quang Hải Đăng . Get Result Compare bandwidth before and after we apply QoS over MPLS Bandwidth of network before apply QoS over MPLS Figure 3.72 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network 3.3.

5 – Get result after implement QoS In figure 3.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Bandwidth of network after apply QoS over MPLS Figure 3. we can see video traffic (TCP_App) more than tcp-app traffic Student: Trần Quang Hải Đăng .5.73 - .

Student: Trần Quang Hải Đăng . IPv6 is implementing in some country. we can create something new. and number of address IPv6 more than address IPv4. In IPv6 environment can better security then IPv4. preference with important traffic. to correct the traffic important example voice traffic. If we deploy MPLS on IPv6. example USA. -This model can apply to Hutech network and real network.74 - . video traffic… -Avoiding obstructed.Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network GET RESULT AND DEFINE OF DEVELOP IN SUBJECT GET RESULT: After we implement QoS over MPLS. we were successful and we get result: -Controlling traffic in network. DEFINE OF DEVELOP IN SUBJECT: Present.

75 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Student: Trần Quang Hải Đăng .

Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Student: Trần Quang Hải Đăng .76 - .

77 - .Supervisor: Nguyễn Đức Quang QoS over MPLS for Hutech network Student: Trần Quang Hải Đăng .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->