<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.14. Isolation in Advanced Zone Using Private VLAN</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.2.0-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
              addID('Apache_CloudStack');
              
	      addID('Apache_CloudStack.4.2.0');
              
              addID('Apache_CloudStack.4.2.0.books');
	      addID('Apache_CloudStack.4.2.0.Admin_Guide');
              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="networks.html" title="Chapter 15. Managing Networks and Traffic" /><link rel="prev" href="add-ip-range.html" title="15.13. Multiple Subnets in Shared Network" /><link rel="next" href="security-groups.html" title="15.15. Security Groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.apache.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://cloudstack.apache.org/docs"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="add-ip-range.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="security-groups.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="pvlan" lang="en-US"><div class="titlepage"><div><div><h2 class="title">15.14. Isolation in Advanced Zone Using Private VLAN</h2></div></div></div><div class="para">
		Isolation of guest traffic in shared networks can be achieved by using Private VLANs (PVLAN). PVLANs provide Layer 2 isolation between ports within the same VLAN. In a PVLAN-enabled shared network, a user VM cannot reach other user VM though they can reach the DHCP server and gateway, this would in turn allow users to control traffic within a network and help them deploy multiple applications without communication between application as well as prevent communication with other users’ VMs.
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				Isolate VMs in a shared networks by using Private VLANs.
			</div></li><li class="listitem"><div class="para">
				Supported on KVM, XenServer, and VMware hypervisors
			</div></li><li class="listitem"><div class="para">
				PVLAN-enabled shared network can be a part of multiple networks of a guest VM.
			</div></li></ul></div><div class="section" id="about-pvlan"><div class="titlepage"><div><div><h3 class="title">15.14.1. About Private VLAN</h3></div></div></div><div class="para">
			In an Ethernet switch, a VLAN is a broadcast domain where hosts can establish direct communication with each another at Layer 2. Private VLAN is designed as an extension of VLAN standard to add further segmentation of the logical broadcast domain. A regular VLAN is a single broadcast domain, whereas a private VLAN partitions a larger VLAN broadcast domain into smaller sub-domains. A sub-domain is represented by a pair of VLANs: a Primary VLAN and a Secondary VLAN. The original VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another.
		</div><div class="para">
			Three types of ports exist in a private VLAN domain, which essentially determine the behaviour of the participating hosts. Each ports will have its own unique set of rules, which regulate a connected host's ability to communicate with other connected host within the same private VLAN domain. Configure each host that is part of a PVLAN pair can be by using one of these three port designation:
		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					<span class="bold bold"><strong>Promiscuous</strong></span>: A promiscuous port can communicate with all the interfaces, including the community and isolated host ports that belong to the secondary VLANs. In Promiscuous mode, hosts are connected to promiscuous ports and are able to communicate directly with resources on both primary and secondary VLAN. Routers, DHCP servers, and other trusted devices are typically attached to promiscuous ports.
				</div></li><li class="listitem"><div class="para">
					<span class="bold bold"><strong>Isolated VLANs</strong></span>: The ports within an isolated VLAN cannot communicate with each other at the layer-2 level. The hosts that are connected to Isolated ports can directly communicate only with the Promiscuous resources. If your customer device needs to have access only to a gateway router, attach it to an isolated port.
				</div></li><li class="listitem"><div class="para">
					<span class="bold bold"><strong>Community VLANs</strong></span>: The ports within a community VLAN can communicate with each other and with the promiscuous ports, but they cannot communicate with the ports in other communities at the layer-2 level. In a Community mode, direct communication is permitted only with the hosts in the same community and those that are connected to the Primary PVLAN in promiscuous mode. If your customer has two devices that need to be isolated from other customers' devices, but to be able to communicate among themselves, deploy them in community ports.
				</div></li></ul></div><div class="para">
			For further reading:
		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					<a href="http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379">Understanding Private VLANs</a>
				</div></li><li class="listitem"><div class="para">
					<a href="http://tools.ietf.org/html/rfc5517">Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment</a>
				</div></li><li class="listitem"><div class="para">
					<a href="http://kb.vmware.com">Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691)</a>
				</div></li></ul></div></div><div class="section" id="prereq-pvlan"><div class="titlepage"><div><div><h3 class="title">15.14.2. Prerequisites</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					Use a PVLAN supported switch.
				</div><div class="para">
					See <a href="http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml">Private VLAN Catalyst Switch Support Matrix</a>for more information.
				</div></li><li class="listitem"><div class="para">
					All the layer 2 switches, which are PVLAN-aware, are connected to each other, and one of them is connected to a router. All the ports connected to the host would be configured in trunk mode. Open Management VLAN, Primary VLAN (public) and Secondary Isolated VLAN ports. Configure the switch port connected to the router in PVLAN promiscuous trunk mode, which would translate an isolated VLAN to primary VLAN for the PVLAN-unaware router.
				</div><div class="para">
					Note that only Cisco Catalyst 4500 has the PVLAN promiscuous trunk mode to connect both normal VLAN and PVLAN to a PVLAN-unaware switch. For the other Catalyst PVLAN support switch, connect the switch to upper switch by using cables, one each for a PVLAN pair.
				</div></li><li class="listitem"><div class="para">
					Configure private VLAN on your physical switches out-of-band.
				</div></li><li class="listitem"><div class="para">
					Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS).
				</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
						OVS on XenServer and KVM does not support PVLAN natively. Therefore, CloudStack managed to simulate PVLAN on OVS for XenServer and KVM by modifying the flow table.
					</div></div></div></li></ul></div></div><div class="section" id="ability-pvlan"><div class="titlepage"><div><div><h3 class="title">15.14.3. Creating a PVLAN-Enabled Guest Network</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
					Log in to the CloudStack UI as administrator.
				</div></li><li class="listitem"><div class="para">
					In the left navigation, choose Infrastructure.
				</div></li><li class="listitem"><div class="para">
					On Zones, click View More.
				</div></li><li class="listitem"><div class="para">
					Click the zone to which you want to add a guest network.
				</div></li><li class="listitem"><div class="para">
					Click the Physical Network tab.
				</div></li><li class="listitem"><div class="para">
					Click the physical network you want to work with.
				</div></li><li class="listitem"><div class="para">
					On the Guest node of the diagram, click Configure.
				</div></li><li class="listitem"><div class="para">
					Click the Network tab.
				</div></li><li class="listitem"><div class="para">
					Click Add guest network.
				</div><div class="para">
					The Add guest network window is displayed.
				</div></li><li class="listitem"><div class="para">
					Specify the following:
				</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Name</strong></span>: The name of the network. This will be visible to the user.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Description</strong></span>: The short description of the network that can be displayed to users.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>VLAN ID</strong></span>: The unique ID of the VLAN.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Secondary Isolated VLAN ID</strong></span>: The unique ID of the Secondary Isolated VLAN.
						</div><div class="para">
							For the description on Secondary Isolated VLAN, see <a class="xref" href="pvlan.html#about-pvlan">Section 15.14.1, “About Private VLAN”</a>.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Scope</strong></span>: The available scopes are Domain, Account, Project, and All.
						</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
									<span class="bold bold"><strong>Domain</strong></span>: Selecting Domain limits the scope of this guest network to the domain you specify. The network will not be available for other domains. If you select Subdomain Access, the guest network is available to all the sub domains within the selected domain.
								</div></li><li class="listitem"><div class="para">
									<span class="bold bold"><strong>Account</strong></span>: The account for which the guest network is being created for. You must specify the domain the account belongs to.
								</div></li><li class="listitem"><div class="para">
									<span class="bold bold"><strong>Project</strong></span>: The project for which the guest network is being created for. You must specify the domain the project belongs to.
								</div></li><li class="listitem"><div class="para">
									<span class="bold bold"><strong>All</strong></span>: The guest network is available for all the domains, account, projects within the selected zone.
								</div></li></ul></div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Network Offering</strong></span>: If the administrator has configured multiple network offerings, select the one you want to use for this network.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Gateway</strong></span>: The gateway that the guests should use.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Netmask</strong></span>: The netmask in use on the subnet the guests will use.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>IP Range</strong></span>: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs.
						</div></li><li class="listitem"><div class="para">
							<span class="bold bold"><strong>Network Domain</strong></span>: A custom DNS suffix at the level of a network. If you want to assign a special domain name to the guest VM network, specify a DNS suffix.
						</div></li></ul></div></li><li class="listitem"><div class="para">
					Click OK to confirm.
				</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="add-ip-range.html"><strong>Prev</strong>15.13. Multiple Subnets in Shared Network</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="security-groups.html"><strong>Next</strong>15.15. Security Groups</a></li></ul></body></html>
