mtpti5iD/redhat-docs_dataset huggingface dataset:
4.3. Brocade Fabric Switch Table 4.4, "Brocade Fabric Switch" lists the fence device parameters used by fence_brocade , the fence agent for Brocade FC switches. Table 4.4. Brocade Fabric Switch luci Field cluster.conf Attribute Description Name name A name for the Brocade device connected to the cluster. IP Address or Hostname ipaddr The IP address or host name assigned to the device. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Force IP Family inet4_only, inet6_only Force the agent to use IPv4 or IPv6 addresses only Force Command Prompt cmd_prompt The command prompt to use. The default value is '\USD'. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Port port The switch outlet number. Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0. Use SSH secure Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. SSH Options ssh_options SSH options to use. The default value is -1 -c blowfish . Path to SSH Identity File identity_file The identity file for SSH. Unfencing unfence section of the cluster configuration file When enabled, this ensures that a fenced node is not re-enabled until the node has been rebooted. This is necessary for non-power fence methods (that is, SAN/storage fencing). When you configure a device that requires unfencing, the cluster must first be stopped and the full configuration including devices and unfencing must be added before the cluster is started. For more information about unfencing a node, see the fence_node (8) man page. Figure 4.3, "Brocade Fabric Switch" shows the configuration screen for adding an Brocade Fabric Switch fence device. Figure 4.3. Brocade Fabric Switch The following command creates a fence device instance for a Brocade device: The following is the cluster.conf entry for the fence_brocade device:

Commands:
ccs -f cluster.conf --addfencedev brocadetest agent=fence_brocade ipaddr=brocadetest.example.com login=root passwd=password123
<fencedevices> <fencedevice agent="fence_brocade" ipaddr="brocadetest.example.com" login="brocadetest" name="brocadetest" passwd="brocadetest"/> </fencedevices>
Chapter 30. Real-Time Kernel Removing USB no longer causes a might_sleep() warning on MRG Realtime kernel Removing an USB device on MRG Realtime kernel previously caused taking a sleeping spin lock with interruptions disabled. Consequently,the system logged a might_sleep() warning. This update replaces the local_irq_disable and local_irq_enable calls by local_irq_disable_nort and local_irq_enable_nort , respectively, which fixes this bug. (BZ#1443711)

Commands:
6.3. Module Deployment Create a module under the "modules" directory and define the translator name and module name in the teiid subsystem in standalone.xml file or domain.xml file and restart the server. The dependent Red Hat JBoss Data Virtualization or any other Java class libraries must be defined in module.xml file of the module. For production profiles this is recommended. Example 6.1. Example module.xml file The following example is the module.xml file provided for the Salesforce translator. This file is located in the EAP_HOME /docs/teiid/datasources/salesforce/modules/org/springframework/spring/main directory.

Commands:
<module xmlns="urn:jboss:module:1.0" name="org.springframework.spring"> <resources> <resource-root path="spring-beans.jar"/> <resource-root path="spring-context.jar"/> <resource-root path="spring-core.jar"/> </resources> <dependencies> <module name="javax.api"/> </dependencies> </module>
Chapter 16. Installing Using Anaconda This chapter describes an installation using the graphical user interface of anaconda . 16.1. The Text Mode Installation Program User Interface While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. However, because text mode presents you with a simpler, more streamlined installation process, certain options that are available in graphical mode are not also available in text mode. These differences are noted in the description of the installation process in this guide, and include: configuring advanced storage methods such as LVM, RAID, FCoE, zFCP, and iSCSI. customizing the partition layout customizing the bootloader layout selecting packages during installation configuring the installed system with firstboot

Commands:
13.3. Certificate Management in Email Clients The following example shows how to manage certificates in the Mozilla Thunderbird email client. It represents a procedure to set up certificates in email clients in general. In Mozilla Thunderbird, open the Thunderbird main menu and select Preferences Account Settings . Select the Security item, and click View Certificates to open the Certificate Manager . Figure 13.7. Account Settings in Thunderbird To import a CA certificate: Download and save the CA certificate to your computer. In the Certificate Manager , choose the Authorities tab and click Import . Figure 13.8. Importing the CA Certificate in Thunderbird Select the downloaded CA certificate. To set the certificate trust relationships: In the Certificate Manager , under the Authorities tab, select the appropriate certificate and click Edit Trust . Edit the certificate trust settings. Figure 13.9. Editing the Certificate Trust Settings in Thunderbird To use a personal certificate for authentication: In the Certificate Manager , under the Your Certificates tab, click Import . Figure 13.10. Importing a Personal Certificate for Authentication in Thunderbird Select the required certificate from your computer. Close the Certificate Manager and return to the Security item in Account Settings . Under the Digital Signing section of the form, click Select to choose your personal certificate to use for signing messages. Under Encryption , click Select to choose your personal certificate to encrypt and decrypt messages.

Commands:
12.2. Delegating Host Management Hosts are delegated authority over other hosts through the host-add-managedby command. This creates a managedby entry. Once the managedby entry is created, then the host can retrieve a keytab for the host it has delegated authority over. Log in as the admin user. Add the managedby entry. For example, this delegates authority over client2 to client1. Obtain a ticket as the host client1 and then retrieve a keytab for client2 :

Commands:
kinit admin
ipa host-add-managedby client2.example.com --hosts=client1.example.com
kinit -kt /etc/krb5.keytab host/`hostname` ipa-getkeytab -s `hostname` -k /tmp/client2.keytab -p host/client2.example.com Keytab successfully retrieved and stored in: /tmp/client2.keytab
3.6. Saving Network Packet Filter Settings After configuring the appropriate network packet filters for your situation, save the settings so they get restored after a reboot. For iptables , type the following command: /sbin/service iptables save This saves the settings in /etc/sysconfig/iptables so they can be recalled at boot time. Once this file is written, you are able to use the /sbin/service command to start, stop, and check the status (using the status switch) of iptables . The /sbin/service will automatically load the appropriate module for you. For an example of how to use the /sbin/service command, see Section 2.3, "Starting the Piranha Configuration Tool Service" . Finally, you need to be sure the appropriate service is set to activate on the proper runlevels. For more on this, see Section 2.1, "Configuring Services on the LVS Router" . The chapter explains how to use the Piranha Configuration Tool to configure the LVS router and describe the steps necessary to activate the Load Balancer Add-On.

Commands:
probe::nfs.proc.read_done Name probe::nfs.proc.read_done - NFS client response to a read RPC task Synopsis nfs.proc.read_done Values timestamp V4 timestamp, which is used for lease renewal prot transfer protocol count number of bytes read version NFS version status result of last operation server_ip IP address of server Description Fires when a reply to a read RPC task is received or some read error occurs (timeout or socket shutdown).

Commands:
11.5. Naming Scheme for VLAN Interfaces Traditionally, VLAN interface names in the format: interface-name . VLAN-ID are used. The VLAN-ID ranges from 0 to 4096 , which is a maximum of four characters and the total interface name has a limit of 15 characters. The maximum interface name length is defined by the kernel headers and is a global limit, affecting all applications. In Red Hat Enterprise Linux 7, four naming conventions for VLAN interface names are supported: VLAN plus VLAN ID The word vlan plus the VLAN ID. For example: vlan0005 VLAN plus VLAN ID without padding The word vlan plus the VLAN ID without padding by means of additional leading zeros. For example: vlan5 Device name plus VLAN ID The name of the parent interface plus the VLAN ID. For example: enp1s0.0005 Device name plus VLAN ID without padding The name of the parent interface plus the VLAN ID without padding by means of additional leading zeros. For example: enp1s0.5

Commands:
7.9. Additional Resources A complete list of SSSD-related man pages is available in the SEE ALSO section in the sssd (8) man page. Troubleshooting advice: Section A.1, "Troubleshooting SSSD" . A procedure for configuring SSSD to process password expiration warnings sent by the server and display them to users on the local system: Setting Password Expiry in Red Hat Knowledgebase An SSSD client can automatically create a GID for every user retrieved from an LDAP server, and at the same time ensure that the GID matches the user's UID unless the GID number is already taken. To see how automatic creation of GIDs can be set up on an SSSD client which is directly integrated into Active Directory, see the corresponding section in the Windows Integration Guide .

Commands:
Chapter 102. KafkaUserTlsExternalClientAuthentication schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserTlsExternalClientAuthentication type from KafkaUserTlsClientAuthentication , KafkaUserScramSha512ClientAuthentication . It must have the value tls-external for the type KafkaUserTlsExternalClientAuthentication . Property Description type Must be tls-external . string

Commands:
6. Package Management 6.1. Strong package checksums RPM provides support for signed packages using strong hash algorithms such as SHA-256 in order to ensure package integrity and increase security. Red Hat Enterprise Linux 6 packages are transparently compressed with the XZ lossless compression library, which implements the LZMA2 compression algorithm for greater compression (thus reducing package size) and speedier unpacking (when installing RPMs). Further information on the stronger package checksums is available in the Deployment Guide 6.2. The PackageKit Package Manager Red Hat provides PackageKit for viewing, managing, updating, installing and uninstalling packages and package groups compatible with your system, and enabled in Yum repositories. PackageKit consists of several graphical interfaces that can be opened from the GNOME panel menu, or from the Notification Area, when PackageKit alerts you that updates are available. Additionally, PackageKit allows for quick repository enablement and disablement, a graphical and searchable transaction log, and PolicyKit integration. Futher information on Package Kit is available in the Deployment Guide 6.3. Yum Via its plugin architecture, Yum provides new or enhanced support for various capabilities such as delta RPMs (using the presto plugin), RHN communication (rhnplugin), and auditing and applying-using a calculated least-invasive (minimal) number of updates-only relevant security fixes to a system (security plugin). Yum also ships with the yum-config-manager utility, which shows exhaustive information about all set configuration options and parameters for each individual repository. Further information on updates to Yum is available in the Deployment Guide

Commands:
23.14. Hypervisor Features Hypervisors may allow certain CPU or machine features to be enabled ( state='on' ) or disabled ( state='off' ). ... <features> <pae/> <acpi/> <apic/> <hap/> <privnet/> <hyperv> <relaxed state='on'/> </hyperv> </features> ... Figure 23.24. Hypervisor features All features are listed within the <features> element, if a <state> is not specified it is disabled. The available features can be found by calling the capabilities XML, but a common set for fully virtualized domains are: Table 23.10. Hypervisor features elements State Description <pae> Physical address extension mode allows 32-bit guest virtual machines to address more than 4 GB of memory. <acpi> Useful for power management. For example, with KVM guest virtual machines it is required for graceful shutdown to work. <apic> Allows the use of programmable IRQ management. This element has an optional attribute eoi with values on and off , which sets the availability of EOI (End of Interrupt) for the guest virtual machine. <hap> Enables the use of hardware assisted paging if it is available in the hardware.

Commands:
<features> <pae/> <acpi/> <apic/> <hap/> <privnet/> <hyperv> <relaxed state='on'/> </hyperv> </features>
Chapter 7. Upgrading hosts to major Red Hat Enterprise Linux release You can use a job template to upgrade your Red Hat Enterprise Linux hosts to the major release. Below upgrade paths are possible: Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 Prerequisites Ensure that your Red Hat Enterprise Linux hosts meet the requirements for the upgrade. For Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 upgrade, see Planning an upgrade in Upgrading from RHEL 7 to RHEL 8 . For Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 upgrade, see Planning an upgrade to RHEL 9 in Upgrading from RHEL 8 to RHEL 9 . Prepare your Red Hat Enterprise Linux hosts for the upgrade. For Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 upgrade, see Preparing a RHEL 7 system for the upgrade in Upgrading from RHEL 7 to RHEL 8 . For Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 upgrade, see Preparing a RHEL 8 system for the upgrade in Upgrading from RHEL 8 to RHEL 9 . Distribute Satellite SSH keys to the hosts that you want to upgrade. For more information, see Section 13.14, "Distributing SSH keys for remote execution" . Procedure If you are using a custom job template for the Leapp pre-upgrade check, configure the leapp_preupgrade remote execution feature to point to your template: In the Satellite web UI, navigate to Administer > Remote Execution Features . Click leapp_preupgrade . In the Job Template dropdown menu, select your template. Click Submit . In the Satellite web UI, navigate to Hosts > All Hosts . Select the hosts that you want to upgrade to the major Red Hat Enterprise Linux version. From the Schedule Remote Job list, select Preupgrade check with Leapp . When the check is finished, click the Leapp preupgrade report tab to see if Leapp has found any issues on your hosts. Issues that have the Inhibitor flag are considered crucial and are likely to break the upgrade procedure. Issues that have the Has Remediation flag contain remediation that can help you fix the issue. Click an issue that is flagged as Has Remediation to expand it. If the issue contains a remediation Command , you can fix it directly from Satellite using remote execution. Select the issue. If the issue contains only a remediation Hint , use the hint to fix the issue on the host manually. Repeat this step for other issues. After you selected any issues with remediation commands, click Fix Selected and submit the job. After the issues are fixed, click Rerun , and then click Submit to run the pre-upgrade check again to verify that the hosts you are upgrading do not have any issues and are ready to be upgraded. If the pre-upgrade check verifies that the hosts do not have any issues, click Run Upgrade and click Submit to start the upgrade. Alternatively, you can upgrade your host by selecting Upgrade with Leapp in the Schedule Remote Job drop down menu.

Commands:
Appendix D. LVM Volume Group Metadata The configuration details of a volume group are referred to as the metadata. By default, an identical copy of the metadata is maintained in every metadata area in every physical volume within the volume group. LVM volume group metadata is small and stored as ASCII. If a volume group contains many physical volumes, having many redundant copies of the metadata is inefficient. It is possible to create a physical volume without any metadata copies by using the --metadatacopies 0 option of the pvcreate command. Once you have selected the number of metadata copies the physical volume will contain, you cannot change that at a later point. Selecting 0 copies can result in faster updates on configuration changes. Note, however, that at all times every volume group must contain at least one physical volume with a metadata area (unless you are using the advanced configuration settings that allow you to store volume group metadata in a file system). If you intend to split the volume group in the future, every volume group needs at least one metadata copy. The core metadata is stored in ASCII. A metadata area is a circular buffer. New metadata is appended to the old metadata and then the pointer to the start of it is updated. You can specify the size of metadata area with the --metadatasize . option of the pvcreate command. The default size is too small for volume groups with many logical volumes or physical volumes. D.1. The Physical Volume Label By default, the pvcreate command places the physical volume label in the 2nd 512-byte sector. This label can optionally be placed in any of the first four sectors, since the LVM tools that scan for a physical volume label check the first 4 sectors. The physical volume label begins with the string LABELONE . The physical volume label Contains: Physical volume UUID Size of block device in bytes NULL-terminated list of data area locations NULL-terminated lists of metadata area locations Metadata locations are stored as offset and size (in bytes). There is room in the label for about 15 locations, but the LVM tools currently use 3: a single data area plus up to two metadata areas.

Commands:
Chapter 3. Accessing the registry In OpenShift Dedicated, Red Hat Site Reliability Engineering (SRE) manages the registry for you. However, you can check the status of the registry pods and view the registry logs. 3.1. Checking the status of the registry pods As an administrator with the dedicated-admin role, you can list the image registry pods running in the openshift-image-registry project and check their status. Prerequisites You have access to the cluster as a user with the dedicated-admin role. Procedure List the pods in the openshift-image-registry project and view their status: USD oc get pods -n openshift-image-registry Example output NAME READY STATUS RESTARTS AGE image-registry-79fb4469f6-llrln 1/1 Running 0 77m node-ca-hjksc 1/1 Running 0 73m node-ca-tftj6 1/1 Running 0 77m node-ca-wb6ht 1/1 Running 0 77m node-ca-zvt9q 1/1 Running 0 74m 3.2. Viewing registry logs You can view the logs for the registry by using the oc logs command. Procedure Use the oc logs command with deployments to view the logs for the container image registry: USD oc logs deployments/image-registry -n openshift-image-registry Example output 2015-05-01T19:48:36.300593110Z time="2015-05-01T19:48:36Z" level=info msg="version=v2.0.0+unknown" 2015-05-01T19:48:36.303294724Z time="2015-05-01T19:48:36Z" level=info msg="redis not configured" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002 2015-05-01T19:48:36.303422845Z time="2015-05-01T19:48:36Z" level=info msg="using inmemory layerinfo cache" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002 2015-05-01T19:48:36.303433991Z time="2015-05-01T19:48:36Z" level=info msg="Using OpenShift Auth handler" 2015-05-01T19:48:36.303439084Z time="2015-05-01T19:48:36Z" level=info msg="listening on :5000" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002

Commands:
oc get pods -n openshift-image-registry
NAME READY STATUS RESTARTS AGE image-registry-79fb4469f6-llrln 1/1 Running 0 77m node-ca-hjksc 1/1 Running 0 73m node-ca-tftj6 1/1 Running 0 77m node-ca-wb6ht 1/1 Running 0 77m node-ca-zvt9q 1/1 Running 0 74m
oc logs deployments/image-registry -n openshift-image-registry
2015-05-01T19:48:36.300593110Z time="2015-05-01T19:48:36Z" level=info msg="version=v2.0.0+unknown" 2015-05-01T19:48:36.303294724Z time="2015-05-01T19:48:36Z" level=info msg="redis not configured" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002 2015-05-01T19:48:36.303422845Z time="2015-05-01T19:48:36Z" level=info msg="using inmemory layerinfo cache" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002 2015-05-01T19:48:36.303433991Z time="2015-05-01T19:48:36Z" level=info msg="Using OpenShift Auth handler" 2015-05-01T19:48:36.303439084Z time="2015-05-01T19:48:36Z" level=info msg="listening on :5000" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002