1 00:00:15,270 --> 00:00:20,040 In this lab, we are going to continue configuring our campus network. 2 00:00:22,830 --> 00:00:31,950 We've been asked to use both CDP or Cisco Discovery Protocol and LLDP or Link-Layer Discovery Protocol 3 00:00:32,340 --> 00:00:34,130 to verify links. 4 00:00:34,200 --> 00:00:41,330 So we need to check the links between the devices and confirm that the links are correctly configured 5 00:00:41,340 --> 00:00:48,180 per the diagram. We need to verify which ports are forwarding and blocking in spanning tree 6 00:00:48,330 --> 00:00:54,060 and then we need to optimize spanning tree with core 1 being the root for odd VLANs and core 7 00:00:54,060 --> 00:00:57,360 2 being the root for even VLANs. 8 00:00:57,360 --> 00:01:04,290 So have a look at this topology package trace and makes this easy which links are currently blocking 9 00:01:04,680 --> 00:01:06,150 in spanning tree. 10 00:01:06,150 --> 00:01:14,190 Can you see which ports are blocking notice on call one of these ports or blocking and spanning tree 11 00:01:14,700 --> 00:01:15,860 on access 1. 12 00:01:15,990 --> 00:01:21,250 This port is blocking in spanning tree. Now think about the problem. 13 00:01:21,450 --> 00:01:30,010 If a large amount of traffic was sent from many PCs in VLAN 10 on this access switch to this server. 14 00:01:30,030 --> 00:01:39,620 How would traffic flow? Traffic would have to go across this uplink to Core 2 and then use this single 15 00:01:40,010 --> 00:01:45,830 gigabit 1 0 23 link to core 1 to get to the server. 16 00:01:45,830 --> 00:01:53,180 Now imagine that you had many servers here as well as many PCs on switch 2 and switch 3 trying to 17 00:01:53,180 --> 00:01:59,850 get to a group of servers on the left end side. Let's say they were moving large files. 18 00:01:59,850 --> 00:02:07,680 How would traffic flow? So traffic from all of these PCs in VLAN 10 20 and 30 would end up going 19 00:02:07,680 --> 00:02:15,120 via core 2 and then going across the single link to core 1 to get to these servers. 20 00:02:15,120 --> 00:02:22,590 These links are being blocked by spanning tree so no traffic will go from VLAN 20 to core 1 all the 21 00:02:22,590 --> 00:02:29,220 traffic will go to core 2 to get to the servers on the left end side. 22 00:02:29,550 --> 00:02:35,480 That's gonna be a problem because we're gonna have a bottleneck or an issue on gigabit 1 0 23 00:02:35,490 --> 00:02:42,600 23 this is a gigabit port but all of these uplinks are also gigabit ports and PCs are sending 24 00:02:42,600 --> 00:02:51,000 traffic at gig speeds. So if you have 100 PCs sending traffic to multiple servers this gigabit 25 00:02:51,000 --> 00:02:55,530 1 0 23 link is gonna be over saturated. 26 00:02:55,530 --> 00:02:59,300 In other words, there's gonna be too much traffic for that single link. 27 00:02:59,610 --> 00:03:06,290 So we want to optimize our spanning tree and this topology and ensure that core 1 is the route for odd VLANs 28 00:03:06,930 --> 00:03:09,930 and core2 is the root for even VLANs. 29 00:03:10,020 --> 00:03:18,120 In other words core 1 will be the root for VLAN 1 VLAN 10 and VLAN 30, core 2 will be the root 30 00:03:18,330 --> 00:03:21,870 for VLAN 20 and VLAN 100. 31 00:03:22,110 --> 00:03:26,150 So we're going to split traffic across the core switches. 32 00:03:26,250 --> 00:03:32,250 You also need to configure ether channel on the core switches so that we don't have one of these links 33 00:03:32,250 --> 00:03:39,320 blocking, both of these ports should be forwarding. So to do that we're gonna use ether channel. 34 00:03:39,400 --> 00:03:45,070 We also need to configure IP addresses on the core switches to enable inter VLAN routing. 35 00:03:45,070 --> 00:03:47,150 Here are the IP addresses of core 1. 36 00:03:47,200 --> 00:03:53,320 Here are the IP addresses of Core 2 and you need to configure IP addresses on the access switches in 37 00:03:53,320 --> 00:03:56,230 VLAN 1. In the next lab 38 00:03:56,230 --> 00:04:03,550 after this we'll configure IP addresses in the PCs and verify connectivity in our campus network 39 00:04:03,610 --> 00:04:07,570 to ensure that things are working right. 40 00:04:07,630 --> 00:04:09,520 So this is a big lab. 41 00:04:09,520 --> 00:04:11,340 Are you able to do it yourself 42 00:04:11,470 --> 00:04:18,490 Download the attached packet tracer file and try and configure the lab yourself or you can watch 43 00:04:18,490 --> 00:04:21,910 me in the next video complete this lab. 44 00:04:21,910 --> 00:04:25,660 Best way to learn is to try things so try it. 45 00:04:25,660 --> 00:04:26,440 If you get stuck, 46 00:04:26,440 --> 00:04:35,990 Have a look at to the videos to help you.