6.9a Configure and verify IP SLA - ICMP

you are now tuned in to the network the youtube channel that takes complex networking topics and dumps them down to a more simple language today's topic is configure and verify ipsla specifically icmp this is a topic in the ccnp rock exam it'll be known as ccnp enterprise exam come february 24th 2020 so after that it'll be known as again cc ump enterprise let's go ahead and take a look at the exam blueprint to see where we came from and where we are headed hashtag library for daigo don't forget to hit that like button please subscribe to my channel and hit that notification bell that'll let you know when i upload these videos this is the exam blueprint implementing cisco ip routing exam code 300-101 anyway we just wrapped up the section described sla architecture we just briefly described what sla is today we're going to configure and verify it but specifically icmp after that we'll move on to tracking objects so what was uh ipsla well we said sla was service level agreement right it was basically promising somebody hey this is what i'm this is the type of service i'm going to give you ipsla is we're saying basically this is the type of ip services that i'm expecting right well there's different types of ip services right we are going to specifically set up icmp so we're going to be sending and you know what i have cmp is right icmp is basically ping ping is basically sending a message or like a a packet and then expecting it to come back a reply right so it's just like a radar where you send a message and then it comes right back to us right and we're measuring the time of how long it takes to come back if it doesn't come back at a certain time then it did then that's our threshold that's that our that's our expectation when we set a service level agreement let's head over to the slides for the official definition i cmp sla the icmp is one of the main protocols of an ip suite it is mainly used by let's give all this this first bullet point right here icmp is ping y'all know i like to keep it simple the second bullet point ipsla icmp echo operation is to monitor the end-to-end response time in between routers and devices by using ipv4 and ipv6 simply put you look at this topology right here we got this router sends him a ping right that's the destination ip advice we're expecting the echo reply to come back and basically we measure how long it took to get there and come back and then we set a service level agreement right did it take you know 50 seconds to come back did it take 30 seconds to come back did it come did it take 20 milliseconds to come back whatever our agreement is that is our threshold you know it could be because we're you know we're monitoring for a specific company or it could be just an internal agreement internal sla you know that's our expectations that we could have set for ourselves right the icmp echo is most useful for troubleshooting the network connectivity issues so basically ping that's basically what ping does but and that we're going to set ping with an sla so that way if it comes back at a certain time and if it comes if it took too long then we'll either get an snmp trap or we're just measuring we're just going to be constantly sending pins and measure how long it took if if we see it takes longer than expected then it did not meet our sla agreement how do we configure it it's real simple i'm not gonna say that because there it is really flexible on what you can do just to get into the mode it's real simple though this we know how to do right we go to enable mode or privilege exact go to global config mode with configuration terminal and then we type in ipsla monitor i believe some ios is you just type in ipsla and then the number but in this case the the ios version i'm gonna be using it's ipsla monitor and then you create a monitor number so the example below right here ip sla monitor 6 or 5 or 20 whatever the case may be once you do that you are going to be in ipsla operation mode right or config mode rather from there you can set so many parameters you can choose what type you don't have to necessarily pick icmp you can measure voip packets you can measure jitter loss delay all of that stuff right but obviously for this exam we're gonna set up icmp echo messages and measure how long it took and stuff like that we could change the size of the package we could change how often we send a ping message and so on and so forth that's just like extending ping you know if you just type in ping and then it asks you a set of what you'll get a wizard it'll ask you a set of questions um on what you want to do to customize your ping packets right this is kind of the same way but uh we're just doing it for uh for sla purposes so in this case once you're in ipsla configuration mode you type in icmp echo who the destination who are you sending these packets to right in this case it says source but it's really yeah you do the destination first then you can change the source and then move on from and it'll just ask you so many questions we can't obviously cover them all but you know this is what we'll do for uh for the exam we have to do icmp step five is you can choose how often you send it in this case we're sending it you just type in the keyword frequency in this case we're sending it every 300 seconds we're sending a ping packet and that's what we're doing here that's that's the rate of which the specified sip sla operation repeats this is optional obviously you get out of it just type in end i believe you could also do exit here's some show commands show ipsla monitor configuration that shows you how you know you set up your ips la and then you can do statistics to see basically if you're if you're paying uh if your sla messages are failing you also have to set a responder you don't have to but if you want it to work you have to set a responder so like when we look at this right here he will be we're doing the ip sla configuration on this device we would have to set this device as a responder or actually it may be just this device as a responder so somebody got to be a responder to let us know to uh that the pain packets are actually responding but anyways that way we can get our statistics let's go ahead and fire up gns3 y'all know what it is when y'all see this little girl y'all can visit gns3vault.com to get this live as well i'll leave a link in the description below so that way you can practice as well uh and also he does his own he does uh his own video solutions as well if you want to follow his channel his channel as well as on the website also shout out to networklessons.com i get a lot of information and tutorials on that website all right so here's the lab we're going to be working with today we got router lettuce over here cucumber tomato and pickle right they are sitting in a 13 182 160 13 network 12 network 24 network and 34 network we're going to be setting up ip sla icm psla and all of these guys i believe we also will be doing dns http where some of this stuff was kind of out of scope let's go ahead and fire these bad boys up we i believe are already consoled into them let me just refresh them real quick reconnect on all these bad boys sorry for the bad continuity i know y'all noticed i got a new another shirt i had to take the girl out for you know a little date date night tonight she wouldn't let me go finish my video so anyway we've got seven steps here and let's go ahead and get right to it so step one says configure router lettuce which is this guy right here to send icmp echo packets to ip address 44 4.4.4.4 every nine seconds it should never stop so lettuce is going to be sending packets to 4.4 which i believe is this guy let's see if it's tomato enable show ip interface brief yes so he's going to be sending ping packets to this guy and then he'll be measuring them to see how long it takes but he'll be sending them he needs to send them every nine seconds and it should never stop so we're consoled into lettuce right now and let's go ahead and do that the basics configuration for ip sla we said is ip sla monitor and then you choose the operation number that's how you set it up basically so we're in global config mode and again it is ip sla monitor and as you can see right there we can set up a whole bunch of stuff we can set up as a responder but right now we are going to do the entry number which we'll just do this is entry number one this is this is step one right now as you notice we are in sla monitor config mode right so he says we need to send icmp echo packets to the address 4.4.4.4 so what are our options here well we have type of entry when you do contact sensitive help it says you can exit or you type so we'll just do type what else we have after that we can send dns packets dns query packets we can frame relay we can do echo ftp http which one do you think would be ping well we don't see icmp in here right so we're gonna go ahead and do echo since that sounds like the closest thing to it right so we'll say echo what else does he say here protocol context sensitive help says ip icmp echo that sounds like what we want to do right there right so ip icmp we'll just tab it out what's the host name we said it was 4.4.4.4 contact sensitive help says what's the source address well they didn't say we wanted to do a source address or source interface so we may just leave that blank right there and uh could we just enter there i believe we can just enter notice now we are in sla monitor echo mode what did they say after that we could do let's just do see contact sensitive health we have a whole bunch of options here right well the only thing we didn't do was the every nine seconds part and that it should never stop so what do we see here we want to do frequency the frequency of the operation was what we type in frequency says here in seconds how many seconds we said nine seconds we just push enter there because we see your character turn right contact doesn't help after that it says it should never stop what do we see here can we do anything about neter never stop well we do see live of history kept maximum number of history lives to collect what do you think this is super mario no no that's not what we want to do here but you know what i'll just give y'all just tell y'all right now to do the life of an sla you got to get out of this sla configuration mode you just got to go to regular global config mode so we're going to exit out of this now we're in global config mode and we're going to say ip sla right we do monitor we question mark and as you can see right there schedule is right there it is so schedule is what we know we want right there so we type a schedule what's the schedule well it's asking us for the entry number well we created sla monitor number one that's what we need to do so we'll do one right here then it says here we could aid we do age out which is how long to keep this entry when it's inactive that's not what we wanted the length of time we want to execute in seconds that sounds like it right there we're occurring pro to be scheduled automatically every day we didn't say anything about that and the start time that sounds like it too so let's start off with the start time let's go ahead and well he didn't say when to start so let's just go ahead and imply that he wants us to start now by doing just the key word now after that how long to keep this entry he didn't say that length of time that sounds like it reoccurring that don't really sound like it he said it should never stop so let's go ahead with life question mark and as you can see right there the life in seconds no he said it should never stop so forever is the key word we want to use there right so i'm just going to paste that there hit enter that is going to be the schedule we can check our configuration with show ip sla monitor and it's configuration is how we can check it right we do that we can see let me widen that up for y'all this is the configuration for entry number one we didn't specify an owner or a tag we said it's an echo which what's an echo it's just ping really we send in a pet an echo packet to this destination device and come right back that's all it is an icmp echo operation is to monitor the end to end response time in between router and devices by using ipv4 and ipd6 in this case it's lightbp4 the echo must is most useful for troubleshooting the network connectivity issue ping that's all it is that's all it is it's ping what else we got here we said the target address was 4.4 that's what we said didn't do any verified data we said every nine seconds is when we want to send it so we've got a bunch of other stuff here we didn't really specify these and we just left everything else as default so we'll leave it as is that was step one right step two configure router cucumber let's go into cucumber right here to send dns request packets to ip address quad one every eight seconds it should never stop quad one i believe is lettuce let me verify that though lettuce is quad one so we're gonna configure our cucumber to send dns packets to lettuce every eight seconds and that it should never stop so this sounds really similar as the other one except now we're doing dns request packets so we're gonna go into cucumber we're gonna go to global config mode and we said to do that was ipsla monitor we're going to say monitor number two right because this is the step number two we're in again sla monitor config mode what do we want to do we said we want to send dns request packets context sensitive help says we want to type what type we want to do dns right there it is right there dns we'll paste that into that bad boy target address was what we said the target assets was quad 1 so 1.1.1.1 what was the name server we'll just do name saver like that the host name uh we didn't really say so we'll just say quad one uh source we didn't we really didn't want to specify we don't really want to specify one we'll just leave it as is notice we are in sla monitor dns config mode there's so many sub configuration modes there's just so many ways you can figure things anyways uh what is the context sensitive help says we need to set up well we already set up dns request packets we said quad one we need to do every eight seconds how do we do that again is frequency so we say frequency what eight let's go ahead and do a uh oh minimum frequency should be nine so that's a that's a weird one right there interesting you know what i went ahead and checked renee's video solution he just went ahead and skipped that part and just put a nine there so y'all don't be free yeah again you visit gns3volt.com this is where you can get this lab rene monarch also has the video solutions on there so you can check out his website for it or you can just do a search on youtube and you'll see his solutions as well he went ahead and put a nine there so frequency is nine uh and it should never stop we'll just go ahead and do a timeout zero as well so it doesn't time out and we'll say we said it'll never stop right so we're gonna get out of this we're gonna go to ip sla monitor schedule and the schedule was for monitor number two while we are monitored to now we could do start time now life forever okay so i believe that should be it for for uh number two step three configure router pickle which is this guy right here to send g711 packets if you don't know that's pretty much like voip packets or like quality of service type of packets to ip address 2.2.2 which i believe was cucumber let's see actually let's do this let's verify his uh what we just did right there show ip sla monitor configuration and there it is right there right so monitor two what we just created right there entry number two there is no owner or tag dns the target address was quad one source is quad two we didn't specify a port number we said every nine seconds even though renee asked for every eight seconds start time already passed because we said now right life is forever don't you wish we could live forever we didn't specify everything else we left everything else as default so that was set up for that again uh question three says to send g711 packets to ip quad 2 which i believe is cucumber port 16 384 with a codex size of 160 bytes with an interval of 20 milliseconds it should never stop so we're on we need to go to pickle and there's pickle right there and he's going to be sending those packets there's g711 packets to this guy right there right and then test the uh pretty much the sla for it right so we're gonna go into pickle right now we're gonna go to global config mode again the same thing ipsla and remember on the exam even though we're kind of like going and doing dns request packets g711 and and and changing the code exercise and stuff like that for the exam you only got to do icmp so all this stuff is bonus right here but we doing it anyway because you know we're just trying to be more advanced whatever it is and plus that's what that's what uh renee wanted us to do he likes to challenge us so ipsla monitor we're going to call this one monitor number three this is the step number three and then we're gonna go to ipsla monitor mode and then we're gonna say type right what type we said we said g711 right we don't see any g711 here but we know it's a voip type of patrick traffic that's the next one we should go with but we're not gonna do that because i remember looking at this and it wasn't voip traffic it's actually jitter yeah so we're gonna say type jitter destination ip address we said was 2.2.2.2 right so we're going to do 2.2.2.2 the destination port was as you can see one six three eight four destination port and then type in one six three eight four what else we want to do here he said they wanted a codex size of 160 bytes so we're going to say codec well actually we're going to do kodak type first so this just kodak what type he said g711 so you can pick a or you you want to get more into this stuff right here this i believe is quality of service or voip you want to get in collaboration that's what that is and then uh what else they wanted us to do we said the size so kodak size was 160 bytes and then he wanted us to do the interval of 20 milliseconds so we're going to say codec hyphen interval 20 milliseconds and it should never stop we'll do the forever part after that you know we got to get out of this mode right so we'll push enter there notice we are in sla monitor jitter mode configuration mode from here we could do frequency it should never stop right so we say and it's every how many seconds he said and we already did that so we don't need to worry about that the uh it should never stop so basically we want to get into schedule for this so we get out of this and do ip sla monitor which monitor schedule this was a schedule number for operation number three we said the life should be forever what we want to do is start time first let's do start time now life forever right because it should never stop is what he said right there and he didn't say when he wanted us to start so we're implying now step four configure out a cucumber we're going to cucumber right here which is that guy at the top for it to respond to the g711 packets so he is gonna be send those g711 packets we're gonna set him up as a ipsla responder if you don't know what that is i'll put it in the description below on what a responder is basically he's going to be responding to the traffic if you do and i'll show you real quick pickle is going to be sending those packets right pickle's going to be sending it to him so let's check that configuration on step 3 real quick so we're gonna we'll go back to pickle and do a show ipsla monitor configuration and it was configuration number three and if you notice right here we have it does say forever right that was uh configuration number three right we said configuration number three the target address was dot two which is cucumber we didn't specify uh a source address we said the target port was one six three eight four that's the kodak type that's the size of the codec this how often we gonna send it uh if you notice right here it says we there's nothing in here that there should be something here that tells you that nobody's responding to these oh it's not on the configuration it'd be under statistics so we're gonna do show ipsla monitor statistics and then we put the entry number which was three and this is where you're gonna find it at there it is if you notice here it says number success is zero number of failures two so we sent two ipsla messages but kodak uh g uh the g711 packets two of them but they failed why because this guy's not responding so we need to make cucumber a responder and that's what we're going to do here with step four so step four says the configure router cucumber to respond to the g711 packet so we're gonna go to cucumber and we're gonna go to global config mode and we're going to say ipsla we're not going to say we're going to say monitor i guess that's what it was monitor but we're going to say responder he's in a monitor responder this will enable ipsla monitor responder so we're saying responder here the type of protocol we ain't really got to do that we're just going to say responder we could specify which types of stuff but we're just going to say responder now that we do that we're going to go back to pickle and see if he has any responding by doing the statistics again first step three we've got three failures we'll check again later we'll check real quick again because see they're gonna be sent everything i think every 20 i forgot how many times with the frequency on this but it may take a little bit before we see them again now we got a success so now we got a success and this is the uh just statistics if you want to really get into this but again this is out of scope for the ccnp exam this part right here so so we did step four those are responding now step five it says the configure router tomato which is this guy right here to send g729 packets to ip address 3.3.3 which i believe is pickled or lettuce let's see tomato is going to be sending g729 packets to pickle on port 136374 with a codex size of 20 bytes and it should never stop so similar to what we just did except we're using a different port number different destination number and we're sending g729 packets again if you want to know more about this stuff i'll probably leave in the link in description below if i got time so let's go ahead and tomato and go to global config mode we're going to say ip same thing sla monitor we're going to say this is monitor number what this was step number five five now we're in ipsla monitor mode and we're going to say the type was uh again jitter and we're going to say the destination ip address was 3.3.3.3 the destination port we need to put the destination port and then type in one six three seven four didn't really say what source but he did specify the codec type so he said the codec type was g729 we just do codec and then the type was g729 there's only one type right there so g729 we'll do the codec size the size was 20 bytes he also specified that was it he didn't really specify the interval or anything so we'll just hit enter here notice we're in sla monitor jitter configuration mode and from here we could we could do the frequency and timeout we'll set the timeout to be zero we'll set the frequency to be we'll set the frequency to be let's say if we do eight for a jitter yeah i guess we could do eight it should never stop so we gotta get out of this and say ip sla monitor schedule and it was for schedule for number five start time will be now the life will be forever start time and then life so start time and then life if you want to remember the syntax for this and we can again check that with show ip sla monitor configuration 5 and as you can see start time passed life is forever and if we do the same thing with show ipsla monitor statistics notice we've got two failures zero successes why because we don't have a responder right right now he wants to configure router pickle which is this guy right here because remember we did tomato to send those g7 29 packets to test test the the sla for it but now we're gonna set pickle to be the responder go into pickle this guy right there global config mode ipsla monitor responder that's it that was step six last one y'all step seven says to configure actually let's let's check that let's check that let's do let's get out of this show ipsla monitor do we have a responder here yes we could check here we've got it is enabled recent sources none so far we don't have any statistics on that although tomato should be sending us some right maybe because we didn't specify the source not too sure but again don't worry about that don't get too hung up on this some of this this stuff is really out of it's out of scope of the exam in my opinion step seven says the configurator lettuce this guy right here to send http get packets to ip address 34.4 so i'm going to send ip http get packets to that that ip address every 60 seconds so we're going to go into lettuce go to global config mode ipsla monitor monitor 7 and then we're going to say type what was the type y'all can see it right there right it's http operation again you know what http get is right every time you click on a hyperlink or every time you click or you type in something and then the first thing it does is sends a http get request so you're getting information from an http server that's what this is right so http get request what's the url we're gonna just say http colon slash slash let's say network bra dot com no that ain't right what we need to do here maybe we gotta type in url get url and then http colon slash slash network broad dot com what else we need to do here we need to do a source no we didn't did he specify a source is that what he asked for no he just said to send it to that ip address so we're going to say let's say a name server and then the ip address 192 dot 168.34.4 he did not specify anything else he just said if this frequency was every 60 seconds so we leave that in that as is we're going to say frequency was every 60 seconds we're gonna put the timeout at zero so it does not time out um what else did he say i think that's pretty much it that's pretty much it we're going to exit out of that and we're going to double check that with what show ipsla configuration we can verify it with that entry number seven right there let me fix that for y'all see type of operation to perform is http the target address it says quad zero but we do have a url which is networkboor.com that don't look right that don't look right our target address should be 192.168.34.4 so that ain't right we need to fix that we need to fix that let's see here let's go back to configuration mode config terminal ip sla monitor seven we said hold up we might not we might need to do that one over again because now we can't even we can't even put the ip address because that didn't look right this said the target address was quad zero but we did have a http get to this address right here networkbro.com oh you know why because we would have to set up dns we would have to set up like dns and we're not gonna do that that's kind of out of scope for this we just going to leave this as is so that's the reason why we would have to have like maybe like a dns server so that way it um resolves network broad.com to that ip address which was 192.168.34.4 every 60 seconds and we're not going to set that up if you can even check renee's uh video solution for that he doesn't even do that so that is all i got for y'all today that is my youtube page that is my twitter handle we are almost finished y'all we got about four more videos and we are done with this video series i'd like to thank you guys for you know following me and my journey i'll let you guys know when i pass the exam because i promise you i'm gonna pass this exam for now go ahead and please leave a comment below share this video if you like my teaching style and please hit the like button when you leave for now please comment like subscribe to the network

Channel: NetworkBruh

Views: 1,226

Keywords: CCNP, CCNA, IP SLA, ICMP, #labeveryday

Id: Lxn2vqB4Dew

Length: 30min 44sec (1844 seconds)

Published: Thu Sep 05 2019