WEBVTT

0:00:08.680000 --> 0:00:14.880000
 Okay, in this next section, we're going
 to talk about RIP-NG, which is,

0:00:14.880000 --> 0:00:19.560000
 of course, RIP-4-IPV-6.

0:00:19.560000 --> 0:00:22.980000
 Now if you take a look at our diagram
 here, again, I sort of have this

0:00:22.980000 --> 0:00:27.880000
 set up so we can do a sampling of all
 the routing protocols and end up

0:00:27.880000 --> 0:00:30.440000
 with full connectivity here.

0:00:30.440000 --> 0:00:34.660000
 So, if you take a look, I have RIP
-NG set up there on between routers

0:00:34.660000 --> 0:00:40.600000
 4 and 5 and switch 1 and switch
 2 down there at the bottom.

0:00:40.600000 --> 0:00:47.160000
 All of these VLANs are already created
 on the switches and so on.

0:00:47.160000 --> 0:00:51.180000
 Okay, so we're just going to jump in and
 configure RIP on those four devices

0:00:51.180000 --> 0:00:56.520000
 to start with and then we'll be leaving
 that there for the rest of our

0:00:56.520000 --> 0:00:59.900000
 lessons, or at least for the
 majority of them anyway.

0:00:59.900000 --> 0:01:02.820000
 Okay. So a little bit of
 information on this.

0:01:02.820000 --> 0:01:08.640000
 RIP-NG is covered in RFC 2080
 just for your reference.

0:01:08.640000 --> 0:01:14.060000
 It, of course, runs on top
 of IPv6 as it's transport.

0:01:14.060000 --> 0:01:19.620000
 Still UDP, everything else about
 it's pretty much the same.

0:01:19.620000 --> 0:01:23.300000
 You know, what I always like to point
 out to people is, you know, this

0:01:23.300000 --> 0:01:28.860000
 is basically RIP version
 2 for IPv6.

0:01:28.860000 --> 0:01:31.980000
 It obviously exchanges
 IPv6 routes.

0:01:31.980000 --> 0:01:35.520000
 Now, one difference we have, and I'm going
 to show you this as we go through

0:01:35.520000 --> 0:01:42.280000
 the config, is that we can actually
 run up to four instances of RIP on

0:01:42.280000 --> 0:01:45.940000
 the router. So I'll get to
 that here in just a second.

0:01:45.940000 --> 0:01:52.680000
 And of course, it's named RIP-NG, but
 it's really just RIP version 2.

0:01:52.680000 --> 0:01:56.740000
 And you know, I want to point out that,
 you know, with RIP-NG, they really

0:01:56.740000 --> 0:02:01.640000
 have the opportunity to fix everything
 that was wrong with RIP version

0:02:01.640000 --> 0:02:05.680000
 2, all of its issues are
 problems and so on.

0:02:05.680000 --> 0:02:10.840000
 Okay, so I mean, they didn't,
 you understand.

0:02:10.840000 --> 0:02:15.860000
 I just want to make sure, I just want
 to point out that they could have.

0:02:15.860000 --> 0:02:21.400000
 But now, seriously, jokes aside, they
 do, it does still have pretty much

0:02:21.400000 --> 0:02:28.280000
 all the same attributes
 as RIP version 2.

0:02:28.280000 --> 0:02:31.820000
 So same hop limit,
 same, all of that.

0:02:31.820000 --> 0:02:36.340000
 So really, it just comes down to, from
 a running it and configuring its

0:02:36.340000 --> 0:02:42.320000
 standpoint, it's really just a configuration
 change that we have to go

0:02:42.320000 --> 0:02:45.600000
 over. So let's switch over
 to the command line.

0:02:45.600000 --> 0:02:48.520000
 We'll start with router 4, since that's
 the first place we need to run

0:02:48.520000 --> 0:02:58.360000
 it. And probably the most important thing
 to realize about just IPv6 routing

0:02:58.360000 --> 0:03:06.460000
 protocols in general is the good old
 network statement that we have, and

0:03:06.460000 --> 0:03:12.320000
 we've known so famously for all these
 years for IPv4, they're all gone.

0:03:12.320000 --> 0:03:18.460000
 We now configure everything on the actual
 interfaces, which much better,

0:03:18.460000 --> 0:03:22.100000
 much more accurate, it's just
 another way of doing it.

0:03:22.100000 --> 0:03:27.760000
 So what we're going to do here is we're
 going to say interface, FA01,

0:03:27.760000 --> 0:03:32.920000
 IPv6, RIP, and then like I said,
 you have to give it a name.

0:03:32.920000 --> 0:03:37.120000
 You can run up to four instances.

0:03:37.120000 --> 0:03:42.920000
 And they are 100% local names.

0:03:42.920000 --> 0:03:46.760000
 These are local RIP processes
 on the router.

0:03:46.760000 --> 0:03:50.600000
 So I could just say RIP.

0:03:50.600000 --> 0:03:53.560000
 I like to be a little
 bit of a rebel.

0:03:53.560000 --> 0:03:58.760000
 I like to call it RIP V3, because I think
 that's what it should have been

0:03:58.760000 --> 0:04:01.380000
 called. That's a whole other discussion
 I'm not going to get into right

0:04:01.380000 --> 0:04:03.120000
 now, but whatever.

0:04:03.120000 --> 0:04:04.800000
 And then you just say enable.

0:04:04.800000 --> 0:04:09.320000
 And that's it. Okay.

0:04:09.320000 --> 0:04:12.300000
 Really all there is to it.

0:04:12.300000 --> 0:04:15.820000
 Top over to switch one.

0:04:15.820000 --> 0:04:26.880000
 And we will say interface, VLAN, let's
 see, start with 41, IPv6, RIP.

0:04:26.880000 --> 0:04:31.900000
 Now just to show you how this works,
 I'm going to for now do it a little

0:04:31.900000 --> 0:04:33.880000
 bit different on switch one.

0:04:33.880000 --> 0:04:40.140000
 Now I'll start just for the simple
 part of doing it the same way.

0:04:40.140000 --> 0:04:43.780000
 So I'll just say RIP V3.

0:04:43.780000 --> 0:04:49.480000
 Enable. And just so there's something
 to advertise, interface, loop back

0:04:49.480000 --> 0:05:08.060000
 zero, RIP V3 enable,
 do debug IPv6 RIP.

0:05:08.060000 --> 0:05:11.000000
 And notice we've already
 learned to leak back.

0:05:11.000000 --> 0:05:21.080000
 This is us sending a RIP update.

0:05:21.080000 --> 0:05:24.700000
 Of course we have nothing to tell anybody,
 because if you look at the

0:05:24.700000 --> 0:05:30.920000
 diagram, router four is not going to
 be running any other interfaces on

0:05:30.920000 --> 0:05:36.420000
 RIP. So all I'm really doing
 is getting updates.

0:05:36.420000 --> 0:05:43.160000
 So here is of course switch one down
 there, advertising his loop back

0:05:43.160000 --> 0:05:45.180000
 to me, because he's down
 there at the bottom.

0:05:45.180000 --> 0:05:46.480000
 So very, very simple.

0:05:46.480000 --> 0:05:50.340000
 There it is. So I'm learning
 his loop back.

0:05:50.340000 --> 0:05:52.920000
 Now if I were to go, and this is where
 we're going to start having a little

0:05:52.920000 --> 0:05:57.520000
 bit of fun, first off, just generically,
 let me fire up RIP everywhere

0:05:57.520000 --> 0:06:05.740000
 else. So on router five, I'm going to
 say interface, FA01, IPv6 router,

0:06:05.740000 --> 0:06:08.680000
 that's the one to config.

0:06:08.680000 --> 0:06:10.520000
 I'll show you that in a minute.

0:06:10.520000 --> 0:06:11.560000
 Whoops, I just did it again.

0:06:11.560000 --> 0:06:33.900000
 IPv6 RIP, RIP V3 enable, switch two,
 interface VLAN 52, interface loop

0:06:33.900000 --> 0:06:39.540000
 back zero, and interface VLAN 12, which
 is between switch one and switch

0:06:39.540000 --> 0:06:43.440000
 two at the bottom.

0:06:43.440000 --> 0:06:46.000000
 So switch two is just running
 RIP everywhere.

0:06:46.000000 --> 0:06:53.300000
 That being the case, router five should
 have just learned about VLAN 12

0:06:53.300000 --> 0:06:56.500000
 and switch two's loop back.

0:06:56.500000 --> 0:07:03.840000
 Okay? Now what I have not done on purpose
 is on switch one, I've not done

0:07:03.840000 --> 0:07:09.280000
 anything on his VLAN 12 interface, because
 I want to show you something.

0:07:09.280000 --> 0:07:12.940000
 These instances of RIP, okay?

0:07:12.940000 --> 0:07:29.860000
 I can say interface VLAN 12, and I could
 say IPv6 RIP V3 A enable, a different

0:07:29.860000 --> 0:07:37.160000
 process. Okay? Now notice, he's still
 sending and receiving updates for

0:07:37.160000 --> 0:07:40.740000
 RIP V3 A. There it goes.

0:07:40.740000 --> 0:07:43.680000
 Okay? Now the debugs are going to get
 in our way a little bit here, so

0:07:43.680000 --> 0:07:45.540000
 I'm going to say do you all.

0:07:45.540000 --> 0:07:49.000000
 You can see he's sending and
 receiving RIP updates.

0:07:49.000000 --> 0:07:51.360000
 I always sort of joke
 about the RIP debugs.

0:07:51.360000 --> 0:07:56.780000
 If you can't read this, I really can't
 help you, because it's such plain

0:07:56.780000 --> 0:07:59.700000
 English compared to most debugs.

0:07:59.700000 --> 0:08:01.980000
 I'm sending this, I'm
 receiving this.

0:08:01.980000 --> 0:08:04.260000
 Here's the tag, the metrics,
 and the prefixes.

0:08:04.260000 --> 0:08:08.780000
 I mean, that's pretty much as
 easy as it gets, honestly.

0:08:08.780000 --> 0:08:13.560000
 But let's take a look at
 the routes we've gotten.

0:08:13.560000 --> 0:08:20.780000
 Okay? Now what you want to remember
 as we go through this is we have a

0:08:20.780000 --> 0:08:25.600000
 whole separate RIP process
 running on switch one.

0:08:25.600000 --> 0:08:36.000000
 So if I say do show IP V6 route
 RIP, I said six and typed four.

0:08:36.000000 --> 0:08:46.120000
 Okay? Notice that he's learning about
 52 and eight, which is that's switch

0:08:46.120000 --> 0:08:54.540000
 two's loop back, and VLAN 52 between
 route or five and switch two.

0:08:54.540000 --> 0:08:56.780000
 That's what he should be learning.


0:08:56.780000 --> 0:09:05.940000
 But if you go up to
 route of four, okay?

0:09:05.940000 --> 0:09:10.280000
 Notice he's not learning
 about VLAN 52.

0:09:10.280000 --> 0:09:13.940000
 He's not learning about VLAN 12.

0:09:13.940000 --> 0:09:18.240000
 He's not learning about switch
 two's loop back, okay?

0:09:18.240000 --> 0:09:25.080000
 Because what's going on right now is
 switch one is running two separate

0:09:25.080000 --> 0:09:30.960000
 RIP processes, and he keeps
 those completely separate.

0:09:30.960000 --> 0:09:36.060000
 So switch one learns all the routes,
 and we're not going to leave it this

0:09:36.060000 --> 0:09:38.840000
 way, but just so we have something to
 advertise the other way, at least

0:09:38.840000 --> 0:09:53.700000
 for now. And we'll turn
 this on for IPV6 RIP.

0:09:53.700000 --> 0:09:55.220000
 We'll do the same on route.

0:09:55.220000 --> 0:09:57.920000
 Well, we don't need it on route
 five because we have VLAN 52.

0:09:57.920000 --> 0:10:01.000000
 It's okay. So now we're
 going to switch one.

0:10:01.000000 --> 0:10:03.340000
 I just want to point out he should
 be learning everything.

0:10:03.340000 --> 0:10:07.100000
 See, he's got route
 of four's loop back.

0:10:07.100000 --> 0:10:09.140000
 He's got route or two's loop back.


0:10:09.140000 --> 0:10:11.140000
 He's got VLAN 52.

0:10:11.140000 --> 0:10:12.080000
 He's got everything.

0:10:12.080000 --> 0:10:19.440000
 But what he will not do is pass the routes
 between the two separate processes.

0:10:19.440000 --> 0:10:24.500000
 So that means a route of four is never
 going to learn the things from

0:10:24.500000 --> 0:10:29.260000
 RIP V3 instance A that we created.


0:10:29.260000 --> 0:10:32.480000
 He still has the one loop back.

0:10:32.480000 --> 0:10:41.240000
 And similarly, if we go over to switch
 two, he's not going to learn.

0:10:41.240000 --> 0:10:44.300000
 Well, he's not going to learn anything
 because he's directly connected.

0:10:44.300000 --> 0:10:50.740000
 Although he should have, no, we never
 put route of five's loop back in.

0:10:50.740000 --> 0:10:53.600000
 That's okay. Switch two is directly
 connected to everything.

0:10:53.600000 --> 0:10:56.860000
 But he doesn't have bare minimum, you
 can see here, he doesn't have VLAN

0:10:56.860000 --> 0:11:02.780000
 41. He doesn't have the link between
 route of four and switch one because

0:11:02.780000 --> 0:11:07.860000
 that's in the other instance
 of RIP on switch one.

0:11:07.860000 --> 0:11:14.780000
 So, you can use the instances to create
 two separate RIP environments

0:11:14.780000 --> 0:11:17.900000
 on a device. Okay?

0:11:17.900000 --> 0:11:22.640000
 Now, that said, if you really want to
 get confusing, I could go to switch

0:11:22.640000 --> 0:11:26.300000
 one and I could say
 interface VLAN 12.

0:11:26.300000 --> 0:11:32.420000
 And the last thing we did
 was turn on RIP V3A.

0:11:32.420000 --> 0:11:35.780000
 What if I also turned on RIP V3?

0:11:35.780000 --> 0:11:41.180000
 Okay. You can run multiple instances
 on the same interface.

0:11:41.180000 --> 0:11:46.780000
 And what that means is that the RIP V3
 processes, that would be the stuff

0:11:46.780000 --> 0:11:51.960000
 coming from router four, that's going
 to go out his VLAN 12 interface

0:11:51.960000 --> 0:11:55.660000
 now. So if I go over to switch two,
 he should have just picked up router

0:11:55.660000 --> 0:12:03.360000
 four's loop back and VLAN 41.

0:12:03.360000 --> 0:12:09.260000
 There we go. So he picks up VLAN
 41, router four's loop back.

0:12:09.260000 --> 0:12:11.020000
 Oh yeah, I didn't even
 think about that one.

0:12:11.020000 --> 0:12:13.800000
 But also, yeah, switch one's
 loop back as well.

0:12:13.800000 --> 0:12:20.540000
 So now he just picked up all of
 the RIP V3 normal instance.

0:12:20.540000 --> 0:12:23.800000
 However, it's only
 a one-way street.

0:12:23.800000 --> 0:12:32.680000
 Router four, always going
 to get everything now.

0:12:32.680000 --> 0:12:35.200000
 There's switch one's loop back.

0:12:35.200000 --> 0:12:35.840000
 You should get everything.

0:12:35.840000 --> 0:12:38.040000
 Here we go. Now we're good.

0:12:38.040000 --> 0:12:41.600000
 So it doesn't go both ways.

0:12:41.600000 --> 0:12:48.320000
 So he gets switch four's loop back and
 he just got 12 because it's connected.

0:12:48.320000 --> 0:12:51.620000
 So notice he picked up the
 12 he didn't have before.

0:12:51.620000 --> 0:12:54.800000
 See up here, he only
 had the loop back.

0:12:54.800000 --> 0:12:59.300000
 See he picked up the 12 now, but he's
 not picking up the routes being

0:12:59.300000 --> 0:13:02.800000
 advertised in on that interface.

0:13:02.800000 --> 0:13:07.980000
 So it starts getting a little bit weird
 with multiple instances here.

0:13:07.980000 --> 0:13:14.580000
 But that's probably like the biggest
 change with RIP in IPv6.

0:13:14.580000 --> 0:13:17.760000
 Other than that, and I'm going
 to go back to switch two.

0:13:17.760000 --> 0:13:19.820000
 Like I said, I'm not going
 to leave it like that.

0:13:19.820000 --> 0:13:23.200000
 What I'm going to do is I'm going
 to take off the instance A.

0:13:23.200000 --> 0:13:25.020000
 We don't even need it.

0:13:25.020000 --> 0:13:31.460000
 And now we should have
 four routes everywhere.

0:13:31.460000 --> 0:13:33.620000
 Let's go back up to router four.

0:13:33.620000 --> 0:13:36.720000
 The second here.

0:13:36.720000 --> 0:13:42.700000
 Rips not, of course, the fastest
 thing in the world.

0:13:42.700000 --> 0:13:51.460000
 Let's see what we have
 here real quick.

0:13:51.460000 --> 0:14:00.400000
 Cool. So we got all the
 routes everywhere.

0:14:00.400000 --> 0:14:05.060000
 And like I said on router four, I also,
 I'm not going to leave his loop

0:14:05.060000 --> 0:14:09.240000
 back. We're going to end up putting
 that in OSPF later in a different

0:14:09.240000 --> 0:14:11.840000
 lab, in a different lesson.

0:14:11.840000 --> 0:14:20.780000
 So RIP should be running just on the RIP
 interfaces to show IPv6 protocols.

0:14:20.780000 --> 0:14:26.980000
 And RIP, RIP V3 is running
 just on a ZFA 01 interface.

0:14:26.980000 --> 0:14:31.220000
 Okay. So again, there's not a whole
 lot of different timers and all that

0:14:31.220000 --> 0:14:34.920000
 kind of stuff. They're
 all the same as IPv4.

0:14:34.920000 --> 0:14:37.560000
 There's really no
 difference there.

0:14:37.560000 --> 0:14:40.280000
 So I'm not going to spend a whole ton
 of time on RIP because hopefully

0:14:40.280000 --> 0:14:45.320000
 not too many people are still running
 RIP, particularly for IPv6.

0:14:45.320000 --> 0:14:46.600000
 But it's there. It works.

0:14:46.600000 --> 0:14:48.700000
 It's supported. There's
 nothing wrong with it.

0:14:48.700000 --> 0:14:50.800000
 It's, of course, incredibly
 simple.

0:14:50.800000 --> 0:14:54.700000
 Just not the fastest protocol
 that we have to choose from.

