WEBVTT

1
00:00.000 --> 00:07.270
So our next step is going to be to create the two gateways that we need to

2
00:07.270 --> 00:08.400
build our VPN

3
00:08.400 --> 00:09.720
between.

4
00:09.720 --> 00:13.830
One of them is going to be the virtual network gateway, which represents the

5
00:13.830 --> 00:14.640
Azure side of

6
00:14.640 --> 00:19.400
our tunnel and the other one is the local gateway, which although we're calling

7
00:19.400 --> 00:20.200
it local

8
00:20.200 --> 00:26.150
in Azure is actually referring to the headquarters site or the other end of the

9
00:26.150 --> 00:27.640
VPN connection.

10
00:27.640 --> 00:31.260
So let's go ahead and jump in and configure these two components that we need
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.640 --> 00:31.260
So let's go ahead and jump in and configure these two components that we need

11
00:31.260 --> 00:32.000
to build

12
00:32.000 --> 00:35.040
our VPN.

13
00:35.040 --> 00:39.880
So we'll start off here on the Azure homepage again and just something I want

14
00:39.880 --> 00:40.320
to point

15
00:40.320 --> 00:46.060
out up here at the top of the homepage are things that you've used fairly

16
00:46.060 --> 00:47.240
recently.

17
00:47.240 --> 00:52.180
So what's up here on this list isn't necessarily going to match in any way what

18
00:52.180 --> 00:53.840
I have here

19
00:53.840 --> 00:59.000
and you may not have things like virtual network gateways and local network

20
00:59.000 --> 00:59.840
gateways that

21
00:59.840 --> 01:03.880
we're going to be using here in this demonstration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:59.840 --> 01:03.880
we're going to be using here in this demonstration.

22
01:03.880 --> 01:09.460
Also over on the side launch bar where I also have virtual network gateways and

23
01:09.460 --> 01:10.280
local network

24
01:10.280 --> 01:11.720
gateways.

25
01:11.720 --> 01:17.080
Those are there simply because I already have those pinned to that side menu in

26
01:17.080 --> 01:18.640
my account.

27
01:18.640 --> 01:23.760
So if you don't have these or as we go through any of the Azure services, if

28
01:23.760 --> 01:24.340
you're ever

29
01:24.340 --> 01:30.000
missing anything that we talk about, you can always search for the resource up
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:30.000 --> 01:30.600
here in

31
01:30.600 --> 01:33.480
the search bar at the top of the page.

32
01:33.480 --> 01:38.020
Then once you find it and you access it, you can then pin it to the side menu

33
01:38.020 --> 01:38.920
yourself.

34
01:38.920 --> 01:43.340
And of course, after you've visited it a few times, it'll show up up here at

35
01:43.340 --> 01:44.460
the top

36
01:44.460 --> 01:46.620
under your frequently used.

37
01:46.620 --> 01:51.920
All of that said what we need to start with here in this section is creating a

38
01:51.920 --> 01:52.980
virtual network

39
01:52.980 --> 01:54.220
gateway.

40
01:54.220 --> 01:59.260
So that said, we'll just simply come over here and click on virtual network

41
01:59.260 --> 01:59.820
gateways.

42
01:59.820 --> 02:01.700
Once again, we don't have one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:59.820 --> 02:01.700
Once again, we don't have one.

43
02:01.700 --> 02:05.540
So we'll simply come up here to the top and hit create.

44
02:05.540 --> 02:10.020
Notice that the resource group actually says to select a virtual network to get

45
02:10.020 --> 02:10.820
the resource

46
02:10.820 --> 02:16.420
group because this has to be in the same resource group as your virtual network

47
02:16.420 --> 02:16.580
.

48
02:16.580 --> 02:20.940
So if we hop ahead just a little bit and we come down here to the virtual

49
02:20.940 --> 02:21.940
network and we

50
02:21.940 --> 02:27.960
choose our Vnet one, we'll see that that resource group field now updates to

51
02:27.960 --> 02:29.020
show the resource

52
02:29.020 --> 02:35.180
group of SD when so it sort of pulls that back from the virtual network itself.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:29.020 --> 02:35.180
group of SD when so it sort of pulls that back from the virtual network itself.

53
02:35.180 --> 02:38.900
Now for the virtual network gateway, the next thing we want to do here is of

54
02:38.900 --> 02:39.540
course give

55
02:39.540 --> 02:41.220
it a name.

56
02:41.220 --> 02:45.380
I'll simply call it VNG1 for virtual network gateway.

57
02:45.380 --> 02:49.760
Once again, you choose the appropriate region, the gateway type, we're here to

58
02:49.760 --> 02:51.620
build a VPN,

59
02:51.620 --> 02:55.500
although you could also do an express route VPN if you prefer, we're just going

60
02:55.500 --> 02:56.260
to do a regular

61
02:56.260 --> 02:58.060
VPN.

62
02:58.060 --> 03:02.730
For the skew, there's actually a lot of different choices and you can do some
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:58.060 --> 03:02.730
For the skew, there's actually a lot of different choices and you can do some

63
03:02.730 --> 03:04.620
research into Microsoft

64
03:04.620 --> 03:07.580
Azure to figure out what all the different skews are.

65
03:07.580 --> 03:11.140
They have to do with performance and number of supported connections.

66
03:11.140 --> 03:15.400
You can get a little bit of information on these if you click on the eye over

67
03:15.400 --> 03:16.100
here, you can

68
03:16.100 --> 03:19.260
see it gives you some basic information.

69
03:19.260 --> 03:23.150
So again, you would want to choose the appropriate one based on your need for

70
03:23.150 --> 03:24.060
performance and

71
03:24.060 --> 03:27.380
number of terminated VPNs and so on.

72
03:27.380 --> 03:30.420
We're just going to go ahead and leave the default skew here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:27.380 --> 03:30.420
We're just going to go ahead and leave the default skew here.

73
03:30.420 --> 03:34.140
It'll work fine for this demonstration.

74
03:34.140 --> 03:39.670
Next notice here under subnet, it has already chosen our gateway subnet with

75
03:39.670 --> 03:40.780
the 10.30

76
03:40.780 --> 03:43.380
dot 1 dot 0 slash 24.

77
03:43.380 --> 03:45.380
So that's correct.

78
03:45.380 --> 03:46.740
Notice that it's sort of grayed out.

79
03:46.740 --> 03:47.940
We can't even choose this.

80
03:47.940 --> 03:51.790
I mean, we can highlight the field, but if we click on it, we don't get a drop

81
03:51.790 --> 03:52.340
down.

82
03:52.340 --> 03:55.580
It's showing us our only choice.

83
03:55.580 --> 03:59.240
Next if we scroll down a little bit here, we see that we need to create some

84
03:59.240 --> 04:00.140
public IP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:59.240 --> 04:00.140
public IP

85
04:00.140 --> 04:01.220
addresses.

86
04:01.220 --> 04:04.390
So what we're going to do is we're going to choose to create a new public IP

87
04:04.390 --> 04:05.100
address.

88
04:05.100 --> 04:08.860
I'm simply going to call this VNG one.

89
04:08.860 --> 04:10.260
IP one.

90
04:10.260 --> 04:13.420
You can of course name it whatever you prefer.

91
04:13.420 --> 04:16.960
We're going to leave the assignment on static there and then for the

92
04:16.960 --> 04:18.220
availability zone,

93
04:18.220 --> 04:21.780
I'm just going to choose this to be in zone one.

94
04:21.780 --> 04:26.060
Then for the second address, this again would be for the second tunnel.

95
04:26.060 --> 04:31.820
We'll name this VNG one IP two and for the availability zone on this one, we'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:26.060 --> 04:31.820
We'll name this VNG one IP two and for the availability zone on this one, we'll

96
04:31.820 --> 04:32.260
choose

97
04:32.260 --> 04:36.780
availability zone two so that we have some redundancy.

98
04:36.780 --> 04:39.740
Once again, we could hit next to add tags.

99
04:39.740 --> 04:43.540
We don't really need that so we'll just say review and create.

100
04:43.540 --> 04:46.940
We'll verify everything on here is correct, which it is.

101
04:46.940 --> 04:49.340
So let's go ahead and hit create.

102
04:49.340 --> 04:52.100
This will take just a moment to deploy here.

103
04:52.100 --> 04:56.900
Okay, so it's been just a few minutes here and our deployment is now complete.

104
04:56.900 --> 05:00.640
Just for reference when you're doing this on your own, this takes about 10
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:56.900 --> 05:00.640
Just for reference when you're doing this on your own, this takes about 10

105
05:00.640 --> 05:01.260
minutes to

106
05:01.260 --> 05:02.420
deploy.

107
05:02.420 --> 05:05.580
So we skipped ahead here until it was deployed.

108
05:05.580 --> 05:07.900
Then now we can go to the resource.

109
05:07.900 --> 05:09.980
Here of course, we see a nice overview.

110
05:09.980 --> 05:14.810
However, we don't have any information of course about our tunnels because well

111
05:14.810 --> 05:15.340
, none

112
05:15.340 --> 05:17.900
of this is completely configured yet.

113
05:17.900 --> 05:22.980
The next thing of course that we need to do is configure our local network

114
05:22.980 --> 05:23.300
gateway.

115
05:23.300 --> 05:26.860
So for that, let's come over here to local network gateway.

116
05:26.860 --> 05:29.020
Once again, we'll hit create.

117
05:29.020 --> 05:31.260
We choose our subscription.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:29.020 --> 05:31.260
We choose our subscription.

118
05:31.260 --> 05:32.700
We choose our resource group.

119
05:32.700 --> 05:34.540
We choose our region.

120
05:34.540 --> 05:36.380
We give it a name.

121
05:36.380 --> 05:41.420
So in this case, I'll simply call it LNG1 for local network gateway one.

122
05:41.420 --> 05:45.730
And then of course, we can choose whether we want to specify the IP address or

123
05:45.730 --> 05:46.900
the FQDN

124
05:46.900 --> 05:48.900
or fully qualified domain name.

125
05:48.900 --> 05:54.260
So if we wanted to say something like gateway.company.com something like that,

126
05:54.260 --> 05:54.980
then of course, we would

127
05:54.980 --> 05:56.980
choose FQDN.

128
05:56.980 --> 05:59.820
In my case, I'm simply going to put in the IP address.

129
05:59.820 --> 06:05.820
This again is the IP address for the outside of my headquarters network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
05:59.820 --> 06:05.820
This again is the IP address for the outside of my headquarters network.

130
06:05.820 --> 06:08.340
This is going to be the public address.

131
06:08.340 --> 06:12.180
In other words, the NAT outside address.

132
06:12.180 --> 06:17.300
So how this is going to be seen from Microsoft Azure.

133
06:17.300 --> 06:22.510
Once we have the address in, we have to specify the address range that's

134
06:22.510 --> 06:23.940
available behind

135
06:23.940 --> 06:26.460
this local network gateway.

136
06:26.460 --> 06:30.700
So I'm simply going to say 10.0.0.0/8.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
06:26.460 --> 06:30.700
So I'm simply going to say 10.0.0.0/8.

137
06:30.700 --> 06:34.590
That would cover all of our sites if we decided to deploy multiple sites at the

138
06:34.590 --> 06:36.460
same time.

139
06:36.460 --> 06:40.620
Once all of this is properly configured, let's go to next.

140
06:40.620 --> 06:45.060
Here's where we can choose whether we want to actually configure BGP or not.

141
06:45.060 --> 06:47.780
In this case, it's a fairly simple network.

142
06:47.780 --> 06:50.940
And we're just going to be doing static routing to get this working.

143
06:50.940 --> 06:55.300
But we could definitely deploy BGP here if we wanted to.

144
06:55.300 --> 06:59.740
Of course, if we turn on yes, it's going to give us some other options here as

145
06:59.740 --> 07:00.660
far as giving
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
06:59.740 --> 07:00.660
far as giving

146
07:00.660 --> 07:06.500
it an autonomous system number and configuring the BGP peer IP address.

147
07:06.500 --> 07:11.250
Now again, we're not going to do this in our case, but we could if we wanted to

148
07:11.250 --> 07:11.260
.

149
07:11.260 --> 07:15.940
So with that said, let's go ahead and go to review and create.

150
07:15.940 --> 07:21.140
As long as everything here looks correct, we'll go ahead and hit create.

151
07:21.140 --> 07:24.420
And once this is configured, let's go to the resource.

152
07:24.420 --> 07:30.060
And here on the overview page, we can see that this is properly configured.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

152
07:24.420 --> 07:30.060
And here on the overview page, we can see that this is properly configured.

153
07:30.060 --> 07:35.420
So in this video, we took care of creating our virtual network gateway for the

154
07:35.420 --> 07:36.100
Azure side

155
07:36.100 --> 07:41.500
of the VPN connection and the local network gateway representing the remote end

156
07:41.500 --> 07:42.260
, which of

157
07:42.260 --> 07:45.740
course, in our case, is our headquarters site.

158
07:45.740 --> 07:50.780
Once all of this is configured, the next step is to configure the VPN itself.

159
07:50.780 --> 07:52.940
So that's what we're gonna do in the next video.

160
07:52.940 --> 08:02.940
[BLANK_AUDIO]