mtpti5iD/redhat-docs_dataset huggingface dataset:
1.9.3. Command Line Administration Tools In addition to Conga and the system-config-cluster Cluster Administration GUI, command line tools are available for administering the cluster infrastructure and the high-availability service management components. The command line tools are used by the Cluster Administration GUI and init scripts supplied by Red Hat. Table 1.1, "Command Line Tools" summarizes the command line tools. Table 1.1. Command Line Tools Command Line Tool Used With Purpose ccs_tool - Cluster Configuration System Tool Cluster Infrastructure ccs_tool is a program for making online updates to the cluster configuration file. It provides the capability to create and modify cluster infrastructure components (for example, creating a cluster, adding and removing a node). For more information about this tool, refer to the ccs_tool(8) man page. cman_tool - Cluster Management Tool Cluster Infrastructure cman_tool is a program that manages the CMAN cluster manager. It provides the capability to join a cluster, leave a cluster, kill a node, or change the expected quorum votes of a node in a cluster. cman_tool is available with DLM clusters only. For more information about this tool, refer to the cman_tool(8) man page. gulm_tool - Cluster Management Tool Cluster Infrastructure gulm_tool is a program used to manage GULM. It provides an interface to lock_gulmd , the GULM lock manager. gulm_tool is available with GULM clusters only. For more information about this tool, refer to the gulm_tool(8) man page. fence_tool - Fence Tool Cluster Infrastructure fence_tool is a program used to join or leave the default fence domain. Specifically, it starts the fence daemon ( fenced ) to join the domain and kills fenced to leave the domain. fence_tool is available with DLM clusters only. For more information about this tool, refer to the fence_tool(8) man page. clustat - Cluster Status Utility High-availability Service Management Components The clustat command displays the status of the cluster. It shows membership information, quorum view, and the state of all configured user services. For more information about this tool, refer to the clustat(8) man page. clusvcadm - Cluster User Service Administration Utility High-availability Service Management Components The clusvcadm command allows you to enable, disable, relocate, and restart high-availability services in a cluster. For more information about this tool, refer to the clusvcadm(8) man page.

Commands:
8.6. Pluggable Authentication Modules (PAM) Common configuration for PAM services is located in the /etc/pam.d/system-auth-ac file. Authentication modules are now also written into additional PAM configuration files: /etc/pam.d/password-auth-ac , /etc/pam.d/smartcard-auth-ac and /etc/pam.d/fingerprint-auth-ac . The PAM module for sshd and other remote services such as ftpd now include the /etc/pam.d/password-auth file in Red Hat Enterprise Linux 6 instead of /etc/pam.d/system-auth .

Commands:
Chapter 1. Red Hat build of OpenJDK 8 overview OpenJDK (Open Java Development Kit) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is available in three versions: 8u, 11u, and 17u. Packages for the Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Ecosystem Catalog.

Commands:
4.91. icu 4.91.1. RHSA-2011:1815 - Moderate: icu security update Updated icu packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team 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 for each vulnerability from the CVE link(s) associated with each description below. The International Components for Unicode (ICU) library provides robust and full-featured Unicode services. Security Fix CVE-2011-4599 A stack-based buffer overflow flaw was found in the way ICU performed variant canonicalization for some locale identifiers. If a specially-crafted locale representation was opened in an application linked against ICU, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. All users of ICU should upgrade to these updated packages, which contain a backported patch to resolve this issue. All applications linked against ICU must be restarted for this update to take effect.

Commands:
Chapter 4. SAP Automation and Performance 4.1. RHEL System Roles for SAP The Red Hat Enterprise Linux System Roles for SAP, provided exclusively with the Red Hat Enterprise Linux for SAP Solutions subscription, removes human error from complex and repetitive SAP configuration tasks, such as configuration of a Red Hat Enterprise Linux system for installation of SAP HANA, SAP S/4HANA or SAP NetWeaver software. Customers can use RHEL System Roles for SAP to enforce SAP best practices for configuration and setup of both SAP NetWeaver and SAP HANA deployments on RHEL 9, install SAP HANA scale-up and scale-out, and configure a 2-node Pacemaker cluster for managing HANA Scale-Up System Replication. Additional resources For more information, see Red Hat Enterprise Linux System Roles for SAP . 4.2. Tuned To ensure that RHEL is configured appropriately to best support SAP workloads, the RHEL for SAP Solutions provides tuned profiles sap and sap-hana , which contain many of the SAP best practices and some additional recommended configuration settings. Additional resources For more information, see SAP note 3108302 . 4.3. Compatibility libraries RHEL for SAP Solutions provides additional GCC runtime compatibility libraries required by newer SAP NetWeaver, S/4HANA and SAP HANA releases when necessary. RHEL 9 is GCC11 compatible, so no compat-sap-c++ package is required when installing SAP software which has been built with GCC11 or lower. Additional resources For more information, see SAP note 3057467 . 4.4. Smart Management The RHEL subscription includes the Smart Management Add-On to provide easy management and updates of Red Hat Enterprise Linux systems by using Red Hat Satellite Server.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2025-03-05 17:09:53 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
8.4.4. Generating Reports and Guides Another useful features of oscap is the ability to generate SCAP content in a human-readable format. The oscap utility allows you to transform an XML file into the HTML or plain-text format. This feature is used to generate security guides and checklists, which serve as a source of information, as well as guidance for secure system configuration. The results of system scans can also be transformed to well-readable result reports. The general command syntax is the following: oscap module generate sub-module [ specific_module/sub-module_options_and_arguments ] file where module is either xccdf or oval , sub-module is a type of the generated document, and file represents an XCCDF or OVAL file. The following are the most common examples of the command usage: Example 8.9. Generating a Guide with a Checklist To produce an SSG guide with a checklist for the xccdf_org.ssgproject.content_profile_rht-ccp profile, run the following command: The guide will be stored as the ssg-guide-checklist.html file in the current directory. Example 8.10. Transforming an SSG OVAL Scan Result into a Report To transform a result of an SSG OVAL scan into a HTML file, run the following command: The result report will be stored as the ssg-scan-oval-report.html file in the current directory. This example assumes that you run the command from the same location where the scan-oval-results.xml file is stored. Otherwise you need to specify the fully-qualified path of the file that contains the scan results. Example 8.11. Transforming an SSG XCCDF Scan Result into a Report To transform a result of an SSG XCCDF scan into a HTML file, run the following command: The result report will be stored as the ssg-scan-xccdf-report.html file in the current directory. Alternatively, you can generate this report in the time of the scan using the --report command-line argument:

Commands:
~]USD oscap xccdf generate guide --profile xccdf_org.ssgproject.content_profile_rht-ccp /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml > ssg-guide-checklist.html
~]USD oscap oval generate report scan-oval-results.xml > ssg-scan-oval-report.html
~]USD oscap xccdf generate report scan-xccdf-results.xml > scan-xccdf-report.html
~]USD oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_rht-ccp --results scan-xccdf-results.xml --report scan-xccdf-report.html /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
Chapter 1. Understanding Red Hat Network Functions Virtualization (NFV) Network Functions Virtualization (NFV) is a software-based solution that helps the Communication Service Providers (CSPs) to move beyond the traditional, proprietary hardware to achieve greater efficiency and agility while reducing the operational costs. An NFV environment allows for IT and network convergence by providing a virtualized infrastructure using the standard virtualization technologies that run on standard hardware devices such as switches, routers, and storage to virtualize network functions (VNFs). The management and orchestration logic deploys and sustains these services. NFV also includes a Systems Administration, Automation and Life-Cycle Management thereby reducing the manual work necessary. 1.1. Advantages of NFV The main advantages of implementing network functions virtualization (NFV) are as follows: Accelerates the time-to-market by allowing you to to quickly deploy and scale new networking services to address changing demands. Supports innovation by enabling service developers to self-manage their resources and prototype using the same platform that will be used in production. Addresses customer demands in hours or minutes instead of weeks or days, without sacrificing security or performance. Reduces capital expenditure because it uses commodity-off-the-shelf hardware instead of expensive tailor-made equipment. Uses streamlined operations and automation that optimize day-to-day tasks to improve employee productivity and reduce operational costs. 1.2. Supported Configurations for NFV Deployments Red Hat OpenStack Platform supports NFV deployments with the inclusion of automated OVS-DPDK and SR-IOV configuration. Hyper-converged Infrastructure (HCI) Customers can now co-locate the Compute sub-system with the Red Hat Ceph Storage nodes. This hyper-converged model delivers lower cost of entry, smaller initial deployment footprints, maximized capacity utilization, and more efficient management in NFV use cases. Composable roles You can now use composable roles to create custom deployments. Composable roles allow you to add or remove services from each role. For more information on the Composable Roles, see Composable Roles and Services . Open vSwitch (OVS) with LACP As of OVS 2.9, LACP with OVS is fully supported. This is not recommended for Openstack control plane traffic, as OVS or Openstack Networking interruptions may interfere with management. For more information See Open vSwitch Bonding Options . OVS Hardware offload (Technology Preview) Red Hat OpenStack Platform supports, with limitations, the deployment of OVS hardware offload as a technology preview. For information about deploying OVS with hardware offload, see OpenvSwitch Hardware offload . For more information on the support scope for features marked as technology previews, see Technology Preview . Note Red Hat does not support the use of Open Virtual Network (OVN) with Network Functions Virtualization infrastructure (NFVi).

Commands:
2.2.3. Examples of iptables Rules This section provides iptables rule examples for enabling IP ports on Red Hat Cluster nodes and computers that run luci . The examples enable IP ports for a computer having an IP address of 10.10.10.200, using a subnet mask of 10.10.10.0/24. Note Examples are for cluster nodes unless otherwise noted in the example titles. Example 2.1. Port 6809: cman Example 2.2. Port 8084: luci (Cluster Node or Computer Running luci ) Example 2.3. Port 11111: ricci (Cluster Node and Computer Running luci ) Example 2.4. Port 14567: gnbd Example 2.5. Port 16851: modclusterd Example 2.6. Port 21064: dlm Example 2.7. Ports 40040, 40042, 41040: lock_gulmd Example 2.8. Ports 41966, 41967, 41968, 41969: rgmanager Example 2.9. Ports 50006, 50008, 50009: ccsd (TCP) Example 2.10. Port 50007: ccsd (UDP)

Commands:
-A INPUT -i 10.10.10.200 -m state --state NEW -p udp -s 10.10.10.0/24 -d 10.10.10.0/24 --dport 6809 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 8084 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 11111 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 14567 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 16851 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 21064 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 40040,40042,41040 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 41966,41967,41968,41969 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p tcp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 50006,50008,50009 -j ACCEPT
-A INPUT -i 10.10.10.200 -m state --state NEW -m multiport -p udp -s 10.10.10.0/24 -d 10.10.10.0/24 --dports 50007 -j ACCEPT
7.27. coolkey 7.27.1. RHBA-2015:1370 - coolkey bug fix update Updated coolkey packages that fix one bug are now available for Red Hat Enterprise Linux 6. The coolkey packages provide the coolkey smart card support library for the CoolKey, common access card (CAC), and personal identity verification (PIV) smart cards. Bug Fix BZ# 1115626 Previously, after the user inserted a contactless PIV card, coolkey could not access it in a contactless way. As a consequence, the light indicating the card status started to blink inconsistently, and the Enterprise Security Client (ESC) failed to detect the card. With this patch, coolkey accesses the card certificate or key instead of the PIV authentication, PIV signing, or PIV key exchange keys. As a result, when the user inserts a contactless PIV card, ECS now successfully detects it. Users of coolkey are advised to upgrade to these updated packages, which fix this bug.

Commands:
8.4.2. Converting slapd configuration This example assumes that the file to convert from the old slapd configuration is located at /etc/openldap/slapd.conf and the new directory for OpenLDAP configuration is located at /etc/openldap/slapd.d/ . Remove the contents of the new /etc/openldap/slapd.d/ directory: Run slaptest to check the validity of the configuration file and specify the new configuration directory: Configure permissions on the new directory: Once the service is confirmed to be working in the new configuration directory, remove the old configuration file:

Commands:
rm -rf /etc/openldap/slapd.d/*
slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d
chown -R ldap:ldap /etc/openldap/slapd.d
chmod -R 000 /etc/openldap/slapd.d
chmod -R u+rwX /etc/openldap/slapd.d
rm -rf /etc/openldap/slapd.conf
Chapter 1. Introduction The Red Hat Virtualization Manager provides a Representational State Transfer (REST) API . The API provides software developers and system administrators with control over their Red Hat Virtualization environment outside of the standard web interface. The API is useful for developers and administrators to integrate the functionality of a Red Hat Virtualization environment with custom scripts or external applications that access the API via the standard Hypertext Transfer Protocol (HTTP). The benefits of the API are: Broad client support - Any programming language, framework, or system with support for HTTP protocol can use the API. Self descriptive - Client applications require minimal knowledge of the virtualization infrastructure, as many details are discovered at runtime. Resource-based model - The resource-based REST model provides a natural way to manage a virtualization platform. This provides developers and administrators with the ability to: Integrate with enterprise IT systems. Integrate with third-party virtualization software. Perform automated maintenance or error-checking tasks. Automate repetitive tasks in a Red Hat Virtualization environment with scripts. This documentation acts as a reference for the Red Hat Virtualization API. It aims to provide developers and administrators with instructions and examples to help harness the functionality of their Red Hat Virtualization environment through the API, either directly or using the provided SDKs. 1.1. Representational State Transfer Representational State Transfer (REST) is a design architecture that focuses on resources for a specific service and their representations. A resource representation is a key abstraction of information that corresponds to one specific managed element on a server. A client sends a request to a server element located at a Uniform Resource Identifier (URI) and performs operations with standard HTTP methods, such as GET , POST , PUT , and DELETE . This provides a stateless communication between the client and server where each request acts independently of any other request, and contains all the information necessary to complete the request. 1.1.1. API Prerequisites Prerequisites for using the Red Hat Virtualization API: A networked installation of Red Hat Virtualization Manager, which includes the API. A client or programming library that initiates and receives HTTP requests from the API server, for example: The oVirt Python SDK . The oVirt Java SDK . The cURL command line tool. RESTClient , a debugger for RESTful web services. Knowledge of Hypertext Transfer Protocol (HTTP), the protocol used for REST API interactions. See RFC 2616: HTTP/1.1 . Knowledge of Extensible Markup Language (XML) or JavaScript Object Notation (JSON), which the API uses to construct resource representations. See W3C Extensible Markup Language (XML) 1.0 and ECMA-404: JSON data interchange syntax .

Commands:
16.8. virt-resize: Resizing Guest Virtual Machines Offline This section provides information about resizing offline guest virtual machines. 16.8.1. Introduction This section describes virt-resize , a tool for expanding or shrinking guest virtual machines. It only works for guest virtual machines which are offline (shut down). It works by copying the guest virtual machine image and leaving the original disk image untouched. This is ideal because you can use the original image as a backup, however there is a trade-off as you need twice the amount of disk space.

Commands:
15.2. FTP Servers Red Hat Enterprise Linux ships with two different FTP servers: Red Hat Content Accelerator - A kernel-based Web server that delivers high performance Web server and FTP services. Since speed as its primary design goal, it has limited functionality and runs only as an anonymous FTP server. For more information about configuring and administering Red Hat Content Accelerator , consult the documentation available online at http://www.redhat.com/docs/manuals/tux/ . vsftpd - A fast, secure FTP daemon which is the preferred FTP server for Red Hat Enterprise Linux. The remainder of this chapter focuses on vsftpd . 15.2.1. vsftpd The Very Secure FTP Daemon ( vsftpd ) is designed from the ground up to be fast, stable, and, most importantly, secure. Its ability to handle large numbers of connections efficiently and securely is why vsftpd is the only stand-alone FTP distributed with Red Hat Enterprise Linux. The security model used by vsftpd has three primary aspects: Strong separation of privileged and non-privileged processes - Separate processes handle different tasks, and each of these processes run with the minimal privileges required for the task. Tasks requiring elevated privileges are handled by processes with the minimal privilege necessary - By leveraging compatibilities found in the libcap library, tasks that usually require full root privileges can be executed more safely from a less privileged process. Most processes run in a chroot jail - Whenever possible, processes are change-rooted to the directory being shared; this directory is then considered a chroot jail. For example, if the directory /var/ftp/ is the primary shared directory, vsftpd reassigns /var/ftp/ to the new root directory, known as / . This disallows any potential malicious hacker activities for any directories not contained below the new root directory. Use of these security practices has the following effect on how vsftpd deals with requests: The parent process runs with the least privileges required - The parent process dynamically calculates the level of privileges it requires to minimize the level of risk. Child processes handle direct interaction with the FTP clients and run with as close to no privileges as possible. All operations requiring elevated privileges are handled by a small parent process - Much like the Apache HTTP Server, vsftpd launches unprivileged child processes to handle incoming connections. This allows the privileged, parent process to be as small as possible and handle relatively few tasks. All requests from unprivileged child processes are distrusted by the parent process - Communication with child processes are received over a socket, and the validity of any information from child processes is checked before being acted on. Most interaction with FTP clients is handled by unprivileged child processes in a chroot jail - Because these child processes are unprivileged and only have access to the directory being shared, any crashed processes only allows the attacker access to the shared files.

Commands: