Important: mind the context labels.
When using whitelisted subnets in Awingu as a security measure, it may be necessary to white list new IP ranges (for instance if there is some form of Network Address Translation (NAT) which also results in client connections coming from different IP addresses).
Preparation in case of a multi node environment
When using a multi node setup, it is required to temporarily revert to a single node setup.
To do so, login as an Awingu administrator on the main node.
Go to System Settings > Global > Service Management.
Make sure this main node has both the frontend and backend roles.
After verifying this, delete the nodes in the Service Management.
In case an internal database is used: verify if the database role is checked.
In case an external database is used: no database role will be checked.
Afterwards, shutdown all nodes except the main appliance. They will not be used anymore.
Follow the procedure below to change the IP address of the main node.
Afterwards, add new nodes with new IP addresses.
Mind that the Awingu version of each node must be the same as the version of the main node.
- Download Awingu appliances (including older versions)
Changing IP address of the Awingu appliance manually
- Open the virtual machine's console on the hypervisor.
- In the console, select Network and adjust the settings to set a static IP address or to configure DHCP.
Mind to alter network adapter settings in the hypervisor if needed, for instance if it's needed to update the VLAN ID.
- Reboot the Awingu appliance through the hypervisor (restart guest).