[ Pobierz całość w formacie PDF ]
Kernel Dump screen provides for configuration of this facility.
1. Kernel Dump Configuration
Crash dumps generated by kdump are exported over NFS or SSH. Select the desired transfer
method and press Space to enable it. Alternatively, to keep the kernel dumps on the hypevisor's
local storage, select Restore (local) and press Space to enable it. This action also disables
any previously configured kernel dump export options.
Where export of the kernel dumps over NFS or SSH is chosen a location to which the kdump files
will be exported to must also be specified.
a. NFS location
Set the NFS location to which crash logs should be exported in the NFS Location field.
The NFS Location should be the full NFS path which includes fully qualified domain name
and directory path.
57
Red Hat Enterprise Linux 6 Hypervisor Deployment Guide
Example 5.4 . NFS Location
example.redhat.com:/var/crash
b. SSH location
Set the SSH location to which crash logs should be exported in the SSH Location field.
The SSH Location should be the full SSH login which includes the fully qualified domain
name and username.
Example 5.5. SSH Location
root@example.redhat.com
2. Save Configuration
To save the configuration the user must select and press Enter.
The Kernel Dump configuration has been updated and kernel dumps will be exported to the remote
server(s) specified.
5.9. Remote Storage
The Hypervisor supports the use of a remote iSCSI initiator for storage. The iSCSI initiator to use is set
on the Remote Storage screen.
Procedure 5.7. Remote Storage Configuration
1. iSCSI Initiator Name
Enter the initiator name in the iSCSI Initiator Name field. The iSCSI initiator name is
expected to take the form of an iSCSI Qualified Name (IQN). This format is defined by RFC 3720,
which is available at http://tools.ietf.org/html/rfc3720.
The IQN is made up of the following elements, separated by the . character:
the literal string iqn,
the date that the naming authority took control of the domain in yyyy-mm format,
the reversed domain name - demo.redhat.com becomes com.redhat.demo, and
optionally, a storage target name as specified by the naming authority - preceded by a colon.
Example 5.6. iSCSI Initiator Name
iqn.2011-08.com.redhat.demo:target1
2. Set the NFSv4 Domain
Defines the local NFSv4 domain name. An NFSv4 domain is a namespace with a unique username
to user identifier and groupname to group identifier mapping.
3. Save Configuration
To save the configuration the user must select and press Enter.
The Remote Storage configuration has been updated.
58
Chapter 5. Configuration
5.10. CIM (Common Information Model)
Enabling and configuring CIM attaches the Hypervisor to your pre-existing CIM management
infrastructure, allowing your infrastructure to monitor this Hypervisor's virtual machines.
Example 5.7. CIM Configuration
CIM Configuration
[ ] Enable CIM
CIM Access
Password: ______________
Confirm Password: ______________
5.11. RHEV-M
To configure the Hypervisor to connect to the Red Hat Enterprise Virtualization Manager, you must
provide the details of the server on which the manager resides. The settings entered on the Hypervisor
must match those that were used during installation of the Red Hat Enterprise Virtualization Manager.
Important
Setting a password on the RHEV-M configuration screen sets the hypervisor's root password
and enables SSH password authentication. Once the hypervisor has successfully been added to
the manager it is recommended that SSH password authentication is disabled.
Procedure 5.8. RHEV-M Configuration
1. A. Configuration Using a Management Server Address
a. Enter the IP address or fully qualified domain name of the manager in the Management
Server field.
b. Enter the management server port in the Management Server Port field. The
default value is 44 3. Where a different port was selected during Red Hat Enterprise
Virtualization Manager installation then it should be specified here, replacing the default
value.
c. Enable the Verify RHEVM Certificate option if you wish to verify that the finger
print of the certificate retrieved from the management server you specified is correct.
The value that the certificate finger print should be compared against is returned at the
end of Red Hat Enterprise Virtualization Manager installation.
d. Leave the Password and Confirm Password fields blank. These fields are not
required if the address of the management server is known.
B. Configuration Using a Password
a. Enter a password in the Password field. 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.
59
Red Hat Enterprise Linux 6 Hypervisor Deployment Guide
b. Re-enter the password in the Confirm Password field.
c. 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.
2. Save Configuration
To save the configuration the user must select and press Enter.
The RHEV-M configuration has been updated.
If you need further assistance with this task, refer to the Red Hat Enterprise Virtualization Administration
Guide chapter on Red Hat Enterprise Virtualization Hosts.
5.12. Plugins
This screen lists any modifications made with edit-node prior to installation, such as driver update
packages. Select to view more details about the available plugins.
5.13. Red Hat Network
Virtual machines running on the hypervisor may need to consume Red Hat Enterprise Linux virtualization
entitlements. Where this is the case the hypervisor must be registered to Red Hat Network or a Satellite
server. The hypervisor is able to connect to these services via a HTTP proxy where one is in use.
Note that when new versions of the hypervisor itself become available they are installed from the Red [ Pobierz całość w formacie PDF ]
zanotowane.pl doc.pisz.pl pdf.pisz.pl chiara76.opx.pl
Kernel Dump screen provides for configuration of this facility.
1. Kernel Dump Configuration
Crash dumps generated by kdump are exported over NFS or SSH. Select the desired transfer
method and press Space to enable it. Alternatively, to keep the kernel dumps on the hypevisor's
local storage, select Restore (local) and press Space to enable it. This action also disables
any previously configured kernel dump export options.
Where export of the kernel dumps over NFS or SSH is chosen a location to which the kdump files
will be exported to must also be specified.
a. NFS location
Set the NFS location to which crash logs should be exported in the NFS Location field.
The NFS Location should be the full NFS path which includes fully qualified domain name
and directory path.
57
Red Hat Enterprise Linux 6 Hypervisor Deployment Guide
Example 5.4 . NFS Location
example.redhat.com:/var/crash
b. SSH location
Set the SSH location to which crash logs should be exported in the SSH Location field.
The SSH Location should be the full SSH login which includes the fully qualified domain
name and username.
Example 5.5. SSH Location
root@example.redhat.com
2. Save Configuration
To save the configuration the user must select and press Enter.
The Kernel Dump configuration has been updated and kernel dumps will be exported to the remote
server(s) specified.
5.9. Remote Storage
The Hypervisor supports the use of a remote iSCSI initiator for storage. The iSCSI initiator to use is set
on the Remote Storage screen.
Procedure 5.7. Remote Storage Configuration
1. iSCSI Initiator Name
Enter the initiator name in the iSCSI Initiator Name field. The iSCSI initiator name is
expected to take the form of an iSCSI Qualified Name (IQN). This format is defined by RFC 3720,
which is available at http://tools.ietf.org/html/rfc3720.
The IQN is made up of the following elements, separated by the . character:
the literal string iqn,
the date that the naming authority took control of the domain in yyyy-mm format,
the reversed domain name - demo.redhat.com becomes com.redhat.demo, and
optionally, a storage target name as specified by the naming authority - preceded by a colon.
Example 5.6. iSCSI Initiator Name
iqn.2011-08.com.redhat.demo:target1
2. Set the NFSv4 Domain
Defines the local NFSv4 domain name. An NFSv4 domain is a namespace with a unique username
to user identifier and groupname to group identifier mapping.
3. Save Configuration
To save the configuration the user must select and press Enter.
The Remote Storage configuration has been updated.
58
Chapter 5. Configuration
5.10. CIM (Common Information Model)
Enabling and configuring CIM attaches the Hypervisor to your pre-existing CIM management
infrastructure, allowing your infrastructure to monitor this Hypervisor's virtual machines.
Example 5.7. CIM Configuration
CIM Configuration
[ ] Enable CIM
CIM Access
Password: ______________
Confirm Password: ______________
5.11. RHEV-M
To configure the Hypervisor to connect to the Red Hat Enterprise Virtualization Manager, you must
provide the details of the server on which the manager resides. The settings entered on the Hypervisor
must match those that were used during installation of the Red Hat Enterprise Virtualization Manager.
Important
Setting a password on the RHEV-M configuration screen sets the hypervisor's root password
and enables SSH password authentication. Once the hypervisor has successfully been added to
the manager it is recommended that SSH password authentication is disabled.
Procedure 5.8. RHEV-M Configuration
1. A. Configuration Using a Management Server Address
a. Enter the IP address or fully qualified domain name of the manager in the Management
Server field.
b. Enter the management server port in the Management Server Port field. The
default value is 44 3. Where a different port was selected during Red Hat Enterprise
Virtualization Manager installation then it should be specified here, replacing the default
value.
c. Enable the Verify RHEVM Certificate option if you wish to verify that the finger
print of the certificate retrieved from the management server you specified is correct.
The value that the certificate finger print should be compared against is returned at the
end of Red Hat Enterprise Virtualization Manager installation.
d. Leave the Password and Confirm Password fields blank. These fields are not
required if the address of the management server is known.
B. Configuration Using a Password
a. Enter a password in the Password field. 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.
59
Red Hat Enterprise Linux 6 Hypervisor Deployment Guide
b. Re-enter the password in the Confirm Password field.
c. 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.
2. Save Configuration
To save the configuration the user must select and press Enter.
The RHEV-M configuration has been updated.
If you need further assistance with this task, refer to the Red Hat Enterprise Virtualization Administration
Guide chapter on Red Hat Enterprise Virtualization Hosts.
5.12. Plugins
This screen lists any modifications made with edit-node prior to installation, such as driver update
packages. Select to view more details about the available plugins.
5.13. Red Hat Network
Virtual machines running on the hypervisor may need to consume Red Hat Enterprise Linux virtualization
entitlements. Where this is the case the hypervisor must be registered to Red Hat Network or a Satellite
server. The hypervisor is able to connect to these services via a HTTP proxy where one is in use.
Note that when new versions of the hypervisor itself become available they are installed from the Red [ Pobierz całość w formacie PDF ]