WEBVTT

00:00:01.000 --> 00:00:07.000
So now, let's talk about VRRP, Virtual Router Redundancy Protocol.

00:00:07.000 --> 00:00:17.000
So, great news, VRRP and HSRP are very, very similar except for terms and some of the features that are on by default or off by default,

00:00:17.000 --> 00:00:27.000
which is fantastic because this gives you the opportunity to learn a lot about HSRP like you have today and then carry a lot of that knowledge over to VRRP.

00:00:27.000 --> 00:00:34.000
So, with VRRP, instead of using the terms active and standby, they use the terms master and backup.

00:00:34.000 --> 00:00:43.000
Notice there's no listener like we had with HSRP. So, with HSRP, active, standby, listener, whereas in this case you have master and backups.

00:00:43.000 --> 00:00:51.000
So, you could have one or more backups. So, if you had five routers and you wanted them all to be part of the same group, you'd have one master and the rest would all be backups in that case.

00:00:51.000 --> 00:00:58.000
So, router with the highest priority, forwards packets, responds to ARP requests, sends and receives hello packets, same thing as we discussed with HSRP.

00:00:58.000 --> 00:01:10.000
And then when it comes to the backup routers, router with second highest priority, third, fourth, fifth, sixth, in this particular case, sends and receives hello packets, waits for master to fail, so it can become the master.

00:01:10.000 --> 00:01:21.000
So, on Cisco routers, by default, you are technically using VRRP version number two by default.

00:01:21.000 --> 00:01:32.000
But we just refer to it as VRRP and VRRP version two only supports IPv4 networks, just like we talked about HSRP version one only supporting IPv4.

00:01:32.000 --> 00:01:36.000
To support IPv6, you got to do HSRP version number two.

00:01:36.000 --> 00:01:38.000
Okay, well, with VRRP, we're actually using version two.

00:01:38.000 --> 00:01:45.000
And if we want to use IPv6, we have to use VRRP version number three.

00:01:45.000 --> 00:01:47.000
All right.

00:01:47.000 --> 00:01:52.000
So, the command we would utilize in that particular case to change it, I'll type it in here.

00:01:53.000 --> 00:01:55.000
AFHRP.

00:01:55.000 --> 00:01:57.000
It would be in global configuration mode, actually.

00:01:57.000 --> 00:02:14.000
So, in global configuration mode, so config FHRP version VRRP v3 is what we'd use in Cisco IOS in order to use VRRP version number three.

00:02:15.000 --> 00:02:22.000
Preemption is also enabled by default with VRRP, so it's not something that you're going to have to configure.

00:02:22.000 --> 00:02:24.000
It's automatically on, and you really don't want to shut it off.

00:02:24.000 --> 00:02:30.000
So, when you look at the configuration for VRRP, it's very, very, very similar, except I don't have to do preemption.

00:02:30.000 --> 00:02:34.000
So, let's go ahead and do a live configuration here of this.

00:02:35.000 --> 00:02:43.000
And so, what we can do is let's type in interface VLAN 20 here.

00:02:43.000 --> 00:02:54.000
And in this case, let's remove standby 20 IP 10.0.2.254.

00:02:54.000 --> 00:02:57.000
So, I want no standby.

00:02:57.000 --> 00:03:02.000
So, do show run interface VLAN 20.

00:03:03.000 --> 00:03:04.000
All right.

00:03:04.000 --> 00:03:05.000
So, let's go ahead and do VLAN 20.

00:03:05.000 --> 00:03:10.000
So, we'll make this one the master, and we'll make this one the backup.

00:03:10.000 --> 00:03:11.000
So, that's what we'll do.

00:03:11.000 --> 00:03:16.000
So, this is the master, and this is going to be our backup for interface VLAN 20.

00:03:16.000 --> 00:03:17.000
So, DSW2.

00:03:20.000 --> 00:03:21.000
Let's do DSW1 first.

00:03:21.000 --> 00:03:24.000
So, we'll type in interface VLAN 20.

00:03:24.000 --> 00:03:35.000
We'll type in VRRP 20 with the IP address of 10.0.2.254, and then we'll type in VRRP.

00:03:35.000 --> 00:03:36.000
Oh, no.

00:03:36.000 --> 00:03:39.000
I'm going to leave this one as the lower priority.

00:03:39.000 --> 00:03:45.000
So, we're going to have DSW2 have the higher priority when it's all said and done.

00:03:45.000 --> 00:03:48.000
So, you'll see here that I'm the master right now.

00:03:48.000 --> 00:03:49.000
Why?

00:03:49.000 --> 00:03:50.000
Because I'm the only one.

00:03:50.000 --> 00:03:51.000
There's nobody else here to compete against me.

00:03:51.000 --> 00:03:53.000
So, let's go over to DSW2.

00:03:53.000 --> 00:04:02.000
We'll type in interface VLAN number 20, and we'll type in VRRP group number 20, and give it the IP of 10.0.2.254.

00:04:02.000 --> 00:04:04.000
And what's going to happen in this particular case?

00:04:04.000 --> 00:04:05.000
Let's see what happens.

00:04:05.000 --> 00:04:06.000
Okay.

00:04:06.000 --> 00:04:09.000
So, I give myself the backup status, but I promoted myself to master.

00:04:09.000 --> 00:04:11.000
Why?

00:04:11.000 --> 00:04:12.000
We have the same priority.

00:04:12.000 --> 00:04:13.000
Why did I promote myself to master?

00:04:13.000 --> 00:04:16.000
Same priority, but I have the higher IP address.

00:04:16.000 --> 00:04:17.000
Okay.

00:04:17.000 --> 00:04:21.000
So, there's a prime example of same priority, but a higher IP address.

00:04:22.000 --> 00:04:27.000
Remember, preemption is enabled by default here, so that's why we promoted ourself to master.

00:04:27.000 --> 00:04:35.000
So, I'm going to type in anyways VRRP 20, and then we're going to say our priority.

00:04:35.000 --> 00:04:37.000
Let's increase our priority anyways.

00:04:41.000 --> 00:04:48.000
One of the things about VRRP is that if you give yourself a priority of 255, you automatically become the master no matter what.

00:04:49.000 --> 00:04:51.000
Not a big gift for the exam, though.

00:04:56.000 --> 00:04:58.000
That makes sense, because you have the highest priority, right?

00:05:02.000 --> 00:05:03.000
So obvious.

00:05:04.000 --> 00:05:05.000
All right.

00:05:05.000 --> 00:05:09.000
What else do we want to talk about here when it comes to VRRP?

00:05:09.000 --> 00:05:11.000
So, we've covered priority.

00:05:11.000 --> 00:05:12.000
We've covered the IP address.

00:05:12.000 --> 00:05:16.000
Let's take a look at do show VRRP.

00:05:17.000 --> 00:05:18.000
So, what are we going to see here?

00:05:18.000 --> 00:05:19.000
We're going to see the virtual IP address.

00:05:19.000 --> 00:05:20.000
You're going to see the MAC address.

00:05:20.000 --> 00:05:21.000
So, there's the MAC address.

00:05:21.000 --> 00:05:36.000
I want you to remember, 00005E, and then 0001 for VRRP version 2, and then we have 14.

00:05:37.000 --> 00:05:39.000
So, 14 being the group number.

00:05:39.000 --> 00:05:43.000
So, remember, what group does this MAC address belong to?

00:05:43.000 --> 00:05:44.000
It's not 14.

00:05:45.000 --> 00:05:46.000
It's 20.

00:05:46.000 --> 00:05:49.000
So, you're going to have to do that conversion like I showed you with HSRP.

00:05:54.000 --> 00:05:55.000
All right.

00:05:55.000 --> 00:05:56.000
Let's take a peek at our notes here.

00:05:59.000 --> 00:06:01.000
Preemption is automatically enabled, as you can see.

00:06:03.000 --> 00:06:10.000
You'll see that our hello interval is one second by default with VRRP, whereas with HSRP it was three seconds.

00:06:10.000 --> 00:06:12.000
It's already faster.

00:06:13.000 --> 00:06:14.000
By default at one second.

00:06:19.000 --> 00:06:26.000
And you'll see that the down interval or the dead interval is 3.57 seconds.

00:06:26.000 --> 00:06:35.000
So, 3.57 times the actual hello, and that's legit.

00:06:35.000 --> 00:06:37.000
It's actually like 3.57.

00:06:37.000 --> 00:06:38.000
They round it to 3.6.

00:06:39.000 --> 00:06:40.000
So, 3.6 times the hello.

00:06:40.000 --> 00:06:45.000
It's actually 3.57 times the hello is your automatic down interval.

00:06:45.000 --> 00:06:52.000
So, if we set it to something like 2, then it would be 3.57 times 2 would be our down interval at that time.

00:06:52.000 --> 00:06:54.000
So, it automatically adjusts for you the down interval.

00:06:57.000 --> 00:07:00.000
So, what about interface tracking?

00:07:00.000 --> 00:07:09.000
So, when it comes to interface tracking with VRRP, it's going to be the exact same as we saw when I configured it for HSRP.

00:07:09.000 --> 00:07:17.000
So, we would have to create a tracking object and then attract the tracking object to VRRP.

00:07:17.000 --> 00:07:21.000
So, the command would be VRRP, then your group number, and then track.

00:07:21.000 --> 00:07:24.000
And then you can go ahead and attach your tracking object to it.

00:07:24.000 --> 00:07:28.000
So, let's say we have tracking object to seven, and then decrement your priority, but whatever you need.

00:07:28.000 --> 00:07:32.000
So, like I said, everything we learned about HSRP still applies here to VRRP.

00:07:37.000 --> 00:07:39.000
So, we'll take a look at our slides right now.

00:07:39.000 --> 00:07:43.000
And so, under normal conditions, this is how traffic, let's say, is flowing right now.

00:07:43.000 --> 00:07:50.000
If, let's say, DSW2 failed, well, then our backup is going to become our master at that particular point in time,

00:07:50.000 --> 00:07:52.000
and our traffic is going to automatically adjust that way.

00:07:52.000 --> 00:08:01.000
When everything goes back to normal on DSW2, then we're going to preempt and take over and become the master again,

00:08:01.000 --> 00:08:04.000
and DSW1 is going to become the backup, and we're going to failover.

00:08:04.000 --> 00:08:07.000
And, again, we send out a GARP, just like we do with HSRP.

00:08:07.000 --> 00:08:11.000
So, we send out that GARP, so that way there we can update the MAC address tables of our switches.

00:08:11.000 --> 00:08:17.000
So, if we go to somebody like ASW1 right now, we should see that ASW1 has the MAC address.

00:08:17.000 --> 00:08:26.000
ASW1 has the MAC address for that HSRP group.

00:08:26.000 --> 00:08:28.000
There it is.

00:08:35.000 --> 00:08:38.000
Oh, upstream interface tracking.

00:08:38.000 --> 00:08:40.000
What are we going to have to do?

00:08:40.000 --> 00:08:43.000
Create a tracking object like we did for HSRP.

00:08:43.000 --> 00:08:48.000
Create the tracking object, apply it to our VRRP group.

00:08:48.000 --> 00:08:55.000
So, just like we did with HSRP, though, we maybe want to track this interface and track this interface

00:08:55.000 --> 00:08:57.000
and maybe decrement this one by a certain value.

00:08:57.000 --> 00:08:58.000
So, what is our priority right now?

00:08:58.000 --> 00:09:03.000
I think our priority is a total of 200, and this one is 100 right now.

00:09:03.000 --> 00:09:07.000
So, maybe decrement this one by 51, decrement this one by 51.

00:09:07.000 --> 00:09:13.000
And so, that way there, if we lose both, then we'll fail over and use DSW1.

00:09:13.000 --> 00:09:19.000
But if only one of them fails, then we can continue using DSW2.

00:09:19.000 --> 00:09:24.000
In this example here, we'll see that our tracking object right now is up.

00:09:24.000 --> 00:09:32.000
So, since our tracking object is up, our traffic is flowing through DSW2.

00:09:32.000 --> 00:09:35.000
And we'll see right now that it's up.

00:09:35.000 --> 00:09:37.000
But if it goes down, we'll decrement by 200.

00:09:37.000 --> 00:09:39.000
So, our priority right now is 200.

00:09:39.000 --> 00:09:44.000
So, let's go ahead and bring down interface gigabit 1 size 0 size 14.

00:09:44.000 --> 00:09:50.000
And so, since that interface has gone down, tracking object has gone down.

00:09:50.000 --> 00:09:55.000
Therefore, we go back up, and DSW1 becomes our master.

00:09:55.000 --> 00:10:00.000
So, just like with HSRP, and if we look at this output now, we'll see that tracking object 5 is down,

00:10:00.000 --> 00:10:01.000
decrement 200.

00:10:01.000 --> 00:10:06.000
So, 200 configured minus 200 equals 0.

00:10:06.000 --> 00:10:08.000
So, all the same.

00:10:08.000 --> 00:10:10.000
And then what about further upstream?

00:10:10.000 --> 00:10:12.000
So, if we had a failure further upstream, it would be the same thing.

00:10:12.000 --> 00:10:14.000
You'd need an IPSLA.

00:10:14.000 --> 00:10:19.000
So, you set up your IPSLA instance, in this case a ping, set your frequencies, set your schedule,

00:10:19.000 --> 00:10:26.000
and then create your tracking object that is keeping track of that IPSLA instance,

00:10:27.000 --> 00:10:31.000
and then attach the tracking object to your VRRP command.

00:10:31.000 --> 00:10:36.000
So, in this particular example now, the SLA instance is down.

00:10:36.000 --> 00:10:43.000
So, because the SLA instance is down, that means that our tracking object is going to be down.

00:10:43.000 --> 00:10:48.000
And so, because the tracking object is down, we're going to decrement our priority.

00:10:48.000 --> 00:10:51.000
So, priority is now 0 because the tracking object is down.

00:10:51.000 --> 00:10:54.000
That's attached to the IPSLA instance.

00:10:54.000 --> 00:10:58.000
With VRRP, as I said, our timers are more aggressive by default.

00:10:58.000 --> 00:11:03.000
So, your timer is 1 automatically for the hello time.

00:11:03.000 --> 00:11:05.000
You can make the millisecond values as well.

00:11:05.000 --> 00:11:11.000
As you can see from here, VRRP 20 timers advertise milliseconds.

00:11:11.000 --> 00:11:21.000
And as we said, the dead timer is automatically going to adjust based on the hello timer that you specify.

00:11:21.000 --> 00:11:26.000
We said it's, what, 3.57 when it's all said and done?

00:11:26.000 --> 00:11:34.000
Rounds up to about, like, 3.6 times.

00:11:34.000 --> 00:11:37.000
And then also, forget about preemption.

00:11:37.000 --> 00:11:43.000
Preemption delay, I should say, is that, again, you don't want to take over as the master too early

00:11:43.000 --> 00:11:46.000
if the rest of the network's not converged yet.

00:11:46.000 --> 00:11:49.000
Because if the rest of the network's not converged and you take over as master

00:11:49.000 --> 00:11:52.000
and you start receiving traffic, then you might not be able to get where the traffic needs to go,

00:11:52.000 --> 00:11:54.000
and then you're going to have to drop it anyways.

00:11:54.000 --> 00:11:59.000
So, you're going to want to measure how long it takes for your network to converge under various situations

00:11:59.000 --> 00:12:07.000
and set a timer that is going to be appropriate for all situations combined.

00:12:07.000 --> 00:12:08.000
And then authentication.

00:12:08.000 --> 00:12:10.000
Let me check this device here.

00:12:10.000 --> 00:12:17.000
Authentication is something that has been available and then not been available for VRRP.

00:12:17.000 --> 00:12:18.000
That's right.

00:12:18.000 --> 00:12:19.000
That is true.

00:12:19.000 --> 00:12:20.000
Let's see if it is on this.

00:12:20.000 --> 00:12:21.000
Yes, it is.

00:12:21.000 --> 00:12:23.000
For this Cisco platform and device, it is.

00:12:23.000 --> 00:12:25.000
So, VRRP authentication.

00:12:25.000 --> 00:12:28.000
And you'll notice it's only plain text authentication.

00:12:28.000 --> 00:12:33.000
It's not MD5 authentication that is supported.

00:12:33.000 --> 00:12:37.000
And there are a lot of the RFC itself.

00:12:37.000 --> 00:12:44.000
Last time I checked, which was a while ago, but the RFC did not even include authentication as an option.

00:12:44.000 --> 00:12:50.000
And as a result of that, a lot of vendors don't actually offer authentication for VRRP.

00:12:50.000 --> 00:12:55.000
But Cisco does, and they only support plain text authentication on a lot of different products.

00:12:55.000 --> 00:12:59.000
So, just something to keep in mind that maybe your device, if it's a non-Cisco device,

00:12:59.000 --> 00:13:04.000
and it doesn't support authentication, it's because the RFC, the industry standard,

00:13:04.000 --> 00:13:07.000
does not recommend authentication for it.

00:13:07.000 --> 00:13:08.000
That was last time I checked.

00:13:08.000 --> 00:13:11.000
They might have an amendment or update it to it now,

00:13:11.000 --> 00:13:15.000
but that's not something that would probably show up the RFC information on the certification exam.

00:13:15.000 --> 00:13:20.000
But, you know, if they ask you to configure VRRP authentication on the certification exam,

00:13:20.000 --> 00:13:23.000
well, then obviously they're asking you to configure something that is supported.

00:13:23.000 --> 00:13:30.000
So, you would just go ahead and do it, and it would more than likely be plain text in that case.

00:13:30.000 --> 00:13:32.000
All right, folks, so that is our cover of VRRP.

00:13:32.000 --> 00:13:34.000
Very quick, a lot quicker than our HSRP discussion.

00:13:34.000 --> 00:13:37.000
But like I said, you already know everything.

00:13:37.000 --> 00:13:38.000
It's just now, what are the differences?

00:13:38.000 --> 00:13:41.000
So, you know the differences, as we've covered them here, so that way they're on the certification exam.

00:13:41.000 --> 00:13:45.000
You know the differences, and you'll be able to make decisions based on those differences.