A vLAN is a private network between Miniserver VM®s and dedicated servers in your account, facilitating entirely secure communications within your infrastructure. In addition traffic speeds are limited by the inter-rack networking infrastructure and not by each servers external bandwidth so vLAN speeds can be very fast.
This is included free with Performance Patrol™ and for customers with a dedicated server.
vLANs can be managed using the vLAN management page can be found in the Your Services of the Summary page. It will show a list of all the available vLANs in the account.
An example vLAN on the summary page looks like the following:
Any new vLANs that are ordered or the vLAN that is included with he load balancer product will get added as new lines to this page.
The Manage link on the far right of each vLAN row will take you to the service overview page for that vLAN.
In the service overview page, the following relevant details are displayed.
Manage VLAN hosts in the Management tools section can be used to add and remove hosts to the vLAN.
The manager will also display the private IP addresses assigned to each host.
Adding or removing a host will trigger a network configuration change that can affect your service, so confirmation will be requested before performing any operation.
The configuration changes are described in the following sections.
When a Miniserver host is added or removed, it will be rebooted. A new private IP address from the vLAN class C network may be assigned (if needed). Once the Miniserver reboot is completed, the new IP address will be available.
A Miniserver can join several vLANs at once.
Dedicated servers won't be rebooted, manual configuration of the assigned private IP address may be required.
A dedicated server requires a vLAN to function so it's not possible to remove it from its vLAN. It can be moved to a different vLAN, and that operation needs to be performed with the management tool of the destination vLAN.
A dedicated server can join additional vLANs at the same time.
When a Miniserver is added to a vLAN, a new private IP address will get added to a new network interface on the server. Any subsequent vLANs that the server is made a member of will get added as additional interfaces.
However, if the "Set as the primary vLAN for this host" box is checked when the server is added to a new vLAN then the new private IP will replace the IP on the first interface. This has the additional effect of removing the server from the old vLAN.
This is less relevant in dedicated servers as the network configuration changes have to be performed manually.
Once a host is removed from a vLAN it is possible that the private IP address will not be in use any more. That private IP address is not removed automatically to avoid possible configuration problems in host's services.
Please contact support if you want a private IP address to be deallocated.
Servers configured to provide a service in a load balancer can't be removed or moved to a different vLAN because that would disrupt the load balanced service. You must remove servers from the load balancer before they can be removed from the vLAN. This can be done via the Load Balancer Management section of your Memset account.
Hosts in a load balancer will appear in the host manager tagged with a LB label.
The Memset backend systems are not able to automatically configure the networking for Windows servers, both dedicated servers and Miniservers, and fully virtualized Miniservers running any operating system.
The new private IP address will need manually adding to the server after the server has been added to the vLAN. If you need assistance with this please lodge a support ticket with the Memset support team via the Reboot and Contact page.
A server can be a member of several vLANs without any problems. When a server is added to an extra vLAN, a new network interface will be created on the server and the private IP added to it (unless "Set as the primary vLAN for this host" is used) and function alongside the other vLAN IP's.
Should you wish to migrate the server to a new vLAN i.e. remove it from from the first and add it to the second then you must either:
Last updated 11 June 2015, 09:29 GMT