Updating Network Settings

If you do not want the foundation server to obtain network settings automatically from a DHCP server, you can configure them manually in the VM console:

In a web browser, navigate to the virtual IP address of the cluster. You can also use the IP address or the hostname of a Controller VM in the cluster.
In the username and password fields, enter credentials of a user account with Prism Element administrative privileges, and press [Enter] on the keyboard.
From the main menu, navigate to the VMs dashboard, select Foundation for Mine with Veeam VM and click the Launch Console button to open the VM console.
To log in to the VM console, specify credentials that you use to access the Mine console.
Open the network settings file using the following command:

$ sudo nano /etc/netplan/eth0.yaml

Replace the default network settings with your settings: enter a static IP address to assign to the foundation server and the subnet mask, a default gateway IP address, and IP addresses of the primary and alternate DNS servers. For example, to assign the IP address 192.168.148.132 with the gateway server 192.168.144.1 and DNS servers as 192.168.128.101 and 192.168.0.101, update the settings in the following way:

network:

version: 2

renderer: networkd

ethernets:

eth0:

dhcp4: no

addresses: [192.168.148.132/20]

routes:

- to: default

via: 192.168.144.1

nameservers:

addresses: [192.168.128.101,192.168.0.101]

Important

The network configuration yaml file is sensitive to the number of line indents (spaces) that define the structure of the settings. If the number of indents is incorrect, network configuration will become invalid. In this case, an error message will be displayed, for example:

Invalid YAML at //etc/netplan/eth0.yaml line 7 column 6: did not find expected key

Apply the updated configuration using the following command:

$ sudo netplan apply

Tip

To troubleshoot issues related to the updated network settings, use the following command:

$ sudo netplan --debug apply

If you have already deployed Mine with Veeam, reboot the foundation server and redeploy Mine dashboard.