From 011bae7c0a9a6fde90e18ce7777ec679310e5d7b Mon Sep 17 00:00:00 2001 From: Radhika PC Date: Wed, 3 Jul 2013 15:14:25 +0530 Subject: [PATCH] CLOUDSTACK-2808 --- docs/en-US/add-tier.xml | 9 +++++ docs/en-US/vlan-assign-isolated-nw.xml | 56 +++++++++++--------------- 2 files changed, 32 insertions(+), 33 deletions(-) diff --git a/docs/en-US/add-tier.xml b/docs/en-US/add-tier.xml index e5334d39ca6..17e02be7b7b 100644 --- a/docs/en-US/add-tier.xml +++ b/docs/en-US/add-tier.xml @@ -74,6 +74,15 @@ Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC. + + VLAN: The VLAN ID for the tier you create. + This option is only visible if the network offering you selected is + VLAN-enabled. + For more information, see the Assigning VLANs to Isolated + Networks section in the &PRODUCT; Administration Guide. + For more information, see . + Netmask: The netmask for the tier you create. For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is diff --git a/docs/en-US/vlan-assign-isolated-nw.xml b/docs/en-US/vlan-assign-isolated-nw.xml index 82fd5b58b41..2ed0129cfdf 100644 --- a/docs/en-US/vlan-assign-isolated-nw.xml +++ b/docs/en-US/vlan-assign-isolated-nw.xml @@ -22,51 +22,41 @@
Assigning VLANs to Isolated Networks &PRODUCT; provides you the ability to control VLAN assignment to Isolated networks. You can - assign a VLAN ID when a network is created, just the way it's done for Shared networks. - Additionally, a network with VLAN ID can be excluded from the Network Garbage Collection. + assign a VLAN ID when a network is created, just the way it's done for Shared networks. The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be re-used either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned. + To enable you to assign VLANs to Isolated networks, - Log in to the CloudPlatform UI as an administrator or end user. + Create a network offering by specifying the following: + + + Guest Type: Select Isolated. + + + Specify VLAN: Select the option. + + + For more information, see . + For more information, see the &PRODUCT; Installation Guide. - Ensure that the VLAN range does not already exist. + Using this network offering, create a network. + You can create a VPC tier or an Isolated network. - Check whether the new VLAN range overlaps with any existing ones. If overlaps, extend - the existing range. If does not overlap, add the new range. - - - In the left navigation, choose Infrastructure. On Zones, click View More, then click the - zone to which you want to work with. - - - Click Physical Network. - - - In the Guest node of the diagram, click Configure. - - - Click Add VLAN Ranges button - - - - - add-vlan-ico.png: button to add a VLAN range. - - - The Add VLAN Ranges dialog is displayed. - - - Specify the start and end of the VLAN range. - - - Click OK. + Specify the VLAN when you create the network. + When VLAN is specified, a CIDR and gateway are assigned to this network and the state is + changed to Setup. In this state, the network will not be garbage collected. + + You cannot change a VLAN once it's assigned to the network. The VLAN remains with the + network for its entire life cycle. +