All language subtitles for Free-CCNA-Wireless-Architectures-Day-56-CCNA-200-301-Complete-Course_en

Welcome to Jeremy’s IT Lab. This is\xa0\n

If you like these videos, please\xa0\n

Also, please like and leave a comment, and\xa0\n

series of videos. Thanks for your help. In this\xa0\n

In the previous video we looked at various\xa0\n

but in this video we’ll look at some more\xa0\n

By architectures, I mean how the wireless\xa0\n

network as a whole, including the wired network\xa0\n

access points, 1.1.e, controllers,\xa0\n

Here’s what we’ll cover. Before covering wireless\xa0\n

messages and the 802.11 frame format. 802.11\xa0\n

wired Ethernet LANs, so there are some\xa0\n

is different as well. Then we’ll cover different\xa0\n

lightweight, and cloud-based. Finally we’ll look\xa0\n

We didn’t cover WLCs in the previous video.\xa0\n

access points, and are essential in large\xa0\n

thousands of wireless access points. Make\xa0\n

for a bonus question from Boson Software’s\xa0\n

So let’s look at the 802.11 frame format first.\xa0\n

802.3 Ethernet frame. 802.11 frames are\xa0\n

but for the CCNA you don’t have to learn it in as\xa0\n

I’ll just provide a high-level overview. First\xa0\n

header than an Ethernet header, but depending on\xa0\n

the fields might not be present in the frame. For\xa0\n

but not all messages use all 4 address fields.\xa0\n

frame control. It’s 2 bytes, 16 bits, in\xa0\n

message type and subtype. I’ll talk about\xa0\n

Next is the Duration/ID field. As the name\xa0\n

Depending on the message type it can indicate\xa0\n

dedicated for transmission of the frame. Or\xa0\n

the connection, between the wireless\xa0\n

field is similar to the Ethernet type/length\xa0\n

Next up the addresses. Up to four addresses\xa0\n

Which addresses are present, and their\xa0\n

The four addresses that can be\xa0\n

DA. This is the final recipient of the frame. The\xa0\n

The receiver address, RA. This is the immediate\xa0\n

final destination. And the transmitter address,\xa0\n

but not necessarily the original sender,\xa0\n

Having four addresses like this isn’t\xa0\n

but 802.11 wireless networks have unique\xa0\n

control. It’s used to reassemble fragments and\xa0\n

control, which as you probably guessed is\xa0\n

After that is a field called HT, high throughput,\xa0\n

throughout operations. I didn’t mention\xa0\n

Wi-Fi 4, is also known as high throughput\xa0\n

is also known as Very High Throughput, VHT, Wi-Fi.\xa0\n

and after it is the frame body, which is the\xa0\n

And finally there is the FCS, frame\xa0\n

Just like in an Ethernet frame, this is used to\xa0\n

for 802.11 frames. Remember, not all of these\xa0\n

It all depends on the version of 802.11 being used\xa0\n

and their operations can be much more complicated\xa0\n

in wireless networks you should definitely learn\xa0\n

Next, before 802.11 message types, I want\xa0\n

which I only briefly mentioned in the last video.\xa0\xa0

Access points are used to bridge traffic\xa0\n

for example hosts connected to the wired network.\xa0\n

it must be associated with the AP, and there is a\xa0\n

There are three connection states. First, when\xa0\n

with the AP. Second, when the station is\xa0\n

And finally, when the station is authenticated\xa0\n

be authenticated and associated with the AP to\xa0\n

simple version of that process. First, the station\xa0\n

APs and BSSs are available, and the AP sends\xa0\n

Note that there are actually two ways for a\xa0\n

scanning, where the station sends probe requests\xa0\n

That’s what I show in the diagram on the left.\xa0\n

station listens for beacon messages from an AP.\xa0\n

the BSS. Okay, so using either active or passive\xa0\n

BSS. However it’s still in that first connection\xa0\n

Then there is an authentication exchange, for\xa0\n

and the AP authenticates it. If this is\xa0\n

authenticated but not yet associated. Finally,\xa0\n

and if this is successful we have\xa0\n

authenticated and associated. Finally the\xa0\n

Now, all of these messages, probe,\xa0\n

are the same type of 802.11 message.\xa0\n

There are three 802.11 message types.\xa0\n

are used to manage the BSS. For example, the\xa0\n

beacon, probe, authentication, and\xa0\n

There are more management messages than these,\xa0\n

is control. These frames are used to control\xa0\n

assist with the delivery of management and data\xa0\n

send messages, which I very briefly mentioned\xa0\n

Also, ACK messages, used to acknowledge that\xa0\n

The third type of message is data. These are\xa0\n

Okay, here’s a brief overview of\xa0\n

I can’t say exactly which information you’ll be\xa0\n

good idea to have a basic understanding of these\xa0\n

First up we are going to talk about different ways\xa0\n

There are three main wireless AP deployment\xa0\n

I’ll introduce autonomous APs first. Autonomous\xa0\n

on a WLC, wireless LAN controller. Hence the\xa0\n

that means they are configured individually.\xa0\n

remotely via telnet or SSH, or also an HTTP or\xa0\n

small networks this is fine, but configuring\xa0\n

becomes unrealistic. Note that an IP address for\xa0\n

so you can connect via telnet, SSH, or HTTP to\xa0\n

as how much power it should use to transmit and\xa0\n

manually per AP. Security policies, for example\xa0\n

Other settings such as QoS are also configured\xa0\n

management of the APs. So, as I said before,\xa0\n

Here’s an example network with autonomous\xa0\n

should connect to the wired network with a\xa0\n

so it might be obvious that a trunk connection\xa0\n

but even if the AP provides only one SSID,\xa0\n

It’s because the management traffic used\xa0\n

as well as the other devices, the\xa0\n

I might not have mentioned this earlier in the\xa0\n

traffic separate from regular data traffic\xa0\n

So, there are trunk links between each of\xa0\n

for the wireless clients, as well as VLAN99 for\xa0\n

data traffic from wireless clients has a very\xa0\n

wireless clients associated with the same AP.\xa0\n

you’ll understand it when you see the path that\xa0\n

So, with an autonomous AP traffic between these\xa0\n

and then to the other AP and PC. Or between\xa0\n

there’s no need for the traffic to even go\xa0\n

this is different compared to the traffic\xa0\n

Notice that each VLAN has to stretch across the\xa0\n

bad practice. Why is that? Why is it bad to have\xa0\n

Well, there are many reasons, but here are a\xa0\n

is a broadcast domain, and if the VLANs are\xa0\n

each broadcast message will be\xa0\n

The second reason is that\xa0\n

A big focus of modern network design is\xa0\n

because disabling links means a reduction in total\xa0\n

labor-intensive if it has to be done over dozens\xa0\n

autonomous APs can be used in small networks, but\xa0\n

A large network can have thousands of APs,\xa0\n

APs one-by-one is not realistic. Finally,\xa0\n

in the modes covered in the previous video,\xa0\n

Now let’s talk about the next major deployment\xa0\n

of an AP can be split between the AP and a\xa0\n

handle real-time operations like transmitting\xa0\n

encryption and decryption of traffic,\xa0\n

However, other functions are carried out by\xa0\n

and QoS management, client authentication,\xa0\n

etc. The WLC centrally controls all of\xa0\n

This is called split-MAC architecture,\xa0\n

because the functions are split between the\xa0\n

also used to centrally configure the lightweight\xa0\n

and manually configure them one-by-one,\xa0\n

Note that the WLC can be located in the same\xa0\n

or in a different subnet and VLAN. I’ll talk about\xa0\n

and lightweight APs authenticate each other using\xa0\n

These certificates follow the X.509 standard,\xa0\xa0

which is the same that websites use to prove their\xa0\n

only authorized APs can join the network, so an\xa0\n

Here’s an example network, with a wireless\xa0\n

lightweight APs use a protocol called CAPWAP,\xa0\n

points, to communicate. CAPWAP is based on\xa0\n

access point protocol. For communications, two\xa0\n

like this. Note that each of\xa0\n

represents two separate tunnels,\xa0\n

So, let’s see what those two tunnels are. One is\xa0\n

There’s another port number for you to remember,\xa0\n

So, this tunnel is used to configure the\xa0\n

Note that all traffic in this tunnel is\xa0\n

The second tunnel is the data tunnel, using UDP\xa0\n

sent through this tunnel to the WLC. It does not\xa0\n

to another client associated with the same AP.\xa0\n

Now, of course in reality the traffic does pass\xa0\n

However it is encapsulated with new headers to\xa0\n

IPsec tunnels in the WAN video. Note that traffic\xa0\n

but you can configure it to be encrypted using\xa0\n

layer security. I mentioned TLS, transport\xa0\n

DTLS is basically the same thing, but it\xa0\n

Now, here’s another difference between\xa0\n

Because all traffic from wireless clients\xa0\n

APs connect to switch access ports, not\xa0\n

if you want, but there’s no need for\xa0\n

To make that clear, let me demonstrate the\xa0\n

Okay, I’ve simplified the diagrams. On the\xa0\n

a lightweight AP and a WLC. On the right we have\xa0\n

local-MAC architecture. As you know, when using\xa0\n

with a trunk link. There should be a VLAN for\xa0\n

network device management. If a wireless client\xa0\n

it sends the frame to its wireless access point,\xa0\n

the wired network, which will then forward it\xa0\n

wants to send traffic to another device associated\xa0\n

the wired network. The frame is sent to the AP\xa0\n

When using a split-MAC architecture, this is all\xa0\n

have to connect to the switch with a trunk, an\xa0\n

needed to connect the WLC to the wired network. In\xa0\n

a VLAN and forming the border between the wired\xa0\n

Traffic from a wireless client is sent to the\xa0\n

sends it over the wired network to the default\xa0\n

Even if the traffic is destined for a host\xa0\n

to the WLC, and then tunneled back and sent to\xa0\n

demonstrate the differences between the traffic\xa0\n

There are some key benefits to using a split-MAC\xa0\n

don’t have to memorize it, but you should\xa0\n

First, scalability. With a WLC, or even multiple\xa0\n

and support a network with thousands of APs. That\xa0\n

WLCs also provide dynamic channel assignment.\xa0\n

each AP should use, so you don’t have to\xa0\n

The WLC can also automatically set the appropriate\xa0\n

coverage without interfering with other APs.\xa0\n

coverage. So, when an AP stops functioning, the\xa0\n

to avoid coverage holes. Seamless roaming is also\xa0\n

noticeable delay. Another benefit is client load\xa0\n

the WLC can associate the client with the\xa0\n

the last benefit I’ll mention is security and QoS\xa0\n

policies ensures consistency across the network.\xa0\n

but definitely be aware that the split-MAC\xa0\n

Now, just as autonomous APs can function as\xa0\n

APs have different modes as well. First is local\xa0\n

a BSS, or multiple BSSs for clients to associate\xa0\n

of an AP. Next is FlexConnect mode. In this mode\xa0\n

associate with, but it adds extra functionality.\xa0\n

forward traffic between the wired and wireless\xa0\n

So, here on the left are some standard\xa0\n

All traffic is tunneled to the WLC first.\xa0\xa0

But what if connectivity to the WLC is lost,\xa0\n

a problem if FlexConnect is enabled, because\xa0\n

like an autonomous AP, no need to tunnel the\xa0\n

The next mode is sniffer mode. In this mode\xa0\n

Instead it is dedicated to capturing 802.11 frames\xa0\xa0

and sending them to a device running software\xa0\n

traffic and then sends those packets to\xa0\n

The next mode is Monitor mode. Again, it doesn’t\xa0\n

to receiving 802.11 frames to detect rogue\xa0\n

device, an AP can send de-authentication messages\xa0\n

The next mode, rogue detector mode, is similar\xa0\n

AP does not even use its radio. Instead it\xa0\n

but it receives a list of suspected rogue clients\xa0\n

ARP messages on the wired network and correlating\xa0\n

it can detect rogue devices. Okay, the next is\xa0\n

clients. That is SE-connect, or spectrum expert\xa0\n

spectrum analysis on all channels. It can send\xa0\n

Expert on a PC to collect and analyze the data.\xa0\n

Okay, the next mode is bridge/mesh mode.\xa0\xa0

Like the autonomous AP’s outdoor bridge mode,\xa0\n

between sites, even over long distances. A mesh\xa0\n

Here’s an example similar to what we saw in the\xa0\n

And here’s an example that looks more like\xa0\n

potentially long distances. Now there’s\xa0\n

which basically adds flexconnect functionality\xa0\n

access points to locally forward traffic\xa0\n

Here’s that complete list. This is a lot\xa0\n

looked at each one, but that’s okay. If you\xa0\n

Cisco has documentation about each of them\xa0\n

but for the CCNA exam you should just be able to\xa0\n

I don’t recommend memorizing this list,\xa0\n

Now let’s look at the last main type of AP\xa0\n

architecture is in between autonomous AP and\xa0\n

functions. Basically, it involves autonomous\xa0\n

An example is Cisco Meraki, and because the\xa0\n

you should be aware of for the CCNA. The Meraki\xa0\n

can be used to configure APs, monitor the\xa0\n

etc. Just like I mentioned for WLCs, Meraki\xa0\n

what transmit power to use, etc. However,\xa0\n

It is sent directly to the wired\xa0\n

So, only what we call management traffic\xa0\n

Let’s see an example. Information such as RF\xa0\n

is sent to servers in the Meraki cloud.\xa0\n

PCs communicating with each other, is direct and\xa0\n

So, I think you can see how the functionality\xa0\n

Here’s an image from Meraki demonstrating the same\xa0\n

the green arrow, is sent to the Meraki cloud.\xa0\n

is sent directly to its intended destination\xa0\n

Here’s another image from that same Meraki\xa0\n

This is where you monitor the wireless network,\xa0\n

I use the Cisco Meraki solution in my job and\xa0\n

and the Meraki dashboard makes it easy to monitor\xa0\n

Okay, that’s all for the cloud-based\xa0\n

between autonomous AP and split-MAC architecture.\xa0\n

The final topic for today is WLC deployment\xa0\n

LAN controllers, this applies\xa0\n

not autonomous AP or cloud-based AP architectures.\xa0\n

four ways to deploy a WLC in your network. I’ll\xa0\n

them first. First, a unified WLC deployment. The\xa0\n

device, in a central location of the network.\xa0\n

The WLC is a VM running on a server,\xa0\n

Keep in mind that this is not the same as the\xa0\n

In this case the APs are not cloud-based, they\xa0\n

here simply refers to where the WLC is. In an\xa0\n

in a switch in the network. And finally\xa0\n

the WLC functionality is actually integrated\xa0\n

So here is an example of a unified WLC, a\xa0\n

that is deployed in a central location of the\xa0\n

6000 APs, and if you need more than that you can\xa0\n

suitable for a large enterprise campus. Here’s\xa0\n

Of course the larger models are more powerful\xa0\n

Next is the cloud-based WLC. In this case the\xa0\n

a private cloud in a data center. This kind of\xa0\n

and again if more are needed you can add\xa0\n

a split-MAC architecture with a cloud-based WLC\xa0\n

we looked at earlier. These are lightweight APs,\xa0\n

Next, embedded WLCs. In this case\xa0\n

This type of WLC can support up to about 200\xa0\n

more switches with embedded WLCs. Embedded\xa0\n

Finally, Cisco Mobility Express places the WLC\xa0\n

internal CAPWAP tunnels to it, and the other\xa0\n

up to about 100 APs, and you’ll have to add\xa0\n

to support more APs. This kind of deployment\xa0\n

Here’s that summary of the\xa0\n

and I’ve added information about how\xa0\n

Definitely be familiar with these\xa0\n

Okay, here’s what we covered in this video.\xa0\n

different kinds of 802.11 messages and the\xa0\n

Because wireless networks have different\xa0\n

there are quite a few differences between 802.3\xa0\n

We then covered the three main kinds of APs,\xa0\n

sure you know the basic characteristics of each\xa0\n

the different wireless LAN controller deployment\xa0\n

Make sure to watch until the end\xa0\n

question from Boson Software’s ExSim for\xa0\n

What kind of message is an 802.11 probe request?\xa0\n

Okay, the answer is C, management. Here are\xa0\n

with a few examples of each.\xa0\nOkay, let’s go to question 2.

Which of the following AP\xa0\n

Pause the video now to select\xa0\nthe best answer, select two.

Okay, the answers are C, lightweight, and D,\xa0\xa0

cloud-based. Lightweight APs are centrally managed\xa0\n

are centrally managed by a cloud server such\xa0\n

Which of the following AP\xa0\n

Pause the video now to select the best answer.

Okay, the answer is C, lightweight. Lightweight\xa0\n

two tunnels, a control tunnel and a data\xa0\n

Which of the following lightweight\xa0\n

Pause the video to select\xa0\nthe best answers, select two.

Okay, the answers are A, local and C, flexconnect.\xa0\n

FlexConnect offers the additional ability\xa0\n

even if the tunnels to the WLC go\xa0\n

Which of the following WLC deployments\xa0\n

Pause the video now to select the best answer.

Okay, the answer is D, unified. Embedded WLCs\xa0\n

mobility express about 100, and unified\xa0\n

Now let’s take a look at a bonus practice\xa0\n