Page 1 Red Hat Network 4.1.0 Reference Guide...
Page 2 All other trademarks referenced herein are the property of their respective owners. The GPG ﬁngerprint 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......................2 1.3. Provisioning ......................3 1.4. Monitoring ......................4 1.5.
Page 4 5. Red Hat Network Registration Client ................49 5.1. Conﬁguring 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 Proﬁle ................56 5.4.1. Hardware System Proﬁle ..............56 5.4.2.
Page 5 6.6.1. Software Channels .................129 6.6.2. Channel Entitlements ..............133 6.6.3. Download Software................133 6.6.4. Package Search ................134 6.6.5. Manage Software Channels ............134 6.6.6. Manage Conﬁg Channels — ..........136 6.7. Schedule ......................144 6.7.1. Pending Actions ................144 6.7.2. Failed Actions ................145 6.7.3. Completed Actions.................145 6.7.4.
Page 6 6.11.14. Release Notes................164 6.11.15. Get RHN Software ..............164 7. Monitoring ........................165 7.1. Prerequisites ....................165 7.2. Red Hat Network Monitoring Daemon ( ) ........166 rhnmd 7.2.1. Probes requiring the daemon ............166 7.2.2. Installing the Red Hat Network Monitoring Daemon....167 7.2.3. Conﬁguring SSH................167 7.2.4.
Page 7 A. Command Line Conﬁg Management Tools ............197 A.1. Red Hat Network Actions Control ............197 A.1.1. General command line options .............197 A.2. Red Hat Network Conﬁguration Client ...........198 A.2.1. Listing Conﬁg Files...............198 A.2.2. Getting a Conﬁg File..............199 A.2.3. Viewing Conﬁg Channels .............200 A.2.4.
Page 8 C.4.2. General::Remote Program with Data ..........224 C.4.3. General::SNMP Check ..............225 C.4.4. General::TCP Check ..............225 C.4.5. General::UDP Check ..............226 C.4.6. General::Uptime (SNMP) .............227 C.5. Linux ......................227 C.5.1. Linux::CPU Usage ................228 C.5.2. Linux::Disk IO Throughput ............228 C.5.3. Linux::Disk Usage.................229 C.5.4. Linux::Inodes ................230 C.5.5.
Page 9 C.9.4. Oracle::Buffer Cache..............254 C.9.5. Oracle::Client Connectivity ............255 C.9.6. Oracle::Data Dictionary Cache .............256 C.9.7. Oracle::Disk Sort Ratio ..............256 C.9.8. Oracle::Idle Sessions ..............257 C.9.9. Oracle::Index Extents ..............258 C.9.10. Oracle::Library Cache ..............258 C.9.11. Oracle::Locks ................259 C.9.12. Oracle::Redo Log ................260 C.9.13. Oracle::Table Extents ..............261 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 ﬁle 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 ﬁnd it? Have you ever tried to ﬁnd an RPM through an Internet search engine or an RPM repository and been linked to an unknown site? Have you ever tried to ﬁnd an RPM but instead found only source ﬁles 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 following services: 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 ﬁelds. On the Create a Red Hat Login page, click Create a new Business Login. After creating a business account, you may add users within your organization to it.
Page 20: Monitoring
Chapter 1. Red Hat Network Overview Like Management, Provisioning is based upon an organization. It takes this concept a step further by enabling customers with Provisioning entitlements to kickstart, reconﬁg- ure, track, and revert systems on the ﬂy. In addition to all of the features mentioned in lower service levels, Provisioning provides: Kickstarting —...
Page 21: Errata Notiﬁcations And Scheduled Package Installations
RPM packages are signed with Red Hat’s GNU Privacy Guard (GPG) signature to ensure authenticity. Red Hat Network incorporates the following security measures: 1. Your System Proﬁle, available at http://rhn.redhat.com, is accessible only with an RHN-veriﬁed username and password.
Page 22: Before You Begin
Chapter 1. Red Hat Network Overview 2. A Digital Certiﬁcate 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. The ﬁle is only readable by the root user on the client system. 3.
Page 23 Chapter 1. Red Hat Network Overview 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 Proﬁles, 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 conﬁgured package directory. --tmpdir=directory The default location is . This /var/spool/up2date option is useful if you do not have enough space in the conﬁgured location. Specify an alternate RPM database to use temporarily. --dbpath=dir Table 2-1.
Page 28 Chapter 2. Red Hat Update Agent Figure 2-1. Conﬁgure 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 Proﬁle. 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 Proﬁle, 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 ﬁeld. 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 Proﬁle consists of a list of RPM packages for which you wish to receive notiﬁcations. 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 Proﬁle is sent.
Page 36: Channels
Chapter 2. Red Hat Update Agent Figure 2-7. Sending System Proﬁle 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 ﬁnished 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 Brieﬂy 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 conﬁguration option Do not install packages after retrieval. Install all available packages from a given channel --installall= < channel-label > Only add packages to the database and do not --justdb install them.
Page 47 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: Installing The Red Hat Gpg Key
(as root): /usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY download ﬁrst, 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 bsV7QdSGqBk3snNOizmFj543RaHyEbnwKWbNADhujWMeUAxN+7Q8UmVkIEhhdCwg SW5jLiAoU2VjdXJpdHkgUmVzcG9uc2UgVGVhbSkgPHNlY2FsZXJ0QHJlZGhhdC5j b20+iFcEExECABcFAj3GczYFCwcKAwQDFQMCAxYCAQIXgAAKCRBeVICDZQ1YghAU AJoCeQfuMR2dKyLft/10O6qUs+MNLQCggJgdO8MUO2y11TWID3XOYgyQG+2InAQT AQIABgUCPtyYpQAKCRDurUz9SaVj2e97A/0b2s7OhhAMljNwMQS4I2UWVGbgtxdu D+yBcG/3mwL76MJVY7aX+NN/tT9yDGU+FSiQZZCL/4OFOHMvjpcDqfJY+zpTlBii ZMAPJWTs2bB+0QaXxUgWlwW84GVf2rA6RSbvMLTbDjTH8t7J1RGP9zAqu8SgraTA QbQdao6TNxVt+ohGBBMRAgAGBQI+3LjCAAoJECGRgM3bQqYOf5MAoIjiJDe+hDOj 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 ﬁle 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 your System Proﬁle is not updated automatically. You must send your updated System Proﬁle to the RHN Servers. To synchronize the RPM package list on your local system and on Red Hat Network, run the command: up2date -p After running this command, your RHN System Proﬁle reﬂects the latest software versions...
Page 51 Chapter 2. Red Hat Update Agent Enable HTTP Proxy option and type your proxy server in the text ﬁeld with the for- mat http://HOST:PORT. For example, to use the proxy server squid.mysite.org on port 3128, you would enter squid.mysite.org:3128 in the text ﬁeld. Additionally, if your proxy server requires a username and password, select the Use Authentication op- tion and enter your username and password in the respective text ﬁelds.
Page 52 Chapter 2. Red Hat Update Agent Warning You must use Red Hat Update Agent Version 2.5.4 or higher to upgrade your kernel automatically. Red Hat Update Agent will install the updated kernel and conﬁgure LILO or GRUB to boot the new kernel the next time the system is rebooted. Figure 2-17.
Page 53 Chapter 2. Red Hat Update Agent The following installation options are conﬁgurable (see Figure 2-17): Use GPG to verify package integrity — before installing packages, verify Red Hat’s • GPG signature (highly recommended for security reasons) After installation, keep binary packages on disk — save binary packages in the de- •...
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 conﬁgure the settings used by the Red Hat Update Agent and store them in the conﬁguration ﬁle /etc/sysconfig/rhn/up2date To run the command line version of the Red Hat Update Agent Conﬁguration 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 speciﬁc 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.6.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 notiﬁcations. 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 Notiﬁcation Tool
Chapter 4. Red Hat Network Alert Notiﬁcation Tool The Red Hat Network Alert Notiﬁcation Tool is a notiﬁer 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 Notiﬁcation Tool Figure 4-2. HTTP Proxy Conﬁguration If your network connection requires you to use an HTTP Proxy Server to make HTTP connections, on the Proxy Conﬁguration screen, type your proxy server in the text ﬁeld with the format HOST:PORT.
Page 63: Notiﬁcation Icons
Chapter 4. Red Hat Network Alert Notiﬁcation Tool 4.2. Notiﬁcation 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 Notiﬁcation 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 Proﬁle. 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 conﬁguration 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 conﬁgured 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 proﬁle 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 Proﬁle.
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 Proﬁle, 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 Proﬁle.
Page 72: Registering A System Proﬁle
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 Proﬁle 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 Proﬁle
Chapter 5. Red Hat Network Registration Client Figure 5-8. System Proﬁle - Hardware 5.4.2. Software System Proﬁle The software System Proﬁle consists of a list of RPM packages for which you wish to receive notiﬁcations. 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 Proﬁle omits this information from your System Proﬁle.
Page 76: Finishing Registration
Chapter 5. Red Hat Network Registration Client Choose which packages to exclude, if any, from the System Proﬁle, and click Next to continue with the registration process. Figure 5-11. Choose which RPM Packages to Exclude from System Proﬁle 5.5. Finishing Registration As seen in Figure 5-12, the last step of registration is to conﬁrm that you want to send your System Proﬁle to the Red Hat Network.
Page 77 Chapter 5. Red Hat Network Registration Client Figure 5-12. Finished Collecting Information for System Proﬁle Figure 5-13 shows the progress bar displayed while your proﬁle is sent. This process may take some time depending on your connection speed. Figure 5-13. Send System Proﬁle to Red Hat Network The Red Hat Network Registration Client displays the Registration Finished screen (Figure 5-14 once your System Proﬁle has been sent successfully.
Page 78: Entitling Your System
Update 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 To change the entitlement level of a system or systems, check the box to the left of the systems and click the appropriate button for the desired entitlement level. Note that you must apply a Management entitlement to a system before you can add a Provisioning enti- tlement.
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 speciﬁc 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 speciﬁed 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 notiﬁcations regarding systems. • Probe Status — — View probes by state. • Notiﬁcation — — 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 This page contains important information about your systems, including summaries of system status, actions, and Errata Alerts. If you are new to the RHN website, it is recommended that you read Section 6.1 Navigation to become familiar with the layout and symbols used throughout the website.
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...
Page 90: Your Preferences
Chapter 6. Red Hat Network Website it actually contains. Replace the asterisks in the Password and Password Conﬁrmation text ﬁelds with your new password. 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 modiﬁed, make the changes, and click Update Address.
Page 91: Locale Preferences
Chapter 6. Red Hat Network Website this checkbox, you must identify each system to be included in this summary email. (By default, all Management and Provisioning systems are included in the summary.) This can be done either individually through the System Details page or for multiple systems at once through the System Set Manager interface.
Page 92 Chapter 6. Red Hat Network Website Provisioning — offers the highest level of functionality. It should be used to provision • multiple systems that will need to be re-installed and reconﬁgured regularly. The Provi- sioning offering provides tools for kickstarting machines, managing their conﬁguration ﬁles, conducting snapshot rollbacks, and inputting searchable custom system informa- tion, as well as all of the functionality included in the Management service level.
Page 93: Systems
Chapter 6. Red Hat Network Website As the title suggests, this page provides links to the main Red Hat site, from which you can renew or purchase entitlements. The Red Hat Renewal Center can renew both your Red Hat Enterprise Linux subscription and your Red Hat Network entitlements. The Red Hat Store can provide additional entitlements.
Page 94 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 identiﬁes group status and displays the number of systems contained.
Page 95: 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 the •...
Page 96 Chapter 6. Red Hat Network Website Important If the RHN website identiﬁes package updates for the system, yet the Red Hat Update Agent responds with "Your system is fully updated" when run, a conﬂict likely exists in the system’s package proﬁle or in the conﬁguration ﬁle.
Page 97: 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 98 Chapter 6. Red Hat Network Website Software • Conﬁguration • Provisioning — • Monitoring — • Groups • Events • The following sections discuss these tabs and their sub-tabs in detail. 6.4.2.8.1. System Details ⇒ Details This page is not accessible from any of the standard navigation bars. However, clicking on the name of a system anywhere in the web interface brings you to this page.
Page 99 Chapter 6. Red Hat Network Website the ﬁle does not match the value listed in the proﬁle, the proﬁle is not the most recent one and may be removed. Hostname The hostname as deﬁned by the client system. This information is often found in for Red Hat Enterprise Linux systems.
Page 100 Chapter 6. Red Hat Network Website de-select Auto Errata Update from the System Details ⇒ Details ⇒ Properties subtab. Locking a system can help to prevent you from accidentally making any changes to a system until you are ready to do so. For example, the system may be a production system that you do not wish to receive updates or new packages until you decide to unlock it.
Page 101 Chapter 6. Red Hat Network Website Note The ﬁnal link under Subscribed Channels is the Alter Channel subscriptions link. Click on this link to select from the available base and child channels for this system. When ﬁnished making selections, click the Change Subscriptions button to conﬁrm the changes.
Page 102 Chapter 6. Red Hat Network Website Proﬁle Name By default, this is the hostname of the system. You can however alter the proﬁle name to anything that allows you to distinguish this proﬁle from others. Base Entitlement Select a base channel for the system from the available base entitlements. Add-on entitlements If available, apply a Monitoring or Provisioning entitlement to the system.
Page 103 Chapter 6. Red Hat Network Website 6.4.2.8.1.3. System Details ⇒ Details ⇒ Remote Command — This subtab allows you to run a remote command on the system if the system possesses a Provisioning entitlement. Before doing so, you must ﬁrst conﬁgure the system to accept such commands.
Page 104 Chapter 6. Red Hat Network Website RHN settings. For this reason, you should not regenerate, delete, or use this key (with ) while a proﬁle-based kickstart is in progress. If you do, the kickstart will fail. rhnreg_ks 6.4.2.8.1.5. System Details ⇒ Details ⇒ Hardware This subtab provides detailed information about the system, including networking, BIOS, storage, and other devices.
Page 105 Chapter 6. Red Hat Network Website 6.4.2.8.1.9. System Details ⇒ Details ⇒ Satellite Displays the certiﬁcate of an active Red Hat Network. You can deactivate an old certiﬁcate here and upload a new one if necessary. This tab requires a Provisioning entitlement. For detailed information on activating a Satellite, refer to the RHN Satellite Installation Guide.
Page 106 Chapter 6. Red Hat Network Website Package List button on the bottom right-hand corner of this page. The next time the RHN Daemon connects to RHN, it updates your System Proﬁle with the latest list of installed packages. List/Remove Lists installed packages from the system’s software System Proﬁle and enables you to remove them.
Page 107 Chapter 6. Red Hat Network Website of the compared proﬁle. Note that this action may delete packages on the system not in the proﬁle, as well as install packages from the proﬁle. To install speciﬁc packages, select the checkboxes of packages from the proﬁle. To remove speciﬁc packages al- ready installed on the system itself, select the checkboxes of packages showing a difference of This system only.
Page 108 Chapter 6. Red Hat Network Website 6.4.2.8.3.1. System Details ⇒ Conﬁguration ⇒ Overview This subtab provides access to the conﬁguration statistics of your system and to the most common tasks used to manage conﬁguration ﬁles. You may change the settings listed under Conﬁguration Stats by clicking on the blue text for that setting.
Page 109 Chapter 6. Red Hat Network Website then unsubscribing from the channel providing the ﬁle will mean that the ﬁle is no longer managed (though it will not remove the ﬁle from the system). 6.4.2.8.3.3. System Details ⇒ Conﬁguration ⇒ Diff This subtab compares a conﬁguration ﬁle as stored on the Satellite with the ﬁle as it exists on the client.
Page 110 Chapter 6. Red Hat Network Website your systems. To add ﬁles, click the import new ﬁles link, enter the path to the ﬁle on you local system, and click the Add button. Select the Import Files button to conﬁrm. 6.4.2.8.4. System Details ⇒ Provisioning — This tab and its subtabs allow you to schedule and monitor kickstarts and to return your system to a previous state.
Page 111 Chapter 6. Red Hat Network Website 6.4.2.8.4.2. System Details ⇒ Provisioning ⇒ Snapshots — Snapshots enable you to roll back the system’s package proﬁle, conﬁguration ﬁles, and RHN settings. Snapshots are captured whenever an action takes place on a Provisioning- entitled system.
Page 112 Chapter 6. Red Hat Network Website To add a probe to the system, click the create new probe link at the top-right corner of the page and complete the ﬁelds on the following page. Refer to Section 7.5.1 Managing Probes for detailed instructions. Once the probe has been added, you must reconﬁgure your Monitoring infrastructure to recognize it.
Page 113: System Groups
Chapter 6. Red Hat Network Website 6.4.2.8.7.1. System Details ⇒ Events ⇒ Pending Lists events that are scheduled but have not begun. A prerequisite action must complete successfully before a given action is attempted. If an action has a prerequisite, no check- box is available to cancel that action.
Page 114 Chapter 6. Red Hat Network Website 4. Assign system group permissions to users. (Refer to Section 6.8 Users — As shown in Figure 6-8, the System Groups list displays all of your system groups. Figure 6-8. System Group List The System Groups list contains several columns for each group: Select —...
Page 115: Creating Groups
Chapter 6. Red Hat Network Website System Group Details page. Refer to Section 6.4.3.3 System Group Details — more information. The status icons call for differing degrees of attention: — All systems within group are up-to-date • — Critical Errata available, update strongly recommended •...
Page 116 Chapter 6. Red Hat Network Website 6.4.3.3. System Group Details — At the top of each System Group Details page are two links: work with group and delete group. Clicking delete group deletes the System Group and should be used with caution. Clicking Work with Group functions similarly to the Use Group button from the System Groups list in that it loads the group’s systems and launches the System Set Manager immediately.
Page 117: 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 identiﬁed. 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 118 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 119 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 120 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 identiﬁed ﬁelds 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 121 Chapter 6. Red Hat Network Website 6.4.4.9.2.2. System Set Manager ⇒ Channels ⇒ Conﬁg Channels ⇒ Diff — Use this subtab to validate conﬁguration ﬁles on the selected systems against copies in your central repository on RHN. The table lists the conﬁguration ﬁles associated with any of the selected systems.
Page 122 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 123 Chapter 6. Red Hat Network Website scription of the Conﬁguration subtab of the Channels tab for instructions. You may then identify a speciﬁc 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 124 Chapter 6. Red Hat Network Website 6.4.4.11.5. System Set Manager ⇒ Misc ⇒ Delete Systems — Click Delete System Proﬁles, then click the Conﬁrm Deletions button to remove the selected proﬁles permanently. 6.4.4.11.6. System Set Manager ⇒ Misc ⇒ Add or Remove Add-On Entitlements —...
Page 125: Advanced Search
Chapter 6. Red Hat Network Website 6.4.5. Advanced Search — The System Search page allows you to search through your systems according to speciﬁc 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 ﬁnding and removing outdated Sys- tem Proﬁles.
Page 126 Chapter 6. Red Hat Network Website are the separator used when including two or more activation keys at once. Refer to Section 6.4.6.2 Using Multiple Activation Keys at Once — for details. 3. Provide the following information: Description — User-deﬁned description to identify the generated activation key. •...
Page 127: Stored Proﬁles
Chapter 6. Red Hat Network Website 6.4.6.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 proﬁle. This allows you to aggregate the aspects of various keys without recreating a new key speciﬁc to the desired systems, simplifying the registration and kickstart processes while slowing the growth of your key list.
Page 128: Custom System Info
Chapter 6. Red Hat Network Website 6.4.8. 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 129 Chapter 6. Red Hat Network Website Figure 6-9. Kickstart Overview This overview page displays the status of kickstart on your client systems: the types and number of proﬁles you have created and the progress of systems that are scheduled to be kickstarted.
Page 130 The Red Hat Enterprise Linux System Administration Guide contains an in-depth discus- sion of kickstart and is available here: http://www.redhat.com/docs/manuals/enterprise/. 6.4.9.1.1. Kickstart Explained When a machine is to receive a network-based kickstart, the following events must occur in this order: 1.
Page 131 Chapter 6. Red Hat Network Website 6.4.9.1.2. Kickstart Prerequisites Although Red Hat Network has taken great pains to ease the provisioning of systems, some preparation is still required for your infrastructure to handle kickstarts. For instance, before creating kickstart proﬁles, you may consider: A DHCP server is not required for kickstarting, but it can make things easier.
Page 132 Chapter 6. Red Hat Network Website tribution label. Note that you cannot move between versions (2.1 to 3) or between updates (U1 to U2). Next, you may customize further for your needs, such as by adding mul- isolinux.cfg tiple kickstart options, different boot messages, shorter timeout periods, etc. Next, create the ISO as described in the Making an Installation Boot CD-ROM section of the Red Hat Enterprise Linux 3 Installation Guide.
Page 133 Chapter 6. Red Hat Network Website 6.4.9.2. View a List of Kickstart Proﬁles Figure 6-10. Kickstart Proﬁles This page lists all proﬁles for your organization, whether those proﬁles are active, and the boot image to which that proﬁle points. You can either create a new kickstart proﬁle by clicking the create new kickstart proﬁle link in the upper right or edit existing proﬁles by clicking in the name of the proﬁle.
Page 134 Security section of the Red Hat Enterprise Linux Security Guide, available at http://www.redhat.com/docs/manuals/enterprise/. The ﬁnal stage of the wizard presents the Kickstart Details ⇒ Details tab. On this tab and the other sub-tabs, nearly every option for the new kickstart proﬁle can be customized. The following sections describe the options available on each sub-tab.
Page 135 Chapter 6. Red Hat Network Website File Location The exact location from which the kickstart tree is mounted. This value is determined when the proﬁle is created. You can view it on this page but you cannot change it. 6.4.9.3.3. Kickstart Details ⇒ Advanced Options — From this page, you can toggle several installation options on and off by checking and unchecking the boxes to the left of the option.
Page 136 Chapter 6. Red Hat Network Website 6.4.9.3.6. System Details ⇒ Locale — From this sub-tab, you can change the timezone associated with kickstarted systems. 6.4.9.3.7. System Details ⇒ Partitioning — From this sub-tab, you can indicate the partitions that you wish to be created during instal- lation.
Page 137 ﬁle here: /var/www/satellite/rhn/kickstart/ < kickstart label > /RedHat/base/comps.xml 6.4.9.3.12. Software ⇒ Package Proﬁles — If you have previously created a Package Proﬁle from one of your registered systems, you can use that proﬁle as a template for the ﬁles to be installed on a kickstarted system. Refer to Section 6.4.2.8.2.2 System Details ⇒...
Page 138 Chapter 6. Red Hat Network Website 6.4.9.3.13. Activation Keys — Figure 6-14. Activation Keys The Activation Keys tab, which has no sub-tabs, allows you select Activation Keys to include as part of the kickstart proﬁle. These keys, which must have been created previous to creating the kickstart proﬁle, will be used when re-registering kickstarted systems.
Page 139 Chapter 6. Red Hat Network Website ﬁle by including the following line within the Partition Details ﬁeld of the System Details ⇒ Partitioning tab: %include /tmp/part-include 6.4.9.3.15. Kickstart File — Figure 6-16. Kickstart File The Kickstart File tab, which has no sub-tabs, allows you to view or download the kick- start proﬁle that has been generated from the options chosen in the previous tabs.
Page 140 Chapter 6. Red Hat Network Website Important The GPG key you upload to RHN must be in ASCII format. Using a GPG key in binary format causes anaconda, and therefore the kickstart process, to fail. 6.4.9.6. Kickstart ⇒ Distributions — Enables you to identify custom installation trees that may be used for kickstarting.
Page 141: Errata
Chapter 6. Red Hat Network Website 6.4.9.7. Kickstart ⇒ File Preservation — Collects lists of ﬁles to be protected and re-deployed on systems during kickstart. For instance, if you have many custom conﬁguration ﬁles located on a system to be kickstarted, enter them here as a list and associate that list with the kickstart proﬁle to be used.
Page 142: 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-17, the Relevant Errata page displays a customized list of Errata Alerts that applies to your registered systems.
Page 143: All Errata
Chapter 6. Red Hat Network Website 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. Refer to Section 6.5.2.2 Errata Details for more information. 6.5.2.
Page 144 Chapter 6. Red Hat Network Website Important If you use scheduled package installation, the packages are installed via the RHN Daemon. You must enable the RHN Daemon on your systems. Refer to Chapter 3 Red Hat Network Daemon for more details. The following rules apply to Errata Updates: Each package is a member of one or more channels.
Page 145: Advanced Search
Chapter 6. Red Hat Network Website None takes you to the Action Details page. This column corresponds to one on the Errata tab of the System Details page. 6.5.3. Advanced Search The Advanced Search page allows you to search through Errata according to speciﬁc criteria, such as summary, advisory, and package name.
Page 146 Chapter 6. Red Hat Network Website Channels can be further broken down by their relevance to your systems. Two such lists emerge: Relevant and All. 6.6.1.1. Relevant Channels As shown in Figure 6-18, the Relevant Channels page is shown by default when you click Software Channels in the left navigation bar.
Page 147 Chapter 6. Red Hat Network Website 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 148 Chapter 6. Red Hat Network Website 6.6.1.4.2. Software Channel Details ⇒ Subscribers — List of users who have subscription permissions to the channel. This tab appears on two conditions: First, the user must be an Organization Administrator or a Channel Adminis- trator.
Page 149: Channel Entitlements
Chapter 6. Red Hat Network Website 6.6.1.4.6. Software Channel Details ⇒ Subscribed Systems List of entitled systems subscribed to the channel. The list displays system names, base channels, and their levels of entitlement. Clicking on a system name takes you to its System Details page.
Page 150: Download Software
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 151 Chapter 6. Red Hat Network Website 6.6.5. Manage Software Channels This tab allows Administrators to create, clone, and delete custom channels. These chan- nels may contain altered versions of distribution-based channels or custom packages. 6.6.5.1. Manage Software Channels ⇒ Channel Details The default screen of the Manage Software Channels tab is a listing of all available chan- nels.
Page 152: Manage Conﬁg Channels
Chapter 6. Red Hat Network Website or custom Errata may be added to custom channels. Errata may be included in a cloned channel if they are selected during channel creation. 6.6.5.1.4. Manage Software Channels ⇒ Channel Details ⇒ Packages This subtab is similar to the Errata subtab. It allows Channel and Organization Adminis- trators to list, remove, compare, and add packages to the custom channel.
Page 153 Chapter 6. Red Hat Network Website that allow you to treat your conﬁguration ﬁles as templates that can be deployed across your organization, with the relevant values populated upon individual system installation. Please note that whenever a conﬁguration ﬁle is deployed via RHN, a backup of the previ- ous ﬁle including its full path is made in the directory on /var/lib/rhncfg/backups/...
Page 154 Chapter 6. Red Hat Network Website page. Clicking on a channel name takes you to the Details tab. Clicking on the number of ﬁles takes you to the Files tab. Clicking on the number of systems takes you to the Systems tab.
Page 155 Chapter 6. Red Hat Network Website 6.6.6.5. Conﬁguration Channel Details — If you click on the name of a channel in a list, the Conﬁguration Channel Details page will appear. This page contains the following tabs: 6.6.6.5.1. Conﬁguration Channel Details ⇒ Details — General information about the channel.
Page 156 Chapter 6. Red Hat Network Website 6.6.6.5.2.3. Conﬁguration Channel Details ⇒ Files ⇒ Create File — Allows you to create a conﬁguration ﬁle from scratch within the interface. The ﬁelds here work similarly to those on the Upload subtab: Path is the location to which the ﬁle will be deployed.
Page 157 Chapter 6. Red Hat Network Website ranks this conﬁg channel below all others. When done, the selected systems will appear in the Systems tab. 6.6.6.6. Conﬁguration File Details — If you click on the name or number of a ﬁle in a list, the Conﬁguration File Details page will appear.
Page 158 Chapter 6. Red Hat Network Website 6.6.6.6.4. Conﬁguration File Details ⇒ Copy — A list of conﬁguration channels that may receive a copy of the ﬁle. To copy the ﬁle to a channel, select the channel’s checkbox and click the Copy File button. Copy to Conﬁg Channel —...
Page 159 Chapter 6. Red Hat Network Website your variables match those set in the Macro Start Delimiter and Macro End Delimiter ﬁelds and do not conﬂict with other characters in the ﬁle. The delimiters must be two characters in length and cannot contain the percent (%) symbol. As an example, you may have a ﬁle applicable to all of your servers that differs only in IP address and hostname.
Page 160: Schedule
Chapter 6. Red Hat Network Website Using the Red Hat Network Conﬁguration Manager ( ) will not trans- rhncfg-manager late or alter ﬁles, as that tool is system agnostic — does not depend on rhncfg-manager system settings. Binary ﬁles cannot be interpolated. 6.7.
Page 161: Failed Actions
Chapter 6. Red Hat Network Website Figure 6-19. 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 162: 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 163: 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 164: User List ⇒ Active
Chapter 6. Red Hat Network Website Server. This person may change the base channels of systems, make channels globally subscribable, and create entirely new channels. Conﬁguration Administrator — This role enables the user to manage the conﬁguration • of systems in the organization using either the RHN website or the Red Hat Network Conﬁguration Manager.
Page 165 Chapter 6. Red Hat Network Website Figure 6-20. 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 deactivate users.
Page 166 Chapter 6. Red Hat Network Website Warning User deletion is irreversible; exercise it with caution. Consider disabling the user ﬁrst in order to assess the effect deletion will have on your infrastructure. To deactivate a user: 1. Navigate to the user’s User Details tab. 2.
Page 167 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 168 Chapter 6. Red Hat Network Website 6.8.1.1.4.2. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions ⇒ Management — Identiﬁes 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 169: User List ⇒ Deactivated
Chapter 6. Red Hat Network Website 6.8.1.1.7. User List ⇒ Active ⇒ User Details ⇒ Notiﬁcation 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 ﬁelds. If you will receive these alerts via pager, select the associated checkbox to have the messages sent in a shorter format.
Page 170: Probe Status
Chapter 6. Red Hat Network Website 6.9.1. Probe Status — As shown in Figure 6-21, the Probe Status page is shown by default when you click Mon- itoring in the top navigation bar. Figure 6-21. Probe Status The Probe Status page displays the summary count of probes in the various states and provides a simple interface to ﬁnd problematic probes quickly.
Page 171 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 172: Notiﬁcation
Chapter 6. Red Hat Network Website 6.9.1.4. Probe Status ⇒ Pending — The probes whose data have not been received by RHN. This state is expected for a probe that has just been scheduled but has not yet run. If all probes go into a pending state, your monitoring infrastructure may be failing.
Page 173 Chapter 6. Red Hat Network Website To create a new notiﬁcation method, click on the name of the user to whom the notiﬁca- tion will apply. The user’s User Details ⇒ Notiﬁcation Methods page appears. Refer to Section 6.8.1.1.7 User List ⇒ Active ⇒ User Details ⇒ Notiﬁcation Methods — further information.
Page 174: Probe Suites
Chapter 6. Red Hat Network Website 9. Recurring: Select whether a ﬁlter runs continuously or on a recurring basis. A recur- ring ﬁlter runs multiple times for a period of time smaller than the duration of the ﬁlter. For example, a recurring ﬁlter could run for 10 minutes of every hour between the start and end times of the ﬁlter.
Page 175 Chapter 6. Red Hat Network Website 3. As described in Section 6.4.2.8.5 System Details ⇒ Monitoring — , conﬁgure the probe and click the Create Probe button in the lower right. Repeat this process until all desired probes have been added. Note Sendmail must be conﬁgured correctly on your RHN Satellite Server and each client system to which the Probe Suite is applied must have the...
Page 176: Scout Conﬁg Push
Chapter 6. Red Hat Network Website 3. Check the box next to the system(s) you wish to remove from the Probe Suite. 4. Click the Detach System(s) from Probe Suite button The second method is to remove the system from the suite. This removes the system from the suite and deletes all running probes from the system.
Page 177: Satellite Tools
Chapter 6. Red Hat Network Website RHN Satellite Server to reset. It also schedules restart events for the Monitoring services on all Monitoring-enabled RHN Proxy Servers that connect to this Satellite. This is done so that the Monitoring services on these servers immediately reload their conﬁguration. Typically, the defaults provided in other ﬁelds are acceptable, since they are derived from your Satellite installation.
Page 178: Satellite Tools ⇒ String Manager
Chapter 6. Red Hat Network Website 6.10.1. Satellite Tools ⇒ Satellite Conﬁguration The form on this page allows you to alter the basic conﬁguration of your RHN Satellite Server. You may turn SSL, Monitoring, and Solaris support on and off. You may also conﬁgure your Satellite to operate as a Disconnected Satellite, or add an HTTP Proxy.
Page 179: Faq
Chapter 6. Red Hat Network Website 6.11.3. FAQ The FAQ page lists Frequently Asked Questions and answers to those questions. These are broken down into the following categories, each represented by a separate button and page: Top Ten, General, Account Management, Getting Started, Service Levels, Using RHN, Technical Questions, Management Service, Privacy/Legal, Policies, Deﬁnitions, and All.
Page 180: Proxy Guide
The Outage Policy page identiﬁes 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 notiﬁed 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 181: 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 efﬁciently. With it, you can keep close watch on system resources, network services, databases, and both standard and custom applications.
Page 182: Red Hat Network Monitoring Daemon
Chapter 7. Monitoring for 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 ( installation rhnmd instructions and a quick list of probes requiring this secure connection.
Page 183: 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 identiﬁed in Section 7.2.1 Probes requiring the daemon.
Page 184: Installing The Ssh Key
Chapter 7. Monitoring required between the systems and RHN. This may be especially desirable if you already have running. To conﬁgure the daemon for monitoring use: sshd 1. Ensure the SSH package is installed on the systems to be monitored: rpm -qi ssh 2.
Page 185: Notiﬁcations
Chapter 7. Monitoring Note If valid entries already exist in , add the daemon key to the authorized_keys ﬁle 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 186: Creating Notiﬁcation Methods
These notiﬁcations come in the form of brief text messages sent to either email or pager addresses. Here is an example of an email notiﬁcation: 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 187: Redirecting Notiﬁcations
Chapter 7. Monitoring Notification #116 for Users Run from: RHN Monitoring Satellite As you can see, the longer email notiﬁcations 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 188: Filtering Notiﬁcations
Chapter 7. Monitoring Note You can halt or redirect almost all probe notiﬁcations by replying to a notiﬁcation emails with a variation of the command . However, you cannot halt Satellite ack suspend host probe notiﬁcations by responding to a probe with or other redirect ack suspend host responses.
Page 189: Probes
Chapter 7. Monitoring 5. On the System Details ⇒ Probes tab, select another notiﬁcation method and click Update Probe. 6. You may now return to the Monitoring ⇒ Notiﬁcations page and delete the notiﬁ- cation method. 7.5. Probes Now that the Red Hat Network Monitoring Daemon has been installed and notiﬁcation methods have been created, you may begin installing probes on your Monitoring-entitled systems.
Page 190: Establishing Thresholds
Chapter 7. Monitoring 7. If the Timeout ﬁeld 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 191: 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 ﬁrst number, while the probe name (as entered in the RHN website) is...
Page 192: Rhn-Catalog
--commandline retrieves everything else, including alert thresholds and notiﬁcation 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 193 Chapter 7. Monitoring The above command requests the probe output for probeID 5, for all run levels, with a high level of verbosity. More speciﬁcally, 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 194 Chapter 7. Monitoring...
Page 195: Unix Support Guide
Chapter 8. UNIX Support Guide 8.1. Introduction This chapter documents the installation procedure for, and identiﬁes 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 196: 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: The Red Hat Network Service Daemon ( ), which triggers accord- • rhnsd rhn_check ing to a conﬁgurable interval The Red Hat Network Conﬁguration Client ( ), which executes all •...
Page 197: Excluded Features
Chapter 8. UNIX Support Guide The Channels tab of the RHN website has been augmented to accommodate the storage • and installation of native UNIX ﬁle types. 8.1.5. Excluded Features The following RHN features are not available with the UNIX support system: All Provisioning-level functionality, such as kickstarting and package rollback, with the •...
Page 198 Chapter 8. UNIX Support Guide Figure 8-1. Enabling UNIX Support During Satellite Installation 2. After the Satellite has been installed: Enable UNIX support by conﬁguring the Satellite after it has been installed. To do so, select Satellite Tools in the top menubar, then select Satellite Conﬁguration in the left navigation bar.
Page 199: Client System Preparation
Chapter 8. UNIX Support Guide Figure 8-2. Enabling UNIX Support After Satellite Installation Click the Update Conﬁguration button to conﬁrm the change. 3. Finally, you must create a base channel to which your client systems may subscribe. This is because RHN does not provide UNIX content; as a result, you cannot use to create the channel.
Page 200: Download And Install Additional Packages
Chapter 8. UNIX Support Guide pared for connection: 1. Download and install and required third-party libraries. gzip 2. Download the RHN application tarball from the Satellite to the client and install the contents. 3. Next, deploy the SSL certiﬁcates required for a secure connection. 4.
Page 201 Chapter 8. UNIX Support Guide On recent versions of Solaris, the necessary libraries are provided by the following natively installed packages: • SUNWgccruntime • SUNWopenssl* • SUNWzlib For older Solaris versions, the following required packages may be downloaded from http://www.sunfreeware.com: •...
Page 202 Chapter 8. UNIX Support Guide 8.3.1.3. Download RHN Client Packages Download the appropriate tarball of packages from the directory /var/www/html/pub/ of your Satellite. If you are able to use a GUI web browser like Mozilla, navigate to the directory of the Satellite and save the appropriate tarball to your client: /pub http://your-satellite.example.com/pub/rhn-solaris-bootstrap- version...
Page 203: Deploying Client Ssl Certiﬁcates
# MANPATH=$MANPATH:/opt/redhat/rhn/solaris/man # export MANPATH Alternatively, you can also access the man pages from the command line, with the follow- ing command: # man -M /opt/redhat/rhn/solaris/man man page < > Finally, add the Red Hat Libraries to your PATH as you did with...
Page 204: Conﬁguring The Clients
2. Move the client SSL certiﬁcate to the RHN-speciﬁc 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 ﬁnished, the new client certiﬁcate will be installed in the appropriate directory for your UNIX system.
Page 205: Registration And Updates
SSL certiﬁcate described in Section 8.3.2 Deploying Client SSL Certiﬁcates, 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 Your client systems are now ready for registration with Red Hat Network and management by your Satellite.
Page 206: Obtaining Updates
Chapter 8. UNIX Support Guide Be sure to replace the argument of each option with values appropriate to your orga- nization. 6. Go back to the website, click the name of the activation key, and ensure the new system appears within the Activated Systems tab. 8.4.2.
Page 207 Chapter 8. UNIX Support Guide to translate Solaris packages, patches, and patch clusters to a format that the Satellite can understand. 8.4.2.1.1. solaris2mpm As mentioned brieﬂy in Section 8.1.4 Differences in Functionality, is part solaris2mpm of RHN Push for Solaris. The content that is pushed to a Solaris channel on the Satellite must ﬁrst be in .mpm format.
Page 208 Chapter 8. UNIX Support Guide Option Description Prints program usage information and exits -?, --usage Temporary directory to work from --tempdir= < tempdir > Selects the architecture (i386 or Sparc) for multi-arch --select-arch= < arch > packages. Table 8-1. options solaris2mpm 8.4.2.1.2.
Page 209 It can be started from the command line in this way: rhnsd --foreground --interval=240 The default location for . Below rhnsd /opt/redhat/rhn/solaris/usr/sbin/rhnsd are the available options for on Solaris: rhnsd Option Description...
Page 210: Remote Commands
Chapter 8. UNIX Support Guide Argument Description Show program version information. --version Show this help message and exit. --help Show additional output. --verbose List the latest versions of all packages installed. --list Update packages associated with this System --packages Proﬁle. Update this system’s hardware proﬁle on RHN.
Page 211: Issuing 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 ﬁle 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 212 Chapter 8. UNIX Support Guide...
Page 213: Command Line Conﬁg Management Tools
Appendix A. Command Line Conﬁg 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 conﬁguration ﬁles: the Red Hat Network Conﬁguration Client and the Red Hat Network Conﬁguration Manager. There is a complementary Red Hat Network Actions Control tool that is used to enable and dis- able conﬁguration management on client systems.
Page 214: Red Hat Network Conﬁguration Client
Appendix A. Command Line Conﬁg Management Tools Option Description Option Description --enable-deploy Allow rhncfg-client to deploy ﬁles. --enable-diff Allow rhncfg-client to diff ﬁles. --enable-upload Allow rhncfg-client to upload ﬁles. --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 215: Listing Conﬁg Files
Appendix A. Command Line Conﬁg Management Tools A.2.1. Listing Conﬁg Files To list the conﬁguration ﬁles for the machine and the labels of the conﬁg channels contain- ing them, issue the command: rhncfg-client list The output resembles the following list: Config Channel File config-channel-17...
Page 216: Viewing Conﬁg Channels
Appendix A. Command Line Conﬁg Management Tools A.2.3. Viewing Conﬁg Channels To view the labels and names of the conﬁg 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 217: Verifying Conﬁg Files
Appendix A. Command Line Conﬁg Management Tools /usr/bin/diff: /home/test/blah/var/spool/aalib.rpm: No such file or directory A.2.5. Verifying Conﬁg Files To quickly determine if client conﬁguration ﬁles 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 ﬁle...
Page 218: Creating A Conﬁg Channel
Appendix A. Command Line Conﬁg Management Tools than root, you may have to make conﬁguration changes within the ﬁle. The ~/.rhncfgrc session ﬁle is cached in to prevent logging in for every ~/.rhncfg-manager-session command. The default timeout for the Red Hat Network Conﬁguration Manager is 30 minutes. To alter this, add the option and new value to the server.session_lifetime...
Page 219: Differentiating Between Latest Conﬁg Files
Appendix A. Command Line Conﬁg Management Tools rhncfg-manager add /path/to/file --channel=channel-label In addition to the required channel label and the path to the ﬁle, you may use the available options for modifying the ﬁle during its addition. For instance, you may alter the path and ﬁle name by including the option in the command, like: --dest-file...
Page 220: Differentiating Between Various Versions
Appendix A. Command Line Conﬁg 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 ﬁle(s) from this conﬁg channel -rREVISION, --revision=REVISION Use this revision -dDEST_FILE, Upload the ﬁle as this path...
Page 221: Downloading All Files In A Channel
Appendix A. Command Line Conﬁg 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 conﬁg channel -rREVISION, --revision=REVISION Use this revision -h, --help Show help message and exit Table A-6.
Page 222: Getting The Contents Of A File
Appendix A. Command Line Conﬁg Management Tools A.3.6. Getting the Contents of a File To direct the contents of a particular ﬁle to stdout, issue the command: rhncfg-manager get --channel=channel-label /tmp/dest_path/example-config.txt You should see the contents of the ﬁle as output. A.3.7.
Page 223: Removing A File From A Channel
Appendix A. Command Line Conﬁg 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 ﬁle 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 224: Determining The Number Of File Revisions
Appendix A. Command Line Conﬁg Management Tools A.3.11. Determining the Number of File Revisions To ﬁnd out how many revisions (revisions go from 1 to N where N is an integer greater than 0) of a ﬁle/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 225: Uploading Multiple Files At Once
Appendix A. Command Line Conﬁg Management Tools A.3.13. Uploading Multiple Files at Once To upload multiple ﬁles to a conﬁg 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 226 Appendix A. Command Line Conﬁg Management Tools...
Page 227: 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 228: Viewing The Cid
Appendix B. RHN API Access use the method within the system class to obtain a list of systems list_user_systems available to the user that contains the associated B.4. Viewing the cid Like servers, channels have their own IDs. This value, the , is a required parameter for some methods, including .
Page 229 Appendix B. RHN API Access ############################################################################ 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. my $client = new Frontier::Client(url =>...
Page 230 Appendix B. RHN API Access # Additional system calls are described at: http://$HOST/rpc/api/system/...
Page 231: Probes
Appendix C. Probes As described in Section 6.9 Monitoring — , Monitoring-entitled systems can have probes applied to them that constantly conﬁrm 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 232: 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 233: Apache::trafﬁc
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 234: Apache::uptime
Appendix C. Probes Trafﬁc — The kilobytes per second of trafﬁc the server has processed since the probe • last ran. directive in the ﬁle of the Web server must be set to ExtendedStatus httpd.conf On for this probe to function properly. Field Value Application Protocol*...
Page 235: 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 conﬁgured 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 236: 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 237: 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 238: 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 239: 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 speciﬁed servlet is reloaded per minute. •...
Page 240: General::remote Program With Data
Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon ( ) must be running rhnmd on 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 241: 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 identiﬁer (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 242: 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 speciﬁed port number. It collects the following metric: Remote Service Latency — The time it takes in seconds for the TCP server to answer a •...
Page 243: 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 identiﬁer (OID) to obtain this value. The only error status it will return is UNKNOWN.
Page 244: Linux::cpu Usage
Appendix C. Probes monitored 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 ﬁve-second average of the percent of CPU usage at probe • execution.
Page 245: 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 246: 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 speciﬁed ﬁle 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 ﬁles in a Linux ﬁle system.
Page 247: 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 Trafﬁc settings C.5.6.
Page 248: 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 ﬁeld.
Page 249: 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 250: Linux::process Health
Appendix C. Probes C.5.10. Linux::Process Health The Linux::Process Health probe monitors user-speciﬁed 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 251: 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 veriﬁes that the speciﬁed process is functioning prop- erly.
Page 252: 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 rhnmd on the monitored system to execute this probe.
Page 253: Linux::users
Appendix C. Probes Field Value Local IP address ﬁlter pattern list Local port number ﬁlter Remote IP address ﬁlter pattern list Remote port number ﬁlter 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 254: 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 255: 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 ﬁle and collects the following metrics: Regular Expression Matches — The number of matches that have occurred since the •...
Page 256: 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 ﬁle growth and collects the following metrics: Size —...
Page 257: 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 258: 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 259: 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 260: 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 261: 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 262: 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 263: 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 264: 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 ﬁrst line of the response from the system.
Page 265: 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 266: 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 267: 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 speciﬁed port and collects the following metric: Remote Service Latency — The time it takes in seconds for the SSH server to answer a •...
Page 268: 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 269: 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 ﬁle to ensure that the DNS name is resolved correctly. C.9.1.
Page 270: 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 271: 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 272: 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 273: 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 274: 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 275: 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 276: 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 277: 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 278: 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 279: 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 280: 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 281: Rhn Satellite Server::latency
Appendix C. Probes Field Value Critical Maximum Output Rate Table C-65. RHN Satellite Server::Interface Trafﬁc 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 282: 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 283: 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 284: 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 285: Rhn Satellite Server::swap
Appendix C. Probes Field Value Command Name Process ID (PID) ﬁle 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 286 Appendix C. Probes...
Page 287: Glossary
An Errata Alert that pertains to a bug ﬁx. 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 288 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 289 Errata, Bugzilla bug IDs, relevant releases/architectures, solutions including required RPMs, and MD5 checksums for veriﬁcation. 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 ﬁxes are submitted by Red Hat engineers as well as the Linux community through Bugzilla which generates a bug report for each issue.
Page 290 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. Notiﬁcation 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 291 Glossary Probe State The measure of a probe’s adherence to its deﬁned 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, reconﬁguring, tracking, and reverting systems.
Page 292 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 Conﬁguration Tool to conﬁgure its preferences, including whether to install the packages after they are downloaded.
Page 293 Glossary Software Manager The name of the ﬁrst 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 294 Glossary...
Page 295: Index
Index child, 129 entitling, 133 errata, 132 list of, 129 packages, 132 account relevant, 130 deactivate, 74 retired, 131 action Software and Conﬁguration Files, 129 completed systems, 146 Channels and Packages details, 146 Channel List, 129 failed systems, 147 child channel, 129 in progress systems, 147 activation key, 109 client applications...
Page 296 getting started, 6 GNU Privacy Guard, 6 deactivate user, 149 delete user (RHN Satellite Server only), 149 deleting a system, 82 hardware proﬁle Digital Certiﬁcate, 5 Updating on server, 88 download ISO images, 134 Help Desk, 162 HTTP Proxy, 46 email address change, 74 initialization script...
Page 297 Users, 237 Virtual Memory, 238 navigation, 65 List Navigation Network Services explanation of, 70 DNS Lookup, 244 LogAgent FTP, 245 Log Pattern Match, 239 IMAP Mail, 245 Log Size, 240 Mail Transfer (SMTP), 246 probes Ping, 246 nocpulse, 238 POP Mail, 247 probes, 244 Remote Ping, 248 RPCService, 249...
Page 298 Table Extents, 261 Process Counts by State, 232 Tablespace Usage, 262 Process Health, 234 Process Running, 235 TNS Ping, 263 Organization Administrator, 150 Swap Usage, 236 overview of website, 67 TCP Connections by State, 236 Users, 237 Virtual Memory, 238 LogAgent Log Pattern Match, 239 package installation...
Page 299 Execution Time, 264 Interface Trafﬁc, 264 quality assurance Latency, 265 overview, 5 Load, 265 Quick Search Probe Count, 266 explanation of, 69 Process Counts, 266 Process Health, 267 Process Running, 268 Processes, 267 reactivating Swap, 269 systems, 87 Users, 269 Red Hat Enterprise Linux 2.1 WebLogic requiring the Red Hat Network Registration...
Page 300 Red Hat Network packages username, 54 comparison, 7 with a proxy server, 50 Network Registration Client with activation key, 109 (rhn)_register) remote commands initial description, 2 Red Hat packages enabling, 194 for UNIX, 184 issuing, 195 installing, 184 RHN Satellite Server Red Hat Update Agent, 48 Disk Space, 263 Command Line Arguments, 29...
Page 301 system group list status, 98 Schedule, 144 System Groups Scheduled Actions Action Details, 146 assigning and removing, 96 Actions List, 146 joining and leaving, 96 Archived Actions, 145 System Group List, 97 Completed Actions, 145 system list, 79 Failed Actions, 145 System Proﬁle, 56 Pending Actions, 144 Scout Conﬁg Push, 165...
Page 302 Errata Search, 129 Help, 162 UNIX variants language, 75 (see supported) locale, 75 unsubscribe to channel, 129 logging in, 70 Update Monitoring, 153 service level, 2 navigation bar, 65 updating overview, 65 via command line, 193 Purchase History, 77 via website, 192 Relevant Errata, 126 user Schedule, 144...

Red Hat NETWORK 4.1.0 Reference Manual

Introduction to the Guide

Red hat Network Overview

Red hat Update Agent

Red hat Network Daemon

Red hat Network Alert Notiﬁcation Tool

Red hat Network Registration Client

Red hat Network Website

Monitoring

UNIX Support Guide

Command Line Conﬁg Management Tools

RHN API Access

Probes

Glossary

Index

Quick Links

Troubleshooting

Related Manuals for Red Hat NETWORK 4.1.0

Summary of Contents for Red Hat NETWORK 4.1.0