WEBVTT 0:00:03.040000 --> 0:00:08.560000 Welcome to this video on a review of InterVLAN routing for our CCNA 200 0:00:08.560000 --> 0:00:14.400000 -301 bootcamp. So InterVLAN routing is talking about a situation where 0:00:14.400000 --> 0:00:19.900000 we have hosts in one VLAN needing to send their packets to hosts or A 0:00:19.900000 --> 0:00:22.240000 -host in a different VLAN. 0:00:22.240000 --> 0:00:25.620000 Normally with this layer 2 switching that couldn't happen. 0:00:25.620000 --> 0:00:30.700000 So we need something that can route the packets between those two subnets. 0:00:30.700000 --> 0:00:32.480000 Now there are three ways to do that. 0:00:32.480000 --> 0:00:35.960000 We could use a router on a stick model where the switch itself is just 0:00:35.960000 --> 0:00:37.380000 a layer 2 switch. 0:00:37.380000 --> 0:00:40.820000 The switch has no knowledge of routing and he's just forwarding his packets 0:00:40.820000 --> 0:00:42.980000 to a router that's doing all that work. 0:00:42.980000 --> 0:00:47.580000 We could actually enable the switch itself for routing with switched virtual 0:00:47.580000 --> 0:00:51.860000 interfaces or we could convert some of the switching ports to layer 3 0:00:51.860000 --> 0:00:57.700000 routed ports. If we do the router on a stick model the router will have 0:00:57.700000 --> 0:01:01.500000 subinterfaces which is a single point of failure and probably not something 0:01:01.500000 --> 0:01:03.980000 you want to do. So let's look right here. 0:01:03.980000 --> 0:01:07.500000 So router on a stick simply means this. 0:01:07.500000 --> 0:01:12.060000 I have my switch right here. 0:01:12.060000 --> 0:01:20.420000 I have my router right here and I have a single interface connected to 0:01:20.420000 --> 0:01:27.080000 that router. Now that single interface is configured as a VLAN trunk. 0:01:27.080000 --> 0:01:30.420000 So on the switches side it's pretty easy. 0:01:30.420000 --> 0:01:45.480000 All you have to do is switch port trunk encapsulation dot 1Q and then 0:01:45.480000 --> 0:01:52.320000 we do switch port mode trunk. 0:01:52.320000 --> 0:01:53.640000 That's all we have to do. 0:01:53.640000 --> 0:01:56.320000 A little bit more work here on the router side which we'll talk about 0:01:56.320000 --> 0:02:00.240000 in just a second but the whole point behind this is on the switches side. 0:02:00.240000 --> 0:02:02.120000 We have a bunch of different VLANs. 0:02:02.120000 --> 0:02:05.000000 This might here might be VLAN 2. 0:02:05.000000 --> 0:02:09.420000 We might have some other hosts here in VLAN 3 and some other hosts here 0:02:09.420000 --> 0:02:13.780000 in VLAN 4. And if the switch is not going to the routing force and the 0:02:13.780000 --> 0:02:18.180000 router will we need all this traffic to be able to go up this trunk. 0:02:18.180000 --> 0:02:23.220000 So it can be routed back and forth between by the switch. 0:02:23.220000 --> 0:02:25.720000 I mean by the router, not the switch. 0:02:25.720000 --> 0:02:28.640000 So in order to do this what we're going to do is we're going to go on 0:02:28.640000 --> 0:02:32.420000 to this router's physical interface and we're going to break it up into 0:02:32.420000 --> 0:02:37.660000 sub interfaces. So the physical interface might be fast ethernet 0 slash 0:02:37.660000 --> 0:02:41.900000 0. All we have to do there is no shut and that's it. 0:02:41.900000 --> 0:02:46.780000 And then we create these logical sub interfaces one per VLAN. 0:02:46.780000 --> 0:02:52.220000 So we would say fast ethernet 0 slash 0 dot. 0:02:52.220000 --> 0:02:55.020000 And then we could put any number after the dot we want but typically we 0:02:55.020000 --> 0:02:56.880000 put the number of the VLAN after the dot. 0:02:56.880000 --> 0:02:59.740000 So why don't we start with 0 slash 0 dot 2. 0:02:59.740000 --> 0:03:08.780000 Fast ethernet 0 slash 0 dot 3 and fast ethernet 0 slash 0 dot 4. 0:03:08.780000 --> 0:03:10.700000 Then we have to tell each sub interface. 0:03:10.700000 --> 0:03:13.980000 Hey, I need you to do 802 dot 1 queue tagging. 0:03:13.980000 --> 0:03:18.580000 So you can recognize incoming tags and you can apply outgoing tags. 0:03:18.580000 --> 0:03:23.120000 So we use the encapsulation. 0:03:23.120000 --> 0:03:32.980000 Dot 1 queue and then we put the VLAN number in there. 0:03:32.980000 --> 0:03:36.060000 Capsulation dot 1 queue 3. 0:03:36.060000 --> 0:03:42.160000 Capsulation dot 1 queue 4. 0:03:42.160000 --> 0:03:45.160000 And then lastly, we put our IP addresses on here. 0:03:45.160000 --> 0:03:46.320000 We put the IP address. 0:03:46.320000 --> 0:03:49.060000 It's appropriate for VLAN 2. 0:03:49.060000 --> 0:03:52.120000 Whatever subnet that is an IP address. 0:03:52.120000 --> 0:03:56.060000 It's appropriate for VLAN 3 and IP address. 0:03:56.060000 --> 0:03:57.800000 It's appropriate for VLAN 4. 0:03:57.800000 --> 0:04:00.300000 And that's what we see here on this slide. 0:04:00.300000 --> 0:04:06.420000 Create our sub interfaces and then on each sub interface we do the encapsulation 0:04:06.420000 --> 0:04:09.100000 dot 1 queue command and an IP address. 0:04:09.100000 --> 0:04:11.840000 And then the router will be able to route between those sub interfaces 0:04:11.840000 --> 0:04:14.980000 because they have created connected routes. 0:04:14.980000 --> 0:04:18.020000 And a router can route back and forth between connected routes all day 0:04:18.020000 --> 0:04:21.420000 long. We don't need any routing protocol or anything to do that. 0:04:21.420000 --> 0:04:24.520000 Now, like I said in the previous slide, the downside to this is that router 0:04:24.520000 --> 0:04:26.080000 is a single point of failure. 0:04:26.080000 --> 0:04:30.760000 If it fails, those hosts will not have any default gateway anymore. 0:04:30.760000 --> 0:04:32.940000 Or maybe the router itself might not fail. 0:04:32.940000 --> 0:04:36.960000 Maybe somebody yanks out that cable, that trunking cable between the router 0:04:36.960000 --> 0:04:40.620000 and the switch. So for that reason, it might be better just to have the 0:04:40.620000 --> 0:04:43.360000 switch itself do the routing for us. 0:04:43.360000 --> 0:04:46.740000 And in most modern network designs today, that's what you'll actually 0:04:46.740000 --> 0:04:50.640000 see. That the switch itself, the access layer switch is actually doing 0:04:50.640000 --> 0:04:53.640000 the routing and serving as the default gateway. 0:04:53.640000 --> 0:04:56.580000 So you can do that in one of two ways. 0:04:56.580000 --> 0:05:02.560000 So we could use SBIs. 0:05:02.560000 --> 0:05:06.560000 So we could just simply say, okay, well, I've got VLAN 2, so I'll create 0:05:06.560000 --> 0:05:11.460000 an interface. Well, actually just take a look at the next slide. 0:05:11.460000 --> 0:05:16.800000 Right here, I'll create an interface VLAN 2. 0:05:16.800000 --> 0:05:19.440000 And then I'll put an IP address on it that's in the same subnet as all 0:05:19.440000 --> 0:05:21.120000 my hosts in VLAN 2. 0:05:21.120000 --> 0:05:24.920000 And then I've got some hosts here in VLAN 3, so I'll create an interface 0:05:24.920000 --> 0:05:28.260000 VLAN 3, put an IP address on there. 0:05:28.260000 --> 0:05:34.260000 Now, the switches, most switches don't have routing enabled by default. 0:05:34.260000 --> 0:05:37.580000 So you can create switch virtual interfaces, that's what we call these 0:05:37.580000 --> 0:05:39.300000 interface VLANs right here. 0:05:39.300000 --> 0:05:42.580000 You can create these all day long, but they won't be able to route packets 0:05:42.580000 --> 0:05:44.700000 back and forth between them. 0:05:44.700000 --> 0:05:49.740000 That's why on most switches, we also have to enable IP routing globally 0:05:49.740000 --> 0:05:51.580000 to enable it to do that. 0:05:51.580000 --> 0:05:54.600000 That turns on routing functionality. 0:05:54.600000 --> 0:05:58.100000 And then, of course, we'd have to get our DHCP server involved. 0:05:58.100000 --> 0:06:02.580000 Our DHCP server would have to know that when a DHCP discover comes in 0:06:02.580000 --> 0:06:06.400000 from somebody in VLAN 2, the DHCP server should say, oh, your default 0:06:06.400000 --> 0:06:08.680000 gateway is 2.2.2.2. 0:06:08.680000 --> 0:06:15.340000 And for you guys over there in VLAN 3, your default gateway is 3.3.3.3. 0:06:15.340000 --> 0:06:19.360000 Or, of course, we could make it even easier and configure this exact same 0:06:19.360000 --> 0:06:22.400000 switch as our DHCP server. 0:06:22.400000 --> 0:06:30.540000 One other alternative you could do is we could have layer 3 routed ports. 0:06:30.540000 --> 0:06:36.360000 So an example of this is done on the distribution layer switches. 0:06:36.360000 --> 0:06:38.380000 Let me give you an example of that. 0:06:38.380000 --> 0:06:42.340000 Let's say we have a switch right here. 0:06:42.340000 --> 0:06:49.440000 Switch 1. And he's got something like this. 0:06:49.440000 --> 0:06:55.320000 So this is going to be VLAN 1. 0:06:55.320000 --> 0:06:59.860000 Actually, let's make it even simpler like this. 0:06:59.860000 --> 0:07:05.600000 Let's say we've got three access layer switches. 0:07:05.600000 --> 0:07:10.300000 Switch 1, switch 2, and switch 3. 0:07:10.300000 --> 0:07:13.860000 Each access layer switch is only serving a single VLAN. 0:07:13.860000 --> 0:07:17.540000 So maybe this guy here is serving VLAN 1. 0:07:17.540000 --> 0:07:20.400000 This access layer switch. 0:07:20.400000 --> 0:07:23.840000 He's only doing VLAN 2. 0:07:23.840000 --> 0:07:25.160000 And this other guy. 0:07:25.160000 --> 0:07:28.340000 He's doing VLAN 3. 0:07:28.340000 --> 0:07:34.820000 Okay. And they're all connected up to a distribution switch. 0:07:34.820000 --> 0:07:39.060000 Who's going to do the routing back and forth between these VLANs? 0:07:39.060000 --> 0:07:43.240000 Well, we could on this distribution switch, we could say, hey, I'm going 0:07:43.240000 --> 0:07:45.980000 to make this an access port in VLAN 1. 0:07:45.980000 --> 0:07:49.320000 And then in that switch, I'm going to create interface VLAN 1 and put 0:07:49.320000 --> 0:07:51.960000 an IP address on it like we just saw in the last slide. 0:07:51.960000 --> 0:07:54.880000 And then we can say, hey, I'm going to make this an access port in VLAN 0:07:54.880000 --> 0:07:57.360000 2 and create a switch virtual interface for that. 0:07:57.360000 --> 0:07:58.800000 You could do that. 0:07:58.800000 --> 0:08:02.280000 Or we could just say, hey, I'm going to go this interface right here and 0:08:02.280000 --> 0:08:04.020000 do these two commands. 0:08:04.020000 --> 0:08:08.020000 No switch port. And now that it's now I've just converted into what's 0:08:08.020000 --> 0:08:10.040000 called a routed interface. 0:08:10.040000 --> 0:08:12.820000 And now I can actually put an IP address on it. 0:08:12.820000 --> 0:08:14.660000 And that IP address. 0:08:14.660000 --> 0:08:20.940000 So 1.1.1.99. That can serve as the default gateway for all the people 0:08:20.940000 --> 0:08:24.080000 in VLAN 1. And I could do the same thing over here. 0:08:24.080000 --> 0:08:30.180000 I could say no switch port on that and give him an IP address that will 0:08:30.180000 --> 0:08:34.960000 be serving as the default gateway for all the people in that VLAN. 0:08:34.960000 --> 0:08:38.180000 So that's what we mean by routed interfaces. 0:08:38.180000 --> 0:08:42.060000 Interfaces where we disabled their switch port capability. 0:08:42.060000 --> 0:08:43.700000 They're no longer in a VLAN. 0:08:43.700000 --> 0:08:46.760000 And they're just like an interface and a router where you can stick an 0:08:46.760000 --> 0:08:51.620000 IP address on. Now remember, even if we do that on the switch, we're still 0:08:51.620000 --> 0:08:56.980000 globally going to want to type IP routing to enable to route between our 0:08:56.980000 --> 0:09:03.180000 connected interfaces. 0:09:03.180000 --> 0:09:04.780000 Here's an example of that. 0:09:04.780000 --> 0:09:07.600000 Just like it drew on the whiteboard just a moment ago. 0:09:07.600000 --> 0:09:17.480000 I don't think there's really anything to add to this picture. 0:09:17.480000 --> 0:09:20.380000 And we can do show IP route connected. 0:09:20.380000 --> 0:09:26.380000 To verify that routing is actually enabled, whether it be on our router 0:09:26.380000 --> 0:09:28.660000 or on our switch. 0:09:28.660000 --> 0:09:34.720000 So that concludes this video on inter VLAN routing. 0:09:34.720000 --> 0:09:35.460000 I hope you found it helpful.