In this video, we're going to put a game plan together for the implementation
of HSRP.
And we're going to use gig 00 here on R1 and gig 1 0 here on R2 to support that
fault tolerance
for the benefit of our client here PC12, which is expecting to have a default
gateway at 10.12.0.9 U9.
So as far as our game plan, let's go ahead for HSRP and let's use group number
one.
And that's just a number we'd pick out of the air. So as long as the two
interfaces are believing
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
and agreeing on using the same group, we're good to go. So we use group number
one.
And let's also use version two of HSRP. And let's also go ahead and enable pre
empt.
And that way the interface has the highest priority at any given moment. If
they're both up,
that will become the active router in HSRP. So we'll enable preempt. And then
on R1,
let's go ahead and set the priority. The default is 100. But on R1, let's go
ahead and set it
to 99 just below the default. And then on R2, on its gig 1 0 interface, let's
set the priority
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
to 105. And then to test it, we can go to PC12 here. And it should be able to
use this default gateway
of .99 to go ahead and reach some other resource. So over here on R4, there's a
loopback interface
of 4.4.4.4.4. And all the routing is set up already in this environment. So as
a test, we could ping
from PC12 over to 4444. This is a validation that we can get off of our local
subnet.
As far as testing goes, if R2's gig 1 0 was the active router, and over here R1
was a standby,
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
if we shut down this interface on R2 gig 1 0, we should be able to still be
able to reach
remote networks on PC12 because R1, which was the backup router, would become
the active router,
once it identified that it can no longer communicate or reach over here to R2's
gig 1 0 interface.
And again, that's the goal. To have first hop, the first hop for a client, like
their default gateway,
to have fault tolerance and redundancy. And that's what we're doing here with
HSRP. So with this
game plan in mind, let's go to the lab environment and let's configure HSRP on
R1's gig 0 0 and on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
R1's gig 0 0 and on
R2's gig 1 0 for the benefit of PC12. All right. So here in the lab environment
, and at the tail end
of the set of videos, I'll give you a chance as well to get hands on practice
with setting up FHRP.
So here, let me go ahead and double click on the lab topology image here. That
looks good. Let
me go ahead and scoosh that over just a little bit. And then on server one
right here, this is how we
get to the console access for all of these devices, the four routers, the
switch, and also our virtual PCs.
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
So we'll go ahead and double click here on server one nugged to open that up.
We'll give that a
moment or two to initialize. And here it comes. Fantastic. Here are the tabs
for R1, R2, R3, R4,
switch one, PC12, PC20, and PC30. Also, I have here on the desktop of the
server one computer. I've got a
document called FHRP useful commands. It's open right here. And if you want to
leverage that and refer
to the commands or do some copying, pasting what you're comfortable with the
commands, that's all well
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
and good. So here is the notepad document to the right. And I'll just click on
the taskbar here for
multi tab putty and get access to our consoles. In fact, I'm going to go ahead
and scoots this over
a little bit more. Fantastic. So I can see both at the same time. So here's the
syntax for HSRP.
We go into the interface and you specify the version of HSRP we want to use. So
the command that we're
going to use to both configure and also to view HSRP is the command standby. So
we'll go into
interface config and let's make sure we have the right interface here. This can
be gig 000 here on
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
R1. And on gig 00, we're going to say standby space version two as opposed to
version one. That way
we're using version two. Then we're going to say standby group one and specify
the virtual IP address.
That'll be the default gateway the client's going to use and then we can
specify standby the group
number, the keyword priority and then the actual priority we want to give
itself. We want R1 to have
a priority of 99 instead of the default priority of 100 with some of these
command right there.
And if we want to enable preempt, we'd also do that for that same group standby
one preempt. So in the lab
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
what I'm going to do is I'm going to go ahead and go into configuration mode. I
'm going to default
interface gig 00. And what that's going to do is going to wipe out whatever is
there previously
because we're not only going to configure HSRP, we're also going to configure
VRRP and also GLBP.
So I just want to wipe them out each time just to make sure we have nice fresh
start.
So I'm going to take R1's config here and when you do the lab at the tail end
of the set of videos,
I would encourage you to do a couple of times just do it manually. Make sure
you're comfortable with
the commands and then once you've done it a few times, you can use the note pad
document as a review
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
or if you want to copy paste, you're welcome to that as well. So we'll take the
config for R1,
we'll go to the R1 tab, we'll right click and paste and we've just defaulted
the interface.
I put the IP address back at 10.12.0.1 for R1 and then I use these commands
right here to
implement HSRP on that interface gig 00. So now that we have that set up, we
should have
effectively a default gateway that R1 is now providing that PC12 can now use.
So if we go to PC12
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
and on PC12, if we do a show IP, it'll show us the IP address it has of 10.12.0
.51, fantastic.
And it also shows here the default gateway and I just did a copy paste of
standby version 2,
which means nothing to this little PC. So here is the default gateway and so if
you do the ping here
to 10.12.0.99, we should get a response and there it is. That response is
coming back from R1.
It's the only device there running HSRP and if we go back to R1 and we do the
show standby and press
enter, here it's showing that this is our one. It is currently active as
opposed to standby. The virtual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
opposed to standby. The virtual
IP address is 10.12.0.99. The virtual MAC address is this one ending in F001
and so this character
here, the one, the zero one is representing the actual group number. So if we
use group 2,
that would show up as a two. It shows here that preemption is enabled. The
active router is local,
standby router is unknown. That's because we haven't configured R2 yet and the
priority is 99.
And here is the actual group name. It's a combination of HSRP and the
identifier for the interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
identifier for the interface.
You can also name the group if you want but by default it's going to use this
syntax. So if we
look for this MAC address ending in F001, let's go to the switch and here on
the switch and this
take a look at our topology real quick. So if we're looking at this switch one
and on the switch,
we do a show MAC address table and press enter, you'll notice that it has that
MAC address associated
with gig 0/1 and that port happens to be where our one's gig 0, 0 interface is
connected right there.
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
So our next step is then to go ahead and add the real fault tolerance by also
configuring gig 1,0
over on R2 with the parameters that we planned on. So if we go to R2, then we
go to our notepad document.
On R2, we'll go into configuration mode, we'll set interase gig 1,0 to its
defaults,
we'll give it an IP address of 10.12.0.2 and then we'll issue the standby
commands,
specifying version 2, the virtual IP address for group 1 being 10.12.0.99 and a
priority of 105
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
and we'll also enable preempt. So we'll go ahead and put that on R2 right now.
So I'll copy that
and now with that in my buffer, we'll go to R2 and right click and paste. So we
should lose the
neighbor adjacency with OSPF and then it should come back because we removed
the IP address and now it's
going through the HSRP state change of from listening to active as shown right
here. And that's
because it had a higher priority. So if we were to do this, show standby now.
In price center,
here's showing that this router R2 is active. Here's the virtual IP address.
Here's the virtual MAC
address associated with that .99 address. Preemption is enabled. The active WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
address associated with that .99 address. Preemption is enabled. The active
router is local, meaning on R2
and the standby router is over at 10.12.0.1. That's R1. And the reason that we
are active and the other
guy standby is because our priority is 105 preempt is enabled and the other
router has a priority of 99.
So if we looked at the topology. So if we went back to the switch and we asked
to switch the show
to its MAC address table, it would now associate that MAC address ending in F00
1 with gig 02, which
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
leads over to R2's gig 1 0. That's because R2 on its gig 1 0 interface is now
the active router.
So if we go up to switch one and here on switch one, we hit the upper key and
show MAC address
table. Notice previously, F001 was associated with gig 01 and now F001 is
associated with gig 02.
So if we were to go back to our PC PC 12 and if we were going to ping something
like 4.4.4.4,
which is the loop back interface on R4, no problem. And if we do a show app, it
'll show us the
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
ARP cache. And there's the ARP cache that we currently have for the 10.12.0.99
address, our default
gateway. And that's the MAC address ending in F001. So because 2 is the active
router, as shown
right here with the output of show standby, what would happen if we went to
interface gig 1/0
and we said shut down. So that's now shut down R1 can no longer see the hello
message during
the else coming over from R2 regarding HSRP. So if we go back to R1 and we look
at the console
message here, it went from speak to standby. And in a moment, it's going to go
from standby to active.
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
And now it's the active router. So we do a show standby here on router 1 is
showing the status
active. Here's the virtual IP address we're supporting as the default gateway
address for our
clients. There's the associated there to MAC address and the active router is
local. And the
standby router is unknown. And that's because we have no idea where the standby
router is because
at the moment our 2's gig 1/0 interface is shut down and no longer
communicating.
So the benefit of this is we go back to PC12 and let's do a show ARP. So the AR
P cache is still there,
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
still showing F001 for its default gateway address. So we did a ping to 4.4.4.4
press center.
That still works. No problem because we still have one or two routers that are
part of the
HSRP pair that's still providing that default gateway functionality. And this
time it's R1. So we
did a trace to 4.4.4.4. And we looked at the path. In fact, let's do a trace
and we'll do a
dash capital P1 for using ICMP. And that way we don't have the destination port
and reachable message.
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
The first hop is router 1. Then it's going to router 3. And then it's going to
router 4. So if we
look at our topology, that'd be from PC12 down to R1 over the serial interface
to R3. And then from
R3 up to R4. And we went back to R2. And here on R2 because it was preemptive
to enable if we did a
no shutdown. That's going to bring up the interface. We'll let it have a moment
. So OSPF can do its
convergence. So now that we've given that a moment, if we do a show stand by
and press center,
here on router 2, it's now showing as active. And if we go back to our client,
which is PC12,
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
and we did a trace again, you'll notice now it's going through router 2 and
then down to router 3
and down to router 4. And the path is different because a different router is
providing the functionality
of the default gateway. So now that we've taken a look at the configuration and
verification of HSRP
in the next video, let's go ahead and do the same technique except using VRRP,
the OpenStandard,
for first hopper dynasty protocols. So when you're ready, I'll see you there in
just a moment.