WEBVTT 1 00:00.000 --> 00:05.950 In a real world network, we are absolutely going to want to optimize our access 2 00:05.950 --> 00:07.240 layer environment 3 00:07.240 --> 00:11.120 by performing these configurations on the distribution switch. 4 00:11.120 --> 00:15.240 The goal is going to be to divide our VLANs up and load balance that way 5 00:15.240 --> 00:16.240 because we don't 6 00:16.240 --> 00:20.030 want to block the same link for all of the VLANs or that link will never get 7 00:20.030 --> 00:20.560 used and 8 00:20.560 --> 00:23.160 the other one is likely going to get overwhelmed. 9 00:23.160 --> 00:30.320 So if we have VLANs 10 through 19, we could do an evens and odds kind of split. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:23.160 --> 00:30.320 So if we have VLANs 10 through 19, we could do an evens and odds kind of split. 10 00:30.320 --> 00:38.100 So we could say 11, 13, 15, 17 and 19 for the switch on the left and then VLANs 11 00:38.100 --> 00:39.800 10, 12, 12 00:39.800 --> 00:43.800 14, 16 and 18 on the right. 13 00:43.800 --> 00:52.120 This is going to define which VLANs I am the root for and also the FHRP active. 14 00:52.120 --> 00:57.510 And so whether we're running VRRP or HSRP either way, it's going to be the same 15 00:57.510 --> 00:57.720 and then 16 00:57.720 --> 01:02.360 we'll do the same thing over on this side with us having root and active WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:57.720 --> 01:02.360 we'll do the same thing over on this side with us having root and active 17 01:02.360 --> 01:03.240 configured 18 01:03.240 --> 01:05.480 for these even VLANs. 19 01:05.480 --> 01:09.650 Now how you split up the VLANs doesn't matter if you did 10 through 14 and 15 20 01:09.650 --> 01:10.120 through 21 01:10.120 --> 01:12.200 19, that would be perfectly fine. 22 01:12.200 --> 01:16.820 Again, our assumption, it's truly an assumption is that every VLAN has about 23 01:16.820 --> 01:17.800 the same amount 24 01:17.800 --> 01:19.800 of traffic flowing through it. 25 01:19.800 --> 01:24.040 If we know that VLANs 17 and 19 are heavier than the rest, then we'd want to 26 01:24.040 --> 01:24.720 split those 27 01:24.720 --> 01:25.720 up. 28 01:25.720 --> 01:28.600 But in this example, we weren't given that information. 29 01:28.600 --> 01:34.430 So at this point, we will see that the VLANs here, the odd VLANs will block WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 01:28.600 --> 01:34.430 So at this point, we will see that the VLANs here, the odd VLANs will block 30 01:34.430 --> 01:35.360 this link and 31 01:35.360 --> 01:40.080 then the even VLANs will block the link over here. 32 01:40.080 --> 01:43.800 And that will mean that the even traffic flows out this way. 33 01:43.800 --> 01:48.950 I guess from the client side, the even VLANs will flow this way and land on 34 01:48.950 --> 01:49.720 their own 35 01:49.720 --> 01:50.720 active. 36 01:50.720 --> 01:55.930 The odd traffic will flow out this way, land on the SVI for their traffic and 37 01:55.930 --> 01:56.600 we will be 38 01:56.600 --> 01:59.480 very efficient here. 39 01:59.480 --> 02:02.480 So the second apology involves virtual port channels. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 01:59.480 --> 02:02.480 So the second apology involves virtual port channels. 40 02:02.480 --> 02:05.680 And as we talked about, this means that we have this active, active load- 41 02:05.680 --> 02:06.400 balanced type 42 02:06.400 --> 02:10.200 of situation and this completely changes the nature of things. 43 02:10.200 --> 02:15.110 We don't have STP blocked ports in our environment or at least for this 44 02:15.110 --> 02:17.320 particular link. 45 02:17.320 --> 02:22.680 And our FHRP's are running active, active. 46 02:22.680 --> 02:27.890 And at this point, it doesn't matter whether we're getting sent out this link 47 02:27.890 --> 02:29.800 or this link, 48 02:29.800 --> 02:34.200 either way, we're going to be able to get processed and forwarded on. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:29.800 --> 02:34.200 either way, we're going to be able to get processed and forwarded on. 49 02:34.200 --> 02:38.790 And so this is where Cisco changes their recommendations to say whichever one 50 02:38.790 --> 02:39.160 of these 51 02:39.160 --> 02:41.040 nodes is the VPC primary. 52 02:41.040 --> 02:43.040 Let's say it's the one on the left. 53 02:43.040 --> 02:49.250 At this point, this switch should be configured as the STP root for all of the 54 02:49.250 --> 02:50.120 VLANs and 55 02:50.120 --> 02:56.160 the FHRP active for all of the VLANs as well. 56 02:56.160 --> 02:59.000 So this will be for VLANs 10 through 19. 57 02:59.000 --> 03:02.910 Now I know we said it's active, active, but we will still see that this node is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 02:59.000 --> 03:02.910 Now I know we said it's active, active, but we will still see that this node is 58 03:02.910 --> 03:03.400 running 59 03:03.400 --> 03:04.960 as the standby node. 60 03:04.960 --> 03:09.320 The difference is the standby node is able to, again, forward that traffic out. 61 03:09.320 --> 03:11.480 So it does change things a little bit in the data center. 62 03:11.480 --> 03:15.820 It's important to be aware of that because as we study FHRP's and when we get 63 03:15.820 --> 03:16.360 to a spanning 64 03:16.360 --> 03:20.210 tree protocol, all of that is going to go out to not only our campus 65 03:20.210 --> 03:21.320 environments, but 66 03:21.320 --> 03:23.320 also the data center environment as well. 67 03:23.320 --> 03:26.680 And we need to understand how to deploy that into this type of environment. 68 03:26.680 --> 03:29.400 I hope this has been informative for you and a light to thank you for viewing.