WEBVTT

1
00:00.000 --> 00:03.840
Now one of the first elements regarding a first hop or dnc protocol to provide

2
00:03.840 --> 00:04.960
a fault tolerant

3
00:04.960 --> 00:09.710
default gateway for a client is that you need to have at least two routers that

4
00:09.710 --> 00:11.120
can support that client.

5
00:11.120 --> 00:15.050
So in our example in our topology here let's go ahead and focus on PC12 as a

6
00:15.050 --> 00:16.240
client device

7
00:16.240 --> 00:19.600
that's connected to the switch port here on this multiplier switch or in this

8
00:19.600 --> 00:20.160
example it's just

9
00:20.160 --> 00:24.120
acting as a layer two switch and then I've got two routers router one and

10
00:24.120 --> 00:25.840
router two that can act

11
00:25.840 --> 00:30.500
as part of the first hop or dnc protocol and the fault tolerance. So let's take
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:25.840 --> 00:30.500
as part of the first hop or dnc protocol and the fault tolerance. So let's take

12
00:30.500 --> 00:31.120
a moment and

13
00:31.120 --> 00:35.030
discuss how these routers on their respective gig zero zero interface and gig

14
00:35.030 --> 00:36.160
one zero interface

15
00:36.160 --> 00:40.110
can provide fault tolerance for a PC. So starting off the PC here has the ip

16
00:40.110 --> 00:43.840
address of 10.12.0.51

17
00:43.840 --> 00:49.210
with a 24 bit mask and its default gateways configured to be .99 on that same

18
00:49.210 --> 00:49.840
network.

19
00:49.840 --> 00:53.120
Now that PC could be statically configured with that ip address and default

20
00:53.120 --> 00:53.920
gateway or it could

21
00:53.920 --> 00:59.160
learn via DHCP but the end of the day if that client's default gateways .99 if

22
00:59.160 --> 01:00.240
this PC is going to forward
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.160 --> 01:00.240
this PC is going to forward

23
01:00.240 --> 01:04.270
traffic to any other network other than the local 10.12.0 network it's going to

24
01:04.270 --> 01:05.040
forward it to his

25
01:05.040 --> 01:09.180
default gateway at .99. So for fault tolerance if we have two routers like

26
01:09.180 --> 01:10.160
router one and router two

27
01:10.160 --> 01:14.000
that can support first hop or dnc protocols there's three options that we can

28
01:14.000 --> 01:15.280
choose from. One is a

29
01:15.280 --> 01:22.350
proprietary protocol from Cisco called hsrp which is an acronym for Cisco's hot

30
01:22.350 --> 01:23.680
standby router

31
01:23.680 --> 01:28.160
protocol and here's how it works we configure the gig one zero interface here

32
01:28.160 --> 01:29.120
on our two and the

33
01:29.120 --> 01:33.920
gig zero zero interface here on router one and we specify that with hsrp we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:29.120 --> 01:33.920
gig zero zero interface here on router one and we specify that with hsrp we're

34
01:33.920 --> 01:34.800
going to have a

35
01:34.800 --> 01:39.700
virtual ip address and for the purposes of this topology that virtual ip

36
01:39.700 --> 01:40.800
address that they're both

37
01:40.800 --> 01:47.020
going to support is giving me the default gateway address of 10.12.0.99 and

38
01:47.020 --> 01:47.840
that way if one of these

39
01:47.840 --> 01:50.920
two routers fails the other one is there to support that default gateway

40
01:50.920 --> 01:52.320
address and vice versa.

41
01:52.320 --> 01:55.920
Now behind the scenes with hsrp besides having a virtual ip address that's

42
01:55.920 --> 01:57.360
supported by both of

43
01:57.360 --> 02:01.490
these routers we're also going to have a virtualized mac address. Now the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:57.360 --> 02:01.490
these routers we're also going to have a virtualized mac address. Now the

44
02:01.490 --> 02:03.040
actual mac address is associated

45
02:03.040 --> 02:07.800
with this virtual ip address it depends on a few things number one are we using

46
02:07.800 --> 02:09.120
hsrp version one

47
02:09.120 --> 02:12.520
or we're using hsrp version two and regardless of those two there's also

48
02:12.520 --> 02:14.240
another option that says

49
02:14.240 --> 02:17.990
let's use the burn in address on the device acting as the active router

50
02:17.990 --> 02:19.360
supporting the virtual ip

51
02:19.360 --> 02:22.450
address but by default there's a specific mac address associated with version

52
02:22.450 --> 02:23.280
one and a different

53
02:23.280 --> 02:27.530
specific mac address that's used with version two and with hsrp we can set up h

54
02:27.530 --> 02:28.640
srp group so we

55
02:28.640 --> 02:31.420
would get that for example group one or group two or group three and as part of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:28.640 --> 02:31.420
would get that for example group one or group two or group three and as part of

56
02:31.420 --> 02:32.400
the last character or

57
02:32.400 --> 02:36.510
characters of the virtual mac address it's going to include that group number.

58
02:36.510 --> 02:37.520
Now as these devices

59
02:37.520 --> 02:40.990
are communicating back and forth they're also using multicast and the actual

60
02:40.990 --> 02:42.240
address for that multicast

61
02:42.240 --> 02:44.970
address for the back and forth is a communicating with each other and verify

62
02:44.970 --> 02:46.240
the other person is there

63
02:46.240 --> 02:49.050
meaning our one verifies that our two is still there and our two is verifying

64
02:49.050 --> 02:49.920
that our one is still

65
02:49.920 --> 02:56.810
there. That multicast is 224.0.0.0.0 and if we're using hsrp version one is two

66
02:56.810 --> 02:58.480
if we're using hsrp

67
02:58.480 --> 03:02.420
version two that could rest ends in one zero two. So if you want the two rout
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:58.480 --> 03:02.420
version two that could rest ends in one zero two. So if you want the two rout

68
03:02.420 --> 03:03.200
ers here on this

69
03:03.200 --> 03:06.540
common ethernet segment to go ahead and support hsrp they both need to be

70
03:06.540 --> 03:08.160
running version one or both

71
03:08.160 --> 03:11.690
need to be running version two. There's also the concept of a priority and if

72
03:11.690 --> 03:12.240
both of these

73
03:12.240 --> 03:15.050
interfaces came up at the same time and they're trying to decide which one's

74
03:15.050 --> 03:15.600
going to be

75
03:15.600 --> 03:19.140
responsible for responding to the virtual mac address and also responding to

76
03:19.140 --> 03:19.760
the virtual

77
03:19.760 --> 03:23.030
IP address which is what the client is using on their default gateway the

78
03:23.030 --> 03:24.000
priority is going to

79
03:24.000 --> 03:28.200
determine which one wins. So by default the priority is 100 so if we want our

80
03:28.200 --> 03:29.040
two to win we could

81
03:29.040 --> 03:32.930
set our two to be a priority for example of 101 and we believe our one as a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:29.040 --> 03:32.930
set our two to be a priority for example of 101 and we believe our one as a

82
03:32.930 --> 03:34.640
default priority of 100

83
03:34.640 --> 03:37.670
and if these two interfaces came up at the same time router two would win

84
03:37.670 --> 03:38.480
because it has the

85
03:38.480 --> 03:42.210
higher priority. Now let's imagine that our one came up first it has a priority

86
03:42.210 --> 03:43.360
of 100 and then

87
03:43.360 --> 03:46.990
let's say a minute or two later we bring up interface gig one slash zero on our

88
03:46.990 --> 03:47.760
two and it has a

89
03:47.760 --> 03:52.270
higher priority by default with hsrp they don't preempt. Our two's not gonna

90
03:52.270 --> 03:53.520
say hey my priorities

91
03:53.520 --> 03:57.490
bigger and better so I should be the active router. However if we want to force

92
03:57.490 --> 03:58.640
that to happen there's

93
03:58.640 --> 04:02.130
also an option called preempt where basically says the router comes up with a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
03:58.640 --> 04:02.130
also an option called preempt where basically says the router comes up with a

94
04:02.130 --> 04:03.040
higher priority it's

95
04:03.040 --> 04:06.640
going to take over that responsibility and switch roles. So if we had a higher

96
04:06.640 --> 04:08.400
priority here of 101

97
04:08.400 --> 04:12.400
and a lower priority here of 100 gig one zero would be the active router that's

98
04:12.400 --> 04:13.360
supporting the virtual

99
04:13.360 --> 04:16.890
IP address and the virtual MAC address and the other interface here would be

100
04:16.890 --> 04:17.920
the standby and you

101
04:17.920 --> 04:22.060
can actually have two or three or four routers all in that common segment but

102
04:22.060 --> 04:23.120
you have one active

103
04:23.120 --> 04:26.870
one standby and the others are just waiting in the wings. It's also possible to

104
04:26.870 --> 04:27.600
set up multiple

105
04:27.600 --> 04:30.590
groups as well so for our demonstration and our discussion here we're just
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:27.600 --> 04:30.590
groups as well so for our demonstration and our discussion here we're just

106
04:30.590 --> 04:31.840
gonna use a single group.

107
04:31.840 --> 04:34.770
So if the actual group number doesn't matter if you're using group one or group

108
04:34.770 --> 04:36.080
10 or group 20

109
04:36.080 --> 04:39.150
as long as you're using the same group on both interfaces on that common

110
04:39.150 --> 04:41.040
segment. So let me go ahead

111
04:41.040 --> 04:44.860
and clean that up a little bit and let's talk about yet another option for a

112
04:44.860 --> 04:45.840
first hop redundancy

113
04:45.840 --> 04:50.680
protocol and that one is not a proprietary one it is an open standard and that

114
04:50.680 --> 04:52.960
is called vrrp and

115
04:52.960 --> 04:59.600
that acronym stands for the virtual router redundancy protocol. And as I

116
04:59.600 --> 05:00.640
mentioned it's an open
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
04:59.600 --> 05:00.640
mentioned it's an open

117
05:00.640 --> 05:03.850
standard so for running for example Cisco router and a non-sysco router but

118
05:03.850 --> 05:04.720
they both support

119
05:04.720 --> 05:09.440
vrrp we could use that as our first hop redundancy protocol. Now the way that v

120
05:09.440 --> 05:11.360
rrp works is amazing

121
05:11.360 --> 05:16.690
because it's virtually identical to how hsrp works. We have the concept of

122
05:16.690 --> 05:17.920
priority so far two has

123
05:17.920 --> 05:23.470
a priority of 101 and our one has a priority of 100 our two is going to be the

124
05:23.470 --> 05:24.320
active router except

125
05:24.320 --> 05:27.050
they don't call it the active router they call it the master and that master is

126
05:27.050 --> 05:27.760
in charge of the

127
05:27.760 --> 05:31.030
virtual IP address so the default gateway address would be dot 99 that's the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
05:27.760 --> 05:31.030
virtual IP address so the default gateway address would be dot 99 that's the

128
05:31.030 --> 05:32.000
virtual IP address

129
05:32.000 --> 05:35.280
and corresponding with that there also be a virtual MAC address associated with

130
05:35.280 --> 05:36.560
vrp as well

131
05:36.560 --> 05:40.920
that's mapped or associated with that dot 99 address. And so the master router

132
05:40.920 --> 05:41.360
is going to be

133
05:41.360 --> 05:45.490
responsible for responding to our requests for that address and responding with

134
05:45.490 --> 05:46.400
the virtual MAC

135
05:46.400 --> 05:49.850
address and then may responsible for actually providing that default gateway

136
05:49.850 --> 05:50.720
function for the

137
05:50.720 --> 05:54.030
benefit of the client. So if we clean this up a little bit and didn't use the

138
05:54.030 --> 05:54.880
words active and

139
05:54.880 --> 05:58.240
standby but instead we'll use the terms master and backup. So over here this

140
05:58.240 --> 05:59.520
will be the master

141
05:59.520 --> 06:03.390
responsible for responding to our requests for that dot 99 address and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
05:59.520 --> 06:03.390
responsible for responding to our requests for that dot 99 address and

142
06:03.390 --> 06:04.400
responding back with the

143
06:04.400 --> 06:07.970
appropriate layer two address associated with that default gateway address and

144
06:07.970 --> 06:08.880
over here are one

145
06:08.880 --> 06:12.300
and it's gig zero zero interface that would be the backup. And although there

146
06:12.300 --> 06:13.040
is the option of

147
06:13.040 --> 06:18.520
configuring preempt with vrp preempt is on by default. So what that means if we

148
06:18.520 --> 06:19.680
have r2

149
06:19.680 --> 06:24.740
with a priority of 101 and over here we have r1 it's gig zero zero interface

150
06:24.740 --> 06:25.760
with a priority of 100

151
06:25.760 --> 06:30.400
and we change this from 100 on r1 we set it to 102 for example preempt because
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
06:25.760 --> 06:30.400
and we change this from 100 on r1 we set it to 102 for example preempt because

152
06:30.400 --> 06:31.040
it's enabled by

153
06:31.040 --> 06:36.010
default that would cause r1 then to become the master and r2 on its gig one

154
06:36.010 --> 06:37.200
zero interface would

155
06:37.200 --> 06:42.560
then become the backup. But both hsrp and brp are going to have that virtual ip

156
06:42.560 --> 06:43.520
address for the

157
06:43.520 --> 06:47.790
router and an associated layer two address and whichever device is the active

158
06:47.790 --> 06:49.360
in the case of hsrp

159
06:49.360 --> 06:53.360
or the master in the case of vrp is going to be responsible for responding to

160
06:53.360 --> 06:54.000
our requests for

161
06:54.000 --> 06:57.580
that virtual ip address as well as providing the default gateway functionality

162
06:57.580 --> 06:58.160
for the client

163
06:58.160 --> 07:01.640
regarding that dot 99. So let's clean that up just a little bit and let's talk
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
06:58.160 --> 07:01.640
regarding that dot 99. So let's clean that up just a little bit and let's talk

164
07:01.640 --> 07:03.440
about one other

165
07:03.440 --> 07:10.640
fhrp and that is called GLBP and GLBP is an acronym for gateway load balancing

166
07:10.640 --> 07:12.800
protocol just like that.

167
07:12.800 --> 07:18.800
Now with GLBP we are going to have a virtual default gateway ip address and our

168
07:18.800 --> 07:19.440
example here we're

169
07:19.440 --> 07:24.720
going to use .99 again so it's going to be 10.12.0.99 that's going to be our

170
07:24.720 --> 07:26.480
gateway address however

171
07:26.480 --> 07:30.000
instead of just having one router do all the work it can actually load balance
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
07:30.000 --> 07:30.800
the traffic

173
07:30.800 --> 07:35.120
between the two routers that are supporting gateway load balancing protocol and

174
07:35.120 --> 07:35.520
you could have

175
07:35.520 --> 07:39.970
three or four or more routers all participating in that activity and here's how

176
07:39.970 --> 07:40.800
it works one of the

177
07:40.800 --> 07:45.090
routers the one of the highest priority is going to be the active virtual

178
07:45.090 --> 07:46.800
gateway. So in our example

179
07:46.800 --> 07:52.230
let's go ahead and use three routers let's say r1, r2 and r3 they're all

180
07:52.230 --> 07:53.360
connected to a common

181
07:53.360 --> 08:00.740
segment here and let's go ahead and say this is gig 0/1 this is gig 0/2 and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
07:53.360 --> 08:00.740
segment here and let's go ahead and say this is gig 0/1 this is gig 0/2 and

182
08:00.740 --> 08:02.400
this is gig 0/3.

183
08:02.400 --> 08:05.570
One of these routers the one with the highest priority is going to become the

184
08:05.570 --> 08:07.120
active virtual gateway

185
08:07.120 --> 08:10.970
and for the purposes of this example let's go ahead and say it's r1 that won

186
08:10.970 --> 08:12.480
that role and then r2

187
08:12.480 --> 08:16.160
and r3 if the active virtual gateway goes away they can have an election and

188
08:16.160 --> 08:16.720
determine who

189
08:16.720 --> 08:19.760
is going to take over that responsibility but for now let's imagine that r1 won

190
08:19.760 --> 08:20.240
the election

191
08:20.240 --> 08:24.750
it's the active virtual gateway now what exactly does that mean r1 gets to do

192
08:24.750 --> 08:25.600
well the active virtual

193
08:25.600 --> 08:29.320
gateway based on the message going back and forth in this common segment is

194
08:29.320 --> 08:30.240
going to identify
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

194
08:29.320 --> 08:30.240
going to identify

195
08:30.240 --> 08:34.910
that there are three routers involved here itself and also r2 and r3 and it's

196
08:34.910 --> 08:35.840
going to assign each

197
08:35.840 --> 08:41.480
of those routers as an active virtual forwarder so it's going to be here here

198
08:41.480 --> 08:42.480
and here meaning

199
08:42.480 --> 08:46.280
all three routers have the ability to forward traffic to support that default

200
08:46.280 --> 08:48.800
gateway address of 10.12.0.99

201
08:48.800 --> 08:53.010
and to facilitate the load balancing the active virtual gateway is going to

202
08:53.010 --> 08:54.160
give each of the

203
08:54.160 --> 08:58.640
active virtual forwarders a virtualized MAC address so down here I'll put MAC

204
08:58.640 --> 08:59.200
address

205
08:59.200 --> 09:03.860
and let's see the MAC address here on r1 the virtual MAC address is 1010 and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

205
08:59.200 --> 09:03.860
and let's see the MAC address here on r1 the virtual MAC address is 1010 and

206
09:03.860 --> 09:05.280
let's say for r2 the

207
09:05.280 --> 09:10.100
virtual MAC address is 1020 and on r3 let's say it's 1030 and let's just say

208
09:10.100 --> 09:11.280
that's the last four

209
09:11.280 --> 09:16.280
characters of its hexadessimal represented MAC address and then to actually

210
09:16.280 --> 09:17.280
make this picture

211
09:17.280 --> 09:20.280
completely let me add some clients I'm going to go ahead and put client one and

212
09:20.280 --> 09:21.440
I'll put down here

213
09:21.440 --> 09:26.790
client two and put down here client three so r1 is the active virtual gateway

214
09:26.790 --> 09:27.680
all three of them are

215
09:27.680 --> 09:30.950
active virtual forwarders and in their role as the active virtual forwarder
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

215
09:27.680 --> 09:30.950
active virtual forwarders and in their role as the active virtual forwarder

216
09:30.950 --> 09:32.000
they've been assigned

217
09:32.000 --> 09:35.680
from the active virtual gateway a virtualized MAC address they can use for that

218
09:35.680 --> 09:36.640
purpose so here's

219
09:36.640 --> 09:41.010
the magic when client one does an rp request looking for its layer two

220
09:41.010 --> 09:44.080
addresses default gateway of 10.12.0.99

221
09:44.080 --> 09:48.220
the active virtual gateway is going to respond back with one of the three

222
09:48.220 --> 09:49.520
addresses so let's imagine

223
09:49.520 --> 09:53.090
that client one when does rp request for its default gateway is responded back

224
09:53.090 --> 09:54.080
to you by the active virtual

225
09:54.080 --> 09:58.010
gateway with the MAC address any in 1010 that means that r1 would be providing

226
09:58.010 --> 09:58.960
that functionality the

227
09:58.960 --> 10:02.650
default gateway functionality for client one and then let's imagine client two
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

227
09:58.960 --> 10:02.650
default gateway functionality for client one and then let's imagine client two

228
10:02.650 --> 10:03.760
does an rp request for

229
10:03.760 --> 10:09.240
its default gateway of 10.12.0.99 and the active virtual gateway hears that rp

230
10:09.240 --> 10:10.240
request and responds

231
10:10.240 --> 10:14.180
back for this time it responds back with the MAC address of 1020 or the MAC

232
10:14.180 --> 10:16.080
address any in 1020 so

233
10:16.080 --> 10:20.550
C2 client two believes oh the layer two address for the default gateway address

234
10:20.550 --> 10:21.760
is when any in 1020

235
10:21.760 --> 10:25.580
and as a result r2 would be processing that because that's the active virtual

236
10:25.580 --> 10:26.560
forwarder that's

237
10:26.560 --> 10:30.030
managing that virtualized MAC address of 1020 and then third let's imagine that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

237
10:26.560 --> 10:30.030
managing that virtualized MAC address of 1020 and then third let's imagine that

238
10:30.030 --> 10:31.280
client three does an

239
10:31.280 --> 10:36.320
rp request for 10.12.0.99 and the active virtual gateway hears that request and

240
10:36.320 --> 10:36.880
responds back with

241
10:36.880 --> 10:40.360
the layer two addresses of 10.30 and then client three thinks oh the layer two

242
10:40.360 --> 10:41.360
address of my default

243
10:41.360 --> 10:45.470
gateway is when any in 10.30 and as a result it'll be r3 that's actually doing

244
10:45.470 --> 10:46.720
the forwarding for

245
10:46.720 --> 10:50.930
client three's traffic and that's how we can do load balancing across two or

246
10:50.930 --> 10:51.280
more

247
10:51.280 --> 10:56.800
devices that are using the first hop redundancy protocol named GLBP where with

248
10:56.800 --> 10:58.960
hsrp and vrp basically

249
10:58.960 --> 11:02.830
on one given subnet it's going to be one router that's either the active or the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

249
10:58.960 --> 11:02.830
on one given subnet it's going to be one router that's either the active or the

250
11:02.830 --> 11:03.680
master router

251
11:03.680 --> 11:07.330
and the other router or routers are simply waiting for that active or the

252
11:07.330 --> 11:08.960
master router to fail so they

253
11:08.960 --> 11:12.670
can take over the responsibility but here with gateway load balancing protocol

254
11:12.670 --> 11:13.520
we literally have

255
11:13.520 --> 11:17.220
the ability to do load balancing and with waiting we can also set up

256
11:17.220 --> 11:19.120
proportional load balancing so

257
11:19.120 --> 11:23.760
we could have for example you know r1 get twice as much traffic as r2 and have

258
11:23.760 --> 11:24.880
r3 get four times

259
11:24.880 --> 11:29.200
just much traffic for example as r1 but by default if we're using round robin

260
11:29.200 --> 11:30.400
and we have equal weights
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

260
11:29.200 --> 11:30.400
and we have equal weights

261
11:30.400 --> 11:34.240
it would be a round robin equal weighted distribution across all three of our

262
11:34.240 --> 11:36.000
routers as part of gateway

263
11:36.000 --> 11:40.380
load balancing protocol so now that we've taken a look at three options for

264
11:40.380 --> 11:41.200
providing fault

265
11:41.200 --> 11:46.350
tolerance here for pc12 with hsrp or vrp or with gateway load balancing

266
11:46.350 --> 11:47.760
protocol in the next video

267
11:47.760 --> 11:52.000
I'd like to start walking through the configuration of each of these and we'll

268
11:52.000 --> 11:53.760
start off with hsrp

269
11:53.760 --> 11:58.400
in the very next video. So I'll see you in that next video in just a moment.