WEBVTT 1 00:00.000 --> 00:07.940 So for this challenge, we're tasked with moving our redundant tunnel or tunnel 2 00:07.940 --> 00:08.980 2 from 3 00:08.980 --> 00:12.900 on-prem R1 over to on-prem R2. 4 00:12.900 --> 00:16.980 But there is also a second part to the challenge, which is to have all of the 5 00:16.980 --> 00:18.440 necessary Ike version 6 00:18.440 --> 00:25.520 2 and IP [garbled] settings on both sides just in case we need to move both tunnels 7 00:25.520 --> 00:25.980 to either 8 00:25.980 --> 00:27.700 individual router. 9 00:27.700 --> 00:32.000 Now for on-prem R1, of course, it's already configured for both tunnels because WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:27.700 --> 00:32.000 Now for on-prem R1, of course, it's already configured for both tunnels because 10 00:32.000 --> 00:32.600 both tunnels 11 00:32.600 --> 00:33.940 are already here. 12 00:33.940 --> 00:39.550 So that really means that we want to configure on-prem R2 for both potential 13 00:39.550 --> 00:40.500 tunnels. 14 00:40.500 --> 00:45.360 Now the first thing we want to do is here on on-prem R1, we're going to have to 15 00:45.360 --> 00:46.160 remove 16 00:46.160 --> 00:48.380 some of our configuration here. 17 00:48.380 --> 00:53.700 First, we need to remove the route pointing down tunnel 2 because the next 18 00:53.700 --> 00:54.320 thing we're 19 00:54.320 --> 00:58.460 going to do is, well, actually remove tunnel 2. 20 00:58.460 --> 01:03.300 So now that we've removed the route and the tunnel from on-prem R1, if we do a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 00:58.460 --> 01:03.300 So now that we've removed the route and the tunnel from on-prem R1, if we do a 21 01:03.300 --> 01:03.740 show 22 01:03.740 --> 01:08.710 IP interface brief, we'll see that our tunnel 1, of course, is still up, but 23 01:08.710 --> 01:10.100 tunnel 2 is 24 01:10.100 --> 01:11.420 now gone. 25 01:11.420 --> 01:14.380 So that you take care of everything we need to do on router 1. 26 01:14.380 --> 01:18.120 So now let's jump over to on-prem R2. 27 01:18.120 --> 01:22.060 This of course is going to be very, very similar to the way we configured on- 28 01:22.060 --> 01:23.960 prem R1 through 29 01:23.960 --> 01:25.460 this skill. 30 01:25.460 --> 01:29.200 So the first thing we need to do is put our keys on here. 31 01:29.200 --> 01:33.520 So we'll put on our key ring containing both of our keys. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 31 01:29.200 --> 01:33.520 So we'll put on our key ring containing both of our keys. 32 01:33.520 --> 01:37.040 Next we'll put in our three components for IPv2. 33 01:37.040 --> 01:41.510 So first we put in our proposal, then our policy, and then of course our 34 01:41.510 --> 01:42.480 profile tying 35 01:42.480 --> 01:44.520 all of this together. 36 01:44.520 --> 01:49.040 And notice, like with our key ring, we're putting in the match identity for 37 01:49.040 --> 01:49.860 both remote 38 01:49.860 --> 01:50.860 peers. 39 01:50.860 --> 01:56.080 Again, that's in case we ever need to move tunnel 1 over to this router. 40 01:56.080 --> 02:01.380 This router is already ready to go with the necessary information. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 01:56.080 --> 02:01.380 This router is already ready to go with the necessary information. 41 02:01.380 --> 02:07.030 Next up we'll put in our IP second information, so our transform set and our IP 42 02:07.030 --> 02:08.060 sec profile, 43 02:08.060 --> 02:12.620 and then finally we're ready to configure interface tunnel 2. 44 02:12.620 --> 02:17.930 So now that we've moved our tunnel 2 configuration over here to on-prem 1, let 45 02:17.930 --> 02:19.420 's do a show IP interface 46 02:19.420 --> 02:20.420 brief. 47 02:20.420 --> 02:26.430 We see that tunnel 2 is now up, so our final step would be to put in our 48 02:26.430 --> 02:28.060 necessary route, 49 02:28.060 --> 02:34.540 pointing our traffic for the 10.30.0.0 network down tunnel 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 02:28.060 --> 02:34.540 pointing our traffic for the 10.30.0.0 network down tunnel 2. 50 02:34.540 --> 02:41.260 As one final verification, let's go ahead and do a trace to the 10.30.10.100 51 02:41.260 --> 02:42.340 network, sourcing 52 02:42.340 --> 02:47.740 it from our inside interface, and we see that it's successful going directly to 53 02:47.740 --> 02:50.340 the 10.30.10.100. 54 02:50.340 --> 02:54.300 The main thing we're looking for here, of course, is to make sure that it's not 55 02:54.300 --> 02:55.060 going through 56 02:55.060 --> 03:01.520 on-prem R1, but rather it's going directly across its own tunnel, which as we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:55.060 --> 03:01.520 on-prem R1, but rather it's going directly across its own tunnel, which as we 57 03:01.520 --> 03:03.340 can see, it is. 58 03:03.340 --> 03:09.950 So that means we've successfully moved our tunnel from on-prem R1 to on-prem R2 59 03:09.950 --> 03:10.060 , which 60 03:10.060 --> 03:15.620 means that we have completed this challenge as well as this skill. 61 03:15.620 --> 03:19.640 If you find you were missing any of the information needed to complete this 62 03:19.640 --> 03:20.820 challenge, I would 63 03:20.820 --> 03:26.100 encourage you to go back and review the necessary steps in the skill above. 64 03:26.100 --> 03:32.900 Otherwise, congratulations on completing Configure Native IPSec VPN to Azure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 03:26.100 --> 03:32.900 Otherwise, congratulations on completing Configure Native IPSec VPN to Azure. 65 03:32.900 --> 03:36.620 I hope this has been informative for you, and I'd like to thank you for viewing 66 03:36.620 --> 03:36.940 . 67 03:36.940 --> 03:46.940 [BLANK_AUDIO]