All language subtitles for Free-CCNA-VLANs-Part-2-Day-17-Lab-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

Also, remember to download this practice lab\n

If you want more labs like these, I highly\n

the CCNA, click the link in the video description\n

It’s a network simulator like packet tracer,\n

than packet tracer, and it includes plenty\n

I have collapsed all of the other sections\n

IP services, and security fundamentals, but\n

studying now are here, in the network access\nsection.

Configuring VLANs, VLANs, deleting VLANs,\n

in day 18’s lecture video, VLAN configuration,\ntrunking.

Stick around to the end of the video for a\n

And once again, click the link in the description\n

I used NetSim for my CCNP, and NetSim alone\n

to pass all of my exams on the first try.

In this lab, we will configure VLANs, specifically\n

This is the same network topology used in\n

So, let’s get started with step 1.

Step 1 says to configure the switch interfaces\n

Enter privileged exec mode with ENABLE, then global config

So, there are two PC’s in VLAN10, let’s\nconfigure those first.

And the switch creates VLAN10 for us.

Okay, that’s all for these hosts.

Once again, the switch creates the VLAN for us.

Okay, that’s all for SW1 for now.

Enter privileged exec mode with ENABLE.

Then global config mode with CONF T (CONFIGURE\nTERMINAL).

Step 2 is to configure the connection between\n

We should configure an unused VLAN as the\n

Okay, let’s configure the interface.

If you remember from the lecture video, in\n

TRUNK ENCAPSULATION DOT1Q command before configuring the interface

Let’s see if we have to do that here.

SWITCHPORT TRUNK, then use the question mark.

As you can see, there is no option for ENCAPSULATION.

This isn’t a case of packet tracer not supporting\n

switch itself only supports DOT1Q encapsulation.

As I mentioned in the lecture video, modern\n

since the industry standard DOT1Q is used almost\nexclusively.

So, we can go straight to the next command.

Now, let’s allow VLANs 10 and 30.

SWITCHPORT TRUNK ALLOWED VLAN 10,30.

Why don’t I need to allow VLAN20 on this\ntrunk?

I already explained this in the lecture video,\n

If PC5, in VLAN20, wants to reach any hosts\n

first, which will send it back to SW2 in VLAN10\n

Watch the lecture video again if you want\n

Okay, finally let’s set the native VLAN\nto an

SWITCHPORT TRUNK NATIVE VLAN 1001.

You can use anything here, just use an unused VLAN.

Now, do all of the necessary VLANs exist on\nthis switch?

We have VLANs 10 and 30, looks good.

We don’t need to create any more VLANs.

The configurations will be the same as on\nSW1.

SWITCHPORT TRUNK ALLOWED VLAN 10,30.

Again, VLAN20 doesn’t need to be allowed,\n

so SW2 doesn’t need to send VLAN20 traffic\nalong this trunk.

Okay, next set the native VLAN.

SWITCHPORT TRUNK NATIVE VLAN 1001.

Okay, that’s all for the configuration of\nthe trunk.

Now, do all necessary VLANs exist on the switch?

So, VLANs 10 and 30 are allowed on the trunk,\n

Vlans allowed and active in management domain\n

That’s a problem, it means SW2 won’t actually\n

That’s because VLAN30 doesn’t exist yet\non the switch.

VLANs 10 and 20 were automatically created\n

Okay, now you can see that it appears here.

Step 3 is to configure the connection between\n

Let’s quickly do the configuration here\n

the G0/1 trunk, except we must allow all three\nVLANs.

SWITCHPORT TRUNK ALLOWED VLAN 10,20,30.

SWITCHPORT TRUNK NATIVE VLAN 1001.

Enter privileged exec mode with ENABLE, then\n

First, let’s enable the physical interface.

As I have said many times before, Cisco router\n

Now let’s configure the VLAN10 subinterface.

This subinterface number DOESNT have to match\n

Okay, let’s set the VLAN number itself.

Finally, the IP address, which should be the\n

IP ADDRESS 10.0.0.62 255.255.255.192.

I get the question sometimes, why does the\n

Well, it doesn’t have to be, but you should\n

address or the last usable address as the\n

consistency across the network.

Don’t just use a random address for the\n

Okay, now let’s configure VLAN20’s subinterface.

Once again, set the last usable address as\nthe router’s address.

IP ADDRESS 10.0.0.126 255.255.255.192.

Okay, finally\nis VLAN30's subinterface.

IP ADDRESS 10.0.0.190 255.255.255.192, which\n

So, that’s all of the configurations for\nthis lab.

Next up is to test connectivity.

If everything is configured correctly, each\n

I’ll do some pings from PC7 to test.

Let’s ping another PC in VLAN10, PC1.

Let’s watch the ping in simulation mode.

As you can see, because PC1 is in the same\n

directly to PC1, no need for inter-VLAN routing.

Now let’s go back to realtime mode and try\n

Let’s take a look in simulation mode.

PING 10.0.0.65. Notice that the ping has\n

to SW2 and then to PC5, and the reply follows\nthe same path.

Okay, back to realtime mode, and finally we\n

Okay, the ping works, and once again let’s take a look at it in

Once again, the ping must go to R1 first to\n

reaching PC3, and then it follows the same\npath back.

Okay, that’s all for this lab.

Okay, let's move on to the Boson NetSim preview.

I've selected one lab here, Inter-VLAN Routing\n1.

Click on the lab, and you get a little preview.

And then click on 'load lab'.

This is very much like the lab we just did.

One router, two switches, and some PCs connected\nto each switch.

There is a command summary which shows you\n

And these are all commands you already know.

ENCAPSULATION DOT1Q, to set the VLAN on a\nrouter subinterface.

And SWITCHPORT commands, ACCESS VLAN, SWITCHPORT MODE.

And then next, the IP addresses on each device.

There are three main tasks for this lab.

Task 1, configure the switch and PC hosts.

Task 2, configure subinterfaces.

And task 3, complete and verify connectivity.

And each of these tasks has multiple sub-tasks,\nmultiple steps.

So, for this preview let's just do task 1.

This involves configuring basic network connectivity\n

So, in this lab PC1 and PC2 are connected\n

different departments within the company.

So, your task is to assign the two PC hosts\n

Okay, so step 1, verify the current IP configurations\n

Verify that they match the IP configurations\n

With PC1 and PC2's IP information.

So, to check the configuration on each PC,\n

You see, by default we are in Router1's CLI.

To access the CLI of separate devices, here\n

And also we will be using Switch1, so click\non console here.

To check the IP configuration on a PC, use\nthis command.

The subnet mask is correct, this is a /25\nprefix length.

And the default gateway is .1, which is correct.

And that happens to be the IP address of R1's\n

IPCONFIG /ALL. 192.168.100.130 is correct.

The default gateway is .129, which is correct,\n

Step 2, configure Switch1 with the appropriate\nhostname.

Let's go to the CLI of Switch1.

You can see it has the default hostname of\n

There we go, the hostname has changed to Switch1.

Okay, each PC is a member of a different department\n

PC1 belongs to VLAN10 and PC2 belongs to VLAN12.

Do VLANs 10 and 20 exist on SW1?

So, you can check that with a command you\n

You can see all ports are in, sorry about\n

And VLANs 10 and 12 do not exist.

So, we can go on to step 4, which says if\n

And then, without exiting from here, we can\n

There we go, DO SHOW VLAN BRIEF.

And you can see both VLANs were created, VLAN10\nand VLAN12.

There is no documentation present about your\n

and PC2 are connected to on Switch 1 before\n

How would you go about discovering which port\n

So, this might be a little bit of a challenge.

And then I'll go back to the PCs, PC1.

So, what you have to look for here is the\n'Physical Address'.

Physical address, what is that?

Well, it's the MAC address of this PC.

So, take note of these last four digits, 3538.

And now on Switch1, let's check the MAC address\ntable.

Now, notice here it's MAC hyphen ADDRESS hyphen\nTABLE.

On some newer devices you'll probably find\n

Now, let's see if this switch supports the\ncommand.

So, on this switch we will use the SHOW MAC\n

I think I mentioned that in one of my previous\n

So, we were looking for 3538, and you can\n

So, PC1 is connected to FastEthernet0/3.

Take note of the last four digits again, 6059.

6059, that is FastEthernet0/4.

And, just to check let's look at the diagram\nup here.

Okay, so PC1 FastEthernet0/3, PC2 FastEthernet0/4,\n

Okay, so add the PCs to the correct VLANs.

So, CONF T. PC1 is connected to FastEthernet0/3,\n

Okay, step 7, on Switch1 verify your configuration.

Okay, in VLAN10 we have FastEthernet0/3, which\n

FastEthernet0/4, which is connected to PC2.

So, our configurations are correct.

Okay, next, issue a ping from PC1 to PC2.

So, we're expecting this to fail but let's\ndo the ping anyway.

So, these pings are gonna fail.

I'll just wait for a few to go through.

Okay, so why are these pings failing?

So, these two PCs are in separate VLANs, so\n

But we haven't configured any inter-VLAN routing\nyet.

So, for example on Switch1, let's see if we\n

You can see FastEthernet 2 is a trunk, connected\nto Switch2.

But FastEthernet0/1 is not a trunk.

How about on R1, do we have any subinterfaces\nconfigured?

No, no subinterfaces configured.

So, router-on-a-stick, our inter-VLAN routing,\n

Okay, so there are two more tasks, configuring\n

I'll let you guys do those on your own.

And if you ever have any trouble, or want\n

So, for task 1 you can see the IPCONFIG /ALL\n

this is SHOW VLAN, I used SHOW VLAN BRIEF,\n

Configuring the VLANs, and everything we just\n

Okay, so once you're done the lab, click here,\n'grade lab'.

Now, we're not finished, so it's gonna tell\n

do it correctly, but that's okay.

There you go, 'you missed one or more commands\nin the lab.'

So, you can see here on Switch2, PC1, 2, 3,\n

That's because we didn't have to do any configurations\non these.

But we're missing configurations on Router\n1 and Switch1.

So, these commands in red are commands that\nwe missed.

So we were gonna set the host name on Router1,\n

Oh yeah, configuring FastEthernet0/1 as a\ntrunk.

Okay, so that's all for today's NetSim preview.

If you want to get a copy of NetSim and try\n

Please subscribe to the channel, like the\n

with anyone else studying for the CCNA.

If you\nwant to leave a tip, check the links in the

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