Configure Network Settings
The next step is to configure the network resources of the system. When deploying a server workload, it is possible to assign any number of virtual network interfaces and map those interfaces to a logical network. Each compute node is attached to a physical network A -NIC 0 and physical network B -NIC 1 that correspond to the 10GBit physical ethernet ports on the blade. When assigning a server workload network interface to a logical network, it can be assigned to either:
- Network A -NIC 0, as a direct attached network link
- Network B -NIC 1, as a direct attached network link
- A virtual SDN overlay network that is accessible to any server workload running on any NexVisor system if it has the appropriate assignment to a resource group
The virtual SDN overlay option can scale up to an unlimited number of virtual networks and does not rely on any network assisted VLAN protocols. It allows you to aggregate the physical network paths (A and B) to scale up throughput whilst providing Ethernet level secure isolation. The virtual overlay network implementation is extremely efficient, providing native bandwidth scaling per physical ethernet path without any software overlay overhead commonly introduced with implementations of SDN protocols such as VxLAN or GRE.
Note : The system comes pre-configured with Networks A and B at initialization time. The virtual SDN overlay option is the recommended approach for any communication between workloads, running across the system, which does not necessarily require routable external traffic access.
To set up a virtual network, please follow the next steps:
Step 1 - Choose the IP address assignment method:
First step is to configure the IP address assignment behaviour for this network. The administrator can choose one of the following virtual network options, referring to the DHCP type:
External - directly attached to physical interfaces and IP addresses assigned from external DHCP server
Internal - virtual private network assigned with DHCP IP adddresses internally
Static - configured with static IP address assignment either attached directly to physical interfaces or isolated internally for virtual private networks
-DHCP assignment of addresses based on server workload network interface MAC address -Static IP assignment configured into the server workload using the cloud-init logic
Network settings offer two additional options:
- Routable: Should be enabled in case access needs to be provided to private networks communicating with external workload traffic. In the case of Internal networks, Routable should be enabled in conjuction with the NAT Forwarding option, as shown following image.
Be aware in case of Internal DHCP routable network the IP address x.x.x.254 is reserved by the system. This IP address cannot be allocated in the provided 'IP Address End' range of the custom network by the user.
- IPv4 -IPv6 supported versions
Please ensure that all the corresponding network fields, such as IP Address Start , IP Address End , Gateway IP, DHCP server IP and Network Prefix are properly provided, in order to avoid complicated network diagnostic issues when communicating between server workloads.
Step 2 - Select the physical paths to carry traffic:
Select physical paths that should be used to send and receive traffic for the virtual network. You can physically separate traffic between virtual networks if performance isolation is required. The physical paths selected will be used to transmit packets in aggregate to other virtual network members.
Step 3 - Finalise the network creation wizard:
Enter the Name and Description for your new virtual network. Click the Finish button to instantiate the network.