Network Configuration

Network Configuration

To facilitate the greatest level of customer privacy and flexibility, we use 802.1q port trunking to each server, and we map private VLANs and VXLANs based on each customer’s need.

By default, each server has at least two 8012.1q VLANs:

Additional VLANs may be added for other needs, such as storage.

Note: Changes to VLANs, MAC Addresses, or BMC are prohibited:

It is not allowed to change the MAC address of the NIC, nor to make any changes to the BMC, nor to try to use other VLANs. If these changes are made, the server may be null-routed until we can rectify the configuration with you.

Public Network

Your Public Network is optional. Depending on your configuration this may use a common network block shared by other servers in the Pod.

If you are using a public network, you are responsible to configure a DNS provider for your needs (this is not provisioned automatically).

Private VLAN(s)

Each customer is assigned a Private VLAN for all servers in a Pod. There is no default VLAN for untagged packets, unless you request it. This private VLAN can be used for cross-server internal networking, or it can be ignored.

Private VLANs are limited to the Pod — if you have servers across Pods, they must communicate through the public network.

We only provide Layer-2 services on this VLAN. You can add any Layer-3 network space as you so desire, and are responsible for the management of this network space.

Traffic Management / Load Balancers

At this time, there are no load-balancer or higher-level network services available, but these services are on our roadmap. You can create these services on your servers, however.

Cato Digital

Ready to get started?

View available application or storage servers. Get Started
Cato Digital ™, and © Cato Digital, inc  | Terms | Privacy