Part III. Copying host networks

To save time, you can copy a source host’s network configuration to a target host in the same cluster.

Copying the network configuration includes:

  • Logical networks attached to the host, except the ovirtmgmt management network
  • Bonds attached to interfaces

Limitations

  • Do not copy network configurations that contain static IP addresses. Doing this sets the boot protocol in the target host to none.
  • Copying a configuration to a target host with the same interface names as the source host but different physical network connections produces a wrong configuration.
  • The target host must have an equal or greater number of interfaces than the source host. Otherwise, the operation fails.
  • Copying QoS, DNS, and custom_properties is not supported.
  • Network interface labels are not copied.
Warning

Copying host networks replaces ALL network settings on the target host except its attachment to the ovirtmgmt management network.

Prerequisites

  • The number of NICs on the target host must be equal or greater than those on the source host. Otherwise, the operation fails.
  • The hosts must be in the same cluster.

Procedure

  1. In the Administration Portal, click ComputeHosts.
  2. Select the source host whose configuration you want to copy.
  3. Click Copy Host Networks. This opens the Copy Host Networks window.
  4. Use Target Host to select the host that should receive the configuration. The list only shows hosts that are in the same cluster.
  5. Click Copy Host Networks.
  6. Verify the network settings of the target host

Tips

  • Selecting multiple hosts disables the Copy Host Networks button and context menu.
  • Instead of using the Copy Host Networks button, you can right-click a host and select Copy Host Networks from the context menu.
  • The Copy Host Networks button is also available in any host’s details view.

1. Assigning Additional IPv4 Addresses to a Host Network

A host network, such as the ovirtmgmt management network, is created with only one IP address when initially set up. This means that if a NIC’s configuration file is configured with multiple IP addresses, only the first listed IP address will be assigned to the host network. Additional IP addresses may be required if connecting to storage, or to a server on a separate private subnet using the same NIC.

The vdsm-hook-extra-ipv4-addrs hook allows you to configure additional IPv4 addresses for host networks. For more information about hooks, see Appendix A, VDSM and Hooks.

In the following procedure, the host-specific tasks must be performed on each host for which you want to configure additional IP addresses.

Assigning Additional IPv4 Addresses to a Host Network

  1. On the host that you want to configure additional IPv4 addresses for, install the VDSM hook package. The package is available by default on Red Hat Virtualization Hosts but needs to be installed on Red Hat Enterprise Linux hosts.

    # dnf install vdsm-hook-extra-ipv4-addrs
  2. On the Manager, run the following command to add the key:

    # engine-config -s 'UserDefinedNetworkCustomProperties=ipv4_addrs=.*'
  3. Restart the ovirt-engine service:

    # systemctl restart ovirt-engine.service
  4. In the Administration Portal, click ComputeHosts.
  5. Click the host’s name. This opens the details view.
  6. Click the Network Interfaces tab and click Setup Host Networks.
  7. Edit the host network interface by hovering the cursor over the assigned logical network and clicking the pencil icon.
  8. Select ipv4_addr from the Custom Properties drop-down list and add the additional IP address and prefix (for example 5.5.5.5/24). Multiple IP addresses must be comma-separated.
  9. Click OK to close the Edit Network window.
  10. Click OK to close the Setup Host Networks window.

The additional IP addresses will not be displayed in the Manager, but you can run the command ip addr show on the host to confirm that they have been added.