Change the Management IP of a Node Hosting the Veeam Software Appliance VMΒΆ

When an ARTESCA node hosting a Veeam Software Appliance VM moves to a new network, you must update both the node management IP and the network configuration of the VM.

  1. Configure the new IPv4 settings (IP address, subnet, gateway, and DNS servers) on the node network interface, using the sudo nmtui or sudo nmcli command-line tool.

  2. Change the ARTESCA management IP and, if the instance IP changed, add the new instance IP.

    [artesca-os@bootstrap ~]$
    
    sudo ./artesca-installer configure-frontend management
    
  3. Edit the network attachment definition of the Veeam Software Appliance VM.

    [artesca-os@bootstrap ~]$
    
    sudo kubectl --kubeconfig=/etc/kubernetes/admin.conf edit network-attachment-definition -n veeam bridge-external
    

    The config field contains the VM network configuration.

    config: '{ "cniVersion": "0.3.1", "name": "bridge-external", "type": "bridge",
      "bridge": "br-artesca-vm", "ipam": { "type": "host-local",
      "subnet": "192.168.14.0/24", "rangeStart": "192.168.14.242",
      "rangeEnd": "192.168.14.242", "gateway": "192.168.14.254",
      "routes": [ {"dst": "0.0.0.0/0"}, {"dst": "1.1.1.1/32", "gw": "192.168.14.42"} ] } }'
    

    Update the following fields accordingly.

    Field

    New value

    rangeStart and rangeEnd

    The new IP address of the Veeam Software Appliance VM. Set both fields to the same value.

    subnet

    The new subnet of the ARTESCA node, in CIDR notation.

    gateway

    The new gateway of the network.

    gw

    The new management IP of the ARTESCA node.

    Note

    The gw field is the IP address of the ARTESCA node itself, while gateway is the gateway of the network.

  4. Retrieve the name of the Veeam Software Appliance VM.

    [artesca-os@bootstrap ~]$
    
    sudo kubectl --kubeconfig=/etc/kubernetes/admin.conf get vm -n veeam
    
    NAME             AGE   STATUS     READY
    vbr-1234         63d   Running    True
    
  5. Restart the Veeam Software Appliance VM to apply the new network configuration. Replace <VM_NAME> with the name of the VM retrieved in the previous step (for example vbr-1234).

    [artesca-os@bootstrap ~]$
    
    sudo virtctl --kubeconfig=/etc/kubernetes/admin.conf stop <VM_NAME> -n veeam
    sudo virtctl --kubeconfig=/etc/kubernetes/admin.conf start <VM_NAME> -n veeam