All language subtitles for Free-CCNA-VLANs-Part-3-Day-18-CCNA-200-301-Complete-Course_en

This is a free, complete course for the CCNA.

If you like these videos, please subscribe\n

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

This video will once again cover the topic\nof VLANs..

Although we’ve already covered the most\n

a few more things you should know about VLANs\nfor your CCNA.

This is going to be a long video again, so\n

First off, here are the topics that will be\n

First off, a little addition to the previous\n

of a native VLAN on a router when using router\n

Next up, we will look at a few wireshark captures\n

Wireshark is a great tool for network engineers,\n

series to help you understand these topics.

After that we’ll look at the final method\n

also known as multilayer switching.

I’ve always told you that switches are Layer\n

many modern switches are actually Layer 3\n

Next up are two topics which have actually\n

DTP, the dynamic trunking protocol, and VTP,\n

I was planning to cover these in this video,\n

reserve a separate video for them.

Although these have both been removed from\n

be important for you to understand these topics\n

you may actually see some questions about\n

However, I will give just a basic overview\n

Before getting started, I want to say make\n

quiz, from now on I’ll be featuring one\n

set of practice exams for the CCNA.

If you want to get a copy of Boson ExSim for\n

No other practice exams help you get ready\n

you can I highly recommend getting and using\n

So let’s move on to the first point, using\n

I said in the previous lecture video that\n

an unused VLAN, as the native VLAN feature\n

I will talk more about network security later\n

However, if you want to use the native VLAN\n

The native VLAN feature does have one benefit.

Because frames in the native VLAN aren’t\n

is smaller so it allows the device to send\n

In the previous video, I set the native VLAN\n

So, just for this demonstration let’s set\n

There are 2 methods of configuring the native\n

First up, you can use the command ENCAPSULATION\n

This tells the router that this subinterface\n

just like the native VLAN on a switch.

It will assume untagged frame belong to the\n

The second option is to not use a subinterface at all, but just

for the native VLAN on the physical interface of the router.

The ENCAPSULATION DOT1Q command is not necessary in this case.

Okay, let’s look at each option.

First, I will configure the first option.

On the g0/0.10 interface, I configured ENCAPSULATION\n

Note that this is the complete topology from\n

The only change is that I added NATIVE to\n

Let’s take this opportunity to look at a\n

This PC in VLAN20 has an IP address of 192.168.1.65,\n

I will use wireshark to monitor this connection\n

Wireshark will capture all frames on this\n

take a look at what traffic is passing through.

Let’s send that ping. We will first look\n

It will be in VLAN20, and it’s being sent\n

Here’s the wireshark capture for the ICMP\n

First off, you can see the source and destination\n

Now let’s look at the Ethernet header encapsulating\n

Type: 802.1Q virtual LAN, and notice the hexadecimal\n

I said in the previous video that dot1q is\n

and that is where the TYPE field usually goes.

This here is the ‘TPID’ field of the dot1q\ntag.

Under it, these are the rest of the fields\nof the 802.1Q tag.

First is the PCP, priority code point.

It has a value of 0, so no special priority\n

Under it is the DEI, drop eligible indicator.

Again, a value of 0, so it won’t be dropped\n

Next is the most important field, the VLAN\n

The PC that sent the ping is in VLAN 20, and\n

Finally, under that is the normal TYPE field\n

It normally comes after the SOURCE MAC ADDRESS\n

Next let’s look at the ICMP echo request\n

It will now be in VLAN10, because the destination\nis in VLAN10.

VLAN10 is configured as the native VLAN on\n

Here’s the exact same ICMP echo request,\n

It has been encapsulated with a new Ethernet\n

This is the native VLAN function at work.

Both R1 and SW2 understand that untagged frames\n

That ICMP echo request will continue to the\n

VLAN10 is configured as the native VLAN on\nall devices.

When this PC in VLAN10 sends the ICMP echo\n

R1, which will then tag it in VLAN20, and\n

Now let’s take a quick look at the second\n

router, which is simply configuring the IP\n

no need for a subinterface or the encapsulation\ndot1q command.

First, I used ‘NO INTERFACE G0/0.10’.

Then, I entered interface configuration mode\n

To help you visualize it, here is the output\n

First off, these commands here on the physical\n

The physical interface is configured normally\n

This will be used for the native VLAN, VLAN10.

The other subinterfaces are just like we configured\n

dot1q command and their own IP address.

This will function just like the first option\nwe saw.

SW2 will send VLAN10 packets in untagged frames\n

As I said before, it is recommended that you\n

for security purposes, but if you want to\n

how to do it on a router, so these are two methods you can use.

You might also need to know this for your\nexam, by the way.

Here’s the network diagram once again.

We have one router, and two switches.

Or I should say, two Layer 2 switches.

This is the icon we’ve been using for regular\nLayer 2 switches.

But let me introduce you to another type of\nswitch.

This is the icon I will use for what is called\n

From now on I will use either term, Layer\n

By the way, these are the official Cisco icons\n

but I think the ones I use in my videos look\n

First let’s review exactly what a multilayer\nswitch does.

A multilayer switch is capable of both switching\nAND routing.

A regular layer 2 switch is NOT layer 3 aware,\n

It only cares about Layer 2 information like\nMAC addresses.

You can assign IP addresses to its interfaces\nlike a router.

Previously we haven’t assigned any IP addresses\n

With a Layer 3 switch, you can configure ‘routed\n

Not just physical interfaces, but you can\n

and assign IP addresses to those interfaces.

These are not separate physical\n

software of the switch that can be used to\n

You can configure routes, like static routes,\n

Finally, it can be used for inter-VLAN routing.

So far, we have looked at two methods of inter-VLAN\nrouting.

The first one, in day 16’s video, was using\n

This works, but if you have many VLANs you\n

The second method was router on a stick, which\n

traffic from all VLANs between the switch\n

This is efficient in terms of the number of\n

all of the traffic going to the router and\n

So, in large networks, a multilayer switch\n

Here is the topology again, now let’s\n

And now let’s make one more change.

I’ve replaced the trunk link between SW2\n

we will no longer run VLANs across this.

I’ll talk about this link later and assign\n

SW2’s G0/1 interface. But for now\n

For review, when we used router on a stick\n

between VLANs was sent to R1 first, and then\n

For example, if this PC in VLAN20 wants to\n

From the PC to SW2, from SW2 to R1, tagged\n

from SW2 to SW1, tagged in VLAN10, and finally\n

However, SW2 is a multilayer switch.

It doesn’t have to send the traffic to R1\n

It can do that with something called ‘Switch\n

SVIs (or Switch Virtual Interfaces) are the virtual\n

Configure each PC to use the SVI (NOT the\n

When using router on a stick, the router was\n

This time, we will use the switch’s SVIs\ninstead.

To send traffic to different subnets/VLANs,\n

the switch will route the traffic.

These are the SVIs I configured on SW2.

These are the same IP addresses I configured\n

usable IP address in each subnet.

So, these are already configured on each PC\n

need to change the PC configurations.

Now let’s take a look at the path the traffic\n

The destination is in the 192.168.1.0/26 subnet.

SW2 now has its own routing table, so it looks\n

sees that the destination is connected to\nits VLAN10 SVI.

So, the traffic is now routed to VLAN10.

If SW2 doesn’t have the destination MAC\n

flood the frame to all VLAN10 interfaces.

But, let’s assume it has already learned\n

over its trunk interface, tagged as VLAN10.

SW1 then forwards it to the destination.

Now, what if the hosts want to reach destinations\n

For example, I’ve added a cloud connected\n

Because SW2 is their default gateway, any\n

But our previous router on a stick configurations\n

In addition to configuring virtual interfaces,\n

configure their physical interfaces to operate\n

So, we can assign the subnet 192.168.1.192/30\n

R1, with SW2’s G0/1 interface having an\n

interface having an IP address of 192.168.1.194.

Then, we configure a default route on SW2\n

outside of the LAN will be sent to R1.

I already covered static routes, including\n

explain the concept in depth again, but I\n

So, let’s do that, let’s get into the\n

link between SW2 and R1, and then the SVIs\non SW2.

First off, remove R1’s router on a stick\n

First off, I delete each subinterface with\n

Then, I use the command DEFAULT INTERFACE\n

After that, I used SHOW IP INTERFACE BRIEF\n

Notice the status of the subinterfaces, it\nsays DELETED.

Although we have successfully deleted the\n

a ‘deleted’ status unless we reload the\nrouter.

That’s no problem though, so I’ll just\nleave them.

Then I simply enter interface configuration\n

I use SHOW IP INTERFACE BRIEF again, and you\n

Now let’s look at the switch’s side of\n

First, I reset the G0/1 interface to its default\n

because it was configured as a trunk for router\n

Next up is a very important command, one you\nmust not forget.

This command enables Layer 3 routing on the\n

If you forget this command, your inter-VLAN\n

Next up is another important command, NO SWITCHPORT on the

This is the command that changes the interface\n

Now you will be able to assign an IP address\nto it.

So, I assigned 192.168.1.193/30, and used\n

the IP address is assigned to it just like\na router interface.

Last up is the default route pointing to R1.

As I’ve already shown you in a previous\n

followed by the next hop, in this case 192.168.1.194,\n

I then used SHOW IP ROUTE to confirm, and\n

with a default route pointing to R1, and connected\n

And one additional command you can use to

confirm is SHOW INTERFACES STATUS, which I\n

Notice that, in the VLAN column, instead of\n

Okay, now let’s move on to configure those\nSVIs on SW2.

SVI configuration is very simple.

Here are the configurations for SW2.

Use the command INTERFACE VLAN10, for example,\n

Then assign an IP address, and use NO SHUTDOWN\nto enable it.

SVIs are shutdown but default, so remember\n

I repeated the process for VLAN20 and VLAN30,\n

Now, just to demonstrate one problem you might\n

that doesn’t exist on the switch, VLAN40,\n

I also made sure to enable it with NO SHUTDOWN.

However, look at the SVI itself.

Well, it's because the VLAN doesn’t exist\non the switch.

Let’s take a look at the conditions required\n

First, the VLAN must exist on the switch.

In this case, we haven’t created VLAN40\n

When you assign an access port to a VLAN,\n

will automatically create the VLAN.

However, if you create an SVI for a VLAN that\n

Second, the switch must have at least one\n

and/or one trunk port that allows the VLAN\n

For example, in the topology we’re using\n

VLAN20, so their SVIs can go up.

There are no connected hosts in VLAN30, however\n

over it, so VLAN30’s SVI is up as well.

The VLAN must not be shutdown.

Note that this is NOT the SVI, but the VLAN\nitself.

You can enter VLAN configuration mode, and\n

If you do this, the SVI for that VLAN can’t\nbecome UP/UP.

Note that, I think you can’t do this command\n

Cisco switch if you want to try this one out.

Finally, if the SVI itself is shutdown, it\n

use the NO SHUTDOWN command after you create\n

I used the SHOW IP ROUTE command again, and\n

been added to the route table for the SVIs\n

Okay, so our configurations are all done.

The next video will be a practice lab, so\n

If you have trouble remembering the commands,\n

doing them multiple times, until you feel\nconfident.

So, if one of our PCs wants to reach a destination\n

which will send it to R1, which will take\ncare of it from there.

Note that we didn’t actually configure any\n

on inter-VLAN routing at this point.

If one of our PCs wants to reach a destination\n

VLAN, SW2 will do the inter-VLAN routing without\n

Okay, before moving on to the quiz let’s\n

I showed you two ways of configuring the native\n

Usually, it’s best to just set the native\n

use the native VLAN feature, you should know\n

We looked at some wireshark captures, both\n

because it was in the native VLAN.

Finally, I showed you the final method of\n

I hadn’t talked about before, a Layer 3\n

By configuring SVIs, switch virtual interfaces,\n

subnets and VLANs without having to send the traffic\n

It’s like having a mini router within the\nswitch.

These last two topics, DTP and VTP, will be\n

As I mentioned at the beginning of the video,\n

quiz, a few simple questions to help you review\n

one question from Boson’s ExSim, which is\n

I used Boson ExSim for my CCNA and CCNP, and\n

pass all of my exams on the first try.

If you want to pick up a copy of ExSim, check\n

Let’s go on to question 1 of today’s quiz.

Which TWO answers are valid options to configure\n

(select two, each answer is a complete solution).

Instead of reading out each answer, I’ll\n

A, B, C, and D. Pause the video to think about\n

The answer is B and C. B uses the ENCAPSULATION\n

this is one option for configuring the native\nVLAN on a router.

The other option is C, to simply configure\n

rather than the subinterface.

In that case, you do not need the ENCAPSULATION\nDOT1Q command.

Okay, let’s go to question 2.

You create an SVI for VLAN225 on SW1, assign\n

but the interface remains down/down.

Which TWO options might be causing this? (select\n

B, you didn’t issue the SWITCHPORT MODE\n

C, You didn’t issue the SWITCHPORT ACCESS\n

Or D, No interfaces in VLAN225 are up/up.

Pause the video to think about your answer.

The answer is A and D. In order for an SVI to be up/up, the VLAN

access interface in the VLAN that is up/up,\n

You don’t need to issue the switchport mode\n

Let’s go to question 3, which will be the\n

a sample question from Boson ExSim for CCNA.

Which command is used to configure a switch\n

B, IP Address, followed by the IP address\nand Subnet mask.

Pause the video to think about your answer.

The answer is A, no switchport.

This configures the interface as a routed\n

C, ip routing, is used to enable IP routing\n

Let's go on to today's Boson ExSim practice\nquestion.

You issue the following commands on a Catalyst\n2950 switch.

SWITCHPORT TRUNK ENCAPSULATION DOT1Q.

SWITCHPORT TRUNK NATIVE VLAN 44.

Which of the following statements is true\n

Okay, let's check each option.

A, VLAN 1 traffic will be untagged.

B, VLAN 44 traffic will be untagged.

C, all VLAN traffic will be tagged.

Or D, all VLAN traffic will be untagged.

Please pause the video to think about your\nanswer.

Okay, so I think the correct answer is B,\n

Traffic in the native VLAN will not be tagged\n

So, I think VLAN 44 traffic will be untagged.

And as you can see, B is in fact the correct\nanswer.

Let's check out Boson's explanation a little\nbit.

Traffic from VLAN 44 will be untagged when\n

VLAN 44 traffic is untagged because it has\n

SWITCHPORT TRUNK NATIVE VLAN 44 command.

By default, the native VLAN is VLAN 1.

So, by default A would be the correct answer,\n

You can issue the SWITCHPORT TRUNK NATIVE\n

Okay, here are explanations for why the incorrect\n

It also says you can issue the SHOW INTERFACES\n

that are configured for trunking, the native\n

allowed VLANs for each trunk port.

And here is an example, down here, after we\n

Okay, there are also references here, to Cisco's\n

This is volume 1, chapter 8, about Ethernet\nvirtual LANs, VLANs.

And some Cisco documentation.

I will leave links to these in the description\n

reading about VLAN trunks, dot1q, please check\n

Okay, so that's all for today's Boson ExSim\npractice question.

If you want to get a copy of Boson ExSim,\n

practice exams, please follow the link in\nthe video description.

As usual, there will be supplementary materials\nfor this video.

There will be a review flashcard deck to use\n

Download the deck from the link in the description.

There will also be a packet tracer practice\n

That will be in a separate video.

Before finishing this video, I want to give\n

Thank you to C Mohd, Johan, And then I’m\n

If this is you, please let me know and I will\n

Okay, continuing on, thank you to Mark, Aleksa,\n

Magrathea, Devin, Charlsetta, Lito, Yonatan,\n

Sorry if I pronounced your name wrong, but\n

Please subscribe to the channel, like the\n

with anyone else studying for the CCNA.

If you want to leave a tip, check the links\nin the description.

I'm also a Brave verified publisher and accept\n