In the previous video we configured HSRP, a proprietary first hopper density
protocol from Cisco,
and in this video we're going to focus on the configuration verification of VR
RP, which is an
open standard. Now, the actual logic is very, very similar between VRRP and HS
RP, including we
are going to use group numbers for VRRP. We are going to have priorities that
are used to determine
which is going to be the master and which is going to be the backup. And we
also have the concept
of preempt. Now, by default, the preempt option is on with VRRP. So if you want WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of preempt. Now, by default, the preempt option is on with VRRP. So if you want
to turn it off,
you can, but preempt is on by default. That means if gig 1, 0 is configured for
VRRP with a
priority of 102, and then we configured our one with a priority of 103, because
preempt is on by
default, our one would assume the role of the master and the gig 1, 0 interface
here over on R2
would become the backup. And the syntax for implementing VRRP is virtually
identical to how we would
implement HSRP except we're going to use the keyword VRRP instead of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
implement HSRP except we're going to use the keyword VRRP instead of the
keyword standby. So with that
in mind, let's head back to the lab and let's remove the configurations on gig
0, 0 here and on
gig 1, 0 here on R2. And let's replace them with fresh IP addresses and then we
'll also add VRRP
on top of it. And then once that's done, we can test it from PC12. And here we
go. So let's go to R1
first and in my notepad document, I'm going to scroll down to the VRRP section,
which is right here.
So in R1, we're going to go into configuration mode and default the interface WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in R1, we're going to go into configuration mode and default the interface
gig 0, 0 is just
to wipe out anything that was there. And then we'll go into interface config,
put back its IP
address of 10, 12, 0, 1. And then we're going to use VRRP group 1, specify the
IP address of 10,
12, 0, 99, and also a priority of 99 for that group for the interface over on R
1. And then for
R2, similar treatment, except we'll go to the appropriate interface of gig 1, 0
on R2,
and then put back its IP address of 10, 12, 0, 2, and then set up VRRP group 1
with the same virtual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with the same virtual
IP address. But this time we're going to give a priority of 105. So the default
priority is 100,
so 105 will be higher than the default. It'll also be higher than R1. And
because preempt is on
by default, once we configure R2, it should take over the master role. So to
start off, let's go ahead
and copy the config here for R1. We'll copy that into my buffer, go to the
right router, which is R1.
We'll paste that in and then we'll give it a moment. Oh, and here it has a
duplicate address
in this because R2 is still acting as the, as the, it's just RP router over WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in this because R2 is still acting as the, as the, it's just RP router over
there for its interface,
gig 1, 0. So let's actually go over to R2 and let me just default the interface
for gig 1, 0,
over on R2. And that way it won't complain. So we'll go to R2 right click. We
'll default the interface
fantastic. And then we'll go back to R1 and I'm going to put R1's configuration
back in. So right click
copy, go to R1, paste it in. And here we go. So VRP is going from init to
backup. And then it went
from backup to master as shown right there. So if we do a show, VRP and press WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
from backup to master as shown right there. So if we do a show, VRP and press
enter is showing that
this router, router one is currently the master. There's the virtual IP address
. There's the virtual
MAC address, ending in 010. Preemptions enabled by default. There's the
priority that we manually set.
And the master router is 10.12.0.1. That's us. That's R1's interface address.
And its priority is 99.
So if we were to go back to PC12 and here on PC12's do a show, ARP. So if we
look at the ARP
cache, it has the correct MAC address. So that's timing out. But will we also
just do a nice clean slate,
we could do a clear ARP, press enter. And then let's do a show, ARP just to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we could do a clear ARP, press enter. And then let's do a show, ARP just to
verify the ARP
cache is empty. And let's say ping to 4.4.4.4. Now before we press enter, that
should cause PC12
to realize, oh, I'm trying to reach a network that's not local. I need to know
the layer 2
address of my default gateway, which is .99. So I can go ahead and learn the
layer 2 address for that.
And then forward the frame at layer 2 to my default gateway. And then my
default gateway can make
a routing decision. So at the moment, R1 is the only router configured with VRP
to support
that IP address. And that is working great. And if we go back to the switch and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that IP address. And that is working great. And if we go back to the switch and
here on the switch,
if we do a show MAC address table, there's that address ending in 0101 that's
associated with port
gig 01. And that's the connection that goes down to R1. Now let's go ahead and
configure R2.
It's gig 1 0 when we're placing when we do that. And when we give it a higher
priority, it will
then become the master router for the segment. And the switch should believe
that same MAC address
ending in 0101 is reachable off gig 02. And that's because R2 when it becomes
the master
in gig 1 0 is going to send some frames into the network. And the source WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in gig 1 0 is going to send some frames into the network. And the source
addresses are going to
have that layer 2 address ending in 0101. So let's go to R2. Let's go to our
text document. And here's
what we'll configure. We're going to default the interface, give it its IP
address back, and then
set up the virtual IP address of 10.12.0.99. And set up a priority that's 105.
So we'll copy that,
put it in my buffer. We'll go to R2, right click, and away we go. All right, so
it went from
a knit to backup. It should go from backup to master right there. And now R2 is
the master router for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the master router for
VRRP group number one. So if we did a show VRRP here in press dinner, here
shows the state is master,
there's our virtual IP address, there's the virtual MAC address. And here it
confirms that the
master router is 10.12.02. That's us locally. And our priority is 105. So if we
went back to the
switch and this confirm what port we're connected to. So R2 on its gig 1 0
interfaces connected to
gig 0 slash 2 on the switch. So if we went into the switch and hit the up your
key into the show
MAC address table, check it out. That MAC address ending in 0101 is now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
MAC address table, check it out. That MAC address ending in 0101 is now
associated with gig 0 slash 2.
So if we went back to PC 12 and still a quick show ARP. So it still believes
the MAC address associated
with default gateway is 0101. That's great, great, great. So let's do a ping to
4.4.4.4. No worries.
And that's R2 that's providing that default gateway functionality. So if we did
a trace to 4.4.4.4,
that would confirm our first top is R2 and then R3 and then onto R4. So if we
went to R2 and let's
confirm the interface we're dealing with. So on R2, if we shut down gig 1 slash WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
confirm the interface we're dealing with. So on R2, if we shut down gig 1 slash
0. So we'll do that.
We'll go into configuration mode, interface gig 1 slash 0. And let's say shut
down and press center.
Or we're going to lose the OSPF neighbor ship. But check this out. If you go
back to PC 12,
it still has, if we look at the ARP cache here, it still believes that .99 is
associated with that
same layer to address. But this time it's going to be R1 that's supporting it.
So if we go to R1
and we do a show and right there it has the VRRP message went from backup to
master. So we do a show
VRRP in press center. It's now showing that router 1 is the master along with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
VRRP in press center. It's now showing that router 1 is the master along with
the virtual IP address
and the virtual MAC. And if we go back to the switch and we get the up arrow
key, a moment ago,
this MAC address was associated with gig 0 slash 2 going over to R2. But now if
we do a show
MAC address table, that MAC address is now associated with gig 0 slash 1, which
goes down to R1. And if we
go to PC 12 and we try to ping, for example, to 4.4.4.4 just to verify
connectivity. And then
furthermore, let's do a trace to 4444. So earlier we did it and the first top WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
furthermore, let's do a trace to 4444. So earlier we did it and the first top
was R2. And now if we do
that same trace, now the first top is R1. Based on that last octet, then going
to R3, then going to R4.
And we're going to get rid of the port unreachable message. We can do a dash
capital P space
protocol 1 and then we'd use ICMP, but the path is going to be the same. Going
from R1 to R3 to R4.
And because I don't want to leave the network broken, let me go back to R2 and
we'll do a no shutdown.
And then once that comes up, it'll form the OSPMFJs and C. It'll become the
master for the segment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
master for the segment
regarding VRP. And once again, we go back to our client, which is PC 12. And we
hit the up arrow key
and do a trace to 4444 press center. The first top is now R2 and then goes to R
3 and then to R4.
So so far, so great. We've now configured HSRP and verified it. We've
configured VRP and verified it.
And in the next video, I'd like to walk you through the configuration and
verification
of Gateway Load Balancing Protocol. So I'll see you there in just a moment.