WEBVTT

1
00:00.000 --> 00:04.440
So for this challenge, we're asked to deploy

2
00:04.440 --> 00:08.320
a redundant router into Microsoft Azure.

3
00:08.320 --> 00:11.560
This is of course going to be far easier than deploying

4
00:11.560 --> 00:15.120
the first one because we already have Azure set up to

5
00:15.120 --> 00:18.080
support the catalyst 8000V,

6
00:18.080 --> 00:20.600
meaning we already have our virtual networks and

7
00:20.600 --> 00:22.720
our subnet setup and so on,

8
00:22.720 --> 00:28.480
and we already have our templates created on the SD-WAN side.

9
00:28.480 --> 00:32.480
So we can actually start off right here in the marketplace
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.480 --> 00:32.480
So we can actually start off right here in the marketplace

10
00:32.480 --> 00:36.040
with deploying our second C8000V.

11
00:36.040 --> 00:38.240
So let's go ahead and start.

12
00:38.240 --> 00:43.440
We'll simply do our search once again for the C8000V.

13
00:43.440 --> 00:46.440
We'll choose our bring your own license model.

14
00:46.440 --> 00:48.720
Once again, we'll select the correct version.

15
00:48.720 --> 00:53.400
In our case, that's 171301A. We'll hit Create.

16
00:53.400 --> 00:55.880
We'll put it in the correct resource group.

17
00:55.880 --> 00:57.760
We'll give it a name.

18
00:57.760 --> 01:00.360
We'll make this Azure R2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:57.760 --> 01:00.360
We'll make this Azure R2.

19
01:00.360 --> 01:03.760
Again, we'll set the region and our availability and

20
01:03.760 --> 01:05.960
zone options appropriately.

21
01:05.960 --> 01:09.520
If we scroll down, we see the security type is correct.

22
01:09.520 --> 01:12.040
The image has been selected properly.

23
01:12.040 --> 01:17.240
It is set to X64 and it is using the correct VM size,

24
01:17.240 --> 01:19.840
the standard DS2V2.

25
01:19.840 --> 01:22.240
Once again, we don't want hibernation,

26
01:22.240 --> 01:24.800
but we do need to set up our administrator account.

27
01:24.800 --> 01:26.920
So we'll scroll down here a little further.

28
01:26.920 --> 01:30.360
We'll change this from generate a new pair to once again,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:26.920 --> 01:30.360
We'll change this from generate a new pair to once again,

29
01:30.360 --> 01:35.160
use our existing key and we will choose our Azure key.

30
01:35.160 --> 01:37.720
We'll hit next to go to disks.

31
01:37.720 --> 01:39.960
Again, we don't need to change anything here,

32
01:39.960 --> 01:42.360
so we'll just hit next for networking.

33
01:42.360 --> 01:46.480
So once again, SDWAN is correct for our virtual network.

34
01:46.480 --> 01:49.680
We do want our first interface on subnet one.

35
01:49.680 --> 01:53.200
We do want it to create its own public IP address.

36
01:53.200 --> 01:55.880
It's going to create its own network security group.

37
01:55.880 --> 01:58.680
So all of this so far is correct.

38
01:58.680 --> 02:01.640
And if we look here at the bottom, we can if we want,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:58.680 --> 02:01.640
And if we look here at the bottom, we can if we want,

39
02:01.640 --> 02:04.800
choose to delete this once we get rid of the router.

40
02:04.800 --> 02:06.800
Since it is a lab, normally again,

41
02:06.800 --> 02:08.920
you may or may not want to do that.

42
02:08.920 --> 02:11.400
We'll leave the accelerated networking enabled

43
02:11.400 --> 02:13.840
and no load balancing.

44
02:13.840 --> 02:15.840
Now we know from going through the skill

45
02:15.840 --> 02:18.320
that we don't really need to change anything else here.

46
02:18.320 --> 02:21.160
So we'll just go right to review and create.

47
02:21.160 --> 02:22.400
We'll go ahead and hit create.

48
02:22.400 --> 02:24.440
Everything here looks correct.

49
02:24.440 --> 02:26.400
So now that the deployment is complete,

50
02:26.400 --> 02:28.440
let's go to the resource.

51
02:28.440 --> 02:30.160
And we know that we have to stop this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:28.440 --> 02:30.160
And we know that we have to stop this

52
02:30.160 --> 02:32.040
to add an additional interface.

53
02:32.040 --> 02:35.120
So let's just go ahead and stop this right away.

54
02:35.120 --> 02:37.640
We'll simply hit stop and yes,

55
02:37.640 --> 02:40.160
and we'll give this a moment to shut down.

56
02:40.160 --> 02:42.240
So we see here after just a few moments,

57
02:42.240 --> 02:45.040
it has gone to stopped, deallocated.

58
02:45.040 --> 02:46.440
The reason, of course, we had to do this

59
02:46.440 --> 02:48.440
was to deal with our networking.

60
02:48.440 --> 02:51.600
So with that said, let's go over here to network settings.

61
02:51.600 --> 02:54.480
And of course, there's a few things we want to change.

62
02:54.480 --> 02:57.640
First, on our primary network interface,

63
02:57.640 --> 03:00.400
we need to enable IP forwarding.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:57.640 --> 03:00.400
we need to enable IP forwarding.

64
03:00.400 --> 03:02.080
We'll apply that.

65
03:02.080 --> 03:04.640
And we want to change its IP address.

66
03:04.640 --> 03:08.920
We'll go into IP config here, change it to static.

67
03:08.920 --> 03:12.360
And this is supposed to be 253.

68
03:12.360 --> 03:13.720
We're supposed to set the address

69
03:13.720 --> 03:15.200
according to the diagram,

70
03:15.200 --> 03:18.040
and that's the address the diagram gives us.

71
03:18.040 --> 03:21.480
So we'll put that address in and we'll hit save.

72
03:21.480 --> 03:24.600
The next thing we have to do is add our second interface.

73
03:24.600 --> 03:28.320
So let's go back to the virtual machine itself.

74
03:28.320 --> 03:31.440
So these are the network settings on the actual VM.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:28.320 --> 03:31.440
So these are the network settings on the actual VM.

75
03:31.440 --> 03:35.120
And now what we want to do is attach a network interface.

76
03:35.120 --> 03:38.360
Now in this case, there actually are some other interfaces.

77
03:38.360 --> 03:40.840
However, those are, of course, already in use

78
03:40.840 --> 03:42.280
by our other router.

79
03:42.280 --> 03:43.960
So what we actually want to do here

80
03:43.960 --> 03:47.160
is create and attach a network interface.

81
03:47.160 --> 03:52.080
This one we'll call Azure R2 Gigabit 2.

82
03:52.080 --> 03:55.080
This one again goes on subnet 10.

83
03:55.080 --> 03:58.800
And if we scroll down, we're going to give this a static address.

84
03:58.800 --> 04:03.520
This is going to be the 10.30.10.253.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:58.800 --> 04:03.520
This is going to be the 10.30.10.253.

85
04:03.520 --> 04:05.520
We'll go ahead and hit create.

86
04:05.520 --> 04:08.000
Now that our networking is set up appropriately,

87
04:08.000 --> 04:12.800
we can go back to overview and start this router up.

88
04:12.800 --> 04:15.280
Now that the virtual machine is up and running,

89
04:15.280 --> 04:16.920
let's go ahead and connect to it,

90
04:16.920 --> 04:21.520
using the public IP address and our SSH key.

91
04:21.520 --> 04:24.440
So now that we've gotten connected into our router,

92
04:24.440 --> 04:26.560
the next thing we need to do is put in our certificate.

93
04:26.560 --> 04:28.840
So let's go ahead and paste that in.

94
04:28.840 --> 04:32.240
And then of course, we need to change this to controller mode.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:28.840 --> 04:32.240
And then of course, we need to change this to controller mode.

95
04:32.240 --> 04:33.720
We'll confirm the two defaults,

96
04:33.720 --> 04:36.480
losing our configuration and rebooting.

97
04:36.480 --> 04:39.120
So now our router is reloaded.

98
04:39.120 --> 04:41.800
Let's go in and config transaction.

99
04:41.800 --> 04:45.640
And we'll paste in our baseline configuration for the system.

100
04:45.640 --> 04:50.640
Then we'll install our certificate back into config transaction.

101
04:50.640 --> 04:53.720
And now we can put in our SD WAN configuration.

102
04:53.720 --> 04:57.480
Again, this is for our gigabit interface and our tunnel.

103
04:57.480 --> 05:02.280
Once that's done, we can go ahead and add this into SD WAN manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:57.480 --> 05:02.280
Once that's done, we can go ahead and add this into SD WAN manager.

104
05:02.280 --> 05:06.480
Once this is complete, we can jump over to SD WAN manager.

105
05:06.480 --> 05:09.720
We see Azure R2 coming online here,

106
05:09.720 --> 05:13.680
but it's of course unmanaged because we still need to apply our template.

107
05:13.680 --> 05:15.040
So let's do that.

108
05:15.040 --> 05:18.800
Let's go over to configuration, templates.

109
05:18.800 --> 05:21.520
Then for our Azure edge routers,

110
05:21.520 --> 05:25.240
let's click on our menu, go to attach devices,

111
05:25.240 --> 05:27.960
and add Azure R2.

112
05:27.960 --> 05:31.840
We'll attach it, fill in our information.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
05:27.960 --> 05:31.840
We'll attach it, fill in our information.

113
05:31.840 --> 05:34.760
Once we have everything filled out, we'll hit next,

114
05:34.760 --> 05:36.440
configure devices.

115
05:36.440 --> 05:40.000
Once that completes, we can come back here to monitor overview.

116
05:40.000 --> 05:44.360
And we see that we now have six WAN edges that are reachable.

117
05:45.000 --> 05:49.320
We can see that Azure R2 is now currently online.

118
05:49.320 --> 05:54.800
Again, we don't have CPU and memory utilization, but that's normal.

119
05:54.800 --> 05:58.760
So now let's find out if we have the routes that we expect to have

120
05:58.760 --> 06:01.680
on on-prem R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
05:58.760 --> 06:01.680
on on-prem R1.

121
06:01.680 --> 06:06.320
So what we want to look at here is a show IP route for VRF 10.

122
06:06.320 --> 06:13.200
Specifically what we're looking for is this entry here for 10.30.10.0/24,

123
06:13.200 --> 06:19.040
which now has two paths available, one through Azure R1,

124
06:19.040 --> 06:21.960
and the other through Azure R2.

125
06:21.960 --> 06:26.480
So now we have our redundant routing exactly as we wanted.

126
06:26.480 --> 06:30.920
So that concludes this challenge and therefore this skill.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

126
06:26.480 --> 06:30.920
So that concludes this challenge and therefore this skill.

127
06:30.920 --> 06:33.840
If you feel that you are missing any of the information needed

128
06:33.840 --> 06:37.280
to complete this challenge, I would encourage you to go back

129
06:37.280 --> 06:41.440
and review the necessary sections in the skill above.

130
06:41.440 --> 06:47.800
Otherwise, congratulations on completing manual SDWAN deployment to Azure.

131
06:47.800 --> 06:51.970
I hope this has been informative for you, and I'd like to thank you for viewing

132
06:51.970 --> 06:52.120
.

133
06:52.120 --> 07:01.660
[BLANK_AUDIO]