mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Preparing to deploy OpenShift Data Foundation Deploying OpenShift Data Foundation on OpenShift Container Platform using dynamic storage devices provides you with the option to create internal cluster resources. This will result in the internal provisioning of the base services, which helps to make additional storage classes available to applications. Before you begin the deployment of Red Hat OpenShift Data Foundation, follow these steps: Optional: If you want to enable cluster-wide encryption using an external Key Management System (KMS) then follow the steps: Ensure that you have a valid Red Hat OpenShift Data Foundation Advanced subscription. To know how subscriptions for OpenShift Data Foundation work, see knowledgebase article on OpenShift Data Foundation subscriptions . When the Token authentication method is selected for encryption then refer to Enabling cluster-wide encryption with the Token authentication using KMS . When the Kubernetes authentication method is selected for encryption then refer to Enabling cluster-wide encryption with the Kubernetes authentication using KMS . Ensure that you are using signed certificates on your Vault servers. Minimum starting node requirements An OpenShift Data Foundation cluster will be deployed with minimum configuration when the standard deployment resource requirement is not met. See Resource requirements section in Planning guide. Disaster recovery requirements [Technology Preview] Disaster Recovery features supported by Red Hat OpenShift Data Foundation require all of the following prerequisites to successfully implement a disaster recovery solution: A valid Red Hat OpenShift Data Foundation Advanced subscription A valid Red Hat Advanced Cluster Management for Kubernetes subscription To know how subscriptions for OpenShift Data Foundation work, see knowledgebase article on OpenShift Data Foundation subscriptions . For detailed requirements, see Configuring OpenShift Data Foundation Disaster Recovery for OpenShift Workloads guide, and Requirements and recommendations section of the Install guide in Red Hat Advanced Cluster Management for Kubernetes documentation.

Commands:
5.2. Known Issues If the qeth interface was previously configured using system-config-network 1.6.0.el6.2 , the "OPTIONS=" line needs to be manually added to /etc/sysconfig/network-scripts/ifcfg-<interface> . After the configuration has been manually changed, activate the interface by either rebooting the system, or running the following commands: A known issue in the bnx2 driver prevents BCM5709S network adapters from performing a vmcore core dump over NFS. Intel 82575EB ethernet devices do not function in a 32 bit environment. To work around this issue, modify the kernel parameters to include the intel_iommu=off option. Running the rds-ping command may fail, returning the error: Note, also that this error may occur even with LOAD_RDS=yes set in /etc/rdma/rdma.conf . To work around this issue, load the rds-tcp module. Running the command rds-stress on a client may result in the following error attempting to connect to the server: When configuring a network interface manually, including static IP addresses and search domains, it is possible that a search entry will not be propagated to /etc/resolv.conf . Consequently, short host names that do not include the domain name will fail to resolve. To workaround this issue, add a search entry manually to /etc/resolv.conf . Under some circumstances, the NetworkManager panel applet cannot determine if a user has permission to enable networking. Consequently, after logging into the desktop, the "Enable Networking" and "Enable Wireless" checkboxes may be disabled. To work around this, run the following command as root: Alternatively, WiFi can be enabled using the command: or disabled using the command: Under some circumstances, the netcf command crashes, returning the error message: To work around this issue, set the following value in /etc/sysctl.conf: This issue presents when the augeas library (used by netcf ) has trouble parsing one of the system config files that netcf needs to read or modify. The default value of the Emulex lpfc module parameter, lpfc_use_msi, was 2 (MSI-X) on Red Hat Enterprise Linux 5.4. In Red Hat Enterprise Linux 6 this default is now set to 0 (INTx). This change causes the driver behavior to stop using MSI-X interrupt mode and reverts to using non-msi (INTx) interrupt mode. This change in defaults addresses apparent regressions in some hardware platforms, introduced when the default lpfc driver value was previously changed from 0 to 2 (which made MSI-X the default behavior). If the lpfc module is behaving erratically, work around this issue by setting the lpfc module parameter lpfc_use_msi to 2.

Commands:
/sbin/znet_cio_free SUBSYSTEM="ccw" DEVPATH="bus/ccw/devices/<SUBCHANNEL 0>" /lib/udev/ccw_init ifup <interface>
bind() failed, errno: 99 (Cannot assign requested address).
connecting to <server IP address>:4000: No route to host connect(<server IP address>) failed#
touch /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy
nmcli nm wifi on
nmcli nm wifi off
Failed to initialize netcf error: unspecified error
net.bridge.bridge-nf-call-iptables = 0
30.2. Text Mode If you installed Red Hat Enterprise Linux without the X Window System , the Initial Setup starts in text mode: Figure 30.4. Initial Setup in text mode To configure an entry, enter the menu number and press Enter . Additionally, you can press the following keys: q to close the application. Until you accepted the license agreement, closing the application causes the system to reboot. c to continue. Pressing this key in a submenu returns you to the main menu. In the main menu, pressing the c key stores the settings and closes the application. Note that you cannot continue without accepting the license agreement. r to refresh the menu. Menu entries can have different statuses: [x] : This setting is already configured. However, you can change the setting. [!] : This setting is mandatory but not yet set. [ ] : This setting is optional and not yet set. To start the Initial Setup again, see Section 30.3, "Starting Initial Setup Manually" .

Commands:
Appendix A. Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Enterprise Linux. Revision History Revision 6.7-4 Wed Mar 8 2017 Aneta Steflova Petrova Version for 6.9 GA publication. Revision 6.7-3 Wed May 4 2016 Marc Muehlfeld Preparing document for 6.8 GA publication. Revision 6.7-2 Thu Jan 7 2016 Aneta Petrova Rebuilt with an updated brand. Revision 6.7-1 Tue Jan 5 2016 Aneta Petrova Fixed rendering of PAM configuration examples. Revision 6.7-0 Tue Jul 14 2015 Tomas Capek Version for 6.7 GA release. Revision 6.6-1 Fri Dec 19 2014 Tomas Capek Rebuilt to update the sort order on the splash page. Revision 6.6-0 Fri Oct 10 2014 Tomas Capek Version for 6.6 GA release. Revision 6.4-0 March 28, 2013 Ella Deon Lackey Fixed formatting for publican upgrade. Revision 6.2-4 December 5, 2011 Ella Deon Lackey Release for 6.2. GA. Added PIV and CAC card to supported smart cards list. Revision 6.1-0 Thu May 5, 2011 Ella Deon Lackey Fixed bugs, other updates. Revision 6.0-0 Thu Oct 22 2009 Ella Deon Lackey Initial draft for Red Hat Enterprise Linux 6.

Commands:
11.2.9. Dialup Interfaces If you are connecting to the Internet via a dialup connection, a configuration file is necessary for the interface. PPP interface files are named using the following format: ifcfg-ppp X where X is a unique number corresponding to a specific interface. The PPP interface configuration file is created automatically when wvdial , or Kppp is used to create a dialup account. It is also possible to create and edit this file manually. The following is a typical /etc/sysconfig/network-scripts/ifcfg-ppp0 file: Serial Line Internet Protocol ( SLIP ) is another dialup interface, although it is used less frequently. SLIP files have interface configuration file names such as ifcfg-sl0 . Other options that may be used in these files include: DEFROUTE = answer where answer is one of the following: yes - Set this interface as the default route. no - Do not set this interface as the default route. DEMAND = answer where answer is one of the following: yes - This interface allows pppd to initiate a connection when someone attempts to use it. no - A connection must be manually established for this interface. IDLETIMEOUT = value where value is the number of seconds of idle activity before the interface disconnects itself. INITSTRING = string where string is the initialization string passed to the modem device. This option is primarily used in conjunction with SLIP interfaces. LINESPEED = value where value is the baud rate of the device. Possible standard values include 57600 , 38400 , 19200 , and 9600 . MODEMPORT = device where device is the name of the serial device that is used to establish the connection for the interface. MTU = value where value is the Maximum Transfer Unit ( MTU ) setting for the interface. The MTU refers to the largest number of bytes of data a frame can carry, not counting its header information. In some dialup situations, setting this to a value of 576 results in fewer packets dropped and a slight improvement to the throughput for a connection. NAME = name where name is the reference to the title given to a collection of dialup connection configurations. PAPNAME = name where name is the user name given during the Password Authentication Protocol ( PAP ) exchange that occurs to allow connections to a remote system. PERSIST = answer where answer is one of the following: yes - This interface should be kept active at all times, even if deactivated after a modem hang up. no - This interface should not be kept active at all times. REMIP = address where address is the IP address of the remote system. This is usually left unspecified. WVDIALSECT = name where name associates this interface with a dialer configuration in /etc/wvdial.conf . This file contains the phone number to be dialed and other important information for the interface.

Commands:
DEVICE=ppp0 NAME=test WVDIALSECT=test MODEMPORT=/dev/modem LINESPEED=115200 PAPNAME=test USERCTL=true ONBOOT=no PERSIST=no DEFROUTE=yes PEERDNS=yes DEMAND=no IDLETIMEOUT=600
Chapter 10. Deploying with Key Manager If you have deployed edge sites to the release of Red Hat OpenStack Platform 16.1.2, you will need to regenerate roles.yaml to implement this feature: To implement the feature, regenerate the roles.yaml file used for the DCN site's deployment. 10.1. Deploying edge sites with Key Manager If you want to include access to the Key Manager (barbican) service at edge sites, you must configure barbican at the central location. For information on installing and configuring barbican, see Deploying Barbican . You can configure access to barbican from DCN sites by including the /usr/share/openstack-tripleo-heat-templates/environments/services/barbican-edge.yaml .

Commands:
openstack overcloud roles generate DistributedComputeHCI DistributedComputeHCIScaleOut -o ~/dcn0/roles_data.yaml
openstack overcloud deploy --stack dcn0 --templates /usr/share/openstack-tripleo-heat-templates/ -r ~/dcn0/roles_data.yaml . -e /usr/share/openstack-tripleo-heat-templates/environments/services/barbican-edge.yaml
2.5. Disaster Recovery Disaster recovery is quicker and easier when the systems are virtualized. On a physical system, if something serious goes wrong, a complete reinstall of the operating system is usually required, resulting in hours of recovery time. However, if the systems are virtualized this is much faster due to the migration ability. If the requirements for live migration are followed, virtual machines can be restarted on another host, and the longest possible delay would be in restoring guest data. Also, because each of the virtualized systems are completely separate from each other, one system's downtime will not affect any others.

Commands:
Chapter 61. Enabling notifications in the Red Hat Customer Portal You can enable notifications in the Red Hat Customer Portal to receive product updates and announcements. These notifications inform you of updated or added documentation, product releases, and patch updates related to your installation. With notifications enabled, you can more readily apply product updates as they become available in the Red Hat Customer Portal to keep your distribution current with the latest enhancements and fixes. Prerequisites You have a Red Hat Customer Portal account and are logged in. Procedure In the top-right corner of the Red Hat Customer Portal window, click your profile name and click Notifications . Select the Notifications tab and click Manage Notifications . to Follow , select Products from the drop-down menu, and then select Red Hat Process Automation Manager or Red Hat Decision Manager from the drop-down menu that appears. Click Save Notification to finish. You can add notifications for any other products as needed in the same way.

Commands:
7.83. hwdata 7.83.1. RHEA-2013:0376 - hwdata enhancement update An updated hwdata package that adds various enhancements is now available for Red Hat Enterprise Linux 6. The hwdata package contains tools for accessing and displaying hardware identification and configuration data. Enhancements BZ# 839221 The PCI ID numbers have been updated for the Beta and the Final compose lists. BZ#739816 Support for NVidia graphic card N14E-Q5, 0x11BC has been added. BZ#739819 Support for NVidia graphic card N14E-Q3, 0x11BD has been added. BZ#739821 Support for NVidia graphic card N14E-Q1, 0x11BE has been added. BZ#739824 Support for NVidia graphic card N14P-Q3, 0x0FFB has been added. BZ#739825 Support for NVidia graphic card N14P-Q1, 0x0FFC has been added. BZ#760031 Support for Broadcom BCM943228HM4L 802.11a/b/g/n 2x2 Wi-Fi Adapter has been added. BZ#830253 Support for Boot from Dell PowerEdge Express Flash PCIe SSD devices has been added. BZ#841423 Support for the Intel C228 chipset and a future Intel processor based on Socket H3 has been added. BZ#814114 This update also adds the current hardware USB IDs file from the upstream repository. This file provides support for Broadcom 20702 Bluetooth 4.0 Adapter Softsailing. All users of hwdata are advised to upgrade to this updated package, which adds these enhancements.

Commands:
Chapter 15. Planning for Installation on IBM Z 15.1. Pre-installation Red Hat Enterprise Linux 7 runs on zEnterprise 196 or later IBM mainframe systems. The installation process assumes that you are familiar with the IBM Z and can set up logical partitions (LPARs) and z/VM guest virtual machines. For additional information on IBM Z, see http://www.ibm.com/systems/z . For installation of Red Hat Enterprise Linux on IBM Z, Red Hat supports DASD (Direct Access Storage Device) and FCP (Fiber Channel Protocol) storage devices. Before you install Red Hat Enterprise Linux, you must decide on the following: Decide whether you want to run the operating system on an LPAR or as a z/VM guest operating system. Decide if you need swap space and if so, how much. Although it is possible (and recommended) to assign enough memory to a z/VM guest virtual machine and let z/VM do the necessary swapping, there are cases where the amount of required RAM is hard to predict. Such instances should be examined on a case-by-case basis. See Section 18.15.3.4, "Recommended Partitioning Scheme" . Decide on a network configuration. Red Hat Enterprise Linux 7 for IBM Z supports the following network devices: Real and virtual Open Systems Adapter (OSA) Real and virtual HiperSockets LAN channel station (LCS) for real OSA You require the following hardware: Disk space. Calculate how much disk space you need and allocate sufficient disk space on DASDs [2] or SCSI [3] disks. You require at least 10 GB for a server installation, and 20 GB if you want to install all packages. You also require disk space for any application data. After the installation, you can add or delete more DASD or SCSI disk partitions. The disk space used by the newly installed Red Hat Enterprise Linux system (the Linux instance) must be separate from the disk space used by other operating systems you have installed on your system. For more information about disks and partition configuration, see Section 18.15.3.4, "Recommended Partitioning Scheme" . RAM. Acquire 1 GB (recommended) for the Linux instance. With some tuning, an instance might run with as little as 512 MB RAM. Note When initializing swap space on an FBA ( Fixed Block Architecture ) DASD using the SWAPGEN utility, the FBAPART option must be used. [2] Direct Access Storage Devices (DASDs) are hard disks that allow a maximum of three partitions per device. For example, dasda can have partitions dasda1 , dasda2 , and dasda3 . [3] Using the SCSI-over-Fibre Channel device driver (the zfcp device driver) and a switch, SCSI LUNs can be presented to Linux on IBM Z as if they were locally attached SCSI drives.

Commands:
2.8.2.5. Saving the Settings Click OK to save the changes and enable or disable the firewall. If Enable firewall was selected, the options selected are translated to iptables commands and written to the /etc/sysconfig/iptables file. The iptables service is also started so that the firewall is activated immediately after saving the selected options. If Disable firewall was selected, the /etc/sysconfig/iptables file is removed and the iptables service is stopped immediately. The selected options are also written to the /etc/sysconfig/system-config-firewall file so that the settings can be restored the time the application is started. Do not edit this file manually. Even though the firewall is activated immediately, the iptables service is not configured to start automatically at boot time. Refer to Section 2.8.2.6, "Activating the IPTables Service" for more information.

Commands:
Chapter 2. Customizing and managing Red Hat Ceph Storage Red Hat OpenStack Services on OpenShift (RHOSO) 18.0 supports Red Hat Ceph Storage 7. For information on the customization and management of Red Hat Ceph Storage 7, refer to the Red Hat Ceph Storage documentation . The following guides contain key information and procedures for these tasks: Administration Guide Configuration Guide Operations Guide Data Security and Hardening Guide Dashboard Guide Troubleshooting Guide

Commands:
14.7. Security and Data Access You have some options on defining your data access security for your VDB via the VDB Editor. The first level is provided by the model visibility check-box in the Models section (Spyglass column). If unchecked, that model and its contents will not be returned by the Teiid runtime with the standard JDBC metadata. The level of security is provided defining permissions for your data roles which can be managed via Data Roles tab in the VDB Editor. For a unique data role, each model and most objects within that model can have specific values of data access including the following: Security (Row-based condition and column masking) Create Read Update Delete Execute Alter Double-clicking the Security box for a table will launch the Row Filter Definition dialog where you can define condition. Double-clicking the Security box for a column will launch the Column Masking Definition dialog where you can define condition and column masking. In order to edit or remove security, select the Row Filter or Column Masking tabs and use the Edit or Remove buttons. Figure 14.2. Data Role dialog

Commands:
B.11. Unable to add bridge br0 port vnet0: No such device Symptom The following error message appears: For example, if the bridge name is br0 , the error message will appear as: In libvirt versions 0.9.6 and earlier, the same error appears as: Or for example, if the bridge is named br0 : Investigation Both error messages reveal that the bridge device specified in the guest's (or domain's) <interface> definition does not exist. To verify the bridge device listed in the error message does not exist, use the shell command ip addr show br0 . A message similar to this confirms the host has no bridge by that name: If this is the case, continue to the solution. However, if the resulting message is similar to the following, the issue exists elsewhere: Solution Edit the existing bridge or create a new bridge with virsh Use virsh to either edit the settings of an existing bridge or network, or to add the bridge device to the host system configuration. Edit the existing bridge settings using virsh Use virsh edit name_of_guest to change the <interface> definition to use a bridge or network that already exists. For example, change type='bridge' to type='network' , and <source bridge='br0'/> to <source network='default'/> . Create a host bridge using virsh For libvirt version 0.9.8 and later, a bridge device can be created with the virsh iface-bridge command. This will create a bridge device br0 with eth0 , the physical network interface which is set as part of a bridge, attached: Optional: If desired, remove this bridge and restore the original eth0 configuration with this command: Create a host bridge manually For older versions of libvirt , it is possible to manually create a bridge device on the host. Refer to Section 11.3, "Bridged Networking with libvirt" for instructions.

Commands:
Unable to add bridge name_of_bridge port vnet0: No such device
Unable to add bridge br0 port vnet0: No such device
Failed to add tap interface to bridge name_of_bridge : No such device
Failed to add tap interface to bridge 'br0' : No such device
br0 : error fetching interface information: Device not found
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/ether 1b:c4:94:cf:fd:17 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global br0
virsh iface-bridge eth0 br0
virsh iface-unbridge br0
17.4. Connection Factories In Red Hat JBoss Data Grid, all JDBC cache stores rely on a ConnectionFactory implementation to obtain a database connection. This process is also known as connection management or pooling. A connection factory can be specified using the ConnectionFactoryClass configuration attribute. JBoss Data Grid includes the following ConnectionFactory implementations: ManagedConnectionFactory SimpleConnectionFactory. PooledConnectionFactory. Report a bug 17.4.1. About ManagedConnectionFactory ManagedConnectionFactory is a connection factory that is ideal for use within managed environments such as application servers. This connection factory can explore a configured location in the JNDI tree and delegate connection management to the DataSource . Report a bug 17.4.2. About SimpleConnectionFactory SimpleConnectionFactory is a connection factory that creates database connections on a per invocation basis. This connection factory is not designed for use in a production environment. Report a bug

Commands: