mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. Disabling anonymous binds If a user attempts to connect to Directory Server without supplying any credentials, this operation is called anonymous bind . Anonymous binds simplify searches and read operations, such as finding a phone number in the directory by not requiring users to authenticate first. However, anonymous binds can also be a security risk, because users without an account are able to access the data. Warning By default, anonymous binds are enabled in Directory Server for search and read operations. This allows unauthorized access to user entries as well as configuration entries, such as the root directory server entry (DSE). 8.1. Disabling anonymous binds using the command line To increase the security, you can disable anonymous binds. Procedure Set the nsslapd-allow-anonymous-access configuration parameter to off : # dsconf -D " cn=Directory Manager " ldap://server.example.com config replace nsslapd-allow-anonymous-access=off Verification Run a search without specifying a user account: # ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed 8.2. Disabling anonymous binds using the web console To increase the security, you can disable anonymous binds. Prerequisites You are logged in to the instance in the web console. Procedure Navigate to Server Server Settings Advanced Settings . Set the Allow Anonymous Access parameter to off . Click Save . Verification Run a search without specifying a user account: # ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed

Commands:
dsconf -D " cn=Directory Manager " ldap://server.example.com config replace nsslapd-allow-anonymous-access=off
ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed
ldapsearch -H ldap://server.example.com -b " dc=example,dc=com " -x ldap_bind: Inappropriate authentication (48) additional info: Anonymous access is not allowed
26.3. Installing a CA Certificate Manually To install a new certificate to IdM, use the ipa-cacert-manage install command. For example, the command allows you to change the current certificate when it is nearing its expiration date. Run the ipa-cacert-manage install command, and specify the path to the file containing the certificate. The command accepts PEM-formatted certificate files: The certificate is now present in the LDAP certificate store. Run the ipa-certupdate utility on all servers and clients to update them with the information about the new certificate from LDAP. You must run ipa-certupdate on every server and client separately. Important Always run ipa-certupdate after manually installing a certificate. If you do not, the certificate will not be distributed to the other machines. The ipa-cacert-manage install command can take the following options: -n gives the nickname of the certificate; the default value is the subject name of the certificate -t specifies the trust flags for the certificate in the certutil format; the default value is C,, . For information about the format in which to specify the trust flags, see the ipa-cacert-manage (1) man page.

Commands:
ipa-cacert-manage install /etc/group/cert.pem
Appendix B. iSCSI Gateway Variables iSCSI Gateway General Variables seed_monitor Purpose Each iSCSI gateway needs access to the Ceph storage cluster for RADOS and RBD calls. This means the iSCSI gateway must have an appropriate /etc/ceph/ directory defined. The seed_monitor host is used to populate the iSCSI gateway's /etc/ceph/ directory. gateway_keyring Purpose Define a custom keyring name. perform_system_checks Purpose This is a Boolean value that checks for multipath and LVM configuration settings on each iSCSI gateway. It must be set to true for at least the first run to ensure the multipathd daemon and LVM are configured properly. iSCSI Gateway RBD-TARGET-API Variables api_user Purpose The user name for the API. The default is admin . api_password Purpose The password for using the API. The default is admin . api_port Purpose The TCP port number for using the API. The default is 5000 . api_secure Purpose Value can be true or false . The default is false . loop_delay Purpose Controls the sleeping interval in seconds for polling the iSCSI management object. The default value is 1 . trusted_ip_list Purpose A list of IPv4 or IPv6 addresses that have access to the API. By default, only the iSCSI gateway hosts have access.

Commands:
7.85. ipset 7.85.1. RHBA-2015:1353 - ipset bug fix update Updated ipset packages that fix one bug are now available for Red Hat Enterprise Linux 6. The ipset packages provide IP sets, a framework inside the Linux 2.4.x and 2.6.x kernel, which can be administered by the ipset utility. Depending on the type, an IP set can currently store IP addresses, TCP/UDP port numbers or IP addresses with MAC addresses in a way that ensures high speed when matching an entry against a set. Bug Fix BZ# 1121665 When the user was trying to create a program using the ipset library, linking failed with an undefined reference to the ipset_port_usage() function. With this update, ipset_port_usage() is now provided by the library and a program using the ipset library is now compiled successfully. Users of ipset are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 24. Managing Instance Groups An Instance Group enables you to group instances in a clustered environment. Policies dictate how instance groups behave and how jobs are executed. The following view displays the capacity levels based on policy algorithms: Additional resources For more information about the policy or rules associated with instance groups, see the Instance Groups section of the Automation controller Administration Guide . For more information on connecting your instance group to a container, see Container Groups . 24.1. Creating an instance group Use the following procedure to create a new instance group. Procedure From the navigation panel, select Administration Instance Groups . Select Add from the Add instance group list. Enter the appropriate details into the following fields: Name : Names must be unique and must not be named "controller". Policy instance minimum : Enter the minimum number of instances to automatically assign to this group when new instances come online. Policy instance percentage : Use the slider to select a minimum percentage of instances to automatically assign to this group when new instances come online. Note Policy instance fields are not required to create a new instance group. If you do not specify values, then the Policy instance minimum and Policy instance percentage default to 0. Max concurrent jobs : Specify the maximum number of forks that can be run for any given job. Max forks : Specify the maximum number of concurrent jobs that can be run for any given job. Note The default value of 0 for Max concurrent jobs and Max forks denotes no limit. For more information, see Instance group capacity limits in the Automation controller Administration Guide . Click Save . When you have successfully created the instance group the Details tab of the newly created instance group remains, enabling you to review and edit your instance group information. This is the same screen that opens when you click the Edit icon from the Instance Groups list view. You can also edit Instances and review Jobs associated with this instance group: 24.1.1. Associating instances to an instance group Procedure Select the Instances tab of the Instance Groups window. Click Associate . Click the checkbox to one or more available instances from the list to select the instances you want to associate with the instance group: In the following example, the instances added to the instance group displays along with information about their capacity: 24.1.2. Viewing jobs associated with an instance group Procedure Select the Jobs tab of the Instance Group window. Click the arrow icon to a job to expand the view and show details about each job. Each job displays the following details: The job status The ID and name The type of job The time it started and completed Who started the job and applicable resources associated with it, such as the template, inventory, project, and execution environment Additional resources The instances are run in accordance with instance group policies. For more information, see Instance Group Policies in the Automation controller Administration Guide .

Commands:
19.2. Installation and Deployment Installation Guide The Installation Guide documents relevant information regarding the installation of Red Hat Enterprise Linux 7. This book also covers advanced installation methods such as kickstart, PXE installations, and installations over VNC, as well as common post-installation tasks. System Administrator's Guide The System Administrator's Guide provides information about deploying, configuring, and administering Red Hat Enterprise Linux 7. Storage Administration Guide The Storage Administration Guide provides instructions on how to effectively manage storage devices and file systems on Red Hat Enterprise Linux 7. It is intended for use by system administrators with intermediate experience in Red Hat Enterprise Linux. Global File System 2 The Global File System 2 book provides information about configuring and maintaining Red Hat GFS2 (Global File System 2) in Red Hat Enterprise Linux 7. Logical Volume Manager Administration The Logical Volume Manager Administration guide describes the LVM logical volume manager and provides information on running LVM in a clustered environment. Kernel Crash Dump Guide The Kernel Crash Dump Guide documents how to configure, test, and use the kdump crash recovery service available in Red Hat Enterprise Linux 7.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ JMS Pool in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ JMS Pool, you must install Apache Maven . To use AMQ JMS Pool, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.messaginghub</groupId> <artifactId>pooled-jms</artifactId> <version>2.0.0.redhat-00001</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ JMS Pool can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Clients 2.10.0 JMS Pool Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-clients-2.10.0-jms-pool-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use the git clone command to clone the source repository to a local directory named pooled-jms : USD git clone https://github.com/messaginghub/pooled-jms.git pooled-jms Change to the pooled-jms directory and use the git checkout command to switch to the 2.0.0 branch: USD cd pooled-jms USD git checkout 2.0.0 The resulting local directory is referred to as <source-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.messaginghub</groupId> <artifactId>pooled-jms</artifactId> <version>2.0.0.redhat-00001</version> </dependency>
unzip amq-clients-2.10.0-jms-pool-maven-repository.zip
git clone https://github.com/messaginghub/pooled-jms.git pooled-jms
cd pooled-jms git checkout 2.0.0
10.8. Configuring VLAN switchport mode Red Hat Enterprise Linux machines are often used as routers and enable an advanced VLAN configuration on their network interfaces. You need to set switchport mode when the Ethernet interface is connected to a switch and there are VLANs running over the physical interface. A Red Hat Enterprise Linux server or workstation is usually connected to only one VLAN, which makes switchport mode access suitable, and the default setting. In certain scenarios, multiple tagged VLANs use the same physical link, that is Ethernet between the switch and Red Hat Enterprise Linux machine, which requires switchport mode trunk to be configured on both ends. For example, when a Red Hat Enterprise Linux machine is used as a router, the machine needs to forward tagged packets from the various VLANs behind the router to the switch over the same physical Ethernet, and maintain separation between those VLANs. With the setup described, for example, in Section 10.3, "Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli" , use the Cisco switchport mode trunk . If you only set an IP address on an interface, use Cisco switchport mode access .

Commands:
3.5.4. Host Storage Disk images can be stored on a range of local and remote storage technologies connected to the host. Image files Image files can only be stored on a host be file system. The image files can be stored on a local file system, such as ext4 or xfs, or a network file system, such as NFS. Tools such as libguestfs can manage, back up, and monitor files. Disk image formats on KVM include: raw Raw image files contain the contents of the disk with no additional metadata. Raw files can either be pre-allocated or sparse, if the host file system allows it. Sparse files allocate host disk space on demand, and are therefore a form of thin provisioning. Pre-allocated files are fully provisioned but have higher performance than sparse files. Raw files are desirable when disk I/O performance is critical and transferring the image file over a network is rarely necessary. qcow2 qcow2 image files offer a number of advanced disk image features, including backing files, snapshots, compression, and encryption. They can be used to instantiate virtual machines from template images. qcow2 files are typically more efficient to transfer over a network, because only sectors written by the virtual machine are allocated in the image. LVM volumes Logical volumes (LVs) can be used for disk images and managed using the system's LVM tools. LVM offers higher performance than file systems because of its simpler block storage model. LVM thin provisioning offers snapshots and efficient space usage for LVM volumes, and can be used as an alternative to migrating to qcow2. Host devices Host devices such as physical CD-ROMs, raw disks, and logical unit numbers (LUNs) can be presented to the guest. This enables a guest to use storage area network (SAN) or iSCSI LUNs, as well as local CD-ROM media, with good performance. Host devices can be used when storage management is done on a SAN instead of on hosts. Distributed storage systems Gluster volumes can be used as disk images. This enables high-performance clustered storage over the network. Red Hat Enterprise Linux 6.5 and above includes native support for creating virtual machines with GlusterFS. This enables a KVM host to boot virtual machine images from GlusterFS volumes, and to use images from a GlusterFS volume as data disks for virtual machines. When compared to GlusterFS FUSE, the native support in KVM delivers higher performance. Note For more information on storage and virtualization, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide .

Commands:
Chapter 5. Management of Ceph daemons As a storage administrator, you can manage Ceph daemons on the Red Hat Ceph Storage dashboard. 5.1. Daemon actions The Red Hat Ceph Storage dashboard allows you to start, stop, restart, and redeploy daemons. Note These actions are supported on all daemons except monitor and manager daemons. Prerequisites A running Red Hat Ceph Storage cluster. Dashboard is installed. At least one daemon is configured in the storage cluster. Procedure You can manage daemons two ways. From the Services page: Log in to the dashboard. From the Cluster drop-down menu, select Services . View the details of the service with the daemon to perform the action on by clicking the Expand/Collapse icon on its row. In Details , select the drop down to the desired daemon to perform Start , Stop , Restart , or Redeploy . Figure 5.1. Managing daemons From the Hosts page: Log in to the dashboard. From the Cluster drop-down menu, select Hosts . From the Hosts List , select the host with the daemon to perform the action on. In the Daemon tab of the host, click the daemon. Use the drop down at the top to perform Start , Stop , Restart , or Redeploy . Figure 5.2. Managing daemons

Commands:
Chapter 1. Migration toolkit for containers overview You can migrate stateful application workloads between OpenShift Container Platform 4 clusters at the granularity of a namespace by using the Migration Toolkit for Containers (MTC). To learn more about MTC see understanding MTC . Note If you are migrating from OpenShift Container Platform 3, see about migrating from OpenShift Container Platform 3 to 4 and installing the legacy Migration Toolkit for Containers Operator on OpenShift Container Platform 3 . 1.1. Installing MTC You must install the Migration Toolkit for Containers Operator that is compatible for your OpenShift Container Platform version: OpenShift Container Platform 4.6 and later versions: Install the Migration Toolkit for Containers Operator by using Operator Lifecycle Manager (OLM) . OpenShift Container Platform 4.5 and earlier versions: Manually install the legacy Migration Toolkit for Containers Operator . Then you configure object storage to use as a replication repository . 1.2. Upgrading MTC You can upgrade the MTC by using OLM. 1.3. Reviewing MTC checklists Before you migrate your application workloads with the Migration Toolkit for Containers (MTC), review the premigration checklists . 1.4. Migrating applications You can migrate your applications by using the MTC web console or the command line . 1.5. Advanced migration options You can automate your migrations and modify the MigPlan and MigrationController custom resources in order to perform large-scale migrations and to improve performance. You can check the following items: Create a registry route for direct image migration Configuring proxies Migrating an application by using the MTC API Running a state migration Creating migration hooks Editing, excluding, and mapping migrated resources Configuring the migration controller for large migrations 1.6. Troubleshooting migrations You can perform the following troubleshooting tasks: Viewing plan resources Viewing the migration plan aggregated log file Using the migration log reader Accessing performance metrics Using the must-gather tool Using the Velero CLI to debug Backup and Restore CRs Debugging a partial migration failure Using MTC custom resources for troubleshooting Checking common issues and concerns 1.7. Rolling back a migration You can roll back a migration by using the MTC web console, the CLI or manually. 1.8. Uninstalling MTC and deleting resources You can uninstall the MTC and delete its resources to clean up the cluster.

Commands:
Appendix C. Using AMQ Broker with the examples The AMQ Core Protocol JMS examples require a running message broker with a queue named exampleQueue . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named exampleQueue . USD <broker-instance-dir> /bin/artemis queue create --name exampleQueue --address exampleQueue --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-08-24 14:25:38 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name exampleQueue --address exampleQueue --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop