Cisco SDWAN QoS

hi this video will look at configuring Kunis in Cisco Stephen attached the simple topology we will use for this demo we have a hub device connected with two hub 200 Mbps link and a spoke connector at 20 Mbps link we will simply create a three classic US policy you can create more classes but for this demo we'll stick to three for the first class we will match traffic with DHCP bits EF or 0 XB 18x and map it to q 0 which is the priority queue and allocate 10% of the link bandwidth now since this is a priority queue any traffic exceeding the rate will be polished we will then create a second class which will match traffic with BAC P bits EF 41 and map it to q1 and allocate 30% of the link bandwidth to it and finally we'll create a third class which will match all the rest of the traffic and will have an allocation of 60% of the panel now since these two Q's are rated focues they can leverage to bandwidth available from other queues when there is no traffic on the other peers so let's begin let's go to templates let's go to the interface template attached to this book you and here you can see the only Q's configuration that we have is the shaping rate of India BP is configured on the device now I have put machines connected to the sto edges and I'll be using type of to test so let's check what's available bandwidth from this book you and we can see we are getting our query MVP is search traffic which is pre-configured shaping rate on the device let's consider our cures policy this will be a localized policy let's go to class one let's create a first class and call it q0 and map it to q0 let's create another one which plus q1 q1 and finally a class q2 map it to Qt you extra torque use maps let's call this spoke qsr man it's a dork you let's select q1 you and q1 was supposed to have 30% of the bandwidth see let's add a second cue and give it 60% of bandwidth you now I can see that you have Q zero which is 10% bandwidth q1 at 30% and q2 860 let's see let's get next we don't need any access lists intermixed you let's just first preview the policy this is a policy so let's save it so that's our cue policy that's been defined let's create a centralized policy and map our cues views to our interesting traffic you so this will be our data policy okay next you let's sign up on you let's add a sequence and then here match dhcp 46 which is EF and then associate it to class q0 let's also add a counter and let's call this q0 country you see let's create a second rule and in this role let's match forty ACP 34 which is a 41 and associated to class q1 and an accountant you see let's finally error bathroom here we match everything and then associate it to q2 you it's sensitive all to action to exit see if the policy let's click Next you here let's map it to site now case this should be spoke and the median width should be weeping wall inlets let's preview policy as you can see we are matching DSP 46 and setting it to class q0 so may be matching DCP 34 which is a 41 and mapping it to q1 then you're matching the rest of the traffic to q2 so let's save the policy let's activate the policy what is this done let's go back to templates go to a spoke template put additional templates an ad or policy that we just created save quickly check the country you that's the Q's Maps configuration you let's go back to templates it's time for the feed template go to the spoke interface template let's go to AC lqs and here associated to the Q's map that we defined spoke us MA State you so the configurations have been pushed let's go back to our open to machines let's check our bandwidth again I can still see that we are sort of getting 20 Mbps bandwidth let's try sending traffic on q0 in sy will send traffic marked with dhcp bit EF you use - s0 expiate which means it is sending with the basic a bit of EF and you can see that we are getting about 20 piece of traffic which is 10% of the shaping rate configured the interface as against and our default traffic we can see that it's getting about 20 Mbps and now let's let's push some traffic on q0 and you can see that q0 is getting two MVPs of traffic and you can see the bandwidth on the default queue has reduced but that was mount once the project rocket straps you can see that the default queue traffic starts to utilize the bandwidth available from other queues as well now let's try sending traffic on the q1 which is traffic with dhcp marking of EF 41 so here the bit should be 0 x8 8 which is tcp air for a 1 in X now this was associated 30% of the boundaries of the link so it's getting about 6 MVPs of 20 Mbps link and corresponding you can see that the traffic on the default queue has reduced by that much amount and you are seeing it we are getting about 12 Mbps of traffic and once the traffic on the q1 stops the default traffic is able to utilized all the available bandwidth on the link thus Sisco is divine curious helps you to provide preferential treatment to specific types of traffic and allocated bandwidth based on the requirement that's all for this demo and in a subsequent video we will look at configuring / to milk us thanks for watching

Channel: Narayan Subramanian

Views: 3,928

Keywords: sdwan, cisco, viptela, qos, priority, app experience

Id: RG2cI2V29V4

Length: 11min 29sec (689 seconds)

Published: Thu Jul 16 2020