Network changes

Changing the controller's IP

Note: it's assumed that the controller's IP is in the 'default' network, typically .cluster or any other luna defined network.

When the ip address remains indide the current subnet, the steps below can be followed:

The ip address for the controller can be changed by the operating system's utilities like nmcli or nmtui. After that step, it's important to inform luna about the change by:

luna cluster change --controller <ip>

When a a bigger change is needed, please follow the below steps:

If the network itself has distinctively changed, say subnet mask or address, a few more steps need to be taken. the ip address for the controller can be changed by the operating system's utilities like nmcli or nmtui. Then change the applicable luna network:

luna network change -N a.b.c.d/xx <network>

then change the controller's IP:

luna cluster change --controller <ip>

Changing a DNS forwarder

Change the forwarder in luna:

luna cluster change --forwardserver_ip a.b.c.d

This could be one IPv4 or IPv6 address, or multiple comma separated like "a.b.c.d, e.f.g.h"

Also make sure that the resolv.conf uses the localhost or IP of the controller as primary/sole nameserver. This is the default.