Procedure 7.9. Logging in to the Hypervisor

1. Start the machine on which the Hypervisor is installed.
2. Enter the user name admin, and press Enter.
3. Enter the password you set during installation, and press Enter.

Procedure 7.14. Configuring Security

1. Select the Enable SSH password authentication option and press the space bar to enable SSH authentication.
2. Select the Disable AES-NI option and press the space bar to disable the use of AES-NI for encryption.
3. Optionally, enter the number of bytes by which to pad blocks in AES-NI encryption if AES-NI encryption is enabled.
4. Enter a new password for the admin user in the Password field and Confirm Password to change the password used to log into the Hypervisor console.
5. Select <Save> and press Enter.

Procedure 7.15. Configuring the Hypervisor Keyboard Layout

1. Select a keyboard layout from the list provided.

   Keyboard Layout Selection
   	
   Choose the Keyboard Layout you would like to apply to this system.
   
   Current Active Keyboard Layout: U.S. English
   Available Keyboard Layouts
   Swiss German (latin1)
   Turkish
   U.S. English
   U.S. International
   Ukranian
   ...
   
   <Save>

2. Select <Save> and press Enter to save the selection.

Procedure 7.16. Configuring Simple Network Management Protocol

1. Select the Enable SNMP option and press the space bar to enable SNMP.
2. Enter a password in the Password and Confirm Password fields.
3. Select <Save> and press Enter.

Procedure 7.17. Configuring Hypervisor Common Information Model

1. Select the Enable CIM option and press the space bar to enable CIM.

   Enable CIM     [ ]

2. Enter a password in the Password field and Confirm Password field.
3. Select <Save> and press Enter.

Procedure 7.18. Configuring Logging

1. In the Logrotate Max Log Size field, enter the maximum size in kilobytes that log files can reach before they are rotated by logrotate. The default value is 1024.
2. Select an Interval to configure logrotate to run Daily, Weekly, or Monthly. The default value is Daily.
3. Optionally, configure rsyslog to transmit log files to a remote syslog daemon:
   1. Enter the remote rsyslog server address in the Server Address field.
   2. Enter the remote rsyslog server port in the Server Port field. The default port is 514.
4. Optionally, configure netconsole to transmit kernel messages to a remote destination:
   1. Enter the Server Address.
   2. Enter the Server Port. The default port is 6666.
5. Select <Save> and press Enter.

Procedure 7.19. Configuring Kernel Dumps

1. Select an option for storing kernel dumps:

   • Local

     1. Select the Local option and press the space bar to store kernel dumps on the local system.

   • SSH

     1. Select the SSH option and press the space bar to export kernel dumps via SSH.
     2. Enter the location in which kernel dumps will be stored in the SSH Location (root@example.com) field.
     3. Enter an SSH Key URL (optional).

   • NFS

     1. Select the NFS option and press the space bar to export kernel dumps to an NFS share.
     2. Enter the location in which kernel dumps will be stored in the NFS Location (example.com:/var/crash) field.
2. Select <Save> and press Enter.

Procedure 7.20. Configuring Remote Storage

1. Enter an initiator name in the iSCSI Initiator Name field or the path to the NFS share in the NFSv4 Domain (example.redhat.com) field.
   ⁠

   Example 7.14. iSCSI Initiator Name

   iSCSI Initiator Name:
   iqn.1994-05.com.redhat:5189835eeb40_____

   ⁠

   Example 7.15. NFS Path

   NFSv4 Domain (example.redhat.com):
   example.redhat.com_____________________

2. Select <Save> and press Enter.

Procedure 7.21. Configuring a Hypervisor Management Server

• • Configure the Hypervisor Management Server using the address of the Manager.
    1. Enter the IP address or fully qualified domain name of the Manager in the Management Server field.
    2. Enter the management server port in the Management Server Port field. The default value is 443. If a different port was selected during Red Hat Enterprise Virtualization Manager installation, specify it here, replacing the default value.
    3. Leave the Password and Confirm Password fields blank. These fields are not required if the address of the management server is known.
    4. Select <Save & Register> and press Enter.
    5. In the RHEV-M Fingerprint screen, review the SSL fingerprint retrieved from the Manager, select <Accept>, and press Enter. The Certificate Status in the RHEV-M screen changes from N/A to Verified.
  • Configure the Hypervisor Management Server using a password.
    1. Enter a password in the Password field. Although the Hypervisor will accept a weak password, it is recommended that you use a strong password. Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
    2. Re-enter the password in the Confirm Password field.
    3. Leave the Management Server and Management Server Port fields blank. As long as a password is set, allowing the Hypervisor to be added to the Manager later, these fields are not required.
    4. Select <Save & Register> and press Enter.

Procedure 7.22. Setting Up Self-Hosted Engine on RHEV-H

1. Specify the Red Hat Enterprise Virtualization Manager virtual machine installation method:
   • To install using the RHEV-M Virtual Appliance, enter the URL to the appliance. For example: http://file.domain.com/rhevm-appliance.ova. This is the recommended Manager installation method.
   • To install using PXE boot, select the PXE Boot Engine VM option.
   
2. Click <Start first host setup> and press Enter. Click OK to start the hosted-engine deployment script.
   

3. Configuring Storage

   Select the type of storage to use.

   During customization use CTRL-D to abort.
   Please specify the storage you would like to use (iscsi, nfs3, nfs4)[nfs3]:

   • For NFS storage types, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs

     Important

     The share must be accessible from the hypervisor and must be owned by user vdsm and group kvm.
   • For iSCSI, specify the iSCSI portal IP address, port, user name and password, and select a target name from the auto-detected list:

     Please specify the iSCSI portal IP address:           
     Please specify the iSCSI portal port [3260]:           
     Please specify the iSCSI portal user:           
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

   Choose the storage domain and storage data center names to be used in the environment.

   [ INFO  ] Installing on first host
   Please provide storage domain name. [hosted_storage]: 
   Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]:

4. Configuring the Network

   The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access.

   Note

   Configuring a bonded and vlan-tagged network interface as the management bridge is currently not supported. To work around this issue, see https://access.redhat.com/solutions/1417783 for more information.

   Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
   iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: 
   Please indicate a pingable gateway IP address [X.X.X.X]:
   

5. Configuring the Virtual Machine

   The script creates a virtual machine to be configured as the Red Hat Enterprise Virtualization Manager.

   [ INFO ] Checking OVF archive content
   [ INFO ] Checking OVF XML content
   Please specify an alias for the Hosted Engine image [hosted_engine]:
   The following CPU types are supported by this host:
             - model_Penryn: Intel Penryn Family
             - model_Conroe: Intel Conroe Family
   Please specify the CPU type to be used by the VM [model_Penryn]: 
   You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]: 
   Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]:
   

6. Configuring the Hosted Engine

   Specify a name for the hypervisor to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user to access the Administrator Portal. Provide the FQDN for the Manager virtual machine.

   Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]: 
   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
   Confirm 'admin@internal' user password: 
   Please provide the FQDN for the engine you would like to use. This needs to match the FQDN that you will use for the engine installation within the VM: HostedEngine-VM.example.com
   Please provide the name of the SMTP server through which we will send notifications [localhost]: 
   Please provide the TCP port number of the SMTP server [25]: 
   Please provide the email address from which notifications will be sent [root@localhost]: 
   Please provide a comma-separated list of email addresses which will get notifications [root@localhost]:
   

7. Configuration Preview

   Before proceeding, the hosted-engine script displays the configuration values you have entered, and prompts for confirmation to proceed with these values.

8. Creating the Manager Virtual Machine

   The script creates the Manager virtual machine and provides connection details.

   You can now connect to the VM with the following command:
   	/usr/bin/remote-viewer vnc://localhost:5900
   Use temporary password "3042QHpX" to connect to vnc console.
   Please note that in order to use remote-viewer you need to be able to run graphical applications.
   This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
   Otherwise you can run the command from a terminal in your preferred desktop environment.
   If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command:
   virsh -c qemu+tls://Test/system console HostedEngine
   If you need to reboot the VM you will need to start it manually using the command:
   hosted-engine --vm-start
   You can then set a temporary password using the command:
   hosted-engine --add-console-password
   The VM has been started.  Install the OS and shut down or reboot it.  To continue please make a selection:
            
             (1) Continue setup - engine installation is complete
             (2) Power off and restart the VM
             (3) Abort setup
             (4) Destroy VM and abort setup
            
             (1, 2, 3, 4)[1]:

9. On a machine that supports graphical applications and has virt-viewer installed, connect to the Manager virtual machine. Enter the temporary password.

   /usr/bin/remote-viewer vnc://Host-HE1.example.com:5900

10. Use the RHEV-M Virtual Appliance setup utility to set the root password and change the default authentication and keyboard configuration as necessary. You will not be able to complete RHN registration at this stage as there will be no network connection.
    
11. Run the following command to complete your Red Hat Enterprise Virtualization Manager setup:

    # engine-setup --offline --config-append=rhevm-setup-answers

12. Synchronizing the Host and the Manager

    Return to the hypervisor and continue the hosted-engine deployment script by selecting option 1:

    (1) Continue setup - engine installation is complete

    [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
    [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
    [ INFO  ] The VDSM host is now operational
              Please shutdown the VM allowing the system to launch it as a monitored service.
              The system will wait until the VM is down.
    

13. Shutdown the Manager virtual machine.

    # shutdown -h now

14. Confirm that setup is complete and hit the Enter key to return to the Hypervisor console.

    [ INFO  ] Enabling and starting HA services
              Hosted Engine successfully set up
    [ INFO  ] Stage: Clean up
    [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-2015xx.conf'
    [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
    [ INFO  ] Stage: Pre-termination
    [ INFO  ] Stage: Termination
    
    [screen is terminating]
    Hit <Return> to return to the TUI
    

Procedure 7.23. Registering the Hypervisor with the Red Hat Network

1. Enter your Red Hat Network user name in the Login field.
2. Enter your Red Hat Network password in the Password field.
3. Enter a profile name to be used for the system in the Profile Name (optional) field. This is the name under which the system will appear when viewed in Red Hat Network.
4. Select the method by which to register the Hypervisor:

   • The Red Hat Network

     Select the RHN option and press the space bar to register the Hypervisor directly with the Red Hat Network. You do not need to enter values in the URL and CA URL fields.
     ⁠

     Example 7.16. Red Hat Network Configuration

     (X) RHN     ( ) Satellite     ( ) SAM
     URL:      _______________________________________________________________
     CA URL:   _______________________________________________________________

   • Satellite

     1. Select the Satellite option and press the space bar to register the Hypervisor with a Satellite server.
     2. Enter the URL of the Satellite server in the URL field.
     3. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
     ⁠

     Example 7.17. Satellite Configuration

     ( ) RHN     (X) Satellite     ( ) SAM
     RHN URL:   https://your-satellite.example.com_____________________________
     CA URL:    https://your-satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

   • Subscription Asset Manager

     1. Select the Subscription Asset Manager option and press Space to register the Hypervisor via Subscription Asset Manager.
     2. Enter the URL of the Subscription Asset Manager server in the URL field.
     3. Enter the URL of the certificate authority for the Subscription Asset Manager server in the CA URL field.
     ⁠

     Example 7.18. Subscription Asset Manager Configuration

     ( ) RHN     ( ) Satellite     (X) SAM
     URL:  https://subscription-asset-manager.example.com_____________________________
     CA :  https://subscription-asset-manager.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

5. If you are using a proxy server, you must also specify the details of that server:
   1. Enter the IP address or fully qualified domain name of the proxy server in the Server field.
   2. Enter the port by which to attempt a connection to the proxy server in the Port field.
   3. Enter the user name by which to attempt a connection to the proxy server in the Username field.
   4. Enter the password by which to authenticate the user name specified above in the Password field.
6. Select <Save> and press Enter.