All right, my friend.
It is time to take it up another notch by adding
routing protocols that are specific to a VRF.
Now, in preparation for this, I realized there's like--
not eleventy billion ways to do this.
But there are many different ways
of doing this, because we have EIGRP
in named mode, which supports address families that we could
use.
And that would work.
We have OSPF version 3.
And we have address families in that hat we could use.
Or we could use the legacy methods for OSPF and/or EIGRP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Or we could use the legacy methods for OSPF and/or EIGRP.
And any one of those options could work.
So in this video, what I'd like to do
is walk you through a fairly traditional way
of doing OSPF routing, like router OSPF and a process ID.
But-- but we'll tag on the additional option regarding
which VRF this is for, and that we
can have two separate routing processes--
one for VRF purple, one for VRF green.
And we can use those to neighbor up with those customer edges.
So with that in mind, let's take a look at the topology. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So with that in mind, let's take a look at the topology.
And let's set up dynamic routing protocols with VRFs.
And as a little bonus, I have reset the lab.
That'll give you another opportunity
to implement the VRFs in the appropriate interfaces.
And if you want to use the VRF definition with the address
families, or if you want to use the IPv4 only version--
either way is great.
We've had practice with both in the previous lab.
So you can use whichever method you choose here.
They'll both work great.
So with R4, I'm going to create the VRFs,
because they don't exist.
Show VRF.
So, we'll go into configuration mode, VRF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, we'll go into configuration mode, VRF.
And I'm going to use the IPv4 only.
IP VRF and let's say green.
IP VRF purple.
Why doesn't it auto-complete this name I'm making up?
Because it's a name I'm making up.
And then we'll allocate the interfaces
to show IP interface brief.
So gig 0-- gig 1/0 is for green.
And gig 2/0 is for purple.
We'll go into interface gig 1/0.
And because I'm using IPv4, it's going to be IP VRF forwarding. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And because I'm using IPv4, it's going to be IP VRF forwarding.
And I'll say green.
And I'll put on the IP address.
It's right here.
Boom.
And the mask And interface gig 2/0.
And we'll put on the VRF.
IP VRF forwarding for purple.
And we'll put on the IP address, which is 172.16.4,
which is that interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is that interface.
Done.
So let's set up the routing protocols.
And what we'll do is a router, OSPF 1--
the traditional flavor of OSPF, instead of
OSPF version 3 or named EIGRP.
All that supports it, by the way.
And then we'll use a question mark and check this out.
We want this routing process--
routing process OSPF 1--
to be associated with VRF green.
Just like that.
Oh, surprise, Keith. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Oh, surprise, Keith.
I see a do show IP protocols.
I already have--
I already have OSPF running in my network.
And it says, that OSPF process was already for the default
routing table, not for green.
So I should have--
I should have looked to see what routing protocols were running.
So let's do this.
Let's do a router OSPF 2 for our good friend Mr. Green.
Aye-aye.
And we'll add all the networks in--
so, 0,0,0,0-- too many zeros. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
so, 0,0,0,0-- too many zeros.
And a wild card mass saying, everybody comes in.
And we'll put them in area 0.
So this is going to be OSPF process 2.
And then, if we go into router OSPF 3 for VRF purple--
and we'll do the same thing.
We'll bring everybody in there.
Now if we do a show IP OSPF interface brief--
and this is kind of interesting, because this interface right
here, even though it shows up--
that interface and its routing process--
process 2-- are associated with VRF green. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
process 2-- are associated with VRF green.
And this guy right here-- gig 2/0--
is associated with VRF purple.
And I'm not getting any neighborships.
And let's talk about why that is.
Because my customer edges are not
running any routing protocols yet.
So let's run OSPF normally on them.
They don't know anything about the VRFs
that are happening at the provider edge.
Let's go ahead and run routing protocols on customer one site
2, a customer two site 2.
Let's do it.
So we'll go back to our lab.
And we'll go to customer two, site 2-- that's this guy. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we'll go to customer two, site 2-- that's this guy.
Router OSPF 1, network everything.
So that last set of all zeros--
if you do a do show IP protocols,
it flips them for us.
Just saves you from typing 255s a few more times.
So the wildcard bits are all on.
Our neighborship came up great.
And we'll go to customer two, site 2,
and we'll do the same thing.
WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the customer edges don't know anything about this VRF game
that's being played on the provider edge.
However, we have full adjacencies on both devices.
So if we go back to R4, and we do a show IP OSPF neighbor,
it's going to show us neighborships.
So there's the router IDs of the two customer edges.
And if you do a show IP route for VRF green,
we have the 33 33 loopback address.
And if we show IP rate for VRF purple, perp-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we show IP rate for VRF purple, perp--
purple-- there that is.
Also, if we wanted to do a ping--
we could do a ping VRF as purple to 44 dot 44 dot 44 dot 44.
That should be successful, because we've learned it
via OSPF as part of that VRF.
And we're sourcing the ping from that VRF.
So one of the challenges and opportunities
when you're working with VRFs is just
to be aware about what routes are in those VRFs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to be aware about what routes are in those VRFs.
And if you're doing a ping or something else like that--
or a trace route-- you want make sure you
do it VRF specific-- that you're sourcing it
from that VRF, which has the routes, then,
to make a forwarding decision and send packets on its way.
In this set of videos, we've had the opportunity
to do three basic things.
One, we've talked about the benefits of using VRFs--
like a little mini me version of a routing table inside
of a router, with its own routes,
its own interfaces you assign to it keep routes isolated.
Secondly, we looked at several different ways WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Secondly, we looked at several different ways
of configuring VRFs--
one that supports IPv4 only, and one the
supports address families with IPv4 and IPv6.
And then third, we identified how
we could use routing protocols that
are specific to a VRF you dynamically neighbor up
with other devices.
And those routes that come in would be associated
with the respective VRFs.
And in addition, we also had the opportunity
to do hands on practice to reinforce those concepts.
So thanks for joining me in this set of videos.
I'll see you in the next group.
Meanwhile, I hope this has been informative for you, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.