WEBVTT

0:00:03.200000 --> 0:00:04.620000
 Welcome to this video.

0:00:04.620000 --> 0:00:08.040000
 We're going to focus in now on some
 of the connections that you will see

0:00:08.040000 --> 0:00:12.560000
 on the backs of access points and controllers,
 certain names of these

0:00:12.560000 --> 0:00:15.720000
 connections and what the purposes
 are of these connections.

0:00:15.720000 --> 0:00:24.600000
 So we call this the infrastructure connections
 of your wireless LAN components.

0:00:24.600000 --> 0:00:29.780000
 Okay, so as a brief review here, we
 know that in your typical corporate

0:00:29.780000 --> 0:00:34.580000
 enterprise or campus network or hospital,
 your wireless LAN will consist

0:00:34.580000 --> 0:00:39.780000
 of one or more access points, probably
 lightweight access points could

0:00:39.780000 --> 0:00:42.420000
 be autonomous or standalone.

0:00:42.420000 --> 0:00:48.260000
 Wireless Nix on your end devices like
 your laptops, PCs, servers, tablet,

0:00:48.260000 --> 0:00:53.120000
 smartphones, wireless transceivers
 that are built into the Wi-Fi host

0:00:53.120000 --> 0:00:57.660000
 and the access points, then you're probably
 going to have a controller.

0:00:57.660000 --> 0:01:00.540000
 Now this is optional, but
 you'll probably see that.

0:01:00.540000 --> 0:01:05.220000
 So the access points and the controllers
 are connected to the physical

0:01:05.220000 --> 0:01:09.860000
 wired network, and they have to use
 this to exchange data between each

0:01:09.860000 --> 0:01:14.260000
 other, as well as to put the data from
 you, the Wi-Fi client, onto the

0:01:14.260000 --> 0:01:16.980000
 wired network so it can ultimately
 get to the internet or wherever it

0:01:16.980000 --> 0:01:21.240000
 needs to go. So what do these
 connections look like?

0:01:21.240000 --> 0:01:25.940000
 All right, so let's start here.

0:01:25.940000 --> 0:01:29.040000
 So we've got your lightweight
 access point.

0:01:29.040000 --> 0:01:32.620000
 On the back end, it's going to
 have one or two uplink ports.

0:01:32.620000 --> 0:01:35.600000
 This is what's going to connect
 to your wired switch.

0:01:35.600000 --> 0:01:39.620000
 Now those uplink ports, like it says
 here, are typically gigabit links,

0:01:39.620000 --> 0:01:42.300000
 10, 100, 1000 gigabit links.

0:01:42.300000 --> 0:01:45.880000
 So clearly it has to connect to a switch
 port that at least supports that

0:01:45.880000 --> 0:01:48.520000
 speed if not faster.

0:01:48.520000 --> 0:01:53.880000
 So switch ports must meet or exceed
 the bandwidth requirements of the

0:01:53.880000 --> 0:01:56.380000
 access point uplinks.

0:01:56.380000 --> 0:02:03.640000
 All right, so here's an example of the
 back of one of your access points.

0:02:03.640000 --> 0:02:08.380000
 So the console port is what you would
 connect to to initially configure

0:02:08.380000 --> 0:02:13.420000
 it. Now this would just be typically
 on a standalone or autonomous access

0:02:13.420000 --> 0:02:16.500000
 point. You wouldn't normally have to
 configure anything on a lightweight

0:02:16.500000 --> 0:02:19.380000
 access point. You just plug
 it into the wired network.

0:02:19.380000 --> 0:02:24.380000
 It will do DHCP, and as part of doing
 DHCP, hopefully it will learn the

0:02:24.380000 --> 0:02:26.460000
 IP address of the wireless
 LAN controller.

0:02:26.460000 --> 0:02:29.240000
 So no configuration necessary
 on your part.

0:02:29.240000 --> 0:02:33.000000
 But on an autonomous or standalone access
 point, yes, you would want to

0:02:33.000000 --> 0:02:36.580000
 configure the console port and at a
 minimum, you want to give it an IP

0:02:36.580000 --> 0:02:41.220000
 address. That way you can then connect
 to the GUI and browse to it.

0:02:41.220000 --> 0:02:45.420000
 And then you're going to have one port
 that's probably labeled POE, which

0:02:45.420000 --> 0:02:52.240000
 stands for power because they're going
 to be up on the ceiling or maybe

0:02:52.240000 --> 0:02:54.260000
 even behind the ceiling tile.

0:02:54.260000 --> 0:02:56.280000
 So you're going to be running an ethernet
 cable to them and you're going

0:02:56.280000 --> 0:02:59.620000
 to running power over
 that ethernet cable.

0:02:59.620000 --> 0:03:04.000000
 And if you have an aux port,
 you could use that.

0:03:04.000000 --> 0:03:08.700000
 The aux port is usually bundled with
 the power over ethernet port.

0:03:08.700000 --> 0:03:12.760000
 And we're going to talk more about that
 when we talk about link aggregation.

0:03:12.760000 --> 0:03:14.940000
 All right, what about
 the controller?

0:03:14.940000 --> 0:03:20.580000
 Now this here is one of Cisco's this
 is the 9800 series controllers.

0:03:20.580000 --> 0:03:22.720000
 And what type of interfaces
 will you find on this?

0:03:22.720000 --> 0:03:26.480000
 Now, clearly we're talking about an
 appliance, a physical box that was

0:03:26.480000 --> 0:03:29.340000
 purpose built to be a wireless
 LAN controller.

0:03:29.340000 --> 0:03:34.000000
 Well, it's also going to have a console
 port that you can connect to for

0:03:34.000000 --> 0:03:36.820000
 sending for getting access
 to the command line.

0:03:36.820000 --> 0:03:37.960000
 No IP address needed.

0:03:37.960000 --> 0:03:42.160000
 You know you would connect via secure
 CRT or hyper terminal or putty or

0:03:42.160000 --> 0:03:46.860000
 something just like you would to the
 console port of a router or a switch.

0:03:46.860000 --> 0:03:49.960000
 Now it's also going to have something
 called a service port.

0:03:49.960000 --> 0:03:53.120000
 The service port does support IP.

0:03:53.120000 --> 0:03:56.080000
 So you can connect an ethernet cable
 to the service port and using the

0:03:56.080000 --> 0:03:59.740000
 service port you can get access to
 the GUI of the device to configure

0:03:59.740000 --> 0:04:01.880000
 it that way and manage it.

0:04:01.880000 --> 0:04:05.480000
 You might have one or
 more redundancy ports.

0:04:05.480000 --> 0:04:08.960000
 This is to be able to connect two
 of these controllers together.

0:04:08.960000 --> 0:04:14.200000
 So one can be providing a redundant
 backup to the other controller.

0:04:14.200000 --> 0:04:17.380000
 And then you have your data ports, which
 are sometimes called distribution

0:04:17.380000 --> 0:04:20.900000
 ports, which connect
 to the actual switch.

0:04:20.900000 --> 0:04:25.140000
 So now it gets access
 to the wired network.

0:04:25.140000 --> 0:04:30.640000
 Now those distribution system ports
 are what we call data ports.

0:04:30.640000 --> 0:04:34.140000
 You could you could operate
 those in one of two ways.

0:04:34.140000 --> 0:04:38.340000
 You could operate them as individual
 interfaces to where each data port

0:04:38.340000 --> 0:04:40.700000
 is assigned its own
 unique IP address.

0:04:40.700000 --> 0:04:44.900000
 And now some access points could build
 capwap tunnels to maybe the first

0:04:44.900000 --> 0:04:49.580000
 data port. Other groups of access points
 could build their capwap tunnels

0:04:49.580000 --> 0:04:53.360000
 to the second data port
 and so on and so forth.

0:04:53.360000 --> 0:04:57.400000
 The downside to that though is if I have
 a grouping of let's say a hundred

0:04:57.400000 --> 0:05:02.260000
 access points and they are all connected,
 they're all building their capwap

0:05:02.260000 --> 0:05:06.880000
 tunnels to the IP address right
 here on this first port.

0:05:06.880000 --> 0:05:09.100000
 But what happens if
 that port goes down?

0:05:09.100000 --> 0:05:12.080000
 Now they've lost their connectivity
 to their controller in a lightweight

0:05:12.080000 --> 0:05:16.000000
 access point without a connection
 to the controller is useless.

0:05:16.000000 --> 0:05:19.360000
 It's going to kick off all the Wi-Fi
 clients that are on it and it won't

0:05:19.360000 --> 0:05:22.300000
 allow any new Wi-Fi clients
 to connect to it.

0:05:22.300000 --> 0:05:28.880000
 So a better idea would be to do something
 called link aggregation and

0:05:28.880000 --> 0:05:32.980000
 bundle those ports into a
 link aggregation group.

0:05:32.980000 --> 0:05:36.620000
 So when you do that, it's kind of like
 you're doing ether channeling.

0:05:36.620000 --> 0:05:39.420000
 You're bundling them into the group
 and then you're going to put your

0:05:39.420000 --> 0:05:44.000000
 IP address not on the physical port
 itself but on something else like

0:05:44.000000 --> 0:05:48.180000
 maybe a management interface, a logical
 port that will be associated to

0:05:48.180000 --> 0:05:50.340000
 this link aggregation group.

0:05:50.340000 --> 0:05:53.520000
 So now all your access points will
 just be building a capwap tunnel to

0:05:53.520000 --> 0:05:59.300000
 a single IP to a single IP address which
 is not dependent on one single

0:05:59.300000 --> 0:06:05.480000
 port. And this can be implemented on
 access points, controllers, or both

0:06:05.480000 --> 0:06:09.540000
 and it does provide a little
 bit of load sharing as well.

0:06:09.540000 --> 0:06:16.600000
 So that completes our review on the infrastructure
 connections on wireless