Private VLANs provide Layer 2 isolation between ports within the same private VLAN. Private-VLAN ports are access ports that are one of these types:
- Promiscuous— A promiscuous port belongs to the primary VLAN and can communicate with all interfaces, including the community and isolated host ports that belong to the secondary VLANs associated with the primary VLAN.
- Isolated—An isolated port is a host port that belongs to an isolated secondary VLAN. It has complete Layer 2 separation from other ports within the same private VLAN, except for the promiscuous ports. Private VLANs block all traffic to isolated ports except traffic from promiscuous ports. Traffic received from an isolated port is forwarded only to promiscuous ports.
- Community—A community port is a host port that belongs to a community secondary VLAN. Community ports communicate with other ports in the same community VLAN and with promiscuous ports. These interfaces are isolated at Layer 2 from all other interfaces in other communities and from isolated ports within their private VLAN.
Router is Connected on interface Fa0/1 of catalyst Switch and we have different servers ie Webservers 1,2 (Fa0/2,Fa0/3) and Mailservers 1,2 (Fa0/4,Fa0/5) which have different communication requirements.From the above diagram , the Private VLAN arrangement is described as below –
- VLAN 100 is the primary VLAN. Router should be connected to port Fa0/1 in promiscuous mode.
- VLAN 101 is the community ports. Interface Fa0/2 and Fa0/3 will be for Webserver 1 and Webserver 2 respectively and part of community Vlan since they can communicate to each other in addition to Router.
- VLAN 102 is the isolated ports. Interface Fa0/4 and Fa0/5 will be for Mailserver 1 and Mailserver 2 respectively and part of isolated VLAN since they can only communicate to Router and can’t talk to each other.
The configuration is performed as below –
Here the private VLANs are configured under respective primary and secondary category.
In this section , the Private VLAN association is performed with respective interface.
Once the configuration is performed, we validate the configuration with below commands –