mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 17. Errata Management with Red Hat Satellite Red Hat Virtualization can be configured to view errata from Red Hat Satellite in the Red Hat Virtualization Manager. This enables the administrator to receive updates about available errata, and their importance, for hosts, virtual machines, and the Manager once they have been associated with a Red Hat Satellite provider. Administrators can then choose to apply the updates by running an update on the required host, virtual machine, or on the Manager. For more information about Red Hat Satellite see the Red Hat Satellite Documentation . Red Hat Virtualization 4.3 supports errata management with Red Hat Satellite 6.5. Important The Manager, hosts, and virtual machines are identified in the Satellite server by their FQDN. This ensures that external content host IDs do not need to be maintained in Red Hat Virtualization. The Satellite account used to manage the Manager, hosts and virtual machines must have Administrator permissions and a default organization set. Configuring Red Hat Virtualization Errata To associate a Manager, host, and virtual machine with a Red Hat Satellite provider first the Manager must be associated with a provider. Then the host is associated with the same provider and configured. Finally, the virtual machine is associated with the same provider and configured. Associate the Manager by adding the required Satellite server as an external provider. See Section 14.2.1, "Adding a Red Hat Satellite Instance for Host Provisioning" for more information. Note The Manager must be registered to the Satellite server as a content host and have the katello-agent package installed. For more information on how to configure a host registration see Registering Hosts in the Red Hat Satellite document Managing Hosts . Optionally, configure the required hosts to display available errata. See Section 10.5.3, "Configuring Satellite Errata Management for a Host" for more information. Optionally, configure the required virtual machines to display available errata. The associated host needs to be configured prior to configuring the required virtual machines. See Configuring Red Hat Satellite Errata Management for a Virtual Machine in the Virtual Machine Management Guide for more information. Viewing Red Hat Virtualization Manager Errata Click Administration Errata . Select the Security , Bugs , or Enhancements check boxes to view only those errata types. For more information on viewing available errata for hosts see Section 10.5.21, "Viewing Host Errata" and for virtual machines see Viewing Red Hat Satellite Errata for a Virtual Machine in the Virtual Machine Management Guide .

Commands:
9. Networking 9.1. Multiqueue Networking Every data packet transferred over a network device represents processing which must be completed by a CPU. The low-level network implementation in Red Hat Enterprise Linux 6 allows network device drivers to divide network packet processing across multiple queues. Dividing these processes allows a system to better utilize the multiple processors and CPU cores present on modern systems. 9.2. Internet Protocol version 6 (IPv6) The -generation Internet Protocol version 6 (IPv6) specification is designed as the successor to Internet Protocol version 4 (IPv4). IPv6 specifies a wide range of improvements over IPv4, including: expanded addressing capabilites, flow labeling and simplified header formats. 9.2.1. Optimistic Duplicate Address Detection Duplicate Address Detection (DAD) is a feature of the Neighbor Discovery Protocol portion of IPv6. Specifically, DAD is tasked with checking if an IPv6 address is already being used. Red Hat Enterprise Linux features Optimistic Duplicate Address Detection, a speed optimization of DAD. 9.2.2. Intra-Site Automatic Tunnel Addressing Protocol Red Hat Enterprise Linux 6 features support for the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP). ISATAP is a protocol designed to assist in the transition from IPv4 to IPv6, by providing a mechanism to connect IPv6 routers and hosts over IPv4 network infrastructure. 9.3. Netlabel Netlabel is a new kernel-level feature in Red Hat Enterprise Linux 6 that provides network packet labeling services for Linux Security Modules (LSMs). Labeling data packets using netlabel allows an LSM to better enforce security requirements on incoming network packets. 9.4. Generic Receive Offload The low-level network implementation in Red Hat Enterprise Linux 6 features Generic Receive Offload (GRO) support. The GRO system increases the performance of inbound network connections by reducing the amount of processing done by the CPU. GRO implements the same technique as the Large Receive Offload (LRO) system, but can be applied to a wider range of transport layer protocols. 9.5. Wireless Support Red Hat Enterprise Linux 6 contains enhanced support for wireless networking and devices. Support for the wireless local area networking using the IEEE 802.11 set of standards has been improved, with added support for 802.11n based wireless networking.

Commands:
Chapter 6. Resolved issues Red Hat 3scale API Management 2.15 resolves the following issues: Table 6.1. Resolved issues Issue number Description THREESCALE-1752 Messages counter in the Dashboard is not correct THREESCALE-5225 Upstream cannot be null error in APIcast logs THREESCALE-7491 Member user in Analytics group getting Access Denied when accessing the Backend analytics THREESCALE-7570 Unable to delete application key when it has a dot in the key name THREESCALE-8383 Need to redeploy Sidekiq when updating Email Templates THREESCALE-9437 Internal Error occurs when changing password for users in member role THREESCALE-9537 Batcher Policy storage ran out of memory THREESCALE-9711 Provide a way to get 3scale patch version details from 3scale installation THREESCALE-10065 Messages deleted from Sent mailbox are deleted immediately instead of being moved to Trash THREESCALE-10147 Finalized option missing in dropdown for Invoice API THREESCALE-10212 Broken "Buyer Account approved" email template THREESCALE-10238 The Operator reconciles a Product created with the ProductCR when mapping rules are duplicated THREESCALE-10259 Special character "#" is breaking the Downalod CSV functionality on the Analytics page THREESCALE-10308 JWT claim check policy fails to match resource and skips the check THREESCALE-10582 Upstream timeouts don't work with Camel Service THREESCALE-10752 Account edit form in admin portal incorrectly rendering country field THREESCALE-10792 The operator doesn't delete the objects in the correct order THREESCALE-10934 Batcher policy does not accept the same chars specified in Porta regex for app_id, app_key & user_key THREESCALE-11183 Backend CR can't be created when using wss protocol

Commands:
7.297. ghostscript 7.297.1. RHBA-2013:0651 - ghostscript bug fix update Updated ghostscript packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Ghostscript suite contains utilities for rendering PostScript and PDF documents. Ghostscript translates PostScript code to common, bitmap formats so that the code can be displayed or printed. Bug Fix BZ# 920251 Due to a bug in a function that copies CIDFontType 2 fonts, document conversion attempts sometimes caused the ps2pdf utility to terminate unexpectedly with a segmentation fault. A patch has been provided to address this bug so that the function now copies fonts properly and ps2pdf no longer crashes in the described scenario. Users of ghostscript are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 8. Networking Multi-message send system call Red Hat Enterprise Linux 6.2 introduces the multi-message send system call which is the send version of the existing recvmmsg system call in Red Hat Enterprise Linux 6. The system call sendmmsg socket API looks like this: Transmit Packet Steering (XPS) Red Hat Enterprise Linux 6.2 includes Transmit Packet Steering (XPS) for multiqueue devices. XPS introduces more efficient transmission of network packets for multiqueue devices by specifically targeting the processor involved in sending the packet. XPS enables the selection of the transmit queue for packet transmission based on configuration. This is analogous to the receive-side functionality implemented in Red Hat Enterprise Linux 6.1 which allowed for processor selection based on the receive queue (RPS). XPS has shown to improve throughput by 20% to 30%. Traffic flooding for unregistered groups Previously, the bridge flooded packets to unregistered groups via all ports. However, this behavior is not desirable in environments where traffic to unregistered groups is always present. In Red Hat Enterprise Linux 6.2, traffic is only sent to unregistered groups via ports marked as router ports. To force flooding to any given port, mark that port as a router port. Stream Control Transmission Protocol (SCTP) Multihome support Red Hat Enterprise Linux 6.2 adds support for SCTP multihoming-the ability of nodes (that is, multi-home nodes) to be reached at several IP addresses. Tracepoints for UDP packet drop events In Red Hat Enterprise Linux 6.2, more tracepoints have been added for UDP packet drop events. These tracepoints provide a way to analyze the reasons why UDP packets are dropped. IPSet The IPSet feature in the kernel has been added to store multiple IP addresses or port numbers, and match them against a collection via iptables . TCP initial receive window default The TCP initial receive window default has been increased from 4 kB to 15 kB. The benefit of this increase is that more data (15 kB > payload > 4 kB) can now fit in the initial window. With a 4 kB setting (IW3), any payload larger than 4 kB would have to be broken into multiple transfers. TCP initial congestion window default In Red Hat Enterprise Linux 6.2, the TCP initial congestion window default is now set to 10 , according to RFC 5681 . Additionally, the initial-window code common to TCP and CCID-2 has been consolidated. GSO support on IPv6 GSO (Generic Segmentation Offload) support for the IPv6 forward path has been added, improving the performance of host to guest communication if GSO is enabled. vios-proxy vios-proxy is a stream-socket proxy for providing connectivity between a client on a virtual guest and a server on a Hypervisor host. Communication occurs over virtio-serial links. This feature is introduced as a Technology Preview in Red Hat Enterprise Linux 6.2.

Commands:
struct mmsghdr { struct msghdr msg_hdr; unsigned msg_len; }; ssize_t sendmmsg(int socket, struct mmsghdr *datagrams, int vlen, int flags);
Chapter 8. Host Management and Monitoring Using RHEL Web Console RHEL web console is an interactive web interface that you can use to perform actions and monitor Red Hat Enterprise Linux hosts. You can enable a remote-execution feature to integrate Satellite with RHEL web console. When you install RHEL web console on a host that you manage with Satellite, you can view the RHEL web console dashboards of that host from within the Satellite web UI. You can also use the features that are integrated with RHEL web console, for example, Red Hat Image Builder. 8.1. Enabling RHEL Web Console on Satellite By default, RHEL web console integration is disabled in Satellite. If you want to access RHEL web console features for your hosts from within Satellite, you must first enable RHEL web console integration on Satellite Server. Procedure On Satellite Server, run satellite-installer with the --enable-foreman-plugin-remote-execution-cockpit option: 8.2. Managing and Monitoring Hosts Using RHEL Web Console You can access the RHEL web console web UI through the Satellite web UI and use the functionality to manage and monitor hosts in Satellite. Prerequisites RHEL web console is enabled in Satellite. RHEL web console is installed on the host that you want to view: For Red Hat Enterprise Linux 8, see Installing the web console in the Managing systems using the RHEL 8 web console guide. For Red Hat Enterprise Linux 7, see Installing the web console in the Managing systems using the RHEL 7 web console guide. Satellite or Capsule can authenticate to the host with SSH keys. For more information, Section 12.8, "Distributing SSH Keys for Remote Execution" . Procedure In the Satellite web UI, navigate to Hosts > All Hosts and select the host that you want to manage and monitor with RHEL web console. In the upper right of the host window, click Web Console . You can now access the full range of features available for host monitoring and management, for example, Red Hat Image Builder, through the RHEL web console. For more information about getting started with Red Hat web console, see the Managing systems using the RHEL 8 web console guide or the Managing systems using the RHEL 7 web console guide. For more information about using Red Hat Image Builder through RHEL web console, see Accessing Image Builder GUI in the RHEL 8 web console or Accessing Image Builder GUI in the RHEL 7 web console . 8.3. Disabling RHEL Web Console on Satellite Perform the following procedure if you want to disable RHEL web console on Satellite. Procedure Run this satellite-installer command: In the Satellite web UI, navigate to Administer > Settings and click the Remote execution tab. In the Cockpit URL row, erase the setting under Value and click Submit . This removes the Web Console button from the Satellite web UI. Uninstall the RHEL web console package from Satellite:

Commands:
satellite-installer --enable-foreman-plugin-remote-execution-cockpit
satellite-installer --no-enable-foreman-plugin-remote-execution-cockpit
remove rubygem-foreman_remote_execution-cockpit
8.2.5. Storage of Backups Once the backups are complete, what happens then? The obvious answer is that the backups must be stored. However, what is not so obvious is exactly what should be stored -- and where. To answer these questions, we must first consider under what circumstances the backups are to be used. There are three main situations: Small, ad-hoc restoration requests from users Massive restorations to recover from a disaster Archival storage unlikely to ever be used again Unfortunately, there are irreconcilable differences between numbers 1 and 2. When a user accidentally deletes a file, they would like it back immediately. This implies that the backup media is no more than a few steps away from the system to which the data is to be restored. In the case of a disaster that necessitates a complete restoration of one or more computers in your data center, if the disaster was physical in nature, whatever it was that destroyed your computers would also have destroyed the backups sitting a few steps away from the computers. This would be a very bad state of affairs. Archival storage is less controversial; since the chances that it will ever be used for any purpose are rather low, if the backup media was located miles away from the data center there would be no real problem. The approaches taken to resolve these differences vary according to the needs of the organization involved. One possible approach is to store several days worth of backups on-site; these backups are then taken to more secure off-site storage when newer daily backups are created. Another approach would be to maintain two different pools of media: A data center pool used strictly for ad-hoc restoration requests An off-site pool used for off-site storage and disaster recovery Of course, having two pools implies the need to run all backups twice or to make a copy of the backups. This can be done, but double backups can take too long, and copying requires multiple backup drives to process the copies (and probably a dedicated system to actually perform the copy). The challenge for a system administrator is to strike a balance that adequately meets everyone's needs, while ensuring that the backups are available for the worst of situations.

Commands:
Chapter 5. Kernel Parameters You can modify the kernel behaviour with kernel parameters. Parameter Description BridgeNfCallArpTables Configures sysctl net.bridge.bridge-nf-call-arptables key. The default value is 1 . BridgeNfCallIp6Tables Configures sysctl net.bridge.bridge-nf-call-ip6tables key. The default value is 1 . BridgeNfCallIpTables Configures sysctl net.bridge.bridge-nf-call-iptables key. The default value is 1 . ExtraKernelModules Hash of extra kernel modules to load. ExtraKernelPackages List of extra kernel related packages to install. ExtraSysctlSettings Hash of extra sysctl settings to apply. FsAioMaxNumber The kernel allocates aio memory on demand, and this number limits the number of parallel aio requests; the only drawback of a larger limit is that a malicious guest could issue parallel requests to cause the kernel to set aside memory. Set this number at least as large as 128 * (number of virtual disks on the host) Libvirt uses a default of 1M requests to allow 8k disks, with at most 64M of kernel memory if all disks hit an aio request at the same time. The default value is 0 . InotifyInstancesMax Configures sysctl fs.inotify.max_user_instances key. The default value is 1024 . InotifyIntancesMax Configures sysctl fs.inotify.max_user_instances key. The default value is 1024 . KernelDisableIPv6 Configures sysctl net.ipv6.{default/all}.disable_ipv6 keys. The default value is 0 . KernelIpForward Configures net.ipv4.ip_forward key. The default value is 1 . KernelIpNonLocalBind Configures net.ipv{4,6}.ip_nonlocal_bind key. The default value is 1 . KernelIpv4ConfAllRpFilter Configures the net.ipv4.conf.all.rp_filter key. The default value is 1 . KernelIpv6ConfAllForwarding Configures the net.ipv6.conf.all.forwarding key. The default value is 0 . KernelPidMax Configures sysctl kernel.pid_max key. The default value is 1048576 . NeighbourGcThreshold1 Configures sysctl net.ipv4.neigh.default.gc_thresh1 value. This is the minimum number of entries to keep in the ARP cache. The garbage collector will not run if there are fewer than this number of entries in the cache. The default value is 1024 . NeighbourGcThreshold2 Configures sysctl net.ipv4.neigh.default.gc_thresh2 value. This is the soft maximum number of entries to keep in the ARP cache. The garbage collector will allow the number of entries to exceed this for 5 seconds before collection will be performed. The default value is 2048 . NeighbourGcThreshold3 Configures sysctl net.ipv4.neigh.default.gc_thresh3 value. This is the hard maximum number of entries to keep in the ARP cache. The garbage collector will always run if there are more than this number of entries in the cache. The default value is 4096 .

Commands:
14.3. LVM References Use these sources to learn more about LVM. Installed Documentation rpm -qd lvm2 - This command shows all the documentation available from the lvm package, including man pages. lvm help - This command shows all LVM commands available. Useful Websites http://sources.redhat.com/lvm2 - LVM2 webpage, which contains an overview, link to the mailing lists, and more. http://tldp.org/HOWTO/LVM-HOWTO/ - LVM HOWTO from the Linux Documentation Project.

Commands:
7.91. iprutils 7.91.1. RHBA-2013:0378 - iprutils bug fix and enhancement update An updated iprutils package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The iprutils package provides utilities to manage and configure SCSI devices that are supported by the IBM Power RAID SCSI storage device driver. Note The iprutils package has been upgraded to upstream version 2.3.12, which provides a number of bug fixes and enhancements over the version and adds support for the suspend/resume utility for IBM BlueHawk. (BZ# 822648 , BZ# 860532 , BZ#829761) Bug Fixes BZ#826907 Previously, showing disk details caused the iprconfig utility, which is used to configure Hardware RAID devices, to terminate unexpectedly. Now, disk details are shown properly and iprconfig no longer crashes. BZ#830982 Previously, in some situations, iprconfig failed to change the IOA asymmetric access mode if the saved mode in the configuration file located in the "/etc/ipr/" directory was different than the current mode. With this update, iprconfig sets the mode correctly and a warning message is returned when this inconsistency is detected. BZ#869751 Previously, iprutils showed the wrong disk platform location within the system location string when the "iprconfig -c show-details sgx" command was used. Now, the platform location for the hard disk is combined with the location of "secured easy setup" (SES) and the physical location slot number which prevents this error from occurring. Users of iprutils are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 1. Service accounts An account can be either a user account or a service account. A user account authenticates human users in your organization. A service account authenticates applications or services without human intervention. You create service accounts on Red Hat Hybrid Cloud Console for the following reasons: An application or service needs access to specific resources. The application or service needs to access resources without the need for human intervention. The application or service needs to access resources from multiple locations. You must use service accounts to connect to cloud service APIs on Red Hat Hybrid Cloud Console . Red Hat support for basic authentication ends on December 31, 2024 and will only permit token-based authentication after that date. Service accounts support token-based authentication. For more information about service account implementation, see Transition of Red Hat Hybrid Cloud Console APIs from basic authentication to token-based authentication via service accounts . Note APIs require an access grant token from Red Hat Single Sign-On. The token expires after 15 minutes (900 seconds). Repeat the process of obtaining an access token every 10 minutes (600 seconds) so that the token is rotated prior to expiration. RFC 6749, Section 4.1.4 Additional resources Update Your API Integration Transition of Red Hat Hybrid Cloud Console APIs from basic authentication to token-based authentication via service accounts

Commands:
7.49. environment-modules 7.49.1. RHBA-2015:0670 - environment-modules bug fix update Updated environment-modules packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The environment-modules packages provide for the dynamic modification of user environment using module files. Each module file contains the information needed to configure the shell for an application. Once the package is initialized, the environment can be modified on a per-module basis using the module command which interprets module files. Bug Fixes BZ# 979789 Previously, misleading information about available modules in nested module directories was displayed to the user. To fix this bug, the code detecting module versions has been amended, and correct information is now displayed. BZ# 1117307 Prior to this update, modules were not properly unloaded when a loading module file contained the "module unload" command. With this update, the logic in the code for version detection of modules has been modified, and modules that contain the "module unload" command are now unloaded correctly. Users of environment-modules are advised to upgrade to these updated packages, which fix these bugs.

Commands: