9.4. Hosts and Networking

1. Click Compute Hosts and select a host.
2. Click Management Refresh Capabilities.

1. Click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click the Network Interfaces tab.
4. Click Setup Host Networks.
5. Optionally, hover your cursor over host network interface to view configuration information provided by the switch.

6. Attach a logical network to a physical host network interface by selecting and dragging the logical network into the Assigned Logical Networks area next to the physical host network interface.

   Note

   If a NIC is connected to more than one logical network, only one of the networks can be non-VLAN. All the other logical networks must be unique VLANs.

7. Configure the logical network:

   1. Hover your cursor over an assigned logical network and click the pencil icon to open the Edit Management Network window.

   2. From the IPv4 tab, select a Boot Protocol from None, DHCP, or Static. If you selected Static, enter the IP, Netmask / Routing Prefix, and the Gateway.

      Note

      For IPv6, only static IPv6 addressing is supported. To configure the logical network, select the IPv6 tab and make the following entries:

      • Set Boot Protocol to Static.
      • For Routing Prefix, enter the length of the prefix using a forward slash and decimals. For example: /48
      • IP: The complete IPv6 address of the host network interface. For example: 2001:db8::1:0:0:6
      • Gateway: The source router’s IPv6 address. For example: 2001:db8::1:0:0:1
      Note

      If you change the host’s management network IP address, you must reinstall the host for the new IP address to be configured.

      Each logical network can have a separate gateway defined from the management network gateway. This ensures traffic that arrives on the logical network will be forwarded using the logical network’s gateway instead of the default gateway used by the management network.

      Important

      Set all hosts in a cluster to use the same IP stack for their management network; either IPv4 or IPv6 only. Dual stack is not supported.

   3. Use the QoS tab to override the default host network quality of service. Select Override QoS and enter the desired values in the following fields:

      • Weighted Share: Signifies how much of the logical link’s capacity a specific network should be allocated, relative to the other networks attached to the same logical link. The exact share depends on the sum of shares of all networks on that link. By default this is a number in the range 1-100.
      • Rate Limit [Mbps]: The maximum bandwidth to be used by a network.
      • Committed Rate [Mbps]: The minimum bandwidth required by a network. The Committed Rate requested is not guaranteed and will vary depending on the network infrastructure and the Committed Rate requested by other networks on the same logical link.

   4. To configure a network bridge, click the Custom Properties tab and select bridge_opts from the drop-down list. Enter a valid key and value with the following syntax: key=value. Separate multiple entries with a whitespace character. The following keys are valid, with the values provided as examples. For more information on these parameters, see Section B.1, “Explanation of bridge_opts Parameters”.

      forward_delay=1500
      gc_timer=3765
      group_addr=1:80:c2:0:0:0
      group_fwd_mask=0x0
      hash_elasticity=4
      hash_max=512
      hello_time=200
      hello_timer=70
      max_age=2000
      multicast_last_member_count=2
      multicast_last_member_interval=100
      multicast_membership_interval=26000
      multicast_querier=0
      multicast_querier_interval=25500
      multicast_query_interval=13000
      multicast_query_response_interval=1000
      multicast_query_use_ifaddr=0
      multicast_router=1
      multicast_snooping=1
      multicast_startup_query_count=2
      multicast_startup_query_interval=3125

   5. To configure ethernet properties, click the Custom Properties tab and select ethtool_opts from the drop-down list. Enter a valid value using the format of the command-line arguments of ethtool. For example:

      --coalesce em1 rx-usecs 14 sample-interval 3 --offload em2 rx on lro on tso off --change em1 speed 1000 duplex half

      This field can accept wildcards. For example, to apply the same option to all of this network’s interfaces, use:

      --coalesce * rx-usecs 14 sample-interval 3

      The ethtool_opts option is not available by default; you need to add it using the engine configuration tool. See Section B.2, “How to Set Up Red Hat Virtualization Manager to Use Ethtool” for more information. For more information on ethtool properties, see the manual page by typing man ethtool in the command line.

   6. To configure Fibre Channel over Ethernet (FCoE), click the Custom Properties tab and select fcoe from the drop-down list. Enter a valid key and value with the following syntax: key=value. At least enable=yes is required. You can also add dcb= and auto_vlan=[yes|no]. Separate multiple entries with a whitespace character. The fcoe option is not available by default; you need to add it using the engine configuration tool. See Section B.3, “How to Set Up Red Hat Virtualization Manager to Use FCoE” for more information.

      Note

      A separate, dedicated logical network is recommended for use with FCoE.

   7. To change the default network used by the host from the management network (ovirtmgmt) to a non-management network, configure the non-management network’s default route. See Section 9.1.5, “Configuring a Non-Management Logical Network as the Default Route” for more information.
   8. If your logical network definition is not synchronized with the network configuration on the host, select the Sync network check box. For more information about unsynchronized hosts and how to synchronize them, see Section 9.4.3, “Synchronizing Host Networks”.
8. Select the Verify connectivity between Host and Engine check box to check network connectivity. This action only works if the host is in maintenance mode.
9. Click OK.

1. Use the Administration Portal to make changes rather than making changes locally on the host.
2. Edit VLAN settings according to the instructions in Section 9.4.4, “Editing a Host’s VLAN Settings”.

Synchronizing Host Networks on the Logical Network Level

1. Click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click the Network Interfaces tab.
4. Click Setup Host Networks.
5. Hover your cursor over the unsynchronized network and click the pencil icon to open the Edit Network window.
6. Select the Sync network check box.
7. Click OK to save the network change.
8. Click OK to close the Setup Host Networks window.

1. Put the host in maintenance mode.
2. Manually remove the management network from the host. This will make the host reachable over the new VLAN.
3. Add the host to the cluster. Virtual machines that are not connected directly to the management network can be migrated between hosts safely.

1. Click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click the Network Interfaces tab.
4. Click Setup Host Networks.
5. Drag your VLAN-tagged logical networks into the Assigned Logical Networks area next to the physical network interface. The physical network interface can have multiple logical networks assigned due to the VLAN tagging.

6. Edit the logical networks:

   1. Hover your cursor over an assigned logical network and click the pencil icon.
   2. If your logical network definition is not synchronized with the network configuration on the host, select the Sync network check box.

   3. Select a Boot Protocol:

      • None
      • DHCP
      • Static
   4. Provide the IP and Subnet Mask.
   5. Click OK.
7. Select the Verify connectivity between Host and Engine check box to run a network check; this will only work if the host is in maintenance mode.
8. Click OK.

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.

   # yum 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 Compute Hosts.
5. Click the host’s name to open 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.

1. Click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click the Network Interfaces tab.
4. Click Setup Host Networks.
5. Click Labels and right-click [New Label]. Select a physical network interface to label.
6. Enter a name for the network label in the Label text field.
7. Click OK.

Procedure

1. Configure the username and password in /etc/ovirt-lldp-labeler/conf.d/ovirt-lldp-credentials.conf:

   • username - the username of the Manager administrator. The default is admin@internal.
   • password - the password of the Manager administrator. The default is 123456.

2. Configure the LLDP Labeler service by updating the following values in etc/ovirt-lldp-labeler/conf.d/ovirt-lldp-credentials.conf:

   • clusters - a comma-separated list of clusters on which the service should run. Wildcards are supported. For example, Cluster* defines LLDP Labeler to run on all clusters starting with word Cluster. To run the service on all clusters in the data center, type *. The default is Def*.
   • api_url - the full URL of the Manager’s API. The default is https://Manager_FQDN/ovirt-engine/api
   • ca_file - the path to the custom CA certificate file. Leave this value empty if you do not use custom certificates. The default is empty.
   • auto_bonding - enables LLDP Labeler’s bonding capabilities. The default is true.
   • auto_labeling - enables LLDP Labeler’s labeling capabilities. The default is true.
3. Optionally, you can configure the service to run at a different time interval by changing the value of OnUnitActiveSec in etc/ovirt-lldp-labeler/conf.d/ovirt-lldp-labeler.timer. The default is 1h.

4. Configure the service to start now and at boot by entering the following command:

   # systemctl enable --now ovirt-lldp-labeler

   To invoke the service manually, enter the following command:

   # /usr/bin/python /usr/share/ovirt-lldp-labeler/ovirt_lldp_labeler_cli.py

1. Place the host into maintenance mode so the virtual machines are live migrated to another host. See Section 10.5.15, “Moving a Host to Maintenance Mode” for more information. Alternatively, manually shut down or migrate all the virtual machines to another host. See Manually Migrating Virtual Machines in the Virtual Machine Management Guide for more information.
2. Click Remove, and click OK to remove the host from the Administration Portal.

3. Use the hostnamectl tool to update the host name. For more options, see Configure Host Names in the Red Hat Enterprise Linux 7 Networking Guide.

   # hostnamectl set-hostname NEW_FQDN

4. Reboot the host.
5. Re-register the host with the Manager. See Section 10.5.1, “Adding Standard Hosts to the Red Hat Virtualization Manager” for more information.