WEBVTT 0:00:02.980000 --> 0:00:09.180000 Hello and welcome to this video titled Essential RSTP Cisco iOS commands. 0:00:09.180000 --> 0:00:12.480000 In this video I'm going to give you some of the real basic commands you 0:00:12.480000 --> 0:00:16.500000 need to turn on rapid spanning tree and to allow you to have deterministic 0:00:16.500000 --> 0:00:19.160000 placement of the root bridge. 0:00:19.160000 --> 0:00:23.860000 Then I'll show you how to verify in Cisco iOS which switch is operating 0:00:23.860000 --> 0:00:25.620000 as the root bridge. 0:00:25.620000 --> 0:00:29.680000 So let's start with some of these basic commands here. 0:00:29.680000 --> 0:00:34.560000 So while some Cisco switches do run rapid spanning tree by default, most 0:00:34.560000 --> 0:00:39.080000 of them don't. So your very first thing you would need to do is to enable 0:00:39.080000 --> 0:00:40.840000 rapid spanning tree. 0:00:40.840000 --> 0:00:43.940000 And you can see here the command for that this is done at the global level, 0:00:43.940000 --> 0:00:47.700000 spanning dash tree mode rapid dash pbs t. 0:00:47.700000 --> 0:00:51.900000 And in case you're not familiar with that term pbs t, what that's referring 0:00:51.900000 --> 0:00:57.760000 to is that for each and every VLAN you have on that switch that's active 0:00:57.760000 --> 0:01:02.560000 that has ports in it, a tree, a rapid spanning tree tree will be created 0:01:02.560000 --> 0:01:04.820000 for that individual VLAN. 0:01:04.820000 --> 0:01:08.780000 So if I have five VLANs active on my switch, that means that switch will 0:01:08.780000 --> 0:01:13.940000 be maintaining five different trees, each one with its own root bridge, 0:01:13.940000 --> 0:01:19.440000 each tree with its own independent set of forwarding and blocking interfaces. 0:01:19.440000 --> 0:01:24.960000 Now rapid spanning tree is backwards compatible with legacy spanning tree. 0:01:24.960000 --> 0:01:27.840000 It can interoperate with the two of them. 0:01:27.840000 --> 0:01:33.220000 The next thing is we hopefully either through my videos or on your own 0:01:33.220000 --> 0:01:38.900000 study, you have learned what the concept is of an edge port in rapid spanning 0:01:38.900000 --> 0:01:42.600000 tree. And an edge port is not something a switch is able to determine 0:01:42.600000 --> 0:01:47.260000 on its own. So we need to enable a command to let the switch know that, 0:01:47.260000 --> 0:01:50.960000 hey, this interface right here, this is edge, this is going to a host 0:01:50.960000 --> 0:01:56.020000 like a router or a PC or a laptop or a server, something where we can 0:01:56.020000 --> 0:01:59.820000 send a broadcast to it without any fear that's going to circle back around 0:01:59.820000 --> 0:02:02.080000 and cause a broadcast storm. 0:02:02.080000 --> 0:02:06.760000 So the way the rapid spanning tree on Cisco switches identifies an edge 0:02:06.760000 --> 0:02:11.580000 port is by enabling a feature called portfast on that interface. 0:02:11.580000 --> 0:02:15.520000 Portfast very simply when you enable that interface means that as soon 0:02:15.520000 --> 0:02:19.300000 as that interface detects electrical connectivity, it will immediately 0:02:19.300000 --> 0:02:21.280000 go into the forwarding state. 0:02:21.280000 --> 0:02:25.100000 It'll skip any transitionary states and immediately go forwarding, which 0:02:25.100000 --> 0:02:28.800000 is something that would be appropriate for an edge port. 0:02:28.800000 --> 0:02:32.160000 And those here, you can also enable spanning tree with the optional keyword 0:02:32.160000 --> 0:02:36.180000 of trunk. That would be appropriate not if you're trunking to another 0:02:36.180000 --> 0:02:38.640000 switch. That would not be the time to do that. 0:02:38.640000 --> 0:02:42.080000 That would be if you're trunking, for example, to a router or maybe you're 0:02:42.080000 --> 0:02:45.460000 trunking to a server that maybe has a bunch of virtual machines in it 0:02:45.460000 --> 0:02:49.620000 or something. But if you're trunking to something and that thing you're 0:02:49.620000 --> 0:02:54.840000 trunking to is not doing spanning tree and is not capable of reflecting 0:02:54.840000 --> 0:03:00.060000 BPD, reflecting broadcast back to you again, then you can enable portfast 0:03:00.060000 --> 0:03:05.100000 on that trunk. So here we can see the interface command to do it or you 0:03:05.100000 --> 0:03:08.940000 could do it at the global level with spanning tree portfast default. 0:03:08.940000 --> 0:03:12.120000 And with that command, any interface that's currently operating as an 0:03:12.120000 --> 0:03:15.040000 access port will be enabled for portfast. 0:03:15.040000 --> 0:03:19.560000 Now at an absolute minimum, that's what we're going to want to do. 0:03:19.560000 --> 0:03:25.020000 We're going to want to enable Rapids PVST as a mode and any interfaces 0:03:25.020000 --> 0:03:27.040000 on our switch are connected to hosts. 0:03:27.040000 --> 0:03:28.820000 We're going to want to enable portfast. 0:03:28.820000 --> 0:03:32.480000 That way the switch will be able to identify those as edge ports. 0:03:32.480000 --> 0:03:36.540000 And I'll show you what that looks like in just one second. 0:03:36.540000 --> 0:03:40.020000 Now usually what people will also do is they will have deterministic placement 0:03:40.020000 --> 0:03:41.500000 of their root bridge. 0:03:41.500000 --> 0:03:43.800000 In other words, they'll say, hey, I've got all these switches right here, 0:03:43.800000 --> 0:03:48.400000 but this switch in particular, I want that to be my root bridge. 0:03:48.400000 --> 0:03:52.140000 Maybe because he's centrally located, he's sort of right in the middle 0:03:52.140000 --> 0:03:56.460000 of the apology, maybe it's because he's the biggest, fastest switch I've 0:03:56.460000 --> 0:03:59.260000 got with the most memory and the most processing power. 0:03:59.260000 --> 0:04:02.700000 But for whatever reason, you will probably identify a switch in your network 0:04:02.700000 --> 0:04:04.700000 that you want to make the root bridge. 0:04:04.700000 --> 0:04:07.960000 Because remember, if you don't configure something, spanning tree will 0:04:07.960000 --> 0:04:11.580000 determine the root bridge all on its own based simply on the lowest bridge 0:04:11.580000 --> 0:04:16.520000 ID, which usually defaults to the lowest MAC address because all switches 0:04:16.520000 --> 0:04:20.280000 have the same priority, 326768 by default. 0:04:20.280000 --> 0:04:22.980000 So whoever would be having the lowest MAC address, which is usually the 0:04:22.980000 --> 0:04:26.200000 oldest switch, will end up becoming the root bridge. 0:04:26.200000 --> 0:04:27.700000 And that's not what you want. 0:04:27.700000 --> 0:04:32.480000 So there's a couple of ways you can deterministically set the root bridge. 0:04:32.480000 --> 0:04:37.800000 So one way is using this macro command right here, spanning dash tree, 0:04:37.800000 --> 0:04:40.820000 select your VLAN, because remember, we're dealing with individual trees 0:04:40.820000 --> 0:04:45.120000 now per VLAN. So select your VLAN and your VLAN number like VLAN 7 or 0:04:45.120000 --> 0:04:49.220000 VLAN 2, root, and then primary. 0:04:49.220000 --> 0:04:51.720000 Now how does this actually work? 0:04:51.720000 --> 0:04:56.640000 Well, if you did this on a switch that was already the root bridge, what 0:04:56.640000 --> 0:04:59.820000 it would do is it would knock his bridge priority down from the default 0:04:59.820000 --> 0:05:09.680000 of 326768 down to a much lower value of 24576, 24576. 0:05:09.680000 --> 0:05:13.260000 Now if I do this command on a switch who's not the root, let's say there's 0:05:13.260000 --> 0:05:17.500000 another root bridge out there already right now, and I do this root primary 0:05:17.500000 --> 0:05:19.160000 command on my switch. 0:05:19.160000 --> 0:05:26.400000 What it will do is it will lower my bridge ID just enough to beat that 0:05:26.400000 --> 0:05:30.940000 guy. Now remember, bridge priorities have to be an increments or multiples 0:05:30.940000 --> 0:05:36.880000 of 4096. So it will lower my priority in some increment or multiple of 0:05:36.880000 --> 0:05:41.420000 4096 just enough to beat the root bridge so I can become the root bridge. 0:05:41.420000 --> 0:05:42.840000 So that's one way you can do it. 0:05:42.840000 --> 0:05:46.180000 Or you can manually set the priority yourself. 0:05:46.180000 --> 0:05:50.840000 Spanning tree, VLAN, whatever, priority, and then a value. 0:05:50.840000 --> 0:05:54.760000 The benefit of this bottom command is it actually lets you set the priority 0:05:54.760000 --> 0:05:59.700000 value all the way down to zero if you want to, which is clearly as low 0:05:59.700000 --> 0:06:04.300000 as you can go. The top command, the spanning-tree VLAN root primary, it 0:06:04.300000 --> 0:06:08.780000 will dynamically lower the priority except here's one situation where 0:06:08.780000 --> 0:06:10.360000 it won't work very well. 0:06:10.360000 --> 0:06:14.480000 If the current root bridge out there right now already has a priority 0:06:14.480000 --> 0:06:22.440000 of 4096, that root primary command will not work on your switch unless 0:06:22.440000 --> 0:06:25.760000 your MAC address is lower than his. 0:06:25.760000 --> 0:06:27.720000 So for example, look at this. 0:06:27.720000 --> 0:06:30.920000 What if we had this situation where there's currently a root bridge right 0:06:30.920000 --> 0:06:41.920000 now and he is 4096 and let's say his MAC address was something like this. 0:06:41.920000 --> 0:06:46.300000 And here you are, here's your switch. 0:06:46.300000 --> 0:06:58.780000 You are currently at 32,768 and this is your MAC address, 02117777. 0:06:58.780000 --> 0:07:03.880000 Okay, so if you do the command spanning -tree VLAN, let's just go ahead 0:07:03.880000 --> 0:07:07.060000 and type that in here so we can see what that looks like. 0:07:07.060000 --> 0:07:13.780000 So if on this switch right here, I were to do the command spanning-tree 0:07:13.780000 --> 0:07:18.280000 VLAN, let's say two root primary. 0:07:18.280000 --> 0:07:23.760000 So if I did that command on this switch, then the switch would say, okay, 0:07:23.760000 --> 0:07:27.380000 the current root bridge is this. 0:07:27.380000 --> 0:07:34.880000 Well actually if I make my priority match his 4096, I will actually win 0:07:34.880000 --> 0:07:39.320000 because then our priorities will be the same but my MAC address of 1111 0:07:39.320000 --> 0:07:42.080000 is lower than his MAC address of 222. 0:07:42.080000 --> 0:07:44.420000 So that'll actually work. 0:07:44.420000 --> 0:07:49.060000 But where this command will fail you and not work out so well is something 0:07:49.060000 --> 0:07:54.260000 like this. So let's set it back here for a moment. 0:07:54.260000 --> 0:08:03.580000 Let's say you were back to 32768 and you were something like this, 411111. 0:08:03.580000 --> 0:08:11.480000 Okay, now if we do that command on you, the lowest priority value this 0:08:11.480000 --> 0:08:14.800000 command can give you is 4096. 0:08:14.800000 --> 0:08:20.080000 But in this situation, even that wouldn't be good enough because you're 0:08:20.080000 --> 0:08:28.400000 still 0214, the root bridge is 0212, so he's still going to win. 0:08:28.400000 --> 0:08:32.020000 And this command does not allow you to knock it down anything less than 0:08:32.020000 --> 0:08:38.140000 4096. So for that reason, we'd want to set the value to zero on your switch 0:08:38.140000 --> 0:08:42.080000 to make him the root bridge and the only way to do that is by using the 0:08:42.080000 --> 0:08:47.120000 second command that we saw right here, the one at the bottom that shows 0:08:47.120000 --> 0:08:49.040000 you our priority values. 0:08:49.040000 --> 0:08:54.340000 And we can verify that all of this worked by using either one of these 0:08:54.340000 --> 0:08:56.000000 two commands right here. 0:08:56.000000 --> 0:08:57.380000 So let's take a look. 0:08:57.380000 --> 0:08:59.200000 Let's do an example of this. 0:08:59.200000 --> 0:09:02.940000 So here's the topology I'm going to work with. 0:09:02.940000 --> 0:09:08.920000 You can see that I've got three switches and there's definitely a loop 0:09:08.920000 --> 0:09:11.480000 right now if I didn't have spanning tree running. 0:09:11.480000 --> 0:09:15.100000 So step number one is I'm going to enable rapid spanning tree on all three 0:09:15.100000 --> 0:09:16.340000 of these switches. 0:09:16.340000 --> 0:09:19.000000 Now, because I'm going to do the exact same command rather than bore you 0:09:19.000000 --> 0:09:23.240000 by having you watch me type it in three times in succession, what I'm 0:09:23.240000 --> 0:09:27.800000 going to do is I'm just going to open up a text editor right here. 0:09:27.800000 --> 0:09:31.680000 And I'm just going to type in my commands once on here. 0:09:31.680000 --> 0:09:42.920000 So enable config T spanning dash tree mode rapid dash pbs t end. 0:09:42.920000 --> 0:09:45.860000 All right, so I'm just going to do that and copy and paste that into all 0:09:45.860000 --> 0:09:52.180000 three switches. Right now we can confirm that they're not running rapid 0:09:52.180000 --> 0:10:00.220000 spanning tree. You can type the command show spanning dash tree summary. 0:10:00.220000 --> 0:10:08.760000 Okay, if it says pbs t mode, that means you're not doing rapid spanning 0:10:08.760000 --> 0:10:14.840000 tree. You're doing the much older pre 2004 version of spanning tree. 0:10:14.840000 --> 0:10:19.700000 All right, so let's go ahead and copy and paste this into my switches. 0:10:19.700000 --> 0:10:21.560000 So there's switch one. 0:10:21.560000 --> 0:10:26.320000 There's switch two. 0:10:26.320000 --> 0:10:32.140000 Oh, okay, I guess it would help if I didn't have a spell correct on here. 0:10:32.140000 --> 0:10:38.680000 Rapid pbs t. Thank you text editor for changing pbs t to the word post. 0:10:38.680000 --> 0:10:40.440000 All right, so let's put that in there. 0:10:40.440000 --> 0:10:42.220000 That looks better. 0:10:42.220000 --> 0:10:45.520000 All right, what did it not like? 0:10:45.520000 --> 0:10:46.840000 All right, well, it looks like it took it. 0:10:46.840000 --> 0:10:48.460000 Go back to switch one. 0:10:48.460000 --> 0:10:50.640000 He probably didn't take the command either. 0:10:50.640000 --> 0:10:53.520000 And let's go back to switch three. 0:10:53.520000 --> 0:10:57.660000 All right, so they're all running rapid spanning tree. 0:10:57.660000 --> 0:11:02.240000 And I can confirm that once again with show spanning dash tree summary. 0:11:02.240000 --> 0:11:06.620000 And now we see switches in rapid pbs t mode. 0:11:06.620000 --> 0:11:11.460000 All right, so how do we confirm who the current root bridge is? 0:11:11.460000 --> 0:11:13.280000 Well, there's a couple of ways I could do it. 0:11:13.280000 --> 0:11:16.020000 First of all, you have to do it on a per VLAN basis. 0:11:16.020000 --> 0:11:19.040000 So let's just do it on VLAN one to begin with. 0:11:19.040000 --> 0:11:25.440000 So show spanning dash tree VLAN one. 0:11:25.440000 --> 0:11:32.760000 Okay, and the way that you interpret this output is that this information 0:11:32.760000 --> 0:11:38.880000 is all about who the root bridge is. 0:11:38.880000 --> 0:11:44.340000 And the paragraph below it right here is all information about, whoop, 0:11:44.340000 --> 0:11:47.140000 whatever switch you're on right now. 0:11:47.140000 --> 0:11:51.940000 Okay, and we can see that this switch, which is switch three, is not the 0:11:51.940000 --> 0:11:57.680000 root bridge because we can see his priority is 3279. 0:11:57.680000 --> 0:12:02.640000 All right, well, the priority of the root bridge seems to be 326768. 0:12:02.640000 --> 0:12:07.020000 And we can also see that his MAC address does not match up with the MAC 0:12:07.020000 --> 0:12:08.320000 address of the root. 0:12:08.320000 --> 0:12:14.340000 Now, as it so happens in this particular topology, there are some things 0:12:14.340000 --> 0:12:17.180000 are connected to this that should not be connected to this. 0:12:17.180000 --> 0:12:19.820000 So rather than hunt down that root bridge, because I know right now who 0:12:19.820000 --> 0:12:22.820000 that root bridge is, and that's not somebody we want to get on and mess 0:12:22.820000 --> 0:12:30.360000 around with. So I'm just going to quickly, let's just do it on here. 0:12:30.360000 --> 0:12:33.320000 Interface range, fast E then at zero slash. 0:12:33.320000 --> 0:12:39.640000 Zero slash 20 through 24. 0:12:39.640000 --> 0:12:48.840000 Shut down. Okay, so we need to get rid of those. 0:12:48.840000 --> 0:12:52.140000 And the reason I'm doing this, just in case you're curious, is that if 0:12:52.140000 --> 0:12:55.920000 you notice the graphic and the image on the right, a couple of the routers 0:12:55.920000 --> 0:13:01.700000 that I have actually have some switching modules inside of those routers. 0:13:01.700000 --> 0:13:05.060000 And those switching modules aren't configured exactly the same way as 0:13:05.060000 --> 0:13:06.460000 a normal switch. 0:13:06.460000 --> 0:13:10.900000 And spanning tree output on those modules looks totally different than 0:13:10.900000 --> 0:13:16.240000 normal output. So I'm shutting down the ports that lead to those modules. 0:13:16.240000 --> 0:13:20.180000 So now the only switches we'll have are the three switches shown in my 0:13:20.180000 --> 0:13:22.260000 picture. All right, so let's take a look again. 0:13:22.260000 --> 0:13:24.560000 We're on switch two this time, it doesn't matter. 0:13:24.560000 --> 0:13:27.340000 Show spanning tree VLAN one. 0:13:27.340000 --> 0:13:30.580000 All right, this is a great opportunity because look at this. 0:13:30.580000 --> 0:13:34.020000 It actually says this bridge is the root. 0:13:34.020000 --> 0:13:36.720000 So that's what you would see if the switch you happen to be on, if you 0:13:36.720000 --> 0:13:40.580000 were lucky, and the switch you got on, is the root bridge right now. 0:13:40.580000 --> 0:13:43.520000 Okay, so that is switch two. 0:13:43.520000 --> 0:13:45.460000 So we know switch two is the root. 0:13:45.460000 --> 0:13:48.840000 Okay, what are some other ways that we could tell that? 0:13:48.840000 --> 0:13:53.700000 We can do the command show spanning dash tree root. 0:13:53.700000 --> 0:13:57.840000 Now this is, if you have more than one VLAN, you'll see a listing of VLANs 0:13:57.840000 --> 0:14:00.540000 in here on different lines. 0:14:00.540000 --> 0:14:04.000000 They'll show you VLAN, it'll show you the root ID. 0:14:04.000000 --> 0:14:07.460000 And here's a quick and easy way to tell whether you are the root or not. 0:14:07.460000 --> 0:14:09.120000 Look at the root cost. 0:14:09.120000 --> 0:14:11.440000 Now in this video, I haven't talked about cost. 0:14:11.440000 --> 0:14:15.320000 But I'll just tell you right now, if your root cost is zero, that means 0:14:15.320000 --> 0:14:19.620000 that for that particular VLAN, you are the root. 0:14:19.620000 --> 0:14:22.720000 For example, let's compare that against switch number one. 0:14:22.720000 --> 0:14:26.940000 Show spanning dash tree root. 0:14:26.940000 --> 0:14:30.580000 See, he has a non-zero number in there. 0:14:30.580000 --> 0:14:32.360000 So that means he is not the root. 0:14:32.360000 --> 0:14:35.900000 Similarly, if we do the command that we saw before, show spanning tree 0:14:35.900000 --> 0:14:41.920000 VLAN one, we can see that the MAC address of the root is different than 0:14:41.920000 --> 0:14:43.640000 his MAC address. 0:14:43.640000 --> 0:14:46.580000 And here we can see why he lost, right? 0:14:46.580000 --> 0:14:50.520000 Switch one has the exact same priority as whoever the root bridge is, 0:14:50.520000 --> 0:14:52.260000 which we just discovered was switch two. 0:14:52.260000 --> 0:14:53.840000 But look at the MAC addresses. 0:14:53.840000 --> 0:14:57.800000 0014F, that all matches up. 0:14:57.800000 --> 0:15:06.540000 F2, F2, but then we have F2 one, which is lower than F2 four. 0:15:06.540000 --> 0:15:08.520000 So that's why switch two was the winner. 0:15:08.520000 --> 0:15:12.500000 Now I said, hey, we want to deterministically set the root. 0:15:12.500000 --> 0:15:16.760000 Okay, well, let's go ahead and on this guy, use our first command. 0:15:16.760000 --> 0:15:22.520000 Spanning dash tree VLAN one root primary. 0:15:22.520000 --> 0:15:27.500000 So with this command, I do not have to set any values for priority. 0:15:27.500000 --> 0:15:34.320000 And now if I look at that same output again, now we see this bridges the 0:15:34.320000 --> 0:15:40.120000 root and notice it lowered his bridge priority down to 24576. 0:15:40.120000 --> 0:15:43.340000 And remember, we add in the system ID, which is the VLAN number, which 0:15:43.340000 --> 0:15:49.060000 is VLAN one. So that gives him a total priority of 2457. 0:15:49.060000 --> 0:15:52.700000 So that was one way to do it. 0:15:52.700000 --> 0:15:56.900000 And that was the spanning tree VLAN one root primary. 0:15:56.900000 --> 0:15:59.100000 Let's go over to switch three. 0:15:59.100000 --> 0:16:01.920000 What if I want to make switch three the root bridge? 0:16:01.920000 --> 0:16:06.580000 Show spanning dash tree VLAN one. 0:16:06.580000 --> 0:16:10.180000 So right now he's not the root because the MAC address of the root and 0:16:10.180000 --> 0:16:12.340000 his MAC address are totally different. 0:16:12.340000 --> 0:16:16.540000 So rather than do spanning tree VLAN primary, I'm going to say spanning 0:16:16.540000 --> 0:16:21.740000 dash tree VLAN one priority. 0:16:21.740000 --> 0:16:26.280000 And if I do a question mark here, you can see I can do from zero to 61 0:16:26.280000 --> 0:16:28.660000 440. I'm going to set to zero. 0:16:28.660000 --> 0:16:36.640000 And now this switch will be the root bridge. 0:16:36.640000 --> 0:16:38.980000 This bridge is the root. 0:16:38.980000 --> 0:16:43.280000 Now the last thing I want to show you is edge ports. 0:16:43.280000 --> 0:16:46.260000 So right now we are on switch number three. 0:16:46.260000 --> 0:16:48.380000 And notice that switch number three is connected to a couple of routers 0:16:48.380000 --> 0:16:51.580000 over here. He's connected router three and router four. 0:16:51.580000 --> 0:16:55.840000 Now he's connected to router three on fast ethernet zero three, which 0:16:55.840000 --> 0:16:57.500000 shows up right here. 0:16:57.500000 --> 0:17:01.680000 Point to point means it's a full duplex link, but there's no indication 0:17:01.680000 --> 0:17:05.880000 here that any of these links are edge ports. 0:17:05.880000 --> 0:17:09.840000 So if we want to make switch three recognize that interface fast ethernet 0:17:09.840000 --> 0:17:15.360000 zero three is an edge port, we have to enable spanning tree port fast. 0:17:15.360000 --> 0:17:21.020000 We get a little warning because we should not enable that on interfaces 0:17:21.020000 --> 0:17:23.340000 connecting to other switches. 0:17:23.340000 --> 0:17:25.720000 And now we will look at the same output. 0:17:25.720000 --> 0:17:29.660000 Now it says edge. 0:17:29.660000 --> 0:17:33.020000 And in this video I haven't talked about well why does rapid spanning 0:17:33.020000 --> 0:17:36.880000 tree care? Why does it care whether a port is an edge port or not? 0:17:36.880000 --> 0:17:41.000000 So if you look at some of my other videos or even videos from other instructors 0:17:41.000000 --> 0:17:46.080000 you will learn that rapid spanning tree in certain circumstances treats 0:17:46.080000 --> 0:17:50.980000 edge ports a little bit differently when it starts doing things than non 0:17:50.980000 --> 0:17:56.280000 edge ports. So most of the ports we see in this output are non edge except 0:17:56.280000 --> 0:18:01.520000 for fast ethernet zero three where I supply the port fast command. 0:18:01.520000 --> 0:18:05.140000 So that concludes this video. 0:18:05.140000 --> 0:18:06.260000 I hope you found it useful.