mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 9. Monitoring Dashboard Navigation To access the Monitoring Dashboard, follow these steps: Log in to the Web Administration interface at http://web-admin-server.example.com . In the default Cluster view, locate the cluster and click Launch Dashboard . The Cluster dashboard showing the aggregated metrics view is opened in a new window. 9.1. Cluster View Dashboard The Cluster view dashboard allows the Gluster Administrator to: View at-a-glance information about the Gluster cluster that includes health and status information, key performance indicators such as IOPS, throughput, etc, and alerts that can highlight attention to potential issues in the cluster, host, volume, and brick. Compare a metric such as IOPS, CPU, Memory, Network Load across hosts within the cluster. Compare utilization across bricks within a volume, for example, IOPS, capacity, etc. Figure 9.1. Cluster View Dashboard 9.2. Hosts View Dashboard The Host view Dashboard allows the Gluster Administrator to: View at-a-glance information about the Gluster host that includes health and status information, key performance indicators such as IOPS, throughput, etc and alerts that highlights attention to potential issues in the host, volume, brick, and disk. Compare one or more metrics such as IOPS, CPU, Memory, Network Load across bricks within the host. Compare utilization such as IOPS, capacity, etc across bricks within a host. 9.3. Volume View Dashboard The Volume view Dashboard allows the Gluster Administrator to: View at-a-glance information about the Gluster Volume that includes health and status information, key performance indicators that highlights attention to potential issues in the volume, brick, and disk. 9.4. Brick View Dashboard The Brick view dashboard allows the Gluster Administrator to: View at-a-glance information about the Gluster brick that includes health and status information, key performance indicators such as IOPS, throughput, latency, etc and alerts that can highlight attention to potential issues in the brick and underlying disks. Look at performance by brick to address diagnosing of RAID 6 disk failure/rebuild/degradation poor performance on one brick.

Commands:
Chapter 5. Enabling notifications and integrations You can enable the notifications service on Red Hat Hybrid Cloud Console to send notifications whenever a vulnerability event is triggered. For example, you can configure the notifications service to automatically send an email message whenever a security issue affects systems in your installation, or to send an email digest of all the vulnerability events that take place each day. Using the notifications service frees you from having to continually check the Red Hat Insights for RHEL dashboard for event-triggered notifications. In addition to sending email messages, you can configure the notifications service to send event data in other ways: Using an authenticated client to query Red Hat Insights APIs for event data Using webhooks to send events to third-party applications that accept inbound requests Integrating notifications with applications such as Splunk to route event notifications to the application dashboard A Notifications Administrator sets up behavior groups for events in the notifications service. Behavior groups specify the delivery method for each notification and whether the notifications are sent to all users, or just to Organization Administrators. An Organization Administrator creates a User access group with the Notifications Administrator role, and then adds account members to the group. Users who receive email notifications from events may set their user preferences so that they receive individual emails for each event, or a daily digest of events. Additional resources For more information about how to set up notifications and integrations for Vulnerability events, see Configuring notifications on the Red Hat Hybrid Cloud Console and Integrating the Red Hat Hybrid Cloud Console with third-party applications .

Commands:
7.9. Additional Resources Printing configuration and network printing are broad topics requiring knowledge and experience in hardware, networking, and system administration. For more detailed information about deploying printer services in your environments, refer to the following resources. 7.9.1. Installed Documentation lpr(1) man page -- Learn how to print selected files on the printer of your choice. lprm(1) man page -- Learn how to remove print jobs from a printer queue. cupsd(8) man page -- Learn about the CUPS printer daemon. cupsd.conf(5) man page -- Learn about the file format for the CUPS printer daemon configuration file. classes.conf(5) man page -- Learn about the file format for the CUPS class configuration file. Files in /usr/share/doc/cups-<version> -- Learn more about the CUPS printing system.

Commands:
Chapter 5. Editing Virtual Machines 5.1. Editing Virtual Machine Properties Changes to storage, operating system, or networking parameters can adversely affect the virtual machine. Ensure that you have the correct details before attempting to make any changes. Virtual machines can be edited while running, and some changes (listed in the procedure below) will be applied immediately. To apply all other changes, the virtual machine must be shut down and restarted. Note External virtual machines (marked with the prefix external ) cannot be edited through the Red Hat Virtualization Manager. Editing Virtual Machines Click Compute Virtual Machines . Select the virtual machine to be edited. Click Edit . Change settings as required. Changes to the following settings are applied immediately: Name Description Comment Optimized for (Desktop/Server/High Performance) Delete Protection Network Interfaces Memory Size (Edit this field to hot plug virtual memory. See Section 5.4.1, "Hot Plugging Virtual Memory" .) Virtual Sockets (Edit this field to hot plug CPUs. See Section 5.5, "Hot Plugging vCPUs" .) Use custom migration downtime Highly Available Priority for Run/Migration queue Disable strict user checking Icon Click OK . If the Start Configuration pop-up window appears, click OK . Some changes are applied immediately. All other changes are applied when you shut down and restart your virtual machine. Until then, the pending changes icon ( ) appears as a reminder to restart the virtual machine.

Commands:
8.3. Installation Method If you booted the installation from minimal boot media or with the askmethod boot option, use the arrow keys on your keyboard to select an installation method (refer to Figure 8.4, "Installation Method" ). With your selected method highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. Figure 8.4. Installation Method 8.3.1. Installing from a DVD To install Red Hat Enterprise Linux from a DVD, place the DVD your DVD drive and boot your system from the DVD. Even if you booted from alternative media, you can still install Red Hat Enterprise Linux from DVD media. The installation program then probes your system and attempts to identify your DVD drive. It starts by looking for an IDE (also known as an ATAPI) DVD drive. Note To abort the installation process at this time, reboot your machine and then eject the boot media. You can safely cancel the installation at any point before the Write changes to disk screen. Refer to Section 9.16, "Write Changes to Disk" for more information. If your DVD drive is not detected, and it is a SCSI DVD, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter. You may specify options for the driver if necessary; however, most drivers detect your SCSI adapter automatically. If the DVD drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD. This will take some time, and you may opt to skip over this step. However, if you later encounter problems with the installer, you should reboot and perform the media check before calling for support. From the media check dialog, continue to the stage of the installation process (refer to Section 9.3, "Welcome to Red Hat Enterprise Linux" ).

Commands:
4.6.3. Deleting a Fence Device Note Fence devices that are in use cannot be deleted. To delete a fence device that a node is currently using, first update the node fence configuration for any node using the device and then delete the device. To delete a fence device, follow these steps: From the Fence Devices configuration page, check the box to the left of the fence device or devices to select the devices to delete. Click Delete and wait for the configuration to be updated. A message appears indicating which devices are being deleted. When the configuration has been updated, the deleted fence device no longer appears in the display.

Commands:
Chapter 15. Identity: Integrating with Microsoft Active Directory Through Synchronization Identity Management uses active synchronization to integrate user data stored in an Active Directory domain and the user data stored in the IdM domain. Critical user attributes, including passwords, are synchronized between the services. The capability to sync Active Directory and IdM domains is inherent when an IdM server is first installed. The synchronization process is configured by creating agreements between the IdM server and the Active Directory domain controller. This chapter describes how to configure synchronization, how to configure Active Directory for integration with IdM, and how to configure Windows systems within the Active Directory domain to be aware of the IdM domain. 15.1. Supported Windows Platforms Entry synchronization is performed through a process similar to replication, which uses hooks to connect to and retrieve directory data from the Windows server. Password synchronization is performed through a Windows service which is installed on the Windows server and then communicates to the Identity Management server. Both entry and password synchronization are supported with these Windows servers: Windows Server 2008 R2 Windows Server 2012 R2 The version of the password sync service which works with Windows is 1.1.5. This is available in the Red Hat Directory Server downloads part of Red Hat Network.

Commands:
22.16.13. Configuring the Poll Interval To change the default poll interval, add the following options to the end of a server or peer command: minpoll value and maxpoll value Options to change the default poll interval, where the interval in seconds will be calculated by raising 2 to the power of value , in other words, the interval is expressed in log 2 seconds. The default minpoll value is 6, 2 6 equates to 64s. The default value for maxpoll is 10, which equates to 1024s. Allowed values are in the range 3 to 17 inclusive, which equates to 8s to 36.4h respectively. These options are for use with the peer or server . Setting a shorter maxpoll may improve clock accuracy.

Commands:
5.2.3. Creating the Logical Volume The following command creates the striped logical volume striped_logical_volume from the volume group striped_vol_group . This example creates a logical volume that is 2 gigabytes in size, with three stripes and a stripe size of 4 kilobytes.

Commands:
lvcreate -i3 -I4 -L2G -nstriped_logical_volume striped_vol_group Rounding size (512 extents) up to stripe boundary size (513 extents) Logical volume "striped_logical_volume" created
5.7. The file_t and default_t Types When using a file system that supports extended attributes (EA), the file_t type is the default type for files that have not been assigned an EA value. This type is only used for this purpose and does not exist on correctly labeled file systems, because all files on a system running SELinux should have a proper SELinux context, and the file_t type is never used in file-context configuration [8] . The default_t type is used on files that do not match any pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally are kept inaccessible to confined domains. For example, if you create a new top-level directory, such as /mydirectory/ , this directory may be labeled with the default_t type. If services need access to this directory, you need to update the file-context configuration for this location. See Section 5.6.2, "Persistent Changes: semanage fcontext" for details on adding a context to the file-context configuration. [8] Files in the /etc/selinux/targeted/contexts/files/ directory define contexts for files and directories. Files in this directory are read by the restorecon and setfiles utilities to restore files and directories to their default contexts.

Commands:
4.4. Authentication Simultaneous maintaining of TGTs for multiple KDCs Kerberos version 1.10 added a new cache storage type, DIR:, which allows Kerberos to maintain Ticket Granting Tickets (TGTs) for multiple Key Distribution Centers (KDCs) simultaneously and auto-select between them when negotiating with Kerberized resources. In Red Hat Enterprise Linux 6.4, SSSD has been enhanced to allow you to select the DIR: cache for users that are logging in via SSSD. This feature is introduced as a Technology Preview. Package: sssd-1.9.2-82

Commands:
B.78.3. RHBA-2010:0855 - qemu-kvm bug fix update Updated qemu-kvm packages that fix various bugs are now available for Red Hat Enterprise Linux 6. KVM (Kernel-based Virtual Machine) is a full virtualization solution for Linux on AMD64 and Intel 64 systems. qemu-kvm is the user-space component for running virtual machines using KVM. Bug Fixes BZ# 633963 Prior to this update, virtio-net used a packet transmission algorithm that was using a timer to delay a transmission in an attempt to batch multiple packets together. However, this typically resulted in a higher latency. With this update, the default algorithm has been changed to use an asynchronous bottom half transmitter, improving the performance. BZ# 634249 Due to error in the committed_memory() function, the ksmtuned service was unable to determine the correct amount of memory used by qemu-kvm processes when no such process existed. This has been fixed, the relevant part of the source code has been corrected to return 0 when no qemu-kvm process is found, and ksmtuned now works as expected. BZ# 641835 Previously, attempting to commit a copy-on-write image to a raw backing disk image using the "quemu-img commit" command may have failed with the following error: With this update, this error no longer occurs, and such images can now be committed as expected. All users are advised to upgrade to these updated packages, which fix these bugs.

Commands:
qemu-img: Error while committing image
4.4. Cisco MDS Table 4.5, "Cisco MDS" lists the fence device parameters used by fence_cisco_mds , the fence agent for Cisco MDS. Table 4.5. Cisco MDS luci Field cluster.conf Attribute Description Name name A name for the Cisco MDS 9000 series device with SNMP enabled. IP Address or Hostname ipaddr The IP address or host name assigned to the device. UDP/TCP port (optional) udpport The UDP/TCP port to use for connection with the device; the default value is 161. 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. SNMP Version snmp_version The SNMP version to use (1, 2c, 3). SNMP Community community The SNMP community string. SNMP Security Level snmp_sec_level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv). SNMP Authentication Protocol snmp_auth_prot The SNMP authentication protocol (MD5, SHA). SNMP Privacy Protocol snmp_priv_prot The SNMP privacy protocol (DES, AES). SNMP Privacy Protocol Password snmp_priv_passwd The SNMP privacy protocol password. SNMP Privacy Protocol Script snmp_priv_passwd_script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter. 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 (Outlet) Number port The port. Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0. Figure 4.4, "Cisco MDS" shows the configuration screen for adding an Cisco MDS fence device. Figure 4.4. Cisco MDS The following command creates a fence device instance for a Cisco MDS device: The following is the cluster.conf entry for the fence_cisco_mds device:

Commands:
ccs -f cluster.conf --addfencedev mds agent=fence_cisco_mds ipaddr=192.168.0.1 name=ciscomdstest1 login=root passwd=password123 power_wait=60 snmp_priv_passwd=password123 udpport=161
<fencedevices> <fencedevice agent="fence_cisco_mds" community="private" ipaddr="192.168.0.1" login="root" name="ciscomdstest1" passwd="password123" power_wait="60" snmp_priv_passwd="password123" udpport="161"/> </fencedevices>
Appendix B. The LVM Configuration Files LVM supports multiple configuration files. At system startup, the lvm.conf configuration file is loaded from the directory specified by the environment variable LVM_SYSTEM_DIR , which is set to /etc/lvm by default. The lvm.conf file can specify additional configuration files to load. Settings in later files override settings from earlier ones. To display the settings in use after loading all the configuration files, execute the lvm dumpconfig command. For information on loading additional configuration files, see Section C.2, "Host Tags" . B.1. The LVM Configuration Files The following files are used for LVM configuration: /etc/lvm/lvm.conf Central configuration file read by the tools. etc/lvm/lvm_ hosttag .conf For each host tag, an extra configuration file is read if it exists: lvm_ hosttag .conf . If that file defines new tags, then further configuration files will be appended to the list of tiles to read in. For information on host tags, see Section C.2, "Host Tags" . In addition to the LVM configuration files, a system running LVM includes the following files that affect LVM system setup: /etc/lvm/.cache Device name filter cache file (configurable). /etc/lvm/backup/ Directory for automatic volume group metadata backups (configurable). /etc/lvm/archive/ Directory for automatic volume group metadata archives (configurable with regard to directory path and archive history depth). /var/lock/lvm/ In single-host configuration, lock files to prevent parallel tool runs from corrupting the metadata; in a cluster, cluster-wide DLM is used.

Commands:
Chapter 12. Tuning the performance of a Samba server Learn what settings can improve the performance of Samba in certain situations, and which settings can have a negative performance impact. Parts of this section were adopted from the Performance Tuning documentation published in the Samba Wiki. License: CC BY 4.0 . Authors and contributors: See the history tab on the Wiki page. Prerequisites Samba is set up as a file or print server 12.1. Setting the SMB protocol version Each new SMB version adds features and improves the performance of the protocol. The recent Windows and Windows Server operating systems always supports the latest protocol version. If Samba also uses the latest protocol version, Windows clients connecting to Samba benefit from the performance improvements. In Samba, the default value of the server max protocol is set to the latest supported stable SMB protocol version. Note To always have the latest stable SMB protocol version enabled, do not set the server max protocol parameter. If you set the parameter manually, you will need to modify the setting with each new version of the SMB protocol, to have the latest protocol version enabled. The following procedure explains how to use the default value in the server max protocol parameter. Procedure Remove the server max protocol parameter from the [global] section in the /etc/samba/smb.conf file. Reload the Samba configuration 12.2. Tuning shares with directories that contain a large number of files Linux supports case-sensitive file names. For this reason, Samba needs to scan directories for uppercase and lowercase file names when searching or accessing a file. You can configure a share to create new files only in lowercase or uppercase, which improves the performance. Prerequisites Samba is configured as a file server Procedure Rename all files on the share to lowercase. Note Using the settings in this procedure, files with names other than in lowercase will no longer be displayed. Set the following parameters in the share's section: For details about the parameters, see their descriptions in the smb.conf(5) man page on your system. Verify the /etc/samba/smb.conf file: Reload the Samba configuration: After you applied these settings, the names of all newly created files on this share use lowercase. Because of these settings, Samba no longer needs to scan the directory for uppercase and lowercase, which improves the performance. 12.3. Settings that can have a negative performance impact By default, the kernel in Red Hat Enterprise Linux is tuned for high network performance. For example, the kernel uses an auto-tuning mechanism for buffer sizes. Setting the socket options parameter in the /etc/samba/smb.conf file overrides these kernel settings. As a result, setting this parameter decreases the Samba network performance in most cases. To use the optimized settings from the Kernel, remove the socket options parameter from the [global] section in the /etc/samba/smb.conf .

Commands:
smbcontrol all reload-config
case sensitive = true default case = lower preserve case = no short preserve case = no
testparm
smbcontrol all reload-config
2.8. Display Configuration If you are installing the X Window System, you can configure it during the kickstart installation by checking the Configure the X Window System option on the Display Configuration window as shown in Figure 2.11, "X Configuration - General" . If this option is not chosen, the X configuration options are disabled and the skipx option is written to the kickstart file. 2.8.1. General The first step in configuring X is to choose the default color depth and resolution. Select them from their respective pulldown menus. Be sure to specify a color depth and resolution that is compatible with the video card and monitor for the system. Figure 2.11. X Configuration - General If you are installing both the GNOME and KDE desktops, you must choose which desktop should be the default. If only one desktop is to be installed, be sure to choose it. Once the system is installed, users can choose which desktop they want to be their default. , choose whether to start the X Window System when the system is booted. This option starts the system in runlevel 5 with the graphical login screen. After the system is installed, this can be changed by modifying the /etc/inittab configuration file. Also select whether to start the Setup Agent the first time the system is rebooted. It is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.

Commands: