Faddom Help Center

Setting up a static IP address for the Faddom appliance


In many cases, setting up a static IP address for the Faddom server appliance is required. Here we will go over how to set up an IP address for Faddom as well as show how to troubleshoot some common errors in network configuration.

This guide is relevant for the Faddom ova appliance and not for the version that is deployed through the AWS marketplace.


Running the IP configuration script

In order to set an IP address, you must first login to the Faddom server appliance using SSH or through the VMware console. The default user name and password is displayed on the login screen message. It is recommended to change the default password when first logging into the appliance.

After logging in, in the home folder, you will have an IP configuration script. To run it, use the following command:



First, you will get a list of the detected network adapters on the VM, in most cases, you will have only one and you can hit enter to continue.


After selecting the interface, you can enter the details requested. When asked for an IP address, you can enter dhcp instead to switch to using dhcp for the network configuration. Enter values for the IP address, the subnet mask, and the DNS server.


After entering the details, the network configuration will be saved and you should then test to make sure you have access to the server on the new IP address.


DNS Server Considerations

Faddom uses the DNS server in order to translate the IP addresses seen over the network into the host names of your servers. For this, Faddom uses both regular DNS lookup and reverse lookup queries.

In case you have multiple environments with different DNS servers, Faddom can use multiple DNS servers for getting host name information. To do this, you will need to deploy a proxy server for each environment, and configure that proxy server with the correct DNS server. Each proxy server can use a different DNS server, and Faddom will check with all of them when trying to resolve a host name or lookup an IP address.



In some cases, you may get an error when setting an IP address for the VM. In most cases, it will look something like:

Job for network.service failed because the control process exited with error code. 
See "systemctl status network.service" and "journalctl -xe" for details. [FAILED]

In most cases, this will occur when trying to provide an IP address that is already in use on the network. To resolve this, just run the IP configuration script again and provide a free IP address.

You can use the following command to see details on the error message:

systemctl status network.service -l

In other cases, you may not have network access to the VM after setting an IP address. In this case, please make sure that the IP configuration on the VM matches that required for the Network/Port Group that was selected for the VM in the VM settings screen. Also check that the default gateway for the VM is set correctly and that you can ping the gateway from the VM console.





Was this article helpful?
0 out of 0 found this helpful