WEBVTT 1 00:00.000 --> 00:07.690 So now that we've gotten a good idea how to do some troubleshooting on AWS and 2 00:07.690 --> 00:13.110 use the tools that it has available, well Microsoft Azure has very similar 3 00:13.110 --> 00:14.000 tools. 4 00:14.000 --> 00:16.900 Now of course they're going to look a little bit different they get configured 5 00:16.900 --> 00:20.000 a little bit different and of course they're going to be in different places. 6 00:20.000 --> 00:26.420 Overall, it's the same basic idea. So let's go ahead and jump into the Azure 7 00:26.420 --> 00:32.650 interface and find out where these tools are that we can use to troubleshoot WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:26.420 --> 00:32.650 interface and find out where these tools are that we can use to troubleshoot 8 00:32.650 --> 00:34.000 our IP sack VPN. 9 00:34.000 --> 00:39.180 So starting off here on the homepage, the first place to go would be either up 10 00:39.180 --> 00:44.440 on your Azure services if you've used it recently, or if you haven't, you can 11 00:44.440 --> 00:49.000 simply come over here to the side and go to virtual network gateways. 12 00:49.000 --> 00:54.350 Here we have our virtual gateway VNG one. So to start troubleshooting this the 13 00:54.350 --> 00:57.000 first thing we want to do is click on it. 14 00:57.000 --> 01:02.060 So we're going to go to the top our overview page for this virtual network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:57.000 --> 01:02.060 So we're going to go to the top our overview page for this virtual network 15 01:02.060 --> 01:06.700 gateway. Now up at the top we see a lot of information such as the resource 16 01:06.700 --> 01:09.000 group locations, skew and so on. 17 01:09.000 --> 01:13.100 And then down here at the bottom, we have information about the traffic going 18 01:13.100 --> 01:18.080 through this tunnel. And of course we can change the hourly rate for this from 19 01:18.080 --> 01:21.000 one hour up to, well, 30 days. 20 01:21.000 --> 01:25.510 I actually don't have any traffic going through this tunnel right now. So both 21 01:25.510 --> 01:27.000 tables are at the bottom. 22 01:27.000 --> 01:31.340 But you can see here that we could verify the traffic is passing through the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 01:27.000 --> 01:31.340 But you can see here that we could verify the traffic is passing through the 23 01:31.340 --> 01:32.000 tunnel. 24 01:32.000 --> 01:36.820 Another good place to go if we're having issues is we can come over here to the 25 01:36.820 --> 01:39.000 diagnose and solve problems. 26 01:39.000 --> 01:44.250 Now this of course is basically going to be a troubleshooting wizard. We're 27 01:44.250 --> 01:47.000 going to go through here and look at common problems and so on. 28 01:47.000 --> 01:50.270 Now of course we can't really do this since we're not having any problems at 29 01:50.270 --> 01:54.270 the moment. However, this would walk you through finding a lot of the common 30 01:54.270 --> 01:55.000 problems. 31 01:55.000 --> 01:59.570 Something else that can be very useful to do and it's a little bit hidden where 32 01:59.570 --> 02:02.000 to do it if you've not seen it before. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:59.570 --> 02:02.000 to do it if you've not seen it before. 33 02:02.000 --> 02:07.960 But we can actually do what's essentially a hard reset on the virtual network 34 02:07.960 --> 02:13.000 gateway. Oddly enough though, where it is is down here under help. 35 02:13.000 --> 02:17.700 There's a reset down here and if we click on this, it'll tell us exactly what 36 02:17.700 --> 02:19.000 it's going to do. 37 02:19.000 --> 02:24.210 It's going to reboot the Azure virtual network gateway. Now this is of course 38 02:24.210 --> 02:27.000 going to be disruptive to your VPN service. 39 02:27.000 --> 02:32.090 But again, we're probably not going to be doing this if our VPNs are already WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 02:27.000 --> 02:32.090 But again, we're probably not going to be doing this if our VPNs are already 40 02:32.090 --> 02:33.000 working. 41 02:33.000 --> 02:36.150 This is where we would be in troubleshooting. Now there's some other good 42 02:36.150 --> 02:38.000 things here to help us under help as well. 43 02:38.000 --> 02:43.630 We can go to resource health. Here we can get a history of when our VNG 44 02:43.630 --> 02:46.000 services have been available. 45 02:46.000 --> 02:50.980 There's also a VPN troubleshooter here. Again, you can select a VPN and start 46 02:50.980 --> 02:56.000 troubleshooting and it'll walk you through steps to perform troubleshooting. 47 02:56.000 --> 03:01.000 There's also a packet capture here, which of course can also be very handy. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 47 02:56.000 --> 03:01.000 There's also a packet capture here, which of course can also be very handy. 48 03:01.000 --> 03:05.780 And of course, there's also just some general information on how to access 49 03:05.780 --> 03:09.000 support and troubleshooting documentation. 50 03:09.000 --> 03:13.000 Now all of this is about the virtual network gateway itself. 51 03:13.000 --> 03:18.170 And to be perfectly honest, once the VNG is set up and connected into your 52 03:18.170 --> 03:22.000 network, this probably isn't going to fail all that often. 53 03:22.000 --> 03:26.540 And if it does, the most common thing is we would probably just have to reset 54 03:26.540 --> 03:31.000 it. However, the VPNs themselves may have issues. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 03:26.540 --> 03:31.000 it. However, the VPNs themselves may have issues. 55 03:31.000 --> 03:34.000 So for that, we want to come up here to connections. 56 03:34.000 --> 03:38.720 And then we'll click on VPN one. Now, we see that right off the bat, the status 57 03:38.720 --> 03:43.000 says connected. We also see that it's a site to site VPN. 58 03:43.000 --> 03:45.000 But let's go ahead and click on it. 59 03:45.000 --> 03:49.460 And we'll get a little bit of information here on the overview page. We see 60 03:49.460 --> 03:53.000 that it is in fact connected. We see its location and so on. 61 03:53.000 --> 03:58.430 But other important things to look at here. First, we can go to the activity 62 03:58.430 --> 03:59.000 log. 63 03:59.000 --> 04:04.380 Here, for example, we can see where this tunnel first came up. Now it's listing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 03:59.000 --> 04:04.380 Here, for example, we can see where this tunnel first came up. Now it's listing 64 04:04.380 --> 04:09.360 it as a health event resolved, because of course I had it up and then I reset 65 04:09.360 --> 04:11.000 the router so it went down. 66 04:11.000 --> 04:15.370 And then it came back up when I put the configuration back in the router. So it 67 04:15.370 --> 04:19.660 's listing it as a health event resolved about three hours ago, but it was 68 04:19.660 --> 04:24.000 simply me setting up this demonstration on the equipment. 69 04:24.000 --> 04:28.130 Let's go ahead and open up settings. Now we can go to authentication here. If 70 04:28.130 --> 04:32.150 you suspect that maybe the pre shared key got corrupted or was put in wrong or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 04:28.130 --> 04:32.150 you suspect that maybe the pre shared key got corrupted or was put in wrong or 71 04:32.150 --> 04:33.000 something. 72 04:33.000 --> 04:38.190 And we could change our authentication here. Probably not something you have to 73 04:38.190 --> 04:42.680 do if the VPN was already up or something. Maybe there's some other issue going 74 04:42.680 --> 04:43.000 on. 75 04:43.000 --> 04:47.400 But if it's never come up, it's possible to pre share key is wrong. And of 76 04:47.400 --> 04:51.000 course you could change it or actually view it here. 77 04:51.000 --> 04:53.170 Under configuration is where we would fix things like our like phase one, our 78 04:53.170 --> 05:02.130 like phase two, encryption, integrity, and to be home and groups, and so on. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 04:53.170 --> 05:02.130 like phase two, encryption, integrity, and to be home and groups, and so on. So 79 05:02.130 --> 05:07.000 if any of these were incorrect or didn't match with our iOS Xe side. 80 05:07.000 --> 05:10.000 This is where we would come to correct that. 81 05:10.000 --> 05:15.930 And once again, sometimes in networking, we just have to reset things. And once 82 05:15.930 --> 05:19.000 again, to do that down here under help. 83 05:19.000 --> 05:25.340 We have a reset for the VPN connection as well. Now in this case, it's just 84 05:25.340 --> 05:29.000 going to reset the tunnels for this VPN. 85 05:29.000 --> 05:33.730 It's not going to reset the entire virtual network gateway. So if there's more WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 85 05:29.000 --> 05:33.730 It's not going to reset the entire virtual network gateway. So if there's more 86 05:33.730 --> 05:38.480 than just the one connection, it won't affect the other connections. And there 87 05:38.480 --> 05:44.000 's of course, some of the other troubleshooting tools available here under help 88 05:44.000 --> 05:45.000 as well. 89 05:45.000 --> 05:50.020 And one last thing to look at. We actually have some command line tools that we 90 05:50.020 --> 05:55.700 can use to collect information about the VPN. So let's go up here to our cloud 91 05:55.700 --> 05:56.000 console. 92 05:56.000 --> 06:01.840 And make this a little bigger if we like. Once we get connected, we're in what WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 05:56.000 --> 06:01.840 And make this a little bigger if we like. Once we get connected, we're in what 93 06:01.840 --> 06:04.000 's called the bash shell. 94 06:04.000 --> 06:10.130 Specifically the command that we want to look at is A Z, of course, that's to 95 06:10.130 --> 06:15.400 address Azure VPN connection show. And then we have to put in a few flags here 96 06:15.400 --> 06:20.000 to specify the resource group which in my case is SD dash way in. 97 06:20.000 --> 06:25.980 The name of the VPN connection in my case, that's VPN one. So let's go ahead 98 06:25.980 --> 06:27.000 and hit enter. 99 06:27.000 --> 06:33.000 This is then going to give us a dump of all of the information about this VPN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 99 06:27.000 --> 06:33.000 This is then going to give us a dump of all of the information about this VPN. 100 06:33.000 --> 06:37.610 This can be used to import into other management software or other troubles 101 06:37.610 --> 06:41.000 hooting tools to add the information about our VPN. 102 06:41.000 --> 06:46.520 Now, we also have another tool that's only available in PowerShell. So what we 103 06:46.520 --> 06:50.000 can do is we can just go over here and say switch to PowerShell. 104 06:50.000 --> 06:54.830 Then we can put our command, which is get A Z virtual network gateway 105 06:54.830 --> 06:56.000 connection. 106 06:56.000 --> 07:01.670 And once again, it's minus resource group name and we put in our name in this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 106 06:56.000 --> 07:01.670 And once again, it's minus resource group name and we put in our name in this 107 07:01.670 --> 07:08.000 case again SD win minus name, which is the VPN VPN one. We hit enter. 108 07:08.000 --> 07:11.780 We see here that the command is actually trying to go off the right side of the 109 07:11.780 --> 07:16.520 screen a little bit. It is a rather wide command. But nonetheless, we can see 110 07:16.520 --> 07:22.000 that it's telling us our resource group name, the name of the VPN, its location 111 07:22.000 --> 07:27.000 , what type it is routing weight, the DVD timeout, and so on. 112 07:27.000 --> 07:32.760 So it's giving us some basic information about the VPN and its current status WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 112 07:27.000 --> 07:32.760 So it's giving us some basic information about the VPN and its current status 113 07:32.760 --> 07:37.000 because notice here it's telling us that it's connected. 114 07:37.000 --> 07:42.480 So in this video, we look at some of the tools we have available in Microsoft 115 07:42.480 --> 07:47.880 Azure to get that same information that we got in AWS on the Microsoft Azure 116 07:47.880 --> 07:49.000 platform. 117 07:49.000 --> 07:53.080 And we're going to be looking for the same things to troubleshoot IP addresses 118 07:53.080 --> 07:54.000 being wrong. 119 07:54.000 --> 08:00.020 IP encryption. So our phase one and phase two for Ike being incorrect using the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 119 07:54.000 --> 08:00.020 IP encryption. So our phase one and phase two for Ike being incorrect using the 120 08:00.020 --> 08:04.000 wrong encryption, the wrong integrity checks and so on. 121 08:04.000 --> 08:10.000 Next up, let's take a look at this same basic information on Google Cloud. 122 08:10.000 --> 08:13.640 out.