Online Help

VLAN Connectivity

CloudShell provides dedicated VLAN services that enable the creation of Layer 2 connections between both physical and virtual endpoints (for example, physical servers and App-deployed virtual machines) by allocating a VLAN ID for each connection. VLAN-based connectivity supports both peer-to-peer and many-to-many connections.

To use VLANs in CloudShell, the system administrator needs to perform the following configurations:

  1. Associate the VLAN service family to the domain categories
  2. Customize the VLAN service models
Important: Before setting up your L2 resources and connections, review VLAN Connectivity - Points to Consider.

How CloudShell creates VLAN connections

When resolving a VLAN connection between sandbox resources/Apps, CloudShell assumes the devices can access one another on the L2 network. In other words, if the connection involves several interconnected switches, CloudShell only configures the edges of the layer 2 networks but doesn’t affect what happens inside.

For example, the diagram below illustrates an L2 network using three L2 switches. Switch 1 is connected to your physical devices, while switches 2 and 3 comprise the fabric.

When connecting any of the endpoints, whether its physical devices or virtual machines deployed in your vCenter server, CloudShell only cares about their immediate ports, and not what happens between them.

How CloudShell allocates VLAN IDs

CloudShell allocates VLAN IDs for routes using several parameters that are defined by the administrator in the VLAN service. The parameters are Pool Name, VLAN ID, Allocation Ranges, and Isolation Level, which are explained below.

CloudShell can check availability for a specific VLAN ID or find an available VLAN ID within the defined Allocation Ranges.

When connecting a route that uses a VLAN service, CloudShell allocates the VLAN ID based on the availability of the VLAN ID in the pool specified, which is the domain by default. However, if the VLAN ID is Shared (defined in the Isolation Level attribute), it can be shared among multiple connections in the same sandbox and between sandboxes in the same domain/pool.

Associate the VLAN service family to the domain categories

To expose the VLAN services in the Apps / Services catalog of a specific domain, you must associate the service family to each desirable domain's service category. For information about creating service categories for domains, see Creating a service catalog category.

To associate the VLAN services to the domain category:

  1. As system administrator, log into Resource Manager Client.
  2. In the Admin ribbon, click Resource Families.

    The Resource Families explorer is displayed.

  3. Click the service family containing the VLAN services. For example, Virtual Network.

    The family's Parameters pane is displayed.

  4. Click the Categories tab.
  5. Click Add.

    The Select Category dialog box is displayed.

  6. Select the domain category. To select multiple categories, press the [Shift] key.
  7. Save your changes.

Customize the VLAN service models

This section explains how to customize the default settings of the Subnet service and control which settings can be changed by the user in the blueprint diagram. To learn how to add a subnet to a blueprint and set the service's attribute values, see Services in Blueprints.

Note: Additional VLAN services can be created. For example, you could set up multiple VLAN Auto services in the same domain, each with a different allocation range.

Simply duplicate an existing VLAN service and edit the settings, as appropriate. Then, in the Scripts - Resource management page, add the new VLAN service model to the Vlan Service Connect All script.

  • VLAN Auto: This preset automatically selects the VLAN ID for each endpoint connection out of a defined range according to availability in the domain's pool. VLAN Auto allocates VLAN IDs as exclusive by default. This means that the same VLAN ID cannot be used in two or more sandboxes in the same pool.

    Note: VLAN Auto selects only one available VLAN ID, even if it is used in Trunk mode.

  • VLAN Manual: This preset enables the user to specify the VLAN ID to use. VLAN Manual allocates VLAN IDs as shared by default.

  • P2P VLAN Default: This preset enables you to set the default VLAN settings to be used by peer-to-peer connections. By default, it allocates an exclusive VLAN ID for each endpoint connection out of a defined range according to availability in the domain's pool.

    Related Topics