Home > Private VLAN (PVLAN)

Private VLAN (PVLAN)

February 7th, 2012 in SWITCH 642-813 Go to comments

Here you will find answers to Private VLAN Questions

Quick review:

The main purpose of Private VLAN (PVLAN) is to provide the ability to isolate hosts at Layer 2 instead of Layer 3. As you know, a VLAN is a broadcast domain, by using PVLAN we are splitting that domain into some smaller broadcast domains. For example, without PVLAN, a service provider wants to increase security by isolating customers into separate domains so that they can’t access each other, they have to assign them into different VLANs and use different subnets. This can result in a waste of IP addresses and difficulty in VLAN management. Private VLANs (PVLANs) can solve this problem by allowing the isolation of devices at Layer 2 in the same subnet. PVLAN can be considered “VLANs inside VLAN”.

There are three types of ports in PVLAN:

* Isolated: only communicate with promiscuous ports. Notice that it cannot even communicate with another isolated port. Also, there can be only 1 isolated VLAN per PVLAN.
* Promiscuous: can communicate with all other ports. The default gateway is usually connected to this port so that all devices in PVLAN can go outside.
* Community: can communicate with other members of that community and promiscuous ports but cannot communicate with other communities. There can be multiple community VLANs per PVLAN.

PVLAN_Promiscuous_Community_Isolated.jpg

For example, in the topology above:

+ Host A cannot communicate with Host B, C, D, E and F. It can only communicate with Promiscuous port to the router. Notice that even two Isolated ports in the same VLAN cannot communicate with each other.

+ Host C can communicate with Host D because they are in the same community but Host C cannot communicate with E and F because they are in a different community.

+ All hosts can go outside through promiscuous port.

Also I want to mention about the concept of “primary VLAN” and “secondary VLAN”. PVLAN can have only one primary VLAN; all VLANs in a PVLAN domain share the same primary VLAN. Secondary VLANs are isolated or community VLANs.

PVLAN_Primary_VLAN_Secondary_VLAN.jpg

Configuration of PVLAN:

1. Set VTP mode to transparent
2. Create secondary (isolated and community) VLANs and primary VLAN
3. Associate secondary VLANs to the primary VLAN
4. Configure interfaces as promiscuous interfaces
5. Configure interfaces to be isolated or community interfaces.

Sample configuration used the topology above:

//First set VTP to transparent mode
Switch(config)#vtp mode transparent

//Create secondary VLANs
Switch(config)#vlan 101
Switch(config-vlan)#private-vlan isolated
Switch(config-vlan)#vlan 102
Switch(config-vlan)#private-vlan community
Switch(config-vlan)#vlan 103
Switch(config-vlan)#private-vlan community

//Create primary VLAN
Switch(config-vlan)#vlan 100
Switch(config-vlan)#private-vlan primary

//Associate secondary (isolated, community) VLANs to the primary VLAN
Switch(config-vlan)#private-vlan association 101,102,103

//Assign Promiscuous port to the port connected to the router, with the primary VLAN mapped to the secondary VLAN.
Switch(config)# interface f0/1
Switch(config-if)# switchport mode private-vlan promiscuous
Switch(config-if)# switchport private-vlan mapping 100 101,102,103

//Ports connected to hosts A, B, C, D, E, F are configured in host mode and assign to appropriate VLANs (A and B to isolated VLAN 101; C and D to community VLAN 102; E and F to community VLAN 103):
Switch(config)# interface range f0/2 – 0/3 //connect to host A and B
Switch(config-if)# switchport mode private-vlan host
Switch(config-if)# switchport private-vlan host-association 100 101

Switch(config-if)# interface range f0/3 -0/4 //connect to host C and D
Switch(config-if)# switchport mode private-vlan host
Switch(config-if)# switchport private-vlan host-association 100 102

Switch(config-if)# interface f0/5 – 0/6 //connect to host E and F
Switch(config-if)# switchport mode private-vlan host
Switch(config-if)# switchport private-vlan host-association 100 103

To check the configuration, use this command:

Switch# show vlan private-vlan

Question 1

Refer to the exhibit. The web servers WS_1 and WS_2 need to be accessed by external and internal users. For security reasons, the servers should not communicate with each other, although they are located on the same subnet. The servers do need, however, to communicate with a database server located in the inside network. What configuration will isolate the servers from each other?

PVLAN_promiscuous_ports.jpg

A. The switch ports 3/1 and 3/2 will be defined as secondary VLAN community ports. The ports connecting to the two firewalls will be defined as primary VLAN promiscuous ports.
B. The switch ports 3/1 and 3/2 and the ports connecting to the two firewalls will be defined as primary VLAN promiscuous ports.
C. The switch ports 3/1 and 3/2 and the ports connecting to the two firewalls will be defined as primary VLAN community ports.
D. The switch ports 3/1 and 3/2 will be defined as secondary VLAN isolated ports. The ports connecting to the two firewalls will be defined as primary VLAN promiscuous ports.


Answer: D

Explanation

WS_1 and WS_2 cannot communicate with each other so we can put them into isolated ports. Isolated ports can only communicate with promiscuous ports so Fa3/34 and Fa3/35 should be promiscuous ports so that they can send and receive data with the Data Server.

Note: Answer A is not clear because it does not state the switch ports 3/1 and 3/2 are put into the same or different VLAN community ports. If they are put into different VLAN communities then answer A is correct.

Question 2

Refer to the exhibit. What can be concluded about VLANs 200 and 202?

show_vlan_private-vlan_type.jpg

A. VLAN 202 carries traffic from promiscuous ports to isolated, community, and other promiscuous ports in the same VLAN. VLAN 200 carries traffic between community ports and to promiscuous ports.
B. VLAN 202 carries traffic from promiscuous ports to isolated, community, and other promiscuous ports in the same VLAN. VLAN 200 carries traffic from isolated ports to a promiscuous port.
C. VLAN 200 carries traffic from promiscuous ports to isolated, community, and other promiscuous ports in the same VLAN. VLAN 202 carries traffic between community ports and to promiscuous ports.
D. VLAN 200 carries traffic from promiscuous ports to isolated, community, and other promiscuous ports in the same VLAN. VLAN 202 carries traffic from isolated ports to a promiscuous port.


Answer: B

Explanation

In fact the exhibit above is wrong, that output should be from the command “show vlan private-vlan”. The “show vlan private-vlan type” should give output like this:

Vlan
————–
Type
————-
202
200
Primary
isolated

With this output we can see VLAN 202 is configured as the primary VLAN while VLAN 200 is configured as secondary (isolated) VLAN -> B is correct.

Question 3

Private VLANs can be configured as which three of these port types? (Choose three)

A. isolated
B. protected
C. private
D. associated
E. promiscuous
F. community


Answer: A E F

Explanation

There are three types of ports can be configured in a Private VLAN: isolated, promiscuous, community.

* Isolated: only communicate with promiscuous ports. Notice that it cannot even communicate with another isolated port. Also, there can be only 1 isolated VLAN per PVLAN.
* Promiscuous: can communicate with all other ports. The default gateway is usually connected to this port so that all devices in PVLAN can go outside.
* Community: can communicate with other members of that community and promiscuous ports but cannot communicate with other communities. There can be multiple community VLANs per PVLAN.

Question 4

Refer to the exhibit. From the configuration shown, what can you determine about the private VLAN configuration?

Switch# configure terminal
Switch (config)# vlan 20
Switch (config-vlan)# private-vlan primary
Switch (config-vlan)# exit
Switch (config)# vlan 501
Switch (config-vlan)# private-vlan isolated
Switch (config-vlan )#exit
Switch (config)# vlan 502
Switch (config-vlan)#private-vlan community
Switch (config-vlan)# exit
Switch (config)# vlan 503
Switch (config-vlan )# private-vlan community
Switch (config-vlan)# exit
Switch (config)# vlan 20
Switch (config-vlan)#private-vlan association 501-503
Switch (config-vlan)# end

A. Only VLAN 503 will be the community PVLAN because multiple community PVLANs are not allowed.
B. Users of VLANs 501 and 503 will be able to communicate.
C. VLAN 502 is a secondary VLAN.
D. VLAN 502 will be a standalone VLAN because it is not associated with any other VLANs.


Answer: C

Explanation

There are two types of secondary VLAN: isolated and community. In this case VLAN 502 is a community VLAN -> C is correct.

In a PVLAN, multiple community VLANs are allowed. But notice a PVLAN can have only one primary VLAN and one isolated VLAN -> A is not correct.

Only community in the same VLAN can communicate with each other. Users in different communities are not able to communicate -> B is not correct.

The command “private-vlan association 501-503″ associates VLANs 501, 502 and 503 to the Primary VLAN 20 -> D is not correct.

Question 5

When configuring private VLANs, which configuration task must you do first?

A. Configure the private VLAN port parameters.
B. Configure and map the secondary VLAN to the primary VLAN.
C. Disable IGMP snooping.
D. Set the VTP mode to transparent.


Answer: D

Explanation

Before configuring private VLANs, we must set VTP mode to transparent because VTP version 1 and 2 do not support private VLAN (VTP version 3 does support PVLAN). Notice that a switch in VTP transparent mode still forwards other VTP updates to its neighbors.

Question 6

A switch has been configured with Private VLANs. With that type of PVLAN port should the default gateway be configured?

A. Trunk
B. Isolated
C. Primary
D. Community
E. Promiscuous


Answer: E

Explanation

A default gateway should be configured Promiscuous type so that all devices in PVLAN can go outside.

Comments
  1. Ameya
    June 15th, 2012

    In the Q.2 u have given the ans as ‘B’ and in the explanation the ans as ‘D’

  2. hey
    June 16th, 2012

    In Q2, I think the explanation is based on B, so D must be a typo error

  3. certprepare
    June 25th, 2012

    Yes, in Question 2 ‘D’ is a typo. Thanks for your detection, I updated it.

  4. imran
    June 29th, 2012

    so which is correct option ?
    please

  5. Jama Yassin
    June 30th, 2012

    Switch(config)# interface range f0/2 – 0/3 //connect to host A and B
    Switch(config-if)# switchport mode private-vlan host

    … in this configuration is it means that only one host can be connected to the Isolated VLAN? or I can connected more than one host?.. I mean if that port is connected to the Hub.. will all the host in that Hub will communicate the Router?.

    Sorry my English it’s not my native language..

  6. HungN
    July 20th, 2012

    Hi Guys,

    Seeing the answer right in front your eyes before making selection is annoying. So i grabs all of the questions on this site and put them into VCE file to make my life easier. Be sure to check back CertPrepare site regularly for updates.

    Here is the file: http://www.4shared.com/file/C5hmKPbb/CCNP_642-813_CertPrepare-by_Hu.html

    Best of luck !!!

  7. Arch
    August 4th, 2012

    Nicely done!

  8. Sheikh
    November 24th, 2012

    we hv config deny aseccs list on VSS L3 switch, where ABC belongs to vlan 34 ip aseccs-list extended ABC deny ip 172.17.34.0 0.0.0.255 172.30.31.0 0.0.0.255 deny ip 172.17.34.0 0.0.0.255 172.30.32.0 0.0.0.255 deny ip 172.17.34.0 0.0.0.255 172.30.35.0 0.0.0.255 permit ip any any than whn we config the vacl on this switch as below ( are all cmd right? ) Epi-VSS1(config)#Vlan acess-map VACL_VL34 Epi-VSS1(config-access-map)#Match ip address ABC Epi-VSS1(config-access-map)#action drop Epi-VSS1(config-access-map)#exit Epi-VSS1(config)#Vlan acess-map VACL_VL34 Epi-VSS1(config-access-map)#action forward cature Epi-VSS1(config-access-map)#exit Epi-VSS1(config)#vlan filter VACL_VL34 vlan-list 34 for port capture we need to config the switch port capture cmd on same switch or the next switch connected to it?? little bit confuse in this interface gi1/1 switchport capture allowed vlan 34 switchport capture

  9. Badis
    November 25th, 2012

    Missing this question:Which two eetnvs will cause the VTP revision number on a VTP server to change? (Choose two.)-adding VLANs-rebooting the switch-changing the VTP domain name-changing the switch to a VTP client-changing interface VLAN designationsperhaps the answers are the first and the last.

  10. Regalis
    February 15th, 2013

    Q1.

    Answer D suggests setting fa/34 & fa3/35 to promiscuous ports. My understanding is that only one promiscuous port per PVLAN is permitted. Is that correct?

    I agree it is the best answer as all other options would allow the servers to communicate with each other.

  11. Learner
    February 23rd, 2013

    Q-4,
    I didn’t get, how we determined the VLAN 502 to be a secondary VLAN.?

  12. sastre
    February 24th, 2013

    Hi, There are lots of MCQ questions that are in the certprepare but not included in the latest dump. Are those questions no more included in the exam???

  13. Dwarbit
    April 7th, 2013

    @ Learner
    Q4 – Primary Vlan is 20, Isoloated and Community Vlans are Secondary Vlans:

    A. Only VLAN 503 will be the community PVLAN because multiple community PVLANs are not allowed. (False – you can have as many as you need limited only by the amount of ports on the switch)
    B. Users of VLANs 501 and 503 will be able to communicate. (False – Isolated Vlan 501 cannot communicate with Community Vlan 503)
    C. VLAN 502 is a secondary VLAN. (True – as noted above)
    D. VLAN 502 will be a standalone VLAN because it is not associated with any other VLANs. (False – it is a community vlan that is associated with Primary Vlan 20)

  14. TechMom
    April 12th, 2013

    Nothing from this section was in test today.

  15. james
    May 12th, 2013

    Hi i have successfully completed 642-813 exam i prepared exam using pass4sure 642-813 – v12.2 / 155 GB contact foxboxall@gmail.cm to get this dump

  1. No trackbacks yet.
Add a Comment