cloudSwXtch System Requirements

WHAT TO EXPECT

In this article, users will learn about the system requirements needed to successfully deploy a cloudSwXtch. It is recommended for a user to review this page before installing a cloudSwXtch any of the four cloud platforms.

cloudSwXtch Sizing Guidelines

Sizing and Feature Selection For Your cloudSwXtch

The number of endpoints and bandwidth dictate cloudSwXtch sizing requirements. It is recommended for users to contact a swXtch.io sales representative to discuss cloudSwXtch sizing and additional features so that the appropriate license can be distributed. Please note: A cloudSwXtch BYOL offering will not work without a license. 

• Sizing: For bandwidth greater than 2 Gb/s and endpoints greater than 100, you will need different virtual CPUs/NIC sizing. 

• Adding Features: Many additional licensable features are available for cloudSwXtch. For more information, see cloudSwXtch Features.

• MTU:  The MTU should be set 32 bytes higher than what you need.  For example, to send the largest standard packet of 1500 bytes, change the MTU to 1532.  If you require larger MTU size see How to set MTU Size.

  To contact sales, please visit swXtch.io/contact. 

cloudSwXtch BYOL (Marketplace)

cloudSwXtch PAYG for POCs/Trial

*Hard Drive is dependent on the user’s needs. Note: cloudSwXtch Pay As You Go (PAYG) is a $30/hr offering.

Internet Connection

Installing and upgrading cloudSwXtch requires internet connection. Alternatively, if a user does not have access to the internet, they can use the Air-Gapped installation guide for Azure. 

Supported Cloud Environments

• Amazon's AWS Cloud

• Microsoft’s Azure Cloud

• Google's GCP Cloud

• Oracle's OCI Cloud

Virtual Network

A cloudSwXtch instance must have 2 NICs. However, both NICs can share a single subnet for control and data plane communications. This is the preferred method. 

In the event that a user needs higher performance, a user can separate their subnets as described below.

• Contain a subnet for control plane traffic ( referred to as the ctrl-subnet from here on).

• Contain a subnet for data plane traffic ( referred to as the data-subnet from here on).

Please note: GCP does not allow for single subnet configuration. A user must have 2 separate subnets for their data and control NICs.

The virtual network and subnets may be shared with other services in addition to the cloudSwXtch. The size of each subnet should include at least 32 addresses.

Minimum CPU and Memory

A cloudSwXtch must be a minimum of 8 cores and 16 GiB memory, 32 is recommended.

Firewall and Security Group Rules

The xNIC software and the cloudSwXtch communicate with each other using the following protocols and ports. These firewall exceptions must be allowed in the xNIC VMs and the cloudSwXtch VM.

Mesh and High Availability

Both Mesh and High Availability need special firewall exceptions in order to properly work in a user’s cloudSwXtchenvironment. If you plan on using either features, please allow the following:

Mesh

High Availability

Reminder: HA Mesh are mutually exclusive and cannot be used together.

PTP

PTP needs special firewall exceptions in order to properly work in a user’s cloudSwXtch environment. If you plan on using the feature, please allow the following: