To implement VLANs, we'd want to do three basic things.
Number one-- plan it out.
We identify which hosts or which devices we want in which VLANs.
Secondly, implement the changes, and then third,
verify that it works.
So as part of our planning, let's take
a close look at our existing topology right here.
We have six hosts--
PC-1 all the way through PC-6.
These numbers up here that start with 10
are currently their IP addressing information
for each one of them.
So PC-1's IP address ends with dot 11.
PC-2 is dot 22, et cetera, all the way through PC-6
ending in dot 66.
And regarding these hosts, their connectivity to the network--
their physical connectivity is through these switches--
switch number 1 and switch number 2.
And currently, and by default in the Cisco Network,
all the switchports are by default
configured as being members of VLAN number 1.
That's a little bit hard to read.
Let me change the color there.
So as part of our planning, let's decide that we want PC-1
and PC-2 to be in their own VLAN--
their own layer two broadcast domain.
So let's go ahead and put them into a new VLAN
and we'll use VLAN 777.
So we'll create that new VLAN and we'll
assign Gig 0/1 and 0/2 to that VLAN, which will then
cause PC-1 and PC-2 to be in that VLAN called 777,
and we'll leave everybody else in the default
VLAN of VLAN number 1.
So after we make that change at the switchports,
PC-1 and PC-2 will still be able to talk to each other,
but they'll be isolated from the rest of the devices
because the rest of the devices are in VLAN 1,
while they'll be in VLAN 777.
And for the demonstration, we're going
to go ahead and walk through implementing
this on a Cisco switch.
Currently, all six PCs are in VLAN 1,
and let's verify basic connectivity before we
start making some changes.
So here in PC-1, let's go ahead and ping out
to PC-2, PC-3, PC-4, PC-5, and PC-6 just
to verify that we have connectivity
and that the network is currently functioning
before we make any changes.
[MUSIC PLAYING]
Great, so we verified some basic connectivity by doing a ping
test from PC-1 to the other five PCs,
and currently that's working, partly because every other PC
is in the same exact VLAN--
VLAN number 1 by default. Next, let's
go to the switch-- switch number 1 and take a look at it.
Here on switch number 1, let's take a look at the defaults
that we have in place before we start making some changes,
and on a Cisco switch, we can use the command Show VLAN
Brief.
Take a look at the VLAN information.
So over here on the right, we have a list of ports,
and it's currently showing us here on switch 1
that Gig 0/1, 0/2, 0/3, along with a few others,
are all associated with this VLAN, VLAN 1, which
is the default VLAN.
And what we're going to do is we're
going to take Gig 0/1 and 0/2, which
is where PC-1 and PC-2 are connected,
and we are going to first create VLAN 777,
and then put those two individual ports
in that separate VLAN.
So we'll go into configuration mode on this switch,
and the first thing we want to do
is go ahead and create our new VLAN.
So we'll create VLAN 777, and we'll also
give it the name of Human Resources,
that way when we see it, we can know what it is.
Next, we'll exit out of VLAN configuration mode.
We'll do a quick Show for the VLAN,
just to make sure that it exists.
Sure enough, there it is--
VLAN 777 named Human Resources, and at the moment,
there are no ports assigned to it, and that's our next step.
We want to assign ports Gig 0/1 and 0/2 to that specific VLAN.
So we'll go into range configuration mode
so we can put in the commands for those two ports
at the same time, and we'll use the commands Switchport Mode
Access, saying that we want these two
ports to be access ports followed by switchport access
VLAN and the number 777, which is the VLAN we
want them to be a part of.
And having done that, we'll type an End
to go out of configuration mode, and let's do a quick Show
command to verify our work.
And we can do a Show VLAN Brief, and sure enough,
we have VLAN 777, and now we have the two ports of Gig 0/1
and 0/2 that are associated with that specific layer
two broadcast domain.
So our next step is to go ahead and test connectivity.
We should have connectivity.
In fact, let's go over to PC-1.
So here on PC-1, we should have connectivity between PC-1
and PC-2, so we'll test that with a ping, or to 10.0.0.22--
that is PC-2, and that continues to work.
That's great.
Next let's ping 10.0.0.33, which is PC-3.
Now, because PC-1 is in VLAN 777 and the PC we're trying to ping
is in a completely separate layer two broadcast
domain or separate VLAN, there is no connectivity
without some other network device
that's going to move our traffic over there for us.
So this ping command is not expected to work.
And sure enough, it is timing out.
It's not working.
However, if we go to PC-3, here on PC-3,
which is still in VLAN 1, if we try to ping other devices that
are still in VLAN 1, like PC-4, PC-5, or PC-6,
that should still work, because those four PCs are all
in the same broadcast domain--
the same VLAN.
So let's test it with a ping out to 10.0.0.
and let's pick on 44, which is PC-4,
and press Enter, and sure enough, that works great.
But we won't be able to ping from PC-3 over to PC-1 or PC-2,
once again because PC-3 is in a different layer
two VLAN than PC-1 and PC-2.
In this Nugget, we've planned, implemented,
and verified both the creation of a new VLAN
and assigning two switchports to that VLAN.
I hope that this has been informative for you,
and I'd like to thank you for viewing.