7.5. Configuring the Red Hat Enterprise Virtualization Hypervisor
7.5.1. Configuring Networking on the Hypervisor
Procedure 7.7. Configuring the Host Name, DNS, and NTP
- 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 the DNS Server 1 field and enter the IP address of the primary DNS server. Optionally set a secondary DNS server.
- Select the NTP Server 1 field and enter the IP address or host name of the primary NTP server. Optionally set a secondary NTP server.
- Selectand press Enter to save the changes. You must save before you proceed to edit the network interfaces.
Procedure 7.8. Configuring Network Interfaces
- Select a network interface from the list beneath Available System NICs and press Enter to configure that network interface.
Note
To identify the physical network interface card associated with the selected network interface, selectand press Enter. - Choose to configure IPv4 or IPv6.
- Configure a dynamic or static IP address for IPv4:
- Select DHCP under IPv4 Settings and press the space bar to configure a dynamic IP address.
- Select Static under IPv4 Settings, press the space bar, and input the IP Address, Netmask, and Gateway that the Hypervisor will use to configure a static IP address.
Example 7.17. Static IPv4 Networking Configuration
IPv4 Settings ( ) Disabled ( ) DHCP (*) Static IP Address: 192.168.122.100_ Netmask: 255.255.255.0___ Gateway 192.168.1.1_____
- Configure a stateless, dynamic, or static IP for IPv6:
- Select Auto under IPv6 Settings and press the space bar to configure stateless auto configuration.
- Select DHCP under IPv6 Settings and press the space bar to configure a dynamic IP address.
- Select Static under IPv6 Settings, press the space bar, and input the IP Address, Prefix Length, and Gateway that the Hypervisor will use to configure a static IP address.
Example 7.18. Static IPv6 Networking Configuration
IPv6 Settings ( ) Disabled ( ) Auto ( ) DHCP (*) Static IP Address: 2001:db8:1::ab9:C0A8:103_ Prefix Length: 64______ Gateway 2001:db8:1::ab9:1________
- Enter a VLAN identifier in the VLAN ID field to configure a VLAN for the device.
- Select thebutton and press Enter to save the network configuration.
7.5.2. Configuring Remote Storage
Procedure 7.9. Configuring Remote Storage
- 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.19. iSCSI Initiator Name
iSCSI Initiator Name: iqn.1994-05.com.redhat:5189835eeb40_____
Example 7.20. NFS Path
NFSv4 Domain (example.redhat.com): example.redhat.com_____________________
- Selectand press Enter.
7.5.3. Connecting the Hypervisor to the Red Hat Enterprise Virtualization Manager
Important
root
password on the Hypervisor and enables SSH password authentication. Once the Hypervisor has successfully been added to the Manager, disabling SSH password authentication is recommended.
Important
Procedure 7.10. Configuring a Hypervisor Management Server
- Configure the Hypervisor Management Server using the address of the Manager.
- Enter the IP address or fully qualified domain name of the Manager in the Management Server field.
- 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. - Leave the Password and Confirm Password fields blank. These fields are not required if the address of the management server is known.
- Selectand press Enter.
After a few minutes, the Hypervisor is displayed under the Hosts tab in the Administration Portal. You must approve it to use the Hypervisor in your Red Hat Enterprise Virtualization environment. See Section 7.6, “Approving a Registered Hypervisor” for more information. - Configure the Hypervisor Management Server using a password.
- 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.
- Re-enter the password in the Confirm Password field.
- 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.
- Selectand press Enter.
After the password is set, manually add the Hypervisor from the Administration Portal. See Section 9.4, “Manually Adding a Hypervisor from the Administration Portal” for more information.
7.5.4. Registering the Hypervisor
Procedure 7.11. Registering the Hypervisor
- Enter your Customer Portal user name in the Login field.
- Enter your Customer Portal password in the Password field.
- 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 the Customer Portal.
- Select the method by which to register the Hypervisor:
Red Hat Subscription Manager
- Select the RHSM option and press the space bar.
- You do not need to enter values in the URL and CA URL fields.
- Optionally enter an organization name in the Organization field.
Example 7.21. Red Hat Subscription Manager Configuration
(X) RHSM ( ) Satellite ( ) SAM URL: _________________________________________________ CA URL: _________________________________________________ Organization: Organization_Name________________________________
Red Hat Satellite 5
- Select the Satellite option and press the space bar.
- Enter the URL of the Satellite server in the URL field.
- Enter the URL of the certificate authority for the Satellite server in the CA URL field.
- Optionally enter an organization name in the Organization field.
- Optionally enter a life cycle environment name in the Environment field.
Example 7.22. Satellite 5 Configuration
( ) RHSM (X) Satellite ( ) SAM URL: https://sat.example.com____________________________ CA URL: http://sat.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT Organization: Organization_Name__________________________________ Environment: Library____________________________________________
Red Hat Satellite 6.0 or 6.1
- On the Satellite server, extract the certificate:
# cd /tmp # rpm2cpio /var/www/html/pub/katello-ca-consumer-latest.noarch.rpm | cpio -idmv # cat etc/rhsm/ca/candlepin-local.pem etc/rhsm/ca/katello-server-ca.pem >> /var/www/html/pub/katello-server-ca.crt # restorecon -Rv /var/www/html/pub/katello-server-ca.crt # chmod 644 /var/www/html/pub/katello-server-ca.crt
- On the Hypervisor, select the Satellite option and press the space bar.
- Enter the URL of the Satellite server in the URL field.
- Enter the URL of the certificate authority for the Satellite server in the CA URL field.
- Enter an organization name in the Organization field.
- Enter a life cycle environment name in the Environment field.
Example 7.23. Satellite 6 Configuration
( ) RHSM (X) Satellite ( ) SAM URL: https://sat.example.com____________________________ CA URL: http://sat.example.com/pub/katello-server-ca.crt___ Organization: Organization_Name__________________________________ Environment: Library____________________________________________
Red Hat Satellite 6.2
- Select the Satellite option and press the space bar.
- Enter the URL of the Satellite server in the URL field.
- Enter the URL of the certificate authority for the Satellite server in the CA URL field.
- Enter an organization name in the Organization field.
- Enter a life cycle environment name in the Environment field.
Example 7.24. Satellite 6 Configuration
( ) RHSM (X) Satellite ( ) SAM URL: https://sat.example.com____________________________ CA URL: http://sat.example.com/pub/katello-server-ca.crt___ Organization: Organization_Name__________________________________ Environment: Library____________________________________________
Subscription Asset Manager
- Select the SAM option and press the space bar.
- Enter the URL of the Subscription Asset Manager server in the URL field.
- Enter the URL of the certificate authority for the Subscription Asset Manager server in the CA URL field.
- Optionally enter an organization name in the Organization field.
Example 7.25. Subscription Asset Manager Configuration
( ) RHSM ( ) Satellite (X) SAM URL: https://sam.example.com____________________________ CA URL: http://sam.example.com/sam/candlepin-local.pem_____ Organization: Your_Organization__________________________________
- If you are using a proxy server, you must also specify the details of that server:
- Selectand press Enter.
- Enter the IP address or fully qualified domain name of the proxy server in the Server field.
- Enter the port by which to attempt a connection to the proxy server in the Port field.
- Enter the user name by which to attempt a connection to the proxy server in the Username field.
- Enter the password by which to authenticate the user name specified above in the Password field.
- Select RHSM Registration screen.and press Enter to save the configuration and return to the
- Selectand press Enter.
7.5.5. Changing the Admin User Password and Other Security-Related Tasks
admin
user.
Procedure 7.12. Configuring Security-Related Tasks
- To enable SSH authentication, select the Enable SSH password authentication option and press the space bar. SSH authentication can also be enabled in the RHEV-M screen. Leave the option disabled if the function is not required.
- AES-NI encryption is enabled by default.
- If you need to disable it, select the Disable AES-NI option and press the space bar.
- If AES-NI encryption is enabled, you can optionally set the number of bytes by which to pad blocks in AES-NI encryption
- 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. - Selectand press Enter.
7.5.6. Changing the Keyboard Layout on the Hypervisor
Procedure 7.13. Configuring the Hypervisor Keyboard Layout
- 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> - Selectand press Enter to save the selection.
7.5.7. Enabling the SNMP Agent on the Hypervisor
Enable SNMP [ ] SNMP Password Password: _______________ Confirm Password: _______________ <Save> <Reset>
Procedure 7.14. Enabling the SNMP Agent on the Hypervisor
- Select the Enable SNMP option and press the space bar to enable SNMP.
- Enter a password in the Password and Confirm Password fields.
- Select <Save> and press Enter.
7.5.8. Enabling CIM Monitoring Connections on the Hypervisor
Procedure 7.15. Enabling CIM Monitoring Connections on the Hypervisor
- Select the Enable CIM option and press the space bar to enable CIM.
Enable CIM [ ]
- Enter a password in the Password field and Confirm Password field.
- Selectand press Enter.
7.5.9. Configuring Logging
/var/log/ovirt.log
/var/log/ovirt-node.log
/var/log/audit/audit.log
/var/log/messages
- dmesg
Procedure 7.16. Configuring Logging using the Logging Screen
- 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
. - Select an Interval to configure logrotate to run Daily, Weekly, or Monthly. The default value is Daily.
- Optionally configure rsyslog to transmit log files to a remote
syslog
daemon:- Enter the remote rsyslog server address in the Server Address field.
- Enter the remote rsyslog server port in the Server Port field. The default port is
514
.
- Optionally configure netconsole to transmit kernel messages to a remote destination:
- Enter the Server Address.
- Enter the Server Port. The default port is
6666
.
- Selectand press Enter.
7.5.10. Configuring Kernel Dumps
Kdump Options | Description |
---|---|
Disable
|
Disables kernel dumping.
|
Local
|
Stores kernel dumps on the local system.
|
SSH
|
Exports kernel dumps via SSH to the specified remote location.
|
NFS
|
Exports kernel dumps to the specified NFS share.
|
Procedure 7.17. Configuring Kernel Dumps
- Select an option for storing kernel dumps:
Disable
To disable kernel dumps, select, and press the space bar.Local
Select the Local option and press the space bar to store kernel dumps on the local system. This is the default option.SSH
- Select the SSH option and press the space bar to export kernel dumps via SSH.
- Enter the location in which kernel dumps will be stored in the SSH Location (root@example.com) field.
- Enter an SSH Key URL (optional).
NFS
- Select the NFS option and press the space bar to export kernel dumps to an NFS share.
- Enter the location in which kernel dumps will be stored in the NFS Location (example.com:/var/crash) field.
- Selectand press Enter.
7.5.11. The Diagnostics Screen
7.5.12. The Performance Screen
virtual-host
profile is used by default. For Red Hat Enterprise Linux 7 profiles, see Tuned-adm in the Red Hat Enterprise Linux 7 Power Management Guide for more information.
Tuned Profile | Description |
---|---|
|
The system is disabled from using any tuned profile.
|
|
Based on the enterprise-storage profile, virtual-host decreases the swappiness of virtual memory and enables more aggressive writeback of dirty pages.
|
|
A profile optimized for virtual machines.
|
|
A server profile for typical throughput performance tuning.
|
|
A strong power-saving profile directed at machines with classic hard disks.
|
|
A power-saving profile directed at server systems.
|
|
A server profile for typical latency performance tuning.
|
|
A high-impact power-saving profile directed at laptops running on battery.
|
|
A medium-impact power-saving profile directed at laptops running on AC.
|
|
A server profile to improve throughput performance for enterprise-sized server configurations.
|
|
A power-saving profile directed at desktop systems.
|
|
The default power-saving profile. This is the most basic power-saving profile. It only enables the disk and CPU plug-ins.
|