mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 11. Creating a customized RHEL bare metal image by using Insights image builder You can create customized RHEL ISO system images by using the Insights image builder. You can then download these images and install them on a bare metal system according to your requirements. 11.1. Creating a customized RHEL ISO system image by using Insights image builder Complete the following steps to create customized RHEL ISO images by using the Insights image builder. Procedure Access Insights image builder on the browser. The Insights image builder dashboard opens. Click Create image . The Create image dialog wizard opens. On the Image output page, complete the following steps: From the Release list, select the Release that you want to use: for example, choose Red Hat Enterprise Linux (RHEL). From the Select target environments option, select Bare metal - Installer. Click . On the Registration page, select the type of registration that you want to use. You can select from these options: Register images with Red Hat : Register and connect image instances, subscriptions and insights with Red Hat. For details on how to embed an activation key and register systems on first boot, see Creating a customized system image with an embed subscription by using Insights image builder . Register image instances only : Register and connect only image instances and subscriptions with Red Hat. Register later :- Register the system after the image creation. Click . Optional: On the Packages page, add packages to your image. See Adding packages during image creation by using Insights image builder . On the Name image page, enter a name for your image and click . If you do not enter a name, you can find the image you created by its UUID. On the Review page, review the details about the image creation and click Create image . Your image is created as a .iso image. When the new image displays a Ready status in the Status column, click Download .iso image. The .iso image is saved to your system and is ready for deployment. Note The .iso images are available for 6 hours and expire after that. Ensure that you download the image to avoid losing it. 11.2. Installing the customized RHEL ISO system image to a bare metal system You can create a virtual machine (VM) from the ISO image that you created using the Insights image builder. Prerequisites You created and downloaded an ISO image by using Insights image builder. A 8 GB USB flash drive. Procedure Access the directory where you downloaded your ISO image. Place the bootable ISO image file on a USB flash drive. Connect the USB flash drive to the port of the computer you want to boot. Boot the ISO image from the USB flash drive. Perform the steps to install the customized bootable ISO image. The boot screen shows you the following options: Install Red Hat Enterprise Linux 8 Test this media & install Red Hat Enterprise Linux 8 Additional resources Booting the installation

Commands:
5.4.17. Controlling Logical Volume Activation You can flag a logical volume to be skipped during normal activation commands with the -k or --setactivationskip {y|n} option of the lvcreate or lvchange command. This flag is not applied during deactivation. You can determine whether this flag is set for a logical volume with the lvs command, which displays the k attribute as in the following example. By default, thin snapshot volumes are flagged for activation skip. You can activate a logical volume with the k attribute set by using the -K or --ignoreactivationskip option in addition to the standard -ay or --activate y option. The following command activates a thin snapshot logical volume. The persistent "activation skip" flag can be turned off when the logical volume is created by specifying the -kn or --setactivationskip n option of the lvcreate command. You can turn the flag off for an existing logical volume by specifying the -kn or --setactivationskip n option of the lvchange command. You can turn the flag on again with the -ky or --setactivationskip y option. The following command creates a snapshot logical volume without the activation skip flag The following command removes the activation skip flag from a snapshot logical volume. You can control the default activation skip setting with the auto_set_activation_skip setting in the /etc/lvm/lvm.conf file.

Commands:
lvs vg/thin1s1 LV VG Attr LSize Pool Origin thin1s1 vg Vwi---tz-k 1.00t pool0 thin1
lvchange -ay -K VG/SnapLV
lvcreate --type thin -n SnapLV -kn -s ThinLV --thinpool VG/ThinPoolLV
lvchange -kn VG/SnapLV
Chapter 1. Architectures Red Hat Enterprise Linux 7.1 is available as a single kit on the following architectures: [1] 64-bit AMD 64-bit Intel IBM POWER7+ and POWER8 (big endian) IBM POWER8 (little endian) [2] IBM System z [3] In this release, Red Hat brings together improvements for servers and systems, as well as for the overall Red Hat open source experience. 1.1. Red Hat Enterprise Linux for POWER, little endian Red Hat Enterprise Linux 7.1 introduces little endian support on IBM Power Systems servers using IBM POWER8 processors. Previously in Red Hat Enterprise Linux 7, only the big endian variant was offered for IBM Power Systems. Support for little endian on POWER8-based servers aims to improve portability of applications between 64-bit Intel compatible systems ( x86_64 ) and IBM Power Systems. Separate installation media are offered for installing Red Hat Enterprise Linux on IBM Power Systems servers in little endian mode. These media are available from the Downloads section of the Red Hat Customer Portal . Only IBM POWER8 processor-based servers are supported with Red Hat Enterprise Linux for POWER, little endian. Currently, Red Hat Enterprise Linux for POWER, little endian is supported only as a KVM guest under Red Hat Enteprise Virtualization for Power . Installation on bare metal hardware is currently not supported. The GRUB2 boot loader is used on the installation media and for network boot. The Installation Guide has been updated with instructions for setting up a network boot server for IBM Power Systems clients using GRUB2 . All software packages for IBM Power Systems are available for both the little endian and the big endian variant of Red Hat Enterprise Linux for POWER. Packages built for Red Hat Enterprise Linux for POWER, little endian use the the ppc64le architecture code - for example, gcc-4.8.3-9.ael7b.ppc64le.rpm . [1] Note that the Red Hat Enterprise Linux 7.1 installation is supported only on 64-bit hardware. Red Hat Enterprise Linux 7.1 is able to run 32-bit operating systems, including versions of Red Hat Enterprise Linux, as virtual machines. [2] Red Hat Enterprise Linux 7.1 (little endian) is currently only supported as a KVM guest under Red Hat Enteprise Virtualization for Power and PowerVM hypervisors. [3] Note that Red Hat Enterprise Linux 7.1 supports IBM zEnterprise 196 hardware or later; IBM System z10 mainframe systems are no longer supported and will not boot Red Hat Enterprise Linux 7.1.

Commands:
5.7. Manually Unconfiguring Client Machines A machine may need to be removed from one IdM domain and moved to another domain or a virtual machine may be copied. There are a number of different situations where an IdM client needs to be reconfigured. The easiest solution is to uninstall the client and then configure it afresh. Use the --updatedns option, as when installing a client, to update the domain DNS configuration automatically. If it is not possible to uninstall the client directly, then the IdM configuration can be manually removed from the client system. Warning When a machine is unenrolled, the procedure cannot be undone. The machine can only be enrolled again. On the client, remove the old hostname from the main keytab. This can be done by removing every principal in the realm or by removing specific principals. For example, to remove all principals: To remove specific principals: On the client system, disable tracking in certmonger for every certificate. Each certificate must be removed from tracking individually. First, list every certificate being tracked, and extract the database and nickname for each certificate. The number of certificates depends on the configured services for the host. Then, disable tracking for each. For example: On the IdM server, remove the old host from the IdM DNS domain. While this is optional, it cleans up the old IdM entries associated with the system and allows it to be re-enrolled cleanly at a later time. If the system should be re-added to a new IdM domain - such as a virtual machine which was moved from one location to another - then the system can be rejoined to IdM using the ipa-join command on the client system.

Commands:
ipa-client-install --uninstall --updatedns
[jsmith@client ~]USD ipa-rmkeytab -k /etc/krb5.keytab -r EXAMPLE.COM
[jsmith@client ~]USD ipa-rmkeytab -k /etc/krb5.keytab -p host/server.example.com@EXAMPLE.COM
[jsmith@client ~]USD ipa-getcert list
[jsmith@client ~]USD ipa-getcert stop-tracking -n "Server-Cert" -d /etc/httpd/alias
[jsmith@server ~]USD kinit admin [jsmith@server ~]USD ipa host-del server.example.com
[jsmith@client ~]USD ipa-join
8.5. Remediating the System to Align with a Specific Baseline Using the SSG Ansible Playbook Use this procedure to remediate your system with a specific baseline using the Ansible playbook file from the SCAP Security Guide project. This example uses the Protection Profile for General Purpose Operating Systems (OSPP). Warning If not used carefully, running the system evaluation with the Remediate option enabled might render the system non-functional. Red Hat does not provide any automated method to revert changes made by security-hardening remediations. Remediations are supported on RHEL systems in the default configuration. If your system has been altered after the installation, running remediation might not make it compliant with the required security profile. Prerequisites The scap-security-guide package is installed on your RHEL 7 system. The ansible package is installed. See the Ansible Installation Guide for more information. Procedure Remediate your system to align with OSPP using Ansible: Restart the system. Verification Evaluate compliance of the system with the OSPP profile, and save scan results in the ospp_report.html file: Additional Resources scap-security-guide(8) and oscap(8) man pages Ansible Documentation

Commands:
~]# ansible-playbook -i localhost, -c local /usr/share/scap-security-guide/ansible/ssg-rhel7-role-ospp.yml
~]# oscap xccdf eval --profile ospp --report ospp_report.html /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml
14.8.2. make_smbcodepage make_smbcodepage <c|d> <codepage_number> <inputfile> <outputfile> The make_smbcodepage program compiles a binary codepage file from a text-format definition. The reverse is also allowed by decompiling a binary codepage file to a text-format definition. This obsolete program is part of the internationalization features of versions of Samba which are included by default with the current version of Samba.

Commands:
A.5. Kerberos Errors Kerberos errors frequently become apparent when trying to connect to the realm using kinit or a similar client. For information related to Kerberos, first check the Kerberos manpages, help files, and other resources. Important Identity Management has its own command-line tools to use to manage Kerberos policies. Do not use kadmin or kadmin.local to manage IdM Kerberos settings. There are several places to look for Kerberos error log information: For kinit problems or other Kerberos server problems, look at the KDC log in /var/log/krb5kdc.log . For IdM-specific errors, look in /var/log/httpd/error_log . The IdM logs, both for the server and for IdM-associated services, are covered in Section 28.1.4, "Checking IdM Server Logs" . A.5.1. Problems making connections with SSH when using GSS-API If there are bad reverse DNS entries in the DNS configuration, then it may not be possible to log into IdM resources using SSH. When SSH attempts to connect to a resource using GSS-API as its security method, GSS-API first checks the DNS records. The bad records prevent SSH from locating the resource. It is possible to disable reverse DNS lookups in the SSH configuration. Rather than using reverse DNS records, SSH passes the given username directly to GSS-API. To disable reverse DNS lookups with SSH, add or edit the GSSAPITrustDNS directive and set the value to no . A.5.2. There are problems connecting to an NFS server after changing a keytab Clients attempting to mount NFS exports rely on the existence of a valid principal and secret key on both the NFS server and the client host. Clients themselves should not have access to the NFS keytab. The ticket for the NFS connection will be given to clients from the KDC. Failure to export an updated keytab can cause problems that are difficult to isolate. For example, existing service connections may continue to function, but no new connections may be possible.

Commands:
vim /etc/ssh/ssh_config GSSAPITrustDNS no
Chapter 5. Installing the Apache HTTP Server on RHEL 9 by using Application Streams The Red Hat Enterprise Linux (RHEL) Application Streams feature delivers and updates multiple versions of user-space components such as applications, runtime languages, and databases in an AppStream repository. On RHEL 9, if you want to install the Apache HTTP Server from an RPM package, you must install the RHEL distribution of the Apache HTTP Server by using Application Streams. Important Red Hat JBoss Core Services (JBCS) does not provide an RPM distribution of the Apache HTTP Server for RHEL 9. The Apache HTTP Server httpd package that the RHEL AppStream repository provides is the only supported RPM distribution of the Apache HTTP Server for RHEL 9 systems. Note Installing the RHEL distribution of the Apache HTTP Server does not automatically install the mod_jk and mod_proxy_cluster packages. For more information about installing mod_jk and mod_proxy_cluster from RPM packages on RHEL 9, see the Apache HTTP Server Connectors and Load Balancing Guide . 5.1. Installation of the Apache HTTP Server when using Application Streams You can install the RHEL 9 distribution of the Apache HTTP Server from an RPM package by using the standard dnf install command. You can subsequently start and stop the Apache HTTP Server from the command line as the root user. Alternatively, you can enable the Apache HTTP Server to start automatically at system startup. For more information about installing, starting, and stopping the RHEL distribution of the Apache HTTP Server, see Setting up the Apache HTTP web server . Additional resources Application Streams Managing software with the DNF tool 5.2. SELinux policies for the Apache HTTP Server You can use Security-Enhanced Linux (SELinux) policies to define access controls for the Apache HTTP Server. These policies are a set of rules that determine access rights to the product. The Apache HTTP Server has an SELinux type name of httpd_t . By default, the Apache HTTP Server can access files and directories in /var/www/html and other web server directories that have an SELinux type context of httpd_sys_content_t . You can also customize the SELinux policy for the Apache HTTP Server if you want to use a non-standard configuration. Additional resources Using SELinux Customizing the SElinux policy for the Apache HTTP Server in a non-standard configuration

Commands:
Chapter 18. Log Record Fields The following fields can be present in log records exported by the logging subsystem. Although log records are typically formatted as JSON objects, the same data model can be applied to other encodings. To search these fields from Elasticsearch and Kibana, use the full dotted field name when searching. For example, with an Elasticsearch /_search URL , to look for a Kubernetes pod name, use /_search/q=kubernetes.pod_name:name-of-my-pod . The top level fields may be present in every record.

Commands:
Appendix A. General configuration options These are the general configuration options for Ceph. Note Typically, these will be set automatically by deployment tools, such as cephadm . fsid Description The file system ID. One per cluster. Type UUID Required No. Default N/A. Usually generated by deployment tools. admin_socket Description The socket for executing administrative commands on a daemon, irrespective of whether Ceph monitors have established a quorum. Type String Required No Default /var/run/ceph/USDcluster-USDname.asok pid_file Description The file in which the monitor or OSD will write its PID. For instance, /var/run/USDcluster/USDtype.USDid.pid will create /var/run/ceph/mon.a.pid for the mon with id a running in the ceph cluster. The pid file is removed when the daemon stops gracefully. If the process is not daemonized (meaning it runs with the -f or -d option), the pid file is not created. Type String Required No Default No chdir Description The directory Ceph daemons change to once they are up and running. Default / directory recommended. Type String Required No Default / max_open_files Description If set, when the Red Hat Ceph Storage cluster starts, Ceph sets the max_open_fds at the OS level (that is, the max # of file descriptors). It helps prevent Ceph OSDs from running out of file descriptors. Type 64-bit Integer Required No Default 0 fatal_signal_handlers Description If set, we will install signal handlers for SEGV, ABRT, BUS, ILL, FPE, XCPU, XFSZ, SYS signals to generate a useful log message. Type Boolean Default true

Commands:
5.12. Tools coolkey component, BZ# 906537 Personal Identity Verification (PIV) Endpoint Cards which support both CAC and PIV interfaces might not work with the latest coolkey update; some signature operations like PKINIT can fail. To work around this problem, downgrade coolkey to the version shipped with Red Hat Enterprise Linux 6.3. libreport component Even if the stored credentials are used , the report-gtk utility can report the following error message: To work around this problem, close the dialog window; the Login=<rhn-user> and Password=<rhn-password> credentials in the /etc/libreport/plugins/rhtsupport.conf will be used in the same way they are used by report-rhtsupport . For more information, refer to this Knowledge Base article. vlock component When a user password is used to lock a console with vlock , the console can only be unlocked with the user password, not the root password. That is, even if the first inserted password is incorrect, and the user is prompted to provide the root password, entering the root password fails with an error message. libreoffice component Libreoffice contains a number of harmless files used for testing purposes. However, on Microsoft Windows system, these files can trigger false positive alerts on various anti-virus software, such as Microsoft Security Essentials. For example, the alerts can be triggered when scanning the Red Hat Enterprise Linux 6 ISO file. gnome-power-manager component When the computer runs on battery, custom brightness level is not remembered and restored if power saving features like "dim display when idle" or "reduce backlight brightness when idle" are enabled. rsyslog component rsyslog does not reload its configuration after a SIGHUP signal is issued. To reload the configuration, the rsyslog daemon needs to be restarted: parted component The parted utility in Red Hat Enterprise Linux 6 cannot handle Extended Address Volumes (EAV) Direct Access Storage Devices (DASD) that have more than 65535 cylinders. Consequently, EAV DASD drives cannot be partitioned using parted , and installation on EAV DASD drives will fail. To work around this issue, complete the installation on a non EAV DASD drive, then add the EAV device after the installation using the tools provided in the s390-utils package.

Commands:
Wrong settings detected for Red Hat Customer Support [..]
~]# service rsyslog restart
9.2. REST Properties The following properties can be specified on a JBoss Data Virtualization virtual procedure. Property Name Description Is Required Allowed Values METHOD HTTP Method to use Yes GET | POST| PUT | DELETE URI URI of procedure Yes ex:/procedure PRODUCES Type of content produced by the service no xml | json | plain | any text CHARSET When procedure returns Blob, and content type text based, this character set to used to convert the data no US-ASCII | UTF-8 The above properties must be defined with NAMESPACE 'http://teiid.org/rest' on the metadata. Here is an example VDB that defines the REST based service.

Commands:
Chapter 8. Certified SAP applications on RHEL 9 SAP Max DB 7.9.10.02 and later (See SAP Note 1444241 ) SAP ASE 16 (See SAP Note 2489781 ) SAP HANA 2.0 SPS05 and later (See SAP Note 2235581 ) SAP BI 4.3 and later (See SAP Note 1338845 ) SAP NetWeaver (See SAP Note 2772999 ) In general, SAP documents support of their products for certain versions of Red Hat Linux Enterprise in their SAP Product Availability Matrix .

Commands:
Chapter 7. Preparing network functions virtualization (NFV) If you use network functions virtualization (NFV), you must complete some preparation for the overcloud upgrade. 7.1. Network functions virtualization (NFV) environment files In a typical NFV-based environment, you can enable services such as the following: Single-root input/output virtualization (SR-IOV) Data Plane Development Kit (DPDK) You do not require any specific reconfiguration to these services to accommodate the upgrade to Red Hat OpenStack Platform 17.1. However, ensure that the environment files that enable your NFV functionality meet the following requirements: The default environment files to enable NFV features are located in the environments/services directory of the Red Hat OpenStack Platform 17.1 openstack-tripleo-heat-templates collection. If you include the default NFV environment files from openstack-tripleo-heat-templates with your Red Hat OpenStack Platform 16.2 deployment, verify the correct environment file location for the respective feature in Red Hat OpenStack Platform 17.1: Open vSwitch (OVS) networking and SR-IOV: /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-sriov.yaml Open vSwitch (OVS) networking and DPDK: /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs-dpdk.yaml To maintain OVS compatibility during the upgrade from Red Hat OpenStack Platform 16.2 to Red Hat OpenStack Platform 17.1, you must include the /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs.yaml environment file. When running deployment and upgrade commands that involve environment files, you must include any NFV-related environment files after the neutron-ovs.yaml file. For example, when running openstack overcloud upgrade prepare with OVS and NFV environment files, include the files in the following order: The OVS environment file The SR-IOV environment file The DPDK environment file Note There is a migration constraint for NFV workloads: you cannot live migrate instances from OVS-DPDK Compute nodes during an upgrade. Alternatively, you can cold migrate instances from OVS-DPDK Compute nodes during an upgrade.

Commands:
openstack overcloud upgrade prepare -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-sriov.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs-dpdk.yaml