FAQs

Can I move an existing device to a new VLAN?

Existing compute devices, such as a virtual server instance (VSI) or a bare metal, cannot be moved to a new VLAN. A new VSI or bare metal must be provisioned in the new VLAN and deprovisioned accordingly. Single VLAN firewalls cannot be moved to a new VLAN either. Multi VLAN firewalls can be attached to the new VLAN and then detached from the previous VLAN. Refer to the specific offering documentation for capabilities and limitations.

Is there a way to specify which VLAN I want to use for my device when I order it?

Yes, a specific VLAN can be selected during the ordering process. This option is available at the end of the device order form. A private VLAN is selected, followed by a public VLAN. Remember that a subnet selector is presented for each VLAN, and that this selection is optional. Select a subnet only if you have reason to do so because selecting a subnet that lacks available IP addresses negatively impacts the fulfillment of the device. See the Subnet FAQ for more details.

The selected VLAN must be located in the same data center as the device. We cannot assign a device to a VLAN that is in a different data center.

How many devices can be assigned to a single VLAN?

Currently, no limit exists for the number of devices that are associated with a single VLAN at any time. However, when a hardware firewall is associated with a VLAN, the type of firewall might impose restrictions on the number of devices that reside on the VLAN.

What kinds of devices are assigned to a VLAN?

Any device that has a network connection is associated with a VLAN. Dedicated servers have both a public and private network connection, so you see those devices associated with both public and private VLANs.

How do I trunk my VLANs to my servers?

For more information about managing VLANs as trunks, see Configuring VLAN trunks.

As I order a VLAN, what does it mean when I'm told that no VLANs are available?

If you are told that no VLANs are available, see A note about capacity.

How long can empty Premium VLANs remain unused on my account?

Premium VLANs which are not participating in Layer 2 or Layer 3 networks for 90 days or more are subject to automatic cancellation of billing and reclaim of the VLAN in order to maintain sufficient VLAN capacity for all customers. Any secondary subnets present on the VLAN will be unrouted as part of VLAN reclaim. For more information regarding the automatic reclaim policy of unrouted secondary subnets, see the Subnets FAQs.

Why can't my devices communicate with one another on the same private VLAN?

If each server is on a different subnet, then by default, they are not able to communicate via IP addresses. Technically, your servers can communicate by using OSI Model Layer 2 methods because they are on the same VLAN (a Layer 2 construct). For Internet Protocol (IP) (also called Layer 3) communication to work, you can do either of the following:

• Add a route for the subnet you're attempting to communicate with on each server (the route is different on each server)
• Enable VLAN Spanning

Keep in mind that VLAN Spanning has additional implications, so review the feature in detail before enabling it.

What options do I have if I need devices on different private subnets within the same VLAN to communicate by default, but I don't want to enable VLAN Spanning?

If you cannot enable VLAN spanning but require some VLANs and subnets to route between each other, you can associate those VLANs with a firewall or gateway, and manage the routing and security to fit your needs. To route between Pods and data centers, all VLANs requiring connectivity must be associated with the gateway device and an overlay, typically GRE tunnels, established between the gateway devices.