1 00:00:16,010 --> 00:00:22,940 So let's have a look at spanning-tree show spanning-tree VLAN 1, notice we see a difference 2 00:00:22,940 --> 00:00:26,070 here we see a port channel. 3 00:00:26,510 --> 00:00:36,130 One thing to notice here is notice ports such as gigabit 1 0 1 and 1 0 2 1 0 3 are point to point spanning 4 00:00:36,140 --> 00:00:37,440 tree links. 5 00:00:37,490 --> 00:00:38,180 Whereas the port 6 00:00:38,180 --> 00:00:41,960 channel is a shared spanning tree link. 7 00:00:41,960 --> 00:00:43,640 Now for the real world, 8 00:00:44,030 --> 00:00:50,830 typically once you've put interfaces into the port-channel you do the configuration on the port-channel. 9 00:00:50,840 --> 00:00:57,830 However, if you have problems do the configuration in the port channel and then verify that the configuration 10 00:00:57,830 --> 00:01:00,970 has also been applied to the physical interfaces. 11 00:01:01,160 --> 00:01:06,920 If it's not applied to the physical interfaces do the config on both the port channel and the physical 12 00:01:06,920 --> 00:01:11,370 interfaces to ensure that the configuration is correct 13 00:01:11,480 --> 00:01:18,110 but typically you only need to do the configuration on the port-channel. So I'll show you that here when 14 00:01:18,110 --> 00:01:25,100 I do the configuration on the physical interface it's not applied to the port-channel but configuration 15 00:01:25,100 --> 00:01:30,850 applied to the port-channel is pushed down to physical interfaces. 16 00:01:31,070 --> 00:01:32,470 That's how it should work. 17 00:01:32,630 --> 00:01:39,700 Sometimes in the real world, you'll have problems with that. To optimize spanning tree, 18 00:01:40,640 --> 00:01:49,610 what we want to do on those ports is specify spanning tree link type point to point that we'll make 19 00:01:49,940 --> 00:02:00,770 rapid spanning-tree converge quicker shared links are typically used down to hosts or to hubs but we've 20 00:02:00,770 --> 00:02:02,840 got switches here. 21 00:02:02,840 --> 00:02:08,900 So we wanna make the spanning-tree link-type point to point to make it converge quicker. 22 00:02:11,800 --> 00:02:15,910 So show spanning tree VLAN 1. 23 00:02:22,440 --> 00:02:30,100 Now notice I did the configuration on the physical interfaces what I need to do actually is do that 24 00:02:30,160 --> 00:02:40,120 on the port-channel. So spanning tree link type point to point and then I'll do something similar on 25 00:02:40,120 --> 00:02:42,350 this side interface port, 26 00:02:42,610 --> 00:02:51,480 channel 1 spanning-tree link-type point to point and let's see if that's made a difference. 27 00:02:51,640 --> 00:03:00,430 So show spanning-tree VLAN 1 that looks better notice the port channel is showing us point to point. 28 00:03:00,430 --> 00:03:12,370 Okay, so this looks good on this side show spanning-tree VLAN 1 notice on switch 2 no ports are blocking, 29 00:03:13,000 --> 00:03:19,860 previously one of the ports on switch 2 was blocking for VLAN 1. 30 00:03:20,010 --> 00:03:27,750 In other words, previously gigabit 1 0 24 was blocking but it's not blocking at the moment because 31 00:03:27,750 --> 00:03:31,000 that port is part of the port channel. 32 00:03:31,050 --> 00:03:39,480 Notice also the cost of the port channel is lower than other physical interfaces because this is a better 33 00:03:39,900 --> 00:03:41,190 interface. 34 00:03:41,190 --> 00:03:50,130 It's got 2 gigabit ports that make up the channel rather than just a single gigabit port. On this side 35 00:03:50,130 --> 00:03:55,060 show spanning tree VLAN 10. 36 00:03:55,080 --> 00:04:03,150 Now notice here we don't see VLAN 10 propagated across the port channel. 37 00:04:03,150 --> 00:04:11,040 Again, if you have problems like this where configuration is done on the physical interface but is not 38 00:04:11,040 --> 00:04:16,450 shown on the port-channel, type these commands on the port-channel. 39 00:04:16,740 --> 00:04:23,640 So typically once you put your interfaces in a port-channel you do the configuration on the port-channel. 40 00:04:24,240 --> 00:04:33,240 Interface port channel 1, switch port mode trunk, switch port trunk we have to separate encapsulation 41 00:04:33,240 --> 00:04:39,000 first, so switch port trunk encapsulation dot1q switch port mode trunk. 42 00:04:44,970 --> 00:04:50,040 So notice now the configuration is shown on the port-channel 43 00:04:55,480 --> 00:05:02,650 and notice when I use the command show spanning-tree VLAN 10, I still don't see the port-channel because 44 00:05:02,680 --> 00:05:11,220 on this side we're getting an error with inconsistent port-channel information. We have to configure the 45 00:05:11,230 --> 00:05:14,920 commands on the port channel. So interface port 46 00:05:14,920 --> 00:05:23,820 channel 1, switch port trunk encapsulation, dot1q switch port mode 47 00:05:23,890 --> 00:05:24,430 trunk. 48 00:05:27,490 --> 00:05:34,940 So we need to ensure that we have the commands on the port-channel as well as on the physical interface. 49 00:05:34,960 --> 00:05:42,730 Once you add your physical interfaces to the port-channel, you do your configuration on the port-channel 50 00:05:43,030 --> 00:05:51,820 rather than on the physical interfaces. So let's verify the port-channel by using these show interfaces 51 00:05:51,820 --> 00:05:52,180 port- 52 00:05:52,180 --> 00:05:54,540 channel 1 status command. 53 00:05:54,550 --> 00:05:58,890 Notice we told at the moment that the port channel is not connected. 54 00:06:00,010 --> 00:06:04,180 So what I'll do is shut the interfaces down. 55 00:06:04,180 --> 00:06:07,900 This is one thing to remember with port-channel. 56 00:06:07,900 --> 00:06:14,610 It's better to make all your changes while the interfaces are shut down and then no shut them 57 00:06:14,650 --> 00:06:16,810 once you've completed your changes. 58 00:06:17,200 --> 00:06:26,830 If you have any inconsistency, shut the interfaces down and bring them up again to double check things. 59 00:06:26,830 --> 00:06:36,020 Okay, so let's confirm the configuration, on switch 1 that looks good, on switch 2. 60 00:06:36,340 --> 00:06:39,380 We need to make sure that everything is the same. 61 00:06:39,640 --> 00:06:41,920 So both sides look good there. 62 00:06:41,920 --> 00:06:44,170 This configuration is configured on both sides 63 00:06:47,310 --> 00:06:57,770 and the physical interfaces match that configuration on both sides. So show spanning-tree VLAN 1, 64 00:06:58,510 --> 00:06:58,850 port- 65 00:06:58,850 --> 00:07:08,740 channel is forwarding so that's good, show spanning-tree VLAN 1, at the moment 66 00:07:08,750 --> 00:07:14,090 we still have a status of learning that should hopefully go to forwarding very soon. 67 00:07:14,090 --> 00:07:14,900 There you go, 68 00:07:14,900 --> 00:07:15,590 it's forwarding. 69 00:07:18,470 --> 00:07:19,580 Show ether channel, 70 00:07:22,410 --> 00:07:32,260 port-channel shows us that the interfaces are active. Show spanning-tree VLAN 10 notice now we 71 00:07:32,260 --> 00:07:38,320 can see that VLAN 10 is forwarding on the port-channel. 72 00:07:38,320 --> 00:07:49,360 Same is true for VLAN 20, same is true for VLAN 30 and the same is true for VLAN 100. On this side 73 00:07:49,450 --> 00:07:56,980 show spanning-tree or VLAN 10 still needs to go to forwarding on this side. 74 00:07:56,980 --> 00:08:05,450 So we need to just give it some time but you can see there is an example, 100 is forwarding, VLAN 1 is 75 00:08:05,450 --> 00:08:13,400 forwarding, VLAN 10 is now forwarding, VLAN 20 is now forwarding and VLAN 30 is now forwarding. 76 00:08:15,360 --> 00:08:26,270 So on all VLANs on both sides, the switches are forwarding on all ports this is what you want to have 77 00:08:26,510 --> 00:08:32,780 in the core of your network, you don't want to have your core switches blocking, blocking ports should 78 00:08:32,780 --> 00:08:42,230 be on the access switches. So as an example on access 1 shows spanning-tree VLAN 1, one of the ports 79 00:08:42,230 --> 00:08:47,830 is blocking and we know which port is blocking, it's gigabit 1024 80 00:08:48,380 --> 00:08:56,630 and the reason why is that we've made core 1 the route, core 2 is the backup route. So this port should 81 00:08:56,630 --> 00:09:06,270 be blocking. What about for VLAN 10? This port is also blocking, VLAN 100, 23 is blocking 82 00:09:06,570 --> 00:09:16,460 because we made core 2 the route. Now we saw the LEDs go orange but they've now gone back to green because 83 00:09:16,460 --> 00:09:24,530 packet tracer has updated the spanning-tree network so again we can see that the switch is forwarding 84 00:09:25,520 --> 00:09:33,080 on all VLANs. So as I demonstrated in this video you can have problems if there's a mismatch or mis 85 00:09:33,080 --> 00:09:40,580 configuration between the port channel and the physical interfaces. The recommendation is to make sure 86 00:09:40,970 --> 00:09:52,400 that the configuration is the same on both sides make sure that the configuration of both the logical 87 00:09:52,400 --> 00:09:53,330 interface. 88 00:09:53,330 --> 00:10:01,640 In other words, the port channel and the physical interfaces are the same on both sides. So make sure 89 00:10:01,640 --> 00:10:14,180 that this matches this, but also make sure that this matches the configuration of the port-channel on 90 00:10:14,180 --> 00:10:17,410 the same switch as well as on the other switch. 91 00:10:17,900 --> 00:10:21,390 So, essentially everything should be a mirror image. 92 00:10:21,620 --> 00:10:29,430 Make sure that this matches this, makes sure that this matches this. 93 00:10:29,720 --> 00:10:37,880 If you have problems like I had here shut the physical interfaces down confirm all the configuration 94 00:10:38,240 --> 00:10:41,280 and then no shut the physical interfaces. 95 00:10:41,280 --> 00:10:46,240 Hope that helps you for both the exam and for the real world.