WEBVTT 1 00:00.000 --> 00:04.000 All right, well as always be sure to attempt this lab on your own before 2 00:04.000 --> 00:07.200 jumping into the solution, but once you're done, especially if you got hung up 3 00:07.200 --> 00:07.320 on 4 00:07.320 --> 00:11.440 anything, well it's time to jump in and take a look at it together. So our 5 00:11.440 --> 00:17.680 topology is still up there in the top right. We have the need to deploy, first 6 00:17.680 --> 00:23.160 of all, static mode on over here between switch one and the axis switch, LACP 7 00:23.160 --> 00:28.040 between switch two and the axis switch, and then LACP between switches one and 8 00:28.040 --> 00:32.520 two, and we're going to use that max bundles command in order to make sure WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:28.040 --> 00:32.520 two, and we're going to use that max bundles command in order to make sure 9 00:32.520 --> 00:36.320 that everything comes together. And I guess that is also going to be bundled 10 00:36.320 --> 00:42.920 together. We were given port channel IDs of 15 and 25, and we weren't actually 11 00:42.920 --> 00:47.360 given an ID for this top one. Hey, freedom, right? So we can call whatever we 12 00:47.360 --> 00:52.560 want. I'll just go with the classic port channel 10 in this configuration. So 13 00:52.560 --> 00:57.040 let's go ahead and do this. I'm going to get, well first of all, we can 14 00:57.040 --> 00:57.320 reference 15 00:57.320 --> 01:02.600 the diagram, whoops, show CDP neighbor, we reference the diagram, but here we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:57.320 --> 01:02.600 the diagram, whoops, show CDP neighbor, we reference the diagram, but here we 16 01:02.600 --> 01:02.720 can 17 01:02.720 --> 01:07.880 see exactly which ports we need to be concerned with. And so I'm going to get 18 01:07.880 --> 01:14.360 on to the here and say config T interface range gig one slash zero through one. 19 01:14.360 --> 01:20.200 And to configure a static port channel, it's going to be channel group mode. 20 01:20.200 --> 01:21.520 Hold 21 01:21.520 --> 01:26.940 up, we've got to add the number channel group 15 mode on. Alright, and then we 22 01:26.940 --> 01:27.040 'll 23 01:27.040 --> 01:30.520 do a no shut here just in case. And then I'm going to go over to the access WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 01:27.040 --> 01:30.520 do a no shut here just in case. And then I'm going to go over to the access 24 01:30.520 --> 01:31.600 switch 25 01:31.600 --> 01:41.680 into range gig one slash zero through one. And channel group 15 mode on just 26 01:41.680 --> 01:45.200 remember those channel group IDs don't actually have to match, but it's kind of 27 01:45.200 --> 01:49.920 nice when they do helps us keep track of things. So if I do a so CDP neighbor 28 01:49.920 --> 01:55.280 now, we should see that yes, which one is out one zero through one one. So now 29 01:55.280 --> 01:55.320 I 30 01:55.320 --> 01:59.160 can use that command show ether channel summary. Hopefully we see both of those 31 01:59.160 --> 02:03.400 ports in online state and we do just keep in mind that doesn't mean anything WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 31 01:59.160 --> 02:03.400 ports in online state and we do just keep in mind that doesn't mean anything 32 02:03.400 --> 02:03.560 for 33 02:03.560 --> 02:08.280 the other side when we're using static ether channels show ether channel 34 02:08.280 --> 02:08.720 summary. 35 02:08.720 --> 02:16.480 And it is good to go. Alright, so lab task number one is down on the lab task 36 02:16.480 --> 02:20.920 number two, which is LACP between these two switches. We'll do a show CDP 37 02:20.920 --> 02:21.440 neighbor. 38 02:21.440 --> 02:27.360 Make sure we know that's two one and two two config T and range gig two slash 39 02:27.360 --> 02:27.680 one 40 02:27.680 --> 02:35.040 through two channel group. And this is going to be 25. And now we're using LACP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 02:27.680 --> 02:35.040 through two channel group. And this is going to be 25. And now we're using LACP 41 02:35.040 --> 02:35.040 . 42 02:35.040 --> 02:41.520 So we just need to make sure one side is active. I'll do active here on switch 43 02:41.520 --> 02:48.320 two and then down here on the access switch, and range gig to slash one and two 44 02:48.320 --> 02:50.240 channel 45 02:50.240 --> 02:55.800 group 25 mode. And I could do passive here. I'll just go and do active. You 46 02:55.800 --> 02:55.920 know, 47 02:55.920 --> 03:00.480 that way it's active on both sides. It's more likely to come up if I forgot WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 47 02:55.920 --> 03:00.480 that way it's active on both sides. It's more likely to come up if I forgot 48 03:00.480 --> 03:00.600 what 49 03:00.600 --> 03:05.400 I put on the other side, I suppose. But either way, show ether channel summary. 50 03:05.400 --> 03:10.960 Let's see what's going on. So we do see port channel 25 is running LECP and 51 03:10.960 --> 03:11.160 both 52 03:11.160 --> 03:15.110 of those ports are online. Let's confirm it looks that way with switch to again 53 03:15.110 --> 03:15.480 . 54 03:15.480 --> 03:20.520 This part is usually effort that's not needed because it's running LACP. It 55 03:20.520 --> 03:20.920 would not be 56 03:20.920 --> 03:25.110 running on one side if it wasn't running on the other. And indeed it is. So 57 03:25.110 --> 03:25.320 that's 58 03:25.320 --> 03:30.410 lab task number two lab test number three involves configuring LCP up here. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 03:25.320 --> 03:30.410 lab task number two lab test number three involves configuring LCP up here. So 59 03:30.410 --> 03:30.840 I'm going 60 03:30.840 --> 03:36.480 to get onto those interfaces we did during the lab gig zero slash zero through 61 03:36.480 --> 03:37.160 three. 62 03:37.160 --> 03:42.680 I'm going to say channel group. And again, we've got the freedom to give our 63 03:42.680 --> 03:43.240 own ID 64 03:43.240 --> 03:49.420 here. I'm going to say mode active. Go over to switch to pretty much the exact 65 03:49.420 --> 03:49.640 same 66 03:49.640 --> 03:59.400 thing. Zero through three channel group 10 mode active or passive either way. 67 03:59.400 --> 04:07.300 So now let's do a show ether channel summary. All right, so caught it while it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 03:59.400 --> 04:07.300 So now let's do a show ether channel summary. All right, so caught it while it 68 04:07.300 --> 04:07.720 's waiting. 69 04:07.720 --> 04:11.360 If we get a W like this, it's waiting to be aggregated. So let's give it a 70 04:11.360 --> 04:11.880 moment. 71 04:11.880 --> 04:14.700 Looks like we might have one of our ports in a shutdown state. Let's see if 72 04:14.700 --> 04:15.040 that waiting 73 04:15.040 --> 04:20.930 port came online and it did. Good. All right. So show interface gig zero zero. 74 04:20.930 --> 04:21.680 All right. 75 04:21.680 --> 04:24.910 Yeah, it's actually in a shutdown state. I think that's left over from the lab. 76 04:24.910 --> 04:25.400 We'll 77 04:25.400 --> 04:30.440 do a no shut here. That was part of the hot standby demonstration. So now we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 04:25.400 --> 04:30.440 do a no shut here. That was part of the hot standby demonstration. So now we 78 04:30.440 --> 04:31.080 should see 79 04:31.080 --> 04:36.710 that all four of these are part of the port channel. It's waiting to come 80 04:36.710 --> 04:37.680 online. And 81 04:37.680 --> 04:44.620 there it goes. Oh, it's not enabled on the remote port. All right. Well, show 82 04:44.620 --> 04:44.880 wait, is 83 04:44.880 --> 04:52.280 it shut down here too? Oh, it is. All right. So again, in a lab environment, 84 04:52.280 --> 04:52.700 the involving 85 04:52.700 --> 04:57.300 virtual hardware, unfortunately, if you shut down one side, it doesn't done the 86 04:57.300 --> 04:58.100 other. 87 04:58.100 --> 05:02.300 And I forgot to shut it down on both, which is exactly what's required. So let WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 04:58.100 --> 05:02.300 And I forgot to shut it down on both, which is exactly what's required. So let 88 05:02.300 --> 05:02.720 's see if 89 05:02.720 --> 05:07.740 it's online now. All right. And it is all four of our ports are online, which 90 05:07.740 --> 05:08.300 means they're 91 05:08.300 --> 05:14.870 online on the other side too. So now we were told to only allow two of these 92 05:14.870 --> 05:15.860 ports to be 93 05:15.860 --> 05:19.590 in the bundle. That is a command that must go on the port channel interface 94 05:19.590 --> 05:20.680 itself. So 95 05:20.680 --> 05:25.960 again, on an interface port channel 10. And then I do the LACP max bundle 96 05:25.960 --> 05:26.860 command with 97 05:26.860 --> 05:36.430 a two. And I'm going to do that on the other side as well. LACP max bundle of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 97 05:26.860 --> 05:36.430 a two. And I'm going to do that on the other side as well. LACP max bundle of 98 05:36.430 --> 05:38.440 two. So now 99 05:38.440 --> 05:43.620 we should see that we have those hot standby starting to show up. All right. So 100 05:43.620 --> 05:44.080 we're still 101 05:44.080 --> 05:48.490 again, if we go too fast, we catch it waiting. Now it's coming online. Do the 102 05:48.490 --> 05:49.200 command one 103 05:49.200 --> 05:54.980 more time. Good. So now we see two ports are in a port channel state. The other 104 05:54.980 --> 05:55.640 two ports 105 05:55.640 --> 06:00.260 are in a hot standby state. This is where I can demo again, getting on to get WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 05:55.640 --> 06:00.260 are in a hot standby state. This is where I can demo again, getting on to get 106 06:00.260 --> 06:00.980 zero zero 107 06:00.980 --> 06:04.720 and doing a shot, because that virtual hardware I'm going to come over here and 108 06:04.720 --> 06:05.300 do the same 109 06:05.300 --> 06:11.100 thing. So now that we've lost gig zero slash zero wrong switch. Now that we've 110 06:11.100 --> 06:11.400 lost gig 111 06:11.400 --> 06:17.400 zero slash zero before it was in a state here, here's a quick pop question. 112 06:17.400 --> 06:17.840 Which one of 113 06:17.840 --> 06:23.950 these? Whoops, which one of the come on which one of these is going to become 114 06:23.950 --> 06:24.600 part of the 115 06:24.600 --> 06:28.970 bundle. And so think through what we said, which one's prioritized? Is it lower 116 06:28.970 --> 06:29.480 ? Is it 117 06:29.480 --> 06:32.500 higher? If it's layer two, it's usually lower? If it's layer three, it's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 06:29.480 --> 06:32.500 higher? If it's layer two, it's usually lower? If it's layer three, it's 118 06:32.500 --> 06:33.320 usually the higher 119 06:33.320 --> 06:37.530 number wins. And so in our case, the lower number will win, because this is 120 06:37.530 --> 06:38.380 layer two. 121 06:38.380 --> 06:44.730 So this our expectation is going to be that gig zero two becomes our next one. 122 06:44.730 --> 06:45.080 And so 123 06:45.080 --> 06:50.360 if I do a show, either channel summary, let's see if gig zero two was picked. 124 06:50.360 --> 06:51.120 And indeed 125 06:51.120 --> 06:55.500 it was. So one and two are now part of the bundle, gig zero zero is down for 126 06:55.500 --> 06:56.480 some reason. 127 06:56.480 --> 07:01.040 We know why. And then gig zero three continues to remain in a hot standby state WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 127 06:56.480 --> 07:01.040 We know why. And then gig zero three continues to remain in a hot standby state 128 07:01.040 --> 07:01.360 . So that 129 07:01.360 --> 07:04.720 is this lab challenge. This is a great environment with many different links 130 07:04.720 --> 07:05.560 between switches 131 07:05.560 --> 07:10.230 to just play around with these can play around with PGP if you want to, you can 132 07:10.230 --> 07:10.960 , you know, 133 07:10.960 --> 07:14.290 see that again, we just did the hot standby. But we've just got the ability to 134 07:14.290 --> 07:14.840 do active 135 07:14.840 --> 07:18.360 and passive configurations. So definitely take the time to make sure we've got 136 07:18.360 --> 07:18.800 all this 137 07:18.800 --> 07:22.480 configuration down before moving on. Otherwise, if I hope this has been 138 07:22.480 --> 07:23.760 informative for you, 139 07:23.760 --> 07:24.840 and I'd like to thank you for viewing. 140 07:24.840 --> 07:43.500 Thank you for watching.