WEBVTT

1
00:00.000 --> 00:03.040
In this video, we're going to put a game plan together for the implementation

2
00:03.040 --> 00:05.680
of HSRP.

3
00:05.680 --> 00:12.310
And we're going to use gig 00 here on R1 and gig 1 0 here on R2 to support that

4
00:12.310 --> 00:12.800
fault tolerance

5
00:12.800 --> 00:16.400
for the benefit of our client here PC12, which is expecting to have a default

6
00:16.400 --> 00:19.040
gateway at 10.12.0.9 U9.

7
00:19.040 --> 00:23.300
So as far as our game plan, let's go ahead for HSRP and let's use group number

8
00:23.300 --> 00:23.520
one.

9
00:23.520 --> 00:26.730
And that's just a number we'd pick out of the air. So as long as the two

10
00:26.730 --> 00:28.240
interfaces are believing

11
00:28.240 --> 00:31.990
and agreeing on using the same group, we're good to go. So we use group number
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.240 --> 00:31.990
and agreeing on using the same group, we're good to go. So we use group number

12
00:31.990 --> 00:32.240
one.

13
00:32.240 --> 00:37.210
And let's also use version two of HSRP. And let's also go ahead and enable pre

14
00:37.210 --> 00:37.520
empt.

15
00:37.520 --> 00:40.850
And that way the interface has the highest priority at any given moment. If

16
00:40.850 --> 00:41.920
they're both up,

17
00:41.920 --> 00:46.960
that will become the active router in HSRP. So we'll enable preempt. And then

18
00:46.960 --> 00:47.920
on R1,

19
00:47.920 --> 00:51.640
let's go ahead and set the priority. The default is 100. But on R1, let's go

20
00:51.640 --> 00:52.080
ahead and set it

21
00:52.080 --> 00:57.360
to 99 just below the default. And then on R2, on its gig 1 0 interface, let's

22
00:57.360 --> 00:58.160
set the priority

23
00:58.160 --> 01:02.920
to 105. And then to test it, we can go to PC12 here. And it should be able to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:58.160 --> 01:02.920
to 105. And then to test it, we can go to PC12 here. And it should be able to

24
01:02.920 --> 01:03.760
use this default gateway

25
01:03.760 --> 01:08.260
of .99 to go ahead and reach some other resource. So over here on R4, there's a

26
01:08.260 --> 01:09.200
loopback interface

27
01:09.200 --> 01:14.760
of 4.4.4.4.4. And all the routing is set up already in this environment. So as

28
01:14.760 --> 01:16.000
a test, we could ping

29
01:16.000 --> 01:21.020
from PC12 over to 4444. This is a validation that we can get off of our local

30
01:21.020 --> 01:21.760
subnet.

31
01:21.760 --> 01:27.520
As far as testing goes, if R2's gig 1 0 was the active router, and over here R1

32
01:27.520 --> 01:28.560
was a standby,

33
01:28.560 --> 01:33.070
if we shut down this interface on R2 gig 1 0, we should be able to still be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:28.560 --> 01:33.070
if we shut down this interface on R2 gig 1 0, we should be able to still be

34
01:33.070 --> 01:33.600
able to reach

35
01:33.600 --> 01:38.370
remote networks on PC12 because R1, which was the backup router, would become

36
01:38.370 --> 01:39.440
the active router,

37
01:39.440 --> 01:43.760
once it identified that it can no longer communicate or reach over here to R2's

38
01:43.760 --> 01:44.800
gig 1 0 interface.

39
01:44.800 --> 01:48.880
And again, that's the goal. To have first hop, the first hop for a client, like

40
01:48.880 --> 01:49.920
their default gateway,

41
01:49.920 --> 01:53.280
to have fault tolerance and redundancy. And that's what we're doing here with

42
01:53.280 --> 01:54.000
HSRP. So with this

43
01:54.000 --> 01:59.060
game plan in mind, let's go to the lab environment and let's configure HSRP on

44
01:59.060 --> 02:01.040
R1's gig 0 0 and on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:59.060 --> 02:01.040
R1's gig 0 0 and on

45
02:01.040 --> 02:05.430
R2's gig 1 0 for the benefit of PC12. All right. So here in the lab environment

46
02:05.430 --> 02:06.480
, and at the tail end

47
02:06.480 --> 02:10.070
of the set of videos, I'll give you a chance as well to get hands on practice

48
02:10.070 --> 02:11.520
with setting up FHRP.

49
02:11.520 --> 02:15.870
So here, let me go ahead and double click on the lab topology image here. That

50
02:15.870 --> 02:16.480
looks good. Let

51
02:16.480 --> 02:19.470
me go ahead and scoosh that over just a little bit. And then on server one

52
02:19.470 --> 02:20.480
right here, this is how we

53
02:20.480 --> 02:24.490
get to the console access for all of these devices, the four routers, the

54
02:24.490 --> 02:27.120
switch, and also our virtual PCs.

55
02:27.120 --> 02:30.400
So we'll go ahead and double click here on server one nugged to open that up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:27.120 --> 02:30.400
So we'll go ahead and double click here on server one nugged to open that up.

56
02:30.400 --> 02:31.120
We'll give that a

57
02:31.120 --> 02:35.840
moment or two to initialize. And here it comes. Fantastic. Here are the tabs

58
02:35.840 --> 02:38.000
for R1, R2, R3, R4,

59
02:38.000 --> 02:44.410
switch one, PC12, PC20, and PC30. Also, I have here on the desktop of the

60
02:44.410 --> 02:46.240
server one computer. I've got a

61
02:46.240 --> 02:50.780
document called FHRP useful commands. It's open right here. And if you want to

62
02:50.780 --> 02:52.400
leverage that and refer

63
02:52.400 --> 02:55.240
to the commands or do some copying, pasting what you're comfortable with the

64
02:55.240 --> 02:56.480
commands, that's all well

65
02:56.480 --> 03:00.290
and good. So here is the notepad document to the right. And I'll just click on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:56.480 --> 03:00.290
and good. So here is the notepad document to the right. And I'll just click on

66
03:00.290 --> 03:01.920
the taskbar here for

67
03:01.920 --> 03:05.400
multi tab putty and get access to our consoles. In fact, I'm going to go ahead

68
03:05.400 --> 03:06.320
and scoots this over

69
03:06.320 --> 03:10.170
a little bit more. Fantastic. So I can see both at the same time. So here's the

70
03:10.170 --> 03:11.920
syntax for HSRP.

71
03:11.920 --> 03:16.880
We go into the interface and you specify the version of HSRP we want to use. So

72
03:16.880 --> 03:17.920
the command that we're

73
03:17.920 --> 03:23.360
going to use to both configure and also to view HSRP is the command standby. So

74
03:23.360 --> 03:24.000
we'll go into

75
03:24.000 --> 03:26.930
interface config and let's make sure we have the right interface here. This can

76
03:26.930 --> 03:28.000
be gig 000 here on

77
03:28.000 --> 03:32.090
R1. And on gig 00, we're going to say standby space version two as opposed to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:28.000 --> 03:32.090
R1. And on gig 00, we're going to say standby space version two as opposed to

78
03:32.090 --> 03:33.200
version one. That way

79
03:33.200 --> 03:36.860
we're using version two. Then we're going to say standby group one and specify

80
03:36.860 --> 03:38.000
the virtual IP address.

81
03:38.000 --> 03:41.310
That'll be the default gateway the client's going to use and then we can

82
03:41.310 --> 03:42.560
specify standby the group

83
03:42.560 --> 03:45.960
number, the keyword priority and then the actual priority we want to give

84
03:45.960 --> 03:47.440
itself. We want R1 to have

85
03:47.440 --> 03:51.350
a priority of 99 instead of the default priority of 100 with some of these

86
03:51.350 --> 03:52.400
command right there.

87
03:52.400 --> 03:56.310
And if we want to enable preempt, we'd also do that for that same group standby

88
03:56.310 --> 03:58.320
one preempt. So in the lab

89
03:58.320 --> 04:00.900
what I'm going to do is I'm going to go ahead and go into configuration mode. I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:58.320 --> 04:00.900
what I'm going to do is I'm going to go ahead and go into configuration mode. I

90
04:00.900 --> 04:01.840
'm going to default

91
04:01.840 --> 04:04.950
interface gig 00. And what that's going to do is going to wipe out whatever is

92
04:04.950 --> 04:05.760
there previously

93
04:05.760 --> 04:08.720
because we're not only going to configure HSRP, we're also going to configure

94
04:08.720 --> 04:11.520
VRRP and also GLBP.

95
04:11.520 --> 04:14.390
So I just want to wipe them out each time just to make sure we have nice fresh

96
04:14.390 --> 04:14.720
start.

97
04:14.720 --> 04:18.210
So I'm going to take R1's config here and when you do the lab at the tail end

98
04:18.210 --> 04:19.360
of the set of videos,

99
04:19.360 --> 04:23.580
I would encourage you to do a couple of times just do it manually. Make sure

100
04:23.580 --> 04:24.240
you're comfortable with

101
04:24.240 --> 04:27.390
the commands and then once you've done it a few times, you can use the note pad

102
04:27.390 --> 04:28.800
document as a review

103
04:28.800 --> 04:31.800
or if you want to copy paste, you're welcome to that as well. So we'll take the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:28.800 --> 04:31.800
or if you want to copy paste, you're welcome to that as well. So we'll take the

104
04:31.800 --> 04:32.800
config for R1,

105
04:32.800 --> 04:36.640
we'll go to the R1 tab, we'll right click and paste and we've just defaulted

106
04:36.640 --> 04:37.440
the interface.

107
04:37.440 --> 04:41.920
I put the IP address back at 10.12.0.1 for R1 and then I use these commands

108
04:41.920 --> 04:42.320
right here to

109
04:42.320 --> 04:47.760
implement HSRP on that interface gig 00. So now that we have that set up, we

110
04:47.760 --> 04:48.160
should have

111
04:48.160 --> 04:53.680
effectively a default gateway that R1 is now providing that PC12 can now use.

112
04:53.680 --> 04:55.120
So if we go to PC12

113
04:55.120 --> 05:00.830
and on PC12, if we do a show IP, it'll show us the IP address it has of 10.12.0
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
04:55.120 --> 05:00.830
and on PC12, if we do a show IP, it'll show us the IP address it has of 10.12.0

114
05:00.830 --> 05:02.480
.51, fantastic.

115
05:02.480 --> 05:06.000
And it also shows here the default gateway and I just did a copy paste of

116
05:06.000 --> 05:07.040
standby version 2,

117
05:07.040 --> 05:11.200
which means nothing to this little PC. So here is the default gateway and so if

118
05:11.200 --> 05:12.160
you do the ping here

119
05:12.160 --> 05:17.700
to 10.12.0.99, we should get a response and there it is. That response is

120
05:17.700 --> 05:19.520
coming back from R1.

121
05:19.520 --> 05:24.170
It's the only device there running HSRP and if we go back to R1 and we do the

122
05:24.170 --> 05:25.520
show standby and press

123
05:25.520 --> 05:29.320
enter, here it's showing that this is our one. It is currently active as

124
05:29.320 --> 05:33.440
opposed to standby. The virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
05:29.320 --> 05:33.440
opposed to standby. The virtual

125
05:33.440 --> 05:39.230
IP address is 10.12.0.99. The virtual MAC address is this one ending in F001

126
05:39.230 --> 05:40.240
and so this character

127
05:40.240 --> 05:43.910
here, the one, the zero one is representing the actual group number. So if we

128
05:43.910 --> 05:44.640
use group 2,

129
05:44.640 --> 05:48.170
that would show up as a two. It shows here that preemption is enabled. The

130
05:48.170 --> 05:49.840
active router is local,

131
05:49.840 --> 05:53.640
standby router is unknown. That's because we haven't configured R2 yet and the

132
05:53.640 --> 05:55.440
priority is 99.

133
05:55.440 --> 05:59.500
And here is the actual group name. It's a combination of HSRP and the

134
05:59.500 --> 06:01.040
identifier for the interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
05:59.500 --> 06:01.040
identifier for the interface.

135
06:01.040 --> 06:04.510
You can also name the group if you want but by default it's going to use this

136
06:04.510 --> 06:05.600
syntax. So if we

137
06:05.600 --> 06:10.530
look for this MAC address ending in F001, let's go to the switch and here on

138
06:10.530 --> 06:11.760
the switch and this

139
06:11.760 --> 06:15.520
take a look at our topology real quick. So if we're looking at this switch one

140
06:15.520 --> 06:16.000
and on the switch,

141
06:16.000 --> 06:19.990
we do a show MAC address table and press enter, you'll notice that it has that

142
06:19.990 --> 06:21.120
MAC address associated

143
06:21.120 --> 06:27.210
with gig 0/1 and that port happens to be where our one's gig 0, 0 interface is

144
06:27.210 --> 06:28.640
connected right there.

145
06:28.640 --> 06:32.240
So our next step is then to go ahead and add the real fault tolerance by also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
06:28.640 --> 06:32.240
So our next step is then to go ahead and add the real fault tolerance by also

146
06:32.240 --> 06:33.840
configuring gig 1,0

147
06:33.840 --> 06:38.280
over on R2 with the parameters that we planned on. So if we go to R2, then we

148
06:38.280 --> 06:39.600
go to our notepad document.

149
06:39.600 --> 06:43.520
On R2, we'll go into configuration mode, we'll set interase gig 1,0 to its

150
06:43.520 --> 06:44.080
defaults,

151
06:44.080 --> 06:49.400
we'll give it an IP address of 10.12.0.2 and then we'll issue the standby

152
06:49.400 --> 06:50.080
commands,

153
06:50.080 --> 06:56.080
specifying version 2, the virtual IP address for group 1 being 10.12.0.99 and a

154
06:56.080 --> 06:57.280
priority of 105

155
06:57.280 --> 07:00.960
and we'll also enable preempt. So we'll go ahead and put that on R2 right now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
06:57.280 --> 07:00.960
and we'll also enable preempt. So we'll go ahead and put that on R2 right now.

156
07:00.960 --> 07:01.760
So I'll copy that

157
07:01.760 --> 07:05.740
and now with that in my buffer, we'll go to R2 and right click and paste. So we

158
07:05.740 --> 07:06.240
should lose the

159
07:06.240 --> 07:09.590
neighbor adjacency with OSPF and then it should come back because we removed

160
07:09.590 --> 07:10.800
the IP address and now it's

161
07:10.800 --> 07:16.150
going through the HSRP state change of from listening to active as shown right

162
07:16.150 --> 07:16.880
here. And that's

163
07:16.880 --> 07:21.220
because it had a higher priority. So if we were to do this, show standby now.

164
07:21.220 --> 07:21.920
In price center,

165
07:21.920 --> 07:26.750
here's showing that this router R2 is active. Here's the virtual IP address.

166
07:26.750 --> 07:28.160
Here's the virtual MAC

167
07:28.160 --> 07:32.190
address associated with that .99 address. Preemption is enabled. The active
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
07:28.160 --> 07:32.190
address associated with that .99 address. Preemption is enabled. The active

168
07:32.190 --> 07:33.840
router is local, meaning on R2

169
07:33.840 --> 07:38.640
and the standby router is over at 10.12.0.1. That's R1. And the reason that we

170
07:38.640 --> 07:39.440
are active and the other

171
07:39.440 --> 07:44.490
guy standby is because our priority is 105 preempt is enabled and the other

172
07:44.490 --> 07:46.400
router has a priority of 99.

173
07:46.400 --> 07:50.320
So if we looked at the topology. So if we went back to the switch and we asked

174
07:50.320 --> 07:50.880
to switch the show

175
07:50.880 --> 07:55.760
to its MAC address table, it would now associate that MAC address ending in F00

176
07:55.760 --> 07:57.680
1 with gig 02, which

177
07:57.680 --> 08:02.870
leads over to R2's gig 1 0. That's because R2 on its gig 1 0 interface is now
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
07:57.680 --> 08:02.870
leads over to R2's gig 1 0. That's because R2 on its gig 1 0 interface is now

178
08:02.870 --> 08:04.240
the active router.

179
08:04.240 --> 08:07.840
So if we go up to switch one and here on switch one, we hit the upper key and

180
08:07.840 --> 08:08.560
show MAC address

181
08:08.560 --> 08:13.710
table. Notice previously, F001 was associated with gig 01 and now F001 is

182
08:13.710 --> 08:15.680
associated with gig 02.

183
08:15.680 --> 08:21.120
So if we were to go back to our PC PC 12 and if we were going to ping something

184
08:21.120 --> 08:22.800
like 4.4.4.4,

185
08:22.800 --> 08:26.450
which is the loop back interface on R4, no problem. And if we do a show app, it

186
08:26.450 --> 08:26.880
'll show us the

187
08:26.880 --> 08:30.640
ARP cache. And there's the ARP cache that we currently have for the 10.12.0.99
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
08:26.880 --> 08:30.640
ARP cache. And there's the ARP cache that we currently have for the 10.12.0.99

188
08:30.640 --> 08:31.280
address, our default

189
08:31.280 --> 08:36.400
gateway. And that's the MAC address ending in F001. So because 2 is the active

190
08:36.400 --> 08:37.280
router, as shown

191
08:37.280 --> 08:41.270
right here with the output of show standby, what would happen if we went to

192
08:41.270 --> 08:43.360
interface gig 1/0

193
08:43.360 --> 08:48.390
and we said shut down. So that's now shut down R1 can no longer see the hello

194
08:48.390 --> 08:48.880
message during

195
08:48.880 --> 08:53.480
the else coming over from R2 regarding HSRP. So if we go back to R1 and we look

196
08:53.480 --> 08:54.320
at the console

197
08:54.320 --> 08:58.010
message here, it went from speak to standby. And in a moment, it's going to go

198
08:58.010 --> 08:59.600
from standby to active.

199
08:59.600 --> 09:04.000
And now it's the active router. So we do a show standby here on router 1 is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

199
08:59.600 --> 09:04.000
And now it's the active router. So we do a show standby here on router 1 is

200
09:04.000 --> 09:04.720
showing the status

201
09:04.720 --> 09:07.900
active. Here's the virtual IP address we're supporting as the default gateway

202
09:07.900 --> 09:08.560
address for our

203
09:08.560 --> 09:12.270
clients. There's the associated there to MAC address and the active router is

204
09:12.270 --> 09:12.800
local. And the

205
09:12.800 --> 09:17.010
standby router is unknown. And that's because we have no idea where the standby

206
09:17.010 --> 09:18.080
router is because

207
09:18.080 --> 09:21.620
at the moment our 2's gig 1/0 interface is shut down and no longer

208
09:21.620 --> 09:22.640
communicating.

209
09:22.640 --> 09:28.340
So the benefit of this is we go back to PC12 and let's do a show ARP. So the AR

210
09:28.340 --> 09:29.600
P cache is still there,

211
09:29.600 --> 09:35.840
still showing F001 for its default gateway address. So we did a ping to 4.4.4.4
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
09:29.600 --> 09:35.840
still showing F001 for its default gateway address. So we did a ping to 4.4.4.4

212
09:35.840 --> 09:36.720
press center.

213
09:36.720 --> 09:40.640
That still works. No problem because we still have one or two routers that are

214
09:40.640 --> 09:41.360
part of the

215
09:41.360 --> 09:45.600
HSRP pair that's still providing that default gateway functionality. And this

216
09:45.600 --> 09:46.960
time it's R1. So we

217
09:46.960 --> 09:52.550
did a trace to 4.4.4.4. And we looked at the path. In fact, let's do a trace

218
09:52.550 --> 09:52.960
and we'll do a

219
09:52.960 --> 09:57.040
dash capital P1 for using ICMP. And that way we don't have the destination port

220
09:57.040 --> 09:58.080
and reachable message.

221
09:58.080 --> 10:02.000
The first hop is router 1. Then it's going to router 3. And then it's going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

221
09:58.080 --> 10:02.000
The first hop is router 1. Then it's going to router 3. And then it's going to

222
10:02.000 --> 10:02.720
router 4. So if we

223
10:02.720 --> 10:08.160
look at our topology, that'd be from PC12 down to R1 over the serial interface

224
10:08.160 --> 10:09.040
to R3. And then from

225
10:09.040 --> 10:13.760
R3 up to R4. And we went back to R2. And here on R2 because it was preemptive

226
10:13.760 --> 10:14.400
to enable if we did a

227
10:14.400 --> 10:17.910
no shutdown. That's going to bring up the interface. We'll let it have a moment

228
10:17.910 --> 10:18.880
. So OSPF can do its

229
10:18.880 --> 10:21.880
convergence. So now that we've given that a moment, if we do a show stand by

230
10:21.880 --> 10:22.800
and press center,

231
10:22.800 --> 10:27.120
here on router 2, it's now showing as active. And if we go back to our client,

232
10:27.120 --> 10:28.240
which is PC12,

233
10:28.240 --> 10:33.040
and we did a trace again, you'll notice now it's going through router 2 and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

233
10:28.240 --> 10:33.040
and we did a trace again, you'll notice now it's going through router 2 and

234
10:33.040 --> 10:33.920
then down to router 3

235
10:34.480 --> 10:38.020
and down to router 4. And the path is different because a different router is

236
10:38.020 --> 10:39.520
providing the functionality

237
10:39.520 --> 10:42.670
of the default gateway. So now that we've taken a look at the configuration and

238
10:42.670 --> 10:43.920
verification of HSRP

239
10:43.920 --> 10:48.710
in the next video, let's go ahead and do the same technique except using VRRP,

240
10:48.710 --> 10:49.920
the OpenStandard,

241
10:49.920 --> 10:53.560
for first hopper dynasty protocols. So when you're ready, I'll see you there in

242
10:53.560 --> 10:54.240
just a moment.