WEBVTT

1
00:00.000 --> 00:07.660
So for this challenge, we've been told that our customer with this environment

2
00:07.660 --> 00:08.360
has now

3
00:08.360 --> 00:13.880
added a new subnet on their AWS side subnet 20.

4
00:13.880 --> 00:18.060
They're telling us that the subnet is actually functional, however, it's not

5
00:18.060 --> 00:19.840
doing failover.

6
00:19.840 --> 00:23.640
So let's start off by verifying that it's actually working.

7
00:23.640 --> 00:29.560
So here we're on server two and we'll trace route to workstation one, 10, 10,

8
00:29.560 --> 00:30.960
10, 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:29.560 --> 00:30.960
10, 10.

9
00:30.960 --> 00:35.140
We see here that it is in fact functional and it is in fact going through

10
00:35.140 --> 00:35.920
router one

11
00:35.920 --> 00:37.920
and then through tunnel one.

12
00:37.920 --> 00:41.400
However, they're telling us that it doesn't fail over.

13
00:41.400 --> 00:46.400
Now if you want, you could go shut down router one and verify that the failover

14
00:46.400 --> 00:48.200
is not working,

15
00:48.200 --> 00:52.430
but in the interest of time, we will just assume that it is not working and we

16
00:52.430 --> 00:52.920
'll go

17
00:52.920 --> 00:56.640
check out what's going on on router two.

18
00:56.640 --> 01:00.280
So one router two, let's just start with the most obvious thing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:56.640 --> 01:00.280
So one router two, let's just start with the most obvious thing.

19
01:00.280 --> 01:04.760
Let's do a show IP interface brief so we can check its IP address.

20
01:04.760 --> 01:11.150
And what we actually discover is they didn't even configure an interface for

21
01:11.150 --> 01:12.080
router two

22
01:12.080 --> 01:14.400
on subnet 20.

23
01:14.400 --> 01:17.960
So we're going to have to start by creating the interface.

24
01:17.960 --> 01:21.160
That means we have to go into AWS.

25
01:21.160 --> 01:28.140
So in AWS, we'll start in EC2, we'll scroll down here and we'll go to network

26
01:28.140 --> 01:29.480
interfaces.

27
01:29.480 --> 01:32.240
We'll create a new network interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.480 --> 01:32.240
We'll create a new network interface.

28
01:32.240 --> 01:35.040
This is going to be in subnet 20.

29
01:35.040 --> 01:37.880
We do want to give it its own IP address.

30
01:37.880 --> 01:41.160
We'll use the same IP addressing scheme.

31
01:41.160 --> 01:49.370
So this would be 10 dot 20 because this is the AWS side 24 subnet 20 and two 53

32
01:49.370 --> 01:50.000
because

33
01:50.000 --> 01:52.160
this is router two.

34
01:52.160 --> 01:53.680
We'll scroll down.

35
01:53.680 --> 01:55.720
This is an inside interface.

36
01:55.720 --> 02:00.060
So it's going to get the security group SG LAN and then we'll just create the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:55.720 --> 02:00.060
So it's going to get the security group SG LAN and then we'll just create the

37
02:00.060 --> 02:00.600
network

38
02:00.600 --> 02:02.200
interface.

39
02:02.200 --> 02:04.520
As usual, we want to name it.

40
02:04.520 --> 02:07.080
This will be R2 gigabit three.

41
02:07.080 --> 02:11.110
We also want to make sure under actions that we go into change source

42
02:11.110 --> 02:12.560
destination check,

43
02:12.560 --> 02:14.200
turn this off.

44
02:14.200 --> 02:19.560
And finally under actions, we're going to attach this specifically.

45
02:19.560 --> 02:23.360
We're attaching it to AWS R2.

46
02:23.360 --> 02:27.520
We'll hit attach one final note while we're here.

47
02:27.520 --> 02:34.230
We are going to need the network interface IDs, both for router one gigabit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:27.520 --> 02:34.230
We are going to need the network interface IDs, both for router one gigabit

48
02:34.230 --> 02:35.160
three and

49
02:35.160 --> 02:38.080
for this new router two gigabit three.

50
02:38.080 --> 02:41.480
So you probably want to record these while we're here.

51
02:41.480 --> 02:47.300
The other thing, of course, we need if we go over to the VPC, under route

52
02:47.300 --> 02:48.360
tables.

53
02:48.360 --> 02:53.640
We also need to record the route table ID for network 20.

54
02:53.640 --> 02:58.240
This is of course, so that we can set up our redundancy cluster.

55
02:58.240 --> 03:02.450
We're just assuming at this point that the customer did not do any of that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:58.240 --> 03:02.450
We're just assuming at this point that the customer did not do any of that

56
03:02.450 --> 03:02.920
since they

57
03:02.920 --> 03:06.920
didn't even create the interface for router two.

58
03:06.920 --> 03:11.680
So once we have all of that information recorded, let's go back over to our

59
03:11.680 --> 03:12.800
router to configure

60
03:12.800 --> 03:14.480
its interface.

61
03:14.480 --> 03:18.850
So back here on router two, we've configured these interfaces numerous times

62
03:18.850 --> 03:19.320
now.

63
03:19.320 --> 03:22.520
So let's just go ahead and paste this configuration in.

64
03:22.520 --> 03:26.320
And what we see is we're simply creating the gigabit three interface.

65
03:26.320 --> 03:29.040
We're having a pull its address from DHCP.

66
03:29.040 --> 03:34.580
We're configuring OSPF to be non broadcast, resetting hello interval to 10
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:29.040 --> 03:34.580
We're configuring OSPF to be non broadcast, resetting hello interval to 10

67
03:34.580 --> 03:35.480
seconds, putting

68
03:35.480 --> 03:40.760
it in area zero, configuring BFD, no shutting the interface.

69
03:40.760 --> 03:45.730
We also put in here going into router OSPF one and configuring the neighbor

70
03:45.730 --> 03:46.480
statement

71
03:46.480 --> 03:48.440
for router one.

72
03:48.440 --> 03:49.920
So let's do some verification.

73
03:49.920 --> 03:52.960
We'll do a show IP OSPF neighbor.

74
03:52.960 --> 03:57.940
We see that we are in fact up as neighbors with router one over our gigabit

75
03:57.940 --> 03:58.880
three interface

76
03:58.880 --> 04:00.160
now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:58.880 --> 04:00.160
now.

77
04:00.160 --> 04:05.550
And if we do show BFD neighbor, we see that we're also up over our gigabit

78
04:05.550 --> 04:07.080
three interface.

79
04:07.080 --> 04:12.360
So now this is looking all good to configure our redundancy cluster.

80
04:12.360 --> 04:14.960
So let's start here on router two.

81
04:14.960 --> 04:19.560
First thing we need to do of course is go back into guest shell.

82
04:19.560 --> 04:24.400
We'll go into the cloud folder and we'll paste in our command.

83
04:24.400 --> 04:25.840
So what do we configure in?

84
04:25.840 --> 04:29.720
Well, we're configuring this to be instance 22.

85
04:29.720 --> 04:34.840
Then we have the route table ID that we got for subnet 20.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:29.720 --> 04:34.840
Then we have the route table ID that we got for subnet 20.

86
04:34.840 --> 04:39.100
Of course, the region for me is still us East one.

87
04:39.100 --> 04:43.900
And here for the E and I, we're putting in the E and I that we got for router

88
04:43.900 --> 04:44.680
twos, gigabit

89
04:44.680 --> 04:46.640
three interface.

90
04:46.640 --> 04:49.800
We're also going to configure this to be secondary.

91
04:49.800 --> 04:54.460
So we'll configure that and notice that we're getting an error here telling us

92
04:54.460 --> 04:55.120
that this

93
04:55.120 --> 04:59.320
E and I was not found in that region.

94
04:59.320 --> 05:04.280
And that's because I didn't put the proper E and I on this statement.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:59.320 --> 05:04.280
And that's because I didn't put the proper E and I on this statement.

95
05:04.280 --> 05:10.320
So what we want to do is actually delete node 22 and put it back in correctly.

96
05:10.320 --> 05:15.080
I just wanted you to see how you can get rid of these if something gets messed

97
05:15.080 --> 05:15.560
up.

98
05:15.560 --> 05:23.440
So the command is actually delete node dot py and then you put in the instance

99
05:23.440 --> 05:23.800
number.

100
05:23.800 --> 05:27.600
Notice that now it deleted node 22.

101
05:27.600 --> 05:32.520
So let's put it back in correctly so we don't get any errors.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:27.600 --> 05:32.520
So let's put it back in correctly so we don't get any errors.

102
05:32.520 --> 05:36.760
So that's actually the correct E and I for router two.

103
05:36.760 --> 05:40.080
Now when we hit enter, we should get success.

104
05:40.080 --> 05:42.560
So notice this time we don't get any errors.

105
05:42.560 --> 05:48.240
It tells us all the inputs are valid and it created this instance properly.

106
05:48.240 --> 05:54.560
Now let's go over to router one and we'll configure this as the primary node.

107
05:54.560 --> 05:57.280
So once again, this says it was successful.

108
05:57.280 --> 05:59.440
So let's verify.

109
05:59.440 --> 06:02.000
Let's go back into AWS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
05:59.440 --> 06:02.000
Let's go back into AWS.

110
06:02.000 --> 06:06.960
This time we'll go to instances and we're going to shut down router one.

111
06:06.960 --> 06:09.120
So we'll stop the instance.

112
06:09.120 --> 06:11.960
Now let's go back to our server.

113
06:11.960 --> 06:14.120
Let's do our trace again.

114
06:14.120 --> 06:17.160
We got a few our timeouts on that first one.

115
06:17.160 --> 06:22.650
But if we trace it a second time, notice that now it's going to two fifty three

116
06:22.650 --> 06:22.880
, which

117
06:22.880 --> 06:27.560
is router two and it's going across tunnel two.

118
06:27.560 --> 06:32.520
So now our failover for subnet 20 is working properly.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
06:27.560 --> 06:32.520
So now our failover for subnet 20 is working properly.

119
06:32.520 --> 06:39.480
So that concludes this challenge, which means we have also completed this skill

120
06:39.480 --> 06:39.520
.

121
06:39.520 --> 06:46.920
So congratulations on completing configure iOS XE VPN redundancy in AWS.

122
06:46.920 --> 06:51.280
I hope this has been informative for you and I'd like to thank you for viewing.