Red Hat NETWORK 4.0.5 Reference Manual

Hide thumbs Also See for NETWORK 4.0.5:
Table of Contents

Advertisement

Red Hat Network 4.0.5
Reference Guide

Advertisement

Table of Contents

Troubleshooting

loading

Summary of Contents for Red Hat NETWORK 4.0.5

  • Page 1 Red Hat Network 4.0.5 Reference Guide...
  • Page 2 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
  • Page 3: Table Of Contents

    Table of Contents Introduction to the Guide....................i 1. Document Conventions ..................i 2. More to Come ......................v 2.1. Send in Your Feedback .................v 1. Red Hat Network Overview ..................1 1.1. Update ....................... 2 1.2. Management......................3 1.3. Provisioning ......................3 1.4. Monitoring ......................4 1.5.
  • Page 4 5. Red Hat Network Registration Client ................49 5.1. Configuring the Red Hat Network Registration Client.......49 5.2. Starting the Red Hat Network Registration Client ........51 5.3. Registering a User Account ................54 5.4. Registering a System Profile ................56 5.4.1. Hardware System Profile ..............56 5.4.2.
  • Page 5 6.6.1. Software Channels .................120 6.6.2. Channel Entitlements ..............125 6.6.3. Download Software................125 6.6.4. Package Search ................126 6.6.5. Manage Software Channels ............126 6.6.6. Manage Config Channels — ..........128 6.7. Schedule ......................135 6.7.1. Pending Actions ................136 6.7.2. Failed Actions ................137 6.7.3. Completed Actions.................137 6.7.4.
  • Page 6 6.11.14. Release Notes................156 6.11.15. Get RHN Software ..............156 7. Monitoring ........................157 7.1. Prerequisites ....................157 7.2. Red Hat Network Monitoring Daemon ( ) ..........158 rhnmd 7.2.1. Probes requiring the daemon ............158 7.2.2. Installing the Red Hat Network Monitoring Daemon....159 7.2.3. Configuring SSH................159 7.2.4.
  • Page 7 A. Command Line Config Management Tools ............185 A.1. Red Hat Network Actions Control ............185 A.1.1. General command line options .............185 A.2. Red Hat Network Configuration Client ...........186 A.2.1. Listing Config Files...............186 A.2.2. Getting a Config File..............187 A.2.3. Viewing Config Channels .............188 A.2.4.
  • Page 8 C.4.2. General::Remote Program with Data ..........212 C.4.3. General::SNMP Check ..............213 C.4.4. General::TCP Check ..............213 C.4.5. General::UDP Check ..............214 C.4.6. General::Uptime (SNMP) .............215 C.5. Linux ......................215 C.5.1. Linux::CPU Usage ................216 C.5.2. Linux::Disk IO Throughput ............216 C.5.3. Linux::Disk Usage.................217 C.5.4. Linux::Inodes ................218 C.5.5.
  • Page 9 C.9.4. Oracle::Buffer Cache..............242 C.9.5. Oracle::Client Connectivity ............243 C.9.6. Oracle::Data Dictionary Cache .............244 C.9.7. Oracle::Disk Sort Ratio ..............244 C.9.8. Oracle::Idle Sessions ..............245 C.9.9. Oracle::Index Extents ..............246 C.9.10. Oracle::Library Cache ..............246 C.9.11. Oracle::Locks ................247 C.9.12. Oracle::Redo Log ................248 C.9.13. Oracle::Table Extents ..............249 C.9.14.
  • Page 11: Introduction To The Guide

    All versions of this manual are available in HTML and PDF formats at http://www.redhat.com/docs/manuals/RHNetwork/. This version of the manual covers version 4.4.5 of the Red Hat Enterprise Linux 3 and 4 Red Hat Update Agent and versions 2.9.14 and 2.9.12 of the Red Hat Enterprise Linux...
  • Page 12 Introduction to the Guide the command line and press [Enter] to invoke a command. Sometimes a command contains words that would be displayed in a different style on their own (such as file names). In these cases, they are considered to be part of the command, so the entire phrase is displayed as a command.
  • Page 13: User Input

    Introduction to the Guide top level of a menu on a GUI screen or window A word in this style indicates that the word is the top level of a pulldown menu. If you click on the word on the GUI screen, the rest of the menu should appear. For example: Under File on a GNOME terminal, the New Tab option allows you to open multiple shell prompts in the same window.
  • Page 14 Introduction to the Guide <replaceable> Text used in examples that is meant to be replaced with data provided by the user is displayed in this style. In the following example, <version-number> is dis- played in this style: The directory for the kernel source is /usr/src/kernels/ <...
  • Page 15: More To Come

    3.7 Reference Guide, RHN 3.7 Satellite Guide, RHN 3.7 Release Notes, and the RHN 4.0 Release Notes. Translations of the remaining RHN 4.0 documentation will be available after the initial release. Translated documentation is available at http://rhn.redhat.com/help/ 2.1. Send in Your Feedback If you would like to make suggestions about the Red Hat Network Reference Guide, please submit a report in Bugzilla: http://bugzilla.redhat.com/bugzilla/...
  • Page 16 Introduction to the Guide...
  • Page 17: Red Hat Network Overview

    Chapter 1. Red Hat Network Overview Have you ever read about a new version of a software package and wanted to install it but could not find it? Have you ever tried to find an RPM through an Internet search engine or an RPM repository and been linked to an unknown site? Have you ever tried to find an RPM but instead found only source files that you had to compile yourself?
  • Page 18: Update

    The RHN Update service is ideal for a user with one Red Hat Enterprise Linux system or a small number of Red Hat Enterprise Linux systems. Updated Subscription to Update can be purchased at https://www.redhat.com/apps/commerce/rhn/. With each Update subscription, you receive the essential functionality provided to Demo users, plus: Download Software —...
  • Page 19: Management

    To create an account that can be used to entitle systems to RHN Management, go to https://rhn.redhat.com/ and click on the Create Login link under the Sign In fields. On the Create a Red Hat Login page, click Create a new Corporate Login. After creating a corporate account, you may add users within your organization to it.
  • Page 20: Monitoring

    Chapter 1. Red Hat Network Overview signed to allow you to deploy and manage your network of Red Hat Enterprise Linux systems, users, and system groups. Like Management, Provisioning is based upon an organization. It takes this concept a step further by enabling customers with Provisioning entitlements to kickstart, reconfig- ure, track, and revert systems on the fly.
  • Page 21: Errata Notifications And Scheduled Package Installations

    Chapter 1. Red Hat Network Overview Notification — Alerts can be sent to email and pager addresses with contact methods • identified by you when a probe changes state. Each probe notification can be sent to a different method, or address. Central Status —...
  • Page 22: Before You Begin

    Chapter 1. Red Hat Network Overview 1. Your System Profile, available at http://rhn.redhat.com, is accessible only with an RHN-verified username and password. 2. A Digital Certificate is written to the client system after registration and is used to authenticate the system during each transaction between the client and Red Hat Network.
  • Page 23 Chapter 1. Red Hat Network Overview The version number might differ slightly. If you do not have the Red Hat Network Registration Client installed, the command will return: package rhn_register is not installed Perform this check for every package in Table 1-1 that is relevant to your system. Remem- ber, only Red Hat Enterprise Linux 2.1 users need Red Hat Network Registration Client.
  • Page 24 Chapter 1. Red Hat Network Overview...
  • Page 25: Red Hat Update Agent

    Chapter 2. Red Hat Update Agent The Red Hat Update Agent is your connection to Red Hat Network. It enables you to reg- ister your systems, create System Profiles, and alter the settings by which your organization and RHN interact. Once registered, your systems can use the Red Hat Update Agent to retrieve the latest software packages from Red Hat.
  • Page 26 Chapter 2. Red Hat Update Agent On the GNOME and KDE desktops, go to Applications (the main menu on the panel) • => System Tools => Red Hat Network. At a shell prompt (for example, an xterm or gnome-terminal), type the command •...
  • Page 27 Chapter 2. Red Hat Update Agent Option Description Temporarily override the configured package directory. --tmpdir=directory The default location is . This /var/spool/up2date option is useful if you do not have enough space in the configured location. Only add packages to the database and do not install --justdb them.
  • Page 28 Chapter 2. Red Hat Update Agent Figure 2-1. Configure Proxy Server The second dialog box to appear prompts you to install the Red Hat GPG key, as shown in Figure 2-2. This key is used to verify the packages you download for security purposes. Click Yes to install the key, and you will not see this message again.
  • Page 29: Registration

    Chapter 2. Red Hat Update Agent Figure 2-2. Install GPG Key 2.2. Registration Before you begin using Red Hat Network, you must create a username, password, and System Profile. Upon launch, the Red Hat Update Agent senses whether these tasks have been accomplished.
  • Page 30: Registering A User Account

    2.2.1. Registering a User Account Before you create a System Profile, you must create a user account. Red Hat recommends that you do so through the website at https://rhn.redhat.com/newlogin/, but you may also do so via Red Hat Update Agent (...
  • Page 31 Chapter 2. Red Hat Update Agent Those users that have created a Red Hat login previously may enter their username and password and click the Forward button to continue. Users that have registered at least one system with Red Hat Network can add new machines to the same account.
  • Page 32 Chapter 2. Red Hat Update Agent Is not case-sensitive, thereby eliminating the possibility of duplicate usernames differing • only by capitalization In addition, the following restrictions apply to both your username and password: Must be at least four characters long •...
  • Page 33: Activate

    Chapter 2. Red Hat Update Agent Figure 2-5. Create a User Account 2.2.2. Activate The Activation screen allows you to select various details of your registration. If you have a subscription number, enter it in the appropriate field. If not, select the Use one of my existing, active subscriptions radio button.
  • Page 34 Chapter 2. Red Hat Update Agent PCI devices • Disk sizes • Mount points • The software System Profile consists of a list of RPM packages for which you wish to receive notifications. The Red Hat Update Agent displays a list of all RPM packages listed in the RPM database on your system and then allows you to customize the list by deselecting packages.
  • Page 35 Chapter 2. Red Hat Update Agent Figure 2-6. Activate Figure 2-7 shows the progress bar displayed as the System Profile is sent.
  • Page 36: Channels

    Chapter 2. Red Hat Update Agent Figure 2-7. Sending System Profile to Red Hat Network 2.2.3. Channels Red Hat Update Agent next displays all package channels to which you have access. The channels you select from this screen must match the base operating system of the system you are registering.
  • Page 37 Chapter 2. Red Hat Update Agent Figure 2-8. Channels Red Hat Update Agent now compares the packages in your RPM database with those available from the Channel you selected. The progress bar shown in Figure 2-9 is displayed during this process. Figure 2-9.
  • Page 38: Packages Flagged To Be Skipped

    Chapter 2. Red Hat Update Agent Note If the version of on your system is older than the one in your selected channel, up2date the Red Hat Update Agent asks whether you would like to update it. If you agree, the only package that will be updated is the package.
  • Page 39: Available Package Updates

    Chapter 2. Red Hat Update Agent Figure 2-10. Packages Flagged to be Skipped 2.2.5. Available Package Updates The Red Hat Update Agent next displays all available updates except those you chose to skip in the previous screen. Select those you wish to download and click Forward to continue.To view the complete Errata Advisory text for an update, highlight the relevant package and click the View Advisory button.
  • Page 40 Chapter 2. Red Hat Update Agent Figure 2-11. Available Package Updates...
  • Page 41: Retrieving Packages

    Chapter 2. Red Hat Update Agent Figure 2-12. Example Errata Advisory 2.2.6. Retrieving Packages The Red Hat Update Agent tests the packages you selected to be certain that the require- ments of each RPM are met. If any additional packages are required, Red Hat Update Agent displays an error message.
  • Page 42: Installing Packages

    Chapter 2. Red Hat Update Agent Figure 2-13. Retrieving Packages 2.2.7. Installing Packages The packages must be installed after downloading them via the Red Hat Update Agent. If you chose not to install the packages via the Red Hat Update Agent, skip to Section 2.3.2 Manual Package Installation for further instructions.
  • Page 43 Chapter 2. Red Hat Update Agent Figure 2-14. Installing Packages When the Red Hat Update Agent has finished downloading the desired packages (and installing them if you chose the install option), it displays the screen in Figure 2-15. Click Finish to exit the Red Hat Update Agent.
  • Page 44: Command Line Version

    Chapter 2. Red Hat Update Agent Figure 2-15. All Finished 2.3. Command Line Version If you are not running X, you can still run the Red Hat Update Agent from a virtual console or remote terminal. If you are running X but want to use the command line version, you can force it not to display the graphical interface with the following command: up2date --nox The command line version of the Red Hat Update Agent allows you to perform advanced...
  • Page 45 Chapter 2. Red Hat Update Agent up2date -u The command line version of the Red Hat Update Agent accepts the following arguments: Option Description Briefly describe the available options. --usage List the available options and exit. --help Force to install this architecture of the --arch=architecture up2date package.
  • Page 46 Chapter 2. Red Hat Update Agent Option Description Install packages after they are downloaded. This --install argument temporarily overrides the configuration option Do not install packages after retrieval. Install all available packages. Used with --installall --channel Only add packages to the database and do not --justdb install them.
  • Page 47: Installing The Red Hat Gpg Key

    Chapter 2. Red Hat Update Agent Option Description List all packages available that are not currently --show-available installed. Show the channel name associated with each --show-channels package. List all packages currently installed that are not in --show-orphans channels to which the system is subscribed. Show the package installation dialog in GUI mode.
  • Page 48 (as root): /usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY download first, obtain from https://www.redhat.com/security/team/key.html . Here’s an example: Type bits/keyID Date User ID 1024D/650D5882 2001-11-21 Red Hat, Inc. (Security Response Team) 2048g/7EAB9AFD 2001-11-21 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.1 (GNU/Linux) mQGiBDv70vQRBADh701rf8WUzDG88kqlV/N5KQ1PF0amnODB/1EeuAD7n6bCBRmV...
  • Page 49: Manual Package Installation

    Chapter 2. Red Hat Update Agent 9+jlR0qDs9lIi/C2AJ9SBBfd4A8hyR4z3lY7e0LzjWF51LkCDQQ7+9O3EAgA8tMs xdUmuTfA+X78fMXh7LCvrL4Hi28CqvNM+Au81XJjDLNawZvpVmFlMmd9h0Xb5Jt2 BZWLR13rcDUByNdw1EWhVAzCz6Bp9Z3MIDhcP00iIBctIHn7YP9fi5vV0G03iryT XE01mhWoBlC233wr3XHwsqxFfZzaCZqqNKTl0+PNfEAIzJRgtYiW8nzFTPpIR05E oRn6EvmQfayOF2uYDX9Sk//lOD7T7RLtKjM/hPW/9NoCGwwROaG+VUzVv4aelh1L dJGEjpFtdxcrOUMD8xbkuGMznu0mpDI+J2BUDh5n57yOyEMaGrQ0jfY1ZqdqDvZg osY1ZHa6KlmuCWNTnwADBQf/XYhCicp6iLetnPv6lYtyRfFRpnK98w3br+fThywC t81P2nKv8lio6OsRbksGc1gX8Zl6GoHQYfDe7hYsCHZPoWErobECFds5E9M7cmzV TTyNTvrELrs07jyuPb4Q+mHcsYPILGR3M+rnXKGjloz+05kOPRJaBEBzP6B8SZKy QNqEfTkTYU4Rbhkzz/UxUxZoRZ+tqVjNbPKFpRraiQrUDsZFbgksBCzkzd0YURvi CegO2K7JPKbZJo6eJA10qiBQvAx2EUijZfxIKqZeLx40EKMaL7Wa2CM/xmkQmCgg Hyu5bmLSMZ7cxFSWyXOst78dehCKv9WyPxHV3m4iANWFL4hGBBgRAgAGBQI7+9O3 AAoJEF5UgINlDViCKWcAoMCeYStWVKXJTytzHEL6Wl8rXr8WAKCHuapJIA4/eFsf 4ciWtjY8cO0v8Q== =yOVZ -----END PGP PUBLIC KEY BLOCK----- Save the text file and import it into your keyring using the method applicable to your version of RPM.
  • Page 50: Log File

    Chapter 2. Red Hat Update Agent After running this command, your RHN System Profile reflects the latest software versions installed on your system. 2.3.4. Log File The Red Hat Update Agent keeps a log of all the actions that it performs on your system in the file .
  • Page 51 Chapter 2. Red Hat Update Agent Figure 2-16. General Settings In addition, RHN Proxy and Satellite customers have the option of selecting Red Hat Net- work Servers here. These customers should refer to the RHN Client Configuration Guide for detailed instructions. 2.4.1.2.
  • Page 52 Chapter 2. Red Hat Update Agent Figure 2-17. Retrieval/Installation Settings The following package retrieval options can be selected (see Figure 2-17): Do not install packages after retrieval — download selected RPM packages to the • desired directory and ignore the installation preferences Do not upgrade packages when local configuration file has been modified —...
  • Page 53 Chapter 2. Red Hat Update Agent Override version stored in System Profile — override the Red Hat Linux version in • your System Profile Package storage directory — change the directory where packages are downloaded; • the default location is /var/spool/up2date/ 2.4.1.3.
  • Page 54: Command Line Version

    Chapter 2. Red Hat Update Agent Figure 2-18. Package Exceptions Settings 2.4.2. Command Line Version The command line version of this tool performs the same function as the graphical version. It allows you to configure the settings used by the Red Hat Update Agent and store them in the configuration file /etc/sysconfig/rhn/up2date To run the command line version of the Red Hat Update Agent Configuration Tool, use...
  • Page 55: Registering With Activation Keys

    Chapter 2. Red Hat Update Agent noBootLoader 10. serverURL https://xmlrpc.rhn.redhat.com/XMLRPC 11. fileSkipList 12. sslCACert /usr/share/rhn/RHNS-CA-CERT 13. noReplaceConfig 14. useNoSSLForPackage No 15. systemIdPath /etc/sysconfig/rhn/systemid 16. enableProxyAuth 17. retrieveSource 18. versionOverride 19. headerFetchCount 20. networkRetries 21. enableProxy 22. proxyPassword 23. noSSLServerURL http://xmlrpc.rhn.redhat.com/XMLRPC 24.
  • Page 56 Chapter 2. Red Hat Update Agent and subscribe them to specific channels and system groups, all in one action. This automa- tion bypasses entitlement and registration via Red Hat Network Registration Client and Red Hat Update Agent. Alternatively, both the Red Hat Network Registration Client and Red Hat Update Agent offer the activation keys utility as part of their packages.
  • Page 57 Chapter 2. Red Hat Update Agent Refer to Section 6.4.7.2 Using Multiple Activation Keys at Once — to understand how differences in activation keys are handled. The above command performs all the actions of the Red Hat Network Registration Client and the registration function of the Red Hat Update Agent.
  • Page 58 Chapter 2. Red Hat Update Agent...
  • Page 59: Red Hat Network Daemon

    Chapter 3. Red Hat Network Daemon The Red Hat Network Daemon ( ) periodically connects to Red Hat Network rhnsd to check for updates and notifications. The daemon, which runs in the background, is typically started from the initialization scripts in /etc/init.d/rhnsd /etc/rc.d/init.d/rhnsd Provisioning-entitled systems served by an RHN Satellite Server may have actions imme-...
  • Page 60: Viewing Status

    RHN via SSL (port 443). You may test this by • running the following command from a shell prompt: telnet xmlrpc.rhn.redhat.com 443 the Red Hat Network Daemon is activated and running. You may ensure this by running •...
  • Page 61: Red Hat Network Alert Notification Tool

    Chapter 4. Red Hat Network Alert Notification Tool The Red Hat Network Alert Notification Tool is a notifier that appears on the panel and alerts users when software package updates are available for their systems. The list of updates is retrieved from the RHN Servers. The system does not have to be registered with Red Hat Network to display a list of updates;...
  • Page 62 Chapter 4. Red Hat Network Alert Notification Tool Figure 4-2. HTTP Proxy Configuration If your network connection requires you to use an HTTP Proxy Server to make HTTP connections, on the Proxy Configuration screen, type your proxy server in the text field with the format HOST:PORT.
  • Page 63: Notification Icons

    Chapter 4. Red Hat Network Alert Notification Tool 4.2. Notification Icons The applet displays a different icon, depending on the status of the updates. Table 4-1 shows the possible icons and their meaning. Icon Description Updates are available System is up-to-date Checking for updates Error has occurred Table 4-1.
  • Page 64: Applying Updates

    Chapter 4. Red Hat Network Alert Notification Tool Figure 4-3. Available Updates 4.4. Applying Updates If the system is registered with RHN and entitled to a service offering, you can apply the Errata Updates with the Red Hat Update Agent. To launch the Red Hat Update Agent, click on the applet, and then click on the Launch up2date button.
  • Page 65: Red Hat Network Registration Client

    Chapter 5. Red Hat Network Registration Client Before you begin using Red Hat Network, you must create a username, password, and Sys- tem Profile. The Red Hat Network Registration Client walks you through this process. Warning Only systems running Red Hat Enterprise Linux 2.1 need to use the Red Hat Network Registration Client before starting the Red Hat Update Agent.
  • Page 66 To start the command line version, use the command: rhn_register --nox --configure It has more configuration options than the graphical version. You will be presented with a list of options and their current values: enableProxyAuth noSSLServerURL http://xmlrpc.rhn.redhat.com/XMLRPC oemInfoFile /etc/sysconfig/rhn/oeminfo enableProxy networkSetup httpProxy...
  • Page 67: Starting The Red Hat Network Registration Client

    Chapter 5. Red Hat Network Registration Client The most common options configured are to enable a enableProxy httpProxy proxy server. To enable a proxy server, change the value for to Yes and enableProxy the value of to the name of the proxy server and port number in the format httpProxy HOST:PORT.
  • Page 68 Yes. If you overwrite an existing system registration, you can delete the unused profile via the website at https://rhn.redhat.com. Figure 5-3. Warning: This System Already Registered The opening screen for the Red Hat Network Registration Client provides a brief...
  • Page 69 Chapter 5. Red Hat Network Registration Client Next to continue with the registration process. If you click Cancel, the registration process ends and no information is sent. Figure 5-4. Welcome Screen Red Hat is committed to protecting your privacy (see Figure 5-5). The information gathered during the Red Hat Network registration process is used to create a System Profile.
  • Page 70: Registering A User Account

    Chapter 5. Red Hat Network Registration Client Figure 5-5. Red Hat Privacy Statement 5.3. Registering a User Account Before you can create a System Profile, you must create a user account. The only required information in this section is a unique username, password, and a valid email address. In the screen shown in Figure 5-7, you must choose a username and password.
  • Page 71 Chapter 5. Red Hat Network Registration Client Figure 5-6. Error: Username Already Exists Note If you are already a member of redhat.com, you can use the same user name and pass- word. However, you must continue with the registration process to create your System Profile.
  • Page 72: Registering A System Profile

    Chapter 5. Red Hat Network Registration Client Figure 5-7. Create a Unique Username and Password Most users can leave the Org Info section blank. If you have an existing organization ac- count, work with your Organization Administrator to ensure that your system is added to that account.
  • Page 73 Chapter 5. Red Hat Network Registration Client 5.4.1. Hardware System Profile After creating a username and password for your Red Hat Network account, the Red Hat Network Registration Client probes your system for the following information: Red Hat Enterprise Linux version •...
  • Page 74: Software System Profile

    Chapter 5. Red Hat Network Registration Client Figure 5-8. System Profile - Hardware 5.4.2. Software System Profile The software System Profile consists of a list of RPM packages for which you wish to receive notifications. The Red Hat Network Registration Client displays a list of all RPM packages listed in the RPM database on your system and then allows you to customize the list by deselecting packages.
  • Page 75 Chapter 5. Red Hat Network Registration Client Figure 5-9. Registration Wizard Once the RPM package list is built, the list is displayed as shown in Figure 5-10. Dese- lecting Include RPM Packages installed on this system in my System Profile omits this information from your System Profile.
  • Page 76: Finishing Registration

    Chapter 5. Red Hat Network Registration Client Choose which packages to exclude, if any, from the System Profile, and click Next to continue with the registration process. Figure 5-11. Choose which RPM Packages to Exclude from System Profile 5.5. Finishing Registration As seen in Figure 5-12, the last step of registration is to confirm that you want to send your System Profile to the Red Hat Network.
  • Page 77 Chapter 5. Red Hat Network Registration Client Figure 5-12. Finished Collecting Information for System Profile Figure 5-13 shows the progress bar displayed while your profile is sent. This process may take some time depending on your connection speed. Figure 5-13. Send System Profile to Red Hat Network The Red Hat Network Registration Client displays the Registration Finished screen (Figure 5-14 once your System Profile has been sent successfully.
  • Page 78: Entitling Your System

    Demo entitlement after creating an account by registering a system with RHN or creating a redhat.com account To entitle a system, go to http://rhn.redhat.com and log in using the same username and password you just used in the Red Hat Network Registration Client. Click Systems on the top navigation bar and then Systems Entitlements in the left navigation bar.
  • Page 79: Text Mode Rhn Registration Client

    Chapter 5. Red Hat Network Registration Client Warning Changing a system’s entitlement is an irreversible action. You may be unable to change the entitlement levels of some systems. For more information, refer to the RHN entitlement policy linked from the System Entitlements page. The number of entitlements remaining decreases, and your system becomes ready to use the Red Hat Update Agent and RHN website.
  • Page 80 Chapter 5. Red Hat Network Registration Client Figure 5-15. Text Mode Welcome Screen...
  • Page 81: Red Hat Network Website

    Chapter 6. Red Hat Network Website You can use the Red Hat Network website to manage multiple Red Hat Enterprise Linux systems simultaneously, including viewing Errata Alerts, applying Errata Updates, and installing packages. This chapter seeks to identify all of categories, pages, and tabs within the website and explain how to use them.
  • Page 82: Entitlement Views

    Chapter 6. Red Hat Network Website Figure 6-3. Left Navigation Bar — Users Some pages have sub-tabs. These tabs offer an additional layer of granularity in performing tasks for systems or users. The following is a menu bar for all System Details sub-tabs. This system has Management and Provisioning entitlements, but not Monitoring: Figure 6-4.
  • Page 83: Categories And

    Chapter 6. Red Hat Network Website If an icon precedes a paragraph, only the specific portion of the page or tab discussed afterward requires the indicated entitlement level. When a page or tab is associated with a particular entitlement level, all of its tabs and subtabs require at least the same entitlement level but may need a higher entitlement.
  • Page 84 Chapter 6. Red Hat Network Website Activation Keys — — Generate an activation key for an RHN-entitled system. • This activation key can be used to grant a specified level of entitlement or group membership to a newly registered system with the command.
  • Page 85: Errata Alert Icons

    Chapter 6. Red Hat Network Website User List — — List users for your organization. • Monitoring — — Run probes and receive notifications regarding systems. • Probe Status — — View probes by state. • Notification — — View contact methods established for your organization. •...
  • Page 86: Lists

    Some lists also offer the ability to retrieve items alphabetically by clicking the letters above the table. 6.2. Logging into the RHN Website In a Web browser, navigate to http://rhn.redhat.com. The page shown in Figure 6-5 will be displayed.
  • Page 87: Your Rhn

    Chapter 6. Red Hat Network Website Figure 6-5. RHN Website If you have not registered a system yet or do not have a redhat.com account, create a new account by clicking Create Login. After creating a new user account, you must register a system before using RHN.
  • Page 88 Chapter 6. Red Hat Network Website Section 6.1 Navigation to become familiar with the layout and symbols used throughout the website. Figure 6-6. Your Red Hat Network The top of the page shows how many systems need attention, provides a link to quickly view those systems, and displays a summary of scheduled actions.
  • Page 89: Your Account

    Remember, if you change your Red Hat Network password (the one used to log into RHN and redhat.com), you will not see your new one as you type it for security reasons. Also for security, your password is represented by 12 asterisks no matter how many characters it actually contains.
  • Page 90: Your Preferences

    Chapter 6. Red Hat Network Website 6.3.1.1. Addresses The Addresses page allows you to manage your mailing, billing and shipping addresses, as well as the associated phone numbers. Just click Edit this address below the address to be modified, make the changes, and click Update Address. 6.3.1.2.
  • Page 91: Purchase History

    Chapter 6. Red Hat Network Website these summaries only to verified email addresses. To disable all messages, simply deselect this checkbox. RHN List Page Size — Maximum number of items that appear in a list on a single page. • If more items are in the list, clicking the Next button displays the next group of items.
  • Page 92 Chapter 6. Red Hat Network Website Figure 6-7. Systems Overview Clicking the View System Groups link at the top of the Overview page takes you to a similar summary of your system groups. It identifies group status and displays the number of systems contained.
  • Page 93: Systems

    Chapter 6. Red Hat Network Website 6.4.2. Systems The Systems page displays a list of all of your registered systems. The Systems list con- tains several columns of information for each system: Select — Update or unentitled systems cannot be selected. To select systems, mark •...
  • Page 94 Chapter 6. Red Hat Network Website Important If the RHN website identifies package updates for the system, yet the Red Hat Update Agent responds with "Your system is fully updated" when run, a conflict likely exists in the system’s package profile or in the configuration file.
  • Page 95: System Details

    Chapter 6. Red Hat Network Website 6.4.2.5. Inactive The Inactive page displays the systems that have not checked into RHN for 24 hours or more. When the Red Hat Update Agent connects to RHN to see if there are any updates available or if any actions have been scheduled, this is considered a checkin.
  • Page 96 Chapter 6. Red Hat Network Website 6.4.2.8.1. System Details ⇒ Details Displays information about the system. This is the first tab you see when you click on a system. It offers direct access to some of the functionality provided in subsequent tabs. For instance, under the System Info heading, a message appears describing the status of this machine.
  • Page 97 Chapter 6. Red Hat Network Website Section 6.4.4 System Set Manager — for details. The following properties deserve additional explanation: Receive Notifications of Updates/Errata — This setting keeps you abreast of all ad- • visories pertaining to the system. Anytime an update is produced and released for the system, a notification is sent via email.
  • Page 98 Chapter 6. Red Hat Network Website within the Custom System Info page. Refer to Section 6.4.9 Custom System Info — for instructions. Once the key exists, you may assign a value to it by clicking create new value here. Click the name of the key in the resulting list and enter a value for it in the Description field, such as "Example#456."...
  • Page 99 Chapter 6. Red Hat Network Website Then create a file in that directory to act as a flag to RHN signaling permission to allow remote commands: touch /etc/sysconfig/rhn/allowed-actions/script/run You may then identify a specific user, group, and timeout period, as well as the script itself on this page.
  • Page 100 Chapter 6. Red Hat Network Website — When selecting packages install, upgrade, remove, Provisioning customers have option running remote command automatically before after package installation. Refer Section 6.4.2.8.1.8 System Details ⇒ Details ⇒ Remote Command — more information. 6.4.2.8.3.1. System Details ⇒ Packages ⇒ Packages The default display of the Packages tab describes the options available to you and provides the means to update your package list.
  • Page 101 Chapter 6. Red Hat Network Website system’s packages with information from the database, such as MD5 sum, file size, per- missions, owner, group and type. To verify a package or packages, select them, click the Verify Selected Packages button, and confirm this action. Once finished, you can view the results by selecting this action within the History subtab under Events.
  • Page 102 Chapter 6. Red Hat Network Website 6.4.2.8.4.2. System Details ⇒ Channels ⇒ Configuration — Assists in managing the configuration of the system. This section is available to normal users with access to systems that have configuration management enabled. Like software channels, configuration channels store files to be installed on systems.
  • Page 103 Chapter 6. Red Hat Network Website If a file exists, click its name to go to the Configuration File Details page. Refer to Section 6.6.6.6 Configuration File Details — for instructions. To replicate the file within a config channel, select its checkbox, click the Copy to Config Channel button, and select the destination channel.
  • Page 104 Chapter 6. Red Hat Network Website 6.4.2.8.6.1. System Details ⇒ Snapshots ⇒ Snapshots — The default display of the Snapshots tab lists the reason, dates, and times for snapshots taken, as well as any tags associated with the snapshots. To revert to a previous configu- ration, click the Reason of the snapshot taken at the desired date and time and review the potential changes on the provided subtabs, starting with Rollback.
  • Page 105 Chapter 6. Red Hat Network Website Kickstart interface. Refer to Section 6.4.10 Kickstart — for details. 6.4.2.8.7.1. System Details ⇒ Kickstart ⇒ Schedule — The default display of the Kickstart tab, this subtab allows the kickstarting of the selected system. To schedule a kickstart, select a distribution, identify the type (IP address or manual selection of kickstart profile), and click Continue.
  • Page 106 Chapter 6. Red Hat Network Website 6.4.2.8.7.3. System Details ⇒ Kickstart ⇒ Session History — Displays particular points in a kickstart session’s progress. Like Session Status, this subtab appears only if you’ve scheduled a kickstart. It lists individual actions, such as package installs, as they occur.
  • Page 107: System Groups

    Chapter 6. Red Hat Network Website 6.4.2.8.9. System Details ⇒ Probes — Displays all of the probes monitoring the system. You must be logged into an RHN Satellite Server with Monitoring enabled and have Monitoring entitlements to see this tab. The State column shows icons representing the status of each probe. Refer to for descriptions of these states.
  • Page 108 Chapter 6. Red Hat Network Website Figure 6-8. System Group List The System Groups list contains several columns for each group: Select — These checkboxes enable you to add systems in groups to the System Set • Manager. To select groups, mark the appropriate checkboxes and click the Update button below the column.
  • Page 109: Creating Groups

    Chapter 6. Red Hat Network Website — All systems within group are up-to-date • — Critical Errata available, update strongly recommended • — Updates available and recommended • Group Name — The name of the group as configured during its creation. The name •...
  • Page 110 Chapter 6. Red Hat Network Website Groups list in that it loads the group’s systems and launches the System Set Manager immediately. Refer to Section 6.4.4 System Set Manager — for more information. The System Group Details page is broken down into tabs: 6.4.3.3.1.
  • Page 111: System Set Manager

    Chapter 6. Red Hat Network Website 6.4.3.3.5. System Group Details ⇒ Admins — List of all organization users that have the ability to manage the system group. Organiza- tion Administrators are clearly identified. System Group Administrators are marked with an asterisk (*). To change the system group’s users, select and unselect the appropriate checkboxes and click the Update button.
  • Page 112 Chapter 6. Red Hat Network Website 6.4.4.1. System Set Manager ⇒ Overview — Description of the various options available to you in the remaining tabs. 6.4.4.2. System Set Manager ⇒ Systems — List of systems now selected. To remove systems from this set, select them and click the Remove button.
  • Page 113 Chapter 6. Red Hat Network Website 6.4.4.4.2. System Set Manager ⇒ Packages ⇒ Install — A list of channels from which you may retrieve packages. This list includes all channels to which systems in the set are subscribed; a package is installed on a system only if the system is subscribed to the channel from which the package originates.
  • Page 114 Chapter 6. Red Hat Network Website create new group on the top-right corner. In the resulting page, type its name and de- scription in the identified fields and click the Create Group button. To add or remove the selected systems in any of the system groups, toggle the appropriate radio buttons and click the Alter Membership button.
  • Page 115 Chapter 6. Red Hat Network Website 6.4.4.9.2.2. System Set Manager ⇒ Channels ⇒ Config Channels ⇒ Diff — Use this subtab to validate configuration files on the selected systems against copies in your central repository on RHN. The table lists the configuration files associated with any of the selected systems.
  • Page 116 Chapter 6. Red Hat Network Website operating system installed on the system. Systems are unsubscribed from all channels and subscribed to the new base channels. For this reason, this should be done with caution. Se- lect the new base channel from the pulldown menus and click the Change Base Channels button.
  • Page 117 Chapter 6. Red Hat Network Website scription of the Configuration subtab of the Channels tab for instructions. You may then identify a specific user, group, timeout period, and the script on this page. Select a date and time to perform the command, and click Schedule Remote Command. 6.4.4.11.
  • Page 118 Chapter 6. Red Hat Network Website 6.4.4.11.5. System Set Manager ⇒ Misc ⇒ Delete Systems — Click Delete System Profiles, then click the Confirm Deletions button to remove the selected profiles permanently. 6.4.4.11.6. System Set Manager ⇒ Misc ⇒ Add or Remove Add-On Entitlements —...
  • Page 119: System Entitlements

    Chapter 6. Red Hat Network Website 6.4.5. System Entitlements To use all of the features of RHN, your systems must be entitled — subscribed to an RHN service level. Use the System Entitlements page to configure which systems are entitled to which service offerings.
  • Page 120: Advanced Search

    Chapter 6. Red Hat Network Website 6.4.6. Advanced Search — The System Search page allows you to search through your systems according to specific criteria. These criteria include custom system information, system details, hardware, de- vices, interface, networking, packages, and location. The activity selections (Days Since Last Checkin, for instance) can be especially useful in finding and removing outdated Sys- tem Profiles.
  • Page 121 Chapter 6. Red Hat Network Website are the separator used when including two or more activation keys at once. Refer to Section 6.4.7.2 Using Multiple Activation Keys at Once — for details. 3. Provide the following information: Description — User-defined description to identify the generated activation key. •...
  • Page 122: Stored Profiles

    Chapter 6. Red Hat Network Website 6.4.7.2. Using Multiple Activation Keys at Once — Provisioning customers should note that multiple activation keys can be included at the command line or in a single kickstart profile. This allows you to aggregate the aspects of various keys without recreating a new key specific to the desired systems, simplifying the registration and kickstart processes while slowing the growth of your key list.
  • Page 123: Custom System Info

    Chapter 6. Red Hat Network Website 6.4.9. Custom System Info — RHN Provisioning customers may include completely customizable information about their systems. Unlike notes, the information here is more formal and may be searched upon. For instance, you may decide to identify an asset tag for each system. To do this, you must create an asset key within the Custom System Info page.
  • Page 124 Chapter 6. Red Hat Network Website A DHCP server is not required for kickstarting, but it can make things easier. If you • are using static IP addresses, you should select static IP while developing your kickstart profile. An FTP server can be used in place of hosting the kickstart distribution trees via HTTP. •...
  • Page 125 Chapter 6. Red Hat Network Website 7. The new machine is built based upon the parameters established within the kickstart configuration file. 6.4.10.3. Creating Kickstarts If you are not using RHN Satellite Server, and need to develop a new kickstart profile, first create a distribution through the Distributions page.
  • Page 126 Chapter 6. Red Hat Network Website 6.4.10.4.1. Kickstart Details ⇒ Details — The default display of the Kickstart Details page shows the kickstart profile name and label, as well as the associated distribution, URL to be used, whether it’s the default profile for your organization, and any comments about the profile.
  • Page 127 Chapter 6. Red Hat Network Website 6.4.10.4.4. Kickstart Details ⇒ Packages — Allows the addition or removal of specific software packages from the kickstart profile. To include packages, enter them in the text field. These are passed directly to Anaconda. To remove packages, precede them with a dash (-).
  • Page 128 Chapter 6. Red Hat Network Website 6.4.10.4.6.2. Kickstart Details ⇒ Post ⇒ GPG and SSL keys — Displays all of the GPG and SSL keys created by your organization. To include GPG and SSL keys in the %post section, select the keys and click the Update Keys button. Refer to Section 6.4.10.8 Kickstart ⇒...
  • Page 129 Chapter 6. Red Hat Network Website 6.4.10.5. Kickstart ⇒ Profiles — Lists the kickstart profiles created by your organization. Click a name to see the Kickstart Details page. To enable inactive profiles, select the appropriate checkboxes and click the Update Profiles. 6.4.10.6.
  • Page 130 Chapter 6. Red Hat Network Website Important RHN Satellite Server users should note that channels imported with satellite-sync are made available automatically and do not require the creation of a separate installation tree. These trees are available to client systems that kickstart through the Satellite. While you may be able to access the files from a non-kickstarting client, this functionality is not supported and may be removed at any time in the future.
  • Page 131 Chapter 6. Red Hat Network Website When finished, you may include the file preservation list in the kickstart profile to be used on systems containing those files. Refer to Section 6.4.10.3 Creating Kickstarts for precise steps. 6.4.10.11. Building Bootable Kickstart ISOs While you can schedule a registered system to be kickstarted to a new operating system and package profile, it is also useful to be able to kickstart a system that is not registered with RHN, or does not yet have an operating system installed.
  • Page 132: Errata

    Chapter 6. Red Hat Network Website mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 \ -boot-info-table -R -J -v -T isolinux/ Note that is the relative path to the directory containing the isolinux files from isolinux/ the distribution CD, while is the output ISO file, which is placed into the current file.iso directory.
  • Page 133: Relevant Errata

    • In addition to the pages described within this chapter, you may view Errata by product line from the following location: https://rhn.redhat.com/errata. 6.5.1. Relevant Errata As shown in Figure 6-9, the Relevant Errata page displays a customized list of Errata Alerts that applies to your registered systems.
  • Page 134: All Errata

    Chapter 6. Red Hat Network Website Figure 6-9. Errata List Clicking on the Advisory takes you to the Details tab of the Errata Details page. Clicking on the number of associated systems takes you to the Affected Systems tab of the Errata Details page.
  • Page 135 Chapter 6. Red Hat Network Website Apply all applicable Errata Updates to a system by clicking on Systems => Systems in the top and left navigation bars. Click on the name of an entitled system, and click the Errata tab of the resulting System Details page. When the Relevant Errata list appears, click Select All then the Apply Errata button on the bottom right-hand corner of the page.
  • Page 136: Advanced Search

    Chapter 6. Red Hat Network Website 6.5.2.2.1. Errata Details ⇒ Details Provides the Errata Report issued by Red Hat. It describes the problem and solution and lists the channels it affects. Clicking on a channel name displays the Packages tab of the Channel Details page.
  • Page 137: Software Channels

    Chapter 6. Red Hat Network Website 6.6.1. Software Channels The Software Channels page is the first to appear in the Channels category. A software channel is a list of Red Hat Enterprise Linux packages grouped by use. Channels are used to choose packages to be installed on a system.
  • Page 138 Chapter 6. Red Hat Network Website Figure 6-10. Relevant Channels 6.6.1.2. Retired Channels The Retired Channels page displays channels available to your organization that have reached their end-of-life dates. These channels do not receive updates. 6.6.1.3. All Channels The All Channels page can be retrieved by clicking All below Software Channels in the left navigation bar.
  • Page 139 Chapter 6. Red Hat Network Website 6.6.1.4. Software Channel Details If you click on the name of a channel, the Software Channel Details page appears. This page is broken down into the following tabs: 6.6.1.4.1. Software Channel Details ⇒ Details General information about the channel and the parent channel, if it is a child channel.
  • Page 140 Chapter 6. Red Hat Network Website 6.6.1.4.3. Software Channel Details ⇒ Managers — List of users who have permission to manage the channel. This tab is applicable only to RHN Proxy Server and RHN Satellite Server customers with custom channel management privileges.
  • Page 141: Channel Entitlements

    Chapter 6. Red Hat Network Website 6.6.1.4.7. Software Channel Details ⇒ Target Systems List of entitled systems that are eligible for subscription to the channel. This tab appears only for child channels. Use the checkboxes to select the systems, then click the Subscribe button on the bottom right-hand corner.
  • Page 142: Package Search

    Refer http://www.redhat.com/download/howto_download.html additional download instructions and steps to burn images to discs. Refer to the operating system’s respective installation guide for instructions on installing from CD-ROM or hard drive, available at http://www.redhat.com/docs/. ISOs can be further broken down by their relevance to your systems. Two such lists emerge: Relevant and All.
  • Page 143 Chapter 6. Red Hat Network Website To clone an existing channel, click the clone channels link in the upper right of the screen, select the channel to be cloned from the dropdown menu, and click the Create Channel button. The next screen presents various options for the new channel, including base archi- tecture and GPG options.
  • Page 144: Manage Config Channels

    Chapter 6. Red Hat Network Website To list all packages in the channel, click the List / Remove Packages link. Check the box to the left of any package you wish to remove, then click the Remove Packages button in the lower right of the page.
  • Page 145 Chapter 6. Red Hat Network Website 6.6.6.1. Preparing Systems for Config Management For a system to have its configuration managed through RHN, it must have the appropri- ate tools and file installed. These tools may already be installed on your config-enable system, especially if you kickstarted the system with configuration management function- ality.
  • Page 146 Chapter 6. Red Hat Network Website 6.6.6.2.2. Manage Config Channels ⇒ Config Channels ⇒ System — The System Config Channels page can be retrieved by selecting it from the pulldown menu on the main Manage Config Channels page. It displays local override (system- specific) configuration channels and works similarly to the Global Config Channels page in that clicking the name of a system takes you to the List subtab of the Configuration Channel Details page.
  • Page 147 Chapter 6. Red Hat Network Website 6.6.6.5.1. Configuration Channel Details ⇒ Details — General information about the channel. This is the first tab you see when you click on a channel. It displays basic information about the channel, including name and description, and provides the means to alter this information.
  • Page 148 Chapter 6. Red Hat Network Website Note You must enter a valid user and group for the system to which the file (or directory) will be deployed. If either is not valid, the deployment of the file fails with an error message similar to the following: Error: unable to deploy file /root/example-config-file, information on user ’jdoe’...
  • Page 149 Chapter 6. Red Hat Network Website 6.6.6.6.1. Configuration File Details ⇒ Details — General information about the file. This is the first tab you see when you click on a file. It displays basic information about the file, including path, associated channel, revision, and date.
  • Page 150 Chapter 6. Red Hat Network Website 6.6.6.7. Including Macros in your Configuration Files Being able to store and share identical configurations is useful, but what if you have many variations of the same configuration file? What do you do if you have configuration files that differ only in system-specific details, such as hostname and MAC address? In traditional file management, you would be required to upload and distribute each file separately, even if the distinction is nominal and the number of variations is in the hundreds...
  • Page 151: Schedule

    Chapter 6. Red Hat Network Website ), the variables will be replaced with the hostname and IP address of the rhncfg-client system, as recorded in RHN’s System Profile. In the above configuration file, for example, the deployed version resembles the following: hostname=test.example.domain.com ip_address=177.18.54.7 To capture custom system information, insert the key label into the custom information...
  • Page 152: Pending Actions

    Chapter 6. Red Hat Network Website 2. Rollback Package Actions 3. System Reboots 4. Errata Updates 5. Configuration File Alteration (deploy, upload, and diff) 6. Hardware Profile Updates 7. Package List Profile Updates 8. Kickstart Initiation 9. Remote Commands Each page in the Schedule category represents an action status. 6.7.1.
  • Page 153: Failed Actions

    Chapter 6. Red Hat Network Website Figure 6-11. Schedule - Pending Actions 6.7.2. Failed Actions Actions that could not be completed. If the action returns an error, it is displayed here. 6.7.3. Completed Actions Actions that have succeeded. 6.7.4. Archived Actions Actions that you have selected to store for review.
  • Page 154: Actions List

    Chapter 6. Red Hat Network Website 6.7.5. Actions List In each page, each row in the list represents a single scheduled event or action that might affect multiple systems and involve various packages. The list contains several columns of information: Select —...
  • Page 155: Users

    Chapter 6. Red Hat Network Website 6.7.5.1.3. Action Details ⇒ In Progress Systems List of systems on which the action is now being undertaken. To cancel an action, select the system using the appropriate checkbox and click the Unschedule Action button. Clicking a system name takes you to its System Details page.
  • Page 156: User List ⇒ Active

    Chapter 6. Red Hat Network Website Server or RHN Proxy Server. This person may change the base channels of systems, make channels globally subscribable, and create entirely new channels. Configuration Administrator — This role enables the user to manage the configuration •...
  • Page 157 Chapter 6. Red Hat Network Website Figure 6-12. User List 6.8.1.1. User List ⇒ Active ⇒ User Details — The User Details page allows Organization Administrators to manage the permissions and activity of all users. Included in the User Details page is the ability to delete or disable users.
  • Page 158 Chapter 6. Red Hat Network Website To disable a user: 1. Navigate to the user’s User Details tab. 2. Verify that the user is not an Organization Administrator. If they are, uncheck the box to the left of that role and click the Submit button in the lower right of the screen. 3.
  • Page 159 Chapter 6. Red Hat Network Website 6.8.1.1.2. User List ⇒ Active ⇒ User Details ⇒ System Groups — This tab displays a list of system groups that the user may administer. Organization Ad- ministrators may use the check boxes to set this user’s access permissions to each system group.
  • Page 160 Chapter 6. Red Hat Network Website 6.8.1.1.4.2. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions ⇒ Management — Identifies channels the user may manage. To change these, select or unselect the appropriate checkboxes and click the Update Permissions button. This status does not enable the user to create new channels.
  • Page 161: User List ⇒ Disabled

    Chapter 6. Red Hat Network Website 6.8.1.1.7. User List ⇒ Active ⇒ User Details ⇒ Notification Methods — This tab lists email and pager addresses designated to receive alerts from Monitoring probes. To create a method, click create new method and complete the fields. If you will receive these alerts via pager, select the associated checkbox to have the messages sent in a shorter format.
  • Page 162: Probe Status

    Chapter 6. Red Hat Network Website 6.9.1. Probe Status — As shown in Figure 6-13, the Probe Status page is shown by default when you click Mon- itoring in the top navigation bar. Figure 6-13. Probe Status The Probe Status page displays the summary count of probes in the various states and provides a simple interface to find problematic probes quickly.
  • Page 163 Chapter 6. Red Hat Network Website — Unknown - The probe is not able to accurately report metric or state data. • — Pending - The probe has been scheduled but has not yet run or is unable to run. •...
  • Page 164: Notification

    Chapter 6. Red Hat Network Website 6.9.1.5. Probe Status ⇒ OK — The probes that have run successfully without exception. This is the state desired for all probes. 6.9.1.6. Probe Status ⇒ All — All probes scheduled on systems in your account, listed in alphabetical order by the name of system.
  • Page 165 Chapter 6. Red Hat Network Website 6.9.2.1. Notification ⇒ Filters Notification filters allow you to create long-term rules that suspend, redirect, or automat- ically acknowledge standard notifications or send supplemental notifications. This can be helpful in managing verbose or frequent probe communication. 6.9.2.1.1.
  • Page 166: Probe Suites

    Chapter 6. Red Hat Network Website 11. Ending: Enter an end date and time for the filter. 12. Recurring Duration: How long a recurring filter instance is active. This field, appli- cable to recurring filters only, begins at the Beginning time specified above. Any notification generated outside of the specified duration is not filtered.
  • Page 167 Chapter 6. Red Hat Network Website and running. Refer to the RHN Satellite Server 4.0.5 Installation Guide for additional information. 4. Add the systems to which the Probe Suite applies. Click the add systems to probe suite link in the upper right of the screen to continue. 5.
  • Page 168: Scout Config Push

    Chapter 6. Red Hat Network Website Note This action deletes all of the Probe Suites’ probes from the system as well as all of the historical Time Series and Event Log data. This action is irreversible. To remove a system from the Probe Suite and delete all associated probes from the system: 1.
  • Page 169: Satellite Tools

    Chapter 6. Red Hat Network Website 6.10. Satellite Tools This page allows RHN Satellite Server customers to manage the basic configuration of their Satellite. The default page, Task Engine Status, provides a summary of the latest execution times for key tasks. Figure 6-14.
  • Page 170: Satellite Tools ⇒ String Manager

    Chapter 6. Red Hat Network Website Adjust the configuration options and click the Update Configuration button to update the Satellite. 6.10.2. Satellite Tools ⇒ String Manager The Satellite String Manager allows you to control the standard strings generated in emails from the Satellite.
  • Page 171: Migration Faq

    Chapter 6. Red Hat Network Website 6.11.4. Migration FAQ Frequently Asked Questions regarding migration from RHL end-of-life products. 6.11.5. Reference Guide The Reference Guide page takes you to this same document, the most comprehensive set of instructions for using Red Hat Network. Note that links to other technical guides may also appear in the left navigation bar, depending on the entitlement level and product offering of the account with which you logged in.
  • Page 172: Client Configuration Guide

    The Outage Policy page identifies scheduled maintenance windows for Red Hat Network and provides the means to subscribe to the Email Outage List (rhn-outage-list@redhat.com) to be notified of emergency and other unscheduled outages. 6.11.14. Release Notes The Release Notes page lists the notes accompanying every recent release of Red Hat Net- work.
  • Page 173: Monitoring

    Chapter 7. Monitoring The Red Hat Network Monitoring entitlement allows you to perform a whole host of ac- tions designed to keep your systems running properly and efficiently. With it, you can keep close watch on system resources, network services, databases, and both standard and custom applications.
  • Page 174: Red Hat Network Monitoring Daemon

    Chapter 7. Monitoring the internal process monitors to be executed. You may, however, be able to run these probes using the systems’ existing SSH daemon ( ). Refer to sshd Section 7.2 Red Hat Network Monitoring Daemon ( ) for installation instructions rhnmd and a quick list of probes requiring this secure connection.
  • Page 175: Installing The Red Hat Network Monitoring Daemon

    Chapter 7. Monitoring LogAgent::Log Pattern Match • LogAgent::Log Size • Network Services::Remote Ping • Oracle::Client Connectivity • General::Remote Program • General::Remote Program with Data • Note that all probes in the Linux group have this requirement. 7.2.2. Installing the Red Hat Network Monitoring Daemon Install the Red Hat Network Monitoring Daemon to prepare systems for monitoring with the probes identified in Section 7.2.1 Probes requiring the daemon.
  • Page 176: Installing The Ssh Key

    Chapter 7. Monitoring required between the systems and RHN. This may be especially desirable if you already have running. To configure the daemon for monitoring use: sshd 1. Ensure the SSH package is installed on the systems to be monitored: rpm -qi ssh 2.
  • Page 177: Notifications

    Chapter 7. Monitoring Note If valid entries already exist in , add the daemon key to the authorized_keys file rather than replacing the existing key. To do so, save the copied text to in the same directory and then run the following command: id_dsa.pub .ssh/ cat ~/.ssh/id_dsa.pub >>...
  • Page 178: Creating Notification Methods

    These notifications come in the form of brief text messages sent to either email or pager addresses. Here is an example of an email notification: Subject: CRITICAL: [hostname]: Satellite: Users at 1 From: "Monitoring Satellite Notification" (rogerthat01@redhat.com) Date: Mon, 6 Dec 2004 13:42:28 -0800 To: user@organization.com This is RHN Monitoring Satellite notification 01dc8hqw.
  • Page 179: Redirecting Notifications

    Chapter 7. Monitoring Notification #116 for Users Run from: RHN Monitoring Satellite As you can see, the longer email notifications contain virtually everything you would need to know about the associated probe. In addition to the probe command, run time, sys- tem monitored, and state, the message contains the Send ID, which is a unique character string representing the precise message and probe.
  • Page 180: Filtering Notifications

    Chapter 7. Monitoring Note You can halt or redirect almost all probe notifications by replying to a notification emails with a variation of the command . However, you cannot halt Satellite ack suspend host probe notifications by responding to a probe with or other redirect ack suspend host responses.
  • Page 181: Probes

    Chapter 7. Monitoring 5. On the System Details ⇒ Probes tab, select another notification method and click Update Probe. 6. You may now return to the Monitoring ⇒ Notifications page and delete the notifi- cation method. 7.5. Probes Now that the Red Hat Network Monitoring Daemon has been installed and notification methods have been created, you may begin installing probes on your Monitoring-entitled systems.
  • Page 182: Establishing Thresholds

    Chapter 7. Monitoring 7. If the Timeout field appears, review the default value and adjust to meet your needs. Most but not all timeouts result in an UNKNOWN state. If the probe’s metrics are time-based, ensure the timeout is not less than the time alloted to thresholds. Other- wise, the metrics serve no purpose, as the probe will time out before any thresholds are crossed.
  • Page 183: Troubleshooting

    RHN Server as the nocpulse user. The rhn-catalog output will resemble: 2 ServiceProbe on example1.redhat.com (199.168.36.245): test 2 3 ServiceProbe on example2.redhat.com (199.168.36.173): rhel2.1 test 4 ServiceProbe on example3.redhat.com (199.168.36.174): SSH 5 ServiceProbe on example4.redhat.com (199.168.36.175): HTTP The probe ID is the first number, while the probe name (as entered in the RHN website) is...
  • Page 184: Rhn-Catalog

    --commandline retrieves everything else, including alert thresholds and notification intervals and --dump methods. The command above will result in output similar to: 5 ServiceProbe on example4.redhat.com (199.168.36.175 linux:cpu usage Run as: Unix::CPU.pm --critical=90 --sshhost=199.168.36.175 --warn=70 --timeout=15 --sshuser=nocpulse --shell=SSHRemoteCommandShell --sshport=4545 Now that you have the ID, you use it with to examine the probe’s output.
  • Page 185 Chapter 7. Monitoring The above command requests the probe output for probeID 5, for all run levels, with a high level of verbosity. More specifically, you may provide the command parameters derived from rhn-catalog like so: rhn-runprobe 5 --log=all=4 --sshuser=nocpulse --sshport=4545 This yields verbose output depicting the probe’s attempted execution.
  • Page 186 Chapter 7. Monitoring...
  • Page 187: Unix Support Guide

    Chapter 8. UNIX Support Guide 8.1. Introduction This chapter documents the installation procedure for, and identifies differences in, Red Hat Network functionality when used to manage UNIX-based client systems. RHN offers UNIX support to help customers migrate from UNIX to Linux. Because of the limited scope of this task, the features offered for UNIX client management are not as comprehen- sive as those available for managing Red Hat Enterprise Linux systems.
  • Page 188: Included Features

    Chapter 8. UNIX Support Guide 8.1.3. Included Features The following features are included in the UNIX support service level as they exist within RHN: A Provisioning feature called Remote Command that enables users to schedule root-level • commands on any managed client through the Satellite’s website, if the client allows this action All Management-level functionality, such as system grouping, package profile compari- •...
  • Page 189: Excluded Features

    Chapter 8. UNIX Support Guide Note The following changes have been made to solaris2mpm 1. Generated files contain release info: name-version-release.arch.mpm 2. Patch clusters are now "exploded" and files are generated for each patch in the cluster as well as a top-level "meta" file for the cluster The second, , works like the standard...
  • Page 190: Satellite Server Preparation/Configuration

    Chapter 8. UNIX Support Guide 8.2. Satellite Server Preparation/Configuration Before configuring the UNIX clients, you will need to enable UNIX support. This can be accomplished one of two ways, depending on whether you have yet installed your Satellite server: 1. During the Satellite installation: Enable UNIX support on the Satellite by checking the "Enable Solaris Support"...
  • Page 191: Client System Preparation

    Chapter 8. UNIX Support Guide the navigation sidebar. In the screen that follows, check the "Enable Solaris Support" box, as pictured: Figure 8-2. Enabling UNIX Support After Satellite Installation 8.3. Client System Preparation Before your UNIX-based client systems benefit from Red Hat Network, they must be pre- pared for connection: 1.
  • Page 192: Installing Additional Packages

    Chapter 8. UNIX Support Guide 3. Finally, you must reconfigure the client applications to connect to the RHN Satellite Server. Once finished, your systems will be ready to begin receiving RHN updates. 8.3.1. Installing Additional Packages This section steps you through the process of getting RHN-required packages installed on your base operating system.
  • Page 193: Deploying Client Ssl Certificates

    2. Move the client SSL certificate to the RHN-specific directory for your UNIX variant. For Solaris, this can be accomplished with a command similar to: mv /path/to/RHN-ORG-TRUSTED-SSL-CERT /opt/redhat/rhn/solaris/usr/share/rhn/ When finished, the new client certificate will be installed in the appropriate directory for your UNIX system.
  • Page 194 Section 8.3.2 Deploying Client SSL Certificates, for example: sslCACert[comment]=The CA cert used to verify the ssl server sslCACert=/opt/redhat/rhn/solaris/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT 6. Finally, set the shell environment variables on the client to accommodate RHN- specific paths, commands, and libraries. You will need to set the library search path to include the directory.
  • Page 195: Registration And Updates

    Chapter 8. UNIX Support Guide 8.4. Registration and Updates Now that you have installed RHN-specific packages, implemented SSL, and reconfigured your client systems to connect to the RHN Satellite Server, you are ready to begin register- ing systems and obtaining updates. 8.4.1.
  • Page 196 Chapter 8. UNIX Support Guide ing systems use Errata Updates to associate upgrades with specific packages. In addition, Solaris uses answer files to automate interactive package installations, something Linux doesn’t understand, while Red Hat offers the concept of source packages. For this reason, this section seeks to highlight differences in using RHN tools on UNIX systems.
  • Page 197: Remote Commands

    Chapter 8. UNIX Support Guide 8.4.2.2. Updating From the Command Line Like the website, command line use of the Red Hat Update Agent is affected by the lim- itations of UNIX package management. That said, most core functions can still be accom- plished through the command.
  • Page 198: Enabling Commands

    UNIX variant. /etc/sysconfig/rhn/allowed-actions/ For instance, in Solaris, issue this command to create the directory: mkdir -p /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script To create the requisite file in Solaris, issue this command: touch /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script/run 8.5.2. Issuing Commands You may schedule a remote command in a variety of ways: on an individual system, on multiple systems at once, and to accompany a package action.
  • Page 199 Chapter 8. UNIX Support Guide action. Use the radio buttons at the top to determine whether the command should run be- fore or after the package action, establish the settings for the command, and click Schedule Package Install/Upgrade. Note that installing multiple packages that have different remote commands requires scheduling the installs separately or combining the commands into a single script.
  • Page 200 Chapter 8. UNIX Support Guide...
  • Page 201: Command Line Config Management Tools

    Appendix A. Command Line Config Management Tools In addition to the options provided in the RHN website, Red Hat Network offers two command line tools for managing a system’s configuration files: the Red Hat Network Configuration Client and the Red Hat Network Configuration Manager. There is a complementary Red Hat Network Actions Control tool that is used to enable and dis- able configuration management on client systems.
  • Page 202: Red Hat Network Configuration Client

    Appendix A. Command Line Config Management Tools Option Description Option Description --enable-deploy Allow rhncfg-client to deploy files. --enable-diff Allow rhncfg-client to diff files. --enable-upload Allow rhncfg-client to upload files. --enable-mtime-upload Allow rhncfg-client to upload mtime. --enable-all Allow rhncfg-client to do everything. --enable-run Enable script.run --disable-deploy...
  • Page 203: Listing Config Files

    Appendix A. Command Line Config Management Tools A.2.1. Listing Config Files To list the configuration files for the machine and the labels of the config channels contain- ing them, issue the command: rhncfg-client list The output resembles the following list: Config Channel File config-channel-17...
  • Page 204: Viewing Config Channels

    Appendix A. Command Line Config Management Tools A.2.3. Viewing Config Channels To view the labels and names of the config channels that apply to the system, issue the command: rhncfg-client channels You should see output resembling: Config channels: Label Name ----- ---- config-channel-17...
  • Page 205: Verifying Config Files

    Appendix A. Command Line Config Management Tools /usr/bin/diff: /home/test/blah/var/spool/aalib.rpm: No such file or directory A.2.5. Verifying Config Files To quickly determine if client configuration files are different than those associated with it via RHN, issue the command: rhncfg-client verify The output resembles the following: modified /etc/example-config.txt /var/spool/aalib.rpm The file...
  • Page 206: Creating A Config Channel

    Appendix A. Command Line Config Management Tools than root, you may have to make configuration changes within the file. The ~/.rhncfgrc session file is cached in to prevent logging in for every ~/.rhncfg-manager-session command. The default timeout for the Red Hat Network Configuration Manager is 30 minutes. To alter this, add the option and new value to the server.session_lifetime...
  • Page 207: Differentiating Between Latest Config Files

    Appendix A. Command Line Config Management Tools rhncfg-manager add /path/to/file --channel=channel-label In addition to the required channel label and the path to the file, you may use the available options for modifying the file during its addition. For instance, you may alter the path and file name by including the option in the command, like: --dest-file...
  • Page 208: Differentiating Between Various Versions

    Appendix A. Command Line Config Management Tools +++ /home/test/blah/hello_world.txt 2003-12-14 19:08:59.000000000 -0500 @@ -1 +1 @@ -foo +hello, world The following table lists the options available for rhncfg-manager diff Option Description -cCHANNEL, --channel=CHANNEL Get file(s) from this config channel -rREVISION, --revision=REVISION Use this revision -dDEST_FILE, Upload the file as this path...
  • Page 209: Downloading All Files In A Channel

    Appendix A. Command Line Config Management Tools +iD8DBQA9ZY6vse4XmfJPGwgRAsHcAJ9ud9dabUcdscdcqB8AZP7e0Fua0NmKsdhQCeOWHX +VsDTfen2NWdwwPaTM+S+Cow= +=Ltp2 +-----END PGP SIGNATURE----- The following table lists the options available for rhncfg-manager diff-revisions Option Description -cCHANNEL, --channel=CHANNEL Use this config channel -rREVISION, --revision=REVISION Use this revision -h, --help Show help message and exit Table A-6.
  • Page 210: Getting The Contents Of A File

    Appendix A. Command Line Config Management Tools A.3.6. Getting the Contents of a File To direct the contents of a particular file to stdout, issue the command: rhncfg-manager get --channel=channel-label /tmp/dest_path/example-config.txt You should see the contents of the file as output. A.3.7.
  • Page 211: Removing A File From A Channel

    Appendix A. Command Line Config Management Tools example-channel2 example-channel3 config-channel-14 config-channel-17 Note that this does not list channels. local_override server_import A.3.9. Removing a File from a Channel To remove a file from a channel, issue the command: rhncfg-manager remove --channel=channel-label /tmp/dest_path/example-config.txt If prompted for your RHN username and password, provide them.
  • Page 212: Determining The Number Of File Revisions

    Appendix A. Command Line Config Management Tools A.3.11. Determining the Number of File Revisions To find out how many revisions (revisions go from 1 to N where N is an integer greater than 0) of a file/path are in a channel, issue the following command: rhncfg-manager revisions channel-label /tmp/dest_path/example-config.txt The output resembles the following: Analyzing files in config channel example-channel \...
  • Page 213: Uploading Multiple Files At Once

    Appendix A. Command Line Config Management Tools A.3.13. Uploading Multiple Files at Once To upload multiple files to a config channel from local disk at once, issue the command: rhncfg-manager upload-channel channel-label --topdir=topdir The output resembles the following: Using config channel example-channel4 Uploading /tmp/ola_world.txt from blah4/tmp/ola_world.txt The following table lists the options available for rhncfg-manager upload-channel...
  • Page 214 Appendix A. Command Line Config Management Tools...
  • Page 215: Rhn Api Access

    (API) available. This interface can be found by clicking Help at the top-right corner of the RHN website, then clicking API in the left navigation bar. Or you may go directly to: https://rhn.redhat.com/rpc/api/. Use this URL for your XMLRPC server and your browser.
  • Page 216: Determining The Sid

    Appendix B. RHN API Access B.3. Determining the sid Several methods require a value for the , or server ID, parameter. Note that this is different from the . You may determine the of a machine in two different system_id ways.
  • Page 217 Appendix B. RHN API Access # http://www.xmlrpc.com/ # We use the Frontier modules, available from: # http://theoryx5.uwinnipeg.ca/mod_perl/cpan-search?dist=Frontier-RPC ############################################################################ ############################################################################ Defining an XMLRPC session. ############################################################################ # Define the host first. This will be the FQDN of your satellite system. my $HOST = ’satellite.server.yourdomain.com’; # Now we create the client object that will be used throughout the session.
  • Page 218 Appendix B. RHN API Access # This will probably be a pretty long list. my $packages = $client->call(’system.list_packages’, $session, $systemid); for my $package (@$packages) { print Dumper($package); # Additional system calls are described at: http://$HOST/rpc/api/system/...
  • Page 219: Probes

    Appendix C. Probes As described in Section 6.9 Monitoring — , Monitoring-entitled systems can have probes applied to them that constantly confirm their health and full operability. This appendix lists the available probes broken down by command group, such as Apache. Many probes that monitor internal system aspects (such as the Linux::Disk Usage probe) rather than external aspects (such as the Network Services::SSH probe) require the instal- lation of the Red Hat Network Monitoring Daemon (...
  • Page 220: Apache 1.3.X And 2.0.X

    Appendix C. Probes The probes that have run successfully without error. This is the desired state for all probes. Warning The probes that have crossed their WARNING thresholds. Critical The probes that have crossed their CRITICAL thresholds or reached a critical status by some other means.
  • Page 221: Apache::traffic

    Appendix C. Probes Data Transferred Per Child — Records data transfer information only on individual chil- • dren. A child process is one that is created from the parent process or another process. Data Transferred Per Slot — The cumulative amount of data transferred by a child pro- •...
  • Page 222: Apache::uptime

    Appendix C. Probes Traffic — The kilobytes per second of traffic the server has processed since the probe • last ran. directive in the file of the Web server must be set to ExtendedStatus httpd.conf On for this probe to function properly. Field Value Application Protocol*...
  • Page 223: Bea Weblogic 6.X And Higher

    Appendix C. Probes Field Value Port* Pathname* /server-status UserAgent* NOCpulse-ApacheUptime/1.0 Username Password Timeout* Table C-3. Apache::Uptime settings C.3. BEA WebLogic 6.x and higher The probes in this section (with the exception of JDBC Connection Pool) can be configured to monitor the properties of any BEA WebLogic 6.x and higher server (Administration or Managed) running on a given host, even in a clustered environment.
  • Page 224: Bea Weblogic::execute Queue

    Appendix C. Probes C.3.1. BEA WebLogic::Execute Queue The BEA WebLogic::Execute Queue probe monitors the WebLogic execute queue and provides the following metrics: Idle Execute Threads — The number of execution threads in an idle state. • Queue Length — The number of requests in the queue. •...
  • Page 225: Bea Weblogic::jdbc Connection Pool

    Appendix C. Probes Field Value SNMP Community String* public SNMP Port* SNMP Version* BEA Domain Admin Server BEA Server Name* myserver Critical Maximum Heap Free Warning Maximum Heap Free Warning Minimum Heap Free Critical Minimum Heap Free Table C-5. BEA WebLogic::Heap Free settings C.3.3.
  • Page 226: Bea Weblogic::server State

    Appendix C. Probes Field Value Critical Maximum Connections Warning Maximum Connections Critical Maximum Connection Rate Warning Maximum Connection Rate Critical Maximum Waiters Warning Maximum Waiters Table C-6. BEA WebLogic::JDBC Connection Pool settings C.3.4. BEA WebLogic::Server State The BEA WebLogic::Server State probe monitors the current state of a BEA Weblogic Web server.
  • Page 227: General

    Appendix C. Probes Execution Time Moving Average — A moving average of the execution time. • Execution Time Average — A standard average of the execution time. • Reload Rate — The number of times the specified servlet is reloaded per minute. •...
  • Page 228: General::remote Program With Data

    Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on rhnmd the monitored system to execute this probe. Field Value Command* OK Exit Status* Warning Exit Status* Critical Exit Status* Timeout Table C-9. General::Remote Program settings C.4.2.
  • Page 229: General::snmp Check

    Appendix C. Probes Field Value Command* OK Exit Status* Warning Exit Status* Critical Exit Status* Timeout Table C-10. General::Remote Program with Data settings C.4.3. General::SNMP Check The General::SNMP Check probe tests your SNMP server by specifying a single object identifier (OID) in dotted notation (such as 1.3.6.1.2.1.1.1.0) and a threshold as- sociated with the return value.
  • Page 230: General::udp Check

    Appendix C. Probes C.4.4. General::TCP Check The General::TCP Check probe tests your TCP server by verifying that it can connect to a system via the specified port number. It collects the following metric: Remote Service Latency — The time it takes in seconds for the TCP server to answer a •...
  • Page 231: General::uptime (Snmp)

    Appendix C. Probes Field Value Port* Send Expect Timeout* Critical Maximum Latency Warning Maximum Latency Table C-13. General::UDP Check settings C.4.6. General::Uptime (SNMP) The General::Uptime (SNMP) probe records the time since the device was last started. It uses the SNMP object identifier (OID) to obtain this value. The only error status it will return is UNKNOWN.
  • Page 232: Linux::cpu Usage

    Appendix C. Probes system. C.5.1. Linux::CPU Usage The Linux::CPU Usage probe monitors the CPU utilization on a system and collects the following metric: CPU Percent Used — The five-second average of the percent of CPU usage at probe • execution. Requirements —...
  • Page 233: Linux::disk Usage

    Appendix C. Probes Field Value Timeout* Critical Maximum KB read/second Warning Maximum KB read/second Warning Minimum KB read/second Critical Minimum KB read/second Critical Maximum KB written/second Warning Maximum KB written/second Warning Minimum KB written/second Critical Minimum KB written/second Table C-16. Linux::Disk IO Throughput settings C.5.3.
  • Page 234: Linux::inodes

    Appendix C. Probes Field Value Critical Minimum Space Available Table C-17. Linux::Disk Usage settings C.5.4. Linux::Inodes The Linux::Inodes probe monitors the specified file system and collects the following met- ric: Inodes — The percentage of inodes currently in use. • An inode is a data structure that holds information about files in a Linux file system.
  • Page 235: Linux::load

    Appendix C. Probes Field Value Interface* Timeout* Critical Maximum Input Rate Warning Maximum Input Rate Warning Minimum Input Rate Critical Minimum Input Rate Critical Maximum Output Rate Warning Maximum Output Rate Warning Minimum Output Rate Critical Minimum Output Rate Table C-19. Linux::Interface Traffic settings C.5.6.
  • Page 236: Linux::memory Usage

    Appendix C. Probes C.5.7. Linux::Memory Usage The Linux::Memory Usage probe monitors the memory on a system and collects the fol- lowing metric: RAM Free — The amount of free random access memory (RAM) in megabytes on a • system. You can also include the reclaimable memory in this metric by entering yes or no in the Include reclaimable memory field.
  • Page 237: Linux::process Count Total

    Appendix C. Probes Field Value Field Value Timeout* Critical Maximum Blocked Processes Warning Maximum Blocked Processes Critical Maximum Defunct Processes Warning Maximum Defunct Processes Critical Maximum Stopped Processes Warning Maximum Stopped Processes Critical Maximum Sleeping Processes Warning Maximum Sleeping Processes Critical Maximum Child Processes Warning Maximum Child Processes Table C-22.
  • Page 238: Linux::process Health

    Appendix C. Probes C.5.10. Linux::Process Health The Linux::Process Health probe monitors user-specified processes and collects the fol- lowing metrics: CPU Usage — The CPU usage rate for a given process in milliseconds per second. This • metric reports the column of output, which is the cumulative CPU time used by time the process.
  • Page 239: Linux::process Running

    Appendix C. Probes Field Value Critical Maximum Physical Memory Used Warning Maximum Physical Memory Used Critical Maximum Virtual Memory Used Warning Maximum Virtual Memory Used Table C-24. Linux::Process Health settings C.5.11. Linux::Process Running The Linux::Process Running probe verifies that the specified process is functioning prop- erly.
  • Page 240: Linux::swap Usage

    Appendix C. Probes C.5.12. Linux::Swap Usage The Linux::Swap Usage probe monitors the swap partitions running on a system and re- ports the following metric: Swap Free — The percent of swap memory currently free. • Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on rhnmd the monitored system to execute this probe.
  • Page 241: Linux::users

    Appendix C. Probes Field Value Local IP address filter pattern list Local port number filter Remote IP address filter pattern list Remote port number filter Timeout* Critical Maximum Total Connections Warning Maximum Total Connections Critical Maximum TIME_WAIT Connections Warning Maximum TIME_WAIT Connections Critical Maximum CLOSE_WAIT Connections Warning Maximum CLOSE_WAIT Connections...
  • Page 242: Linux::virtual Memory

    Appendix C. Probes Field Value Field Value Timeout* Critical Maximum Users Warning Maximum Users Table C-28. Linux::Users settings C.5.15. Linux::Virtual Memory The Linux::Virtual Memory probe monitors the total system memory and collects the fol- lowing metric: Virtual Memory — The percent of total system memory - random access memory •...
  • Page 243: Logagent::log Pattern Match

    Appendix C. Probes C.6.1. LogAgent::Log Pattern Match The LogAgent::Log Pattern Match probe uses regular expressions to match text located within the monitored log file and collects the following metrics: Regular Expression Matches — The number of matches that have occurred since the •...
  • Page 244: Logagent::log Size

    Appendix C. Probes Field Value Critical Maximum Matches Warning Maximum Matches Warning Minimum Matches Critical Minimum Matches Critical Maximum Match Rate Warning Maximum Match Rate Warning Minimum Match Rate Critical Maximum Match Rate Table C-30. LogAgent::Log Pattern Match settings C.6.2. LogAgent::Log Size The LogAgent::Log Size probe monitors log file growth and collects the following metrics: Size —...
  • Page 245: Mysql 3.23 - 3.33

    Appendix C. Probes Field Value Critical Maximum Output Rate Warning Maximum Output Rate Warning Minimum Output Rate Critical Minimum Output Rate Critical Maximum Lines Warning Maximum Lines Warning Minimum Lines Critical Minimum Lines Critical Maximum Line Rate Warning Maximum Line Rate Warning Minimum Line Rate Critical Minimum Line Rate Table C-31.
  • Page 246: Mysql::opened Tables

    Appendix C. Probes Field Value Database* mysql Timeout Table C-32. MySQL::Database Accessibility settings C.7.2. MySQL::Opened Tables The MySQL::Opened Tables probe monitors the MySQL server and collects the following metric: Opened Tables — The tables that have been opened since the server was started. •...
  • Page 247: Mysql::query Rate

    Appendix C. Probes Field Value Password MySQL Port* 3306 Timeout Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects Critical Minimum Open Objects Table C-34. MySQL::Open Tables settings C.7.4. MySQL::Query Rate The MySQL::Query Rate probe monitors the MySQL server and collects the following metric: Query Rate —...
  • Page 248: Network Services

    Appendix C. Probes Threads Running — The total number of running threads within the database. • Field Value Username Password MySQL Port* 3306 Timeout Critical Maximum Threads Running Warning Maximum Threads Running Warning Minimum Threads Running Critical Minimum Threads Running Table C-36.
  • Page 249: Network Services::ftp

    Appendix C. Probes Field Value Timeout* Critical Maximum Query Time Warning Maximum Query Time Table C-37. Network Services::DNS Lookup settings C.8.2. Network Services::FTP The Network Services::FTP probe uses network sockets to test FTP port availability. It collects the following metric: Remote Service Latency —...
  • Page 250: Network Services::mail Transfer (Smtp)

    Appendix C. Probes Remote Service Latency — The time it takes in seconds for the IMAP server to answer • a connection request. The required Expect value is the string to be matched against after a successful connec- tion is made to the IMAP server. If the expected string is not found, the probe returns a CRITICAL state.
  • Page 251: Network Services::pop Mail

    Appendix C. Probes average against the Warning and Critical threshold levels. The required Packets to send value allows you to control how many ICMP ECHO packets are sent to the system. This probe collects the following metrics: Round-Trip Average — The time it takes in milliseconds for the ICMP ECHO packet to •...
  • Page 252: Network Services::remote Ping

    Appendix C. Probes Remote Service Latency — The time it takes in seconds for the POP server to answer a • connection request. The required Expect value is the string to be matched against after a successful connection is made to the POP server. The probe looks for the string in the first line of the response from the system.
  • Page 253: Network Services::rpcservice

    Appendix C. Probes Field Value Field Value IP Address* Packets to send* Timeout* Critical Maximum Round-Trip Average Warning Maximum Round-Trip Average Critical Maximum Packet Loss Warning Maximum Packet Loss Table C-43. Network Services::Remote Ping settings C.8.8. Network Services::RPCService The Network Services::RPCService probe tests the availability of remote procedure call (RPC) programs on a given IP address.
  • Page 254: Network Services::secure Web Server (Https)

    Appendix C. Probes Field Value Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C-44. Network Services::RPCService settings C.8.9. Network Services::Secure Web Server (HTTPS) The Network Services::Secure Web Server (HTTPS) probe determines the availability of the secure Web server and collects the following metric: Remote Service Latency —...
  • Page 255: Network Services::web Server (Http)

    Appendix C. Probes C.8.10. Network Services::SSH The Network Services::SSH probe determines the availability of SSH on the specified port and collects the following metric: Remote Service Latency — The time it takes in seconds for the SSH server to answer a •...
  • Page 256: Oracle 8I And 9I

    Appendix C. Probes Field Value URL Path Virtual Host Expect Header HTTP/1 Expect Content UserAgent* NOCpulse-check_http/1.0 Username Password Timeout* HTTP Port* Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C-47. Network Services::Web Server (HTTP) settings C.9. Oracle 8i and 9i The probes in this section may be applied to instances of the Oracle database matching the versions supported.
  • Page 257: Oracle::active Sessions

    Appendix C. Probes Finally, customers using these Oracle probes against a database using Oracle’s Multi- Threaded Server (MTS) must contact Red Hat support to have entries added to the RHN Server’s /etc/hosts file to ensure that the DNS name is resolved correctly. C.9.1.
  • Page 258: Oracle::blocking Sessions

    Appendix C. Probes Field Value Oracle Password* Oracle Port* 1521 Timeout* Table C-49. Oracle::Availability settings C.9.3. Oracle::Blocking Sessions The Oracle::Blocking Sessions probe monitors an Oracle instance and collects the follow- ing metric: Blocking Sessions — The number of sessions preventing other sessions from commit- •...
  • Page 259: Oracle::client Connectivity

    Appendix C. Probes Consistent Gets — The number of accesses made to the block buffer to retrieve data in • a consistent mode. Physical Reads — The cumulative number of blocks read from disk. • Buffer Cache Hit Ratio — The rate at which the database goes to the buffer instead of •...
  • Page 260: Oracle::data Dictionary Cache

    Appendix C. Probes Field Value Oracle Port* 1521 ORACLE_HOME* /opt/oracle Expected DB Name* Timeout* Table C-52. Oracle::Client Connectivity settings C.9.6. Oracle::Data Dictionary Cache The Oracle::Data Dictionary Cache probe computes the Data Dictionary Cache Hit Ra- tio so as to optimize the SHARED_POOL_SIZE in .
  • Page 261: Oracle::disk Sort Ratio

    Appendix C. Probes C.9.7. Oracle::Disk Sort Ratio The Oracle::Disk Sort Ratio probe monitors an Oracle database instance and collects the following metric: Disk Sort Ratio — The rate of Oracle sorts that were too large to be completed in mem- •...
  • Page 262: Oracle::index Extents

    Appendix C. Probes Field Value Timeout* Critical Maximum Idle Sessions Warning Maximum Idle Sessions Table C-55. Oracle::Idle Sessions settings C.9.9. Oracle::Index Extents The Oracle::Index Extents probe monitors an Oracle instance and collects the following metric: Allocated Extents — The number of allocated extents for any index. •...
  • Page 263: Oracle::library Cache

    Appendix C. Probes C.9.10. Oracle::Library Cache The Oracle::Library Cache probe computes the Library Cache Miss Ratio so as to optimize the SHARED_POOL_SIZE in . It collects the following metrics: init.ora Library Cache Miss Ratio — The rate at which a library cache pin miss occurs. This •...
  • Page 264: Oracle::redo Log

    Appendix C. Probes Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* Critical Maximum Active Locks Warning Maximum Active Locks Table C-58. Oracle::Locks settings C.9.12. Oracle::Redo Log The Oracle::Redo Log probe monitors an Oracle database instance and collects the follow- ing metrics: Redo Log Space Request Rate —...
  • Page 265: Oracle::table Extents

    Appendix C. Probes Field Value Critical Maximum Redo Buffer Allocation Retry Rate Warning Maximum Redo Buffer Allocation Retry Rate Table C-59. Oracle::Redo Log settings C.9.13. Oracle::Table Extents The Oracle::Table Extents probe monitors an Oracle database instance and collects the following metrics: Allocated Extents-Any Table —...
  • Page 266: Oracle::tablespace Usage

    Appendix C. Probes Field Value Critical Maximum Allocated Extents Warning Maximum Allocated Extents Critical Maximum Available Extents Warning Maximum Available Extents Table C-60. Oracle::Table Extents settings C.9.14. Oracle::Tablespace Usage The Oracle::Tablespace Usage probe monitors an Oracle database instance and collects the following metric: Available Space Used —...
  • Page 267: Oracle::tns Ping

    Appendix C. Probes C.9.15. Oracle::TNS Ping The Oracle::TNS Ping probe determines if an Oracle listener is alive and collects the fol- lowing metric: Remote Service Latency — The time it takes in seconds for the Oracle server to answer • a connection request.
  • Page 268: Rhn Satellite Server::execution Time

    Appendix C. Probes Field Value Critical Maximum Space Used Warning Maximum Space Used Critical Maximum Space Available Warning Maximum Space Available Table C-63. RHN Satellite Server::Disk Space settings C.10.2. RHN Satellite Server::Execution Time The RHN Satellite Server::Execution Time probe monitors the execution time for probes run from a Satellite and collects the following metric: Probe Execution Time Average —...
  • Page 269: Rhn Satellite Server::latency

    Appendix C. Probes Field Value Critical Maximum Output Rate Table C-65. RHN Satellite Server::Interface Traffic settings C.10.4. RHN Satellite Server::Latency The RHN Satellite Server::Latency probe monitors the latency of probes on a Satellite and collects the following metric: Probe Latency Average — The lag in seconds between the time a probe becomes ready •...
  • Page 270: Rhn Satellite Server::probe Count

    Appendix C. Probes Table C-67. RHN Satellite Server::Load settings C.10.6. RHN Satellite Server::Probe Count The RHN Satellite Server::Probe Count probe monitors the number of probes on a Satellite and collects the following metric: Probes — The number of individual probes running on a Satellite. •...
  • Page 271: Rhn Satellite Server::processes

    Appendix C. Probes Field Value Critical Maximum Child Processes Warning Maximum Child Processes Critical Maximum Defunct Processes Warning Maximum Defunct Processes Critical Maximum Stopped Processes Warning Maximum Stopped Processes Critical Maximum Sleeping Processes Warning Maximum Sleeping Processes Table C-69. RHN Satellite Server::Process Counts settings C.10.8.
  • Page 272: Rhn Satellite Server::process Running

    Appendix C. Probes Threads — The number of running threads for a given process. A thread is the basic unit • of CPU utilization, and consists of a program counter, a register set, and a stack space. A thread is also called a lightweight process. Physical Memory Used —...
  • Page 273: Rhn Satellite Server::swap

    Appendix C. Probes Field Value Command Name Process ID (PID) file Critical Number Running Maximum Critical Number Running Minimum Table C-72. RHN Satellite Server::Process Running settings C.10.11. RHN Satellite Server::Swap The RHN Satellite Server::Swap probe monitors the percent of free swap space available on a Satellite.
  • Page 274 Appendix C. Probes...
  • Page 275: Glossary

    An Errata Alert that pertains to a bug fix. Bugzilla Bugzilla is an online application (http://www.redhat.com/bugzilla) that allows users to communicate directly with the developers. From Bugzilla, users can submit bug reports and feature requests for Red Hat Enterprise Linux and related open source...
  • Page 276 Glossary Channel A channel is a list of packages. Channels are used to choose packages to be installed from client systems. Every client system must be subscribed to one Base Channel and can be subscribed to one or more Child Channel . Child Channel A child channel is a Channel associated with a Base Channel but contains extra packages.
  • Page 277 Errata, Bugzilla bug IDs, relevant releases/architectures, solutions including required RPMs, and MD5 checksums for verification. Errata are also available at http://www.redhat.com/errata/. Each RHN Errata Alert is based on the Red Hat En- terprise Linux Errata List. Security issues and bug fixes are submitted by Red Hat engineers as well as the Linux community through Bugzilla which generates a bug report for each issue.
  • Page 278 Glossary Management One of the RHN service level offerings. It has more features than the Update service level, including user management, system groups, and enhanced system details. Notification Method An email address to which RHN Monitoring messages will be sent. Organization Administrator Organization Administrator are sets of users that have the highest level of control over an organization’s Red Hat Network account.
  • Page 279 Glossary Probe State The measure of a probe’s adherence to its defined criteria. States include: OK, Warn- ing, Critical, Pending, Unknown Probe Suite collection or group of RHN Monitoring Probes. Provisioning One of the RHN service level offerings. It has more features than the Management service level, including kickstarting, reconfiguring, tracking, and reverting systems.
  • Page 280 Glossary Red Hat Update Agent The RHN client application ( ) that allows users to retrieve and install all up- up2date dated packages for the client system on which the application is run. Use the Red Hat Update Agent Configuration Tool to configure its preferences, including whether to install the packages after they are downloaded.
  • Page 281 Glossary Software Manager The name of the first Service Level offering for Red Hat Network. Software Manager is now known as RHN Update . System Directory The System Directory section of Red Hat Network allows an organization to divide its client systems into system groups.
  • Page 282 Glossary...
  • Page 283: Index

    Index child, 121 entitling, 125 errata, 124 list of, 121 packages, 124 account relevant, 121 deactivate, 74 retired, 122 action Software and Configuration Files, 120 completed systems, 138 Channels and Packages details, 138 Channel List, 121 failed systems, 139 child channel, 121 in progress systems, 139 activation key, 104 client applications...
  • Page 284 getting started, 6 GNU Privacy Guard, 6 delete user (RHN Satellite Server only), 141 deleting a system, 80 Digital Certificate, 6 disable user, 141 download ISO images, 125 hardware profile Updating on server, 81 Help Desk, 154 HTTP Proxy, 46 email address change, 74 changing, 142...
  • Page 285 OK, 148 Pending, 147 Linux prerequisites, 157 CPU Usage, 216 Scout Config Push, 152 Disk IO Throughput, 216 service level, 4 Disk Usage, 217 Status, 146 Inodes, 218 Unknown, 147 Interface Traffic, 218 Warning, 147 Load, 219 MySQL , 161 Memory Usage, 220 Database Accessibility, 229 probes...
  • Page 286 Remote Program with Data, 212 SNMP Check, 213 Oracle TCP Check, 214 Active Sessions, 241 UDP Check, 214 Availability, 241 Uptime (SNMP), 215 Blocking Sessions, 242 Linux Buffer Cache, 242 CPU Usage, 216 Client Connectivity, 243 Disk IO Throughput, 216 Data Dictionary Cache, 244 Disk Usage, 217 Disk Sort Ratio, 245...
  • Page 287 Buffer Cache, 242 Provisioning Client Connectivity, 243 service level, 3 Data Dictionary Cache, 244 proxy server Disk Sort Ratio, 245 with Red Hat Network Alert Notification Idle Sessions, 245 Tool, 46 Index Extents, 246 with Red Hat Network Registration Client, Library Cache, 247 Locks, 247 with Red Hat Update Agent, 34...
  • Page 288 initial description, 2 as part of an organization, 56 troubleshooting, 44 Configuration, 49 using to apply Errata Updates, 119 Email notification, 54 viewing status, 44 Hardware System Profile, 57 Red Hat Network Monitoring Daemon Password, 54 (rhnmd) monitoring daemon, 158 RPM Package List, 58 installation, 159 Software System Profile, 58...
  • Page 289 complete description, 9 editing details, 94 list of, 91 viewing details, 93 system group list status, 92 Schedule, 135 System Groups Scheduled Actions Action Details, 138 assigning and removing, 87 Actions List, 138 joining and leaving, 87 Archived Actions, 137 System Group List, 91 Completed Actions, 137 system list, 77...
  • Page 290 Errata Search, 120 Help, 154 UNIX variants kickstart profiles, 107 (see supported) logging in, 70 unsubscribe to channel, 121 Monitoring, 145 Update navigation bar, 65 service level, 2 overview, 65 updating Purchase History, 75 via command line, 181 Relevant Errata, 117 via website, 180 Schedule, 135 user...

Table of Contents