WEBVTT

0:00:03.000000 --> 0:00:08.380000
 Hello and welcome to this video titled,
 What is a Wireless Architecture?

0:00:08.380000 --> 0:00:10.560000
 So here are the topics we're
 going to cover in this video.

0:00:10.560000 --> 0:00:12.880000
 I'm going to describe what
 is a wireless architecture.

0:00:12.880000 --> 0:00:17.640000
 I'm going to define that term for you
 so it becomes familiar and then

0:00:17.640000 --> 0:00:21.900000
 we're going to look at some high
-level architectural differences.

0:00:21.900000 --> 0:00:24.080000
 So let's start with a question.

0:00:24.080000 --> 0:00:26.820000
 What do we mean by a wireless
 architecture?

0:00:26.820000 --> 0:00:28.620000
 What does that term actually mean?


0:00:28.620000 --> 0:00:33.120000
 Well, as this slide says here, wireless
 lands can be designed using a

0:00:33.120000 --> 0:00:37.060000
 variety of devices and in a
 variety of configurations.

0:00:37.060000 --> 0:00:42.340000
 At an absolute minimum, you have to have
 a wireless client like your laptop,

0:00:42.340000 --> 0:00:46.000000
 PC, smartphone or tablet
 and an access point.

0:00:46.000000 --> 0:00:49.640000
 That's the absolute minimum configuration
 for a wireless architecture.

0:00:49.640000 --> 0:00:53.780000
 But in Cisco's world, we want to get
 away from that and introduce even

0:00:53.780000 --> 0:00:57.540000
 more complexity by having a controller
 in the environment as well that

0:00:57.540000 --> 0:00:59.380000
 controls the access point.

0:00:59.380000 --> 0:01:02.900000
 And when you introduce that, that involves
 a whole bunch of permutations

0:01:02.900000 --> 0:01:06.160000
 that we call architectures.

0:01:06.160000 --> 0:01:09.740000
 So these configurations and designs are
 what we call wireless architectures

0:01:09.740000 --> 0:01:12.400000
 and we're going to look at the
 different types of these.

0:01:12.400000 --> 0:01:16.000000
 So what are some of the wireless architectures
 we'll be discussing?

0:01:16.000000 --> 0:01:19.460000
 We'll talk about autonomous architectures,
 their pros and their cons.

0:01:19.460000 --> 0:01:25.380000
 We'll talk about cloud-based architectures,
 converged architectures, mesh

0:01:25.380000 --> 0:01:30.280000
 architectures and centralized
 wireless architectures.

0:01:30.280000 --> 0:01:33.160000
 All right, so let's go into a
 little bit more detail here.

0:01:33.160000 --> 0:01:35.900000
 What are some of the high level
 differences between these?

0:01:35.900000 --> 0:01:40.300000
 So all of these architectures fall into
 one of two categories that we'll

0:01:40.300000 --> 0:01:45.380000
 be discussing. Either they are distributed
 architectures or they are centralized

0:01:45.380000 --> 0:01:50.240000
 architectures. Now, these terms can
 mean different things depending on

0:01:50.240000 --> 0:01:52.080000
 who you're talking to.

0:01:52.080000 --> 0:01:56.840000
 For example, some people think of a
 distributed architecture meaning,

0:01:56.840000 --> 0:02:02.320000
 okay, we just have five or ten or 500
 access points in our organization,

0:02:02.320000 --> 0:02:07.880000
 but each one is operating totally independently
 of all the other ones.

0:02:07.880000 --> 0:02:11.380000
 In other words, they are standalone
 or autonomous access points.

0:02:11.380000 --> 0:02:15.060000
 So when you introduce a new access
 point, you have to log on to it and

0:02:15.060000 --> 0:02:17.040000
 configure it yourself manually.

0:02:17.040000 --> 0:02:20.100000
 So we can say in that situation that
 that's a distributed architecture

0:02:20.100000 --> 0:02:24.320000
 because the logic or intelligence that's
 controlling your wireless LANs

0:02:24.320000 --> 0:02:29.060000
 is distributed among all these
 independent access points.

0:02:29.060000 --> 0:02:33.860000
 But another way of looking at this
 is, well, if we're going to have a

0:02:33.860000 --> 0:02:37.640000
 wireless LAN controller that's going
 to reach out and control all those

0:02:37.640000 --> 0:02:41.280000
 access points, all right, well, we can
 still have the concept of distributed

0:02:41.280000 --> 0:02:45.260000
 and centralized architectures even with
 that because when you introduce

0:02:45.260000 --> 0:02:48.520000
 a controller, you could have
 lots of controllers.

0:02:48.520000 --> 0:02:51.600000
 So we could think of a distributed architecture
 as being many controllers,

0:02:51.600000 --> 0:02:55.980000
 either physical boxes sort of spread
 out among my enterprise or campus,

0:02:55.980000 --> 0:02:59.160000
 each one controlling a subset
 of access points.

0:02:59.160000 --> 0:03:01.060000
 That could be considered
 distributed.

0:03:01.060000 --> 0:03:04.280000
 Or we could say, hey, let's move the
 controller right down into the switch

0:03:04.280000 --> 0:03:08.060000
 itself. Let's give the switch that's
 physically connected to the access

0:03:08.060000 --> 0:03:12.360000
 point, the ability to be a controller
 inside the switch.

0:03:12.360000 --> 0:03:15.700000
 That would be another example
 of a distributed architecture.

0:03:15.700000 --> 0:03:19.140000
 However, a centralized architecture
 pretty much always means the same

0:03:19.140000 --> 0:03:23.660000
 thing. That you have one or maybe two
 controllers in a central location

0:03:23.660000 --> 0:03:27.940000
 like a data center and all your access
 points are connecting to that and

0:03:27.940000 --> 0:03:29.700000
 being managed by that.

0:03:29.700000 --> 0:03:32.000000
 So we're going to see the various architectures
 we're going to talk about

0:03:32.000000 --> 0:03:34.660000
 and they're going to fall into some
 of those different categories.

0:03:34.660000 --> 0:03:38.380000
 So what are some common questions that
 need to be answered when we're

0:03:38.380000 --> 0:03:40.600000
 dealing with any of
 these architectures?

0:03:40.600000 --> 0:03:45.320000
 So how you answer these questions will
 determine which architecture is

0:03:45.320000 --> 0:03:47.860000
 most appropriate for you.

0:03:47.860000 --> 0:03:52.700000
 Well, number one, where's the management
 of the access points originated?

0:03:52.700000 --> 0:03:55.320000
 Are the access points
 managing themselves?

0:03:55.320000 --> 0:03:58.520000
 Is management and control those access
 points coming from a switch they're

0:03:58.520000 --> 0:04:02.380000
 directly connected to or from some controller
 appliance much, much further

0:04:02.380000 --> 0:04:06.200000
 away? That will dictate what type
 of architecture that you use.

0:04:06.200000 --> 0:04:11.240000
 Number two. Do the access points have
 a functional GUI or command line

0:04:11.240000 --> 0:04:18.260000
 for management? Number three, who performs
 authentication of Wi-Fi clients?

0:04:18.260000 --> 0:04:21.960000
 Do we want the access point to do that
 or do we want to offload that to

0:04:21.960000 --> 0:04:24.060000
 a controller somewhere?

0:04:24.060000 --> 0:04:28.880000
 And number four, what is the actual
 path of user data as it leaves the

0:04:28.880000 --> 0:04:33.440000
 Wi-Fi domain and enters
 the distribution system?

0:04:33.440000 --> 0:04:38.300000
 So that covers this real high-level
 overview of what is a wireless LAN

0:04:38.300000 --> 0:04:41.600000
 architecture. And thank you very
 much for watching this video.

