Before proceeding
Before verifying the private network configuration, you must have configured it in the operating system of each Cloud Server by following the procedure for the operating system used:
Verifying the private network configuration
After configuring the private network in the operating systems of the Cloud Servers, verify that the machines can communicate correctly using their respective private IP addresses.
For example, you may have two Cloud Servers connected to the same Virtual Switch and configured as follows:
| |
Cloud Server 1 |
Cloud Server 2 |
| IP - Virtual Switch |
192.168.0.1 |
192.168.0.2 |
| Netmask - Virtual Switch |
255.255.255.0 |
255.255.255.0 |
| IP address - operating system |
192.168.0.11 |
192.168.0.12 |
| Netmask - operating system |
255.255.255.0 |
255.255.255.0 |
With this configuration, the two Cloud Servers use unique private IP addresses belonging to the same network,
192.168.0.0/24.
To verify that the Cloud Servers can communicate correctly over the private network, ping the private IP address of the other Cloud Server.
On Windows, open
Command Prompt. In this example:
- from Cloud Server 1, run:
ping 192.168.0.12
- from Cloud Server 2, run:
ping 192.168.0.11
On Linux, from the terminal:
- from Cloud Server 1, run:
ping -c 4 192.168.0.12
- from Cloud Server 2, run:
ping -c 4 192.168.0.11
If the ping command returns a response, communication between the two Cloud Servers over the private network is active.
Do not assign the same private IP address to multiple Cloud Servers: duplicate IP addresses cause a conflict that prevents proper communication within the private network.
What to do if Cloud Servers cannot communicate over the private network
If the ping command does not return a response, check that:
- the Cloud Servers are powered on and are not undergoing any operations, such as startup, shutdown, restart, update or configuration changes;
- the Cloud Servers are connected to the same Virtual Switch;
- the correct network interfaces are connected to the Virtual Switch;
- the private IP addresses configured on the network interfaces are unique and belong to the same network;
- the network interfaces use the netmask specified for the private network;
- the operating system firewall does not block the ICMP traffic used by the ping command.
A lack of response to the ping command does not necessarily indicate a problem with the Virtual Switch: ICMP traffic may be blocked by the operating system firewall even when the private network is configured correctly.