The carpenter's role is to measure twice and then
cut once, and that's what I like to do
as we implement private VLANs.
So let's take a moment.
We'll consider our design of what VLAN numbers
we're going to use for the primary VLAN
and also for the secondary VLANs,
also what type of secondary VLANs
are we going to use, community or isolated.
We'll have that all planned out and then
we'll follow that up in the subsequent video
with the actual implementation and then verification
that the private VLAN is working as expected.
So let's go to the drawing board and let's put a plan together. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's go to the drawing board and let's put a plan together.
All right, and for our plan, here's
what I propose because I already have it up here.
So let's use VLAN 100 as the primary VLAN.
For the IP address base, let's use 10.100.0,
and we can also configure DHCP services just to hand out IP
addresses to clients if we wanted to.
As far as the secondary VLANs, let's create
VLAN 200 as a secondary VLAN.
We'll specify it as a type of community.
We'll create VLAN 300 as a secondary VLAN.
We'll specify it as a type of community as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll specify it as a type of community as well.
And then for VLAN 400, let's specify that as isolated.
And then we can also test to verify the traffic patterns
that are allowed or not allowed based on these secondary VLANs
that ports are associated with.
Now as far as the ports go, let's also plan on some ports.
Let's put port 0/1-2 in VLAN 200.
Let's use ports 1/1-2 in VLAN 300,
and then let's use ports 2/1-2 in VLAN 400.
And that way, we can verify by connecting WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that way, we can verify by connecting
devices, PCs, to those ports, and verifying what works
and what doesn't work.
And here's what we expect.
If we had two devices, 0/1 and 2,
they should be able to talk to each other
but they should not be able to communicate with ports 1/1
or 1/2.
And regarding the two devices here,
we would expect that those devices can communicate
with each other but not with devices off of port 0/1 and 2.
And then for the isolated VLAN, these poor ports here,
we'll use 2/1-2.
Any devices we connect here should not be able to talk WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Any devices we connect here should not be able to talk
to each other, nor should they be able to talk to any devices
in VLAN 300 or 200 as part of our private VLAN,
even though they are all going to have an IP address
on the 10.100.0 network.
The key is here the switch, based
on the configuration with the private VLANs,
is controlling what traffic is allowed
back and forth between the various ports based
on the configuration.
So with that plan in mind, let me walk you
through in the next video the exact configuration
to implement this step by step, and then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to implement this step by step, and then
once we have it configured, we'll
put some devices on those ports, and then
we'll verify the results in a subsequent video.
So I look forward to seeing you in the next video where
we start a configuration in just a moment.
Meanwhile, I hope this has been informative for you
and I'd like to thank you for viewing.