WEBVTT

1
00:00.000 --> 00:07.000
So our next step is going to be to configure a first-hop redundancy protocol.

2
00:07.000 --> 00:10.000
We're specifically going to use HSRP.

3
00:10.000 --> 00:15.530
But the reason we need this, of course, is although we have OSPF right now

4
00:15.530 --> 00:18.000
dealing with failover between our tunnels,

5
00:18.000 --> 00:21.000
well, there's nothing to tell the end workstations that.

6
00:21.000 --> 00:25.370
So things like servers and printers and workstations would have no way of

7
00:25.370 --> 00:28.000
knowing if one tunnel failed

8
00:28.000 --> 00:31.000
and therefore they need to go to the other router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:28.000 --> 00:31.000
and therefore they need to go to the other router.

9
00:31.000 --> 00:34.000
So this is what a first-hop redundancy protocol is for.

10
00:34.000 --> 00:39.380
Now, this is going to work perfectly fine at our headquarters location in a

11
00:39.380 --> 00:41.000
traditional environment

12
00:41.000 --> 00:43.000
where we support multicast.

13
00:43.000 --> 00:49.140
However, remember that AWS does not support multicast, so we're going to have a

14
00:49.140 --> 00:50.000
problem there.

15
00:50.000 --> 00:52.000
But let's go ahead and jump in.

16
00:52.000 --> 00:54.000
We'll configure this at headquarters.

17
00:54.000 --> 00:58.720
Mostly as a reminder, we have been through this before, and then we'll take a

18
00:58.720 --> 01:00.000
look at the AWS side
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
01:00.000 --> 01:02.000
and how it won't work.

20
01:02.000 --> 01:07.000
So let's go ahead and jump in and get this configured.

21
01:07.000 --> 01:12.320
So our goal with our FHRP is going to be to have router one be the primary

22
01:12.320 --> 01:13.000
router.

23
01:13.000 --> 01:17.350
We want router two to be the secondary, and we want it to failover to the

24
01:17.350 --> 01:20.000
secondary should the tunnel fail.

25
01:20.000 --> 01:26.000
Now, the best way to do this is going to be to use IP SLA.

26
01:26.000 --> 01:29.000
So to configure this, we'll simply create an SLA instance.

27
01:29.000 --> 01:31.000
We'll just make it say 100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.000 --> 01:31.000
We'll just make it say 100.

28
01:31.000 --> 01:39.060
We'll set this up as an ICMP echo, and we'll just ping the other side, the 169.

29
01:39.060 --> 01:42.000
254.11.1.

30
01:42.000 --> 01:49.000
We'll set the threshold to 1000, the timeout to 1000, and the frequency to one.

31
01:49.000 --> 01:53.290
This way we're pinging the other side every one second, and after three

32
01:53.290 --> 01:55.000
failures or three seconds,

33
01:55.000 --> 01:58.000
it'll declare the tunnel down.

34
01:58.000 --> 02:01.000
The next thing we have to do, of course, is schedule this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:58.000 --> 02:01.000
The next thing we have to do, of course, is schedule this.

35
02:01.000 --> 02:05.000
So we'll say IPS LAs schedule, instance 100.

36
02:05.000 --> 02:10.000
Once we start, we want it to run forever, and we want it to start now.

37
02:10.000 --> 02:14.360
If we look at the show IPS LAs statistics, we can see that this is currently up

38
02:14.360 --> 02:15.000
and running.

39
02:15.000 --> 02:18.000
We already have nine successes.

40
02:18.000 --> 02:20.000
So far so good.

41
02:20.000 --> 02:24.000
Now, HSRP can't track SLA directly.

42
02:24.000 --> 02:26.000
So we are going to need a tracked object.

43
02:26.000 --> 02:28.000
We'll just make a track object 100.

44
02:28.000 --> 02:34.000
It's going to track IPS LA 100, and specifically the reachability.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:28.000 --> 02:34.000
It's going to track IPS LA 100, and specifically the reachability.

45
02:34.000 --> 02:36.000
We do a show track.

46
02:36.000 --> 02:39.000
We can now see that that tracked object is also up.

47
02:39.000 --> 02:42.000
So now we can configure our HSRP.

48
02:42.000 --> 02:44.000
So we'll go into interface, gigabit two.

49
02:44.000 --> 02:46.000
This is where it needs to be.

50
02:46.000 --> 02:50.000
Now we do need to change the IP address here in router one.

51
02:50.000 --> 02:54.000
So the IP address is now going to be 10.10.10.2.

52
02:54.000 --> 02:56.000
This is the slash 24.

53
02:56.000 --> 02:59.990
We may get an IP address conflict from this because router two is still

54
02:59.990 --> 03:03.000
configured this way, but it'll only be temporary.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:59.990 --> 03:03.000
configured this way, but it'll only be temporary.

55
03:03.000 --> 03:09.000
We want to set the standby one IP to be 10.10.10.1.

56
03:09.000 --> 03:14.000
We want to set the standby one priority to be something like 110.

57
03:14.000 --> 03:18.000
Because again, we said we want this side to be the primary.

58
03:18.000 --> 03:22.800
Now, if it were to fail over and it needs to fail back, we also need to

59
03:22.800 --> 03:24.000
configure pre-empt.

60
03:24.000 --> 03:28.000
So it can fail back in the event of a fail over.

61
03:28.000 --> 03:32.000
We want router one to take over again if the tunnel comes back up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:28.000 --> 03:32.000
We want router one to take over again if the tunnel comes back up.

62
03:32.000 --> 03:35.000
So it does have to be enabled for pre-empt.

63
03:35.000 --> 03:38.000
Then, of course, we have to implement our tracked object.

64
03:38.000 --> 03:42.000
So we say, stand one, track the 100 object.

65
03:42.000 --> 03:48.150
And if that were to go down, we want to decrement our priority by, well, we

66
03:48.150 --> 03:52.610
need to get it below the default of 100 because that's what router two is going

67
03:52.610 --> 03:53.000
to be.

68
03:53.000 --> 03:55.000
So let's say we decrement it by 20.

69
03:55.000 --> 03:57.000
That means it'll go down to 90.

70
03:57.000 --> 04:01.000
And then router two will take over.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:57.000 --> 04:01.000
And then router two will take over.

71
04:01.000 --> 04:03.000
Let's end our configuration.

72
04:03.000 --> 04:05.000
We'll do a show standby.

73
04:05.000 --> 04:08.000
And we see that as of right now, the state is active.

74
04:08.000 --> 04:10.000
The active router is local.

75
04:10.000 --> 04:13.000
It currently has a priority of 110.

76
04:13.000 --> 04:16.000
So, so far router one is configured properly.

77
04:16.000 --> 04:20.000
Let's do a very similar thing on router two.

78
04:20.000 --> 04:22.000
Again, router two is almost identical.

79
04:22.000 --> 04:26.550
So we'll paste the configuration in, but we will do it one part at a time just

80
04:26.550 --> 04:28.000
so we can see it work.

81
04:28.000 --> 04:33.240
So if we do our show IPSLA statistics, we see that our new SLA is up and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
04:28.000 --> 04:33.240
So if we do our show IPSLA statistics, we see that our new SLA is up and

82
04:33.240 --> 04:34.000
working.

83
04:34.000 --> 04:37.000
We'll put in our tracked object.

84
04:37.000 --> 04:39.000
This is also working.

85
04:39.000 --> 04:42.000
And then we'll configure our gigabit interface.

86
04:42.000 --> 04:44.000
We'll do show standby.

87
04:44.000 --> 04:46.000
It's currently in a state of listen.

88
04:46.000 --> 04:48.000
We did that fairly quickly.

89
04:48.000 --> 04:50.000
Let's give it just a moment.

90
04:50.000 --> 04:51.000
Do show stand again.

91
04:51.000 --> 04:53.000
It's now speaking to the other side.

92
04:53.000 --> 04:56.920
So they're figuring out which one is going to be the active, which one's going

93
04:56.920 --> 04:58.000
to be the standby.

94
04:58.000 --> 05:03.700
We look at this again and we see that now router two has assumed the role of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:58.000 --> 05:03.700
We look at this again and we see that now router two has assumed the role of

95
05:03.700 --> 05:07.000
standby with that default priority of 100.

96
05:07.000 --> 05:12.000
If we go back over to router one, do our show standby again.

97
05:12.000 --> 05:18.070
We see nothing's really changed here, except now it has a standby router being

98
05:18.070 --> 05:23.000
router two, where before the standby router was unknown.

99
05:23.000 --> 05:29.000
So this is HSRP working as it should be on the on-prem routers.

100
05:29.000 --> 05:31.000
But here's the problem.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
05:29.000 --> 05:31.000
But here's the problem.

101
05:31.000 --> 05:34.000
Let's go over to the AWS side.

102
05:34.000 --> 05:37.790
Now, since I have already indicated that this is not going to work, we're just

103
05:37.790 --> 05:43.310
going to go ahead and paste in a real quick, simple standby configuration for

104
05:43.310 --> 05:47.000
the gigabit to interface on both router one.

105
05:47.000 --> 05:49.000
And router two.

106
05:49.000 --> 05:52.660
Now, yes, this doesn't have all of the different features we would need, like

107
05:52.660 --> 05:56.000
tracking and all the stuff we just did pre-empt and so on.

108
05:56.000 --> 06:01.000
However, this is enough just to prove that this is not going to work.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
05:56.000 --> 06:01.000
However, this is enough just to prove that this is not going to work.

109
06:01.000 --> 06:03.000
Watch what happens.

110
06:03.000 --> 06:05.000
When we do a show standby.

111
06:05.000 --> 06:08.000
Now, this is still speaking, we have to give it a moment.

112
06:08.000 --> 06:14.000
If we look again, notice that router two has gone active.

113
06:14.000 --> 06:16.000
Now, that's not the most important part.

114
06:16.000 --> 06:19.000
The most important part is what's router one doing.

115
06:19.000 --> 06:25.000
If we do a show stand here, it's also active.

116
06:25.000 --> 06:30.000
This is, of course, because they're not talking to each other over multicast.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
06:30.000 --> 06:38.000
And unfortunately, there's no way to run unicast with either HSRP or VRRP.

118
06:38.000 --> 06:44.000
So we can't implement the same solution here that we did for OSPF.

119
06:44.000 --> 06:46.000
That's exactly why we have the next video.

120
06:46.000 --> 06:50.340
But let's just go ahead and explore this a little bit further just to show you

121
06:50.340 --> 06:53.000
what we, well, in this case, can't do.

122
06:53.000 --> 06:56.000
So let's go back into configuration mode.

123
06:56.000 --> 06:59.000
Back into our interface gigabit to interface.

124
06:59.000 --> 07:03.000
And let's look at the commands available after standby one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
06:59.000 --> 07:03.000
And let's look at the commands available after standby one.

125
07:03.000 --> 07:10.990
Notice there's no choice here for like a neighbor statement or mode unicast or

126
07:10.990 --> 07:17.000
that there's no solution built in here to run this over unicast.

127
07:17.000 --> 07:20.000
And maybe our solution wasn't to run HSRP.

128
07:20.000 --> 07:22.000
Maybe you wanted to run VRRP one.

129
07:22.000 --> 07:25.000
Well, it has the sort of same problem.

130
07:25.000 --> 07:30.000
There's no choice here either to run this as unicast.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
07:30.000 --> 07:33.000
So this is just not going to be a viable solution.

132
07:33.000 --> 07:41.790
As such, we're going to take off the standby one on each of these routers

133
07:41.790 --> 07:46.000
because it's not going to work.

134
07:46.000 --> 07:47.000
So where are we then?

135
07:47.000 --> 07:48.950
Well, we have our first time redundancy working exactly the way we want it to

136
07:48.950 --> 07:57.000
on-prem, but this is not supported in AWS.

137
07:57.000 --> 08:03.860
The good news is we do have catalyst 8000V redundancy that can help us with
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
07:57.000 --> 08:03.860
The good news is we do have catalyst 8000V redundancy that can help us with

138
08:03.860 --> 08:06.000
this situation in AWS.

139
08:06.000 --> 08:08.000
And it is the main thing we're here to look at.

140
08:08.000 --> 08:12.000
And that's exactly what we're going to do in our next section.

141
08:12.000 --> 08:30.000
[ Pause ]