So my first question is how did you do, how did you do with the labs?
I've discovered that the more we practice with hands-on and configuring and ver
ifying protocols and technologies,
the better we get at understanding them and the better we get at troubles
hooting when something goes south,
when something doesn't go quite right. So hopefully you had a good experience
in the lab,
and in this video, we're going to do a walkthrough of the three FHRP protocols,
starting with HSRP,
based on these parameters here, and then we'll replace that with VRRP, and then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
finally we'll
finish up with a walkthrough with Gateway Load Balancing Protocol. So with that
in mind,
let's head over to the lab environment. All right, so here we go. The first
thing I'm going to do
is bring up the lab topology here. It's also included as part of the skill. If
you want to download that
or put it on a separate screen, but I'm a visual person I always like to see
the topology,
just to make sure I'm on the right interface. So we're going to be dealing with
R1's Gig 00,
and R2's Gig 00 as they connect to that common network segment that supporting
the IP
dressing space of 10.12.0. So to get to the consoles, we're going to go ahead WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
dressing space of 10.12.0. So to get to the consoles, we're going to go ahead
and select server 1
nug, and then double click on it to open it up. I also took the liberty a few
minutes ago
of clicking on reset to reset the lab back to its defaults. So that's where we
're starting from
right now for this walkthrough. All right, so here is the terminal window, and
here is the
notepad document. Let me slide this over to the right, and I'm also going to go
ahead and make
this a little bit wider, just like that. All right, so for HSRP, here's our
configuration,
just as we did in the demos earlier. We're going to be defaulting the interface WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just as we did in the demos earlier. We're going to be defaulting the interface
, sitting up the
IP address, specifying standby version 2, the virtual IP address of .99, a
priority of 99,
and preempt all for group 1s. We'll copy that, go over to R1, paste it in, and
then we'll do similar
treatment for R2. So we'll grab R2's config, copy, go to R2, and paste it in.
Now for R2, because we
specified preempt and has a higher priority, it's going to in just a few
moments, it's going to be
the active router, and R1 will act as the standby. So there's the console WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the active router, and R1 will act as the standby. So there's the console
message right there,
seeing it's active, and let's say show standby. So currently with HSRP, this
router,
router 2 is going to act as the default gateway for PC12. So if we go to PC12,
we do a trace,
over to 4444, even as the first top is R2, and then R3, and then R4. However,
if we went to R2,
let's go to the right interface. So on R2, we went to gig 1 zero, and we shut
it down,
which we'll do right now. So we'll get a configuration mode, interface gig 1/0, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which we'll do right now. So we'll get a configuration mode, interface gig 1/0,
and we'll say shut down,
and press enter, and then give that just a moment. Once the other router R1
identifies, hey, there's no
hello messages coming from R2, it'll become active. So if we go to R1, and we
do a show standby,
and press enter, here showing that R1 is now active, it's now supporting the
virtual IP address,
it's also supporting the associated virtual MAC address. And then if we went
back to PC12,
and we did a trace again, in fact, before we do the trace, let me just take a
look at the cache,
show ARP, press center, and sure enough, it still believes that the MAC address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
show ARP, press center, and sure enough, it still believes that the MAC address
for the .99 address
still ends in F0, 0, 1, that hasn't changed, because R1 is now responsible for
that virtual address. So
we did a trace to 4444, the first top is now R1, who then forwards it to R3,
who then forwards it to
R4. And on R2, if we went back to intrace gig 1/0, when we did a no shutdown,
as it's converging,
if we do a show MAC address table on the switch, apparently it's showing that
MAC address table,
I already did it right there. There's the F0, 0, 1 associated with gig 0/2. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I already did it right there. There's the F0, 0, 1 associated with gig 0/2. So
it's already made
that change, and good R2, it's now the active router, it just shows standby,
just to confirm that,
and we went to PC12, we did that trace, the first top is once again, going to
be as shown right here.
All right, so that is HSRP, next let's go ahead and do VRRP. So I'm going to
take the configuration
for R1 copy, and it might complain about the duplicate address, because R2 is
still active for the .99 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
still active for the .99
address, that's okay. And then I'm going to go ahead and do the configuration
here for R2,
for VRRP, and right click copy that and get R2 and paste it in. And because R2
has a higher priority,
and preempt is enabled by default, R2 should act as the master, and then the
other device,
or rather one in this case, will act as the backup. So here on R2, we do a show
standby,
we're no longer running HSRP, so let's do a show VRRP, to show the VRRP
configuration. So this is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
configuration. So this is
the master device, there's the virtual IP address, there's the virtual Mac
ending in 0, 1, 0, 1.
And so if we went to PC12, and PC12 has a, let's do a show ARP, and it has the
old Mac address
for 99, that was from HSRP, so let's go ahead and do a clear ARP, give a nice
fresh start there,
and then without any entries in the Mac address table, here on the cache of PC
12,
let's go ahead and do a trace to 4444. So the first top is .2, then R3, R4. If
we go to R2,
and we go to interface gig 1/0, and we do a shutdown, that'll force R1 to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we go to interface gig 1/0, and we do a shutdown, that'll force R1 to
become the master,
so we can verify that we go into R1, we go to a show VRRP, press enter, and now
R1 is the master,
supporting that same virtual Mac address. So if we go back to PC12, and we do
another trace,
you notice that the first top is going through R1, and then R3 and R4, and so
we don't leave the
network broken, if we go back to R2 and do a no shut, the parameter will go
ahead and cause this
one to be the master again, and as a result, if we go back to PC12, and hit the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
one to be the master again, and as a result, if we go back to PC12, and hit the
up here,
key and do a trace again, now the first top is going to be .2 once again. All
right, so that is
VRRP, and our last option here is to go ahead and configure gateway load
balancing protocol.
So the syntax is GLBP, the group number, the virtual IP address, we'll set the
priorities,
and when they will preempt, and so let's go ahead and do R1 first, R1, right
click and paste,
and then we'll do R2, with the same commands we used in the demos earlier, so I
'll copy the settings
for R2, go over to R2, paste it in, and because preempt is enabled here, R2 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for R2, go over to R2, paste it in, and because preempt is enabled here, R2
should become the active virtual
gateway, and then the two active virtual forwarders will be R1 and R2. So here
in R2, we do a show GLBP
in percent, we are the AVG, and if we went over to R1, and we did a show GLBP,
R1 is the standby.
It also looks like we just stored out our forwarding as well. So let me go
ahead and do another show GLBP
here on R1, and I'll do also another show GLGP here on R2. So there's the
virtual IP address,
that the client's using is a default gateway. We have two group members, one of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that the client's using is a default gateway. We have two group members, one of
those is R2 itself,
that's the second entry, and the first one is R1. There's two forwarders, and
if we go down a little
bit and take a look at the details, forwarder one based on the IP address here
is 10, 12, 0, 1,
that's R1, supporting this virtual MAC address, and forwarder two is R2 itself.
So if we look at the
MAC address table on switch one, and do it, so we'll do a show MAC address
table. Here are the two
MAC addresses associated with gateway load balancing protocol. So the first
forwarder is R1, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
forwarder is R1,
that's reachable out GZR1, and the second forwarder is R2 reachable out of GZR/
2, and should be
shut down either of the interfaces. So let's go to PC12 here real quick, and
let's do a show ARP,
press enter, fantastic, let's do a trace to 4444, you know that's here that the
first top is .1,
and if we did a clear ARP, then we did that same trace again, with round rob
bing, the first top should
be R2. So it's just round robbing the active virtual gateway, just handing out
in a round robbing
fashion, the virtual MAC addresses associated with each of the forwarders. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
fashion, the virtual MAC addresses associated with each of the forwarders. So
if we were to go to
R1 for example, and on R1 let's go ahead and go into interface gig 0/0, and let
's shut it down,
and then let's go back to PC12, and let's clear the ARP cache, so we'll do a
clear ARP, let's go ahead and
do a trace, you'll notice it's using .2 as the first top, and actually behind
the scenes OSPF
is still converging because they shut down an interface. So let me go ahead and
give that just a moment.
In fact let's do a control C to break that, and let's go ahead and try that one
more time, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
more time,
and right there that was the process of OSPF converging, so OSPF is the little
link here, so if we do it
again, we do a trace, the first top is .2, and we do a show ARP, we're using 0/
0, 1 if we do a clear,
and then we did that same trace again, you know, so we're still using 2, but
check it out for you
to show ARP, it's now giving us the address of 0/0, 2. So we have R2, this
acting as the active virtual
gateway, responding to the ARP request, and it's still round robbing with the
virtual MAC addresses
of each of the forwarders, and because R1 is no longer available, R2 is also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of each of the forwarders, and because R1 is no longer available, R2 is also
doing the work of supporting
both those active virtual forwarding addresses. So if we get R2 into a show GLB
P in press center,
it's going to be active for forwarder 1 with that first MAC address, it's also
active for forwarder 2
with that MAC address, and if we flip the roles, for example, we go back to R1,
we do a no shut,
and give that a moment for it to come up, and then if we go to R2, and R2, we
go to config T,
interface gig 1/0, and then we do a shut down, and then I'm also going to give WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
interface gig 1/0, and then we do a shut down, and then I'm also going to give
OSPF a moment to
converge as well, and let's confirm what we just did. We just said to R1 on its
gig 0/0, come on up,
and we just told R2 to gig 1/0 to go ahead and shut down. So as a result, what
should happen is
R1 will now be the active virtual gateway, it'll also perform the role for both
active virtual forwarders.
So if we go back to R1 real quick, and we do a show GLBP in press center, it is
for forwarding
for forwarding group 1, it's active, if we go down a little bit, it's also
active for forwarder 2,
something to go back to PC 12, and let's go ahead and do a clear ARP, and let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
something to go back to PC 12, and let's go ahead and do a clear ARP, and let's
do a trace to 4444,
it's using the first hop of router 1, and if we do a clear ARP, and then go
ahead and do a trace once
again, once again it's using .1, but check it out if we do a show ARP, and the
ARP cache is now using
the second MAC address for the second forwarder. And that's because R1 is doing
all the work,
it's the active virtual gateway, it's responding with answers for the ARP
request, and it's round
robbing between the two virtual MAC addresses, one from forwarder 1, and one
from forwarder 2,
and at this moment it's responsible for both of those because R2 is no longer WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and at this moment it's responsible for both of those because R2 is no longer
responding.
And if we brought R2 back with a no shutdown, and we gave it a few moments
because it has a higher
priority, it's going to become the active virtual gateway, and then as we start
going back to PC 12,
and we do a clear ARP for example, let's do a ping to 4444, and a show ARP, it
was using the MAC
address ending in 0101, let's do a clear ARP, then once again we'll do a ping
to 4444,
and we'll do a show ARP, and now it's using 0102. And because we're now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we'll do a show ARP, and now it's using 0102. And because we're now
dividing the load
between R1 and R2, if we do a trace to 4444, it's using R2 as the first top,
and then if we do a clear
ARP to simulate doing a ARP request for that .99 again, we'll do a trace again,
and this time our
first top is .1, because if we do a show ARP, the layer 2 address that we were
sent back in the ARP
response was 0101. Also just to help reinforce this, I did a quick caption in
the background regarding
four messages related to ARP. Now the first one is a client, this is PC 12, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
four messages related to ARP. Now the first one is a client, this is PC 12,
that's doing an
ARP request saying hey I need the layer 2 address for 10, 12, 0, 99, please let
me know. So if
we look at the details for that, here's the request, and the first response
that's coming back
from the active virtual gateway is the MAC address of 0, 0, 0, 0, 7, B4, 0, 0,
0, 0, 0, 0, 0, 2,
then I cleared the cache on that machine, and it did another request to reach a
remote network,
so I did another ARP request, and this time I responded back with the MAC
address of 0, 1, 0, 1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
address of 0, 1, 0, 1.
So the initial response had 0, 1, 0, 2, and then the second response had 0, 1,
0, 1. And that's how the
active virtual gateway is providing load balancing by responding to the ARP
requests with the virtual
MAC addresses for the various forwarders associated with GLBP. So thank you for
joining me in this set of
videos regarding first hop, redundancy protocols, and I look forward to seeing
you my friend in another
set of videos in the very near future. Until then, I hope this has been
informative, and I'd like to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
informative, and I'd like to
thank you for viewing.