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 the 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 an instance types see each cloud cloudSwXtch installation.
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 is needed. For example, to send the largest standard packet of 1500 bytes, change the MTU to 1532. If a larger MTU size is required, see How to set MTU Size.
To contact sales, please visit swXtch.io/contact.
CPUs
CPUs must be at least an Intel processor with a minimum of 8 cores and 16 recommended.
Memory
A minimum of 8GB of RAM with 16 recommended.
Storage space
An SSD of 24 minimum and 50GB recommended.
Internet Connection
Installing and upgrading cloudSwXtch requires an 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
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 as it simplifies the installation and allows all xNICs to also use just one subnet for a single NIC for installation.
In the event that a user needs higher performance, subnets can be separated, 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 a single VM to have two NICs on the same VPC, hence the same subnet. If the user wants to use a single NIC on the agents, both the ctrl-subnet and the data-subnet must be peered.
Subnet Selection
The subnets must have connectivity to the corresponding subnets used for the xNIC installations.
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.
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.
Subnet | Protocol | Ports | VM |
|---|---|---|---|
ctrl-subnet | http | 80 | all |
ctrl-subnet | udp | 10800-10803 | all |
data-subnet | udp | 9999 | all |
Also, the cloud must allow traffic between VMs with that configuration (Security Groups).
PTP
PTP needs special firewall exceptions in order to work in a user’s cloudSwXtch environment properly. If the user plans on using the feature, please allow the following:
Subnet | Protocol | Ports | VM |
|---|---|---|---|
ctrl-subnet | http | 80 | cloudSwXtch |
ctrl-subnet | udp | 319-320 | all |
ctrl-subnet | tcp | 9200 | all |