Administration Guide

Procedure 2.1. Creating a Storage Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click QoS in the details pane.
3. Click Storage.
4. Click New.
5. Enter a name for the quality of service entry in the QoS Name field.
6. Enter a description for the quality of service entry in the Description field.
7. Specify the throughput quality of service:
   1. Select the Throughput check box.
   2. Enter the maximum permitted total throughput in the Total field.
   3. Enter the maximum permitted throughput for read operations in the Read field.
   4. Enter the maximum permitted throughput for write operations in the Write field.
8. Specify the input and output quality of service:
   1. Select the IOps check box.
   2. Enter the maximum permitted number of input and output operations per second in the Total field.
   3. Enter the maximum permitted number of input operations per second in the Read field.
   4. Enter the maximum permitted number of output operations per second in the Write field.
9. Click OK.

Procedure 2.2. Removing a Storage Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click QoS in the details pane.
3. Click Storage.
4. Select the storage quality of service entry to remove.
5. Click Remove.
6. Click OK when prompted.

Procedure 2.3. Creating a Virtual Machine Network Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click the QoS tab in the details pane.
3. Click VM Network.
4. Click New.
5. Enter a name for the virtual machine network quality of service entry in the Name field.
6. Enter the limits for the Inbound and Outbound network traffic.
7. Click OK.

Procedure 2.4. Removing a Virtual Machine Network Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click the QoS tab in the details pane.
3. Click VM Network.
4. Select the virtual machine network quality of service entry to remove.
5. Click Remove.
6. Click OK when prompted.

Procedure 2.5. Creating a Host Network Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click QoS in the details pane.
3. Click Host Network.
4. Click New.
5. Enter a name for the quality of service entry in the QoS Name field.
6. Enter a description for the quality of service entry in the Description field.
7. Enter the desired values for Weighted Share, Rate Limit [Mbps], and Committed Rate [Mbps].
8. Click OK.

Procedure 2.6. Removing a Host Network Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click the QoS tab in the details pane.
3. Click Host Network.
4. Select the network quality of service entry to remove.
5. Click Remove.
6. Click OK when prompted.

Procedure 2.7. Creating a CPU Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click QoS in the details pane.
3. Click CPU.
4. Click New.
5. Enter a name for the quality of service entry in the QoS Name field.
6. Enter a description for the quality of service entry in the Description field.
7. Enter the maximum processing capability the quality of service entry permits in the Limit field, in percentage. Do not include the % symbol.
8. Click OK.

Procedure 2.8. Removing a CPU Quality of Service Entry

1. Click the Data Centers resource tab and select a data center.
2. Click QoS in the details pane.
3. Click CPU.
4. Select the CPU quality of service entry to remove.
5. Click Remove.
6. Click OK when prompted.

Procedure 3.1. Creating a New Data Center

1. Select the Data Centers resource tab to list all data centers in the results list.
2. Click New to open the New Data Center window.
3. Enter the Name and Description of the data center.
4. Select the storage Type, Compatibility Version, and Quota Mode of the data center from the drop-down menus.
5. Optionally, change the MAC address pool for the data center. The default MAC address pool is preselected by default. For more information on creating MAC address pools see Section 1.1.5, “MAC Address Pools”.
   1. Click the MAC Address Pool tab.
   2. Select the required MAC address pool from the MAC Address Pool drop-down list.
6. Click OK to create the data center and open the New Data Center - Guide Me window.
7. The Guide Me window lists the entities that need to be configured for the data center. Configure these entities or postpone configuration by clicking the Configure Later button; configuration can be resumed by selecting the data center and clicking the Guide Me button.

Procedure 3.2. Re-Initializing a Data Center

1. Click the Data Centers resource tab and select the data center to re-initialize.
2. Ensure that any storage domains attached to the data center are in maintenance mode.
3. Right-click the data center and select Re-Initialize Data Center from the drop-down menu to open the Data Center Re-Initialize window.
4. The Data Center Re-Initialize window lists all available (detached; in maintenance mode) storage domains. Click the radio button for the storage domain you are adding to the data center.
5. Select the Approve operation check box.
6. Click OK to close the window and re-initialize the data center.

Procedure 3.3. Removing a Data Center

1. Ensure the storage domains attached to the data center is in maintenance mode.
2. Click the Data Centers resource tab and select the data center to remove.
3. Click Remove to open the Remove Data Center(s) confirmation window.
4. Click OK.

Procedure 3.4. Force Removing a Data Center

1. Click the Data Centers resource tab and select the data center to remove.
2. Click Force Remove to open the Force Remove Data Center confirmation window.
3. Select the Approve operation check box.
4. Click OK

Procedure 3.5. Changing the Data Center Compatibility Version

1. From the Administration Portal, click the Data Centers tab.
2. Select the data center to change from the list displayed.
3. Click Edit.
4. Change the Compatibility Version to the desired value.
5. Click OK to open the Change Data Center Compatibility Version confirmation window.
6. Click OK to confirm.

Procedure 3.6. Attaching an Existing Data Domain to a Data Center

1. Click the Data Centers resource tab and select the appropriate data center.
2. Select the Storage tab in the details pane to list the storage domains already attached to the data center.
3. Click Attach Data to open the Attach Storage window.
4. Select the check box for the data domain to attach to the data center. You can select multiple check boxes to attach multiple data domains.
5. Click OK.

Procedure 3.7. Attaching an Existing ISO Domain to a Data Center

1. Click the Data Centers resource tab and select the appropriate data center.
2. Select the Storage tab in the details pane to list the storage domains already attached to the data center.
3. Click Attach ISO to open the Attach ISO Library window.
4. Click the radio button for the appropriate ISO domain.
5. Click OK.

Procedure 3.8. Attaching an Existing Export Domain to a Data Center

1. Click the Data Centers resource tab and select the appropriate data center.
2. Select the Storage tab in the details pane to list the storage domains already attached to the data center.
3. Click Attach Export to open the Attach Export Domain window.
4. Click the radio button for the appropriate Export domain.
5. Click OK.

Procedure 3.9. Detaching a Storage Domain from a Data Center

1. Click the Data Centers resource tab and select the appropriate data center.
2. Select the Storage tab in the details pane to list the storage domains attached to the data center.
3. Select the storage domain to detach. If the storage domain is Active, click Maintenance to open the Maintenance Storage Domain(s) confirmation window.
4. Click OK to initiate maintenance mode.
5. Click Detach to open the Detach Storage confirmation window.
6. Click OK.

Procedure 3.10. Assigning a Role to a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Click Add.
4. Enter the name or user name of an existing user into the Search text box and click Go. Select a user from the resulting list of possible matches.
5. Select a role from the Role to Assign: drop-down list.
6. Click OK.

Procedure 3.11. Removing a Role from a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Select the user to remove from the resource.
4. Click Remove. The Remove Permission window opens to confirm permissions removal.
5. Click OK.

Procedure 4.1. Creating a New Cluster

1. Select the Clusters resource tab.
2. Click New.
3. Select the Data Center the cluster will belong to from the drop-down list.
4. Enter the Name and Description of the cluster.
5. Select a network from the Management Network drop-down list to assign the management network role.
6. Select the CPU Architecture and CPU Type from the drop-down lists. It is important to match the CPU processor family with the minimum CPU processor type of the hosts you intend to attach to the cluster, otherwise the host will be non-operational.

   Note

   For both Intel and AMD CPU types, the listed CPU models are in logical order from the oldest to the newest. If your cluster includes hosts with different CPU models, select the oldest CPU model. For more information on each CPU model, see https://access.redhat.com/solutions/634853.
7. Select the Compatibility Version of the cluster from the drop-down list.
8. Select either the Enable Virt Service or Enable Gluster Service radio button to define whether the cluster will be populated with virtual machine hosts or with Gluster-enabled nodes. Note that you cannot add Red Hat Enterprise Virtualization Hypervisor hosts to a Gluster-enabled cluster.
9. Optionally select the Enable to set VM maintenance reason check box to enable an optional reason field when a virtual machine is shut down from the Manager, allowing the administrator to provide an explanation for the maintenance.
10. Optionally select the Enable to set Host maintenance reason check box to enable an optional reason field when a host is placed into maintenance mode from the Manager, allowing the administrator to provide an explanation for the maintenance.
11. Select either the /dev/random source (Linux-provided device) or /dev/hwrng source (external hardware device) check box to specify the random number generator device that all hosts in the cluster will use.
12. Click the Optimization tab to select the memory page sharing threshold for the cluster, and optionally enable CPU thread handling and memory ballooning on the hosts in the cluster.
13. Click the Resilience Policy tab to select the virtual machine migration policy.
14. Click the Scheduling Policy tab to optionally configure a scheduling policy, configure scheduler optimization settings, enable trusted service for hosts in the cluster, enable HA Reservation, and add a custom serial number policy.
15. Click the Console tab to optionally override the global SPICE proxy, if any, and specify the address of a SPICE proxy for hosts in the cluster.
16. Click the Fencing policy tab to enable or disable fencing in the cluster, and select fencing options.
17. Click OK to create the cluster and open the New Cluster - Guide Me window.
18. The Guide Me window lists the entities that need to be configured for the cluster. Configure these entities or postpone configuration by clicking the Configure Later button; configuration can be resumed by selecting the cluster and clicking the Guide Me button.

Procedure 4.2. Editing a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click Edit to open the Edit window.
3. Change the necessary properties and click OK.

Procedure 4.3. Setting Load and Power Management Policies for Hosts

1. Use the resource tabs, tree mode, or the search function to find and select the cluster in the results list.
2. Click Edit to open the Edit Cluster window.
   

   Figure 4.4. Edit Scheduling Policy

3. Select one of the following policies:
   • none
   • vm_evenly_distributed
     1. Set the maximum number of virtual machines that can run on each host in the HighVmCount field.
     2. Define the maximum acceptable difference between the number of virtual machines on the most highly-utilized host and the number of virtual machines on the least-utilized host in the MigrationThreshold field.
     3. Define the number of slots for virtual machines to be reserved on SPM hosts in the SpmVmGrace field.
   • evenly_distributed
     1. Set the time (in minutes) that a host can run a CPU load outside of the defined utilization values before the scheduling policy takes action in the CpuOverCommitDurationMinutes field.
     2. Enter the CPU utilization percentage at which virtual machines start migrating to other hosts in the HighUtilization field.
     3. Enter the minimum required free memory in MB at which virtual machines start migrating to other hosts in the MinFreeMemoryForUnderUtilized.
     4. Enter the maximum required free memory in MB at which virtual machines start migrating to other hosts in the MaxFreeMemoryForOverUtilized.
   • power_saving
     1. Set the time (in minutes) that a host can run a CPU load outside of the defined utilization values before the scheduling policy takes action in the CpuOverCommitDurationMinutes field.
     2. Enter the CPU utilization percentage below which the host will be considered under-utilized in the LowUtilization field.
     3. Enter the CPU utilization percentage at which virtual machines start migrating to other hosts in the HighUtilization field.
     4. Enter the minimum required free memory in MB at which virtual machines start migrating to other hosts in the MinFreeMemoryForUnderUtilized.
     5. Enter the maximum required free memory in MB at which virtual machines start migrating to other hosts in the MaxFreeMemoryForOverUtilized.
4. Choose one of the following as the Scheduler Optimization for the cluster:
   • Select Optimize for Utilization to include weight modules in scheduling to allow best selection.
   • Select Optimize for Speed to skip host weighting in cases where there are more than ten pending requests.
5. If you are using an OpenAttestation server to verify your hosts, and have set up the server's details using the engine-config tool, select the Enable Trusted Service check box.
6. Optionally select the Enable HA Reservation check box to enable the Manager to monitor cluster capacity for highly available virtual machines.
7. Optionally select the Provide custom serial number policy check box to specify a serial number policy for the virtual machines in the cluster, and then select one of the following options:
   • Select Host ID to set the host's UUID as the virtual machine's serial number.
   • Select Vm ID to set the virtual machine's UUID as its serial number.
   • Select Custom serial number, and then specify a custom serial number in the text field.
8. Click OK.

Procedure 4.4. Synchronizing MoM Policy on a Host

1. Click the Clusters tab and select the cluster to which the host belongs.
2. Click the Hosts tab in the details pane and select the host that requires an updated MoM policy.
3. Click Sync MoM Policy.

Procedure 4.7. Importing an Existing Red Hat Gluster Storage Cluster to Red Hat Enterprise Virtualization Manager

1. Select the Clusters resource tab to list all clusters in the results list.
2. Click New to open the New Cluster window.
3. Select the Data Center the cluster will belong to from the drop-down menu.
4. Enter the Name and Description of the cluster.
5. Select the Enable Gluster Service radio button and the Import existing gluster configuration check box.
   The Import existing gluster configuration field is displayed only if you select Enable Gluster Service radio button.
6. In the Address field, enter the hostname or IP address of any server in the cluster.
   The host Fingerprint displays to ensure you are connecting with the correct host. If a host is unreachable or if there is a network error, an error Error in fetching fingerprint displays in the Fingerprint field.
7. Enter the Root Password for the server, and click OK.
8. The Add Hosts window opens, and a list of hosts that are a part of the cluster displays.
9. For each host, enter the Name and the Root Password.
10. If you wish to use the same password for all hosts, select the Use a Common Password check box to enter the password in the provided text field.
    Click Apply to set the entered password all hosts.
    Make sure the fingerprints are valid and submit your changes by clicking OK.

Procedure 4.8. Removing a Cluster

1. Use the resource tabs, tree mode, or the search function to find and select the cluster in the results list.
2. Ensure there are no hosts in the cluster.
3. Click Remove to open the Remove Cluster(s) confirmation window.
4. Click OK

Procedure 4.9. Changing the Cluster Compatibility Version

1. From the Administration Portal, click the Clusters tab.
2. Select the cluster to change from the list displayed.
3. Click Edit.
4. Change the Compatibility Version to the desired value.
5. Click OK to open the Change Cluster Compatibility Version confirmation window.
6. Click OK to confirm.

Procedure 4.10. Assigning a Role to a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Click Add.
4. Enter the name or user name of an existing user into the Search text box and click Go. Select a user from the resulting list of possible matches.
5. Select a role from the Role to Assign: drop-down list.
6. Click OK.

Procedure 4.11. Removing a Role from a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Select the user to remove from the resource.
4. Click Remove. The Remove Permission window opens to confirm permissions removal.
5. Click OK.

Procedure 5.1. Creating a New Logical Network in a Data Center or Cluster

1. Click the Data Centers or Clusters resource tabs, and select a data center or cluster in the results list.
2. Click the Logical Networks tab of the details pane to list the existing logical networks.
3. • From the Data Centers details pane, click New to open the New Logical Network window.
   • From the Clusters details pane, click Add Network to open the New Logical Network window.
4. Enter a Name, Description, and Comment for the logical network.
5. Optionally select the Create on external provider check box. Select the External Provider from the drop-down list and provide the IP address of the Physical Network.
   If Create on external provider is selected, the Network Label, VM Network, and MTU options are disabled.
6. Enter a new label or select an existing label for the logical network in the Network Label text field.
7. Optionally enable Enable VLAN tagging.
8. Optionally disable VM Network.
9. Set the MTU value to Default (1500) or Custom.
10. 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.
11. If Create on external provider is selected, the Subnet tab will be 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.
12. From the vNIC Profiles tab, add vNIC profiles to the logical network as required.
13. Click OK.

Procedure 5.2. Editing a Logical Network

1. Click the Data Centers resource tab, and select the data center of the logical network in the results list.
2. Click the Logical Networks tab in the details pane to list the logical networks in the data center.
3. Select a logical network and click Edit to open the Edit Logical Network window.
4. Edit the necessary settings.
5. Click OK to save the changes.

Procedure 5.3. Removing Logical Networks

1. Click the Data Centers resource tab, and select the data center of the logical network in the results list.
2. Click the Logical Networks tab in the details pane to list the logical networks in the data center.
3. Select a logical network and click Remove to open the Remove Logical Network(s) window.
4. 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.
5. Click OK.

Procedure 5.4. Viewing or Editing the Gateway for a Logical Network

1. Click the Hosts resource tab, and select the desired host.
2. Click the Network Interfaces tab in the details pane to list the network interfaces attached to the host and their configurations.
3. Click the Setup Host Networks button to open the Setup Host Networks window.
4. Hover your cursor over an assigned logical network and click the pencil icon to open the Edit Management Network window.

Procedure 5.5. Specifying Traffic Types for Logical Networks

1. Click the Clusters resource tab, and select a cluster from the results list.
2. Select the Logical Networks tab in the details pane to list the logical networks assigned to the cluster.
3. Click Manage Networks to open the Manage Networks window.
   

   Figure 5.1. Manage Networks

4. Select appropriate check boxes.
5. Click OK to save the changes and close the window.

Procedure 5.6. Editing the Virtual Function Configuration on a NIC

1. Select an SR-IOV-capable host and click the Network Interfaces tab in the details pane.
2. Click Setup Host Networks to open the Setup Host Networks window.
3. Select an SR-IOV-capable NIC, marked with a , and click the pencil icon to open the Edit Virtual Functions (SR-IOV) configuration of NIC window.
4. To edit 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 will delete all previous VFs on the network interface before creating new VFs. This includes any VFs that have virtual machines directly attached.
5. The All Networks check box is selected by default, allowing all networks to access the virtual functions. To specify the virtual networks allowed to access the virtual functions, select the Specific networks radio button to list all networks. You can then either select the check box for desired networks, or you can use the Labels text field to automatically select networks based on one or more network labels.
6. Click OK to close the window. Note that the configuration changes will not take effect until you click the OK button in the Setup Host Networks window.

Procedure 5.7. Creating or editing a vNIC Profile

1. Click the Networks resource tab, and select a logical network in the results list.
2. Select the vNIC Profiles tab in the details pane. If you selected the logical network in tree mode, you can select the vNIC Profiles tab in the results list.
3. Click New or Edit to open the VM Interface Profile window.
   

   Figure 5.2. The VM Interface Profile window

4. Enter the Name and Description of the profile.
5. Select the relevant Quality of Service policy from the QoS list.
6. 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 and port mirroring as these are not compatible. For more information on passthrough, see Section 5.2.4, “Enabling Passthrough on a vNIC Profile”.
7. Use the Port Mirroring and Allow all users to use this Profile check boxes to toggle these options.
8. 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 5.8. Enabling Passthrough

1. Select a logical network from the Networks results list and click the vNIC Profiles tab in the details pane to list all vNIC profiles for that logical network.
2. Click New to open the VM Interface Profile window.
3. Enter the Name and Description of the profile.
4. Select the Passthrough check box. This will disable QoS and Port Mirroring.
5. 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.
6. Click OK to save the profile and close the window.

Procedure 5.9. Removing a vNIC Profile

1. Click the Networks resource tab, and select a logical network in the results list.
2. Select the Profiles tab in the details pane to display available vNIC profiles. If you selected the logical network in tree mode, you can select the VNIC Profiles tab in the results list.
3. Select one or more profiles and click Remove to open the Remove VM Interface Profile(s) window.
4. Click OK to remove the profile and close the window.

Procedure 5.10. Assigning Security Groups to vNIC Profiles

1. Click the Networks tab and select a logical network from the results list.
2. Click the vNIC Profiles tab in the details pane.
3. Click New, or select an existing vNIC profile and click Edit, to open the VM Interface Profile window.
4. 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.
5. In the text field, enter the ID of the security group to attach to the vNIC profile.
6. Click OK.

Procedure 5.11. User Permissions for vNIC Profiles

1. Click the Networks tab and select a logical network from the results list.
2. Select the vNIC Profiles resource tab to display the vNIC profiles.
3. Select the Permissions tab in the details pane to show the current user permissions for the profile.
4. Use the Add button to open the Add Permission to User window, and the Remove button to open the Remove Permission window, to affect user permissions for the vNIC profile.

Procedure 5.12. Configuring the Custom Device Property

1. On the Red Hat Enterprise Virtualization Manager, configure the vmfex custom property and set the cluster compatibility level using --cver.

   # engine-config -s CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}' --cver=3.6
   

2. Verify that the vmfex custom device property was added.

   # engine-config -g CustomDeviceProperties
   

3. Restart the engine.

   # service ovirt-engine restart
   

Procedure 5.13. Configuring a vNIC Profile for UCS Integration

1. Click the Networks resource tab, and select a logical network in the results list.
2. Select the vNIC Profiles tab in the details pane. If you selected the logical network in tree mode, you can select the vNIC Profiles tab in the results list.
3. Click New or Edit to open the VM Interface Profile window.
4. Enter the Name and Description of the profile.
5. Select the vmfex custom property from the custom properties list and enter the UCS port profile name.
6. Click OK.

Procedure 5.14. Importing a Network From an External Provider

1. Click the Networks tab.
2. Click the Import button to open the Import Networks window.
   

   Figure 5.3. The Import Networks Window

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. It is possible to customize the name of the network that you are importing. To customize the name, click on 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. Optionally, clear the Allow All check box for a network in the Networks to Import list to prevent that network from being available to all users.
8. Click the Import button.

Procedure 5.17. Assigning a Role to a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Click Add.
4. Enter the name or user name of an existing user into the Search text box and click Go. Select a user from the resulting list of possible matches.
5. Select a role from the Role to Assign: drop-down list.
6. Click OK.

Procedure 5.18. Removing a Role from a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Select the user to remove from the resource.
4. Click Remove. The Remove Permission window opens to confirm permissions removal.
5. Click OK.

Procedure 5.19. To Refresh Host Capabilities

1. Use the resource tabs, tree mode, or the search function to find and select a host in the results list.
2. Click the Refresh Capabilities button.

Procedure 5.20. Editing Host Network Interfaces and Assigning Logical Networks to Hosts

1. Click the Hosts resource tab, and select the desired host.
2. Click the Network Interfaces tab in the details pane.
3. Click the Setup Host Networks button to open the Setup Host Networks window.
4. 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.
   Alternatively, right-click the logical network and select a network interface from the drop-down menu.
5. 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. Select a Boot Protocol from None, DHCP, or Static. If you selected Static, enter the IP, Netmask / Routing Prefix, and the Gateway.

      Note

      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.
   3. 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.
      For more information on configuring host network quality of service see Section 2.3, “Host Network Quality of Service”
   4. To configure a network bridge, click the Custom Properties drop-down menu and select bridge_opts. 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 ethtool properties, click the Custom Properties drop-down menu and select ethtool_opts. Enter a valid key and value with the following syntax: [key]=[value]. Separate multiple entries with a whitespace character. The ethtool_opts option is not available by default, and you need to add it using the engine configuration tool. See Section B.2, “How to Set Up Red Hat Enterprise Virtualization Manager to Use Ethtool” for more information. See Red Hat Enterprise Linux 6 Deployment Guide or the manual page for more information on ethtool properties.
   6. To configure Fibre Channel over Ethernet (FCoE), click the Custom Properties drop-down menu and select fcoe. 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 Section B.3, “How to Set Up Red Hat Enterprise Virtualization Manager to Use FCoE” for more information.

      Note

      A separate, dedicated logical network is recommended for use with FCoE.
   7. If your logical network definition is not synchronized with the network configuration on the host, select the Sync network check box. A logical network cannot be edited or moved to another interface until it is synchronized.

      Note

      Networks are not considered synchronized if they have one of the following conditions:

      • The VM Network is different from the physical host network.
      • The VLAN identifier is different from the physical host network.
      • A Custom MTU is set on the logical network, and is different from the physical host network.
6. Select the Verify connectivity between Host and Engine check box to check network connectivity; this action will only work if the host is in maintenance mode.
7. Select the Save network configuration check box to make the changes persistent when the environment is rebooted.
8. Click OK.

Procedure 5.21. Adding Multiple VLANs to a Network Interface using Logical Networks

1. Click the Hosts resource tab, and select in the results list a host associated with the cluster to which your VLAN-tagged logical networks are assigned.
2. Click the Network Interfaces tab in the details pane to list the physical network interfaces attached to the data center.
3. Click Setup Host Networks to open the Setup Host Networks window.
4. 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.
5. Edit the logical networks by hovering your cursor over an assigned logical network and clicking the pencil icon to open the Edit Network window.
   If your logical network definition is not synchronized with the network configuration on the host, select the Sync network check box.
   Select a Boot Protocol from:

   • None,
   • DHCP, or
   • Static,
     Provide the IP and Subnet Mask.

   Click OK.
6. 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.
7. Select the Save network configuration check box
8. Click OK.

Procedure 5.22. Adding Network Labels to Host Network Interfaces

1. Click the Hosts resource tab, and select in the results list a host associated with the cluster to which your VLAN-tagged logical networks are assigned.
2. Click the Network Interfaces tab in the details pane to list the physical network interfaces attached to the data center.
3. Click Setup Host Networks to open the Setup Host Networks window.
4. Click Labels, and right-click [New Label]. Select a physical network interface to label.
   
5. Enter a name for the network label in the Label text field.
6. Click OK.

Procedure 5.24. Updating the FQDN of a Hypervisor Host

1. Place the hypervisor into maintenance mode so the virtual machines are live migrated to another hypervisor. See Section 6.5.7, “Moving a Host to Maintenance Mode” for more information. Alternatively, manually shut down or migrate all the virtual machines to another hypervisor. 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. • For RHEL-based hosts:
     • For Red Hat Enterprise Linux 6:
       Edit the /etc/sysconfig/network file, update the host name, and save.

       # vi /etc/sysconfig/network
       HOSTNAME=NEW_FQDN

     • For Red Hat Enterprise Linux 7:
       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

   • For Red Hat Enterprise Virtualization Hypervisors (RHEV-H):
     In the text user interface, select the Network screen, press the right arrow key and enter a new host name in the Hostname field. Select <Save> and press Enter.
4. Reboot the host.
5. Re-register the host with the Manager. See Manually Adding a Hypervisor from the Administration Portal in the Installation Guide for more information.

Procedure 5.25. 

1. Place the Hypervisor into maintenance mode so the virtual machines are live migrated to another hypervisor. See Section 6.5.7, “Moving a Host to Maintenance Mode” for more information. Alternatively, manually shut down or migrate all the virtual machines to another hypervisor. 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. Log in to your Hypervisor as the admin user.
4. Press F2, select OK, and press Enter to enter the rescue shell.
5. Modify the IP address by editing the /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt file. For example:

   # vi /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt
   ...
   BOOTPROTO=none	
   IPADDR=10.x.x.x
   PREFIX=24
   ...

6. Restart the network service and verify that the IP address has been updated.
   • For Red Hat Enterprise Linux 6:

     # service network restart

     # ifconfig ovirtmgmt

   • For Red Hat Enterprise Linux 7:

     # systemctl restart network.service

     # ip addr show ovirtmgmt

7. Type exit to exit the rescue shell and return to the text user interface.
8. Re-register the host with the Manager. See Manually Adding a Hypervisor from the Administration Portal in the Installation Guide for more information.

Procedure 6.1. Adding a Satellite Host Provider Host

1. Click the Hosts resource tab to list the hosts in the results list.
2. Click New to open the New Host window.
3. Use the drop-down menu to select the Host Cluster for the new host.
4. Select the Foreman/Satellite check box to display the options for adding a Satellite host provider host and select the provider from which the host is to be added.
5. Select either Discovered Hosts or Provisioned Hosts.
   • Discovered Hosts (default option): Select the host, host group, and compute resources from the drop-down lists.
   • Provisioned Hosts: Select a host from the Providers Hosts drop-down list.
   Any details regarding the host that can be retrieved from the external provider are automatically set, and can be edited as desired.
6. Enter the Name, Address, and SSH Port (Provisioned Hosts only) of the new host.
7. Select an authentication method to use with the host.
   • Enter the root user's password to use password authentication.
   • Copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_hosts on the host to use public key authentication (Provisioned Hosts only).
8. You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the Advanced Parameters drop-down button to show the advanced host settings.
   1. Optionally disable automatic firewall configuration.
   2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
9. You can configure the Power Management, SPM, Console, and Network Provider using the applicable tabs now; however, as these are not fundamental to adding a Red Hat Enterprise Linux host, they are not covered in this procedure.
10. Click OK to add the host and close the window.

Procedure 6.2. Configuring Satellite Errata Management for a Host

1. Add the Satellite server as an external provider. See Section 11.2.2, “Adding a Red Hat Satellite Instance for Host Provisioning” for more information.
2. Associate the required host with the Satellite server.

   Note

   The host must be registered to the Satellite server and have the katello-agent package installed.

   For more information on how to configure a host registration see Configuring a Host for Registration in the Red Hat Satellite User Guide and for more information on how to register a host and install the katello-agent package see Registration in the Red Hat Satellite User Guide
   1. In the Hosts tab, select the host in the results list.
   2. Click Edit to open the Edit Host window.
   3. Check the Use Foreman/Satellite checkbox.
   4. Select the required Satellite server from the drop-down list.
   5. Click OK.

Procedure 6.3. Configuring Power Management Settings

1. In the Hosts tab, select the host in the results list.
2. Click Edit to open the Edit Host window.
3. Click the Power Management tab to display the Power Management settings.
4. Select the Enable Power Management check box to enable the fields.
5. Select the Kdump integration check box to prevent the host from fencing while performing a kernel crash dump.

   Important

   When you enable Kdump integration on an existing host, the host must be reinstalled for kdump to be configured. See Section 6.5.10, “Reinstalling Virtualization Hosts”.
6. Optionally, select the Disable policy control of power management check box if you do not want your host's power management to be controlled by the Scheduling Policy of the host's cluster.
7. Click the plus (+) button to add a new power management device. The Edit fence agent window opens.
8. Enter the Address, User Name, and Password of the power management device into the appropriate fields.
9. Select the power management device Type from the drop-down list.
10. Enter the SSH Port number used by the power management device to communicate with the host.
11. Enter the Slot number used to identify the blade of the power management device.
12. Enter the Options for the power management device. Use a comma-separated list of 'key=value' entries.
13. Select the Secure check box to enable the power management device to connect securely to the host.
14. Click Test to ensure the settings are correct. Test Succeeded, Host Status is: on will display upon successful verification.
15. Click OK to close the Edit fence agent window.
16. In the Power Management tab, optionally expand the Advanced Parameters and use the up and down buttons to specify the order in which the Manager will search the host's cluster and dc (datacenter) for a fencing proxy.
17. Click OK.

Procedure 6.4. Configuring SPM settings

1. Click the Hosts resource tab, and select a host from the results list.
2. Click Edit to open the Edit Host window.
3. Click the SPM tab to display the SPM Priority settings.
4. Use the radio buttons to select the appropriate SPM priority for the host.
5. Click OK to save the settings and close the window.

Procedure 6.5. Editing a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click Edit to open the Edit window.
3. Change the necessary properties and click OK.

Procedure 6.6. Placing a Host into Maintenance Mode

1. Click the Hosts resource tab, and select the desired host.
2. Click Maintenance to open the Maintenance Host(s) confirmation window.
3. Optionally, enter a Reason for moving the host into maintenance mode in the Maintenance Host(s) confirmation window. This allows you to provide an explanation for the maintenance, which will appear in the logs and when the host is activated again.

   Note

   The host maintenance Reason field will only appear if it has been enabled in the cluster settings. See Section 4.2.2.1, “General Cluster Settings Explained” for more information.
4. Click OK to initiate maintenance mode.

Procedure 6.7. Activating a Host from Maintenance Mode

1. Click the Hosts resources tab and select the host.
2. Click Activate.

Procedure 6.8. Removing a host

1. In the Administration Portal, click the Hosts resource tab and select the host in the results list.
2. Place the host into maintenance mode.
3. Click Remove to open the Remove Host(s) confirmation window.
4. Select the Force Remove check box if the host is part of a Red Hat Gluster Storage cluster and has volume bricks on it, or if the host is non-responsive.
5. Click OK.

Procedure 6.9. Reinstalling Red Hat Enterprise Virtualization Hypervisors and Red Hat Enterprise Linux Hosts

1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
2. Click Maintenance. If migration is enabled at cluster level, any virtual machines running on the host are migrated to other hosts. If the host is the SPM, this function is moved to another host. The status of the host changes as it enters maintenance mode.
3. Click Reinstall to open the Install Host window.
4. Click OK to reinstall the host.

Procedure 6.10. Customizing hosts with tags

1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
2. Click Assign Tags to open the Assign Tags window.
   

   Figure 6.1. Assign Tags Window

3. The Assign Tags window lists all available tags. Select the check boxes of applicable tags.
4. Click OK to assign the tags and close the window.

Procedure 6.11. Viewing Host Errata

1. Click the Hosts resource tab, and select a host from the results list.
2. Click the General tab in the details pane.
3. Click the Errata sub-tab in the General tab.

Procedure 6.12. Viewing Host Devices

1. Use the Hosts resource tab, tree mode, or the search function to find and select a host from the results list.
2. Click the Host Devices tab in the details pane.

Procedure 6.13. Preparing a Host for GPU Passthrough

1. Log in to the host server and find the device vendor ID:product ID. In this example, the IDs are 10de:13ba and 10de:0fbc.

   # lspci -nn
   ...
   01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2)
   01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0fbc] (rev a1)
   ...

2. Edit the grub configuration file and append pci-stub.ids=xxxx:xxxx to the end of the GRUB_CMDLINE_LINUX line.

   # vi /etc/default/grub
   ...
   GRUB_CMDLINE_LINUX="nofb splash=quiet console=tty0 ... pci-stub.ids=10de:13ba,10de:0fbc"
   ...

   Blacklist the corresponding drivers on the host. In this example, nVidia's nouveau driver is being blacklisted by an additional amendment to the GRUB_CMDLINE_LINUX line.

   # vi /etc/default/grub
   ...
   GRUB_CMDLINE_LINUX="nofb splash=quiet console=tty0 ... pci-stub.ids=10de:13ba,10de:0fbc rdblacklist=nouveau"
   ...

   Save the grub configuration file.
3. Refresh the grub.cfg file and reboot the server for these changes to take effect:

   # grub2-mkconfig -o /boot/grub2/grub.cfg

   # reboot

4. Confirm the device is bound to the pci-stub driver with the lspci command:

   # lspci -nnk
   ...
   01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2)
           Subsystem: NVIDIA Corporation Device [10de:1097]
           Kernel driver in use: pci-stub
   01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0fbc] (rev a1)
           Subsystem: NVIDIA Corporation Device [10de:1097]
           Kernel driver in use: pci-stub
   ...

Procedure 6.14. Preparing a Guest Virtual Machine for GPU Passthrough

• • For Linux
    1. Only proprietary GPU drivers are supported. Black list the corresponding open source driver in the grub configuration file. For example:

       $ vi /etc/default/grub
       ...
       GRUB_CMDLINE_LINUX="nofb splash=quiet console=tty0 ... rdblacklist=nouveau"
       ...

    2. Locate the GPU BusID. In this example, is BusID is 00:09.0.

       # lspci | grep VGA
       00:09.0 VGA compatible controller: NVIDIA Corporation GK106GL [Quadro K4000] (rev a1)

    3. Edit the /etc/X11/xorg.conf file and append the following content:

       Section "Device"
       Identifier "Device0"
       Driver "nvidia"
       VendorName "NVIDIA Corporation"
       BusID "PCI:0:9:0"
       EndSection

    4. Restart the virtual machine.
  • For Windows
    1. Download and install the corresponding drivers for the device. For example, for Nvidia drivers, go to NVIDIA Driver Downloads.
    2. Restart the virtual machine.

Procedure 6.15. Setting fencing parameters on a host

1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
2. Click Edit to open the Edit Host window.
3. Click the Power Management tab.
   

   Figure 6.2. Power Management Settings

4. Select the Enable Power Management check box to enable the fields.
5. Select the Kdump integration check box to prevent the host from fencing while performing a kernel crash dump.

   Important

   When you enable Kdump integration on an existing host, the host must be reinstalled for kdump to be configured. See Section 6.5.10, “Reinstalling Virtualization Hosts”.
6. Optionally, select the Disable policy control of power management check box if you do not want your host's power management to be controlled by the Scheduling Policy of the host's cluster.
7. Click the plus (+) button to add a new power management device. The Edit fence agent window opens.
   

   Figure 6.3. Edit fence agent

8. Enter the Address, User Name, and Password of the power management device.
9. Select the power management device Type from the drop-down list.

   Note

   In Red Hat Enterprise Virtualization 3.5 and above, you can use a custom power management device. For more information on how to set up a custom power management device, see https://access.redhat.com/articles/1238743.
10. Enter the SSH Port number used by the power management device to communicate with the host.
11. Enter the Slot number used to identify the blade of the power management device.
12. Enter the Options for the power management device. Use a comma-separated list of 'key=value' entries.
13. Select the Secure check box to enable the power management device to connect securely to the host.
14. Click the Test button to ensure the settings are correct. Test Succeeded, Host Status is: on will display upon successful verification.

    Warning

    Power management parameters (userid, password, options, etc) are tested by Red Hat Enterprise Virtualization Manager only during setup and manually after that. If you choose to ignore alerts about incorrect parameters, or if the parameters are changed on the power management hardware without the corresponding change in Red Hat Enterprise Virtualization Manager, fencing is likely to fail when most needed.
15. Click OK to close the Edit fence agent window.
16. In the Power Management tab, optionally expand the Advanced Parameters and use the up and down buttons to specify the order in which the Manager will search the host's cluster and dc (datacenter) for a fencing proxy.
17. Click OK.

Procedure 6.18. Using Host Power Management Functions

1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
2. Click the Power Management drop-down menu.
3. Select one of the following options:
   • Restart: This option stops the host and waits until the host's status changes to Down. When the agent has verified that the host is down, the highly available virtual machines are restarted on another host in the cluster. The agent then restarts this host. When the host is ready for use its status displays as Up.
   • Start: This option starts the host and lets it join a cluster. When it is ready for use its status displays as Up.
   • Stop: This option powers off the host. Before using this option, ensure that the virtual machines running on the host have been migrated to other hosts in the cluster. Otherwise the virtual machines will crash and only the highly available virtual machines will be restarted on another host. When the host has been stopped its status displays as Non-Operational.

   Important

   When two fencing agents are defined on a host, they can be used concurrently or sequentially. For concurrent agents, both agents have to respond to the Stop command for the host to be stopped; and when one agent responds to the Start command, the host will go up. For sequential agents, to start or stop a host, the primary agent is used first; if it fails, the secondary agent is used.
4. Selecting one of the above options opens a confirmation window. Click OK to confirm and proceed.

Procedure 6.19. Manually fencing or isolating a non-responsive host

1. On the Hosts tab, select the host. The status must display as non-responsive.
2. Manually reboot the host. This could mean physically entering the lab and rebooting the host.
3. On the Administration Portal, right-click the host entry and select the Confirm Host has been rebooted button.
4. A message displays prompting you to ensure that the host has been shut down or rebooted. Select the Approve Operation check box and click OK.

Procedure 6.20. Assigning a Role to a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Click Add.
4. Enter the name or user name of an existing user into the Search text box and click Go. Select a user from the resulting list of possible matches.
5. Select a role from the Role to Assign: drop-down list.
6. Click OK.

Procedure 6.21. Removing a Role from a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the Permissions tab in the details pane to list the assigned users, the user's role, and the inherited permissions for the selected resource.
3. Select the user to remove from the resource.
4. Click Remove. The Remove Permission window opens to confirm permissions removal.
5. Click OK.

Procedure 7.1. Configuring the Required System User Accounts and System User Groups

1. Create the group kvm:

   # groupadd kvm -g 36

2. Create the user vdsm in the group kvm:

   # useradd vdsm -u 36 -g 36

3. Set the ownership of your exported directories to 36:36, which gives vdsm:kvm ownership:

   # chown -R 36:36 /exports/data
   # chown -R 36:36 /exports/export

4. Change the mode of the directories so that read and write access is granted to the owner, and so that read and execute access is granted to the group and other users:

   # chmod 0755 /exports/data
   # chmod 0755 /exports/export

1. In the Red Hat Enterprise Virtualization Manager Administration Portal, click the Storage resource tab.
2. Click New Domain.
   

   Figure 7.1. The New Domain Window

3. Enter a Name for the storage domain.
4. Accept the default values for the Data Center, Domain Function, Storage Type, Format, and Use Host lists.
5. Enter the Export Path to be used for the storage domain.
   The export path should be in the format of 192.168.0.10:/data or domain.example.com:/data.
6. Optionally, you can configure the advanced parameters.
   1. Click Advanced Parameters.
   2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
   3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
   4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
7. Click OK.
   The new NFS data domain is displayed in the Storage tab with a status of Locked until the disk is prepared. The data domain is then automatically attached to the data center.