2.4. Logical Networks

Procedure

1. Click Compute Data Centers or Compute Clusters.
2. Click the data center or cluster name. The Details view opens.
3. Click the Logical Networks tab.

4. Open the New Logical Network window:

   • From a data center details view, click New.
   • From a cluster details view, click Add Network.
5. Enter a Name, Description, and Comment for the logical network.
6. Optional: Enable Enable VLAN tagging.
7. Optional: Disable VM Network.

8. Optional: Select the Create on external provider checkbox. This disables the network label and the VM network. See External Providers for details.

   1. Select the External Provider. The External Provider list does not include external providers that are in read-only mode.
   2. To create an internal, isolated network, select ovirt-provider-ovn on the External Provider list and leave Connect to physical network cleared.
9. Enter a new label or select an existing label for the logical network in the Network Label text field.

10. For MTU, either select Default (1500) or select Custom and specify a custom value.

    Important

    After you create a network on an external provider, you cannot change the network’s MTU settings.

    Important

    If you change the network’s MTU settings, you must propagate this change to the running virtual machines on the network: Hot unplug and replug every virtual machine’s vNIC that should apply the MTU setting, or restart the virtual machines. Otherwise, these interfaces fail when the virtual machine migrates to another host. For more information, see After network MTU change, some VMs and bridges have the old MTU and seeing packet drops and BZ#1766414.

11. If you selected ovirt-provider-ovn from the External Provider drop-down list, define whether the network should implement Security Groups. See Logical Network General Settings Explained for details.
12. From the Cluster tab, select the clusters to which the network will be assigned. You can also specify whether the logical network will be a required network.
13. If the Create on external provider checkbox is selected, the Subnet tab is visible. From the Subnet tab, select the Create subnet and enter a Name, CIDR, and Gateway address, and select an IP Version for the subnet that the logical network will provide. You can also add DNS servers as required.
14. From the vNIC Profiles tab, add vNIC profiles to the logical network as required.
15. Click OK.

Procedure

1. Click Compute Data Centers.
2. Click the data center’s name. This opens the details view.
3. Click the Logical Networks tab and select a logical network.
4. Click Edit.

5. Edit the necessary settings.

   Note

   You can edit the name of a new or existing network, with the exception of the default network, without having to stop the virtual machines.

6. Click OK.

Procedure

1. Click Compute Data Centers.
2. Click a data center’s name. This opens the details view.
3. Click the Logical Networks tab to list the logical networks in the data center.
4. Select a logical network and click Remove.
5. Optionally, select the Remove external network(s) from the provider(s) as well check box to remove the logical network both from the Manager and from the external provider if the network is provided by an external provider. The check box is grayed out if the external provider is in read-only mode.
6. Click OK.

1. Click Network Networks.
2. Click the name of the non-management logical network to configure as the default route to access its details.
3. Click the Clusters tab.
4. Click Manage Network. This opens the Manage Network window.
5. Select the Default Route checkbox for the appropriate cluster(s).
6. Click OK.

Procedure

1. Connect to the host you want to configure.

2. On the host, create a static_route.yml file, with the following example content:

   routes:
     config:
     - destination: 192.168.123.0/24
       next-hop-address: 192.168.178.1
       next-hop-interface: eth1

3. Replace the example values shown with real values for your network.

4. To route your traffic to a secondary added network, use next-hop-interface to specify an interface or network name.

   • To use a non-virtual machine network, specify an interface such as eth1.
   • To use a virtual machine network, specify a network name that is also the bridge name such as net1.

5. Run this command:

   $ nmstatectl set static_route.yml

Procedure

1. Connect to the host you want to reconfigure.
2. On the host, edit the static_route.yml file.
3. Insert a line state: absent as shown in the following example.

4. Add the value of next-hop-interface between the brackets of interfaces: []. The result should look similar to the example shown here.

   routes:
     config:
     - destination: 192.168.123.0/24
       next-hop-address: 192.168.178.
       next-hop-interface: eth1
       state: absent
   interfaces: [{“name”: eth1}]

5. Run this command:

   $ nmstatectl set static_route.yml

Procedure

1. Click Compute Hosts.
2. Click the host’s name. This opens the details view.
3. Click the Network Interfaces tab to list the network interfaces attached to the host, and their configurations.
4. Click Setup Host Networks.
5. Hover your cursor over an assigned logical network and click the pencil icon. This opens the Edit Management Network window.

Procedure

1. Click Compute Clusters.
2. Click the cluster’s name. This opens the details view.
3. Click the Logical Networks tab.
4. Click Manage Networks.
5. Select the appropriate check boxes and radio buttons.
6. Click OK.

Procedure

1. Click Compute Hosts.
2. Click the name of an SR-IOV-capable host. This opens the details view.
3. Click the Network Interfaces tab.
4. Click Setup Host Networks.
5. Select an SR-IOV-capable NIC, marked with a , and click the pencil icon.

6. Optional: To change the number of virtual functions, click the Number of VFs setting drop-down button and edit the Number of VFs text field.

   Important

   Changing the number of VFs deletes all previous VFs on the network interface before creating the new VFs. This includes any VFs that have virtual machines directly attached.

7. Optional: To limit which virtual networks have access virtual functions, select Specific networks.

   1. Select the networks that should have access to the VF, or use Labels to select networks based on their network labels.
8. Click OK.
9. In the Setup Host Networks window, click OK.

Procedure

1. Click Network Networks.
2. Click the logical network’s name. This opens the details view.
3. Click the vNIC Profiles tab.
4. Click New or Edit.
5. Enter the Name and Description of the profile.
6. Select the relevant Quality of Service policy from the QoS list.
7. Select a Network Filter from the drop-down list to manage the traffic of network packets to and from virtual machines. For more information on network filters, see Applying network filtering in the Red Hat Enterprise Linux Virtualization Deployment and Administration Guide.
8. Select the Passthrough check box to enable passthrough of the vNIC and allow direct device assignment of a virtual function. Enabling the passthrough property will disable QoS, network filtering, and port mirroring as these are not compatible. For more information on passthrough, see Enabling Passthrough on a vNIC Profile.
9. If Passthrough is selected, optionally deselect the Migratable check box to disable migration for vNICs using this profile. If you keep this check box selected, see Additional Prerequisites for Virtual Machines with SR-IOV-Enabled vNICs in the Virtual Machine Management Guide.
10. Use the Port Mirroring and Allow all users to use this Profile check boxes to toggle these options.
11. Select a custom property from the custom properties list, which displays Please select a key…​ by default. Use the + and - buttons to add or remove custom properties.
12. Click OK.

Procedure

1. Click Network Networks.
2. Click the logical network’s name. This opens the details view.
3. Click the vNIC Profiles tab to list all vNIC profiles for that logical network.
4. Click New.
5. Enter the Name and Description of the profile.
6. Select the Passthrough check box.
7. Optionally deselect the Migratable check box to disable migration for vNICs using this profile. If you keep this check box selected, see Additional Prerequisites for Virtual Machines with SR-IOV-Enabled vNICs in the Virtual Machine Management Guide.
8. If necessary, select a custom property from the custom properties list, which displays Please select a key…​ by default. Use the + and - buttons to add or remove custom properties.
9. Click OK.

Procedure

1. In the Administration Portal, go to Network VNIC profiles, select the vNIC profile, click Edit and select a Failover vNIC profile from the drop down list.
2. Click OK to save the profile settings.

Procedure

1. Click Network Networks.
2. Click the logical network’s name. This opens the details view.
3. Click the vNIC Profiles tab to display available vNIC profiles.
4. Select one or more profiles and click Remove.
5. Click OK.

Procedure

1. Click Network Networks.
2. Click the logical network’s name. This opens the details view.
3. Click the vNIC Profiles tab.
4. Click New, or select an existing vNIC profile and click Edit.
5. From the custom properties drop-down list, select SecurityGroups. Leaving the custom property drop-down blank applies the default security settings, which permit all outbound traffic and intercommunication but deny all inbound traffic from outside of the default security group. Note that removing the SecurityGroups property later will not affect the applied security group.
6. In the text field, enter the ID of the security group to attach to the vNIC profile.
7. Click OK.

1. Click Network vNIC Profile.
2. Click the vNIC profile’s name. This opens the details view.
3. Click the Permissions tab to show the current user permissions for the profile.
4. Click Add or Remove to change user permissions for the vNIC profile.
5. In the Add Permissions to User window, click My Groups to display your user groups. You can use this option to grant permissions to other users in your groups.

Procedure

1. Click Network Networks.
2. Click Import.
3. From the Network Provider drop-down list, select an external provider. The networks offered by that provider are automatically discovered and listed in the Provider Networks list.
4. Using the check boxes, select the networks to import in the Provider Networks list and click the down arrow to move those networks into the Networks to Import list.
5. You can customize the name of the network that you are importing. To customize the name, click the network’s name in the Name column, and change the text.
6. From the Data Center drop-down list, select the data center into which the networks will be imported.
7. Optional: Clear the Allow All check box to prevent that network from being available to all users.
8. Click Import.

Procedure

1. Click Network Networks.
2. Click the logical network’s name. This opens the details view.
3. Click the Subnets tab.
4. Click New.
5. Enter a Name and CIDR for the new subnet.
6. From the IP Version drop-down list, select either IPv4 or IPv6.
7. Click OK.

Procedure

1. Click Network Networks.
2. Click the logical network’s name. This opens the details view.
3. Click the Subnets tab.
4. Select a subnet and click Remove.
5. Click OK.

Procedure

1. Click Compute Clusters.
2. Click the cluster name. This opens the details view.
3. Click the Logical Networks tab.
4. Click Add Network and define the properties, ensuring that you select ovirt-provider-ovn from the External Providers drop-down list. For more information, see Creating a new logical network in a data center or cluster.
5. Select Enabled from the Security Group drop-down list. For more details see Logical Network General Settings Explained.
6. Click OK.
7. Create security groups using either OpenStack Networking API v2.0 or Ansible.
8. Create security group rules using either OpenStack Networking API v2.0 or Ansible.
9. Update the ports with the security groups that you defined using either OpenStack Networking API v2.0 or Ansible.
10. Optional. Define whether the security feature is enabled at the port level. Currently, this is only possible using the OpenStack Networking API. If the port_security_enabled attribute is not set, it will default to the value specified in the network to which it belongs.

Procedure

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

Procedure

1. Click Compute Hosts.
2. Click the host’s name. This opens 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. This opens 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 Explanation of bridge_opts Parameters.

      forward_delay=1500
      group_addr=1:80:c2:0:0:0
      group_fwd_mask=0x0
      hash_max=512
      hello_time=200
      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 wild cards. 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 How to Set Up 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=[yes|no] 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 How to Set Up 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 Configuring a 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 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 Editing VLAN Settings.

Synchronizing Host Networks on the Logical Network Level

1. Click Compute Hosts.
2. Click the host’s name. This opens 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. This opens 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.

Procedure

1. Click Compute Hosts.
2. Click the host’s name. This opens 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.

Procedure

1. On the host that you want to configure additional IPv4 addresses for, install the VDSM hook package. The package needs to be installed manually on Red Hat Enterprise Linux hosts and Red Hat Virtualization 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 Compute Hosts.
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.

Procedure

1. Click Compute Hosts.
2. Click the host’s name. This opens 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. Place the host into maintenance mode so the virtual machines are live migrated to another host. See 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 Adding standard hosts to the Manager for more information.

Procedure

1. Click Compute Hosts.
2. Click the host’s name. This opens the details view.
3. Click the Network Interfaces tab to list the physical network interfaces attached to the host.
4. Click Setup Host Networks.
5. Check the switch configuration. If the switch has been configured to provide Link Layer Discovery Protocol (LLDP) information, hover your cursor over a physical NIC to view the switch port’s aggregation configuration.

6. Drag and drop a NIC onto another NIC or onto a bond.

   Note

   Two NICs form a new bond. A NIC and a bond adds the NIC to the existing bond.

   If the logical networks are incompatible, the bonding operation is blocked.

7. Select the Bond Name and Bonding Mode from the drop-down menus. See Bonding Modes for details.

   If you select the Custom bonding mode, you can enter bonding options in the text field, as in the following examples:

   • If your environment does not report link states with ethtool, you can set ARP monitoring by entering mode=1 arp_interval=1 arp_ip_target=192.168.0.2.

   • You can designate a NIC with higher throughput as the primary interface by entering mode=1 primary=eth0.

     For a comprehensive list of bonding options and their descriptions, see the Linux Ethernet Bonding Driver HOWTO on Kernel.org.

8. Click OK.

9. Attach a logical network to the new bond and configure it. See Editing Host Network Interfaces and Assigning Logical Networks to Hosts for instructions.

   Note

   You cannot attach a logical network directly to an individual NIC in the bond.

10. Optionally, you can select Verify connectivity between Host and Engine if the host is in maintenance mode.
11. Click OK.