WEBVTT

1
00:00.000 --> 00:06.040
Finally, the moment we've been building up to here,

2
00:06.040 --> 00:07.920
we're going to actually deploy

3
00:07.920 --> 00:11.280
the Cloud Gateway into Microsoft Azure.

4
00:11.280 --> 00:13.840
As long as everything is configured properly,

5
00:13.840 --> 00:16.200
this should go with no problems.

6
00:16.200 --> 00:18.560
Now, one thing I will point out,

7
00:18.560 --> 00:21.600
when Microsoft creates the V-Hub,

8
00:21.600 --> 00:25.040
that actually takes a considerable amount of time.

9
00:25.040 --> 00:27.600
It also takes a little bit of time for

10
00:27.600 --> 00:31.440
the routing table for that V-Hub to come online.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.600 --> 00:31.440
the routing table for that V-Hub to come online.

11
00:31.440 --> 00:35.200
Therefore, this is a bit of a lengthy process,

12
00:35.200 --> 00:37.920
roughly about 40 minutes in fact.

13
00:37.920 --> 00:40.840
So, we're of course not going to sit here and watch the whole thing,

14
00:40.840 --> 00:43.560
we will skip ahead, but just be aware,

15
00:43.560 --> 00:46.320
if you're following along and doing this on your own,

16
00:46.320 --> 00:48.440
this is a place where, well,

17
00:48.440 --> 00:50.240
it might be time to take a lunch break.

18
00:50.240 --> 00:55.960
But nonetheless, let's go ahead and jump in and get this deployment started.

19
00:56.240 --> 01:01.200
So, here we're just going to start off on the Cloud Gateway dashboard,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:56.240 --> 01:01.200
So, here we're just going to start off on the Cloud Gateway dashboard,

20
01:01.200 --> 01:03.920
and down here under the workflows,

21
01:03.920 --> 01:09.040
under manage, we're now going to go to create Cloud Gateway.

22
01:09.040 --> 01:13.120
So, as we said, there's the global configuration,

23
01:13.120 --> 01:14.400
which we did earlier,

24
01:14.400 --> 01:17.040
and then there's a little bit more configuration here

25
01:17.040 --> 01:19.240
when we actually deploy the Gateway.

26
01:19.240 --> 01:22.960
So, the first thing we have to do is give the Cloud Gateway a name,

27
01:22.960 --> 01:27.360
we'll just call it CGW1 for Cloud Gateway 1.

28
01:27.360 --> 01:30.640
There's of course a description field here, which is optional,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:27.360 --> 01:30.640
There's of course a description field here, which is optional,

29
01:30.640 --> 01:32.320
if you want to fill that in.

30
01:32.320 --> 01:34.160
For the account name,

31
01:34.160 --> 01:37.160
we need to choose our authentication account,

32
01:37.160 --> 01:39.360
then we choose our region.

33
01:39.360 --> 01:42.200
For me, this is going to be East US,

34
01:42.200 --> 01:46.070
of course, you'll want to choose the region that you've been using this whole

35
01:46.070 --> 01:46.560
time.

36
01:46.560 --> 01:48.720
We click on the dropdown,

37
01:48.720 --> 01:50.640
we choose our resource group,

38
01:50.640 --> 01:52.960
in this case Cloud OnRamp,

39
01:52.960 --> 01:57.280
and then we have to choose our virtual WAN or our VWAN.

40
01:57.280 --> 01:59.240
Now, we haven't created one yet,

41
01:59.240 --> 02:01.840
so the only option here is going to be to create new.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:59.240 --> 02:01.840
so the only option here is going to be to create new.

42
02:01.840 --> 02:03.320
So, we'll click on that,

43
02:03.320 --> 02:05.800
it'll ask us what we want to call it,

44
02:05.800 --> 02:09.920
we'll just call it VWAN1, hit done,

45
02:09.920 --> 02:13.520
and then for the Azure Virtual WAN hub,

46
02:13.520 --> 02:15.920
notice that it's just going to create a new one

47
02:15.920 --> 02:18.160
based on the Cloud Gateway name,

48
02:18.160 --> 02:20.840
and that's going to be perfectly fine.

49
02:20.840 --> 02:22.640
Down at the bottom,

50
02:22.640 --> 02:27.040
we can make setting changes here if we want for the software image,

51
02:27.040 --> 02:28.680
but notice at this point,

52
02:28.680 --> 02:32.440
it's pulled that information in from the global settings.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:28.680 --> 02:32.440
it's pulled that information in from the global settings.

53
02:32.440 --> 02:38.280
But we do have to tell it which of our shadow routers that we want to use.

54
02:38.280 --> 02:41.200
If we click on the UUIDs here,

55
02:41.200 --> 02:43.480
notice it's only going to show us

56
02:43.480 --> 02:46.640
the two routers that we configured previously.

57
02:46.640 --> 02:50.600
So, these are just the two routers that we have pre-staged.

58
02:50.600 --> 02:54.320
If we scroll down a little bit more now, we can click Add.

59
02:54.320 --> 02:56.000
Before we do that though,

60
02:56.000 --> 02:59.840
take a look at this diagram that Cisco provides to the right,

61
02:59.840 --> 03:02.760
it gives you an idea of what's going to be deployed.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:59.840 --> 03:02.760
it gives you an idea of what's going to be deployed.

62
03:02.760 --> 03:06.960
So, Cloud Gateway as a feature is sort of shown in the middle here,

63
03:06.960 --> 03:11.320
and what it's showing us is that the Azure Virtual WAN hub

64
03:11.320 --> 03:15.760
is going to be deployed along with our Cloud Service routers,

65
03:15.760 --> 03:18.880
which are the two routers that we just chose.

66
03:18.880 --> 03:22.320
All of that said, let's go ahead and hit Add.

67
03:22.320 --> 03:25.120
This will now bring up the status page,

68
03:25.120 --> 03:29.280
and this is going to take a considerable amount of time.

69
03:29.280 --> 03:31.600
So, at this point, we will pause the video
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:29.280 --> 03:31.600
So, at this point, we will pause the video

70
03:31.600 --> 03:34.480
and jump ahead till when it's complete.

71
03:34.480 --> 03:38.240
So, here we've jumped ahead to where we have success.

72
03:38.240 --> 03:39.760
Just for the record,

73
03:39.760 --> 03:43.600
this took about 32 minutes or so, give or take.

74
03:43.600 --> 03:47.920
But let's go ahead and open up the success message.

75
03:47.920 --> 03:49.840
And what we're going to see,

76
03:49.840 --> 03:52.120
we're not going to go through this step-by-step,

77
03:52.120 --> 03:55.120
but as we can see, it actually did a lot of things.

78
03:55.120 --> 03:57.560
It created the multi-Cloud Gateway,

79
03:57.560 --> 04:02.360
it went through and it created an actual storage account on Azure,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:57.560 --> 04:02.360
it went through and it created an actual storage account on Azure,

80
04:02.360 --> 04:04.840
it then deployed the virtual hub.

81
04:04.840 --> 04:06.720
If we scroll all the way to the bottom,

82
04:06.720 --> 04:11.800
we can see here where it actually deployed the virtual network appliance.

83
04:11.800 --> 04:15.320
And finally, it created the Cloud Gateway.

84
04:15.320 --> 04:18.680
So, if this is deployed successfully at this point,

85
04:18.680 --> 04:22.040
we should be able to go back to our dashboard.

86
04:22.040 --> 04:26.360
So, we'll go back here to Monitor, and we'll go to Overview.

87
04:26.360 --> 04:31.720
So, as we can see here, we now have three WAN edges online,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:26.360 --> 04:31.720
So, as we can see here, we now have three WAN edges online,

88
04:31.720 --> 04:33.560
as we expected.

89
04:33.560 --> 04:36.280
And if we want to get a little more information on that,

90
04:36.280 --> 04:39.480
we can go over here and click on the three.

91
04:39.480 --> 04:43.080
And we can see that all of these devices are online.

92
04:43.080 --> 04:48.040
Now, we haven't actually gotten any CPU load or memory utilization

93
04:48.040 --> 04:50.520
from the two routers that were just deployed.

94
04:50.520 --> 04:54.360
That generally takes a couple minutes till that information gets collected.

95
04:54.360 --> 04:57.080
But otherwise, these devices are up and running.

96
04:57.080 --> 05:00.920
So, now that our deployment went through,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:57.080 --> 05:00.920
So, now that our deployment went through,

97
05:00.920 --> 05:03.640
all the devices seem to be up and running properly,

98
05:03.640 --> 05:07.640
let's jump in and do some final verification

99
05:07.640 --> 05:13.560
and set up a VPN so that our on-prem network can talk to the network

100
05:13.560 --> 05:15.480
that's running in Microsoft Azure.

101
05:15.480 --> 05:24.140
[BLANK_AUDIO]