WEBVTT

1
00:00.000 --> 00:06.960
So now that we have some experience troubleshooting VPN cloud gateways,

2
00:06.960 --> 00:10.820
well, we're going to find out that Google Cloud isn't really all that different

3
00:10.820 --> 00:10.960
.

4
00:10.960 --> 00:16.480
So all we really have to do is look at where the tools are in Google Cloud.

5
00:16.480 --> 00:22.120
We'll be looking for almost the same information with sort of one difference.

6
00:22.120 --> 00:27.560
One problem that we're not going to have on Google Cloud is what type of

7
00:27.560 --> 00:31.910
encryption, integrity, and Diffie-Hellman groups we're going to be using
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:27.560 --> 00:31.910
encryption, integrity, and Diffie-Hellman groups we're going to be using

8
00:31.910 --> 00:32.920
because

9
00:32.920 --> 00:36.120
it'll simply use all of the ones it supports.

10
00:36.120 --> 00:41.880
So all we really have to do is make sure that our iOS Xe side is using

11
00:41.880 --> 00:43.960
settings that are supported by Google Cloud.

12
00:43.960 --> 00:45.400
It's that simple.

13
00:45.400 --> 00:49.160
And as long as we are, then those settings are going to be fine.

14
00:49.160 --> 00:53.000
So beyond that, we just have to take a look at the tunnel itself.

15
00:53.280 --> 00:57.920
So let's go ahead and jump in and check out the tools in Google Cloud.

16
00:57.920 --> 01:05.640
So starting off here on the Google Cloud console starting page, what we want to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:57.920 --> 01:05.640
So starting off here on the Google Cloud console starting page, what we want to

17
01:05.640 --> 01:06.120
do

18
01:06.120 --> 01:12.360
is come over here to our main menu and we want to go to network connectivity

19
01:12.360 --> 01:14.360
and then VPN.

20
01:14.360 --> 01:21.280
And this will bring up the page with our VPN gateways and our VPN tunnels.

21
01:21.800 --> 01:27.200
Now, one thing to note here, I do have two tunnels built up and running.

22
01:27.200 --> 01:32.040
However, they are going to two different VPN gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
01:27.200 --> 01:32.040
However, they are going to two different VPN gateways.

23
01:32.040 --> 01:36.680
So if we want to start by verifying the gateways, we can simply come over here

24
01:36.680 --> 01:38.400
to Cloud VPN gateways.

25
01:38.400 --> 01:40.560
We can see our two gateways are up.

26
01:40.560 --> 01:46.400
There are IP addresses for the outside tunnel, the VPC network and the region

27
01:46.400 --> 01:48.520
they're connected to and so on.

28
01:48.880 --> 01:54.080
I could of course also add a new tunnel here to either one of these gateways.

29
01:54.080 --> 01:58.120
Each one of them, of course, only has one tunnel at the moment to get

30
01:58.120 --> 01:58.800
information

31
01:58.800 --> 02:00.240
on each of the tunnels.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:58.800 --> 02:00.240
on each of the tunnels.

32
02:00.240 --> 02:04.040
We want to come back over here to the Cloud VPN tunnels.

33
02:04.040 --> 02:08.320
And of course, the first thing to note here is that we have our two tunnels.

34
02:08.320 --> 02:13.690
It's telling us the Cloud VPN gateway that it's connected to as well as the

35
02:13.690 --> 02:14.600
peer VPN

36
02:14.800 --> 02:18.910
gateway, which of course would be the outside address for the other side of the

37
02:18.910 --> 02:19.280
tunnel.

38
02:19.280 --> 02:23.160
We see any information about it running BGP.

39
02:23.160 --> 02:25.680
None of my tunnels are running BGP.

40
02:25.680 --> 02:28.000
These are just standard VPNs.

41
02:28.000 --> 02:33.840
Of course, the main thing we would be looking for on this page is the fact that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
02:28.000 --> 02:33.840
Of course, the main thing we would be looking for on this page is the fact that

42
02:33.840 --> 02:37.400
the VPN tunnel status is established.

43
02:37.400 --> 02:42.200
If we click on any one of these tunnels, we can get a lot of the other

44
02:42.200 --> 02:43.040
information

45
02:43.160 --> 02:45.960
that we've seen on the other cloud providers.

46
02:45.960 --> 02:51.000
So this particular page is just sort of some generic information we saw most of

47
02:51.000 --> 02:51.400
this

48
02:51.400 --> 02:55.080
previously, but this is where we can go to monitor.

49
02:55.080 --> 03:01.640
So we go here to monitoring and now we get this table that again is adjustable
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:55.080 --> 03:01.640
So we go here to monitoring and now we get this table that again is adjustable

50
03:01.640 --> 03:04.520
per hour up to 30 days.

51
03:04.520 --> 03:10.160
And then we can see how many received bytes and sent bytes and so on have been

52
03:10.160 --> 03:11.560
going through this tunnel.

53
03:12.320 --> 03:16.100
So these are some good tools to keep an eye on as we're going through and

54
03:16.100 --> 03:16.720
troubleshooting

55
03:16.720 --> 03:17.920
Google Cloud.

56
03:17.920 --> 03:24.000
Now, much like Microsoft Azure, Google Cloud also has some CLI tools that we

57
03:24.000 --> 03:24.840
can use.

58
03:24.840 --> 03:29.000
So we can bring up our CLI by clicking on this box up here.

59
03:29.000 --> 03:33.400
If this is the first time you've launched this, this may take a few minutes to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
03:29.000 --> 03:33.400
If this is the first time you've launched this, this may take a few minutes to

60
03:33.400 --> 03:34.400
deploy.

61
03:34.400 --> 03:38.880
So the main command that we're going to be using for interacting with G Cloud

62
03:38.880 --> 03:39.000
is

63
03:39.000 --> 03:40.600
simply G Cloud.

64
03:40.800 --> 03:46.280
However, if we hit enter, although this is helpful, it's a little bit long in

65
03:46.280 --> 03:46.560
that

66
03:46.560 --> 03:51.440
it's going to give us all of the possible endings and commands that can come

67
03:51.440 --> 03:51.760
after

68
03:51.760 --> 03:52.560
this.

69
03:52.560 --> 03:55.520
And as you can see, this is quite long.

70
03:55.520 --> 03:57.560
So we're not going to go through the whole thing.

71
03:57.560 --> 04:06.080
However, if we exit out of this, there's another useful command, G Cloud cheat.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:57.560 --> 04:06.080
However, if we exit out of this, there's another useful command, G Cloud cheat.

72
04:06.280 --> 04:10.990
This is another help document that explains more how the command itself

73
04:10.990 --> 04:12.400
actually works.

74
04:12.400 --> 04:14.320
This one isn't all that long.

75
04:14.320 --> 04:19.240
It's a couple pages so you could actually easily print this out and keep it

76
04:19.240 --> 04:20.160
handy

77
04:20.160 --> 04:23.560
for tips on how to use the G Cloud command.

78
04:23.560 --> 04:27.960
Now, unfortunately, the main command that I brought you here to show you

79
04:27.960 --> 04:34.640
is not going to work, which is G Cloud compute VPN gateways list.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
04:27.960 --> 04:34.640
is not going to work, which is G Cloud compute VPN gateways list.

80
04:34.840 --> 04:40.040
And if we hit enter on this, it tells us that there's zero items, even though

81
04:40.040 --> 04:40.240
we

82
04:40.240 --> 04:44.840
just saw that there are in fact two VPN gateways.

83
04:44.840 --> 04:48.040
And if we try to get a status on one,

84
04:48.040 --> 04:52.840
the command for that is get status, then you list the VPN gateway you want

85
04:52.840 --> 04:53.440
information

86
04:53.440 --> 04:57.120
on. So in this case, it would be VPN dash one.

87
04:57.120 --> 05:00.120
It's going to tell me that this is not valid.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:57.120 --> 05:00.120
It's going to tell me that this is not valid.

88
05:00.320 --> 05:05.240
I'll verify my region and it's still going to tell me that this does not exist.

89
05:05.240 --> 05:11.000
And the reason for that is I'm using standard VPN gateways.

90
05:11.000 --> 05:12.960
This command is actually for the fault

91
05:12.960 --> 05:18.320
tolerant gateways, which is what Google is actually recommending that we use.

92
05:18.320 --> 05:20.160
But just because we didn't want to set up

93
05:20.160 --> 05:24.000
BGP and get all of that working, that's not what we used.

94
05:24.200 --> 05:30.600
But still keep this CLI command handy because it gives us good information
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
05:24.200 --> 05:30.600
But still keep this CLI command handy because it gives us good information

95
05:30.600 --> 05:34.880
if we're running the fault tolerant gateway.

96
05:34.880 --> 05:39.560
So in this video, we looked at the different tools and features that we have

97
05:39.560 --> 05:46.760
available on Google Cloud to help us troubleshoot our VPN gateways and our VPNs

98
05:46.760 --> 05:46.760
.

99
05:46.760 --> 05:52.200
So that concludes what we need to look at in this skill, except, of course,

100
05:52.400 --> 05:56.040
for taking the challenge. So jump in, give that a shot.

101
05:56.040 --> 06:00.800
Good luck. And I'll see you in the solution video on the other side.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:56.040 --> 06:00.800
Good luck. And I'll see you in the solution video on the other side.

102
06:00.800 --> 06:09.400
[BLANK_AUDIO]