Procedure 1.1. Creating a New Role

1. On the header bar, click the Configure button to open the Configure window. The window shows a list of default User and Administrator roles, and any custom roles.
2. Click New. The New Role dialog box displays.
   

   Figure 1.2. The New Role Dialog

3. Enter the Name and Description of the new role.
4. Select either Admin or User as the Account Type.
5. Use the Expand All or Collapse All buttons to view more or fewer of the permissions for the listed objects in the Check Boxes to Allow Action list. You can also expand or collapse the options for each object.
6. For each of the objects, select or clear the actions you wish to permit or deny for the role you are setting up.
7. Click OK to apply the changes you have made. The new role displays on the list of roles.

Procedure 1.2. Editing or Copying a Role

1. On the header bar, click the Configure button to open the Configure window. The window shows a list of default User and Administrator roles, and any custom roles.
2. Select the role you wish to change. Click Edit to open the Edit Role window, or click Copy to open the Copy Role window.
3. If necessary, edit the Name and Description of the role.
4. Use the Expand All or Collapse All buttons to view more or fewer of the permissions for the listed objects. You can also expand or collapse the options for each object.
5. For each of the objects, select or clear the actions you wish to permit or deny for the role you are editing.
6. Click OK to apply the changes you have made.

Procedure 1.3. Creating a Scheduling Policy

1. Click the Configure button in the header bar of the Administration Portal to open the Configure window.
2. Click Scheduling Policies to view the scheduling policies tab.
3. Click New to open the New Scheduling Policy window.
   

   Figure 1.8. The New Scheduling Policy Window

4. Enter a Name and Description for the scheduling policy.
5. Configure filter modules:
   1. In the Filter Modules section, drag and drop the preferred filter modules to apply to the scheduling policy from the Disabled Filters section into the Enabled Filters section.
   2. Specific filter modules can also be set as the First, to be given highest priority, or Last, to be given lowest priority, for basic optimization.
      To set the priority, right-click any filter module, hover the cursor over Position and select First or Last.
6. Configure weight modules:
   1. In the Weights Modules section, drag and drop the preferred weights modules to apply to the scheduling policy from the Disabled Weights section into the Enabled Weights & Factors section.
   2. Use the + and - buttons to the left of the enabled weight modules to increase or decrease the weight of those modules.
7. Specify a load balancing policy:
   1. From the drop-down menu in the Load Balancer section, select the load balancing policy to apply to the scheduling policy.
   2. From the drop-down menu in the Properties section, select a load balancing property to apply to the scheduling policy and use the text field to the right of that property to specify a value.
   3. Use the + and - buttons to add or remove additional properties.
8. Click OK.

Procedure 1.4. Creating an Instance Type

1. On the header bar, click Configure.
2. Click the Instance Types tab.
3. Click New to open the New Instance Type window.
   

   Figure 1.10. The New Instance Type Window

4. Enter a Name and Description for the instance type.
5. Click Show Advanced Options and configure the instance type's settings as required. The settings that appear in the New Instance Type window are identical to those in the New Virtual Machine window, but with the relevant fields only. See Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows in the Virtual Machine Management Guide.
6. Click OK.

Procedure 1.5. Editing Instance Type Properties

1. On the header bar, click Configure.
2. Click the Instance Types tab.
3. Select the instance type to be edited.
4. Click Edit to open the Edit Instance Type window.
5. Change the settings as required.
6. Click OK.

Procedure 1.6. Removing an Instance Type

1. On the header bar, click Configure.
2. Click the Instance Types tab.
3. Select the instance type to be removed.
4. Click Remove to open the Remove Instance Type window.
5. If any virtual machines are based on the instance type to be removed, a warning window listing the attached virtual machines will appear. To continue removing the instance type, select the Approve Operation checkbox. Otherwise click Cancel.
6. Click OK.

Procedure 1.7. Creating a MAC Address Pool

1. On the header bar, click the Configure button to open the Configure window.
2. Click the MAC Address Pools tab.
3. Click the Add button to open the New MAC Address Pool window.
   

   Figure 1.11. The New MAC Address Pool Window

4. Enter the Name and Description of the new MAC address pool.
5. Select the Allow Duplicates check box to allow a MAC address to be used multiple times in a pool. The MAC address pool will not automatically use a duplicate MAC address, but enabling the duplicates option means a user can manually use a duplicate MAC address.

   Note

   If one MAC address pool has duplicates disabled, and another has duplicates enabled, each MAC address can be used once in the pool with duplicates disabled but can be used multiple times in the pool with duplicates enabled.
6. Enter the required MAC Address Ranges. To enter multiple ranges click the plus button next to the From and To fields.
7. Click OK.

Procedure 1.8. Editing MAC Address Pool Properties

1. On the header bar, click the Configure button to open the Configure window.
2. Click the MAC Address Pools tab.
3. Select the MAC address pool to be edited.
4. Click the Edit button to open the Edit MAC Address Pool window.
5. Change the Name, Description, Allow Duplicates, and MAC Address Ranges fields as required.

   Note

   When a MAC address range is updated, the MAC addresses of existing NICs are not reassigned. MAC addresses that were already assigned, but are outside of the new MAC address range, are added as user-specified MAC addresses and are still tracked by that MAC address pool.
6. Click OK.

Procedure 1.9. Editing MAC Address Pool Permissions

1. On the header bar, click the Configure button to open the Configure window.
2. Click the MAC Address Pools tab.
3. Select the required MAC address pool.
4. Edit the user permissions for the MAC address pool:
   • To add user permissions to a MAC address pool:
     1. Click Add in the user permissions pane at the bottom of the Configure window.
     2. Search for and select the required users.
     3. Select the required role from the Role to Assign drop-down list.
     4. Click OK to add the user permissions.
   • To remove user permissions from a MAC address pool:
     1. Select the user permission to be removed in the user permissions pane at the bottom of the Configure window.
     2. Click Remove to remove the user permissions.

Procedure 1.10. Removing a MAC Address Pool

1. On the header bar, click the Configure button to open the Configure window.
2. Click the MAC Address Pools tab.
3. Select the MAC address pool to be removed.
4. Click the Remove button to open the Remove MAC Address Pool window.
5. Click OK.

Procedure 3.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 3.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 3.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 3.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 3.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 3.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 3.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 3.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 4.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. Click OK to create the data center and open the New Data Center - Guide Me window.
6. 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 4.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 4.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 4.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 4.5. Changing the Data Center Storage Type

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 Storage to the desired value.
5. Click OK.

Procedure 4.6. 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 4.7. 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 4.8. 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 4.9. 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 4.10. 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 4.11. 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.12. 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 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.
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. Optionally select the /dev/hwrng source (external hardware device) check box to specify the random number generator device that all hosts in the cluster will use. The /dev/urandom source (Linux-provided device) is enabled by default.
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 Migration Policy tab to define the virtual machine migration policy for the cluster.
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 the MAC Address Pool tab to specify a MAC address pool other than the default pool for the cluster. For more options on creating, editing, or removing MAC address pools, see Section 1.5, “MAC Address Pools”.
18. Click OK to create the cluster and open the New Cluster - Guide Me window.
19. 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 5.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 5.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 5.3. Edit Scheduling Policy

3. Select one of the following policies:
   • none
   • vm_evenly_distributed
     1. Set the minimum number of virtual machines that must be running on at least one host to enable load balancing 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.
     4. Optionally, in the HeSparesCount field, enter the number of additional self-hosted engine nodes on which to reserve enough free memory to start the Manager virtual machine if it migrates or shuts down. See Configuring Memory Slots Reserved for the Self-Hosted Engine on Additional Hosts in the Self-Hosted Engine Guide for more information.
   • 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 above which virtual machines start migrating to other hosts in the MinFreeMemoryForUnderUtilized.
     4. Enter the maximum required free memory in MB below which virtual machines start migrating to other hosts in the MaxFreeMemoryForOverUtilized.
     5. Optionally, in the HeSparesCount field, enter the number of additional self-hosted engine nodes on which to reserve enough free memory to start the Manager virtual machine if it migrates or shuts down. See Configuring Memory Slots Reserved for the Self-Hosted Engine on Additional Hosts in the Self-Hosted Engine Guide for more information.
   • 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 above which virtual machines start migrating to other hosts in the MinFreeMemoryForUnderUtilized.
     5. Enter the maximum required free memory in MB below which virtual machines start migrating to other hosts in the MaxFreeMemoryForOverUtilized.
     6. Optionally, in the HeSparesCount field, enter the number of additional self-hosted engine nodes on which to reserve enough free memory to start the Manager virtual machine if it migrates or shuts down. See Configuring Memory Slots Reserved for the Self-Hosted Engine on Additional Hosts in the Self-Hosted Engine Guide for more information.
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 5.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 5.7. Importing an Existing Red Hat Gluster Storage Cluster to Red Hat 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 5.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 5.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 5.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 5.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 6.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. The External Provider drop-down list will not list any external providers in read-only mode.
   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 6.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.

   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.
5. Click OK to save the changes.

Procedure 6.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. The check box is grayed out if the external provider is in read-only mode.
5. Click OK.

Procedure 6.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 6.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 6.1. Manage Networks

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

Procedure 6.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 6.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 6.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 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.
7. 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 Section 6.2.4, “Enabling Passthrough on a vNIC Profile”.
8. 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.
9. Use the Port Mirroring and Allow all users to use this Profile check boxes to toggle these options.
10. 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.
11. Click OK.

Procedure 6.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.
5. 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.
6. 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.
7. Click OK to save the profile and close the window.

Procedure 6.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 6.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 6.11. User Permissions for vNIC Profiles

1. Click the Networks tab and select a logical network from the results list.
2. Click the vNIC Profiles resource tab to display the vNIC profiles.
3. Click the Permissions tab in the details pane to show the current user permissions for the profile.
4. Click the Add button to open the Add Permission to User window, and the Remove button to open the Remove Permission window, 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 6.12. Configuring the Custom Device Property

1. On the Red Hat 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.

   # systemctl restart ovirt-engine.service
   

Procedure 6.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 6.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 6.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 6.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 6.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 6.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 Management → Refresh Capabilities.

Procedure 6.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. 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

      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.

      Note

      The IPv6 tab should not be used as it is currently 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.
      For more information on configuring host network quality of service see Section 3.3, “Host Network Quality of Service”
   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=[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 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 default_route property in the Custom Properties tab.
      1. For the management network, set the default_route custom property to false.
      2. For the non-management network, set default_route to true.
      Repeat this configuration on each host in the Data Center. The default_route option is not available by default; you need to add it using the engine configuration tool. See Section B.4, “How to Set Up Red Hat Virtualization Manager to Use a Non-Management Network” 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. 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 6.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 6.22. Assigning Additional IPv4 Addresses to a Host Network

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

   # 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 the Hosts resource tab, and select the host for which additional IP addresses must be configured.
5. Click the Network Interfaces tab in the details pane and click the Setup Host Networks button to open the Setup Host Networks window.
6. Edit the host network interface by hovering the cursor over the assigned logical network and clicking the pencil icon to open the Edit Management Network window.
7. 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.
8. Click OK.
9. Select the Save network configuration check box.
10. Click OK.

Procedure 6.23. 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 6.25. Updating the FQDN of a Host

1. Place the host into maintenance mode so the virtual machines are live migrated to another host. See Section 7.5.8, “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 7.5.1, “Adding a Host to the Red Hat Virtualization Manager” for more information.

Procedure 7.1. Adding a Host to the Red Hat Virtualization Manager

1. From the Administration Portal, click the Hosts resource tab.
2. Click New.
3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Address of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.
5. Select an authentication method to use for the Manager to access the host.
   • Enter the root user's password to use password authentication.
   • Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
6. Click the Advanced Parameters button to expand 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.
7. Optionally configure Power Management, SPM, Console, Network Provider, and Kernel. See Section 7.5.5, “Explanation of Settings and Controls in the New Host and Edit Host Windows” for more information. Hosted Engine is used when deploying or undeploying a host for a self-hosted engine deployment.
8. Click OK.

Procedure 7.2. 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 7.3. Configuring Satellite Errata Management for a Host

1. Add the Satellite server as an external provider. See Section 12.2.1, “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 7.4. Adding a Network Node as a Host

1. Use the Red Hat OpenStack Platform director to deploy the Networker role on the network node. See Creating a New Role and Networker in the Red Hat OpenStack Platform Advanced Overcloud Customization Guide.
2. Enable the Red Hat Virtualization repositories. See Subscribing to the Required Entitlements in the Installation Guide.
3. Install the Openstack Networking hook:

   # yum install vdsm-hook-openstacknet

4. Add the network node to the Manager as a host. See Section 7.5.1, “Adding a Host to the Red Hat Virtualization Manager”.

   Important

   Do not select the OpenStack Networking provider from the Network Provider tab. This is currently not supported.
5. Remove the firewall rule that rejects ICMP traffic:

   # iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited

Procedure 7.5. 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 7.5.12, “Reinstalling 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. For information about this window, see Section 7.5.5.2, “Host Power Management Settings Explained”
8. Enter the User Name and Password of the power management device into the appropriate fields.
9. Select the power management device Type in the drop-down list.
10. Enter the IP address in the Address field.
11. Enter the SSH Port number used by the power management device to communicate with the host.
12. Enter the Slot number used to identify the blade of the power management device.
13. Enter the Options for the power management device. Use a comma-separated list of 'key=value' entries.
    • If both IPv4 and IPv6 IP addresses can be used (default), leave the Options field blank.
    • If only IPv4 IP addresses can be used, enter inet4_only=1.
    • If only IPv6 IP addresses can be used, enter inet6_only=1.
14. Select the Secure check box to enable the power management device to connect securely to the host.
15. Click Test to ensure the settings are correct. Test Succeeded, Host Status is: on will display upon successful verification.
    If the host is powered off, you will see Test Succeeded, Host Status is: off
    If the test fails, the default settings that are configured when selecting the power management device type may not match your configuration. This occurs when you change the default fence settings on your hardware. To resolve the problem, update the fence agent settings as follows:
    1. Install the fence-agents package.

       yum install fence-agents

    2. Open the man page for the agent and search for STDIN Parameters section. This contains the names of the parameters that you will need to manually edit. For example, for ilo4 type:

       man fence_ilo4

    3. Check your hardware configuration and determine which value(s) you have changed.
    4. In the Options field in the Edit fence agent window, add the relevant parameter according to the man page and enter the required value according to your configuration.
    5. Click Test to determine if the change was successful. If it was not, check the hardware configuration for additional changes that you have made and repeat the procedure.
16. Click OK to close the Edit fence agent window.
17. 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.
18. Click OK.

Procedure 7.6. 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 7.7. Placing a Host into Maintenance Mode

1. Click the Hosts resource tab, and select the desired host.
2. Click Management → 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 5.2.2.1, “General Cluster Settings Explained” for more information.
4. Optionally, select the required options for hosts that support Gluster.
   Select the Ignore Gluster Quorum and Self-Heal Validations option to avoid the default checks. By default, the Manager checks that the Gluster quorum is not lost when the host is moved to maintenance mode. The Manager also checks that there is no self-heal activity that will be affected by moving the host to maintenance mode. If the Gluster quorum will be lost or if there is self-heal activity that will be affected, the Manager prevents the host from being placed into maintenance mode. Only use this option if there is no other way to place the host in maintenance mode.
   Select the Stop Gluster Service option to stop all Gluster services while moving the host to maintenance mode.

   Note

   These fields will only appear in the host maintenance window when the selected host supports Gluster. See Replacing the Primary Gluster Storage Node in Maintaining Red Hat Hyperconverged Infrastructure for more information.
5. Click OK to initiate maintenance mode.

Procedure 7.8. Activating a Host from Maintenance Mode

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

Procedure 7.9. 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 7.10. Reinstalling Red Hat Virtualization Host or 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 Management → 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 Installation → Reinstall to open the Install Host window.
4. Click OK to reinstall the host.