WEBVTT 00:00:01.000 --> 00:00:06.000 All right, and now it's time to dive into the actual material. 00:00:06.000 --> 00:00:14.000 So the first discussion we're going to have or major discussion we're going to have is all about access and distribution layer features and services. 00:00:14.000 --> 00:00:18.000 So we're going to cover a lot of different topics in this major discussion. 00:00:18.000 --> 00:00:37.000 We're going to be focusing on VLANs, trunks, VTP, inter-VLAN routing, STP in three different flavors, Ether channel bundling, first hop redundancy protocols like HSRP, VRP, GLBP, and then we'll be done. 00:00:37.000 --> 00:00:45.000 And then we'll have to move on to what? Routing at that point in time, which is more about our distribution slash core features. 00:00:45.000 --> 00:00:52.000 All right, so let's get this party started and let's dive into a discussion here on campus architecture first. 00:00:52.000 --> 00:00:59.000 Why? Because we just have to remind ourselves what our campus typically looks like because as we're going to be working with all these different technologies, 00:00:59.000 --> 00:01:07.000 it's important that we have an understanding of what is going on under the scenes with that layout and that architecture. 00:01:07.000 --> 00:01:13.000 So the architecture we typically use is the Cisco Enterprise architecture model. 00:01:13.000 --> 00:01:20.000 And first of all, what does this model gives us? Well, it's very, very, very modular in nature. 00:01:20.000 --> 00:01:27.000 You'll see we have the access layers, the distribution layers, the core layers, and how everything's interconnected together gives us this modularity. 00:01:27.000 --> 00:01:33.000 Why? So that way there are services and functions can be designated to very specific areas. 00:01:33.000 --> 00:01:46.000 So, for example, in this part of our network. Yeah, technology is not working today. Wonderful. 00:01:46.000 --> 00:01:53.000 All right. So in this part of our network here, as an example, we'll be using things like VLAN, spanning tree protocol. 00:01:53.000 --> 00:01:56.000 We'd have our first top redundancy protocols here. 00:01:56.000 --> 00:02:05.000 We'd do some ether channel bundling here and so on and so forth, as well as a multitude of other other services and functions that we can implement in that part of our network. 00:02:05.000 --> 00:02:12.000 Whereas, you know, in this part of our network, we might be using something like OSPF or using something like EIGRP in this part of our network. 00:02:12.000 --> 00:02:17.000 And over here, we might be using BGP between our offices, a lot of different options that we have. 00:02:17.000 --> 00:02:21.000 But you'll see that by having this more modular environment, 00:02:21.000 --> 00:02:27.000 we can have different services and functions designed for very specific purposes within very specific modules, 00:02:27.000 --> 00:02:31.000 therefore essentially giving us this compartmentalized way of building our infrastructure. 00:02:31.000 --> 00:02:36.000 So in the end, what does it do for us? It isolates failures for the rest of our network. 00:02:36.000 --> 00:02:39.000 So that way there, if something happens here, we can contain it there. 00:02:39.000 --> 00:02:41.000 If something happens over there in the data center, we can contain it there. 00:02:41.000 --> 00:02:44.000 If something happens down here, we can contain it down there. 00:02:44.000 --> 00:02:48.000 So a failure in, for example, the access layer should not affect the distribution layer. 00:02:48.000 --> 00:02:52.000 A failure in the distribution layer shouldn't affect the access layer or the core. 00:02:52.000 --> 00:02:56.000 So any failure anywhere should not affect anything else or anyone else. 00:02:56.000 --> 00:02:59.000 In addition, this is all about what type of traffic flow. 00:02:59.000 --> 00:03:04.000 It's about north self-traffic flow, north self-traffic flow. 00:03:04.000 --> 00:03:14.000 So north self-traffic flow means in and out, in and out of your subnets, in and out of your VLANs, in and out of your broadcast domains. 00:03:15.000 --> 00:03:18.000 That is north self-traffic flow. 00:03:18.000 --> 00:03:21.000 What's the opposite of that? East and west traffic flow. 00:03:21.000 --> 00:03:28.000 So east and west traffic flow would be traffic within a subnet, within a VLAN, within a broadcast domain. 00:03:28.000 --> 00:03:33.000 So typically we see a lot of east-west traffic flow where, folks, can anybody tell me? 00:03:33.000 --> 00:03:36.000 Where do we typically see a lot of east-west traffic flow? 00:03:37.000 --> 00:03:39.000 Yeah, in our data center. 00:03:39.000 --> 00:03:43.000 So I have a bunch of servers in my data center that you can see on the left-hand side. 00:03:43.000 --> 00:03:46.000 So a lot of times we're going to have servers talking to each other. 00:03:46.000 --> 00:03:50.000 Why? Because of the way we design our servers and our services nowadays. 00:03:50.000 --> 00:03:59.000 We have a lot of microservices, and they run on different systems, different servers, different virtual machines, different containers. 00:03:59.000 --> 00:04:03.000 And as a result of that, we have a lot of east-west traffic flow. 00:04:04.000 --> 00:04:10.000 So, for example, you might be sitting here, and you're going to do a lot of north-south communication with who? 00:04:10.000 --> 00:04:14.000 You're going to do a lot of north-south communication with your servers. 00:04:14.000 --> 00:04:16.000 But the servers are going to do a lot of what? 00:04:16.000 --> 00:04:20.000 The servers are going to do a lot of east-west discussing, talking with each other. 00:04:20.000 --> 00:04:25.000 So just keep that in mind for the exam, the difference between north-south traffic flowing in and out of those subnets, 00:04:25.000 --> 00:04:28.000 in and out of those VLANs, in and out of those VLANs. 00:04:28.000 --> 00:04:32.000 So just keep that in mind for the exam, the difference between north-south traffic flowing in and out of those subnets, 00:04:32.000 --> 00:04:35.000 in and out of those VLANs, in and out of those broadcast domains, 00:04:35.000 --> 00:04:40.000 whereas your east-west traffic flow would be communication within your subnets, within your VLAN broadcast domains. 00:04:40.000 --> 00:04:46.000 And typically, end stations are not going to be talking to each other within the same subnet VLAN broadcast domain. 00:04:46.000 --> 00:04:53.000 When you think about a PC, who does a PC talk to like 99% of the time? 00:04:53.000 --> 00:04:57.000 Some device outside of its subnet VLAN broadcast domain. 00:04:57.000 --> 00:05:02.000 As a result of that, typically, end users are going to be north-south traffic flow, 00:05:02.000 --> 00:05:05.000 going to some server, some system, somewhere. 00:05:05.000 --> 00:05:10.000 But the servers are going to be doing a lot of east-west communication with themselves. 00:05:10.000 --> 00:05:12.000 This entire enterprise architecture needs to be what? 00:05:12.000 --> 00:05:14.000 Always available, always on. 00:05:14.000 --> 00:05:15.000 So how do we get that? 00:05:15.000 --> 00:05:16.000 A lot of redundancy. 00:05:16.000 --> 00:05:18.000 So we've got redundancy at the distribution layer. 00:05:18.000 --> 00:05:19.000 We've got redundancy in our links. 00:05:19.000 --> 00:05:20.000 We've got redundancy for the WAN. 00:05:20.000 --> 00:05:22.000 We've got redundancy for the Internet. 00:05:22.000 --> 00:05:23.000 We've got redundancy in our data center. 00:05:23.000 --> 00:05:25.000 We've got redundancy everywhere. 00:05:25.000 --> 00:05:28.000 We need to ensure we have a lot of layers of defense here. 00:05:28.000 --> 00:05:32.000 So defending at the edge, but also what? 00:05:32.000 --> 00:05:36.000 Defending in and out of our subnets, in and out of our data centers. 00:05:36.000 --> 00:05:39.000 So ensuring that we implement those defenses 00:05:39.000 --> 00:05:43.000 and traditional defenses where are typically going to be at the distribution layer. 00:05:43.000 --> 00:05:45.000 And it could be something as simple as an ACL. 00:05:45.000 --> 00:05:47.000 We could put a firewall there as well. 00:05:47.000 --> 00:05:50.000 But the idea here is to make sure that we're controlling the flow of traffic in and out of those subnets, 00:05:50.000 --> 00:05:52.000 in and out of those VLANs, in and out of those broadcast domains. 00:05:53.000 --> 00:05:55.000 Same thing at the edge of our environment. 00:05:55.000 --> 00:05:58.000 The mentality of that is slightly changing as well with the new zero-trust architecture. 00:05:58.000 --> 00:06:01.000 If you've never heard of that, you might want to look it up. 00:06:01.000 --> 00:06:04.000 The zero-trust architecture is zero-trust, always verify. 00:06:04.000 --> 00:06:12.000 And as a result of that, instead of just relying on these security mechanisms based on location, 00:06:12.000 --> 00:06:17.000 based on IP addressing, that's what we have basically, a lot of us, 00:06:17.000 --> 00:06:20.000 is security based on location, based on IP address. 00:06:20.000 --> 00:06:25.000 With zero-trust, we are going to be essentially shifting that security model. 00:06:25.000 --> 00:06:28.000 Instead of it based on location and based on IP, it's going to be based on what? 00:06:28.000 --> 00:06:32.000 The contextual identity of a device and a user and an app. 00:06:32.000 --> 00:06:37.000 And as a result of that, the control mechanisms are put into place. 00:06:37.000 --> 00:06:42.000 Instead of that geographical boundaries, they're going to be put in place basically right there on you 00:06:42.000 --> 00:06:44.000 when you are trying to communicate. 00:06:44.000 --> 00:06:50.000 So, if I have a PC here and I'm trying to communicate, I'm going to be controlled right here. 00:06:50.000 --> 00:06:55.000 Right here, traffic is not even going to be allowed to get into the network unless it's 100% approved 00:06:55.000 --> 00:07:00.000 based on the contextual identity of the device, the security posture of that device, 00:07:00.000 --> 00:07:05.000 the user that's using that device, the app that's on that device, and is it updated, so on and so forth. 00:07:05.000 --> 00:07:11.000 And then the end result is that a lot of the perimeter security mechanisms are not necessary, 00:07:11.000 --> 00:07:14.000 although we're not going to get rid of them, but they're not as necessary 00:07:14.000 --> 00:07:17.000 and we're not relying on them to be our only line of defense. 00:07:17.000 --> 00:07:20.000 We're relying on the fact that, hey, if a user is trying to do something, 00:07:20.000 --> 00:07:26.000 that has to be authenticated, authorized, approved at that very specific moment in time, 00:07:26.000 --> 00:07:27.000 so everything you do. 00:07:27.000 --> 00:07:30.000 So, that is a zero-trust architecture. 00:07:30.000 --> 00:07:32.000 And later on in this course, and I bring this up because later on in this course, 00:07:32.000 --> 00:07:35.000 you're going to learn about something called TrustSec. 00:07:35.000 --> 00:07:39.000 If you know about TrustSec, say, I, type in I. 00:07:39.000 --> 00:07:46.000 If you know about TrustSec, TrustSec is actually part of Cisco's zero-trust architecture solution. 00:07:46.000 --> 00:07:47.000 That's what it is. 00:07:47.000 --> 00:07:52.000 And the end result is that you are going to be securing your environment 00:07:52.000 --> 00:07:58.000 based on every single communication that happens, and not just based on location, 00:07:58.000 --> 00:08:00.000 not just based on IP address. 00:08:00.000 --> 00:08:05.000 It's going to be based on a whole bunch of different variables and attributes 00:08:05.000 --> 00:08:08.000 that go into the overall decision-making process. 00:08:08.000 --> 00:08:12.000 And TrustSec is part of our SD-Access solution. 00:08:12.000 --> 00:08:14.000 How many of you are using SD-Access? 00:08:14.000 --> 00:08:19.000 And typically, you're going to use something like Identity Services Engine in order to accomplish that. 00:08:19.000 --> 00:08:23.000 So, we're going to learn a lot of the fundamentals. 00:08:23.000 --> 00:08:26.000 We're going to learn an excessive amount of fundamentals throughout this course. 00:08:26.000 --> 00:08:29.000 But then towards the end of this course, I'm going to introduce you to something like SD-Access, 00:08:29.000 --> 00:08:32.000 something like TrustSec, something like Identity Services Engine, 00:08:32.000 --> 00:08:34.000 because you will be testing on those in the certification exam as well. 00:08:34.000 --> 00:08:35.000 That's why I'm bringing them up here. 00:08:35.000 --> 00:08:37.000 You're going to see them later on in this particular course. 00:08:37.000 --> 00:08:41.000 So, it's going to shift our mentality when it comes to security when it's all said and done. 00:08:41.000 --> 00:08:44.000 And last but not least, this has to be extremely scalable, and it is. 00:08:44.000 --> 00:08:49.000 This is extremely scalable because at any point in time, if we have to add another, 00:08:49.000 --> 00:08:55.000 let's say, access layer switch down here, I can connect it here, I can connect it here, I'm done. 00:08:55.000 --> 00:08:59.000 If we want to go ahead and we need another distribution layer somewhere, 00:08:59.000 --> 00:09:03.000 set up your distribution layer, connect it up to the core, core, core, core, 00:09:03.000 --> 00:09:06.000 and then put our access layer switches down here. 00:09:06.000 --> 00:09:09.000 So, very, very scalable, very flexible. 00:09:09.000 --> 00:09:15.000 Now, if you're interested more in design, if you love design, you love architecture, 00:09:15.000 --> 00:09:23.000 then you want to take a look at going out to Cisco's website right now. 00:09:27.000 --> 00:09:29.000 Oops, got to go back one more page. 00:09:30.000 --> 00:09:31.000 All right. 00:09:31.000 --> 00:09:38.000 So, this one right here, 300.420, prove your knowledge of enterprise design, 00:09:38.000 --> 00:09:43.000 including advanced addressing and routing solutions, advanced enterprise campus networks, 00:09:43.000 --> 00:09:46.000 WAN, security services, network service, SDA. 00:09:46.000 --> 00:09:49.000 So, this is all about designing. 00:09:49.000 --> 00:09:52.000 So, if you're into designing, you want to learn more about designing, 00:09:52.000 --> 00:09:56.000 that's the place to go to learn more about designing. 00:09:57.000 --> 00:10:02.000 300-420-ENSLD, as I like to call it. 00:10:02.000 --> 00:10:04.000 So, you'll notice here that we have different tiers. 00:10:04.000 --> 00:10:07.000 You've got the access layer, you've got the distribution layer, you've got the core, 00:10:07.000 --> 00:10:10.000 you've got access layer, distribution core, you've got access distribution core, 00:10:10.000 --> 00:10:11.000 access distribution core. 00:10:11.000 --> 00:10:14.000 So, let's just zoom in on one section. 00:10:14.000 --> 00:10:18.000 So, that way there we can just focus on access, distribution, and core. 00:10:18.000 --> 00:10:22.000 So, I think you can already see how the core just connects everything together. 00:10:22.000 --> 00:10:27.000 The core provides fast transportation between different distribution areas that you have 00:10:27.000 --> 00:10:29.000 within your enterprise campus. 00:10:29.000 --> 00:10:31.000 A lot of people think that the core is going to have all the services in it, 00:10:31.000 --> 00:10:34.000 and in actuality, the core has minimal services in it 00:10:34.000 --> 00:10:37.000 because we don't want the core to be having to do work. 00:10:37.000 --> 00:10:41.000 We want the core to be all about fast transportation and nothing else. 00:10:41.000 --> 00:10:43.000 So, typically, we're not going to be putting security solutions in the core. 00:10:43.000 --> 00:10:48.000 We're not going to be putting traffic filtering solutions in the core. 00:10:48.000 --> 00:10:53.000 We're not going to be putting those things that could slow down our communication flow 00:10:53.000 --> 00:10:54.000 when it's going through the core. 00:10:54.000 --> 00:10:56.000 We want the core to be as fast as possible. 00:10:56.000 --> 00:10:59.000 So, typically, when it comes to features and services, they're being applied where? 00:10:59.000 --> 00:11:01.000 At the distribution layer. 00:11:01.000 --> 00:11:02.000 They're being applied at the access layer. 00:11:02.000 --> 00:11:05.000 That's typically where we are applying our solutions. 00:11:05.000 --> 00:11:08.000 So, the access layer is providing workgroup and user access to the network. 00:11:08.000 --> 00:11:09.000 We have the distribution layer. 00:11:09.000 --> 00:11:11.000 That's all about policy-based connectivity. 00:11:11.000 --> 00:11:17.000 So, in our typical modern, not modern day, but our typical enterprise networks 00:11:17.000 --> 00:11:20.000 where we're not using newer advanced technologies and solutions, 00:11:20.000 --> 00:11:22.000 where do we typically put our security? 00:11:22.000 --> 00:11:23.000 Right here at the distribution layer. 00:11:23.000 --> 00:11:25.000 It's where we have our policy-based connectivity, 00:11:25.000 --> 00:11:30.000 our policy-based control to control traffic as it's flowing from here up to here 00:11:30.000 --> 00:11:32.000 or flowing from here down to here. 00:11:32.000 --> 00:11:34.000 We're going to control it all right here. 00:11:34.000 --> 00:11:36.000 But there's other ways to do this. 00:11:36.000 --> 00:11:38.000 For example, when we talk about our SD access solution, 00:11:38.000 --> 00:11:40.000 we're going to put all our controls down here instead. 00:11:40.000 --> 00:11:41.000 That's right. 00:11:41.000 --> 00:11:44.000 We're going to put all our controls right down here. 00:11:44.000 --> 00:11:50.000 That way there we can make our network more efficient, more effective, 00:11:50.000 --> 00:11:54.000 and implement security right down here, right at the get-go, right at the start, 00:11:54.000 --> 00:12:00.000 and not have to worry about access controllers up here dealing with the traffic 00:12:00.000 --> 00:12:02.000 that comes to it. 00:12:02.000 --> 00:12:04.000 But more on that type of stuff later on. 00:12:04.000 --> 00:12:08.000 But I want you to be able to pick these out of the lineup of the certification exams. 00:12:08.000 --> 00:12:11.000 You already know a little bit about each of these for the exam as we mentioned them, 00:12:11.000 --> 00:12:14.000 but think about the access layer as the point where end devices are attached to 00:12:14.000 --> 00:12:15.000 the network. 00:12:15.000 --> 00:12:17.000 So this is where we're going to attach our what? 00:12:17.000 --> 00:12:19.000 We're going to attach our PCs. 00:12:19.000 --> 00:12:21.000 Our cameras would be connected here. 00:12:21.000 --> 00:12:23.000 Our printers would be connected here. 00:12:23.000 --> 00:12:25.000 Our phones would be connected here. 00:12:25.000 --> 00:12:28.000 Access points would be connected here. 00:12:28.000 --> 00:12:36.000 This is the point of our network whereby we end up providing connectivity to it, 00:12:36.000 --> 00:12:42.000 either physical connectivity using cables or wireless connectivity using 00:12:42.000 --> 00:12:45.000 wireless access points. 00:12:45.000 --> 00:12:48.000 And this is the most feature-rich area of your network. 00:12:48.000 --> 00:12:49.000 It really is. 00:12:49.000 --> 00:12:52.000 More than the distribution layer and more than the core. 00:12:52.000 --> 00:12:57.000 You've got discovery and configuration services down here, CDP, LLDP as an example. 00:12:57.000 --> 00:12:59.000 You've got security services like 802.1X. 00:12:59.000 --> 00:13:00.000 You've got port security. 00:13:00.000 --> 00:13:01.000 You've got DHCP snooping. 00:13:01.000 --> 00:13:03.000 You've got dynamic ARP inspection. 00:13:03.000 --> 00:13:05.000 You've got IP source guard. 00:13:05.000 --> 00:13:11.000 You've got network identity and access services. 00:13:11.000 --> 00:13:12.000 That's what I'm looking for. 00:13:12.000 --> 00:13:13.000 Again, 802.1X. 00:13:13.000 --> 00:13:15.000 You've got MAC authentication bypass. 00:13:15.000 --> 00:13:18.000 You've got WebAuth that happens down here as well. 00:13:18.000 --> 00:13:19.000 What else have we got? 00:13:19.000 --> 00:13:20.000 We've got QS marking. 00:13:20.000 --> 00:13:21.000 We've got policing. 00:13:21.000 --> 00:13:22.000 We've got queuing. 00:13:22.000 --> 00:13:24.000 We can do DPAC and inspection with NBAR. 00:13:24.000 --> 00:13:27.000 We have spanning tree protocol, rapid spanning tree protocol. 00:13:27.000 --> 00:13:28.000 We can even run. 00:13:28.000 --> 00:13:29.000 We can even run. 00:13:29.000 --> 00:13:30.000 That's right. 00:13:30.000 --> 00:13:31.000 EIGRP, OSPF down here. 00:13:31.000 --> 00:13:34.000 If we build our layer three network, that goes all the way down to here. 00:13:34.000 --> 00:13:35.000 That's right. 00:13:35.000 --> 00:13:41.000 We've got UDLD, FlexLinks, PortFast, UplinkFast, BackboneFast, LoopGuard, VPD, HoopGuard. 00:13:41.000 --> 00:13:43.000 You don't need to know all of those for the exam. 00:13:43.000 --> 00:13:45.000 But just to show you, there's so many services. 00:13:45.000 --> 00:13:48.000 Oh, let's not forget about Power over Ethernet. 00:13:48.000 --> 00:13:51.000 All of that at the access layer and a whole lot more. 00:13:51.000 --> 00:13:53.000 Most feature-rich part of your network. 00:13:53.000 --> 00:13:55.000 If you're ever asked on an exam, what is the most feature-rich part of your network? 00:13:55.000 --> 00:13:57.000 It is your access layer. 00:13:57.000 --> 00:13:58.000 It's not your core. 00:13:58.000 --> 00:13:59.000 It's not your distribution layer. 00:13:59.000 --> 00:14:00.000 It is your access layer. 00:14:00.000 --> 00:14:03.000 That's the most feature-rich part of your network where end users connect. 00:14:04.000 --> 00:14:05.000 Distribution layer is what? 00:14:05.000 --> 00:14:06.000 It's an aggregation point. 00:14:06.000 --> 00:14:07.000 It's a control point. 00:14:07.000 --> 00:14:11.000 For the exam, if they were asked about the distribution layer, what does it do? 00:14:11.000 --> 00:14:12.000 It's an aggregation point. 00:14:12.000 --> 00:14:13.000 It's aggregating what? 00:14:13.000 --> 00:14:15.000 Everybody at the access layer together. 00:14:15.000 --> 00:14:19.000 When you think about everybody that's down here, they're coming up through one of two devices. 00:14:19.000 --> 00:14:20.000 They're coming up through one of two devices. 00:14:20.000 --> 00:14:22.000 We're aggregating that together. 00:14:27.000 --> 00:14:30.000 That's why we typically put our policies here. 00:14:30.000 --> 00:14:32.000 Why we typically put our security here. 00:14:34.000 --> 00:14:40.000 Because we're able to do the most with the minimum amount of work. 00:14:41.000 --> 00:14:43.000 Because this is where everybody has to go through. 00:14:43.000 --> 00:14:44.000 This is where all the traffic flows. 00:14:44.000 --> 00:14:46.000 It's where everything aggregates to. 00:14:46.000 --> 00:14:48.000 So, policy enforcement here. 00:14:55.000 --> 00:14:57.000 Typically, this is going to be what? 00:14:57.000 --> 00:14:59.000 This is going to be our layer three environment. 00:14:59.000 --> 00:15:01.000 It's going to be our layer two environment in this case. 00:15:01.000 --> 00:15:04.000 Folks, when you hear the word layer three, what do you typically think of? 00:15:12.000 --> 00:15:13.000 Chat in. 00:15:14.000 --> 00:15:15.000 Yeah, routing. 00:15:15.000 --> 00:15:16.000 Exactly. 00:15:16.000 --> 00:15:17.000 So, we think of routing. 00:15:17.000 --> 00:15:18.000 What else do we think of? 00:15:18.000 --> 00:15:25.000 Well, with routing, we think of OSPF, or we think of EIGRP, or we think of something like maybe BGP, or we think of ISIS. 00:15:26.000 --> 00:15:28.000 All different dynamic routing protocols. 00:15:28.000 --> 00:15:32.000 Not going to use BGP there, but the other three are perfectly valid options. 00:15:33.000 --> 00:15:35.000 Now, when you hear layer two, what do you typically think of? 00:15:44.000 --> 00:15:45.000 We think of switching. 00:15:45.000 --> 00:15:46.000 Yeah, absolutely. 00:15:46.000 --> 00:15:47.000 So, switching. 00:15:47.000 --> 00:15:50.000 And when we think of switching, what do we think of? 00:15:50.000 --> 00:15:51.000 Yeah, VLANs. 00:15:51.000 --> 00:15:52.000 What else? 00:15:52.000 --> 00:15:53.000 VLANs. 00:15:53.000 --> 00:15:54.000 Ooh, MAC addresses. 00:15:54.000 --> 00:15:56.000 So, up here would be like IPs up there. 00:15:56.000 --> 00:15:57.000 MAC addresses down here. 00:15:57.000 --> 00:15:58.000 What else? 00:15:58.000 --> 00:15:59.000 Trunks. 00:15:59.000 --> 00:16:00.000 Trunks. 00:16:00.000 --> 00:16:01.000 That's a good one. 00:16:02.000 --> 00:16:04.000 What's a protocol that starts with an S? 00:16:07.000 --> 00:16:10.000 That we find down here in layer two that we don't find in layer three? 00:16:10.000 --> 00:16:11.000 Yeah, Spanning Tree Protocol. 00:16:13.000 --> 00:16:15.000 So, what would you classify this then? 00:16:16.000 --> 00:16:22.000 Typically, that is our demarcation point between our layer two technologies and services 00:16:22.000 --> 00:16:24.000 and our layer three technology and services. 00:16:24.000 --> 00:16:26.000 Just another thing to keep in mind for the certification exam. 00:16:27.000 --> 00:16:30.000 Now, how many of you have your network designed like this, 00:16:30.000 --> 00:16:32.000 where you've got your access, your distribution, and your core, 00:16:32.000 --> 00:16:34.000 and you've got layer two and layer three like this? 00:16:38.000 --> 00:16:39.000 If you do, type in yes. 00:16:39.000 --> 00:16:40.000 If you don't, type in no. 00:16:41.000 --> 00:16:44.000 Or if you don't answer, then I assume it's a no. 00:16:46.000 --> 00:16:47.000 All right. 00:16:47.000 --> 00:16:48.000 Yeah. 00:16:48.000 --> 00:16:49.000 So, if you have a collapsed core. 00:16:52.000 --> 00:16:54.000 So, let me ask you this, L. Washington. 00:16:55.000 --> 00:16:59.000 With your collapsed core, are your access layer switches connected directly to the core? 00:17:07.000 --> 00:17:08.000 Yeah. 00:17:08.000 --> 00:17:09.000 Okay. 00:17:09.000 --> 00:17:10.000 Perfect. 00:17:10.000 --> 00:17:11.000 Yeah. 00:17:11.000 --> 00:17:12.000 And why is that? 00:17:12.000 --> 00:17:13.000 Smaller network. 00:17:13.000 --> 00:17:14.000 And that's perfectly fine. 00:17:14.000 --> 00:17:17.000 If you are not large enough to have all three of these layers, 00:17:18.000 --> 00:17:20.000 because it doesn't make sense from a cost standpoint, 00:17:20.000 --> 00:17:22.000 collapsed core is perfectly fine. 00:17:22.000 --> 00:17:24.000 So, the next question I have here, L. Washington, 00:17:25.000 --> 00:17:27.000 is the core device, 00:17:28.000 --> 00:17:29.000 is the core device, 00:17:30.000 --> 00:17:31.000 or let's put it this way, 00:17:33.000 --> 00:17:37.000 is this where layer two begins going down to the access layer then? 00:17:39.000 --> 00:17:40.000 Is that what you've done? 00:17:41.000 --> 00:17:43.000 Or are you doing routing right down to here? 00:17:43.000 --> 00:17:44.000 What is it? 00:17:56.000 --> 00:17:57.000 First option. 00:17:57.000 --> 00:17:58.000 So, layer two. 00:17:58.000 --> 00:17:59.000 Right. 00:17:59.000 --> 00:18:02.000 So, basically, this would be your default gateway for all your subnets, VLANs, broadcasts. 00:18:02.000 --> 00:18:03.000 I mean, absolutely. 00:18:03.000 --> 00:18:05.000 But what I'm trying to point here with this conversation, folks, 00:18:05.000 --> 00:18:07.000 I'm not singling anyone out, right? 00:18:08.000 --> 00:18:10.000 I'm just trying to show you, look, there's variability, right? 00:18:11.000 --> 00:18:13.000 There's variability in what you can do. 00:18:14.000 --> 00:18:16.000 Flexibility with this environment. 00:18:17.000 --> 00:18:18.000 And that's what's so important. 00:18:18.000 --> 00:18:20.000 So, yeah, many of us looks like this. 00:18:21.000 --> 00:18:24.000 Some of us, the distribution layer might not even be there, 00:18:25.000 --> 00:18:27.000 and it's layer two from the core right down to your access layer switches. 00:18:28.000 --> 00:18:30.000 But then there are some of you out there who probably have this. 00:18:31.000 --> 00:18:32.000 If you have this, 00:18:33.000 --> 00:18:34.000 I want you to type in me. 00:18:36.000 --> 00:18:37.000 Do you have this? 00:18:40.000 --> 00:18:41.000 How many of you have this? 00:18:42.000 --> 00:18:44.000 Where all of this is now routing, 00:18:45.000 --> 00:18:47.000 and this is your layer two? 00:18:48.000 --> 00:18:49.000 Totally valid option. 00:18:50.000 --> 00:18:51.000 And we'll talk about this option 00:18:51.000 --> 00:18:53.000 when we get to our discussion on SD access, 00:18:54.000 --> 00:18:56.000 because that's how SD access works the best 00:18:56.000 --> 00:18:58.000 when you do this type of architecture. 00:18:58.000 --> 00:18:59.000 But again, just to show you that, 00:19:00.000 --> 00:19:01.000 there are so many different ways 00:19:01.000 --> 00:19:04.000 you can architect your environment using this approach. 00:19:05.000 --> 00:19:06.000 But what are we going to learn first? 00:19:06.000 --> 00:19:07.000 We're going to get to the fundamentals, 00:19:07.000 --> 00:19:09.000 because the fundamentals matter the most, 00:19:09.000 --> 00:19:10.000 and the fundamentals are what? 00:19:11.000 --> 00:19:13.000 Layer three, layer two. 00:19:13.000 --> 00:19:15.000 And so we're going to learn about all those technologies here 00:19:15.000 --> 00:19:16.000 over our first few sessions, 00:19:17.000 --> 00:19:18.000 because those still apply 00:19:19.000 --> 00:19:20.000 no matter where you are moving this line 00:19:21.000 --> 00:19:22.000 when it's all said and done. 00:19:22.000 --> 00:19:24.000 And like we said, the core just connects everything together. 00:19:25.000 --> 00:19:26.000 It's about high-speed connectivity, 00:19:27.000 --> 00:19:29.000 high availability, highly redundant. 00:19:29.000 --> 00:19:31.000 So it's critical to maintain what? 00:19:31.000 --> 00:19:32.000 End-to-end connectivity. 00:19:32.000 --> 00:19:33.000 Must always be on. 00:19:33.000 --> 00:19:35.000 Has to move packets as fast as possible. 00:19:36.000 --> 00:19:38.000 Provides scalability to the architecture. 00:19:38.000 --> 00:19:39.000 These are all buzzwords, 00:19:39.000 --> 00:19:41.000 keywords for the certification exam. 00:19:43.000 --> 00:19:44.000 All right, so like we said, 00:19:44.000 --> 00:19:45.000 there's the three-tier model. 00:19:47.000 --> 00:19:49.000 There's that three-tier model, right? 00:19:49.000 --> 00:19:51.000 But many of you have a collapsed core, 00:19:51.000 --> 00:19:53.000 so maybe this is what you have instead. 00:19:53.000 --> 00:19:55.000 So there's an example of a collapsed core. 00:19:58.000 --> 00:20:00.000 So I assume L. Washington, that's what you have, right? 00:20:03.000 --> 00:20:04.000 Yeah, right. 00:20:04.000 --> 00:20:07.000 But some organizations might do it this way. 00:20:07.000 --> 00:20:10.000 You see, look, that's also a collapsed core, right? 00:20:11.000 --> 00:20:13.000 Not really collapsed core, but two-tier also. 00:20:14.000 --> 00:20:16.000 All right, Spider-Man really loves this one 00:20:16.000 --> 00:20:18.000 because Spider-Man can take a nap right here. 00:20:20.000 --> 00:20:21.000 Yeah. 00:20:26.000 --> 00:20:28.000 All right, but again, flexibility. 00:20:28.000 --> 00:20:29.000 So pay attention on the exam. 00:20:29.000 --> 00:20:32.000 If they do show you an architecture on the exam, 00:20:32.000 --> 00:20:34.000 right, this, three-tier, right? 00:20:35.000 --> 00:20:36.000 It's clear as bells. 00:20:36.000 --> 00:20:38.000 Access, distribution, core. 00:20:38.000 --> 00:20:39.000 You've got your three tiers. 00:20:39.000 --> 00:20:42.000 You've got your two devices in the middle for the core, right? 00:20:42.000 --> 00:20:43.000 And two, typically you're only gonna have two. 00:20:43.000 --> 00:20:45.000 Any more than that is a waste of money, right? 00:20:45.000 --> 00:20:46.000 Same thing with distribution layer. 00:20:46.000 --> 00:20:48.000 Typically only two, typically only two, 00:20:48.000 --> 00:20:50.000 typically only two, typically only two. 00:20:50.000 --> 00:20:53.000 Again, know that for the exam in case it comes up. 00:20:55.000 --> 00:20:57.000 And then access layer is pretty much whatever you need, 00:20:57.000 --> 00:21:00.000 whatever you need to get the job done at the access layer. 00:21:01.000 --> 00:21:03.000 All right, and then when you get to this model, 00:21:03.000 --> 00:21:05.000 two in the middle for your collapsed core, 00:21:05.000 --> 00:21:07.000 and then as whatever you need around the outside. 00:21:09.000 --> 00:21:12.000 And again, layer two, layer three, doesn't matter, right? 00:21:12.000 --> 00:21:15.000 This could be, for example, this could all be layer three for you. 00:21:15.000 --> 00:21:19.000 This is L3, this is L2, this is L2, right? 00:21:19.000 --> 00:21:21.000 Really depends on how you want to design it. 00:21:21.000 --> 00:21:24.000 Or you could design it this way where it's all layer three. 00:21:26.000 --> 00:21:28.000 And then you got your L2 down here, your L2. 00:21:28.000 --> 00:21:30.000 So again, flexibility, folks. 00:21:30.000 --> 00:21:32.000 So just pay attention to where they draw their lines 00:21:32.000 --> 00:21:34.000 and so on and so forth. 00:21:34.000 --> 00:21:36.000 So that way there you can answer questions on the exam. 00:21:37.000 --> 00:21:39.000 It's not going to be difficult for this exam, 00:21:39.000 --> 00:21:41.000 but as long as you know what I've just taught you. 00:21:42.000 --> 00:21:46.000 So redundancy, as we can see, we've got a redundant distribution. 00:21:46.000 --> 00:21:48.000 We got redundant core devices. 00:21:49.000 --> 00:21:51.000 Something to pay attention to here, though, 00:21:51.000 --> 00:21:55.000 is the fact that notice how these devices are not connected together. 00:21:55.000 --> 00:21:56.000 Why is that? 00:21:56.000 --> 00:22:01.000 Why are they not connected together in a traditional sense? 00:22:01.000 --> 00:22:03.000 Now, for those of you who are doing stacking, okay, stacking, 00:22:04.000 --> 00:22:07.000 we'll just forget about stacking right now. 00:22:07.000 --> 00:22:10.000 Well, why would we not connect them together with Ethernet links? 00:22:12.000 --> 00:22:13.000 Yeah, it would be routing loops. 00:22:13.000 --> 00:22:15.000 You would not do that. 00:22:15.000 --> 00:22:18.000 There's a protocol called Spanning Tree Protocol we're going to learn about. 00:22:18.000 --> 00:22:22.000 Spanning Tree Protocol finds all loops in that environment, 00:22:22.000 --> 00:22:24.000 and what does it do with all those loops? 00:22:25.000 --> 00:22:27.000 It eliminates them by blocking ports. 00:22:27.000 --> 00:22:31.000 So if you did all of this, what might happen in your environment 00:22:31.000 --> 00:22:34.000 is you might end up blocking this, blocking this, blocking this, 00:22:34.000 --> 00:22:38.000 blocking this, blocking this, blocking this to prevent loops. 00:22:38.000 --> 00:22:41.000 So now everybody's traffic flows like this. 00:22:41.000 --> 00:22:43.000 Everybody's traffic flows like this. 00:22:43.000 --> 00:22:44.000 This is not good. 00:22:44.000 --> 00:22:45.000 That's why we don't do it. 00:22:45.000 --> 00:22:50.000 We don't do it like this because this could happen to us, 00:22:50.000 --> 00:22:53.000 and these switches, like this switch is not designed 00:22:53.000 --> 00:22:55.000 to handle the traffic from all those other switches. 00:22:55.000 --> 00:22:57.000 It's an access layer switch. 00:22:58.000 --> 00:22:59.000 It's designed for what? 00:22:59.000 --> 00:23:03.000 North, south, traffic flow, in and out. 00:23:03.000 --> 00:23:04.000 That's what it's designed for. 00:23:04.000 --> 00:23:08.000 So you would not daisy chain them together as we talk about. 00:23:08.000 --> 00:23:13.000 Now, stacking is a different thing, and we have a video in our enterprise, 00:23:13.000 --> 00:23:14.000 not enterprise. 00:23:14.000 --> 00:23:16.000 We have a video in our campus environment, 00:23:16.000 --> 00:23:18.000 enterprise campus environment, I was going to say. 00:23:19.000 --> 00:23:22.000 But down at the bottom under the architecture discussion, 00:23:22.000 --> 00:23:26.000 I will talk about the concept of VSS and stack-wise 00:23:26.000 --> 00:23:28.000 to help you get ready for the certification exam. 00:23:28.000 --> 00:23:32.000 But what we're dealing with is we're dealing with a technology 00:23:32.000 --> 00:23:36.000 that allows you to connect them together. 00:23:36.000 --> 00:23:38.000 So you stack them together. 00:23:39.000 --> 00:23:42.000 You don't have to physically stack them, all right, 00:23:42.000 --> 00:23:45.000 but they got to be close enough together so you can connect a special cable. 00:23:45.000 --> 00:23:48.000 It's called a stacking cable from here to here, 00:23:48.000 --> 00:23:51.000 and then a stacking cable from here to here, 00:23:51.000 --> 00:23:53.000 and then a stacking cable from here to here, 00:23:53.000 --> 00:23:55.000 and then a stacking cable from here back to here. 00:23:55.000 --> 00:23:57.000 And these are all your Ethernet cables. 00:23:57.000 --> 00:24:00.000 So Ethernet cables are here, these are all your Ethernet cables, 00:24:00.000 --> 00:24:02.000 and these are your stacking cables. 00:24:02.000 --> 00:24:08.000 So what this does is it turns it from four single devices into one device. 00:24:08.000 --> 00:24:10.000 That is one switch now. 00:24:10.000 --> 00:24:13.000 When you stack switches together, they now become one entity, 00:24:13.000 --> 00:24:16.000 one switch with a single management IP address, 00:24:16.000 --> 00:24:23.000 allowing you to basically override a lot of the network 00:24:23.000 --> 00:24:30.000 and a lot of the networking configuration blockages 00:24:30.000 --> 00:24:32.000 that would come your way if you didn't do this. 00:24:32.000 --> 00:24:34.000 So, for example, in our case, 00:24:34.000 --> 00:24:38.000 Spanning Tree Protocol prevents me from doing a lot of things I want to do, 00:24:38.000 --> 00:24:42.000 but if I stack, then I can trick Spanning Tree Protocol 00:24:42.000 --> 00:24:45.000 into allowing me to do a lot of things that I wouldn't be allowed to do. 00:24:46.000 --> 00:24:47.000 Okay? 00:24:47.000 --> 00:24:52.000 So definitely, you know, don't connect them together with Ethernet, 00:24:52.000 --> 00:24:54.000 but stacking is perfectly fine, 00:24:54.000 --> 00:24:56.000 and we have a video on stacking for you to watch. 00:24:59.000 --> 00:25:00.000 Yeah. 00:25:00.000 --> 00:25:04.000 And also, you can have stack redundancy for power as well, 00:25:04.000 --> 00:25:06.000 so they can all share power with each other. 00:25:06.000 --> 00:25:09.000 So there's another set of stacking cables you can use as well. 00:25:09.000 --> 00:25:10.000 Absolutely. 00:25:10.000 --> 00:25:11.000 Yeah. 00:25:11.000 --> 00:25:12.000 Yeah. 00:25:12.000 --> 00:25:13.000 So John says, 00:25:13.000 --> 00:25:16.000 I thought daisy chaining meant one switch downstream from another 00:25:16.000 --> 00:25:19.000 but not connecting up to any other switches. 00:25:19.000 --> 00:25:21.000 In reality, John, 00:25:21.000 --> 00:25:26.000 the terminology is not going to make a difference for this certification exam. 00:25:26.000 --> 00:25:31.000 So whether you thought, you know, daisy chaining meant this, right, 00:25:31.000 --> 00:25:35.000 or daisy chaining your access layer switches together, right, 00:25:35.000 --> 00:25:39.000 yeah, not with Ethernet cables, right, 00:25:39.000 --> 00:25:42.000 don't worry too much about the word daisy chaining in that particular case. 00:25:42.000 --> 00:25:43.000 All right? 00:25:43.000 --> 00:25:44.000 So if it means something else to you, 00:25:44.000 --> 00:25:47.000 then continue using daisy chain the way it means to you, 00:25:47.000 --> 00:25:50.000 and whatever words you want to use here to describe what's going on down 00:25:50.000 --> 00:25:52.000 here is perfectly fine, right? 00:25:52.000 --> 00:25:53.000 So in this case, 00:25:53.000 --> 00:25:56.000 don't connect these access layer switches together with Ethernet cables. 00:25:58.000 --> 00:25:59.000 Perfect. 00:25:59.000 --> 00:26:03.000 So now when it comes to multi-tier routed access virtual switch, 00:26:03.000 --> 00:26:04.000 what does that mean? 00:26:04.000 --> 00:26:09.000 We're just talking about our movements that we have in our particular case. 00:26:09.000 --> 00:26:13.000 So, for example, we'll have layer two slash layer three. 00:26:13.000 --> 00:26:15.000 This is what we call the multi-tier approach. 00:26:15.000 --> 00:26:17.000 The multi-tier approach. 00:26:17.000 --> 00:26:21.000 So what happens here is we've got VLANs terminated at the distribution layer. 00:26:21.000 --> 00:26:24.000 So this is your VLAN, your subnet, your broadcast. 00:26:24.000 --> 00:26:28.000 It means that your spanning tree protocol blocks 50% or more of your links in 00:26:28.000 --> 00:26:30.000 this environment down here. 00:26:30.000 --> 00:26:32.000 But you can have the same VLAN on multiple switches. 00:26:32.000 --> 00:26:34.000 So I could have VLAN 10 here, VLAN 10 here. 00:26:34.000 --> 00:26:35.000 Why? 00:26:35.000 --> 00:26:38.000 Because we can communicate through the layer two network this way between 00:26:38.000 --> 00:26:40.000 those devices in the VLAN. 00:26:41.000 --> 00:26:43.000 It's cheaper than all the other options we're going to talk about here. 00:26:43.000 --> 00:26:46.000 And then we have our first top redundancy protocols that we'll put up here as 00:26:46.000 --> 00:26:47.000 we'll see later on. 00:26:47.000 --> 00:26:50.000 So we're going to build this architecture as we go through this course. 00:26:50.000 --> 00:26:52.000 When we get to our SD access discussion, 00:26:52.000 --> 00:26:54.000 we're going to see this example here. 00:26:56.000 --> 00:26:58.000 So SD access architecture, it's called. 00:26:58.000 --> 00:27:00.000 Software defined access in the world of Cisco. 00:27:00.000 --> 00:27:03.000 So down here, now you can see we removed routing all the way down here. 00:27:03.000 --> 00:27:05.000 So your VLANs are actually terminated here. 00:27:05.000 --> 00:27:07.000 They're terminated on those access layers. 00:27:07.000 --> 00:27:09.000 Routing happens everywhere up here. 00:27:09.000 --> 00:27:11.000 So there's no spanning tree protocol. 00:27:11.000 --> 00:27:13.000 Now there's no first top redundancy protocols, 00:27:13.000 --> 00:27:16.000 but it is more expensive because you would have to have multi-layer switches 00:27:16.000 --> 00:27:18.000 here as opposed to layer two switches. 00:27:18.000 --> 00:27:19.000 But now you are, 00:27:19.000 --> 00:27:21.000 every user is directly connected to their what? 00:27:21.000 --> 00:27:22.000 To their default gateway. 00:27:22.000 --> 00:27:25.000 Because this would be the default gateway for the users that are 00:27:25.000 --> 00:27:26.000 connected to it. 00:27:26.000 --> 00:27:30.000 But that means that I can not have users directly connected to their 00:27:30.000 --> 00:27:31.000 default gateway. 00:27:31.000 --> 00:27:34.000 I can only have users directly connected to their default gateway. 00:27:35.000 --> 00:27:38.000 But that means that I can not have users in different VLANs 00:27:38.000 --> 00:27:39.000 span across this environment here. 00:27:39.000 --> 00:27:41.000 For example, if I have VLAN 10 here, 00:27:41.000 --> 00:27:45.000 I wouldn't be allowed to have VLAN 10 here because they are not 00:27:45.000 --> 00:27:47.000 connected to each other. 00:27:47.000 --> 00:27:49.000 Now if we were doing stacking, different story. 00:27:49.000 --> 00:27:53.000 Again, stacking allows us to change some of the rules we have in place. 00:27:53.000 --> 00:27:54.000 But without stacking, 00:27:54.000 --> 00:27:57.000 I can't have somebody in VLAN 10 here and somebody in VLAN 10 here 00:27:57.000 --> 00:27:58.000 anymore. 00:27:58.000 --> 00:28:00.000 So as soon as you move that boundary, layer three. 00:28:00.000 --> 00:28:02.000 Because of that, can't do that. 00:28:02.000 --> 00:28:04.000 Now, could we implement something like VXLAN and get away with it? 00:28:04.000 --> 00:28:05.000 Sure, of course we could. 00:28:05.000 --> 00:28:09.000 But just with the fundamental technologies, no. 00:28:09.000 --> 00:28:11.000 Without adding newer services, newer features, 00:28:11.000 --> 00:28:15.000 more futuristic features and services, 00:28:15.000 --> 00:28:19.000 we wouldn't be able to connect these two devices together that are in 00:28:19.000 --> 00:28:24.000 VLAN 10 without using some tunneling technology to accomplish that. 00:28:24.000 --> 00:28:25.000 Why? 00:28:25.000 --> 00:28:26.000 Because we got a route. 00:28:26.000 --> 00:28:28.000 Traffic is going to flow up here and come back down. 00:28:28.000 --> 00:28:31.000 I need to tunnel through that layer three network to get from layer two 00:28:31.000 --> 00:28:32.000 to layer two. 00:28:32.000 --> 00:28:33.000 VXLAN allows me to do that. 00:28:33.000 --> 00:28:36.000 More on that later. 00:28:36.000 --> 00:28:37.000 Virtual switching. 00:28:37.000 --> 00:28:41.000 So we have to realize we can have switches that are inside servers. 00:28:41.000 --> 00:28:46.000 We can have switches that are inside servers. 00:28:46.000 --> 00:28:50.000 So if we did not have switches inside our server, what would that mean? 00:28:50.000 --> 00:28:55.000 It would mean that every single virtual machine on that server would have to 00:28:55.000 --> 00:29:00.000 be in the same subnet slash VLAN slash broadcast domain as what? 00:29:00.000 --> 00:29:04.000 As the port the server is connected to. 00:29:04.000 --> 00:29:06.000 So let's say this was VLAN 10. 00:29:06.000 --> 00:29:10.000 If I didn't have a virtual switch inside the server, 00:29:10.000 --> 00:29:14.000 then every single virtual machine would have to be part of VLAN 10. 00:29:14.000 --> 00:29:23.000 But by having virtual switches inside the servers and the hypervisors, 00:29:23.000 --> 00:29:25.000 now I can trunk my link. 00:29:25.000 --> 00:29:27.000 If you don't know what trunking is, we'll talk about it later today. 00:29:28.000 --> 00:29:33.000 But trunking, and therefore now this virtual switch can be used to control 00:29:33.000 --> 00:29:34.000 that. 00:29:34.000 --> 00:29:37.000 Maybe that's VLAN 10, that's VLAN 20, that's VLAN 10. 00:29:37.000 --> 00:29:43.000 And as a result of that now, I have the ability to control VLAN subnets, 00:29:43.000 --> 00:29:46.000 broadcast domains from within that server as well. 00:29:46.000 --> 00:29:50.000 So be mindful that even though the physical architecture may look like this, 00:29:50.000 --> 00:29:54.000 you can extend that out into a virtual switch as well. 00:29:54.000 --> 00:29:56.000 And it's important for the real world, 00:29:56.000 --> 00:30:00.000 for you as a network enterprise admin to have control of that switch. 00:30:01.000 --> 00:30:05.000 Now I know your virtual machine admins are probably like, no, no, no, no, no. 00:30:05.000 --> 00:30:07.000 That's ours. It's in our, no, no, no, no, no. 00:30:07.000 --> 00:30:09.000 That's a networking thing. 00:30:09.000 --> 00:30:14.000 And it's very important that the networking professionals have control over 00:30:14.000 --> 00:30:16.000 those virtual switches. Why? 00:30:16.000 --> 00:30:20.000 Because those virtual switches are part of your architecture. 00:30:20.000 --> 00:30:21.000 And more importantly, 00:30:21.000 --> 00:30:26.000 they're part of your security architecture as a networking professional. 00:30:27.000 --> 00:30:28.000 Therefore, 00:30:28.000 --> 00:30:32.000 it's imperative that you have full control over those virtual switches. 00:30:32.000 --> 00:30:35.000 And that's why Cisco has their own virtual switch. 00:30:35.000 --> 00:30:40.000 So that way there you can have that virtual switch installed in that server 00:30:41.000 --> 00:30:44.000 instead of using VMware's vSwitch. Okay. 00:30:44.000 --> 00:30:46.000 You can use Cisco switch instead, 00:30:46.000 --> 00:30:49.000 and it behaves just like your Cisco iOS products. 00:30:50.000 --> 00:30:51.000 So that way there, 00:30:51.000 --> 00:30:56.000 what you are doing can easily be extended into that virtual switch on your 00:30:56.000 --> 00:30:57.000 device. 00:30:57.000 --> 00:31:01.000 So it's going to allow you to manage your VLAN to VLAN communication using 00:31:01.000 --> 00:31:04.000 your virtual switches inside of that actual server. 00:31:06.000 --> 00:31:09.000 All right. So that is our architecture discussion, folks. 00:31:09.000 --> 00:31:14.000 There's many good points in there that I encourage you to ensure you know, 00:31:14.000 --> 00:31:17.000 in case they come up as a multiple choice question on the certification 00:31:17.000 --> 00:31:18.000 exam. 00:31:20.000 --> 00:31:21.000 Thank you.