WEBVTT 1 00:00.000 --> 00:04.200 So for our first IP SLA, we're going to focus on ICMP jitter. 2 00:04.200 --> 00:09.630 And before we go to the CLI on the routers, let's go ahead and configure R8 as 3 00:09.630 --> 00:10.520 a responder. 4 00:10.520 --> 00:14.880 So syntax there is going to be IP SLA space responder. 5 00:14.880 --> 00:18.180 And as a result, for many of these SLAs that we set up, it'll be able to 6 00:18.180 --> 00:20.440 respond and give the information back to R1. 7 00:20.440 --> 00:24.320 And even though the IP SLA responder isn't required for every single possible 8 00:24.320 --> 00:24.960 SLA, 9 00:24.960 --> 00:27.800 for the ones where it is required, it'll be enabled. 10 00:27.880 --> 00:30.950 And an example where it wouldn't be required if we're just doing a connectivity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:27.880 --> 00:30.950 And an example where it wouldn't be required if we're just doing a connectivity 11 00:30.950 --> 00:31.720 test with a ping, 12 00:31.720 --> 00:35.000 it's just ICMP connectivity testing. 13 00:35.000 --> 00:37.080 So we wouldn't need the IP SLA responder for that. 14 00:37.080 --> 00:42.520 But for other features, like ICMP jitter, R8 as a responder can identify when 15 00:42.520 --> 00:45.520 it received that request with a timestamp. 16 00:45.520 --> 00:48.960 It can also document when it sent the response back with another timestamp. 17 00:48.960 --> 00:52.990 And so if we can figure R1 as the probe right here, and let's source the 18 00:52.990 --> 00:54.680 traffic from 1.1.1.1. 19 00:54.920 --> 00:58.810 That's a reachable loop back here on R1. And for the responder down here, we'll 20 00:58.810 --> 01:01.120 use its loop back of 8.8.8.8. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 00:58.810 --> 01:01.120 use its loop back of 8.8.8.8. 21 01:01.120 --> 01:05.620 And so when the probe sends out the ICMP jitter probes down to R8, it's going 22 01:05.620 --> 01:06.920 to be doing its initial timestamp, 23 01:06.920 --> 01:10.720 so it'll be one of them. When R8 receives it, it'll put a timestamp to one. 24 01:10.720 --> 01:14.120 And then when it processes it and says back, it'll send yet another timestamp. 25 01:14.120 --> 01:17.800 So the final response coming back to R1 will include three timestamps. 26 01:17.800 --> 01:22.120 We can also specify the number of packets we want to send in our probe. 27 01:22.120 --> 01:24.000 We can also specify the frequency. 28 01:24.000 --> 01:27.320 So let's go ahead for the number of packets that send three at a time. 29 01:27.320 --> 01:31.680 And for the frequency, let's go ahead and say every 30 seconds. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 01:27.320 --> 01:31.680 And for the frequency, let's go ahead and say every 30 seconds. 30 01:31.680 --> 01:34.400 We can also give an example of setting up a threshold. 31 01:34.400 --> 01:38.650 So let's imagine that the round trip time, even though we're measuring ICMP j 32 01:38.650 --> 01:38.920 itter, 33 01:38.920 --> 01:41.440 we're also going to have information about the total round trip time. 34 01:41.440 --> 01:45.360 Let's set a threshold of 100, meaning 100 milliseconds. 35 01:45.360 --> 01:48.920 And if it's above that number, it would be considered out of compliance or the 36 01:48.920 --> 01:50.400 IPSLA would say fail. 37 01:50.520 --> 01:55.880 So we set a threshold of 100 and the actual round trip time ends up around 125 38 01:55.880 --> 01:56.640 or 130. 39 01:56.640 --> 01:58.760 That would be considered a fail. 40 01:58.760 --> 02:02.540 Or if we're underneath the threshold, that SLA would be considered in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 01:58.760 --> 02:02.540 Or if we're underneath the threshold, that SLA would be considered in 41 02:02.540 --> 02:03.240 compliance. 42 02:03.240 --> 02:07.280 So the three parts of configuring this would be one to tell R8, it's an IPSLA 43 02:07.280 --> 02:07.920 responder. 44 02:07.920 --> 02:10.400 Then on our one, we'll create an IPSLA. 45 02:10.400 --> 02:13.640 And let's go ahead and start with IPSLA number one. 46 02:13.640 --> 02:17.680 As our first example, we'll specify we're measuring ICMP dash jitter. 47 02:17.880 --> 02:21.660 We'll specify the source address, the target address, the frequency, the 48 02:21.660 --> 02:22.200 threshold. 49 02:22.200 --> 02:24.910 And then the second thing we're going to do is we're going to go ahead and 50 02:24.910 --> 02:25.240 start it. 51 02:25.240 --> 02:28.800 So what that means is that we're going to create the IPSLA here and we're going 52 02:28.800 --> 02:30.000 to go ahead and tell it to start. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:30.000 --> 02:33.760 Now, as far as starting the IPSLA, we can say start now or we can specify a 54 02:33.760 --> 02:34.840 date or a time. 55 02:34.840 --> 02:37.360 We can also control how long it's going to run. 56 02:37.360 --> 02:41.200 Do we want it to run forever or do we want it to run for, for example, 10,000 57 02:41.200 --> 02:43.320 seconds or 1000 seconds or 500 seconds. 58 02:43.480 --> 02:48.040 And that's all specified when we schedule that IPSLA to begin running. 59 02:48.040 --> 02:51.000 So without further ado, let's go to our lab topology and let's begin the 60 02:51.000 --> 02:54.760 configuration of an IPSLA for ICMP jitter. 61 02:54.760 --> 02:58.150 So here in our lab environment, let me go ahead and double click on the lab top 62 02:58.150 --> 02:58.480 ology, 63 02:58.480 --> 03:01.000 making sure we're on the right lab based on the title. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 02:58.480 --> 03:01.000 making sure we're on the right lab based on the title. 64 03:01.000 --> 03:01.720 We're looking good. 65 03:01.720 --> 03:03.640 And there's our topology, great, great, great. 66 03:03.640 --> 03:04.680 So let's go down to our right. 67 03:04.680 --> 03:08.400 Another way we get to our consoles for each of the devices is going to server 68 03:08.400 --> 03:09.040 one nug. 69 03:09.040 --> 03:10.760 So we'll double click on server one nug. 70 03:10.760 --> 03:13.120 And that will give us console access to our routers. 71 03:13.360 --> 03:13.880 All right. 72 03:13.880 --> 03:15.400 So here comes server one. 73 03:15.400 --> 03:16.920 We'll give that a moment to initialize. 74 03:16.920 --> 03:18.280 And there it is. 75 03:18.280 --> 03:19.840 So let's start with our eight. 76 03:19.840 --> 03:22.040 In fact, here at our eight, we'll click on the our eight tab. 77 03:22.040 --> 03:24.760 Let me just verify that we have connectivity up to our one. 78 03:24.760 --> 03:26.640 We'll do a show IP route. 79 03:26.640 --> 03:30.400 And sure enough, we have a route to 1111. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 03:26.640 --> 03:30.400 And sure enough, we have a route to 1111. 80 03:30.400 --> 03:33.600 So let's go to a ping to 1.1.1.1. 81 03:33.600 --> 03:36.660 We'll source it from our loop back zero interface, which is eight. 82 03:36.660 --> 03:37.080 Eight to eight. 83 03:37.080 --> 03:37.440 Today. 84 03:37.440 --> 03:38.400 And we have connectivity. 85 03:38.400 --> 03:39.440 That's also a trace. 86 03:39.440 --> 03:40.800 So we can verify the path as well. 87 03:40.800 --> 03:43.640 So trace up to one dot one dot one dot one. 88 03:43.640 --> 03:44.760 And there's our path. 89 03:44.760 --> 03:47.720 So it goes from our eight to six, four, two and one. 90 03:47.720 --> 03:53.160 And that path is right here from eight to six to four to two and then to one. 91 03:53.160 --> 03:53.760 All right. 92 03:53.760 --> 03:56.960 So here on our eight, we'll go into configuration mode and we want this to be a 93 03:56.960 --> 03:57.640 responder. 94 03:57.640 --> 04:02.750 So we'll type in IP, SLA space, question mark, and we want this option right WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 94 03:57.640 --> 04:02.750 So we'll type in IP, SLA space, question mark, and we want this option right 95 04:02.750 --> 04:02.920 there. 96 04:02.920 --> 04:04.360 So we'll type that in press center. 97 04:04.360 --> 04:08.880 So now our eight is ready, willing and able to respond to the request from the 98 04:08.880 --> 04:09.320 probe. 99 04:09.480 --> 04:12.720 And for the probe, we want to go ahead and use our one. 100 04:12.720 --> 04:15.480 So we'll head over to our one by clicking on the tab for our one. 101 04:15.480 --> 04:17.160 We've already verified connectivity. 102 04:17.160 --> 04:21.240 So go into configuration mode, I'll type in IP, SLA space. 103 04:21.240 --> 04:26.520 And let's go ahead and use start with number one for IPS, LA number one. 104 04:26.520 --> 04:27.840 We have a wide range of numbers there. 105 04:27.840 --> 04:30.000 So we'll put in one space and then we'll press enter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 106 04:30.000 --> 04:32.640 So now we have this IP, SLA one. 107 04:32.640 --> 04:35.200 It's just now asking us, Hey, what do you want to measure? 108 04:35.320 --> 04:40.400 DHP DNS FTP, HTTP, ICMP, echo and ICP jitter. 109 04:40.400 --> 04:41.680 That's the one we want right there. 110 04:41.680 --> 04:43.600 We want to measure ICMP jitter. 111 04:43.600 --> 04:47.720 So we'll go ahead and copy paste that in as part of this IP SLA number one. 112 04:47.720 --> 04:51.830 We'll do a space question mark and then we'll specify the target is going to be 113 04:51.830 --> 04:52.000 our 114 04:52.000 --> 04:54.840 eight at eight, eight, eight, eight, eight, eight, sorry Google for using your 115 04:54.840 --> 04:56.160 DNS IP address. 116 04:56.160 --> 04:57.400 But this is just an elaborate environment. 117 04:57.400 --> 05:00.640 And then we'll do a space question mark and the source IP address we want to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 04:57.400 --> 05:00.640 And then we'll do a space question mark and the source IP address we want to 118 05:00.640 --> 05:00.840 use 119 05:00.840 --> 05:04.280 is our one that's one dot one dot one, one space and question mark. 120 05:04.440 --> 05:07.680 And the number of packets we want to use based on our goal here, we had three. 121 05:07.680 --> 05:11.240 So let's go ahead and put three based on our game plan space question mark. 122 05:11.240 --> 05:15.120 And then we can specify an interval here or we can go ahead and simply now that 123 05:15.120 --> 05:15.280 we're 124 05:15.280 --> 05:20.160 in the ICMP jitter SLA configuration mode here, we can specify the frequency. 125 05:20.160 --> 05:26.560 Let's go ahead and put the frequency of 30, meaning every 30 seconds is going 126 05:26.560 --> 05:26.720 to go 127 05:26.720 --> 05:28.640 ahead and send those three packets. 128 05:28.640 --> 05:31.640 And it's also here, specify the threshold. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 128 05:28.640 --> 05:31.640 And it's also here, specify the threshold. 129 05:31.800 --> 05:35.600 So put in threshold and it's going to be in milliseconds, so say 100 130 05:35.600 --> 05:36.000 milliseconds 131 05:36.000 --> 05:38.800 based on our plan and boom, we are now set. 132 05:38.800 --> 05:44.800 Now if we type in exit and we do a do show IP SLA summary just like that. 133 05:44.800 --> 05:46.640 Here we have the idea is one. 134 05:46.640 --> 05:48.280 That's the SLA that we can figure out. 135 05:48.280 --> 05:50.040 SLA number one for the type. 136 05:50.040 --> 05:52.000 It's ICMP dash jitter. 137 05:52.000 --> 05:54.480 The destination is eight dot eight dot eight dot eight. 138 05:54.480 --> 05:57.080 The current status is unknown. 139 05:57.080 --> 05:59.160 It has no information regarding milliseconds. 140 05:59.360 --> 06:02.880 And it says right here, last run, which is kind of crazy because it's not WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 140 05:59.360 --> 06:02.880 And it says right here, last run, which is kind of crazy because it's not 141 06:02.880 --> 06:03.560 running at all. 142 06:03.560 --> 06:07.760 Um, we need to actually tell it to start if we wanted to go ahead and run. 143 06:07.760 --> 06:11.040 Oh, you can tell it's not running by this little carrot symbol right here. 144 06:11.040 --> 06:12.320 So here are the codes. 145 06:12.320 --> 06:16.560 Asterisk means it's active, the little carrot symbol means it's inactive and 146 06:16.560 --> 06:16.600 the 147 06:16.600 --> 06:20.080 little tilde symbol means it's pending, meaning it's going to run, but not yet. 148 06:20.080 --> 06:23.640 So we need to actually tell this IP SLA number one to start. 149 06:23.640 --> 06:28.780 So to do that, we're going to type in the command IP SLA schedule space 150 06:28.780 --> 06:29.240 question mark. 151 06:29.480 --> 06:33.440 Then we'll specify our SLA ID, which is one space and question mark. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 151 06:29.480 --> 06:33.440 Then we'll specify our SLA ID, which is one space and question mark. 152 06:33.440 --> 06:35.920 And then we can specify when we want to start. 153 06:35.920 --> 06:37.520 So I'm going to put in the keyword start time. 154 06:37.520 --> 06:41.420 And I'm going to say, instead of like after a certain amount of time or a 155 06:41.420 --> 06:42.000 certain 156 06:42.000 --> 06:44.870 time of day, I'm going to say now, and then furthermore, we can specify how 157 06:44.870 --> 06:45.160 long 158 06:45.160 --> 06:45.680 it's going to run. 159 06:45.680 --> 06:49.360 So we could say, for example, life space question mark, and then we can say 160 06:49.360 --> 06:49.800 forever 161 06:49.800 --> 06:51.320 or we could say a certain number of seconds. 162 06:51.320 --> 06:54.980 And if we don't specify, you know, how long it should live or how long it 163 06:54.980 --> 06:55.760 should run, 164 06:55.920 --> 06:59.600 we can go ahead and press enter and the default time is 3600 seconds to run for 165 06:59.600 --> 06:59.640 . 166 06:59.640 --> 07:00.480 So now it's running. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 166 06:59.640 --> 07:00.480 So now it's running. 167 07:00.480 --> 07:04.360 So now we do a show IP SLA summary and press enter. 168 07:04.360 --> 07:05.720 Now we have an asterisk there. 169 07:05.720 --> 07:07.920 It shows the round trip time 173. 170 07:07.920 --> 07:10.040 And look at this, it says over threshold. 171 07:10.040 --> 07:16.400 So if we did a show IP SLA statistics and the idea of one and then said detail 172 07:16.400 --> 07:19.200 and press enter, it'll give us more information on that. 173 07:19.200 --> 07:21.920 So it had two successes and one failure. 174 07:22.120 --> 07:27.600 And it has, as of this moment of the show command, it has 3534 seconds to go. 175 07:27.600 --> 07:31.800 Also, if we do that same show command of show IP SLA summary again, now it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 175 07:27.600 --> 07:31.800 Also, if we do that same show command of show IP SLA summary again, now it 176 07:31.800 --> 07:32.000 shows 177 07:32.000 --> 07:32.920 this test is okay. 178 07:32.920 --> 07:36.560 And every 30 seconds in the background, it's sending new probes out. 179 07:36.560 --> 07:39.600 So we do a show IP SLA statistics, one details. 180 07:39.600 --> 07:42.480 It looks like we need a few more samples for this to populate. 181 07:42.480 --> 07:48.120 So while this is populating and gaining information about the IC&P jitter 182 07:48.120 --> 07:48.600 information 183 07:48.600 --> 07:51.440 between R1 and R8, let me take you behind the scenes. 184 07:51.440 --> 07:56.530 I'm going to do a little packet capture of the link right here between R1 and R 185 07:56.530 --> 07:56.840 2. 186 07:56.840 --> 07:59.840 That's the path we're taking from R1 as we go down to R8. 187 07:59.840 --> 08:03.150 I just want to show you the back and forth traffic that's happening with those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 187 07:59.840 --> 08:03.150 I just want to show you the back and forth traffic that's happening with those 188 08:03.150 --> 08:03.440 probes 189 08:03.440 --> 08:05.720 from the Pro Bar 1 going down to R8. 190 08:05.720 --> 08:07.880 So I'm going to let this capture run for a second or two. 191 08:07.880 --> 08:08.600 And there we go. 192 08:08.600 --> 08:13.520 We have traffic from 1.1.1.1 going to 8, 8, 8, 8 right there. 193 08:13.520 --> 08:17.240 So I'll go ahead and stop the capture and let's take a look at one of those. 194 08:17.240 --> 08:18.320 Let's scroll up a little bit. 195 08:18.600 --> 08:22.240 In fact, let me go ahead and just do a filter based on ICMP, a display filter 196 08:22.240 --> 08:23.400 here in Wireshark. 197 08:23.400 --> 08:24.520 And great. 198 08:24.520 --> 08:25.440 There we have a few of them. 199 08:25.440 --> 08:26.960 So let's take this one right here. 200 08:26.960 --> 08:30.260 This is a request double click on it to bring it up, make that a little bit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 200 08:26.960 --> 08:30.260 This is a request double click on it to bring it up, make that a little bit 201 08:30.260 --> 08:30.800 bigger here. 202 08:30.800 --> 08:35.920 So R1 is acting as the probing device and R8 is acting as the IP SLA responder. 203 08:35.920 --> 08:39.280 And if you take a look at the contents here in the ICMP payload, let's go ahead 204 08:39.280 --> 08:40.960 and drop this down a little bit. 205 08:40.960 --> 08:44.810 You'll notice on the outgoing packet, it has an originate timestamp that was 206 08:44.810 --> 08:46.000 put there by R1. 207 08:46.360 --> 08:51.160 And then the next two will be filled in in the responses coming back from R8, 208 08:51.160 --> 08:54.850 including when it received the request and then when it sent that response back 209 08:54.850 --> 08:55.040 . 210 08:55.040 --> 08:59.400 So if we close this and we go to one of the responses here from 8, 8, 8, 8, 8, 211 08:59.400 --> 09:00.360 coming back to 1.1.1.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 211 08:59.400 --> 09:00.360 coming back to 1.1.1.1. 212 09:00.360 --> 09:02.820 We'll go ahead and double click on that to open it up and make that a little 213 09:02.820 --> 09:03.400 bit bigger. 214 09:03.400 --> 09:06.360 And I'll scooch down the byte pane here so we can see. 215 09:06.360 --> 09:09.600 So here's the original timestamp set by R1. 216 09:09.600 --> 09:12.920 And then we have the timestamp that was received and then the timestamp when it 217 09:12.920 --> 09:14.080 sent the response back. 218 09:14.240 --> 09:18.320 And so R1 can take that information and probe after probe after probe. 219 09:18.320 --> 09:22.600 It can identify what the variance is in the delay or the jitter. 220 09:22.600 --> 09:27.320 So now if we go back to R1, let's do a show IP SLA summary and it is still 221 09:27.320 --> 09:28.640 running fantastic. 222 09:28.640 --> 09:31.640 The RTT here is now showing S60. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 222 09:28.640 --> 09:31.640 The RTT here is now showing S60. 223 09:31.640 --> 09:32.240 That's great. 224 09:32.240 --> 09:37.800 And as to show IP SLA statistics, then the ID for SLA, which is one. 225 09:37.800 --> 09:40.570 And then the keyword details press center and now we have some additional 226 09:40.570 --> 09:41.080 information. 227 09:41.080 --> 09:45.300 So here's our round trip time being shown now, min, average and max, all of it 228 09:45.300 --> 09:46.200 under 100. 229 09:46.200 --> 09:49.240 That's why it says over threshold counts occurred. 230 09:49.240 --> 09:51.640 False because things are within the threshold right now. 231 09:51.640 --> 09:55.740 And if we scroll down a little bit further, we have our jitter time information 232 09:55.740 --> 09:56.520 right here below. 233 09:56.520 --> 10:01.300 And if we continue to go down, it's showing here that this SLA based on the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 233 09:56.520 --> 10:01.300 And if we continue to go down, it's showing here that this SLA based on the 234 10:01.300 --> 10:06.790 default is going to run for 2,545 seconds or until we tell it to stop or until 235 10:06.790 --> 10:08.160 we remove the SLA. 236 10:08.640 --> 10:13.370 So now that we have the opportunity to sit up an IP SLA for ICMP jitter, let me 237 10:13.370 --> 10:17.130 go ahead and walk you through a very similar function, but this time, measuring 238 10:17.130 --> 10:18.560 jitter based on UDP. 239 10:18.560 --> 10:22.160 So we'll do that the next video and I'll see you there in just a moment.