mtpti5iD/redhat-docs_dataset huggingface dataset:
31.3. Installation Using VNC Now that you have installed a VNC viewer application and selected a VNC mode for use in anaconda, you are ready to begin the installation. 31.3.1. Installation Example The easiest way to perform an installation using VNC is to connect another computer directly to the network port on the target system. The laptop on a datacenter crash cart usually fills this role. If you are performing your installation this way, make sure you follow these steps: Connect the laptop or other workstation to the target system using a crossover cable. If you are using regular patch cables, make sure you connect the two systems using a small hub or switch. Most recent Ethernet interfaces will automatically detect if they need to be crossover or not, so it may be possible to connect the two systems directly using a regular patch cable. Configure the VNC viewer system to use a RFC 1918 address with no gateway. This private network connection will only be used for the purpose of installation. Configure the VNC viewer system to be 192.168.100.1/24. If that address is in use, just pick something else in the RFC 1918 address space that is available to you. Start the installation on the target system. Booting the installation DVD. If booting the installation DVD, make sure vnc is passed as a boot parameter. To add the vnc parameter, you will need a console attached to the target system that allows you to interact with the boot process. Enter the following at the prompt: Boot over the network. If the target system is configured with a static IP address, add the vnc command to the kickstart file. If the target system is using DHCP, add vncconnect= HOST to the boot arguments for the target system. HOST is the IP address or DNS host name of the VNC viewer system. Enter the following at the prompt: When prompted for the network configuration on the target system, assign it an available RFC 1918 address in the same network you used for the VNC viewer system. For example, 192.168.100.2/24. Note This IP address is only used during installation. You will have an opportunity to configure the final network settings, if any, later in the installer. Once the installer indicates it is starting anaconda, you will be instructed to connect to the system using the VNC viewer. Connect to the viewer and follow the graphical installation mode instructions found in the product documentation.

Commands:
boot: linux vnc
boot: linux vncconnect= HOST
23.2. Using PTP In order to use PTP , the kernel network driver for the intended interface has to support either software or hardware time stamping capabilities. 23.2.1. Checking for Driver and Hardware Support In addition to hardware time stamping support being present in the driver, the NIC must also be capable of supporting this functionality in the physical hardware. The best way to verify the time stamping capabilities of a particular driver and NIC is to use the ethtool utility to query the interface as follows: Where eth3 is the interface you want to check. For software time stamping support, the parameters list should include: SOF_TIMESTAMPING_SOFTWARE SOF_TIMESTAMPING_TX_SOFTWARE SOF_TIMESTAMPING_RX_SOFTWARE For hardware time stamping support, the parameters list should include: SOF_TIMESTAMPING_RAW_HARDWARE SOF_TIMESTAMPING_TX_HARDWARE SOF_TIMESTAMPING_RX_HARDWARE

Commands:
~]# ethtool -T eth3 Time stamping parameters for eth3: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) software-receive (SOF_TIMESTAMPING_RX_SOFTWARE) software-system-clock (SOF_TIMESTAMPING_SOFTWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 0 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL)
Chapter 20. Time Parameters You can modify the time synchronization service with time parameters. Parameter Description ChronyAclRules Access Control List of NTP clients. By default no clients are permitted. The default value is ['deny all'] . ChronyGlobalPoolOptions Default pool options for the configured NTP pools in chrony.conf. If this is specified, NtpIburstEnable, MaxPoll, and MinPoll are ignored. ChronyGlobalServerOptions Default server options for the configured NTP servers in chrony.conf. If this is specified, NtpIburstEnable, MaxPoll, and MinPoll are ignored. EnablePackageInstall Set to true to enable package installation at deploy time. The default value is false . MaxPoll Specify maximum poll interval of upstream servers for NTP messages, in seconds to the power of two. Allowed values are 4 to 17. The default value is 10 . MinPoll Specify minimum poll interval of upstream servers for NTP messages, in seconds to the power of two. The minimum poll interval defaults to 6 (64 s). Allowed values are 4 to 17. The default value is 6 . NtpIburstEnable Specifies whether to enable the iburst option for every NTP peer. If iburst is enabled, when the NTP server is unreachable NTP will send a burst of eight packages instead of one. This is designed to speed up the initial syncrhonization. The default value is True . NtpPool NTP pool list. Defaults to [], so only NtpServer is used by default. NtpServer NTP servers list. The default value is ['0.pool.ntp.org', '1.pool.ntp.org', '2.pool.ntp.org', '3.pool.ntp.org'] . TimeZone The timezone to be set on the overcloud. The default value is UTC .

Commands:
6.7. Dynamic VDB XML Deployment You can create a NAME -vdb.xml file. The XML file captures information about the VDB, the sources it integrates, and preferences for importing metadata. Note The VDB name pattern must adhere to "-vdb.xml" for the VDB deployer to recognize this file. The XML schema for these files is found in EAP_HOME /docs/teiid/schema/vdb-deployer.xsd .

Commands:
7.248. system-config-lvm 7.248.1. RHBA-2013:0385 - system-config-lvm bug fix update Updated system-config-lvm packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The system-config-lvm packages contain a utility for configuring logical volumes (LVs) using a graphical user interface. Bug Fixes BZ# 852864 When there was a RAID1 mirrored volume created using the lvm utility, system-config-lvm did not start correctly. The underlying source code has been modified to prevent system-config-lvm from terminating unexpectedly. The RAID1 volumes are now shown properly, however, they are visible as its underlying logical volumes. BZ# 820539 During an attempt to work with a mirror log, the system-config-lvm utility failed on start. This bug has been fixed and mirrored volumes are now supported as expected. BZ#840070 Due to a bug in the best_fit() function, which tried to fit all existing logical volumes (LVs) into the display area, system-config-lvm did not start correctly on systems with large amount of existing LVs. This bug has been fixed and system-config-lvm is fully functional even on systems with more then 350 LVs. All users of system-config-lvm are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 2. Adding a User Storage Provider (LDAP/Kerberos) to Ansible Automation Platform Central Authentication Ansible Automation Platform Central Authentication comes with a built-in LDAP/AD provider. You can add your LDAP provider to central authentication to be able to import user attributes from your LDAP database. Prerequisites You are logged in as an SSO admin user. Procedure Log in to Ansible Automation Platform Central Authentication as an SSO admin user. From the navigation bar, select Configure section User Federation . Note When using an LDAP User Federation in RH-SSO, a group mapper must be added to the client configuration, ansible-automation-platform, to expose the identity provider (IDP) groups to the SAML authentication. Refer to OIDC Token and SAML Assertion Mappings for more information on SAML assertion mappers. Using the dropdown menu labeled Add provider , select your LDAP provider to proceed to the LDAP configuration page. The following table lists the available options for your LDAP configuration: Configuration Option Description Storage mode Set to On if you want to import users into the central authentication user database. See Storage Mode for more information. Edit mode Determines the types of modifications that admins can make on user metadata. See Edit Mode for more information. Console Display Name Name used when this provider is referenced in the admin console Priority The priority of this provider when looking up users or adding a user Sync Registrations Enable if you want new users created by Ansible Automation Platform Central Authentication in the admin console or the registration page to be added to LDAP Allow Kerberos authentication Enable Kerberos/SPNEGO authentication in the realm with users data provisioned from LDAP. See Kerberos for more information.

Commands:
Appendix B. Revision History Revision History Revision 4-5 Wed Mar 8 2017 Steven Levine Version for 6.9 GA publication. Revision 4-4 Fri Dec 16 2016 Steven Levine Version for 6.9 Beta publication. Revision 3-4 Wed Apr 27 2016 Steven Levine Preparing document for 6.8 GA publication. Revision 3-3 Wed Mar 9 2016 Steven Levine Initial revision for Red Hat Enterprise Linux 6.8 Beta release Revision 2-5 Wed Jul 22 2015 Steven Levine Republish for Red Hat Enterprise Linux 6.7 Revision 2-4 Wed Jul 8 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Revision 2-1 Tue Apr 14 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Beta release Revision 1-13 Thu Oct 9 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Revision 1-10 Tue Nov 19 2013 John Ha Initial revision for Red Hat Enterprise Linux 6.5 Revision 1-8 Fri Sep 27 2013 John Ha Initial revision for Red Hat Enterprise Linux 6.5 Beta release Revision 1-4 Wed Nov 28 2012 John Ha Initial revision for Red Hat Enterprise Linux 6.4 Beta release Revision 1-3 Mon Jun 18 2012 John Ha Initial revision for Red Hat Enterprise Linux 6.3 Revision 1-2 Fri Dec 2 2011 John Ha Initial revision for Red Hat Enterprise Linux 6.2 Revision 1-1 Wed Nov 10 2010 Paul Kennedy Initial release of Red Hat Enterprise Linux 6

Commands:
Chapter 5. Validate the Sensu Client Installation Check the status of the sensu-client on each overcloud node: Review the error log for any issues: /var/log/containers/sensu/sensu-client.log Verify that each overcloud node has the /var/lib/config-data/puppet-generated/sensu/etc/sensu/conf.d/rabbitmq.json file that sets the IP address of the monitoring server.

Commands:
podman ps | grep sensu-client
Chapter 1. Introduction to Red Hat Hybrid Cloud Console notifications Through the notifications service, Red Hat Hybrid Cloud Console services have a standardized way of notifying users of events. By setting up behavior groups, a Notifications administrator specifies the notification delivery method and whether event notifications are sent to all users on an account, specific users, or only to Organization Administrators. For example, the Notifications administrator can configure the service to send an email notification for new-recommendation hits on a system. An Organization Administrator designates Notifications administrators by creating a User Access group with the Notifications administrator role, then adding account members to the group. A Notifications administrator then configures notification behavior groups that define actions taken when service-specific events occur. The notifications service transmits event-triggered notifications to users' email accounts. Users on the Hybrid Cloud Console account set their own preferences for receiving email notifications. In Settings > Notifications > Notification preferences , each user configures their personal settings to receive event notification emails as an instant notification or daily digest. 1.1. Hybrid Cloud Console notification service concepts Review key concepts to understand how the notifications service works: Table 1.1. Notifications concepts Concept Description Actions Operations are performed in response to an event,for example sending an email. Actions are defined in behavior groups that are configured by a Notifications administrator. Application bundle Application bundle refers to an application group within the Hybrid Cloud Console, such as Red Hat Enterprise Linux or OpenShift. Behavior groups Behavior groups determine what actions to take when an event occurs, and whether to notify all account users or only designated administrators. After a Notifications administrator creates a behavior group, they associate it with event types which enables Notifications administrators to apply the same actions to all application-specific events. NOTE: Notifications administrators configure notification behavior groups separately for each application bundle. Email preferences Individual users with access to applications on the Hybrid Cloud Console set their personal email preferences. Users can configure personal email notifications to arrive either instantly, as the event occurs, or consolidated into a daily digest that arrives at midnight, 00:00 Coordinated Universal Time (UTC), for all accounts. IMPORTANT: Selecting instant notification for any service can potentially result in the recipient receiving a very large number of emails. Event type Event types are application-specific system changes that trigger the application or service to initiate notification actions. Event types are created by application developers at Red Hat and are unique for each application bundle. User access roles The following User Access roles interact with notifications: * Organization Administrator * Notifications administrator * Notifications viewer

Commands:
1.2. Virtualization Solutions Red Hat offers two major virtualization solutions with different user focuses and features: Red Hat Enterprise Linux The ability to create, run, and manage virtual machines, as well as a number of vitualization tools and features , are included in Red Hat Enterprise Linux 6. This solution supports a limited number of running guests per host, as well as a limited range of guest types. As such, virtualization on Red Hat Enterprise Linux can be useful for example to developers who require testing in multiple environments, or to small businesses running several servers that do not have strict uptime requirements or service-level agreements (SLAs). Red Hat Virtualization Red Hat Virtualization is based on the Kernel-based Virtual Machine ( KVM ) technology like virtualization on Red Hat Enterprise Linux is, but offers an enhanced array of features. Designed for enterprise-class scalability and performance, it enables management of your entire virtual infrastructure, including hosts, virtual machines, networks, storage, and users from a centralized graphical interface. Red Hat Virtualization can be used by enterprises running larger deployments or mission-critical applications. Examples of large deployments suited to Red Hat Virtualization include databases, trading platforms, and messaging systems that must run continuously without any downtime. Note This guide provides information about virtualization on Red Hat Enterprise Linux. For more information about Red Hat Virtualization, or to download a fully supported 60-day evaluation version, see http://www.redhat.com/en/technologies/virtualization/enterprise-virtualization

Commands:
2.2.7. Python The python package adds support for the Python programming language. This package provides the object and cached bytecode files required to enable runtime support for basic Python programs. It also contains the python interpreter and the pydoc documentation tool. The python-devel package contains the libraries and header files required for developing Python extensions. Red Hat Enterprise Linux also ships with numerous python -related packages. By convention, the names of these packages have a python prefix or suffix. Such packages are either library extensions or python bindings to an existing library. For instance, dbus-python is a Python language binding for D-Bus. Note that both cached bytecode ( * .pyc / * .pyo files) and compiled extension modules ( * .so files) are incompatible between Python 2.4 (used in Red Hat Enterprise Linux 5) and Python 2.6 (used in Red Hat Enterprise Linux 6). As such, you will be required to rebuild any extension modules you use that are not part of Red Hat Enterprise Linux. 2.2.7.1. Python Updates The Red Hat Enterprise Linux 6 version of Python features various language changes. For information about these changes, see the following project resources: What's New in Python 2.5: http://docs.python.org/whatsnew/2.5.html What's New in Python 2.6: http://docs.python.org/whatsnew/2.6.html Both resources also contain advice on porting code developed using Python versions.

Commands:
20.16.16. Channel This represents a private communication channel between the host physical machine and the guest virtual machine and is manipulated by making changes to your guest virtual machine virtual machine using a management tool that results in changes made to the following section of the domain xml ... <devices> <channel type='unix'> <source mode='bind' path='/tmp/guestfwd'/> <target type='guestfwd' address='10.0.2.1' port='4600'/> </channel> <!-- KVM virtio channel --> <channel type='pty'> <target type='virtio' name='arbitrary.virtio.serial.port.name'/> </channel> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/f16x86_64.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> </channel> </devices> ... Figure 20.63. Channel This can be implemented in a variety of ways. The specific type of <channel> is given in the type attribute of the <target> element. Different channel types have different target attributes as follows: guestfwd - Dictates that TCP traffic sent by the guest virtual machine to a given IP address and port is forwarded to the channel device on the host physical machine. The target element must have address and port attributes. virtio - Paravirtualized virtio channel. <channel> is exposed in the guest virtual machine under /dev/vport* , and if the optional element name is specified, /dev/virtio-ports/USDname (for more info, see http://fedoraproject.org/wiki/Features/VirtioSerial). The optional element address can tie the channel to a particular type='virtio-serial' controller, documented above. With QEMU, if name is "org.qemu.guest_agent.0", then libvirt can interact with a guest virtual machine agent installed in the guest virtual machine, for actions such as guest virtual machine shutdown or file system quiescing. spicevmc - Paravirtualized SPICE channel. The domain must also have a SPICE server as a graphics device, at which point the host physical machine piggy-backs messages across the main channel. The target element must be present, with attribute type='virtio'; an optional attribute name controls how the guest virtual machine will have access to the channel, and defaults to name='com.redhat.spice.0' . The optional <address> element can tie the channel to a particular type='virtio-serial' controller.

Commands:
<devices> <channel type='unix'> <source mode='bind' path='/tmp/guestfwd'/> <target type='guestfwd' address='10.0.2.1' port='4600'/> </channel> <!-- KVM virtio channel --> <channel type='pty'> <target type='virtio' name='arbitrary.virtio.serial.port.name'/> </channel> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/f16x86_64.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> </channel> </devices>
Chapter 8. Ceph debugging and logging configuration As a storage administrator, you can increase the amount of debugging and logging information in cephadm to help diagnose problems with Red Hat Ceph Storage. 8.1. Prerequisites Red Hat Ceph Storage software is installed. 8.2. Additional Resources For more information about troubleshooting cephadm , see Cephadm troubleshooting in the Red Hat Ceph Storage Administration Guide . For more information about cephadm logging, see Cephadm operations in the Red Hat Ceph Storage Administration Guide .

Commands:
18.6. ip6tables and IPv6 If the iptables-ipv6 package is installed, netfilter under Red Hat Enterprise Linux can filter the -generation IPv6 Internet protocol. The command used to manipulate the IPv6 netfilter is ip6tables . Most directives for this command are identical to those used for iptables , except the nat table is not yet supported. This means that it is not yet possible to perform IPv6 network address translation tasks, such as masquerading and port forwarding. Saved rules for ip6tables are stored in the /etc/sysconfig/ip6tables file. Old rules saved by the ip6tables initscripts are saved in the /etc/sysconfig/ip6tables.save file. The configuration file for ip6tables initscript is /etc/sysconfig/ip6tables-config and the names for each directive vary slightly. For instance, the iptables-config directive IPTABLES_MODULES is IP6TABLES_MODULES in the ip6tables-config file.

Commands:
9.2.3. Other Host-based IDSes The following list discusses some of the other popular host-based intrusion detection systems available. Refer to the websites of the respective utilities for more information regarding installation and configuration. Note These applications are not included with Red Hat Enterprise Linux and are not supported. They have been included in this document as a reference to users who may be interested in evaluating such applications. SWATCH http://sourceforge.net/projects/swatch/ - The Simple WATCHer (SWATCH) uses log files generated by syslog to alert administrators of anomalies based on user configuration files. SWATCH was designed to log any event that the user wants to add into the configuration file; however, it has been adopted widely as a host-based IDS. LIDS http://www.lids.org/ - The Linux Intrusion Detection System (LIDS) is a kernel patch and administration tool that can also control file modification with access control lists (ACLs), and protect processes and files, even from the root user.

Commands:
5.8.3. Sorting LVM Reports Normally the entire output of the lvs , vgs , or pvs command has to be generated and stored internally before it can be sorted and columns aligned correctly. You can specify the --unbuffered argument to display unsorted output as soon as it is generated. To specify an alternative ordered list of columns to sort on, use the -O argument of any of the reporting commands. It is not necessary to include these fields within the output itself. The following example shows the output of the pvs command that displays the physical volume name, size, and free space. The following example shows the same output, sorted by the free space field. The following example shows that you do not need to display the field on which you are sorting. To display a reverse sort, precede a field you specify after the -O argument with the - character.

Commands:
pvs -o pv_name,pv_size,pv_free PV PSize PFree /dev/sdb1 17.14G 17.14G /dev/sdc1 17.14G 17.09G /dev/sdd1 17.14G 17.14G
pvs -o pv_name,pv_size,pv_free -O pv_free PV PSize PFree /dev/sdc1 17.14G 17.09G /dev/sdd1 17.14G 17.14G /dev/sdb1 17.14G 17.14G
pvs -o pv_name,pv_size -O pv_free PV PSize /dev/sdc1 17.14G /dev/sdd1 17.14G /dev/sdb1 17.14G
pvs -o pv_name,pv_size,pv_free -O -pv_free PV PSize PFree /dev/sdd1 17.14G 17.14G /dev/sdb1 17.14G 17.14G /dev/sdc1 17.14G 17.09G