Back

Use Cases

Here are some of the main use cases for L2 Segments:

Network segmentation

The basic use case is the network segmentation, or subnetting. A single client can allocate multiple L2 Segments and assign servers with different roles to different segments. Because of this, servers with different roles will be in different networks. For example, the servers hosting a public website can be isolated from the servers running a CRM application. This increases the security within the network.

Floating IP addresses

A more complex use case involves floating IP addresses. This use case is typical amongst services demanding high availability. Floating IP address can be transferred between multiple servers allowing for a failover or upgrade of production software. For a floating IP address to be transferred between physical servers, data link layer connectivity is required between those servers.

Private cloud is another instance requiring floating IP addresses. Floating IP addresses allow for the migration of a virtual server between physical servers in a virtualized environment. When a Virtual Machine (VM) is moved to a new bare metal server, the new server announces the takeover of an IP address of the moved VM, so that the VM can remain reachable by its IP address regardless of physical location.

Custom IP addressing

The next use case is to fulfil the specific needs of the proprietary or legacy software systems. Custom IP addressing provides the flexibility to use almost any IP address space within L2 Segments. This service allows the clients to deploy their own DHCP and PXE servers.

Multicast

A large amount of software relies on Ethernet multicast to reduce CPU and bandwidth consumption in one-to-many communications. Use cases include audio, video, and quote broadcasting. Multiplayer video game servers are another example; they can use L2 broadcast segments for multicast communications.

Suggested Articles