mtpti5iD/redhat-docs_dataset huggingface dataset:
1.7. Managing Data Using the ncat utility The ncat networking utility replaces netcat in Red Hat Enterprise Linux 7. ncat is a reliable back-end tool that provides network connectivity to other applications and users. It reads and writes data across the network from the command line, and uses Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Stream Control Transmission Protocol (SCTP) or Unix sockets for communication. ncat can deal with both IPv4 and IPv6 , open connections, send packets, perform port scanning, and supports higher-level features such as SSL , and connection broker. The nc command can also be entered as ncat , using the identical options. For more information about the ncat options, see the New networking utility (ncat) section in the Migration Planning Guide and the ncat (1) man page. Installing ncat To install the ncat package, enter as root : Brief Selection of ncat Use Cases Example 1.1. Enabling Communication between a Client and a Server Set a client machine to listen for connections on TCP port 8080 : On a server machine, specify the IP address of the client and use the same port number: You can send messages on either side of the connection and they appear on both local and remote machines. Press Ctrl+D to close the TCP connection. Note To check a UDP port, use the same nc commands with the -u option. For example: Example 1.2. Sending Files Instead of printing information on the screen, as mentioned in the example, you can send all information to a file. For example, to send a file over TCP port 8080 from a client to a server: On a client machine, to listen a specific port transferring a file to the server machine: On a server machine, specify the IP address of the client, the port and the file which is to be transferred: After the file is transferred, the connection closes automatically. Note You can transfer a file in the other direction as well: Example 1.3. Creating an HTTP proxy server To create an HTTP proxy server on localhost port 8080 : Example 1.4. Port Scanning To view which ports are open, use the -z option and specify a range of ports to scan: Example 1.5. Setting up Secure Client-Server Communication Using SSL Set up SSL on a server: On a client machine: Note To ensure true confidentiality of the SSL connection, the server requires the --ssl-cert and --ssl-key options, and the client requires the --ssl-verify and --ssl-trustfile options. For information on OpenSSL , see the Using OpenSSL section in the Security Guide . For more examples, see the ncat (1) man page.

Commands:
~]# yum install ncat
~]USD ncat -l 8080
~]USD ncat 10.0.11.60 8080
~]USD ncat -u -l 8080
~]USD ncat -l 8080 > outputfile
~]USD ncat -l 10.0.11.60 8080 < inputfile
~]USD ncat -l 8080 < inputfile
~]USD ncat -l 10.0.11.60 8080 > outputfile
~]USD ncat -l --proxy-type http localhost 8080
~]USD ncat -z 10.0.11.60 80-90 Connection to 192.168.0.1 80 port [tcp/http] succeeded!
~]USD ncat -e /bin/bash -k -l 8080 --ssl
~]USD ncat --ssl 10.0.11.60 8080
Chapter 5. Mapping storage management network ports to NICs The following procedure details how to map the storage management network ports to the physical NICs on your hyperconverged nodes. Procedure Copy the compute.yaml heat template file for your environment from the /usr/share/openstack-tripleo-heat-templates/network/config directory. The following options are available: single-nic-vlans single-nic-linux-bridge-vlans multiple-nics bond-with-vlans See the README.md in each template's directory for details on the NIC configuration. Create a new directory within `~/templates called nic-configs . Paste your copy of the compute.yaml template into ~/templates/nic-configs/ and rename it to compute-hci.yaml . Check the parameters: section of ~/templates/nic-configs/compute-hci.yaml for the following definition: Add the StorageMgmtNetworkVlanID definition if it is not already in the compute-hci.yaml file. Map StorageMgmtNetworkVlanID to a specific NIC on each HCI node. For example, if you chose to trunk VLANs to a single NIC, then add the following entry to the network_config: section of ~/templates/nic-configs/compute-hci.yaml : Note Set MTU to 9000 (jumbo frames) when mapping a NIC to StorageMgmtNetworkVlanID to improve the performance of Red Hat Ceph Storage. For more information, see Configure MTU Settings in Director and Configuring jumbo frames . Create a networking environment file called ~/templates/network.yaml . Add the following configuration to the network.yaml file: This file will be used later to invoke the customized Compute NIC template ( ~/templates/nic-configs/compute-hci.yaml ) during overcloud deployment. You can use ~/templates/network.yaml to define any networking parameters, or add any customized networking heat templates. For more information, see Custom network environment file in the Advanced Overcloud Customization guide.

Commands:
StorageMgmtNetworkVlanID: default: 40 description: Vlan ID for the storage mgmt network traffic. type: number
type: vlan device: em2 mtu: 9000 use_dhcp: false vlan_id: {get_param: StorageMgmtNetworkVlanID} addresses: - ip_netmask: {get_param: StorageMgmtIpSubnet}
resource_registry: OS::TripleO::ComputeHCI::Net::SoftwareConfig: /home/stack/templates/nic-configs/compute-hci.yaml
Chapter 19. Implementing Federation Warning Red Hat does not support federation at this time. This feature should only be used for testing, and should not be deployed in a production environment. 19.1. Federate with IdM using Red Hat Single Sign-On You can use Red Hat Single Sign-On (RH-SSO) to federate your IdM users for OpenStack authentication (authN). Federation allows your IdM users to login to the OpenStack Dashboard without revealing their credentials to any OpenStack services. Instead, when Dashboard needs a user's credentials, it will forward the user to Red Hat Single Sign-On (RH-SSO) and allow them to enter their IdM credentials there. As a result, RH-SSO asserts back to Dashboard that the user has successfully authenticated, and Dashboard then allows the user to access the project. 19.2. The federation workflow This section describes how the Identity service (keystone), RH-SSO and IdM interact with each other. Federation in OpenStack uses the concept of Identity Providers and Service Providers: Identity Provider (IdP) - the service that stores the user accounts. In this case, the user accounts held in IdM, are presented to Keystone using RH-SSO. Service Provider (SP) - the service that requires authentication from the users in the IdP. In this case, keystone is the service provider that grants Dashboard access to IdM users. In the diagram below, keystone (the SP) communicates with RH-SSO (the IdP), which is also able to serve as a universal adapter for other IdPs. In this configuration, you can point keystone at RH-SSO, and RH-SSO will forward requests on to the Identity Providers that it supports (known as authentication modules), these currently include IdM and Active Directory. This is done by having the Service Provider (SP) and Identity Provider (IdP) exchange metadata, which each sysadmin then makes a decision to trust. The result is that the IdP can confidently make assertions, and the SP can then receive these assertions. For more information, see the federation guide: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/federate_with_identity_service/

Commands:
Chapter 4. Products managed by Helm charts The Helm chart must be capable of deploying your product on Red Hat OpenShift, using the Helm utilities provided by this platform. For more information about using Helm charts on Red Hat OpenShift, see Working with Helm charts . To be certified, the Helm chart must meet the following requirements. Requirement Justification All containers used by the Helm chart must be Red Hat certified containers. Operating system libraries in the certified container images are covered by the Red Hat OpenShift support, and continuously monitored for security vulnerabilities. For more information on container certification requirements, see Requirements for container images . For more information about the steps to certify your containers, see Working with containers . The chart's apiVersion field must be v2.0. Chart must be compatible with Helm 3 (for example, apiVersion v2), the Helm version supported in OpenShift. Chart must contain a README.md file. Provide basic information about the chart in a human-readable format. Chart must set the kubeVersion field to indicate the minimum Kubernetes version supported. To determine chart compatibility with specific versions of OpenShift. For information on Kubernetes versions used in OpenShift, see What version of the Kubernetes API is included with each OpenShift 4.x release? article. Chart must include one or more tests located in the templates directory. To verify successful chart installation. Chart must include a values.yaml file and a values.schema.json file. Identify chart inputs and provide proper validation. Chart must not contain any Custom Resource Definitions (CRDs). Lifecycle of Custom Resource Definitions (CRDs) needs to be managed properly. Red Hat recommends an Operator for performing this task. For more information about Operators, see Working with Operators . Chart must pass the helm lint command. Ensuring correct chart format. Chart must include the charts.openshift.io/name annotation with a human-readable name. Provide a name that can be used when displaying the chart on the OpenShift console. This name must follow Red Hat trademark guidelines and policies.

Commands:
Chapter 2. Architectures RHTAP standalone CLIs are available for these architectures: Architectures Cosign, Rekor, EC, roxctl Syft Linux x86_64 yes yes arm64 yes ppc64le yes s390x yes MacOS x86_64 yes arm64 yes Windows x86_64 yes Note To use Syft on architectures other than x86_64 on Linux, install the upstream version of Syft . Revised on 2025-02-06 16:31:05 UTC

Commands:
function::user_long_warn Name function::user_long_warn - Retrieves a long value stored in user space Synopsis Arguments addr the user space address to retrieve the long from Description Returns the long value from a given user space address. Returns zero when user space and warns (but does not abort) about the failure. Note that the size of the long depends on the architecture of the current user space task (for those architectures that support both 64/32 bit compat tasks).

Commands:
user_long_warn:long(addr:long)
A.2.4. SSL/TLS Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL), are cryptographic protocols that provide security for communications over networks such as the Internet. TLS and SSL encrypt the segments of network connections at the Transport Layer end-to-end. Several versions of the protocols are in widespread use in applications like web browsing, electronic mail, Internet faxing, instant messaging and voice-over-IP (VoIP). [20] [20] "TLS/SSL." Wikipedia. 24 February 2010 http://en.wikipedia.org/wiki/Transport_Layer_Security

Commands:
Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . This document shows you how to manage Red Hat Gluster Storage using the Administration Portal provided by Red Hat Virtualization Manager.

Commands:
function::msecs_to_string Name function::msecs_to_string - Human readable string for given milliseconds Synopsis Arguments msecs Number of milliseconds to translate. Description Returns a string representing the number of milliseconds as a human readable string consisting of " XmY.ZZZs " , where X is the number of minutes, Y is the number of seconds and ZZZ is the number of milliseconds.

Commands:
msecs_to_string:string(msecs:long)
Chapter 14. The kie-camel component The kie-camel component is an Apache Camel endpoint provided by Red Hat Fuse that integrates Fuse with Red Hat Process Automation Manager. It enables you to specify a Red Hat Process Automation Manager module by using a Maven group ID, artifact ID, and version (GAV) identifier which you can pull into the route and execute. It also enables you to specify portions of the message body as facts. You can use the kie-camel component with embedded engines or with KIE Server. Embedded engines In this scenario, KIE engines run in the same container as the Fuse integration project and you can communicate with engines using KIE commands. To create the Camel producer, use the following URI: For example, enter the following command to initialize a Camel route in Spring: KIE Server In this scenario, the kie-camel component connects to KIE Server using the KIE Server REST API. This enables users to communicate with KIE Server using the KIE Server API. To create a producer, use the following URI: For example, enter the following command to initialize a Camel route in Spring: The message has the following headers: Table 14.1. Message headers and descriptions Header Description CamelKieClient KIE Server client (mandatory) CamelKieOperation KIE Server client (mandatory) CamelKieParameterName The value of the client method parameter (optional) CamelKieBodyParam The method parameter where the message body is stored (optional)

Commands:
kie-local:kie-session-name?action=execute
<from uri="direct:runCommand" /> <to uri="kie-local:kie-session1?action=execute"/>
kie:http://username:password@kie-server-url`
<from uri="direct:runCommand" /> <to uri="kie:http://user:psswd@localhost:8080/kie-server-services/services/rest/server"/>
Chapter 5. What to do ? Day 2 As a storage administrator, once you have installed and configured Red Hat Ceph Storage 6, you are ready to perform "Day Two" operations for your storage cluster. These operations include adding metadata servers (MDS) and object gateways (RGW), and configuring services such as NFS. For more information about how to use the cephadm orchestrator to perform "Day Two" operations, refer to the Red Hat Ceph Storage 6 Operations Guide . To deploy, configure, and administer the Ceph Object Gateway on "Day Two" operations, refer to the Red Hat Ceph Storage 6 Object Gateway Guide .

Commands:
Chapter 1. Introduction to Red Hat JBoss Data Grid 6.6.1 Welcome to Red Hat JBoss Data Grid 6.6.1. As you become familiar with the newest version of JBoss Data Grid these Release Notes provide you with information about new features, as well as known and resolved issues. Use this document in conjunction with the entire JBoss Data Grid documentation suite, available at the Red Hat Customer Service Portal's JBoss Data Grid documentation page . Report a bug 1.1. About Red Hat JBoss Data Grid Red Hat's JBoss Data Grid is an open source, distributed, in-memory key/value data store built from the Infinispan open source software project. Whether deployed in client/server mode or embedded in a Java Virtual Machine, it is built to be elastic, high performance, highly available and to scale linearly. JBoss Data Grid is accessible for both Java and Non-Java clients. Using JBoss Data Grid, data is distributed and replicated across a manageable cluster of nodes, optionally written to disk and easily accessible using the REST, Memcached and Hot Rod protocols, or directly in process through a traditional Java Map API. Report a bug

Commands:
Chapter 6. Confining Users A number of confined SELinux users are available in Red Hat Enterprise Linux 6. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions placed on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the su and sudo commands. This helps protect the system from the user. Refer to Section 4.3, "Confined and Unconfined Users" for further information about confined users. 6.1. Linux and SELinux User Mappings As the Linux root user, run the semanage login -l command to view the mapping between Linux users and SELinux users: In Red Hat Enterprise Linux 6, Linux users are mapped to the SELinux __default__ login by default (which is in turn mapped to the SELinux unconfined_u user). When a Linux user is created with the useradd command, if no options are specified, they are mapped to the SELinux unconfined_u user. The following defines the default-mapping:

Commands:
~]# semanage login -l Login Name SELinux User MLS/MCS Range __default__ unconfined_u s0-s0:c0.c1023 root unconfined_u s0-s0:c0.c1023 system_u system_u s0-s0:c0.c1023
__default__ unconfined_u s0-s0:c0.c1023
Chapter 5. Modifying firewall rules 5.1. Modifying firewall rules for disk encryption On Network-Bound Disk Encryption (NBDE) key servers, you need to open ports so that encryption keys can be served. Procedure On each NBDE key server: Open ports required to serve encryption keys. Note The default port is 80/tcp . To use a custom port, see Deploying a tang server with SELinux in enforcing mode in the Red Hat Enterprise Linux 8 documentation. Verify that the port appears in the output of the following command.

Commands:
firewall-cmd --add-port=80/tcp firewall-cmd --add-port=80/tcp --permanent
firewall-cmd --list-ports | grep '80/tcp'
Preface 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:
10.2. Red Hat Virtualization Host Red Hat Virtualization Host (RHVH) is installed using a special build of Red Hat Enterprise Linux with only the packages required to host virtual machines. It uses an Anaconda installation interface based on the one used by Red Hat Enterprise Linux hosts, and can be updated through the Red Hat Virtualization Manager or via yum . Using the yum command is the only way to install additional packages and have them persist after an upgrade. RHVH features a Cockpit web interface for monitoring the host's resources and performing administrative tasks. Direct access to RHVH via SSH or console is not supported, so the Cockpit web interface provides a graphical user interface for tasks that are performed before the host is added to the Red Hat Virtualization Manager, such as configuring networking and deploying a self-hosted engine, and can also be used to run terminal commands via the Terminal sub-tab. Access the Cockpit web interface at https:// HostFQDNorIP :9090 in your web browser. Cockpit for RHVH includes a custom Virtualization dashboard that displays the host's health status, SSH Host Key, self-hosted engine status, virtual machines, and virtual machine statistics. RHVH uses the Automatic Bug Reporting Tool (ABRT) to collect meaningful debug information about application crashes. For more information, see the Red Hat Enterprise Linux System Administrator's Guide . Note Custom boot kernel arguments can be added to Red Hat Virtualization Host using the grubby tool. The grubby tool makes persistent changes to the grub.cfg file. Navigate to the Terminal sub-tab in the host's Cockpit web interface to use grubby commands. See the Red Hat Enterprise Linux System Administrator's Guide for more information. Warning Red Hat strongly recommends not creating untrusted users on RHVH, as this can lead to exploitation of local security vulnerabilities.

Commands:
7.54. fcoe-utils 7.54.1. RHBA-2013:0412 - fcoe-utils bug fix and enhancement update Updated fcoe-utils packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The fcoe-utils packages provide Fibre Channel over Ethernet (FCoE) utilities, such as the fcoeadm command line tool for configuring FCoE interfaces, and the fcoemon service to configure DCB Ethernet QOS filters. Note The fcoe-utils packages have been upgraded to upstream version 1.0.24, which provides a number of bug fixes and enhancements over the version. Bug Fix BZ#867117 When turning off DCB on a Fibre Channel over Ethernet (FCoE) initiator interface connected to a Cisco Fibre Channel Forwarder (FCF), the fcoemon utility disabled the interface but the FCoE interface was re-enabled by a Netlink event before DCB was operational again. Consequently, the interface did not operate in degraded mode with LUNS present as expected and the output of the "ip l" and "fcoeadm -i" commands was contradictory. A patch has been applied to the fcoemon utility to ensure DCB is operational again before enabling the FCoE interface when a link is brought up. In addition, a patch has been applied to fcoe-utils to improve error handling and error messages related to creating and deleting of FCoE interfaces when DCB is not ready. Enhancement BZ#826291 Support for VLAN notification with VLAN ID 0 has been added. If a VLAN notification has the tag "VLAN 0", the physical port will now be activated. The VLAN interface will not be created but FCoE will be started on the physical interface itself. All users of fcoe-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Appendix B. Revision History Revision History Revision 0.1-4 Tue Mar 02 2021 Lenka Spackova Updated a link to Upgrading from RHEL 6 to RHEL 7 . Fixed CentOS Linux name. Revision 0.1-3 Mon May 11 2020 Lenka Spackova Changed a FIPS-related reference to a more appropriate resource. Revision 0.1-2 Tue Apr 28 2020 Lenka Spackova Updated information about in-place upgrades. Revision 0.1-1 Thu Mar 19 2020 Lenka Spackova Updated a known issue related to an in-place upgrade with FIPS mode (General Updates). Revision 0.1-0 Wed Feb 19 2020 Lenka Spackova Added a known issue related to the Preupgrade Assistant (General Updates). Revision 0.0-9 Tue Feb 26 2019 Lenka Spackova Updated a known issue related to in-place upgrade, based on the released RHBA-2019:0411 advisory. Revision 0.0-8 Thu Nov 22 2018 Filip Hanzelka Added a new known issue related to AD users not being able to use sudo (Authentication and Interoperability). Revision 0.0-7 Wed Oct 31 2018 Lenka Spackova Added a new feature and two known issues related to in-place upgrades (General Updates). Revision 0.0-6 Wed Aug 22 2018 Lenka Spackova Added a known issue related to GRUB Legacy (Installation and Booting). Revision 0.0-5 Tue Jul 31 2018 Lenka Spackova Added a note regarding a change in behavior of the reposync command to New Features (System and Subscription Management). Revision 0.0-4 Tue Jun 19 2018 Lenka Spackova Release of the Red Hat Enterprise Linux 6.10 Release Notes. Revision 0.0-0 Wed Apr 25 2018 Lenka Spackova Release of the Red Hat Enterprise Linux 6.10 Beta Release Notes.

Commands: