WEBVTT 1 00:00.000 --> 00:06.940 So one final step we want to do here before we jump into our challenge is to 2 00:06.940 --> 00:07.280 actually 3 00:07.280 --> 00:12.750 connect into SRV1, make sure that it can actually reach the internet and that 4 00:12.750 --> 00:13.560 the traffic 5 00:13.560 --> 00:15.680 is flowing the way that we want it to. 6 00:15.680 --> 00:21.170 So let's go ahead and get into our jump box, use that to connect to SRV1 and 7 00:21.170 --> 00:21.680 then do some 8 00:21.680 --> 00:26.240 testing from SRV1. 9 00:26.240 --> 00:32.140 Now one quick thing to note as we jump in, if I do an LS here, I want you to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:26.240 --> 00:32.140 Now one quick thing to note as we jump in, if I do an LS here, I want you to 10 00:32.140 --> 00:32.760 note that 11 00:32.760 --> 00:36.280 I have already created Azure Key.Pem. 12 00:36.280 --> 00:40.640 I simply copied my key up here to the Linux box. 13 00:40.640 --> 00:44.240 If you're not familiar with how to do that, I have included that information in 14 00:44.240 --> 00:44.760 the code 15 00:44.760 --> 00:47.360 window below this video. 16 00:47.360 --> 00:54.240 So what we want to do from here now is use this key to SSH over to SRV1. 17 00:54.240 --> 00:59.000 So to do this, we want to do an SSH, we do a minus I to tell it to use our key 18 00:59.000 --> 00:59.520 so we put 19 00:59.520 --> 01:01.360 in the key name there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 00:59.520 --> 01:01.360 in the key name there. 20 01:01.360 --> 01:05.340 Then we put in Azure user just because that's the default, we could of course 21 01:05.340 --> 01:05.840 create 22 01:05.840 --> 01:07.160 more users. 23 01:07.160 --> 01:11.660 But then we say at and it's internal IP address, which we already verified 24 01:11.660 --> 01:13.520 reachability to 25 01:13.520 --> 01:15.320 in the previous video. 26 01:15.320 --> 01:17.800 So now we should be able to go ahead and hit enter. 27 01:17.800 --> 01:22.360 It's going to ask us if we want to accept its fingerprint, we'll say yes. 28 01:22.360 --> 01:24.800 And now we're connected to SRV1. 29 01:24.800 --> 01:28.870 We can also see up here at the very top where it has the correct IP address, 30 01:28.870 --> 01:29.720 which of course 31 01:29.720 --> 01:34.290 we already know that it did because that's what we just SSH into, but just as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 31 01:29.720 --> 01:34.290 we already know that it did because that's what we just SSH into, but just as 32 01:34.290 --> 01:35.280 verification, 33 01:35.280 --> 01:39.360 we can see that it does in fact have the 10.30 to 10.100. 34 01:39.360 --> 01:44.280 Now what we really want to do from here is make sure we can get out to the 35 01:44.280 --> 01:44.320 internet. 36 01:44.320 --> 01:46.840 So we'll ping 8888. 37 01:46.840 --> 01:49.400 We see that is in fact working. 38 01:49.400 --> 01:55.320 We can verify name resolution by pinging Cisco, which is also working. 39 01:55.320 --> 01:59.720 What we really want to do though is make sure that this is in fact going 40 01:59.720 --> 02:02.240 through Azure R1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 01:59.720 --> 02:02.240 through Azure R1. 41 02:02.240 --> 02:05.570 And a real quick way to make sure that this is going through route R1 would be 42 02:05.570 --> 02:06.240 to hop over 43 02:06.240 --> 02:08.800 and look at the nat translation tables. 44 02:08.800 --> 02:12.040 So let's jump over to Azure R1. 45 02:12.040 --> 02:17.110 And if we do our show IP nat translation here on Azure R1, we can see that it 46 02:17.110 --> 02:18.280 is in fact 47 02:18.280 --> 02:26.550 translating from the inside local address 10.30.10.100 to its outside address, 48 02:26.550 --> 02:30.120 the 10.30.1.254. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:26.550 --> 02:30.120 the 10.30.1.254. 49 02:30.120 --> 02:36.400 And we can see here that it's translating going both to the 8888. 50 02:36.400 --> 02:40.560 And to the DNS resolved address for Cisco.com. 51 02:40.560 --> 02:46.960 So this means that SRV1 is sending its traffic through Azure R1 here as we 52 02:46.960 --> 02:47.680 intend it. 53 02:48.680 --> 02:51.920 So in this video, we didn't configure anything. 54 02:51.920 --> 02:57.640 We just jumped into SRV1 and verified that it is in fact functioning the way we 55 02:57.640 --> 02:58.720 intend it. 56 02:58.720 --> 03:02.980 So that concludes everything we need to cover in this skill, except for the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:58.720 --> 03:02.980 So that concludes everything we need to cover in this skill, except for the 57 03:02.980 --> 03:03.920 challenge. 58 03:03.920 --> 03:09.160 In the challenge, we're going to be deploying a redundant router into Microsoft 59 03:09.160 --> 03:09.760 Azure. 60 03:09.760 --> 03:13.600 So let's go ahead and jump in and get started on that challenge. 61 03:13.600 --> 03:17.760 Good luck and I'll see you in the solution video on the other side.