Each Arcus cloudspace has two networks by default, each with a class C (/24) address space. One network is called cons3rt-net for use by Arcus for provisioning, asset installations, remote access, and services like the yum repository. The other default network is called the user-net, for use by you for systems-to-system communication, and for Internet access.
This default network configuration works for most use cases. However, team managers can customize networks by adding and removing networks as described below. Only the cons3rt-net is required and cannot be modified.
Adding Custom Networks to a Cloudspace
Team managers can add custom networks to cloudspaces they manage. First, select cloudspaces in the navigation column on the left and then find the cloudspace you would like to configure and select it.
Next, click the “Manage” button and select “Networking” in the left column.
Finally, add the new network by clicking “+ Add” and filling out the networking details.
If you select Allow traffic from this network to be routed externally
, you will have the option to configure firewall and DNAT rules, and a boundary IP will be automatically assigned.
If you do not select Allow traffic from this network to be routed externally
. The network will be considered “isolated” and cannot communicate with the outside world.
Removing Custom Networks from a Cloudspace
Team managers can remove custom networks from cloudspaces they manage. First, select cloudspaces in the navigation column on the left and then find the cloudspace you would like to configure and select it.
Next, click the “Manage” button and select “Networking” in the left column.
Click the “trash” icon to the right of the desired network to begin to remove the network.
Removing the network without selecting the “deallocate” option results in an “unregistered subnet.” Unregistered subnets are not available to attach to future deployment runs, but can be re-registered at a later date by clicking “Register”.
Removing and selecting the “deallocate” toggle will completely remove the network from the system. Please note that for deallocation to be successful, there must be no remaining runs associated with that network. If there are active runs, the deallocation process will fail, and you may need to contact support.
Default IP Addressing in VMware Arcus cloudspaces
This section is applicable to users with Arcus VMware cloudspaces. Arcus VMware-based cloudspaces typically use the following IP addressing scheme for the two networks:
- cons3rt-net: 172.16.10.0/24
- user-net: 192.168.10.0/24
On the user-net, the block of IPs is divided into pools as follows:
- x.x.x.2-x.x.x.240: *CONS3RT range dynamic pool used for auto assignment of IPs by Arcus
- x.x.x.240-x.x.x254: reserved for Arcus services, do not use
Default IP Addressing in AWS, Azure, and Openstack
In AWS, Azure, and Openstack cloudspaces, there is also a cons3rt-net and user-net. Most AWS, Azure, and Openstack cloudspaces use the following IP addressing scheme by default:
- cons3rt-net: 172.16.10.0/24
- user-net 172.16.11.0/24
Boundary IP Addresses
Boundary IP addresses are automatically configured when a network is created and Allow traffic from this network to be routed externally
has been enabled. The default user-net will have this feature enabled when a cloudspace is allocated for the first time. Boundary IP addresses allow secure communication between the cloudspace and anywhere outside of the cloudspace.
More Help
Review this topic with our video tutorials: