Managing networks

MetalSoft networks are designed around performance and isolation. The network can be configured in many ways depending on the environment.

In general lines there are 3 types of networks:

1. WAN - This network usually used for getting out of the infrastructure. This is the most used network. Note that the WAN network can also contain additional networks available as trunk VLANs.

2. LAN - This is usually used for connecting servers within the same infrastructure. This is rarely used and will be deprecated in the future.

3. SAN - This is a special network dedicated for SAN traffic, only present if drives are attached to server instances.

Networks are connected to server instance arrays which in turn will propagate the network configuration to all of the underlying server instances.

Using multiple links

It is possible and recommended to configure multiple links to join the same network. In these situations the network of the server and the switch will change to enable the link aggregation to work by configuring M-LAG, VLT or other forms of multi-chassis link aggregations on the switches as well as bond interfaces on the Operating System.

Joining an existing network

1. Option #1

In the infrastructure editor, to join an existing network that connects two SEPARATE instance arrays click on any of the the circles that are connected with the network that you want to join and DRAG to the other desired port (circle) on the target instance array and RELEASE. Note that if you want to connect only servers within the same instance array option #2 must be used.

Press Deploy to effect the changes.

2. Option #2

In the infrastructure editor, click on any of the ports (the circles on the top of instance arrays) and using the form select the network in which the respective port must be connected.

Press Deploy to effect the changes.

Creating a LAN network

1. Option #1 In the infrastructure editor, to create a network that connects two instance arrays CLICK AND HOLD on the circles on the top of the instance arrays and DRAG to the other desired port (circle) on the target instance array and RELEASE.

Press Deploy to effect the changes.

2. Option #2 In the infrastructure editor, click on any of the ports and using the form select the Networks tab and input a name for the network and click Create LAN network button.

In the infrastructure editor, click on any of the ports (the circles on the top of instance arrays) and using the form select the network in which the respective port must be connected.

Press Deploy to effect the changes.

Advanced: Subnet pools

Users have the ability to create subnets from which IPs or entire subnets will be allocated to various uses via the network profiles.

Specify the label of the subnet and the network in CIDR notation:

Advanced: Network profiles

Users have the ability to create network profiles and reuse them across networks and infrastructures.

These network profiles alter the way the network is provisioned for a given instance’s connection to a particular network. Normally these network profiles are created by admins and simply used by the clients but in certain situations such as when the client needs to connect to on-prem infrastructure, these needs to be configured by the client.

To create a network profile as a user

Click on the network icon:

Go to the network profiles tab, click on Add network profile:

Input the label and set a vlan ID for the native (access mode vlan). Additional, trunk mode VLANs can be added later. Note that manual allocation requires a special permission). By setting it to automatic an unique VLAN id will be automatically allocated and configured on the port. This is the default behavior.

To add additional trunk mode vlans to the same network profile

To add additional tagged (802.1q - trunk mode) VLANs to the network profile select the network profile and click Add VLAN.

1. Select the required VLAN allocation and if in manual mode set the VLAN ID to use.

Important

The Manual mode is not enabled by default. A special permission (limit) is required to be able to set specific VLAN ids.

2. Available since 6.2: Set a VLAN Auto-Allocation Index. This is used to support multiple automatically allocated VLAN ids and to refer to the auto-allocated VLAN id across multiple network profiles.

3. Select the required subnet The subnet that you can use is either a private subnet created in the Subnet Pools tab or a subnet that is provided by the admins. Only IPv4 IPs are supported at the moment. Note that from this subnet IPs will be allocated to the interfaces connected and configured with this network profile. If more than one subnet will be configured IPs from ALL the subnets will be allocated.

4. Select the external connection External connections are endpoints (ports) on border leaf switches to which to terminate the respective VLAN. The VLAN id will be attached as trunk mode vlan to the external connection. External connections cannot be defined by end-users.

5. Available since 6.2: Set a VRF ID. Use this to when using overlapping IP addresses.

6. Available since 6.2: Set a VRF Auto-Allocation Index. This is used to support multiple automatically allocated VRF ids and to refer to the auto-allocated VRF id across multiple network profiles.