mtpti5iD/redhat-docs_dataset huggingface dataset:
17.4.5. Problems When You Try to Log In If you did not create a user account in the firstboot screens, switch to a console by pressing Ctrl + Alt + F2 , log in as root and use the password you assigned to root. If you cannot remember your root password, boot your system as linux single . Once you have booted into single user mode and have access to the # prompt, you must type passwd root , which allows you to enter a new password for root. At this point you can type shutdown -r now to reboot the system with the new root password. If you cannot remember your user account password, you must become root. To become root, type su - and enter your root password when prompted. Then, type passwd <username> . This allows you to enter a new password for the specified user account. If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at:

Commands:
https://hardware.redhat.com/
Chapter 1. Installation methods You can install a cluster on IBM Power(R) infrastructure that you provision, by using one of the following methods: Installing a cluster on IBM Power(R) : You can install OpenShift Container Platform on IBM Power(R) infrastructure that you provision. Installing a cluster on IBM Power(R) in a restricted network : You can install OpenShift Container Platform on IBM Power(R) infrastructure that you provision in a restricted or disconnected network, by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.

Commands:
8.122. netcf 8.122.1. RHBA-2013:1660 - netcf bug fix update Updated netcf packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The netcf packages contain a library for modifying the network configuration of a system. Network configuration is expressed in a platform-independent XML format, which netcf translates into changes to the system's "native" network configuration files. Bug Fixes BZ# 844578 When using the "virsh iface-start" or "ncftool ifup" command to start a disconnected interface configured to use a DHCP server, the netcf library reported a failure. However, the subsequent list of all interfaces showed the interface as "active". After this update, netcf only reports "active" interface status when the interface is marked both "UP" and "RUNNING" by the "ifconfig" utility and if any attempt to start the interface was successful. BZ# 848722 Previously, attempts to define an interface with a netmask higher than 24 bits failed. This bug has been fixed and it is now possible to define interfaces with netmasks of up to 30 bits. Users of netcf are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 4. Unsupported and deprecated features Cryostat 2.2 removes some features because of their high maintenance costs, low community interest, and better alternative solutions. Removed support for OpenShift Operator CRDs You cannot use the FlightRecorder or the Recording custom resources definitions (CRD) with Cryostat 2.2. Cryostat includes the HTTP REST API and the GraphQL API that provide the same functionality as the OpenShift Operator's CRDs. Additionally, the Cryostat APIs include more features than these CRDs.

Commands:
20.3.3. Channels After a successful authentication over the SSH transport layer, multiple channels are opened via a technique called multiplexing [9] . Each of these channels handles communication for different terminal sessions and for forwarded X11 sessions. Both clients and servers can create a new channel. Each channel is then assigned a different number on each end of the connection. When the client attempts to open a new channel, the clients sends the channel number along with the request. This information is stored by the server and is used to direct communication to that channel. This is done so that different types of sessions do not affect one another and so that when a given session ends, its channel can be closed without disrupting the primary SSH connection. Channels also support flow-control , which allows them to send and receive data in an orderly fashion. In this way, data is not sent over the channel until the client receives a message that the channel is open. The client and server negotiate the characteristics of each channel automatically, depending on the type of service the client requests and the way the user is connected to the network. This allows great flexibility in handling different types of remote connections without having to change the basic infrastructure of the protocol. [9] A multiplexed connection consists of several signals being sent over a shared, common medium. With SSH, different channels are sent over a common secure connection.

Commands:
Chapter 7. Federal Information Processing Standard (FIPS) Red Hat Ceph Storage uses FIPS validated cryptography modules when run on the latest certified Red Hat Enterprise Linux version. Enable FIPS mode on Red Hat Enterprise Linux either during system installation or after it. For container deployments, follow the instructions in the Red Hat Enterprise Linux 9 Security Hardening Guide . Additional Resources Refer to the US Government Standards to know the latest information on FIPS validations. Refer to the Red Hat Ceph Storage Compatibility Guide .

Commands:
7.3.2.2.3. Optimising for concurrency Unlike other file systems, XFS can perform many types of allocation and deallocation operations concurrently provided that the operations are occurring on non-shared objects. Allocation or deallocation of extents can occur concurrently provided that the concurrent operations occur in different allocation groups. Similarly, allocation or deallocation of inodes can occur concurrently provided that the concurrent operations affect different allocation groups. The number of allocation groups becomes important when using machines with a high CPU count and multi-threaded applications that attempt to perform operations concurrently. If only four allocation groups exist, then sustained, parallel metadata operations will only scale as far as those four CPUs (the concurrency limit provided by the system). For small file systems, ensure that the number of allocation groups is supported by the concurrency provided by the system. For large file systems (tens of terabytes and larger) the default formatting options generally create sufficient allocation groups to avoid limiting concurrency. Applications must be aware of single points of contention in order to use the parallelism inherent in the structure of the XFS file system. It is not possible to modify a directory concurrently, so applications that create and remove large numbers of files should avoid storing all files in a single directory. Each directory created is placed in a different allocation group, so techniques such as hashing files over multiple sub-directories provide a more scalable storage pattern compared to using a single large directory.

Commands:
7.73. hivex 7.73.1. RHSA-2015:1378 - Moderate: hivex security and bug fix update Updated hivex packages that fix one security issue and one bug are now available for Red Hat Enterprise Linux 6. Red Hat Product Security has rated this update as having Moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Hivex is a library that can read and write Hive files, undocumented binary files that Windows uses to store the Windows Registry on disk. Security Fix CVE-2014-9273 It was found that hivex attempted to read, and possibly write, beyond its allocated buffer when reading a hive file with a very small size or with a truncated or improperly formatted content. An attacker able to supply a specially crafted hive file to an application using the hivex library could possibly use this flaw to execute arbitrary code with the privileges of the user running that application. Red Hat would like to thank Mahmoud Al-Qudsi of NeoSmart Technologies for reporting this issue. Bug Fix BZ# 1164693 The hivex(3) man page previously contained a typographical error. This update fixes the typo. Red Hat would like to thank Mahmoud Al-Qudsi of NeoSmart Technologies for reporting this issue. All hivex users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

Commands:
7.225. virt-manager 7.225.1. RHBA-2015:1373 - virt-manager bug fix update Updated virt-manager packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Virtual Machine Manager (virt-manager) is a graphical tool for administering virtual machines for KVM, Xen, and QEMU. The virt-manager utility uses the libvirt API and can start, stop, add or remove virtualized devices, connect to a graphical or serial console, and view resource usage statistics for existing virtualized guests on local or remote machines. Bug Fixes BZ# 1174464 Previously, when using the virt-manager tool to install a guest and checking the "Virtualization tools" box in the "Customize package" menu, virt-manager terminated unexpectedly after the installation was completed and the guest was rebooted. This update fixes the underlying code, and virt-manager no longer crashes in the described scenario. BZ# 1190641 Prior to this update, when using the virt-manager GUI to change the number of CPU threads on the guest, the "Apply" and "Cancel" buttons incorrectly remained disabled. With this update, the signal and callback names in virt-manager have been corrected to properly parse changes to the cpu-thread, and the problem no longer occurs. Users of virt-manager are advised to upgrade to these updated packages, which fix these bugs.

Commands:
B.5. Validation Preferences Validation Preferences provide a way to customize the severity of some of the rules checked during model validation. The Validation preference pages, shown below, include the validation preferences for Core, Relational, XML and XSD (XML Schema) models. Figure B.7. Core Model Validation Preferences Panel Figure B.8. Relational Model Validation Preferences Panel Figure B.9. XML Document Model Validation Preferences Panel Figure B.10. XSD Schema Model Validation Preferences Panel Note Increasing the severity level to error will prevent you from testing your VDB or deploying a web service if violations of that preference are found during validation.

Commands:
Chapter 19. Managing Guests with the Virtual Machine Manager (virt-manager) This chapter describes the Virtual Machine Manager ( virt-manager ) windows, dialog boxes, and various GUI controls. virt-manager provides a graphical view of hypervisors and guests on your host system and on remote host systems. virt-manager can perform virtualization management tasks, including: defining and creating guests, assigning memory, assigning virtual CPUs, monitoring operational performance, saving and restoring, pausing and resuming, and shutting down and starting guests, links to the textual and graphical consoles, and live and offline migrations. Important It is important to note which user you are using. If you create a guest virtual machine with one user, you will not be able to retrieve information about it using another user. This is especially important when you create a virtual machine in virt-manager. The default user is root in that case unless otherwise specified. Should you have a case where you cannot list the virtual machine using the virsh list --all command, it is most likely due to you running the command using a different user than you used to create the virtual machine. 19.1. Starting virt-manager To start virt-manager session open the Applications menu, then the System Tools menu and select Virtual Machine Manager ( virt-manager ). The virt-manager main window appears. Figure 19.1. Starting virt-manager Alternatively, virt-manager can be started remotely using ssh as demonstrated in the following command: Using ssh to manage virtual machines and hosts is discussed further in Section 18.2, "Remote Management with SSH" .

Commands:
ssh -X host's address virt-manager
B.57. nss B.57.1. RHSA-2010:0862 - Low: nss security update Updated nss packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Network Security Services (NSS) is a set of libraries designed to support the development of security-enabled client and server applications. CVE-2010-3170 A flaw was found in the way NSS matched SSL certificates when the certificates had a Common Name containing a wildcard and a partial IP address. NSS incorrectly accepted connections to IP addresses that fell within the SSL certificate's wildcard range as valid SSL connections, possibly allowing an attacker to conduct a man-in-the-middle attack. All NSS users should upgrade to these updated packages, which provide NSS version 3.12.8 to resolve this issue. After installing the update, applications using NSS must be restarted for the changes to take effect.

Commands:
Chapter 4. Analyzing and triaging your compliance reports The compliance service displays data for each policy and system registered (and reporting data) to the service. This can be a lot of data, most of which might not be relevant to your immediate goals. The following sections discuss ways to refine the bulk of compliance service data- in Reports, SCAP policies, and Systems- to focus on the systems or policies that matter the most to you. The compliance service enables users to set filters on lists of systems, rules, and policies. Like other Insights for Red Hat Enterprise Linux services, the compliance service also enables filtering by system-group tags. However, because compliance-registered systems use a different reporting mechanism, the tag filters must be set directly in lists of systems in the compliance UI views, rather than from the global, Filter by status dropdown used elsewhere in the Insights application. Important To see accurate data for your systems, always run insights-client --compliance on each system prior to viewing the results in the UI. 4.1. Compliance reports From Security > Compliance > Reports , use the following primary and secondary filters to focus on a specific or narrow set of reports: Policy name. Search for a policy by name. Policy type. Select from the policy types configured for your infrastructure in the compliance service. Operating system. Select one or more RHEL OS major versions. Systems meeting compliance. Show policies for which a percentage (range) of included systems are compliant. 4.2. SCAP policies From Security > Compliance > SCAP policies , use the Filter by name search box to locate a specific policy by name. Then click on the policy name to see the policy card, which includes the following information: Details. View details such as compliance threshold, business objective, OS, and SSG version. Rules. View and filter the rules included in the specific SSG version of the policy by Name, Severity and Remediation available. Then sort the results by Rule name, Severity or Ansible Playbook support. Systems. Search by system name to locate a specific system associated with the policy then click the system name to see more information about that system and issues that may affect it. 4.3. Systems The default functionality on Security > Compliance > Systems is to search by system name. Tags. Search by system group or tag name. Name. Search by system name. Policy. Search by policy name and see the systems included in that policy. Operating system. Search by RHEL OS major versions to see only RHEL 7 or RHEL 8 systems. 4.4. Searching The search function in the compliance service works in the context of the page you are viewing. SCAP Policies. Search for a specific policy by name. Systems. Search by system name, policy, or Red Hat Enterprise Linux operating system major version. Rules list (single system). The rules list search function allows you to search by the rule name or identifier. Identifiers are shown directly below the rule name.

Commands:
probe::scsi.set_state Name probe::scsi.set_state - Order SCSI device state change Synopsis scsi.set_state Values state The new state of the device old_state The current state of the device dev_id The scsi device id state_str The new state of the device, as a string old_state_str The current state of the device, as a string lun The lun number channel The channel number host_no The host number

Commands:
Assessing RHEL Configuration Issues Using the Red Hat Insights Advisor Service Red Hat Insights 1-latest Assess and monitor the configuration issues impacting your RHEL systems Red Hat Customer Content Services

Commands:
USE [master] GO CREATE LOGIN [assessmentLogin] with PASSWORD= N'<*PASSWORD*>' ALTER SERVER ROLE [sysadmin] ADD MEMBER [assessmentLogin] GO
echo "assessmentLogin" > /var/opt/mssql/secrets/assessment echo "<*PASSWORD*>" >> /var/opt/mssql/secrets/assessment
chmod 0600 /var/opt/mssql/secrets/assessment chown mssql:mssql /var/opt/mssql/secrets/assessment
yum -y install powershell
su mssql -c "/usr/bin/pwsh -Command Install-Module SqlServer"
/bin/curl -LJ0 -o /opt/mssql/bin/runassessment.ps1 https://raw.githubusercontent.com/microsoft/sql-server-samples/master/samples/manage/sql-assessment-api/RHEL/runassessment.ps1 chown mssql:mssql /opt/mssql/bin/runassessment.ps1 chmod 0700 /opt/mssql/bin/runassessment.ps1
mkdir /var/opt/mssql/log/assessments/ chown mssql:mssql /var/opt/mssql/log/assessments/ chmod 0700 /var/opt/mssql/log/assessments/
su mssql -c "pwsh -File /opt/mssql/bin/runassessment.ps1"
insights-client
cp mssql-runassessment.service /etc/systemd/system/ cp mssql-runassessment.timer /etc/systemd/system/ chmod 644 /etc/systemd/system/
systemctl enable --now mssql-runassessment.timer
insights-client --group=<name-you-choose>
tags --- group: eastern-sap name: Jane Example contact: jexample@corporate.com Zone: eastern time zone Location: - gray_rack - basement Application: SAP
tags --- group: eastern-sap location: Boston description: - RHEL8 - SAP key 4: value
insights-client
vi /etc/insights-client/tags.yaml
cat /etc/insights-client/tags.yaml group: redhat location: Brisbane/Australia description: - RHEL8 - SAP security: strict network_performance: latency
insights-client
insights-client --unregister
curl -k --user PORTALUSERNAME https://console.redhat.com/api/inventory/v1/hosts | json_pp > hosts.json
yum install perl-JSON-PP
curl -k --user PORTALUSERNAME https://console.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
curl -k --user PORTALUSERNAME -X "DELETE" https://console.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
16.5. Setting Addresses for Devices Many devices have an optional <address> sub-element which is used to describe where the device is placed on the virtual bus presented to the guest virtual machine. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. For domain XML device examples that include an <address> element, see Figure 16.9, "XML example for PCI device assignment" . Every address has a mandatory attribute type that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest virtual machine. For example, a <disk> device uses type='drive' , while a <console> device would use type='pci' on i686 or x86_64 guest virtual machine architectures. Each address type has further optional attributes that control where on the bus the device will be placed as described in the table: Table 16.1. Supported device address types Address type Description type='pci' PCI addresses have the following additional attributes: domain (a 2-byte hex integer, not currently used by qemu) bus (a hex value between 0 and 0xff, inclusive) slot (a hex value between 0x0 and 0x1f, inclusive) function (a value between 0 and 7, inclusive) multifunction controls turning on the multifunction bit for a particular slot/function in the PCI control register By default it is set to 'off', but should be set to 'on' for function 0 of a slot that will have multiple functions used. type='drive' Drive addresses have the following additional attributes: controller (a 2-digit controller number) bus (a 2-digit bus number target (a 2-digit bus number) unit (a 2-digit unit number on the bus) type='virtio-serial' Each virtio-serial address has the following additional attributes: controller (a 2-digit controller number) bus (a 2-digit bus number) slot (a 2-digit slot within the bus) type='ccid' A CCID address, for smart-cards, has the following additional attributes: bus (a 2-digit bus number) slot attribute (a 2-digit slot within the bus) type='usb' USB addresses have the following additional attributes: bus (a hex value between 0 and 0xfff, inclusive) port (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1) type='isa' ISA addresses have the following additional attributes: iobase irq

Commands:
Chapter 2. Upgrading Fuse Online From time to time, fresh application images, which incorporate patches and security fixes, are released for Fuse. You are notified of these updates through Red Hat's errata update channel. You can then upgrade your Fuse images. For OCP 4.x, use the OpenShift OperatorHub to upgrade from Fuse 7.10 to 7.11, by following the steps in Upgrading Fuse by using the OperatorHub (OCP 4.x). You should determine whether upgrading to Fuse 7.11 requires you to make changes to your existing integrations. Even if no changes are required, you must republish any running integration when you upgrade Fuse. Upgrading Fuse by using the OperatorHub (OCP 4.x) Use the OpenShift OperatorHub to upgrade from Fuse Online 7.10 to 7.11. If you want to upgrade from Fuse 7.9.x to Fuse Online 7.10.1, you must first manually upgrade to Fuse 7.10.0 as described in the Upgrading from Fuse Online 7.9.x to 7.10.1 requires manual upgrade steps release note. Fuse 7.11 requires OpenShift Container Platform (OCP) 4.6 or later. If you are using OCP 4.5 or earlier, you must upgrade to OCP 4.6 or later, if you want to upgrade to Fuse 7.11 . On OCP 4.9, When you upgrade to 7.11, the following warning is displayed during the Fuse Operator upgrade process: W1219 18:38:58.064578 1 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress This warning appears because clients (that Fuse uses for the Kubernetes/OpenShift API initialization code) access a deprecated Ingress version. This warning is not an indicator of complete use of deprecated APIs and there is no issue with upgrading to Fuse 7.11. The upgrade process from a Fuse Online 7.10 or an earlier version to a newer Fuse Online 7.11 version depends on the Approval Strategy that you selected when you installed Fuse Online: For Automatic updates, when a new version of the Fuse operator is available, the OpenShift Operator Lifecycle Manager (OLM) automatically upgrades the running instance of the Fuse Online without human intervention. For Manual updates, when a newer version of an Operator is available, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Fuse Online operator updated to the new version as described in the Manually approving a pending Operator upgrade section of the OpenShift documentation. During and after an infrastructure upgrade, existing integrations continue to run with the older versions of Fuse libraries and dependencies. To have existing integrations run with the updated Fuse Online version, you must republish the integrations.

Commands: