mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 31. Using LLDP to debug network configuration problems You can use the Link Layer Discovery Protocol (LLDP) to debug network configuration problems in the topology. This means that, LLDP can report configuration inconsistencies with other hosts or routers and switches. 31.1. Debugging an incorrect VLAN configuration using LLDP information If you configured a switch port to use a certain VLAN and a host does not receive these VLAN packets, you can use the Link Layer Discovery Protocol (LLDP) to debug the problem. Perform this procedure on the host that does not receive the packets. Prerequisites The nmstate package is installed. The switch supports LLDP. LLDP is enabled on neighbor devices. Procedure Create the ~/enable-LLDP-enp1s0.yml file with the following content: interfaces: - name: enp1s0 type: ethernet lldp: enabled: true Use the ~/enable-LLDP-enp1s0.yml file to enable LLDP on interface enp1s0 : Display the LLDP information: Verify the output to ensure that the settings match your expected configuration. For example, the LLDP information of the interface connected to the switch shows that the switch port this host is connected to uses VLAN ID 448 : - type: 127 ieee-802-1-vlans: - name: v2-0488-03-0505 vid: 488 If the network configuration of the enp1s0 interface uses a different VLAN ID, change it accordingly. Additional resources Configuring VLAN tagging

Commands:
interfaces: - name: enp1s0 type: ethernet lldp: enabled: true
nmstatectl apply ~/enable-LLDP-enp1s0.yml
nmstatectl show enp1s0 - name: enp1s0 type: ethernet state: up ipv4: enabled: false dhcp: false ipv6: enabled: false autoconf: false dhcp: false lldp: enabled: true neighbors: - - type: 5 system-name: Summit300-48 - type: 6 system-description: Summit300-48 - Version 7.4e.1 (Build 5) 05/27/05 04:53:11 - type: 7 system-capabilities: - MAC Bridge component - Router - type: 1 _description: MAC address chassis-id: 00:01:30:F9:AD:A0 chassis-id-type: 4 - type: 2 _description: Interface name port-id: 1/1 port-id-type: 5 - type: 127 ieee-802-1-vlans: - name: v2-0488-03-0505 vid: 488 oui: 00:80:c2 subtype: 3 - type: 127 ieee-802-3-mac-phy-conf: autoneg: true operational-mau-type: 16 pmd-autoneg-cap: 27648 oui: 00:12:0f subtype: 1 - type: 127 ieee-802-1-ppvids: - 0 oui: 00:80:c2 subtype: 2 - type: 8 management-addresses: - address: 00:01:30:F9:AD:A0 address-subtype: MAC interface-number: 1001 interface-number-subtype: 2 - type: 127 ieee-802-3-max-frame-size: 1522 oui: 00:12:0f subtype: 4 mac-address: 82:75:BE:6F:8C:7A mtu: 1500
- type: 127 ieee-802-1-vlans: - name: v2-0488-03-0505 vid: 488
Chapter 274. Reactor Component Available as of Camel version 2.20 Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-reactor</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-reactor</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
3.8. Configuring atime Updates Each file inode and directory inode has three time stamps associated with it: ctime - The last time the inode status was changed mtime - The last time the file (or directory) data was modified atime - The last time the file (or directory) data was accessed If atime updates are enabled as they are by default on GFS2 and other Linux file systems then every time a file is read, its inode needs to be updated. Because few applications use the information provided by atime , those updates can require a significant amount of unnecessary write traffic and file locking traffic. That traffic can degrade performance; therefore, it may be preferable to turn off or reduce the frequency of atime updates. Two methods of reducing the effects of atime updating are available: Mount with relatime (relative atime), which updates the atime if the atime update is older than the mtime or ctime update. Mount with noatime , which disables atime updates on that file system. 3.8.1. Mount with relatime The relatime (relative atime) Linux mount option can be specified when the file system is mounted. This specifies that the atime is updated if the atime update is older than the mtime or ctime update. Usage BlockDevice Specifies the block device where the GFS2 file system resides. MountPoint Specifies the directory where the GFS2 file system should be mounted. Example In this example, the GFS2 file system resides on /dev/vg01/lvol0 and is mounted on directory /mygfs2 . The atime updates take place only if the atime update is older than the mtime or ctime update. 3.8.2. Mount with noatime The noatime Linux mount option can be specified when the file system is mounted, which disables atime updates on that file system. Usage BlockDevice Specifies the block device where the GFS2 file system resides. MountPoint Specifies the directory where the GFS2 file system should be mounted. Example In this example, the GFS2 file system resides on /dev/vg01/lvol0 and is mounted on directory /mygfs2 with atime updates turned off.

Commands:
mount BlockDevice MountPoint -o relatime
mount /dev/vg01/lvol0 /mygfs2 -o relatime
mount BlockDevice MountPoint -o noatime
mount /dev/vg01/lvol0 /mygfs2 -o noatime
8.6. Detecting Tokens To see if a token can be detected by Certificate System, use the TokenInfo utility, pointing to the alias directory for the subsystem instance. This is a Certificate System tool which is available after the Certificate System packages are installed. For example: This utility returns all tokens which can be detected by the Certificate System, not only tokens which are installed in the Certificate System.

Commands:
TokenInfo /var/lib/pki/pki-tomcat/alias
Chapter 5. Backing up the Original Manager Back up the original Manager using the engine-backup command, and copy the backup file to a separate location so that it can be accessed at any point during the process. For more information about engine-backup --mode=backup options, see Backing Up and Restoring the Red Hat Virtualization Manager in the Administration Guide . Procedure Log in to the original Manager and stop the ovirt-engine service: Note Though stopping the original Manager from running is not obligatory, it is recommended as it ensures no changes are made to the environment after the backup is created. Additionally, it prevents the original Manager and the new Manager from simultaneously managing existing resources. Run the engine-backup command, specifying the name of the backup file to create, and the name of the log file to create to store the backup log: # engine-backup --mode=backup --file= file_name --log= log_file_name Copy the files to an external server. In the following example, storage.example.com is the fully qualified domain name of a network storage server that will store the backup until it is needed, and /backup/ is any designated folder or path. # scp -p file_name log_file_name storage.example.com:/backup/ If you do not require the Manager machine for other purposes, unregister it from Red Hat Subscription Manager: # subscription-manager unregister After backing up the Manager, deploy a new self-hosted engine and restore the backup on the new virtual machine.

Commands:
systemctl stop ovirt-engine systemctl disable ovirt-engine
engine-backup --mode=backup --file= file_name --log= log_file_name
scp -p file_name log_file_name storage.example.com:/backup/
subscription-manager unregister
Chapter 3. Prerequisites for Configuring Capsule Servers for Load Balancing To configure Capsule Servers for load balancing, complete the following procedures described in Installing Capsule Server . Satellite does not support configuring existing Capsule Servers for load balancing. Registering Capsule Server to Satellite Server Attaching the Satellite Infrastructure Subscription Configuring Repositories Synchronizing the System Clock With chronyd Installing Capsule Server Packages

Commands:
Chapter 2. Tooling Guide extension pack Important The VS Code extensions for Apache Camel are listed as development support. For more information about scope of development support, see Development Support Scope of Coverage for Red Hat Build of Apache Camel . 2.1. Installing extension pack for Apache Camel by Red Hat This section explains how to install Extension Pack for Apache Camel by Red Hat. Procedure Open the VS Code editor. In the VS Code editor, select View > Extensions . In the search bar, type Camel . Select the Extension Pack for Apache Camel by Red Hat option from the search results and then click Install. This installs the extension pack which includes extensions for Apache Camel in the VS Code editor.

Commands:
Chapter 12. Creating a kernel-based virtual machine and booting the installation ISO in the VM You can create a kernel-based virtual machine (KVM) and start the Red Hat Enterprise Linux installation. The following instructions are specific for installation on a VM. If you are installing RHEL on a physical system, you can skip this section. Procedure Create a virtual machine with the instance of Red Hat Enterprise Linux as a KVM guest operating system, by using the following virt-install command on the KVM host: Additional resources virt-install man page on your system Creating virtual machines by using the command line

Commands:
virt-install --name=<guest_name> --disk size=<disksize_in_GB> --memory=<memory_size_in_MB> --cdrom <filepath_to_iso> --graphics vnc
7.147. openssl 7.147.1. RHBA-2015:1398 - openssl bug fix and enhancement update Updated openssl packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library. Bug Fixes BZ# 1119191 Previously, the ciphers(1) manual page did not describe the following Elliptic Curve Cryptography (ECC) cipher suite groups: Elliptic Curve Diffie-Hellman (ECDH) and Elliptic Curve Digital Signature Algorithm (ECDSA), or TLS version 1.2 (TLSv1.2) specific features. This update adds the missing description of the ECDH and ECDSA cipher groups and TLSv1.2 features to ciphers(1), and the documentation is now complete. BZ# 1234487 The server-side renegotiation support did previously not work as expected under certain circumstances. A PostgreSQL failure of database dumps through TLS connection could occur when the size of the dumped data was larger than the value defined in the ssl_renegotiation_limit setting. The regression that caused this bug has been fixed, and the PostgreSQL database dumps through TLS connection no longer fail in the described situation. Enhancement BZ# 961965 This update adds the "-keytab" option to the "openssl s_server" command and the "-krb5svc" option to the "openssl s_server" and "openssl s_client" commands. The "-keytab" option allows the user to specify a custom keytab location; if the user does not add "-keytab", the openssl utility assumes the default keytab location. The "-krb5svc" option enables selecting a service other than the "host" service; this allows unprivileged users without keys to the host principal to use "openssl s_server" and "open s_client" with Kerberos. Users of openssl are advised to upgrade to these updated packages, which fix these bugs and add this enhancement. For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

Commands:
Chapter 2. Forking the RHTAP catalog repository Once developers start using your instance of RHTAP, you might want to customize your instance, to better suit their needs. One aspect of RHTAP that you can customize is the set of software templates that it provides. These templates help developers quickly build applications. Forking our catalog repository, which contains the default set of software templates, enables you to customize the templates for your instance. Prerequisites: A GitHub account Procedure: In your web browser, navigate to the RHTAP software catalog repository . Beneath the banner of the page, select Fork and fork the repository. Uncheck the box that says "Copy the main branch only". In your new fork, beneath the banner, click main to open a dropdown menu. Under Tags , select the release that corresponds to the version of RHTAP that you are using. For example, if you are using version 1.0.0 of RHTAP, you should use your forked instance of this release . Note Be sure to update your fork from time to time, so updates from the upstream repository can benefit your instance of RHTAP.

Commands:
11. Development and Tools 11.1. Technology Previews libdfp An updated libdfp library is available in Red Hat Enterprise Linux 6. libdfp is a decimal floating point math library, and is available as an alternative to the glibc math functions on Power and s390x architectures, and is available in the supplementary channels. Eclipse Plugins The following plugins for the Eclipse software development environment are considered to be Technology Previews in this pre-release version of Red Hat Enterprise Linux 6 The Mylyn plugin for the Eclipse task management subsystem the eclipse-callgraph C/C++ Call Graph Visualization plugin

Commands:
B.105. xorg-x11-drv-qxl B.105.1. RHBA-2010:0917 - xorg-x11-drv-qxl bug fix update An updated xorg-x11-drv-qxl package that fixes various bugs is now available. xorg-x11-qxl-drv is an X11 video driver for the QEMU QXL video accelerator. This driver makes it possible to use Red Hat Enterprise Linux 6 as a guest operating system under KVM and QEMU, using the SPICE protocol. This updated xorg-x11-drv-qxl package includes fixes for the following bugs: BZ# 648933 When using the xql driver, only a limited number of resolution choices were available for use inside the guest, none of which exceeded 1024x768 in size unless the xorg.conf configuration file was (first created, and then) manually edited. This update ensures that larger resolutions are available for guests with appropriate hardware without needing to manually change xorg.conf. BZ# 648935 When using the qxl driver, after connecting to a virtual guest over the SPICE protocol and logging into a desktop session from the GDM display manager, attempting to switch to a virtual console using a key combination caused the X server to crash, and GDM to respawn. This update fixes this issue so that, in the aforementioned situation, switching to a virtual console and back to the graphical desktop works as expected. All users of KVM-based virtualization are advised to upgrade to this updated package, which fixes these issues.

Commands:
33.5. Network Configuration Figure 33.8. Network Configuration If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the Network Configuration page. Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the Network Administration Tool ( system-config-network ). Refer to the Red Hat Enterprise Linux Deployment Guide for details. For each Ethernet card on the system, click Add Network Device and select the network device and network type for the device. Select eth0 to configure the first Ethernet card, eth1 for the second Ethernet card, and so on.

Commands:
3.2. Is Your Hardware Compatible? Hardware compatibility is particularly important if you have an older system or a system that you built yourself. Red Hat Enterprise Linux 6.9 should be compatible with most hardware in systems that were factory built within the last two years. However, hardware specifications change almost daily, so it is difficult to guarantee that your hardware is 100% compatible. One consistent requirement is your processor. Red Hat Enterprise Linux 6.9 supports, at minimum, all 32-bit and 64-bit implementations of Intel microarchitecture from P6 and onwards and AMD microarchitecture from Athlon and onwards. The most recent list of supported hardware can be found at:

Commands:
https://hardware.redhat.com/
E.9. Changing Runlevels at Boot Time Under Red Hat Enterprise Linux, it is possible to change the default runlevel at boot time. To change the runlevel of a single boot session, use the following instructions: When the GRUB menu bypass screen appears at boot time, press any key to enter the GRUB menu (within the first three seconds). Press the a key to append to the kernel command. Add <space> <runlevel> at the end of the boot options line to boot to the desired runlevel. For example, the following entry would initiate a boot process into runlevel 3:

Commands:
grub append> ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
Chapter 6. Creating Ansible playbooks with the all-in-one Red Hat OpenStack Platform environment The deployment command applies Ansible playbooks to the environment automatically. However, you can modify the deployment command to generate Ansible playbooks without applying them to the deployment, and run the playbooks later. Include the --output-only option in the deploy command to generate the undercloud-ansible-XXXXX directory. This directory contains a set of Ansible playbooks that you can run on other hosts. To generate the Ansible playbook directory, run the deploy command with the option --output-only : To run the Ansible playbooks, run the ansible-playbook command, and include the inventory.yaml file and the deploy_steps_playbook.yaml file:

Commands:
[stack@all-in-one]USD sudo openstack tripleo deploy --templates --local-ip=USDIP/USDNETMASK -e /usr/share/openstack-tripleo-heat-templates/environments/standalone/standalone-tripleo.yaml -r /usr/share/openstack-tripleo-heat-templates/roles/Standalone.yaml -e USDHOME/containers-prepare-parameters.yaml -e USDHOME/standalone_parameters.yaml --output-dir USDHOME --standalone --output-only
[stack@all-in-one]USD cd undercloud-ansible-XXXXX [stack@all-in-one]USD sudo ansible-playbook -i inventory.yaml deploy_steps_playbook.yaml
5.161. libusb1 5.161.1. RHBA-2012:0759 - libusb1 bug fix and enhancement update Updated libusb1 package that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libusb1 packages provide a way for applications to access USB devices. The libusb1 packages have been upgraded to upstream version 1.0.9, which provides a number of bug fixes and enhancements over the version. In addition, this update adds a new API needed for support of the SPICE (The Simple Protocol for Independent Computing Environments) USB redirection. (BZ# 758094 ) All users of libusb1 are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 14. Adding allowed registries to the automation controller image configuration Before you can deploy a container image in automation hub, you must add the registry to the allowedRegistries in the automation controller image configuration. To do this you can copy and paste the following code into your automation controller image YAML. Procedure Log in to Red Hat OpenShift Container Platform . Navigate to Home Search . Select the Resources drop-down list and type "Image". Select Image (config,openshift.io/v1) . Click Cluster under the Name heading. Select the YAML tab. Paste in the following under spec value: spec: registrySources: allowedRegistries: - quay.io - registry.redhat.io - image-registry.openshift-image-registry.svc:5000 - <OCP route for your automation hub> Click Save .

Commands:
spec: registrySources: allowedRegistries: - quay.io - registry.redhat.io - image-registry.openshift-image-registry.svc:5000 - <OCP route for your automation hub>
7.26. control-center 7.26.1. RHBA-2013:0335 - control-center bug fix update Updated control-center packages that fix one bug are now available for Red Hat Enterprise Linux 6. The control-center packages provide various configuration utilities for the GNOME desktop. These utilities allow the user to configure accessibility options, desktop fonts, keyboard and mouse properties, sound setup, desktop theme and background, user interface properties, screen resolution, and other settings. Bug Fix BZ#805069 Prior to this update, the status LEDs on Wacom tablets did not correctly indicate the current mode. With this update, the LEDs now indicate which of the Touch Ring or Touch Strip modes are active. All users of control-center are advised to upgrade to these updated packages, which fix this bug.

Commands:
Part I. Migration Planning Migration Planning focuses on the shift of the default Red Hat Enterprise Linux desktop environment from GNOME 2, shipped with Red Hat Enterprise Linux 5 and 6, to GNOME 3. One by one, this part of the guide briefly mentions the changes certain components have gone through and describes the new features the components possess. This guide only refers to changes to the GNOME Desktop environment. For changes to the other parts of Red Hat Enterprise Linux 7 refer to: Red Hat Enterprise Linux 7 System Administrator's Guide , for components such as the GRUB 2 boot loader, package management, systemd , or printer configuration. Red Hat Enterprise Linux 7 Migration Planning Guide for an overview of major changes in behavior and compatibility between Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. The Migration Planning Guide also introduces the tools provided by Red Hat to assist with upgrades to Red Hat Enterprise Linux 7. Red Hat Enterprise Linux 7 Installation Guide for detailed information about installing Red Hat Enterprise Linux 7 and using the Anaconda installer. These documents can be found at http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/ .

Commands:
8.225. squid 8.225.1. RHBA-2014:1446 - squid bug fix update Updated squid packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Squid is a high-performance proxy caching server for web clients, supporting FTP, Gopher, and HTTP data objects. Bug Fixes BZ# 876980 Prior to this update, the /etc/init.d/squid initialization script did not describe the condrestart option, and therefore it did not appear in the Usage message. This bug has been fixed, and condrestart is now displayed correctly in the Usage message. BZ# 998809 Under certain circumstances, the comm_write() function of the squid utility attempted to write to file descriptors that were being closed. Consequently, the squid utility was aborted. With this update, a patch that handles the write attempt has been introduced. As a result, squid is no longer aborted in the aforementioned scenario. BZ# 1011952 Due to a bug in the default /etc/httpd/conf.d/squid.conf configuration file, the squid utility was not allowed to access the CacheManager tool at http://localhost/Squid/cgi-bin/cachemgr.cgi. The bug has been fixed, and squid can now access CacheManager without complications. BZ# 1034616 Under certain circumstances, the squid utility leaked Domain Name System (DNS) queries. Consequently, squid often reached the limit of maximum locks set to 65,535 and terminated unexpectedly. With this update, several changes have been made to prevent leaked queries. Also, the lock limit has been increased to the maximum value of the integer data type. BZ# 1047839 Previously, after receiving a malformed Domain Name System (DNS) response, the squid utility terminated unexpectedly and did not start again. The underlying source code has been modified, and as a result, squid now handles malformed DNS responses without complications. BZ# 1058207 Under certain circumstances, child processes of the squid utility terminated unexpectedly and generated a core file. This bug has been fixed, and squid processes no longer exit abnormally. BZ# 1066368 , BZ# 1089614 Previously, the AuthBasicUserRequest method of the squid utility overrode the default user() methods with its own data. Consequently, a memory leak occurred when using basic authentication, which led to high memory consumption of squid. With this update, the aforementioned override was removed and the memory leak no longer occurs. Users of squid are advised to upgrade to these updated packages, which fix these bugs. After installing this update, the squid service will be restarted automatically.

Commands: