Cluster Networks

A cluster network defines Layer 2 and Layer 3 connectivity within a switch domain.

You use a cluster network to control VLAN tagging, IP addressing, MTU, and routing for cluster traffic.

Cluster networks are scoped to a single switch domain. This ensures traffic isolation and clear operational boundaries.

Cluster Networks Management

View Cluster Networks

The Cluster Networks page displays all defined cluster networks.

To view cluster networks:

Go to Region Networking.
Select Cluster Networks.

The list view includes the following columns:

Name

The unique name of the cluster network.
VLAN ID

The VLAN tag associated with the network.
MTU

The maximum transmission unit in bytes.
Subnet CIDR

The IPv4 subnet in CIDR notation.
Connected Nodes

The number of nodes attached to the network.
Switch Domain

The switch domain that owns the network.

Select a cluster network name to open its details page.

View a Cluster Network’s details

Go to Region Networking.
Select Cluster Networks.
Select a cluster network name to open its details page.

Each cluster network is associated with:

Name

A descriptive identifier of the cluster network. This value is defined during creation and is displayed in list and detail views.
VLAN ID

The VLAN tag assigned to the cluster network. This value identifies the Layer 2 broadcast domain used for traffic isolation.
MTU

The maximum transmission unit, in bytes. This value defines the largest packet size allowed on the network.
Connected Nodes

The number of nodes currently attached to the cluster network. This value indicates active participation in the network.
Nameservers

DNS server entries assigned to the cluster network. These values define how hosts in the network resolve domain names to IP addresses. Each entry can be an IPv4 address or a DNS hostname.
Switch Domain The switch domain that contains the cluster network. This value determines the logical networking boundary.
ID

The unique identifier of the cluster network. This value is defined during creation and is displayed in list and detail views.
Subnet CIDR

The IPv4 subnet in CIDR notation. This value defines the address space available for IP allocations.

A cluster network can also include associated components, displayed in the following tabs:

Nodes tab

Displays nodes connected to the cluster network, including their IP address, Node ID, admin state, and operational state.
Routes tab

Displays configured static routes for the cluster network, including destination networks and next-hop addresses.
Applications tab

Displays applications associated with the cluster network, including application type, switch domain, and linked cluster network.
VIPs tab

Displays virtual IP resources attached to the cluster network, including direction and sharing status.
IP Addresses tab

Displays individual IPv4 addresses and address ranges defined for the cluster network, including allocation status and ownership details.

Create a Cluster Network

Creating a cluster network defines connectivity parameters for a specific switch domain.

To create a cluster network:

Go to Region Networking.
Select Cluster Networks.
Select Create.
Complete the wizard steps.

Info Step

The Info step defines core network properties.

Fields:

Name Enter a unique name for the cluster network.
Switch Domain Select the switch domain that will contain the network. Only one switch domain can be selected.
VLAN Select an existing VLAN. You can also create a new VLAN from this field.
Subnet CIDR Enter the IPv4 subnet in CIDR format (for example, 10.16.24.0/21).
MTU Enter a value between 1500 and 9216. The value is typically aligned with the switch domain.

IP Ranges Step

Define IP allocation ranges for the subnet.

You can:

Create individual IP addresses
Create IP address ranges

Create IP Address Range dialog fields:

Start IP The first IPv4 address in the range.
End IP The last IPv4 address in the range.

Create IP Address dialog fields:

IP Address A single IPv4 address inside the subnet.

Routes Step

Define static routes for the cluster network.

Create Route dialog fields:

Destination The destination network in CIDR format (for example, 0.0.0.0/0).
Next Hop The IPv4 address of the next-hop gateway.
Policy Routing Table The routing table identifier. The default value is 0.

Nameservers Step

Define DNS servers for the cluster network.

Fields:

Nameserver Enter an IPv4 address or DNS name.

After completing all steps, submit the wizard to create the cluster network.

Update a Cluster Network

Updating a cluster network modifies its configuration.

To update a cluster network:

Go to Cluster Networks.
Select the required cluster network.

The details screen opens.

Some of the cluster network tabs permit updating associated components, as follows:

Tab

Update existing

Add new

Delete existing

Nodes

✗

Routes

✗

✓

✓

Applications

✗

✓

✓

VIPs

✓

IP Addresses

✗

✓

✓

Tab	Update existing	Add new	Delete existing
Nodes	✗
Routes	✗	✓	✓
Applications	✗	✓	✓
VIPs	✓
IP Addresses	✗	✓	✓

View Nodes

The Nodes tab displays all nodes connected to the cluster network.

Note

There are no controls for MSP admins to create, modify or delete a cluster network’s nodes.

To view the Nodes tab:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the Nodes tab.

The table lists the following details for each associated node:

Node Name The display name of the connected node. This value identifies the node in the environment.
IP Address The IPv4 address assigned to the node within the cluster network.
Node ID The unique identifier of the connected node.
Admin State The administrative state of the node interface, such as enabled or disabled.
Operational State The runtime state of the node interface, such as up or down.

View or Manage Routes

The Routes tab displays all routes configured for the selected cluster network.

Each entry represents a routing rule that directs traffic to a specific destination network.

The Routes tab allows you to review existing routing rules and verify traffic forwarding behavior for the cluster network.

To view the Routes tab:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the Routes tab.

The table lists the following details for each associated route:

Destination The target network in CIDR format. This defines the address range that the route applies to.
Next Hop The IPv4 address of the gateway used to reach the destination network.

Creating a new route

To create a new route for the selected cluster network:

From the Routes tab’s toolbar, select + Create.

The Create Route dialog opens.
Enter the required fields.
- Destination
  
  Enter the destination network in CIDR format (for example, 0.0.0.0/0). This defines the network that the route will match.
- Next Hop
  
  Enter the IPv4 address of the gateway. This is the address used to forward traffic to the destination.
- Policy Routing Table
  
  Enter the routing table identifier. This value determines which routing table processes the route.
  
  The default value is 0.
Select Create to save the route.

Deleting a route

Caution

Removing a route can immediately stop traffic to the destination network. Services that depend on that route can become unreachable.

Before deleting a route:

Verify the destination network is no longer required.
Confirm that another valid route exists, if needed.
Assess the impact on connected applications and VIPs.
Schedule the change during a maintenance window if production workloads coulbd be affected.

To delete an existing route configured for the selected cluster network:

In the selected cluster network’s Routes tab, select the route to delete.
From the Routes tab’s toolbar, select Delete.

The Delete Route dialog opens, displaying the selected route’s ID.
Select Delete to confirm deleting the route.

The route no longer appears in the Routes tab list.

View or Manage Applications

The Applications tab displays all applications that are attached to the selected cluster network.

Each entry represents a network-based service that uses the cluster network for connectivity.

Use this tab to review which services depend on the cluster network before making configuration changes, such as route modifications or deletion.

To view the Applications tab:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the Applications tab.

The table lists the following details for each associated application:

Name

The application name. This identifies the service in the environment.
Type

The application type, such as network or virtual_ip. This indicates the function of the application.
Switch Domain

The switch domain associated with the application. This confirms the logical networking boundary.
Cluster Network

The cluster network to which the application is attached. This shows the connectivity context for the service.

Creating a new application

To create a new application for the selected cluster network:

From the Applications tab’s toolbar, select + Create.

The Create Application dialog opens.
Enter the required fields.
- Name
  
  Enter a unique name for the application.
- Application Type
  
  The application type determines the behavior of the application.
  
  Select the application type.
  
  Note
  
  Currently, for cluster networks, MSP admins can select only Network as the application type.
Select Create to save the application.

Deleting an application

Deleting an application removes the service from the cluster network.

Caution

Considerations Before Deleting

Review the following before proceeding:

Service Availability

Deleting the application immediately stops theassociated service. Clients could lose connectivity.
VIP Dependencies

If the application is associated with a virtual IP, traffic directed to that VIP could fail.
IP Address Allocation

The application might own allocated IP addresses. Confirm whether those IPs should be released or reassigned.
Route Dependencies

The application could rely on specific static routes.

Removing the application does not remove routes.
Change Management

Perform deletion during a maintenance window if production workloads could be affected.

After deletion, verify that:

Required services are still reachable.
No unintended IP allocations remain.
Monitoring systems reflect the change.

To delete an existing application configured for the selected cluster network:

In the selected cluster network’s Applications tab, select the application to delete.
From the Applications tab’s toolbar, select Delete.

The Delete Application dialog opens, displaying the selected application’s name.
Select Delete to confirm deleting the application.

The application no longer appears in the Applications tab list.

View or Manage VIPs

From the cluster network details page, select VIPs to view virtual IP resources.

VIPs table columns include:

Name The VIP name.
Switch Domain The associated switch domain.
Cluster Network The linked cluster network.
Direction Traffic direction, such as inbound or outbound.
Shared Indicates whether the VIP is shared.

The VIPs tab displays all virtual IP resources that are attached to the selected cluster network.

Each entry represents a logical IP address that can be used to expose or receive traffic for a service.

The table includes:

Name

The name of the virtual IP resource. This identifies the VIP in the environment.
Switch Domain

The switch domain that contains the VIP. This confirms the networking boundary.
Cluster Network

The cluster network to which the VIP is attached. This defines the subnet and VLAN context used by the VIP.
Direction

The traffic direction associated with the VIP, such as inbound or outbound. This defines how the VIP handles traffic flow.
Shared

Indicates whether the VIP is shared across multiple services or dedicated to a single service.

Use the VIPs tab to review external exposure and service entry points before modifying routes, IP ranges, or deleting the cluster network.

Modifying a Virtual IP (VIP)

You can modify a virtual IP from the cluster network details screen.

Caution

Considerations Before Deleting

Modifying a VIP can affect traffic immediately.

Disabling the VIP stops traffic to the IP address.
Changing the direction can alter traffic behavior.
Changing the associated service can redirect traffic.

After saving changes, verify that:

The VIP responds as expected.
Dependent services remain reachable.
Monitoring reflects the updated state.

To modify a VIP:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the VIPs tab.
Select the required VIP.
Select Modify.

The Modify VIP dialog opens.

Some of the VIP fields can be modified:
- Name
  
  The display name of the virtual IP. Update this value to change how the VIP appears in the system.
- Cluster Network (Display only, cannot be modified)
  
  Displays the cluster network to which the VIP is attached. This value is read-only.
- IP Address
  
  The IPv4 address assigned to the VIP. This value identifies the logical service endpoint. Update this value to assign a different IP address to the VIP.
- Enable
  - Select to enable the VIP.
  - Clear to disable the VIP.
  Disabling a VIP stops traffic without deleting it.
- Direction
  
  Defines how traffic is handled.
  
  Select the traffic direction:
  - Inbound
  - Outbound
- Service
  
  This value links the VIP to a specific service.
  
  Enter or select the associated service.
- Shared
  - Select to allow the VIP to be shared.
  - Clear to dedicate the VIP to a single service.
Select Finish to apply the changes.

View or Manage IP Addresses

The IP Addresses tab displays all IPv4 addresses defined for the cluster network.

This includes both allocated addresses and addresses that are available for allocation.

Each entry represents an IP resource within the subnet defined for the cluster network.

To view the cluster network’s IP Addresses:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the IP Addresses tab.

The table of IP Addresses displays all IPv4 addresses defined for the cluster network.

This includes both allocated addresses and addresses that are available for allocation.

Use this tab to review address usage, verify allocations, and confirm that sufficient IP capacity remains available within the subnet.

Each entry in the table represents an IP resource within the subnet defined for the cluster network:
- IPv4 Address
  
  The IP address assigned within the cluster network subnet.
- Node ID
  
  The identifier of the node associated with the IP address, if the address is allocated.
- Status
  
  The allocation state of the IP address, such as allocated or free.
- Owner ID
  
  The identifier of the resource that owns the IP address.
- Owner Type
  
  The type of resource that owns the IP address, such as an application or network interface.

Creating new IP Addresses

You can add individual IP addresses or IP address ranges to a cluster network from the IP Addresses tab.

Note

Considerations

The IP address must belong to the cluster network subnet.
The IP address must not already be allocated.
Avoid adding addresses that overlap with existing ranges.

After adding addresses, verify that the new entries appear in the IP Addresses table.

To add IP addresses:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the IP Addresses tab.
Select one of:
- + Create to add a single IP address.
  
  The Create IP Address dialog opens.
  - IP Address
  Enter a single IPv4 address within the subnet defined for the cluster network. The address must be unique and must belong to the subnet CIDR of the network.
- + Create Range to add a range of addresses.
  
  The Create IP Address Range dialog opens.
  - Start IP
    
    Enter the first IPv4 address in the range. This value defines the beginning of the address block.
  - End IP
    
    Enter the last IPv4 address in the range. This value defines the end of the address block.
Select Create to add the address or address range.

Deleting an IP Address

You can delete individual IP addresses from a cluster network.

Caution

Considerations for deleting IP Addresses

Deleting an IP address removes it from the cluster network address pool.

Review the following before deleting:

Allocated Addresses

Do not delete an IP address that is currently allocated to a node, application, or VIP.
Service Impact

If a resource depends on the IP address, deleting it can interrupt connectivity.
Address Pool Capacity

Deleting address ranges reduces the number of IP addresses available for allocation.

After deletion, verify that:

The address no longer appears in the IP Addresses table.
Dependent services continue to function correctly.

To delete an IP address from a cluster network:

Go to Region Networking.
Select Cluster Networks.
Select the required cluster network name.
Select the IP Addresses tab.
Select the IP address to remove.
Select Delete.

The Delete IP Address dialog opens, displaying the IP address and its ID.
Select Ok to confirm deleting the IP address.

Delete a Cluster Network

Deleting a cluster network removes it from the switch domain.

Before deletion, ensure no dependent resources remain attached to it.

Dependencies can include:

Nodes
Routes
Applications
VIPs
IP allocations

To delete a cluster network:

Go to Cluster Networks.
Select the required network.
Select Delete.
Confirm the action.

Recommended Best Practices

Use clear, descriptive names for cluster networks.
Separate environments by using different switch domains.
Avoid overlapping subnet CIDRs across cluster networks.
Align MTU values with the physical network design.
Define IP ranges before deploying applications.
Review static routes carefully before applying them.
Remove unused cluster networks to reduce complexity.

Troubleshooting Cluster Networks

Cluster Network Not Visible

Verify you are in the correct region.
Confirm the correct switch domain is selected.
Check user permissions.

IP Allocation Fails

Ensure the IP is inside the defined subnet CIDR.
Confirm the IP is not already allocated.
Verify the defined IP ranges include the address.

Route Does Not Work

Validate the destination CIDR format.
Confirm the next-hop IP is reachable.
Check for conflicting routes.

Connectivity Issues

Verify VLAN ID configuration.
Confirm MTU consistency across nodes.
Review nameserver entries.
Check switch domain boundaries.

Use the cluster network overview page to verify:

VLAN ID
Subnet CIDR
MTU

Correct configuration mismatches and retest connectivity.