The basic elements for creating a PRIVATE network are two or more Cloud Servers each with at least one of the network interfaces assigned with a unique private IP address, and a Virtual Switch
The Virtual Switch is required to connect two or more virtual machines as it is otherwise not possible to connect the Cloud Servers with each other using private IP addresses.
In Aruba Cloud Computing a private network can include Cloud Servers with different Operating Systems (Linux, Windows, etc.), as well as Cloud Servers which use different Hypervisors
After assigning on each Cloud Server to a network interface a private IP address (e.g. 192.168.1.1 and 192.168.1.2) it will be possible to connect your Cloud Servers to the Virtual Switch.
In any case the networks that are created are based on the TCP/IP protocol and therefore each network adapter of each Cloud Server must have a unique private IP address set.
To ensure greater security, in Aruba Cloud Computing we have decided to exclude (filter) the NetBios
protocol for recognising the machines connected to the same network. We would like to specify that the only filtered protocol is the NetBIOS Frames (NBF) protocol which works without IP addresses, whereas the NetBIOS over TCP/IP (NBT) works correctly as it is based on TCP/IP.