All right.
I'm excited.
It's time to implement our design.
Based on the previous video, we're
getting private VLANs, so let me walk you through the config.
So here's a little reminder of our plan
from our previous video, and we're
going to do our configuration and my topology
here on switch number 1.
And to make this a little bit less
of a typing exercise and more instructional and to the point,
let me walk you through what we're about to implement.
So config t, we're all familiar with that.
And on these switches, I'm just going to blast everything,
just wiped out all my existing VLANs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just wiped out all my existing VLANs,
so we're starting from scratch, and then
I've got these 12 interfaces that I'm going to go ahead
and just set to there defaults.
So that way, we're starting from scratch.
I'm also going to do spanning tree mode rapid.
That will help me converge just a little bit faster.
Now, one of the elements we need to do,
if you have VTP support for version 3,
I believe you can pull that off, but if you're
using version 1 or 2, that doesn't work.
It's not compatible with private VLANs.
So I'm going to specify vtp mode transparent,
and then we're going to create our VLANs.
In creation of these VLANs, we have the primary VLAN, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
In creation of these VLANs, we have the primary VLAN,
VLAN 100, and also these secondary VLANs here,
but I choose to create all the secondary ones first and then
follow it up with the primary VLAN.
And the reason for that is because in the primary VLAN
configuration, we're going to tell it,
aye, you're also going to be associated
with the primary VLAN with these secondary VLANs.
So if they don't exist yet, that's kind of a problem.
So let's create VLAN 200.
We'll get a name.
I'll call it community A. Just when we see it in output,
we can recognize it, and then we're
specifying the type of private VLAN, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
specifying the type of private VLAN,
secondary VLAN it's going to be is a community.
So any ports that are associated with VLAN 200, this community
VLAN, the traffic would be allowed
to flow between ports in that same community.
And then we would create VLAN 300.
We can give it a name and then specifying it as a private VLAN
type of community and any ports that we associate
with that VLAN, VLAN 300, they can talk to each other,
frames will be forwarded by the switch, but what they can't do
is have their frames forwarded directly between themselves WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is have their frames forwarded directly between themselves
in this community and ports in a different community.
And then we'll create VLAN 400.
We'll give it a name just for identification purposes.
And then for the private VLAN type,
we're going to specify that it is isolated.
So any ports that we associate with VLAN 400, the isolated,
they will not be able to communicate with each other
because they are ports associated with the isolated
VLAN, and they will not be able to communicate with other ports
in a different secondary VLAN.
So all three of these are secondary VLANs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So all three of these are secondary VLANs,
and the first two are the type community
and the third one here is isolated.
Now, even though they can't talk directly to each other,
if we associate some port with the primary VLAN
and specify it as promiscuous, they
will be able to communicate with that promiscuous port, which
is really important if we want that client to be
able to use a default gateway.
And then for the primary VLAN, which we're using VLAN 100,
I'm just giving it a name here, and then
we're specifying private VLAN type is primary.
And then we tell the primary VLAN who it's associated with,
and this is a list of the secondary VLANs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and this is a list of the secondary VLANs
that we just created just a moment ago
or when we configured this, which
we will have created just a few moments prior to this one.
So let's configure it up to that point.
I'm going to right click, copy that in my buffer,
and deploy that configuration.
So there is our secondary VLANs, there's our primary VLAN,
and we've associated 200, 300, and 400 with that primary VLAN.
So we've accomplished part of our goal.
We've created our primary VLAN.
We created our secondary VLAN, the correct types,
and we've also associated these three secondary VLANs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we've also associated these three secondary VLANs
with the primary VLAN.
Next, let's take a look at associating some ports
with each of these secondary VLANs.
So we'll do a couple of ports for VLAN 200,
a couple of ports for VLAN 300, and a couple
of ports for VLAN 400.
And here's the syntax to pull that off.
We're going to interface configuration mode
for these two ports--
0/1 through 2, and we use the command switchport
private-vlan host-association, and then we
put the primary VLAN first, followed by the secondary VLAN
we want these ports to be associated with. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we want these ports to be associated with.
And then we followed up with this command switchport mode
private-vlan host.
And boom, those two ports are now
configured to be associated with that secondary VLAN of 200.
Then we use the same treatment for ports 1/1
through 2 except we're going to modify that and specify
that they're associated with VLAN 300, which
is our second secondary community VLAN.
And then for ports 2/1 through 2,
we're putting those in the VLAN 400, which
is the isolated VLAN.
So let's deploy that part of our config. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's deploy that part of our config.
We'll copy that and paste it in.
And then before we go, let's do this.
Let's create a switch to virtual interface.
So the primary VLAN, we already defined that, is VLAN 100.
And interface VLAN 100 is a switched virtual interface,
a logical interface, a layer 3 interface that's in that VLAN.
So we can do a no shut to bring it up.
We'll give it an IP address.
It's appropriate for this subnet being used by our private VLAN
infrastructure.
And then we're going to add this command, private-vlan mapping,
and then we're going to just say Add.
Now, if you don't use the keyword Add, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, if you don't use the keyword Add,
it'll just replace what's currently there,
but use the keyword add.
It'll add these secondary VLANs as being supported by this VLAN
interface.
So this is effectively saying, hey, Dear Mr. Interface VLAN
100, please feel free to support the traffic for the VLAN 200,
300, 400, which are all secondary VLANs.
So even though interface VLAN 100 is not
a physical interface, it is a logical interface,
we want to make sure it's a promiscuous, logical interface,
and this command here allows that to happen. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and this command here allows that to happen.
So we'll have those commands as well.
And then we have some private VLAN mapping messages
indicating it took those commands.
So what have we done?
We've created the primary VLAN.
We create a secondary VLAN and they're types.
We associated interfaces with those.
We also set up these switched virtual interface
to support the secondary VLANs.
Now, what's next?
Well, we might want to do some verification commands to make
sure that what we think we configured
is actually configured, and we'll
walk through that verification and those steps
in the next video.
So I'll see you there in just a moment.
Meanwhile, I hope this has been informative for you, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.