WEBVTT

1
00:00.000 --> 00:07.700
So for this challenge, we've been tasked with deploying a second or redundant

2
00:07.700 --> 00:10.000
router into AWS.

3
00:10.000 --> 00:14.800
So this is going to be almost the same as we did our one, but we'll actually

4
00:14.800 --> 00:17.000
have a little bit less work to do this time.

5
00:17.000 --> 00:21.530
We already, of course, have our VPC and our networking and our subnets, so we

6
00:21.530 --> 00:28.000
can start right here on the EC2 instances page and begin by launching our two.

7
00:28.000 --> 00:31.000
So we'll come up here to launch instances.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:28.000 --> 00:31.000
So we'll come up here to launch instances.

8
00:31.000 --> 00:34.000
This one will call AWS R2.

9
00:34.000 --> 00:38.000
Once again, of course, it's going to be a C8000V.

10
00:38.000 --> 00:40.000
We'll go ahead and select it.

11
00:40.000 --> 00:43.000
Notice once again, it wants me to subscribe.

12
00:43.000 --> 00:45.000
So we'll just say subscribe now.

13
00:45.000 --> 00:46.000
We'll scroll down.

14
00:46.000 --> 00:49.000
Once again, we need to put in our key pair so we can connect to it.

15
00:49.000 --> 00:51.000
We'll edit our networking.

16
00:51.000 --> 00:54.000
First interface is in subnet one.

17
00:54.000 --> 00:55.000
That is correct.

18
00:55.000 --> 00:58.000
We'll use our same security group.

19
00:58.000 --> 00:59.000
So SG1.

20
00:59.000 --> 01:02.000
We'll go to advanced configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.000 --> 01:02.000
We'll go to advanced configuration.

21
01:02.000 --> 01:06.270
Now for this one, the first interface, we're supposed to do according to our

22
01:06.270 --> 01:07.000
diagram.

23
01:07.000 --> 01:11.490
And if you review the diagram up at the top of the page, you'll notice that

24
01:11.490 --> 01:16.000
this one is supposed to be 10.20.1.253.

25
01:16.000 --> 01:18.000
So we'll go ahead and put that address in there.

26
01:18.000 --> 01:21.000
Then we'll add our additional interface.

27
01:21.000 --> 01:26.000
Remember, this one is going to be in subnet 10.

28
01:26.000 --> 01:30.000
This one is going to be 10.20.10.253.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:30.000 --> 01:32.000
That should be everything we need here.

30
01:32.000 --> 01:34.000
We'll hit launch instance.

31
01:34.000 --> 01:36.000
Go back to instances.

32
01:36.000 --> 01:39.000
We'll hit refresh since it's not even on our list yet.

33
01:39.000 --> 01:40.000
There we go.

34
01:40.000 --> 01:41.000
It is currently launching.

35
01:41.000 --> 01:44.610
Now we could sit here and wait for this or we could go ahead and configure the

36
01:44.610 --> 01:47.000
interface as a while.

37
01:47.000 --> 01:52.060
So once again, if we click on our instance, go to networking, we want to record

38
01:52.060 --> 01:58.000
our interface IDs and their private addresses so we know which interface is on

39
01:58.000 --> 01:59.000
which subnet.

40
01:59.000 --> 02:02.000
Then of course, we go over to network interfaces.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:59.000 --> 02:02.000
Then of course, we go over to network interfaces.

41
02:02.000 --> 02:05.000
And this time, we're going to do two things.

42
02:05.000 --> 02:09.000
First, we want to refresh because we don't have those interfaces yet.

43
02:09.000 --> 02:10.000
There they are.

44
02:10.000 --> 02:15.230
So here we see the one C zero, which in my case, this is the subnet one or the

45
02:15.230 --> 02:17.000
outside interface.

46
02:17.000 --> 02:21.000
So this is a WS R2 gigabit one.

47
02:21.000 --> 02:26.960
And while we have that one highlighted, we'll go to actions, change the source

48
02:26.960 --> 02:30.000
destination check and turn this off.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:30.000 --> 02:32.000
That way it's ready to do IP forward it.

50
02:32.000 --> 02:34.000
Then we'll rename this one.

51
02:34.000 --> 02:38.000
So we'll make that a WS R2 gigabit two.

52
02:38.000 --> 02:44.550
And once again, under our actions, we'll change the source destination check,

53
02:44.550 --> 02:46.000
turning it off.

54
02:46.000 --> 02:49.000
Then we'll hop over to our elastic IPs.

55
02:49.000 --> 02:53.000
I already have one reserved here for R2 VPN zero.

56
02:53.000 --> 02:58.000
So I associate it to our two's gigabit one interface.

57
02:58.000 --> 03:00.000
Again, that's the outside interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
03:00.000 --> 03:04.000
And then we choose this as our two 53 address.

59
03:04.000 --> 03:08.000
Again, we'll allow re association in case we need to and we'll hit associate.

60
03:08.000 --> 03:12.000
So that should take care of everything as far as deploying it in AWS.

61
03:12.000 --> 03:16.000
We should now be able to SSH into this router.

62
03:16.000 --> 03:20.770
So now that we've gotten connected into AWS R2, of course, the next thing we

63
03:20.770 --> 03:23.000
have to do is put in our certificate.

64
03:23.000 --> 03:25.000
So we'll go ahead and paste that in.

65
03:25.000 --> 03:28.000
And then we'll put this into controller mode.

66
03:28.000 --> 03:33.000
We'll of course take the two defaults and we'll wait for router two to reload.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:28.000 --> 03:33.000
We'll of course take the two defaults and we'll wait for router two to reload.

67
03:33.000 --> 03:38.000
So now that we're back up and running, we'll go into config transaction.

68
03:38.000 --> 03:41.000
We'll put in our basic system configuration.

69
03:41.000 --> 03:48.000
So again, your system IP or site ID organization name, the V bond server, etc.

70
03:48.000 --> 03:51.000
Once that's done, we'll install our certificate.

71
03:51.000 --> 03:57.000
We'll go back into configuration mode and put in the configuration for SD WAN.

72
03:57.000 --> 04:02.250
Then finally, we'll add this to SD WAN with our chassis serial number and our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:57.000 --> 04:02.250
Then finally, we'll add this to SD WAN with our chassis serial number and our

73
04:02.250 --> 04:03.000
token.

74
04:03.000 --> 04:08.730
Once this is complete, let's jump over to SD WAN and make sure that it's been

75
04:08.730 --> 04:10.000
added properly.

76
04:10.000 --> 04:15.000
So after a refresh here on the device configuration page,

77
04:15.000 --> 04:20.000
we see that AWS R2 is currently being associated.

78
04:20.000 --> 04:24.000
It's not quite online just yet, but it's in the process.

79
04:24.000 --> 04:30.000
If we go over to monitor and then devices, we'll give this just a few moments
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:30.000 --> 04:31.000
to stabilize

81
04:31.000 --> 04:36.000
and get its health to a green check mark before we apply our template.

82
04:36.000 --> 04:38.000
So it's been just a few seconds.

83
04:38.000 --> 04:43.000
After a refresh, we now have that green check mark on AWS R2.

84
04:43.000 --> 04:48.150
We're not quite getting CPU and memory utilization from it just yet, but that's

85
04:48.150 --> 04:49.000
okay.

86
04:49.000 --> 04:53.000
Now let's apply our template to AWS R2.

87
04:53.000 --> 04:57.000
And this is where it gets really easy to simply add an additional router.

88
04:57.000 --> 05:00.000
We simply go over here to configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
05:00.000 --> 05:02.000
We go to templates.

90
05:02.000 --> 05:07.000
And on our AWS edge router template, we simply attach a new device.

91
05:07.000 --> 05:12.000
We add AWS R2 and we say attach.

92
05:12.000 --> 05:15.000
Host name is still going to be AWS R2.

93
05:15.000 --> 05:20.000
System IP is going to be 10.255.20.2.

94
05:20.000 --> 05:23.000
And the site ID is still going to be site 20.

95
05:23.000 --> 05:26.000
Again, we get a status of a green check mark.

96
05:26.000 --> 05:31.000
Let's hit next, configure devices, and we'll let this finish.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
05:26.000 --> 05:31.000
Let's hit next, configure devices, and we'll let this finish.

97
05:31.000 --> 05:34.000
So we see here that it's been successful.

98
05:34.000 --> 05:36.000
So let's verify that.

99
05:36.000 --> 05:41.000
Let's jump into on-prem router one and take a look at its routing table.

100
05:41.000 --> 05:46.000
So let's go ahead and do a show IP route for VRF 10.

101
05:46.000 --> 05:49.000
And here we see exactly what we were looking for.

102
05:49.000 --> 05:55.000
We have two paths to get to 10.20.10.0/24.

103
05:55.000 --> 06:02.000
One of them through AWS one and the other through AWS two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:55.000 --> 06:02.000
One of them through AWS one and the other through AWS two.

104
06:02.000 --> 06:05.000
So this was exactly the goal of this challenge.

105
06:05.000 --> 06:10.330
With this working, that does in fact conclude this challenge and therefore this

106
06:10.330 --> 06:11.000
skill.

107
06:11.000 --> 06:15.300
If you feel you are missing any of the information needed to complete this

108
06:15.300 --> 06:16.000
challenge,

109
06:16.000 --> 06:21.000
I would encourage you to go back and review the necessary sections above.

110
06:21.000 --> 06:28.000
Otherwise, congratulations on completing manual SDWAN deployment to AWS.

111
06:28.000 --> 06:33.000
I hope this has been informative for you and I'd like to thank you for viewing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
06:28.000 --> 06:33.000
I hope this has been informative for you and I'd like to thank you for viewing.