WEBVTT

1
00:00.000 --> 00:01.260 align:middle line:84%


2
00:01.260 --> 00:02.290 align:middle line:84%
Hey, welcome back.

3
00:02.290 --> 00:03.870 align:middle line:90%
In the previous
video, we identified

4
00:03.870 --> 00:06.240 align:middle line:90%
that on a Cisco
router, we can create

5
00:06.240 --> 00:08.970 align:middle line:90%
logical separate
routing tables which

6
00:08.970 --> 00:11.820 align:middle line:90%
are VRFs, virtual routing
and forwarding instances,

7
00:11.820 --> 00:15.030 align:middle line:90%
and then we can assign
interfaces to that VRF.

8
00:15.030 --> 00:18.210 align:middle line:90%
And when we do, we get a new
directly connected route inside

9
00:18.210 --> 00:19.170 align:middle line:84%
of that VRF.

10
00:19.170 --> 00:20.910 align:middle line:90%
Now what I like to
do in this video

11
00:20.910 --> 00:23.833 align:middle line:90%
is talk with you about
two different options.

12
00:23.833 --> 00:25.500 align:middle line:90%
Not my fault, don't
shoot the messenger.

13
00:25.500 --> 00:28.590 align:middle line:90%
But two different options
for creating a VRF

14
00:28.590 --> 00:29.820 align:middle line:84%
on a Cisco router.

15
00:29.820 --> 00:32.130 align:middle line:90%
And also the syntax
to take an interface
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:29.820 --> 00:32.130 align:middle line:90%
And also the syntax
to take an interface

16
00:32.130 --> 00:34.650 align:middle line:84%
and say, you belong to this VRF.

17
00:34.650 --> 00:36.120 align:middle line:90%
And with fear of
light, because we

18
00:36.120 --> 00:39.060 align:middle line:90%
don't have to worry about
layer 3 VPNs or MPLs,

19
00:39.060 --> 00:42.150 align:middle line:90%
it's really just basically
a 2-step process.

20
00:42.150 --> 00:44.220 align:middle line:84%
We want to create the VRF.

21
00:44.220 --> 00:45.800 align:middle line:90%
And then after we
create the VRF,

22
00:45.800 --> 00:48.750 align:middle line:90%
we'd want to assign at least
one interface to that VRF

23
00:48.750 --> 00:51.000 align:middle line:90%
so it has at least one route
in that virtual routing

24
00:51.000 --> 00:52.360 align:middle line:84%
and forwarding instance.

25
00:52.360 --> 00:54.810 align:middle line:90%
Now the creation, there's
two different ways

26
00:54.810 --> 00:56.550 align:middle line:84%
of creating a VRF.

27
00:56.550 --> 01:00.000 align:middle line:90%
And one of those ways
is for IPv4 only,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:00.000 --> 01:05.433 align:middle line:90%
and the other way is if
you're doing IPv4 and/or IPv6.

29
01:05.433 --> 01:07.350 align:middle line:90%
So I wanted to point out
both ways of doing it

30
01:07.350 --> 01:08.160 align:middle line:90%
so that if you see
the configuration,

31
01:08.160 --> 01:09.735 align:middle line:90%
you won't freak
out and say, what,

32
01:09.735 --> 01:10.860 align:middle line:84%
I didn't learn it that way.

33
01:10.860 --> 01:12.310 align:middle line:90%
Well, actually both
ways of creating it.

34
01:12.310 --> 01:14.768 align:middle line:90%
So the creation for a VRF, a
virtual routing and forwarding

35
01:14.768 --> 01:17.100 align:middle line:90%
instance, if we're
the IPv4 only flavor,

36
01:17.100 --> 01:21.930 align:middle line:90%
the syntax is IP,
space, VRF, space.

37
01:21.930 --> 01:23.430 align:middle line:90%
And then you need
to give it a name.

38
01:23.430 --> 01:25.530 align:middle line:90%
And press Enter and--
bada-bing, bada-boom-- you

39
01:25.530 --> 01:27.810 align:middle line:90%
have a new virtual routing
and forwarding instance

40
01:27.810 --> 01:29.100 align:middle line:84%
called whatever that name is.

41
01:29.100 --> 01:31.703 align:middle line:84%
Let's call it CUST1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:29.100 --> 01:31.703 align:middle line:84%
Let's call it CUST1.

42
01:31.703 --> 01:33.870 align:middle line:90%
So I'm just going to give
it the name of customer 1.

43
01:33.870 --> 01:36.390 align:middle line:90%
And that will support
just IP version 4.

44
01:36.390 --> 01:40.500 align:middle line:90%
If we want to do a VRF that
will support IPv4 and/or IPv6,

45
01:40.500 --> 01:45.473 align:middle line:90%
the syntax is this, VRF,
space, definition, space.

46
01:45.473 --> 01:47.140 align:middle line:90%
And then we go ahead
and give it a name.

47
01:47.140 --> 01:49.470 align:middle line:90%
So that creates a VRF
called Customer 2.

48
01:49.470 --> 01:50.970 align:middle line:90%
And then we take
one more step, we'd

49
01:50.970 --> 01:53.710 align:middle line:90%
be placed in VRF
configuration mode.

50
01:53.710 --> 01:57.120 align:middle line:90%
And from here, we'd specify
address family, space, and then

51
01:57.120 --> 01:59.820 align:middle line:84%
we specify either IPv4 or IPv6.

52
01:59.820 --> 02:02.130 align:middle line:90%
So address family, the keyword
simply says, Oh, what's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:59.820 --> 02:02.130 align:middle line:90%
So address family, the keyword
simply says, Oh, what's

53
02:02.130 --> 02:03.840 align:middle line:90%
the protocol stack
we're working with?

54
02:03.840 --> 02:06.480 align:middle line:90%
If we're working with IPv4,
we'd add that, if it's IPv6

55
02:06.480 --> 02:08.340 align:middle line:84%
we'd specify IPv6.

56
02:08.340 --> 02:11.370 align:middle line:90%
So either way would
create the VRF.

57
02:11.370 --> 02:14.240 align:middle line:90%
And then the second step is
once these VRF's are created,

58
02:14.240 --> 02:16.042 align:middle line:84%
we then go to the interfaces.

59
02:16.042 --> 02:18.000 align:middle line:90%
And then interface config
for these interfaces,

60
02:18.000 --> 02:21.910 align:middle line:90%
we'd use the command, VRF
forwarding and then the name.

61
02:21.910 --> 02:25.560 align:middle line:90%
So if we wanted this gig 0/0 to
be associated with VRF Customer

62
02:25.560 --> 02:27.840 align:middle line:90%
1, we'd say, VRF
forwarding Customer

63
02:27.840 --> 02:29.820 align:middle line:84%
1, the name of our VRF.

64
02:29.820 --> 02:31.470 align:middle line:90%
Or if we want this
interface gig 0/3
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:29.820 --> 02:31.470 align:middle line:90%
Or if we want this
interface gig 0/3

65
02:31.470 --> 02:34.860 align:middle line:90%
to be associated with the
VRF called Customer 2,

66
02:34.860 --> 02:36.990 align:middle line:90%
we'd say VRF forwarding,
and then that name

67
02:36.990 --> 02:39.383 align:middle line:90%
that we assigned to that
VRF, which is Customer 2.

68
02:39.383 --> 02:41.550 align:middle line:90%
And one thing that surprised
me when I was initially

69
02:41.550 --> 02:44.100 align:middle line:90%
learning VRFs is that when
you apply or associate

70
02:44.100 --> 02:47.010 align:middle line:90%
an interface with a VRF,
whatever IP address was

71
02:47.010 --> 02:49.410 align:middle line:90%
on that interface, that IP
address and that network that

72
02:49.410 --> 02:50.910 align:middle line:90%
directly connected
the network, that

73
02:50.910 --> 02:53.560 align:middle line:90%
was associated with the
global routing table.

74
02:53.560 --> 02:55.940 align:middle line:90%
So when you assign an
interface to a VRF,

75
02:55.940 --> 02:59.425 align:middle line:90%
it, bam, just warps it and
removes the IP address.

76
02:59.425 --> 03:01.050 align:middle line:90%
So if you want to
use the same address,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
02:59.425 --> 03:01.050 align:middle line:90%
So if you want to
use the same address,

77
03:01.050 --> 03:03.150 align:middle line:90%
you can but you
have to reapply it

78
03:03.150 --> 03:05.880 align:middle line:90%
once you specify the
interfaces part of the VRF

79
03:05.880 --> 03:08.130 align:middle line:84%
called Customer 1 or Customer 2.

80
03:08.130 --> 03:09.930 align:middle line:90%
So that's the basic
2-step process

81
03:09.930 --> 03:11.580 align:middle line:84%
for getting VRFs working.

82
03:11.580 --> 03:14.670 align:middle line:90%
Create the VRF and assign
the layer 3 interfaces to it.

83
03:14.670 --> 03:17.610 align:middle line:90%
And check this out, it doesn't
apply just to physical routers.

84
03:17.610 --> 03:20.430 align:middle line:90%
What if we've got a multilayer
switch with Switch Virtual

85
03:20.430 --> 03:22.560 align:middle line:90%
Interfaces, layer 3
virtual interfaces for each

86
03:22.560 --> 03:23.460 align:middle line:84%
of the VLANs?

87
03:23.460 --> 03:24.540 align:middle line:84%
It'd be the same process.

88
03:24.540 --> 03:27.120 align:middle line:90%
We create the VRF and
assign those SVIs,

89
03:27.120 --> 03:29.332 align:middle line:90%
those layer 3
interfaces to the VRFs

90
03:29.332 --> 03:30.540 align:middle line:84%
where we want them to belong.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:29.332 --> 03:30.540 align:middle line:84%
where we want them to belong.

91
03:30.540 --> 03:32.105 align:middle line:90%
So in the next
video, let's do this.

92
03:32.105 --> 03:33.480 align:middle line:90%
Let me walk you
through what that

93
03:33.480 --> 03:35.430 align:middle line:90%
would look like
conceptually so we

94
03:35.430 --> 03:37.650 align:middle line:90%
can apply our
concepts of VRF lite

95
03:37.650 --> 03:40.560 align:middle line:90%
to either a physical router
or a multilayer switch who's

96
03:40.560 --> 03:42.070 align:middle line:84%
also performing routing.

97
03:42.070 --> 03:44.080 align:middle line:90%
So we'll jump into that
in the very next video.

98
03:44.080 --> 03:46.000 align:middle line:90%
So I'll see you there
in just a moment.

99
03:46.000 --> 03:48.450 align:middle line:90%
Meanwhile, I hope this has
been informative for you.

100
03:48.450 --> 03:51.620 align:middle line:90%
And I'd like to thank
you for viewing.