Page 1 Red Hat Network Satellite 5.3.0 Reference Guide Red Hat Network Satellite...
Page 2 Reference Guide Red Hat Network Satellite 5.3.0 Reference Guide Red Hat Network Satellite Edition 5.3.0 Copyright © 2009 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version of the OPL is presently available at http://www.opencontent.org/openpub/).
Page 3: Table Of Contents
Introduction to the Guide 1. More to Come ........................ xi 1.1. Send in Your Feedback ..................xii 1. Red Hat Network Overview 1.1. Update ......................... 2 1.2. Management ........................ 2 1.3. Provisioning ......................... 3 1.4. Monitoring ........................4 1.5. Errata Notifications and Scheduled Package Installations ..........4 1.6.
Page 4 Reference Guide 6.4. Applying Updates ....................... 54 6.5. Launching the RHN Website ..................54 7. Red Hat Network Website 7.1. Navigation ........................55 7.1.1. Entitlement Views .................... 55 7.1.2. Categories and Pages ..................56 7.1.3. Errata Alert Icons .................... 59 7.1.4.
Page 5 7.5. Errata ........................116 7.5.1. Relevant Errata ....................117 7.5.2. All Errata ....................... 118 7.5.3. Advanced Search ..................120 7.6. Channels ........................122 7.6.1. Software Channels ..................122 7.6.2. Package Search .................... 127 7.6.3. Manage Software Channels ................128 7.7. Configuration ......................129 7.7.1.
Page 6 Reference Guide 7.10.4. Scout Config Push — ..........................150 7.10.5. General Config — ..........................150 7.11. Admin ........................151 7.11.1. Admin Organizations ................. 151 7.11.2. Admin RHN Satellite Configuration ............151 7.12. Help ........................152 7.12.1. Reference Guide ..................152 7.12.2.
Page 7 9.4.1. Admin Subscriptions Software Channel Entitlements ......... 175 9.4.2. Admin Subscriptions System Entitlements ..........176 9.5. Configuring Systems in an Organization ..............176 9.6. Organizational Trusts ....................177 9.6.1. Establishing an Organizational Trust ............... 177 9.6.2. Sharing Content Channels between Organizations in a Trust ......178 9.6.3.
Page 8 Reference Guide 12.3.2. Deploying Client SSL Certificates ..............212 12.3.3. Configuring the clients .................. 212 12.4. Registration and Updates ..................213 12.4.1. Registering Systems ..................213 12.4.2. Obtaining Updates ..................214 12.5. Remote Commands ....................218 12.5.1. Enabling Commands ..................218 12.5.2.
Page 9 D. Probes D.1. Probe Guidelines ..................... 253 D.2. Apache 1.3.x and 2.0.x .................... 254 D.2.1. Apache::Processes ..................254 D.2.2. Apache::Traffic ....................255 D.2.3. Apache::Uptime ..................... 255 D.3. BEA WebLogic 6.x and higher .................. 256 D.3.1. BEA WebLogic::Execute Queue ..............256 D.3.2.
Page 10 Reference Guide D.8.7. Network Services::Remote Ping ..............277 D.8.8. Network Services::RPCService ............... 277 D.8.9. Network Services::Secure Web Server (HTTPS) ..........278 D.8.10. Network Services::SSH ................278 D.8.11. Network Services::Web Server (HTTP) ............279 D.9. Oracle 8i, 9i, and 10g ....................280 D.9.1.
Page 11: Introduction To The Guide
The Red Hat Network Reference Guide is constantly expanding as new Red Hat Network features and service plans are launched. HTML and PDF versions of this and other manuals are available within the Help section of the RHN Satellite website and at http://www.redhat.com/docs/manuals/satellite. Note...
Page 12: Send In Your Feedback
Introduction to the Guide 1.1. Send in Your Feedback If you would like to make suggestions about the Red Hat Network Satellite Reference Guide, please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component Documentation_Reference_Guide (Product: Red Hat Network Satellite, Version: 520).
Page 13: Red Hat Network Overview
Chapter 1. Red Hat Network Overview Have you ever read about a new version of a software package and wanted to install it but could not find it? Have you ever tried to find an RPM through an Internet search engine or an RPM repository and been linked to an unknown site? Have you ever tried to find an RPM but instead found only source files that you had to compile yourself?
Page 14: Update
Many Red Hat Network terms are used throughout this manual. As you read the Red Hat Network Reference Guide, refer to the Glossary as necessary for an explanation of common terms. http://www.redhat.com/rhn/ For a comparison chart of RHN service levels, refer to compare/. 1.1. 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.
Page 15: Provisioning
Provisioning Hat Login page, click Create a new Business Login. After creating a business account, you may add users within your organization to it. The Red Hat Network features available to you depend on the subscription level for each Red Hat Enterprise Linux system.
Page 16: Monitoring
Chapter 1. Red Hat Network Overview • Custom System Information — Provisioning customers may identify any type of information they choose about their registered systems. This differs from System Profile information, which is generated automatically, and the Notes, which are unrestricted, in that the Custom System Information allows you to develop specific keys of your choosing and assign searchable values for that key to each Provisioning-entitled system.
Page 17: Security, Quality Assurance, And Red Hat Network
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 Profile, available at http://rhn.redhat.com, is accessible only with an RHN-verified username and password. 2. A Digital Certificate is written to the client system after registration and is used to authenticate the system during each transaction between the client and Red Hat Network.
Page 18 Chapter 1. Red Hat Network Overview rpm -q rhn_register If the Red Hat Network Registration Client is installed, it will return something similar to: rhn_register-2.9.3-1 The version number might differ slightly. If you do not have the Red Hat Network Registration Client installed, the command will return: package rhn_register is not installed Table 1.1, “Red Hat Network Packages”...
Page 19: The Rhn_Register Client
Chapter 2. The rhn_register Client Red Hat Enterprise Linux 5 features an application called rhn_register. This application works with the yum-based RHN Hosted and RHN Satellite client called Package Updater (or pup)that replaces Chapter 3, Package Updater. up2date. For more information about pup, refer to The rhn_register application normally runs as part of the firstboot configuration process just after installation.
Page 20 Chapter 2. The rhn_register Client Figure 2.2. Registering for Software Updates The Registering for Software Updates page summarizes the steps involved in the registration process. To learn more about the benefits of Hosted and Satellite, press the Why Should I Connect to RHN button.
Page 21 Using rhn_register Figure 2.3. Choose an Update Location The Choose an Update Location page allows you to select the source of your software updates - either from RHN Hosted or from RHN Satellite Server or Proxy Server. For Satellite or Proxy, the associated radio button and enter the URL of your Satellite or Proxy into the Red Hat Network Location field.
Page 22 Chapter 2. The rhn_register Client Figure 2.4. Enter Your Account Information The Enter Your Account Information page requires you to enter your RHN login information (if you already have one), or to create a new account if you do not. To create a new RHN account, press the Create a New Account button.
Page 23 Using rhn_register Figure 2.5. Create Your System Profile The Create Your System Profile page allows you to select a profile name for the system you are registering. The default name for any system is that system's hostname, although you may change it as you like.
Page 24 Chapter 2. The rhn_register Client Figure 2.6. Review System Subscription Details The Review System Subscription Details page displays the base and child channel information to which your system has been subscribed. Take a moment to review the channels, and then press Forward to continue.
Page 25: Command-Line Version Of Rhn_Register
Command-line version of rhn_register Figure 2.7. Finish Setting Up Software Updates The Finish Setting Up Software Updates page indicates that you have successfully registered a Red Hat Enterprise Linux 5 system with RHN. From this point, you do not have to do anything to receive software updates.
Page 26 Chapter 2. The rhn_register Client Type rhn_register at a shell prompt. If you are on shell terminal window and want to run the non- graphical version, you must type rhn_register --nox to prevent opening the graphical client. Figure 2.8. rhn_register Command-line version The interface of the command-line version of rhn_register has the same configuration screens as the graphical desktop version.
Page 27: Package Updater
Chapter 3. Package Updater Depending on your version of Red Hat Enterprise Linux, systems registered to a Satellite can update client systems directly using various tools and applications installed on the system. For Red Hat Enterprise Linux 5, you can use the Package Updater (or pup) to keep systems updated. The Package Updater (pup) is the desktop update application for Red Hat Enterprise Linux 5.
Page 28 Chapter 3. Package Updater To view the update details of any package, highlight the package and click the arrow next to Update Details. When you are ready to update the packages, click Apply updates. The Updater will resolve any dependencies, and notify you when a package must be installed to meet a dependency for an updated package.
Page 29: The Package Updater Applet
The Package Updater Applet Click Import Key to accept the Key and continue with the update. When the update completes, you may be prompted to reboot your system for the changes to take effect. Figure 3.4. Reboot Prompt You can choose to reboot now or later, but it is recommended to click Reboot Now to start using the updated packages.
Page 30: Updating Packages From The Command Line With Yum
Chapter 3. Package Updater • Quit — close the applet 3.3. Updating Packages from the Command Line with yum The foundation of the Package Updater is the Yum package manager, developed by Duke University to improve the installation of RPMs. yum searches supported repositories for packages and their dependencies so they may be installed together in an effort to alleviate dependency issues.
Page 31 yum Commands yum localinstall absolute path to filename Used when using yum to install a package located locally in the machine.
Page 33: Red Hat Update Agent
Chapter 4. Red Hat Update Agent The Red Hat Update Agent is your connection to Red Hat Network on Red Hat Enterprise Linux 4 It enables you to register your systems, create System Profiles, and alter the settings by which your organization and RHN interact.
Page 34 Chapter 4. Red Hat Update Agent If you choose the last option and start the application from a shell prompt, you can specify the options Table 4.1, “Graphical Update Agent Options”. To view these options, type the command up2date --help. For example, use the following command to specify the directory in which to download the updated packages (temporarily overriding your saved configuration): up2date --tmpdir=/tmp/up2date/...
Page 35 Starting the Red Hat Update Agent Figure 4.1. Configure Proxy Server Figure 4.2, The second dialog box to appear prompts you to install the Red Hat GPG key, as shown in “Install GPG Key”. 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 36: Registration
Chapter 4. Red Hat Update Agent 4.2. Registration Before you begin using Red Hat Network, you must create a username, password, and System Profile. Upon launch, the Red Hat Update Agent senses whether these tasks have been accomplished. If not, it guides you through the registration process. If you ever need to force the Red Hat Update Agent into registration mode, such as to re-register an existing system, you may do so by issuing the following command at a shell prompt: up2date --register...
Page 37: Registering A User Account
4.2.1. Registering a User Account Before you create a System Profile, you must create a user account. Red Hat recommends that you do so through the website at https://rhn.redhat.com/newlogin/, but you may also do so via Red Hat Update Agent (up2date).
Page 38 Chapter 4. Red Hat Update Agent Figure 4.4. Red Hat Login Screen New users must select the I don't have a Red Hat login. I need to create one. radio button and click the Forward button. Add details about yourself and your business to the screen shown in Figure 4.5, “Create a User Account”, and identify the methods by which you may be reached.
Page 39: Activate
Activate Note You must choose a unique username. If you enter one already in use, you will see an error message. Try different usernames until you find one that has not been used. Complete all fields marked by an asterisk (*). The address and email addresses are required so that Red Hat may communicate with you regarding your account.
Page 40 Chapter 4. Red Hat Update Agent • CPU model • CPU speed • Amount of RAM • PCI devices • Disk sizes • Mount points The software System Profile consists of a list of RPM packages for which you wish to receive notifications.
Page 41: Channels
Channels Figure 4.6. Activate Figure 4.7, “Sending System Profile to Red Hat Network” shows the progress bar displayed as the System Profile is sent. Figure 4.7. Sending System Profile to Red Hat Network 4.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 42 Chapter 4. Red Hat Update Agent Figure 4.8. Channels Red Hat Update Agent now compares the packages in your RPM database with those available from Figure 4.9, “Fetching package list” the Channel you selected. The progress bar shown in is displayed during this process.
Page 43: Packages Flagged To Be Skipped
Packages Flagged to be Skipped 4.2.4. Packages Flagged to be Skipped The next step in the initial update is the selection of files to be skipped. Any packages checked here will not be downloaded and updated by the Red Hat Update Agent. This screen is displayed whenever packages are available that are currently selected to be ignored.
Page 44 Chapter 4. Red Hat Update Agent Figure 4.11. Available Package Updates...
Page 45: Retrieving Packages
Retrieving Packages Figure 4.12. Example Errata Advisory 4.2.6. Retrieving Packages The Red Hat Update Agent tests the packages you selected to be certain that the requirements of each RPM are met. If any additional packages are required, Red Hat Update Agent displays an error message.
Page 46: Installing Packages
Chapter 4. Red Hat Update Agent Figure 4.13. Retrieving Packages 4.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 4.3.2, “Manual Package Installation”...
Page 47 Installing Packages Figure 4.14. Installing Packages When the Red Hat Update Agent has finished downloading the desired packages (and installing them Figure 4.15, “All Finished”. Click Finish to exit if you chose the install option), it displays the screen in the Red Hat Update Agent.
Page 48: Command Line Version
Chapter 4. Red Hat Update Agent Figure 4.15. All Finished 4.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 functions...
Page 49 Command Line Version Option Description Briefly describe the available options. -?, --usage List the available options and exit. -h, --help Force up2date to install this architecture of the package. --arch=architecture Not valid with --update, --list, or --dry-run. Specify from which channels to update using channel --channel=channel labels.
Page 50 Chapter 4. Red Hat Update Agent Option Description Update packages associated with this System Profile. -p, --packages Specify an HTTP proxy to use. --proxy=proxy URL Specify a password to use with an authenticated HTTP --proxyPassword=proxy proxy. password Specify a username to use with an authenticated HTTP --proxyUser=proxy user ID proxy.
Page 51: Installing The Red Hat Gpg Key
For older versions of RPM, such as the one that came with Red Hat Enterprise Linux 2.1, use the gpg command (as root): /usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY https://www.redhat.com/security/team/ To download the Red Hat GPG key first, you may obtain it from key.html .
Page 52: Manual Package Installation
Chapter 4. Red Hat Update Agent V7R8BElBmg99IlJmDvA2BI/seXvafhzly9bxSHScFnceco/Az9umIs3NXwv3/yOm ZakDBAC6SAGHBmpVkOdeXJDdb4LcbEhErFU3CpRCjZ6AOnFuiV1MGdulZXvEUgBA I6/PDE5nBHfZY3zPjyLPZVtgYioJpZqcRIx/g+bX2O8kPqvJEuZ19tLCdykfZGpy 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 file and import it into your keyring using the method applicable to your version of RPM. 4.3.2.
Page 53: Log File
Log File rhn-profile-sync After running this command, your RHN System Profile reflects the latest software versions installed on your system. For Red Hat Enterprise Linux 4 systems, use the following command to update the package list, run the command: up2date -p 4.3.4.
Page 54 Chapter 4. Red Hat Update Agent Figure 4.16. General Settings In addition, RHN Proxy and Satellite customers have the option of selecting Red Hat Network Servers here. These customers should refer to the RHN Client Configuration Guide for detailed instructions. 4.4.1.2.
Page 55 Using the Red Hat Update Agent Configuration Tool Figure 4.17. Retrieval/Installation Settings Figure 4.17, “Retrieval/Installation The following package retrieval options can be selected (see Settings”): • Do not install packages after retrieval — download selected RPM packages to the desired directory and ignore the installation preferences •...
Page 56 Chapter 4. Red Hat Update Agent • Override version stored in System Profile — override the Red Hat Linux version in your System Profile • Package storage directory — change the directory where packages are downloaded; the default location is /var/spool/up2date/ 4.4.1.3.
Page 57: Command Line Version
['kernel*'] storageDir /var/spool/up2date adminAddress ['root@localhost'] 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.
Page 58: Registering With Activation Keys
Chapter 4. Red Hat Update Agent Enter the number of the item to modify and enter a new value for the option. When you finish changing your configuration, press Enter to save your changes and exit. Press q and then Enter to quit without saving your changes.
Page 59 Registering with Activation Keys In addition, Provisioning-entitled systems may use multiple activation keys at once, either at the command line or within kickstart profiles. This allows Administrators to include a variety of values without creating a special key for the desired results. To do this, specify the keys separated by commas, like this: rhnreg_ks --activationkey=7202f3b7d218cf59b764f9f6e9fa281b,\ 39f41081f0329c20798876f37cb9p6a3...
Page 60: Registering A System To An Organization
Chapter 4. Red Hat Update Agent • Systems registered by activation keys are tied to the organization account in which the key was created, not the key itself. After registration, a key can be deleted safely without any effect on the systems it was used to register.
Page 61: Red Hat Network Daemon
Red Hat Network Satellite. Make certain: • your client is configured correctly. • your system can communicate with RHN via SSL (port 443). You may test this by running the following command from a shell prompt: telnet xmlrpc.rhn.redhat.com 443...
Page 62 Chapter 5. Red Hat Network Daemon • the Red Hat Network Daemon is activated and running. You may ensure this by running the following commands: chkconfig --level 345 rhnsd on service rhnsd start If these are correct and your systems still indicate they are not checking in, please contact our technical support team.
Page 63: Red Hat Network Alert Notification Tool
Chapter 6. Red Hat Network Alert Notification Tool The Red Hat Network Alert Notification Tool is a notifier that appears on the desktop panel and alerts users when software package updates are available for their Red Hat Enterprise Linux 4 systems.
Page 64 Chapter 6. Red Hat Network Alert Notification Tool Figure 6.2. HTTP Proxy Configuration If your network connection requires you to use an HTTP Proxy Server to make HTTP connections, on the Proxy Configuration screen, type your proxy server in the text field with the format HOST:PORT.
Page 65: Notification Icons
Notification Icons You can also configure the Red Hat Network Alert Notification Tool to ignore specific packages. To select these packages, click on the applet and select the Ignored Packages tab. 6.2. Notification Icons Table 6.1, “Red Hat The applet displays a different icon, depending on the status of the updates. Network Alert Notification Tool Icons”...
Page 66: Applying Updates
Chapter 6. Red Hat Network Alert Notification Tool Figure 6.3. Available Updates 6.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 67: Red Hat Network Website
Chapter 7. 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 68: Categories And
Chapter 7. Red Hat Network Website Icon Entitlement Monitoring Table 7.1. Entitlement Icons If no icon follows a category, page, or tab label within this chapter, the area described is available to all Red Hat Network users. If an icon does follow, the associated entitlement is needed. Remember that Provisioning inherits all of the functions of Management.
Page 69 Categories and Pages • System Set Manager — — Perform various actions on collective sets of systems, including scheduling errata updates, package management, listing and creating new groups, and managing channel entitlements. • Advanced Search — — Quickly search all of your systems by specific criteria, such as name, hardware, devices, system info, networking, packages, and location.
Page 70 Chapter 7. Red Hat Network Website • Manage Software Channels — — Create and edit channels used to deploy configuration files. • Configuration — Keep track of and manage configuration channels, actions, and individual configuration files. • Overview — A general dashboard view that shows a configuration summary •...
Page 71: Errata Alert Icons
Errata Alert Icons — Manage your monitoring infrastructure using suites of monitoring probes that apply to one or more assigned systems. • Scout Config Push — — Displays the status of your monitoring infrastructure. • Admin (visible only to Satellite administrators) — List, create, and manage one or more Satellite organizations, from which the Satellite administrator can assign channel entitlements, create and assign administrators for each organization, and other tasks.
Page 72: Quick Search
Chapter 7. Red Hat Network Website 7.1.4. Quick Search In addition to the Advanced Search functionality for Packages, Errata, Documentation, and Systems offered within some categories, RHN Satellite also offers a Quick Search tool near the the top of each page.
Page 73: Logging Into The Rhn Website
Figure 7.4. RHN Website If you have not registered a system yet or do not have a redhat.com account, create a new account by following the Learn More link, then selecting Create Login on the resulting page. After creating a Chapter 4, Red Hat Update new user account, you must register a system before using RHN.
Page 74: Overview
Chapter 7. Red Hat Network Website If you have not previously accepted the RHN Site Terms and the T7 agreement, you will be asked to do so now before proceeding. To read the content of either agreement, click on its title, which will open a new window.
Page 75 Overview Figure 7.5. Overview This page is broken into functional areas, with the most critical areas displayed first. Users can control which of the following areas are displayed by making selections on the Your RHN Your Preferences page. Refer to Section 7.3.2, “Your Preferences”...
Page 76: Your Account
Remember, if you change your Red Hat Network password (the one used to log into RHN and redhat.com), you will not see your new one as you type it for security reasons. Also for security, your password is represented by 12 asterisks no matter how many characters it actually contains. Replace the asterisks in the Password and Password Confirmation text fields with your new password.
Page 77: Your Preferences
Your Preferences 7.3.1.3. Account Deactivation The Account Deactivation page provides a means to cancel your Red Hat Network service. Click the Deactivate Account button to deactivate your account. The web interface returns you to the login screen. If you attempt to log back in, an error message advises you to contact the Satellite Administrator for your organization.
Page 78: Subscription Management
Chapter 7. Red Hat Network Website 7.3.4. Subscription Management To use all of the features of RHN, your systems must be entitled — subscribed to an RHN service level. Use the System Entitlements page to configure which systems are entitled to which service offerings.
Page 79: Organization Trusts
Organization Trusts To enable the base entitlement, select the checkbox to the left of the system, then click the Set to Management Entitled button. For add-on entitlements, select the system's checkbox, followed by the desired entitlement from the drop-down box, and finally press the Add Entitlement button. If clicking on an entitlement fails to update the information in the table, you may need to purchase additional entitlements.
Page 80: Overview
Chapter 7. Red Hat Network Website 7.4.1. Overview — The Overview page provides a summary of your systems, including their status, number of associated Errata and packages, and entitlement level. Clicking on the name of a system takes you to its System Details page.
Page 81 Systems • — System is locked; Actions prohibited • — System is being kickstarted • — Updates have been scheduled • — System not checking in properly (for 24 hours or more) • — System not entitled to any update service •...
Page 82 Chapter 7. Red Hat Network Website 7.4.2.1. All The All page contains the default set of your systems. It displays every system you have permission to manage. A user has permission to manage a system if he is the only user in his organization, if he is an Satellite Administrator, or if the system is a member of a group to which he has admin rights.
Page 83 Systems • The system is not entitled to any RHN service. System Profiles that remain unentitled for 180 days (6 months) are removed. • The system is entitled, but the Red Hat Network Daemon has been disabled on the system. Refer to Chapter 5, Red Hat Network Daemon for instructions on restarting and troubleshooting.
Page 84 Chapter 7. Red Hat Network Website • Provisioning — • Monitoring — • Groups • Events The following sections discuss these tabs and their sub-tabs in detail. 7.4.2.9.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 85 Systems IP Address The IP address of the client. Kernel The kernel that is installed and operating on the client system. Registered The date and time at which the system registered with RHN and created this profile. Checked In The date and time at which the system last checked in with RHN. Last Booted The date and time at which the system was last started or restarted.
Page 86 Chapter 7. Red Hat Network Website ” for more information about System Groups. It is also possible to lock multiple systems via the System Set Manager. Refer Section 7.4.4.12.4, “System Set Manager Misc Lock Systems — ” to learn how to do so. —...
Page 87 Systems Notifications Indicates the the notification options for this system. You can choose whether you wish to receive email notifying you of available errata updates for this system. In addition, you may choose to include Management-entitled systems in the daily summary email. Auto Errata Update Indicates whether this system is configured to accept updates automatically.
Page 88 Chapter 7. Red Hat Network Website The remaining fields record the physical address at which the system is stored. To confirm any changes to these fields, click the Update Properties button. Note Many of these properties can be set for multiple systems at once through the Section 7.4.4, “System Set Manager —...
Page 89 Systems then be used only once with the rhnreg_ks command line utility to re-register this system and regain Section 4.5, “Registering with Activation Keys” all Red Hat Network settings. Refer to for instructions. Unlike typical activation keys, which are not associated with a specific system ID, keys created here do not show up within the Activation Keys page.
Page 90 Chapter 7. Red Hat Network Website 7.4.2.9.1.8. System Details Details Proxy Activates an RHN Proxy Server. This tab is only available for Provisioning-entitled systems. Select a version of RHN Proxy Server and click the Activate Proxy button to begin the installation and activation process.
Page 91 Systems List/Remove Lists installed packages from the system's software System Profile and enables you to remove them. Click on a package name to view its Package Details page. To delete packages from the system, select their checkboxes and click the Remove Packages button on the bottom right- hand corner of the page.
Page 92 Chapter 7. Red Hat Network Website this system, use the checkboxes next to the channels and click the Change Subscriptions button. You will receive a success message or be notified of any errors. To change the system's base channel, select the new one from the pulldown menu and click the Modify Base Channel button. Refer to Section 7.6.1, “Software Channels”...
Page 93 Systems If you wish to deploy any of these files to the client system, overwriting any changes that have been made locally, check the box to the left of the file and click the Deploy Configuration button. On the following screen, choose a deployment time and click the Schedule Deploy button to confirm. Note If you click on the Filename of a (system override) file, you can edit its contents.
Page 94 Chapter 7. Red Hat Network Website click the Copy to Config Channel button, and select the destination channel. To remove a file, select it and click Delete Selected Files. 7.4.2.9.3.6. System Details Configuration Sandbox This subtab allows you to manipulate configuration files without deploying them. This sandbox provides you with an area in which to experiment with files without affecting your systems.
Page 95 Systems network --bootproto=static --device=eth0 --onboot=on --ip=$IPADDR --gateway=$GATEWAY The $IPADDR will be 192.168.0.28, and the $GATEWAY will be 192.168.0.1 Note There is a hierarchy when creating and using variables in kickstart files. System kickstart variables take precedence over Profile variables, which in turn take precendence over Distribution variables.
Page 96 Chapter 7. Red Hat Network Website by clicking its name in the Snapshot Tags list. To delete tags, select their checkboxes, click Remove Tags, and confirm the action. 7.4.2.9.5. System Details Virtualization This is tab allows you to create a new virtual guest on a host system or allows you to change the status of virtual guests.
Page 97 Systems Once the probe has been added, you must reconfigure your Monitoring Section 7.10.4, “Scout Config Push — infrastructure to recognize it. Refer to ” for details. After the probe has run, its results become available on the Current State page. Refer to Section 7.10.1.7, “Current State —...
Page 98 Chapter 7. Red Hat Network Website Actions can be chained in this manner so that action 'a' requires action 'b' which requires action 'c'. Action 'c' is the first one attempted and has a checkbox next to it until it is completed successfully - if any action in the chain fails, the remaining actions also fail.
Page 99 System Groups — then use the System Set Manager to perform actions on them simultaneously. It is possible to select only those systems that are members of all of the selected groups, excluding those systems that belong only to one or some of the selected groups. To do so, select them and click the Work with Intersection button.
Page 100 Chapter 7. Red Hat Network Website 7.4.3.1. Creating Groups To add a new system group, click the create new group link at the top-right corner of the page. Type a name and description and click the Create Group button. Make sure you use a name that clearly sets this group apart from others.
Page 101 ystem Set Manager — 7.4.3.3.3. System Group Details Target Systems — Target Systems — Lists all systems in your organization. This tab enables you to add systems to the specified system group. Select the systems using the checkboxes to the left and click the Add Systems button on the bottom right-hand corner of the page.
Page 102 Chapter 7. Red Hat Network Website • Tag the most recent snapshots of your selected Provisioning-entitled systems • Revert Provisioning-entitled systems to previous snapshots • Run remote commands on Provisioning-entitled systems Before performing actions on multiple systems, select the systems you wish to modify. To do so, click the List the systems link, check the boxes to the left of the systems you wish to select, and click the Update List button.
Page 103 ystem Set Manager — 7.4.4.4.1. System Set Manager Packages Upgrade — A list of all the packages installed on the selected systems that might be upgraded. Systems must be subscribed to a channel providing the package for the system to be able to upgrade the package. If multiple versions of a package appear, note that only the latest version available to each system is upgraded on that system.
Page 104 Chapter 7. Red Hat Network Website 7.4.4.8. System Set Manager Groups — Tools to create groups and manage group membership. These functions are limited to Satellite Administrators and System Group Administrators. To add a new group, click create new group on the top-right corner.
Page 105 ystem Set Manager — 7.4.4.10.2. System Set Manager Configuration Compare Files — Use this subtab to validate configuration files on the selected systems against copies in your central repository on RHN. The table lists the configuration files associated with any of the selected systems. Clicking its system count displays the systems already subscribed to the file.
Page 106 Chapter 7. Red Hat Network Website using the drop-down menus to configure date and time, then clicking Enable RHN Configuration Management. 7.4.4.11. System Set Manager Provisioning — Options for provisioning systems through the following subtabs: 7.4.4.11.1. System Set Manager Provisioning Kickstart —...
Page 107 ystem Set Manager — 7.4.4.12. System Set Manager Misc — Misc — Update System Profiles and preferences for the system set through the following links: 7.4.4.12.1. System Set Manager Misc System Profile Updates — Click Update Hardware Profile followed by the Confirm Refresh button to schedule a hardware profile update.
Page 108 Chapter 7. Red Hat Network Website 7.4.4.12.7. System Set Manager Misc System Preferences — Toggle the Yes and No radio buttons and click the Change Preferences button to alter your notification preferences for the selected systems. You may apply these preferences to individual systems through the Properties subtab of the System Details page.
Page 109 Advanced Search — • Address — The address of the system or system set • Building — The building or site in an address • Room — The server or system room within a building • Rack — The designated location within a server room where a system is situated. •...
Page 110 Chapter 7. Red Hat Network Website • Days Since Last Check-in — The amount of time (in days) that systems have last checked into RHN Satellite. • Days Since First Check-in — The amount of time (in days) that have passed since the systems first checked into RHN Satellite •...
Page 111 Activation Keys — 7.4.6.1. Managing Activation Keys To generate an activation key: 1. Select Systems => Activation Keys from the top and left navigation bars. 2. Click the create new key link at the top-right corner. Warning In addition to the fields listed below, RHN Satellite customers may also populate the Key field itself.
Page 112 Chapter 7. Red Hat Network Website Figure 7.6. Activation Keys After creating the unique key, it appears in the list of activation keys along with the number of times it has been used. Note that only Activation Key Administrators can see this list. At this point, you may associate child channels and groups with the key so that systems registered with it automatically subscribe to them.
Page 113 Stored Profiles — 7.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 profile. This allows you to aggregate the aspects of various keys without recreating a new key specific to the desired systems, simplifying the registration and kickstart processes while slowing the growth of your key list.
Page 114 Chapter 7. Red Hat Network Website Click create new key at the upper-right corner of the page. Enter a descriptive label and description, such as Asset and Precise location of each system, and click the Create Key. The key will then show up in the custom info keys list.
Page 115 Kickstart — Important If your systems are connected to RHN Hosted servers, you will need an external installation tree for each distribution to be kickstarted. This tree can be hosted anywhere that is accessible by the target system via HTTP. If the systems are connected through an RHN Proxy Server, then you may place the installation tree in /var/www/html/pub/ on the Proxy.
Page 116 Enterprise Linux on multiple machines, making it ideal for network and system administrators. The Red Hat Enterprise Linux System Administration Guide contains an in-depth discussion of kickstart and is available here: http://www.redhat.com/docs/manuals/enterprise/. 7.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 117 Kickstart — 7.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 profiles, you may consider: • A DHCP server is not required for kickstarting, but it can make things easier. If you are using static IP addresses, you should select static IP while developing your kickstart profile.
Page 118 Chapter 7. Red Hat Network Website Next, create the ISO as described in the Making an Installation Boot CD-ROM section of the Red Hat Enterprise Linux 3 Installation Guide. Alternatively, issue the command: mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load- size 4 \ -boot-info-table -R -J -v -T isolinux/ Note that isolinux/ is the relative path to the directory containing the isolinux files from the...
Page 119 Kickstart — 7.4.9.2. Kickstart Profiles Figure 7.8. Kickstart Profiles This page lists all profiles for your organization, whether those profiles are active, and the distribution tree to which that profile is associated. You can either create a new kickstart profile by clicking the create new kickstart profile link, upload or paste the contents of a new kickstart using the upload new kickstart file, or edit an existing profile by clicking the name of the profile.
Page 120 6. On the third page, select a root password for the system. Be sure to follow the password recommendations from the Password Security section of the Red Hat Enterprise Linux Security Guide, available at http://www.redhat.com/docs/manuals/enterprise/. Depending on your base channel, your newly created kickstart profile may be subscribed to a channel that is missing required packages.
Page 121 Kickstart — • Change the Virtualization Type Note Changing the Virtualization Type may require changes to the kickstart profile bootloader and partition options, potentially overwriting user customizations. Consult the Partitioning tab to verify any new or changed settings. • Change the amount of Virtual Memory (in Megabytes of RAM) allocated to virtual guests kickstarted with this profile •...
Page 122 Chapter 7. Red Hat Network Website File Location The exact location from which the kickstart tree is mounted. This value is determined when the profile is created. You can view it on this page but you cannot change it. 7.4.9.3.3. Kickstart Details Variables Kickstart variables can be used to substitute values into kickstart profiles.
Page 123 Kickstart — 7.4.9.3.5. Kickstart Details Bare Metal Kickstart — This sub-tab provides the information necessary to kickstart systems that are not currently registered with RHN. Using the on-screen instructions, you may either kickstart systems using boot media (CD- ROM) or by IP address. 7.4.9.3.6.
Page 124 Enter the package groups, such at @office or @admin-tools you would like to install on the kickstarted system in the large text box on this page. If you would like to know what package groups are available, and what packages they contain, refer to the RedHat/base/ file of your...
Page 125 Kickstart — kickstart tree. Satellite customers will most likely locate this file here: /var/www/satellite/rhn/ kickstart/<kickstart label>/RedHat/base/comps.xml. 7.4.9.3.13. Software Package Profiles — If you have previously created a Package Profile from one of your registered systems, you can use that profile as a template for the files to be installed on a kickstarted system. Refer to Section 7.4.2.9.2.2, “System Details...
Page 126 Chapter 7. Red Hat Network Website machine type and number of disks at kickstart time. This file can be created via %pre script and placed on the system, such as /tmp/part-include. Then you can call for that file by including the following line within the Partition Details field of the System Details Partitioning tab: %include /tmp/part-include...
Page 127 Kickstart — 7.4.9.6. Kickstart Distributions — The Distributions page enables you to find and create custom installation trees that may be used for kickstarting. Note The Distrbutions page does not display Red Hat distributions already provided. They can be found within the Distribution dropdown menu of the Kickstart Details page.) Before creating a distribution, you must make an installation tree available, as described in the Kickstart Installations chapter of the Red Hat Enterprise Linux System Administration Guide.
Page 128: Errata
Chapter 7. Red Hat Network Website network --bootproto=static --device=eth0 --onboot=on --ip=$IPADDR -- gateway=$GATEWAY The $IPADDR will be 192.168.0.28, and the $GATEWAY will be 192.168.0.1 Note There is a hierarchy when creating and using variables in kickstart files. System kickstart variables take precedence over Profile variables, which in turn take precendence over Distribution variables.
Page 129: Relevant Errata
(for Security Updates), and subject of the erratum, as well as the number of affected systems. 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. 7.5.1. Relevant Errata Figure 7.15, “Errata...
Page 130: All Errata
Chapter 7. Red Hat Network Website Figure 7.15. Errata List Clicking on the Advisory takes you to the Details tab of the Errata Details page. Clicking on the number of associated systems takes you to the Affected Systems tab of the Errata Details page. Section 7.5.2.2, “Errata Details”...
Page 131 Refer to for more information. Below Fixes, the specific Bugzilla entries resolved by this erratum are listed. Clicking on any summary text opens that Bugzilla entry at http://bugzilla.redhat.com. Note that you must have a Bugzilla account to view the entry.
Page 132: Advanced Search
Chapter 7. Red Hat Network Website Security updates list the specific vulnerability as tracked by http://cve.mitre.org. This information is listed below the CVEs label. Red Hat provides security update information in OVAL format. OVAL is an open vulnerability and assessment language promoted by Mitre, http://oval.mitre.org. Clicking on the link below the Oval label downloads this information to your system.
Page 133 Advanced Search Figure 7.16. Erratum Search • All Fields — Search errata by synopsis, description, topic, or solution. • Erratum Advisory — The way Red Hat Security Response Team codifies Advisories, such as: RHBA-2007:0530 Searches can be by done year (such as 2007), by type of Advisory (RHBA for Bug fixes, RHEA for Enhancements, and RHSA for Security advisories), or full Advisory name, such as the example above.
Page 134: Software Channels
Chapter 7. Red Hat Network Website CVE-2006-4535 You may also filter errata search results by the type of errata issued. Check or uncheck the boxes next to the type of advisory to search. • Bug Fix Advisory — Errata that contains fixes to issues that were reported by users or discovered during development or testing •...
Page 135 Software Channels For example, administrators can standardize their desktop systems to Red Hat Enterprise Linux 5.1 for x86, while managing servers on Red Hat Enterprise Linux 4.5 for AMD64 and EM64T. Administrators can stay on their version for the duration of the EUS support lifecycle, assured of the behavior of their software version.
Page 136 Chapter 7. Red Hat Network Website Figure 7.17. All Channels 7.6.1.4. Red Hat Channels The Red Hat Channels page displays the Red Hat channels and their available child channels. Versions of Red Hat Enterprise Linux synced directly from RHN Hosted, for example, are listed in this channel.
Page 137 Software Channels 7.6.1.8. 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. 7.6.1.9. Software Channel Details If you click on the name of a channel, the Software Channel Details page appears. This page is broken down into the following tabs: 7.6.1.9.1.
Page 138 Chapter 7. Red Hat Network Website dependencies, the change log, list of files in the package, newer versions, and which systems have the package installed. From here, you can download the packages as RPMs or SRPMs. To search for a specific package or a subset of packages, use the package filter at the top of the list. Enter a substring to search all packages in the list for package names that contain the string.
Page 139: Package Search
Package Search 7.6.2. Package Search Figure 7.18. Package Search The Package Search page allows you to search through packages using various criteria: • Free Form — a general keyword search for users that are unsure of the details of particular package and its contents.
Page 140: Manage Software Channels
Chapter 7. Red Hat Network Website summary:java and description:java Other supported field names for Documentation search include: • name — Search the package names for a particular keyword • version — Search for a particular package's version • filename — Search the package filenames for a particular keyword •...
Page 141: Configuration
Configuration To allow a user to alter the channel, select the checkbox next to the user's name and click the Update button. To allow all users to manage the channel, click the Select All button at the bottom of the list followed by the Update button.
Page 142: Preparing Systems For Config Management
Chapter 7. Red Hat Network Website to as an override channel) and a Sandbox channel. Both central and local configuration management are discussed in detail later in this chapter. 7.7.1. Preparing Systems for Config Management For a system to have its configuration managed through RHN, it must have the appropriate tools and config-enable file installed.
Page 143: Configuration Channels
Configuration Channels 7.7.3. Configuration Channels As mentioned above, RHN manages both central and local configuration channels and files. Central configuration management allows you to deploy configuration files to multiple systems. Local configuration management allows you to specify overrides, or configuration files that are not changed by subscribing the system to a central channel.
Page 144: Configuration Files
Chapter 7. Red Hat Network Website Upload File To upload a file into the configuration channel, browse for the file on your local system, populate all fields, and click the Upload Configuration File button. The Filename/Path field is the absolute path where the file will be deployed. You can also indicate the ownership and permissions to be attached to the file when it is deployed.
Page 145: Locally-Managed Files
Locally-Managed Files Note By default, the maximum file size for configuration files is 128KB. If you need to change that value, find and modify the following line in the /etc/rhn/default/rhn_web.conf file: web.maximum_config_file_size=128 You must also find and change the following line in the /etc/rhn/default/ rhn_server.conf file to the same value: maximum_config_file_size=128 Change the value in both files from 128 to the desired value in kilobytes.
Page 146 Chapter 7. Red Hat Network Website In traditional file management, you would be required to upload and distribute each file separately, even if the distinction is nominal and the number of variations is in the hundreds or thousands. RHN addresses this by allowing the inclusion of macros, or variables, within the configuration files it manages for Provisioning-entitled systems.
Page 147: Systems
Systems To capture custom system information, insert the key label into the custom information macro (rhn.system.custom_info). For instance, if you developed a key labeled "asset" you can add it to the custom information macro in a configuration file to have the value substituted on any system containing it.
Page 148: Schedule
Chapter 7. Red Hat Network Website Note You will still have to perform a few manual steps to enable configuration file deployment, but on-screen instructions are provided to assist with this step. 7.8. Schedule If you click the Schedule tab on the top navigation bar, the Schedule category and links appear. These pages enable you to track the actions taking place within your systems.
Page 149: Failed Actions
Failed Actions Figure 7.19. Schedule - Pending Actions 7.8.2. Failed Actions Actions that could not be completed. If the action returns an error, it is displayed here. 7.8.3. Completed Actions Actions that have succeeded. 7.8.4. Archived Actions Actions that you have selected to store for review. 7.8.5.
Page 150 Chapter 7. Red Hat Network Website • Action — Type of action to perform such as Errata Update or Package Install. Clicking an action name takes you to its Action Details page. Refer to Section 7.8.5.1, “Action Details” for more information.
Page 151 User List Active — Note It is important that the email field is accurate, because the new user must respond to an email sent to that address before they will be able to login to RHN. Once all fields are complete, select the Create Login button. RHN now sends an email to the specified address and redirects you to the Users User List page.
Page 152 Chapter 7. Red Hat Network Website Figure 7.20. User List 7.9.1.1. User List Active User Details — The User Details page allows Satellite Administrators to manage the permissions and activity of all users. Included in the User Details page is the ability to delete or deactivate users. Users may now be deactivated directly from the RHN web interface.
Page 153 User List Active — Warning User deletion is irreversible; exercise it with caution. Consider disabling the user first 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 154 Chapter 7. Red Hat Network Website may change the base channels of systems, make channels globally subscribable, and create entirely new channels. • Configuration Administrator — This role enables the user to manage the configuration of systems in the organization using either the RHN Satellite web-based interface or the Red Hat Network Configuration Manager.
Page 155 User List Active — 7.9.1.1.4. User List Active User Details Channel Permissions — This tab lists all channels available to your organization. You may grant explicit channel subscription permission to this user for each of the channels listed by checking the box to the left of the channel and clicking the Update Permissions button.
Page 156 Chapter 7. Red Hat Network Website 7.9.1.1.6. User List Active User Details Addresses — This tab lists the addresses associated with the user's account. To update this information, click the appropriate Edit this address link, enter the relevant information, and click the Update button. 7.9.1.1.7.
Page 157 Probe Status — Initiate monitoring of a system through the Probes tab of the System Details page. Refer to Section 7.4.2.9, “System Details” Appendix D, Probes for a description of the tab. See for the complete list of available probes. 7.10.1.
Page 158 Chapter 7. Red Hat Network Website • All probes in a given state (OK, WARN, UNKNOWN, CRITICAL, PENDING) • A Probe Event history 7.10.1.1. Probe Status Critical — The probes that have crossed their CRITICAL thresholds or reached a critical status by some other means.
Page 159 Notification — 7.10.1.7. Current State — Identifies the selected probe's status and when it last ran, while providing the ability to generate a report on the probe. Although this page is integral to monitoring, it is found under the Probes tab within the System Details page since its configuration is specific to the system being monitored.
Page 160 Chapter 7. Red Hat Network Website 4. Scope: Determine which monitoring components are subject to the filter. 5. Organization/Scout/Probe: This option allows you to select the organization, scout(s), or probe(s) to which this filter applies. To select multiple items from the list, hold the Ctrl key while clicking the names of the items.
Page 161 Probe Suites Probe Suites page, select the create probe suite link. Enter an easily 1. From the Monitoring distinguishable name for the Probe Suite. You may also choose to add a brief description of the Suite. Click the Create Probe Suite button to continue. 2.
Page 162 Chapter 7. Red Hat Network Website 2. Select the Systems sub-tab. 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 163: Admin
Admin Typically, the defaults provided in other fields are acceptable, since they are derived from your Satellite installation. Nevertheless, you may use the fields on this page to alter your Monitoring configuration. For instance, you may change your mail exchange server here. This page also allows you to alter the destination of all administrative emails from the Satellite.
Page 164: Help
Chapter 7. Red Hat Network Website the /var/www/html/pub/bootstrap/ directory of the Satellite, significantly reduces the effort involved in reconfiguring all systems, which by default obtain packages from the central RHN Servers. The required fields are pre-populated with values derived from previous installation steps. Ensure this information is accurate.
Page 165: Client Configuration Guide
Client Configuration Guide centrally-located server. Client systems then receive these updates from the Proxy rather than by accessing the Internet individually. The RHN Proxy Server Installation Guide provides detailed information regarding RHN Proxy server installation and initial configuration. 7.12.4. Client Configuration Guide By default, all Red Hat Network client applications are configured to communicate with central Red Hat Network Servers.
Page 166 Chapter 7. Red Hat Network Website Figure 7.21. Documentation Search Users can search the available online documentation and filter them according to the following choices in the What to Search drop-down menu: • Content & Title — Search both the title heading or body content of all available documents •...
Page 167 Search If there are several pages of search results, you can limit the amount of visible results shown on one page by clicking the Display quantity items per page drop-down menu, which offers between 10 and 500 results per page. To move between pages, click the right or left angle brackets (>...
Page 169 Chapter 8. Monitoring The Red Hat Network Monitoring entitlement allows you to perform a whole host of actions designed to keep your systems running properly and efficiently. With it, you can keep close watch on system resources, network services, databases, and both standard and custom applications. Monitoring provides both real-time and historical state-change information, as well as specific metric data.
Page 170: Probes Requiring The Daemon
Chapter 8. Monitoring 8.2.1. Probes requiring the daemon An encrypted connection, either through the Red Hat Network Monitoring Daemon or sshd, is required on client systems for the following probes to run: • Linux::CPU Usage • Linux::Disk IO Throughput • Linux::Disk Usage •...
Page 171: Configuring Ssh
Configuring SSH The rhnmd package can be found in the RHN Tools channel for all Red Hat Enterprise Linux distributions. To install it: 1. Subscribe the systems to be monitored to the RHN Tools channel associated with the system. This can be done individually through the System Details Channels Software subtab or for multiple systems at once through the Channel Details...
Page 172: Installing The Ssh Key
Chapter 8. Monitoring 8.2.4. Installing the SSH key Whether you use rhnmd or sshd, you must install the Red Hat Network Monitoring Daemon public SSH key on the systems to be monitored to complete the secure connection. To install it: 1.
Page 173: Notifications
These notifications come in the form of brief text messages sent to either email or pager addresses. Here is an example of an email notification: Subject: CRITICAL: [hostname]: Satellite: Users at 1 From: "Monitoring Satellite Notification" (rogerthat01@redhat.com) Date: Mon, 6 Dec 2004 13:42:28 -0800 To: user@organization.com...
Page 174: Redirecting Notifications
Chapter 8. Monitoring Time: Mon Dec 06, 21:42:25 PST State: CRITICAL System: [hostname] ([IP address]) Probe: Satellite: Users Message: Users 6 (above critical threshold of 2) Notification #116 for Users Run from: RHN Monitoring Satellite As you can see, the longer email notifications contain virtually everything you would need to know about the associated probe.
Page 175: Filtering Notifications
Filtering Notifications Note You can halt or redirect almost all probe notifications by replying to a notification emails with a variation of the command ack suspend host. However, you cannot halt Satellite probe notifications by responding to a probe with ack suspend host or other redirect responses.
Page 176: Managing Probes
Chapter 8. Monitoring entitled to Monitoring, a Probes tab appears within its System Details page. This is where you will conduct most probe-related work. 8.5.1. Managing Probes To add a probe to a system, the system must be entitled to Monitoring. Further, you must have access to the system itself, either as the system's root user, through the System Group Administrator role, or as the Satellite Administrator.
Page 177: Monitoring The Rhn Server
8.6.1. Examining Probes with rhn-catalog To thoroughly troubleshoot a probe, you must first obtain its probe ID. You may obtain this information by running rhn-catalog on the RHN Server as the nocpulse user. The output will resemble: 2 ServiceProbe on example1.redhat.com (199.168.36.245): test 2...
Page 178: Viewing The Output Of Rhn-Runprobe
Chapter 8. Monitoring 3 ServiceProbe on example2.redhat.com (199.168.36.173): rhel2.1 test 4 ServiceProbe on example3.redhat.com (199.168.36.174): SSH 5 ServiceProbe on example4.redhat.com (199.168.36.175): HTTP The probe ID is the first number, while the probe name (as entered in the RHN website) is the final entry on the line.
Page 179 Viewing the output of rhn-runprobe rhn-runprobe --probe=5 --log=all=4 The above command requests the probe output for probeID 5, for all run levels, with a high level of verbosity. More specifically, you may provide the command parameters derived from rhn-catalog, like so: rhn-runprobe 5 --log=all=4 --sshuser=nocpulse --sshport=4545 This yields verbose output depicting the probe's attempted execution.
Page 181: Centrally-Managed Satellite For A Multi-Department Organization
Chapter 9. Multiple Organizations RHN Satellite supports the creation and management of multiple organizations within one Satellite installation, allowing for the division of systems, content, and subscriptions across different organizations or specific groups. This chapter guides the user through basic setup tasks and explains the concepts of multiple organization creation and management within RHN Satellite.
Page 182: Decentralized Management Of Multiple Third Party Organizations
Chapter 9. Multiple Organizations Figure 9.1. Centralized Satellite Management for Multi-Department Organization 9.1.2. Decentralized Management of Multiple Third Party Organizations In this example, the Satellite is maintained by a central group, but each organization is treated separately without relations or ties to the other organizations on the Satellite. Each organization may be a customer of the group that manages the Satellite application itself.
Page 183: General Tips For Multi-Org Usage
Satellite are consuming, you will be unable to activate this new certificate when uploading it through the Satellite's web interface under Admin Satellite Configuration Certificate, uploading it through the http://rhn.redhat.com profile of the Satellite system under the...
Page 184 Chapter 9. Multiple Organizations Satellite tab, or by running the rhn-satellite-activate command. You will get an error stating that there are insufficient entitlements in the certificate. There are a few ways you can reduce Satellite entitlement usage in order to activate your new certificate.
Page 185: Admin Organizations
Admin Organizations Details across various organizations, as well as control an organization's access to systems management tasks. Figure 9.3. Admin The Organizations page contains a listing of organizations across the Satellite, with both User and System counts assigned to each organization. The Organizations page also features a Trusts Section 9.6, “Organizational Trusts”...
Page 186 Chapter 9. Multiple Organizations 9.3. Creating an Organization The Create New Organization page in the RHN Satellite web interface can be accessed by proceeding to Admin Organizations Create New Organization. Administrators can create new organizations and assign entitlements, groups, systems, and users to the group so that organizations can perform administrative tasks on their own without affecting other organizations.
Page 187: Managing Entitlements
Managing Entitlements Satellite Administrators should consider reserving the administrative Organization Administrator account for themselves to have the option of logging into this organization for various reasons. If your Satellite is configured for PAM authentication, avoid using PAM accounts for the administrative organization administrator account in new organizations. Instead, create a Satellite-local account for organization administrators and reserve PAM-authenticated accounts for Satellite logins with less elevated privileges in order to discourage users to frequently log into the Satellite with elevated privileges, as the...
Page 188: Configuring Systems In An Organization
Chapter 9. Multiple Organizations Note Organization Administrators that create a custom channel can only use that channel within their organization unless an Organizational Trust is established between the organizations that want to share the channel. For more information about organizational trusts, refer to Section 9.6, “Organizational Trusts”.
Page 189: Organizational Trusts
Organizational Trusts rhnreg_ks --username=user-123 --password=foobaz Note The --orgid (for Red Hat Enterprise Linux 4 and 5) and --orgpassword (in RHEL 4) parameters in rhnreg_ks are not related to Satellite registration or RHN Satellite's multiple organizations support. 2. Registering Using An Activation Key — You can also register a system to an organization using an activation key from the organization.
Page 190: Sharing Content Channels Between Organizations In A Trust
Chapter 9. Multiple Organizations Figure 9.5. Organizational Trusts Click the checkbox next to the names of the organizations you want to be in the organizational trust with the current organization and click the Modify Trusts button. 9.6.2. Sharing Content Channels between Organizations in a Trust Once an organizational trust has been established, organizations can now share content such as custom software channels with the other organizations in the trust.
Page 191: Migrating Systems From One Trusted Organization To Another
Migrating Systems from One Trusted Organization to Another • Private — Make the channel private so that it cannot be accessed by any organizations except the channel's owner. • Protected — Allow the channel to be accessed by specific trusted organizations of your choice. Note Choosing Protected sharing displays a separate page that prompts you to confirm that you are granting channel access to the organizations by clicking Grant Access...
Page 192 Chapter 9. Multiple Organizations 9.6.3.1. Using migrate-system-profile Using migrate-system-profile is straightforward. You need to ascertain the ID of the system to be migrated, the ID of the organization the system will migrate to, and the hostname or IP address of the Satellite server if you are running the command from another machine.
Page 193 Migrating Systems from One Trusted Organization to Another Figure 9.6. System History Note The Satellite Administrator can migrate a system from one trusted organization to any other in the trust. However, Organization Administrators can only migrate a system from their own organization to another in the trust. Satellite Administrators that need to migrate several systems at once can use the --csv option of migrate-system-profile to automate the process using a simple comma-separated list of systems to migrate.
Page 194: Details Users
Chapter 9. Multiple Organizations For more information about using migrate-system-profile refer to the manual page by typing man migrate-system-profile or for a basic help screen type migrate-system-profile -h. 9.7. Admin Users The Users Across Satellite page contains a list of all users on the Satellite, throughout all organizations.
Page 195 Chapter 10. Virtualization In order to manage and provision your client systems, you must first synchronize content from RHN's central servers to your Satellite. RHN recommends that you sync at least the following channels: • Red Hat Network Tools for RHEL Server (v. 5 for 32-bit x86) — rhn-tools-rhel-i386-server-5 •...
Page 196: Kickstart Your Host System
Chapter 10. Virtualization Note If you are changing the Virtualization Type of an existing kickstart profile, it may also modify the bootloader and partition options, potentially overwriting any user customizations. Be sure to review the Partitioning tab to verify these settings when changing the Virtualization Type.
Page 197 Kickstart Your Host System rhnreg_ks --serverUrl=http://your-satellite.example.com/XMLRPC \ --username=username --password=password Note If your host system is already registered to a different Red Hat Network server, asdd the --force option to the command above. 2. Next, open up the host system's profile in the Satellite web interface. Log into the web interface of your Satellite at https://your-satellite.example.com/.
Page 198 It is possible to use a flash-memory USB key to boot your system in order to kickstart it. Refer to the Red Hat Enterprise Linux System Administration Guide (available at http://www.redhat.com/docs/manuals/enterprise/) for tips on how to do this. Note that your host system's hardware must support boot via these devices.
Page 199 Kickstart Your Host System ks=http://your-satellite.example.com/ks/label/the profile label you created earlier Note For some systems you may either need to add ksdevice=eth0 to the command above or disable one of two or more NICs in the system's BIOS to avoid confusion during the kickstart process.
Page 200 Chapter 10. Virtualization yum install xen kernel-xen rhn-virtualization-host You will then need to edit the /etc/grub.conf configuration file to boot the new xen kernel by default. To do this, select the lines in grub.conf that pertain to the xen kernel from the beginning of the title line to the end of the initrd line, copy the lines, delete them, and paste them so they are the first kernel entry in grub.conf.
Page 201: Setting Up Your Virtual Systems
Setting Up Your Virtual Systems 10.2. Setting Up Your Virtual Systems In order to work with virtual guest systems, you must first create a kickstart profile that will allow you to easily provision virtual guests, then you must provision the guests. 10.2.1.
Page 202: Provision Your Guest Systems
Chapter 10. Virtualization Note As in the previous step, if the default download location is missing, you may not have successfully synced software channel content to your Satellite from Red Hat's servers. 5. For Step 3 of the kickstart profile creation process, choose a root password for the guest system you are provisioning, and click Next to finish creation of the profile.
Page 203: Working With Your Virtual Systems
Working With Your Virtual Systems You may receive the following message from the Kickstart Status page during the guest's kickstart: The install process on the guest system has not communicated to RHN in the past n minutes. This may be due to a hung install process, or it may just be due to a slow install because of hardware constraints.
Page 204: Gaining Console Access Via The Host
Chapter 10. Virtualization 10.3.2. Gaining Console Access Via the Host 1. First you will need to connect to the host system and determine the ID number of the guest you would like to work with. Connect to the host system via ssh and run the following command: xm list This should provide you with a list all of the guests you created on your Satellite, including their ID number.
Page 205: Restarting Guests When Host Reboots
Restarting Guests when Host Reboots yum install -y vim-enhanced 10.3.5. Restarting Guests when Host Reboots By default, when a host system reboots, the guests are not restarted and must be manually started by the administrator. However, the rhn-virtualization-host service can restart guests automatically in the event of a host system reboot.
Page 206 Chapter 10. Virtualization rm /var/lib/xen/disk-images/guest1.disk 4. Finally, you must delete the RHN configuration files from the host system. To locate the RHN configuration file for guest1, run the following command: grep guest1 /etc/sysconfig/rhn/virt/*.xml Then delete the file indicated. For example: rm /etc/sysconfig/rhn/virt/14e5cfbf72342515236ad74b260c2f6b.xml 5.
Page 207: Using Cobbler Check
Chapter 11. Cobbler RHN Satellite features the Cobbler server that allows administrators to centralize their system installation and provisioning infrastructure. Cobbler is an installation server that collects the various methods of performing unattended system installations, whether it be server, workstation, or guest systems in a full or para-virtualized setup.
Page 208: Configuring Cobbler With /Etc/Cobbler/Settings
Chapter 11. Cobbler • httpd — Will check to see if the HTTPD service is running. • iptables — Will remind you that if you are running an IPTables firewall, that you have rules set to allow ports 69 (TFTP), 80 (HTTPD), 25150 and 25151 (Cobbler). Run the cobbler check command as root on your system to see what settings and services need to be enabled to properly run Cobbler on your boot server.
Page 209: Xinetd And Tftp
Xinetd and TFTP 2. Then, the administrator creates a class called PXE, which, if a system that is configured to have PXE first in its boot priority, identifies itself as PXEClient. 3. Then DHCP server then directs the system to the Cobbler server at 192.168.2.1. 4.
Page 210: Syncing And Starting The Cobbler Service
Chapter 11. Cobbler 11.1.5.2. IPTables Configuration Once you have configured SELinux, you must then configure IPTables to allow incoming and outgoing network traffic on the Cobbler server. If you have an existing firewall ruleset using IPTables, you need to add the following rules to open the requisite Cobbler-related ports.
Page 211: Adding A Distribution To Cobbler
Adding a Distribution to Cobbler cobbler sync Then, start the Satellite server: /usr/sbin/rhn-satellite start Warning Do not start or stop the cobblerd service independent of the Satellite service, as doing so may cause errors and other issues. Always use /usr/sbin/rhn-satellite to start or stop RHN Satellite. 11.2.
Page 212: Adding A System To Cobbler
Chapter 11. Cobbler cobbler profile add --name=string --distro=string [--kickstart=url] [-- virt-file-size=gigabytes] [--virt-ram=megabytes] The --name=string is the unique label for the profile, such as rhel5webserver or rhel4workstation . The --distro=string switch specifes the distribution that will be used for this particular profile. Section 11.2, “Adding a Distribution to Cobbler”.
Page 213: Cobbler Templates
Cobbler Templates 11.5. Cobbler Templates Within the RHN Satellite web interface, there are facilities to create variables for use with kickstart Section 7.4.9.3.3, distributions and profiles. For example, to create a kickstart profile variable, refer to “Kickstart Details Variables”. Kickstart variables are a part of an infrastructural change in Satellite to support templating in kickstart files.
Page 214: Using Koan
Chapter 11. Cobbler Kickstart snippets are sections of kickstart code that can be called by a $SNIPPET() function that will be parsed by Cobbler and substitute that function call with the contents of the snippet. For example, if you had a common hard drive partition configuration for all servers, such as: clearpart --all part /boot --fstype ext3 --size=150 --asprimary part / --fstype ext3 --size=40000 --asprimary...
Page 215: Using Koan To Re-Install Running Systems
Using Koan to Re-install Running Systems koan --server=hostname --list-profiles This command lists all of the available profiles created with cobbler profile add. Then, begin the process of creating the image file and starting the installation of the virtual guest system. koan --virt --server=cobbler-server.example.com --profile=virtualfileserver --virtname=marketingfileserver The command specifies that a virtual guest system be created from the Cobbler server (hostname...
Page 217: Unix Support Guide 12.1. Introduction
Chapter 12. UNIX Support Guide 12.1. Introduction This chapter documents the installation procedure for, and identifies differences in, Red Hat Network functionality when used to manage UNIX-based client systems. RHN offers UNIX support to help customers migrate from UNIX to Linux. Because of the limited scope of this task, the features offered for UNIX client management are not as comprehensive as those available for managing Red Hat Enterprise Linux systems.
Page 218: Differences In Functionality
Chapter 12. UNIX Support Guide • The rhn_check program, which checks in with the Satellite and performs any actions scheduled from the server • All Management-level functionality, such as system grouping, package profile comparison, and use of the System Set Manager to administer multiple systems at once •...
Page 219 Satellite Server Preparation/Configuration Enable UNIX support on the Satellite by checking the "Enable Solaris Support" box during the installation process, as pictured: Figure 12.1. Enabling UNIX Support During Satellite Installation 2. After the Satellite has been installed: Enable UNIX support by configuring the Satellite after it has been installed. To do so, select Satellite Tools in the top menubar, then select Satellite Configuration in the left navigation bar.
Page 220: Client System Preparation
Chapter 12. UNIX Support Guide Figure 12.2. Enabling UNIX Support After Satellite Installation Click the Update Configuration button to confirm 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 satellite-sync to create the channel.
Page 221: Download And Install Additional Packages
Download and Install Additional Packages 4. Configure the client applications to connect to the RHN Satellite. Once finished, your systems will be ready to begin receiving RHN updates. The following three section explain these steps in detail. 12.3.1. Download and Install Additional Packages This section steps you through the process of downloading and installing third-party applications and the RHN applications from the Satellite onto the UNIX client.
Page 222 Chapter 12. UNIX Support Guide To verify if a package is installed on the client, use the pkginfo command. For example, to check for a package that contains "zlib" in the name, run the following command: # pkginfo | grep zlib Note Solaris package archive names differ from the name of the installed package.
Page 223 You may choose to use the -n of pkgadd, which runs the command in non-interactive mode. However, this may cause the installation of some packages to fail silently on Solaris Continue until each package is installed in the RHN-specific path: /opt/redhat/rhn/solaris/. 12.3.1.5. Include RHN Packages in the PATH In order to make the RHN packages available at each login, you may wish to add them to your PATH.
Page 224: Deploying Client Ssl Certificates
# man -M /opt/redhat/rhn/solaris/man <man page> Finally, add the Red Hat Libraries to your PATH as you did with libgcc, openssl and zlib. crle -c /var/ld/ld.config -l <current library paths>:/opt/redhat/rhn/ solaris/lib 12.3.2. Deploying Client SSL Certificates To ensure secure data transfer, Red Hat strongly recommends the use of SSL. The RHN Satellite eases implementation of SSL by generating the necessary certificates during its installation.
Page 225: Registration And Updates
Follow these steps on each client system: 1. As root, change to the RHN configuration directory for the system. For Solaris, the full path is / opt/redhat/rhn/solaris/etc/sysconfig/rhn/. 2. Open the up2date configuration file in a text editor. 3. Find the serverURL entry and set its value to the fully qualified domain name (FQDN) of your...
Page 226: Obtaining Updates
Chapter 12. UNIX Support Guide To register UNIX systems with your RHN Satellite, accomplish the following tasks in this order: 1. Log into the Satellite's web interface and click the Systems tab in the top navigation bar followed by Activation Keys in the left navigation bar. Then click the create new key link at the top-right corner of the page.
Page 227 Obtaining Updates on the client as installed entities so they do not appear in the installed packages or patches list. Patch Cluster names look like "patch-cluster-solaris-7_Recommended". The version is a datestring, such as "20040206", the release is always 1 and the epoch is always 0. 12.4.2.1.
Page 228 Chapter 12. UNIX Support Guide Option Description Displays this information and exits -h, --help Prints program usage information and exits -?, --usage Temporary directory to work from --tempdir=<tempdir> Selects the architecture (i386 or Sparc) for multi-arch packages. --select-arch=<arch> Table 12.2. solaris2mpm options 12.4.2.1.2.
Page 229 Obtaining Updates rhnsd --foreground --interval=240 The default location for rhnsd is /opt/redhat/rhn/solaris/usr/sbin/rhnsd. Below are the available options for rhnsd on Solaris: Option Description Run in foreground -f, --foreground Connect to Red Hat Network every MINS minutes -i, --interval=MINS Log all actions to syslog...
Page 230: Remote Commands
/etc/sysconfig/rhn/allowed-actions/ directory specific to your UNIX variant. For instance, in Solaris, issue this command to create the directory: mkdir -p /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script To create the requisite file in Solaris, issue this command: touch /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script/ 12.5.2.
Page 231 Issuing Commands buttons at the top to determine whether the command should run before or after the package action, establish the settings for the command, and click Schedule Package Install/Upgrade. Note that installing multiple packages that have different remote commands requires scheduling the installs separately or combining the commands into a single script.
Page 233 Appendix A. Red Hat Network Registration Client Before you begin using Red Hat Network, you must create a username, password, and System Profile. The Red Hat Network Registration Client walks you through this process. Warning Only systems running Red Hat Enterprise Linux 2.1 need to use the Red Hat Network Registration Client before starting the Red Hat Update Agent.
Page 234 XMLRPC 2. oemInfoFile /etc/sysconfig/rhn/oeminfo 3. enableProxy No 4. networkSetup Yes 5. httpProxy 6. proxyUser 7. serverURL https:// xmlrpc.rhn.redhat.com/XMLRPC 8. proxyPassword 9. debug No Enter number of item to edit <return to exit, q to quit without saving>: Enter the number of the item to modify and enter a new value for the option. When finished changing your configuration, press Enter to save your changes and exit.
Page 235: A.2. Starting The Red Hat Network Registration Client
Starting the Red Hat Network Registration Client httpProxy to the name of the proxy server and port number in the format HOST:PORT. For example, to use the proxy server squid.mysite.org on port 3128, you would change the value to squid.mysite.org:3128. If you require a proxy username and password, set enableProxyAuth to Yes to enable username/ password authentication for the proxy, and set proxyUser and proxyPassword to the appropriate username and password for the proxy.
Page 236 Yes. If you overwrite an existing system registration, you can delete the unused profile via the website at https://rhn.redhat.com. Figure A.3. Warning: This System Already Registered The opening screen for the Red Hat Network Registration Client provides a brief overview of the Figure A.4, “Welcome...
Page 237 Starting the Red Hat Network Registration Client Figure A.4. Welcome Screen Figure A.5, “Red Hat Privacy Statement”). The Red Hat is committed to protecting your privacy (see information gathered during the Red Hat Network registration process is used to create a System Profile.
Page 238: A.3. Registering A User Account
Appendix A. Red Hat Network Registration Client Figure A.5. Red Hat Privacy Statement A.3. Registering a User Account Before you can create a System Profile, you must create a user account. The only required information in this section is a unique username, password, and a valid email address. Figure A.7, “Create a Unique Username and Password”, you must choose In the screen shown in...
Page 239 Registering a User Account Figure A.6. Error: Username Already Exists Note If you are already a member of redhat.com, you can use the same user name and password. However, you must continue with the registration process to create your System Profile.
Page 240: A.4. Registering A System Profile
Appendix A. Red Hat Network Registration Client Figure A.7. Create a Unique Username and Password Most users can leave the Org Info section blank. If you have an existing organization account, work with your Satellite Administrator to ensure that your system is added to that account.This requires entering your organization's ID and password in the provided text fields.
Page 241 Hardware System Profile • Hostname • IP address • CPU model • CPU speed • Amount of RAM • PCI devices • Disk sizes • Mount points Figure A.8, “System Profile The next step is choosing a profile name for your system as shown in Hardware”.
Page 242: A.4.2. Software System Profile
Appendix A. Red Hat Network Registration Client A.4.2. Software System Profile The software System Profile consists of a list of RPM packages for which you wish to receive notifications. The Red Hat Network Registration Client displays a list of all RPM packages listed in the RPM database on your system and then allows you to customize the list by deselecting packages.
Page 243 Software System Profile Figure A.10. RPM Package Information A.4.2.2. Choosing RPM Packages to Exclude from the System Profile By default, all RPM packages in your RPM database are included in your System Profile to be updated by Red Hat Network. To exclude a package, uncheck the package from the list by clicking Figure A.11, “Choose which RPM Packages the checkbox beside the package name.
Page 244: A.5. Finishing Registration
Appendix A. Red Hat Network Registration Client Figure A.11. Choose which RPM Packages to Exclude from System Profile A.5. Finishing Registration Figure A.12, “Finished Collecting Information for System Profile”, the last step of As seen in registration is to confirm that you want to send your System Profile to the Red Hat Network. If you choose Cancel at this point, no information is sent.
Page 245 Finishing Registration Figure A.12. Finished Collecting Information for System Profile Figure A.13, “Send System Profile to Red Hat Network” shows the progress bar displayed while your profile is sent. This process may take some time depending on your connection speed. Figure A.13.
Page 246: A.6. Entitling Your System
Now that you have registered your system, it must be entitled before you can receive updated packages. In other words, you must subscribe it to a service level offering. http://rhn.redhat.com To entitle a system, go to and log in using the same username and password you just used in the Red Hat Network Registration Client.
Page 247: A.7. Text Mode Rhn Registration Client
Text Mode RHN Registration Client Note Removing a required entitlement (such as Provisioning) will not cancel a previously scheduled action (such as a kickstart). As you change the selected entitlements for your systems, the number of available entitlements is updated at the bottom of the screen. A.7.
Page 249: B.1.1. General Command Line Options
Appendix B. Command Line Config Management Tools In addition to the options provided in the RHN website, Red Hat Network offers two command line tools for managing a system's configuration files: the Red Hat Network Configuration Client and the Red Hat Network Configuration Manager. There is a complementary Red Hat Network Actions Control tool that is used to enable and disable configuration management on client systems.
Page 250: B.2. Red Hat Network Configuration Client
Appendix B. Command Line Config Management Tools Option Description --disable-mtime-upload Disable mtime upload --disable-all Disable all options --disable-run Disable script.run --report Report whether the modes are enabled or disabled -f, --force Force the operation without asking first -h, --help show help message and exit Table B.1.
Page 251: B.2.2. Getting A Config File
Getting a Config File in config-channel-14. As a result, the version of the configuration file in config-channel-14 is not deployed for this system, although the file still resides in the channel. The rhncfg-client command does not list the file because it will not be deployed on this system. B.2.2.
Page 252: B.2.5. Verifying Config Files
Appendix B. Command Line Config Management Tools --- /tmp/@3603.0.rhn-cfg-tmp 2004-01-13 14:18:31.000000000 -0500 +++ / etc/example-config.txt 2003-12-16 21:35:32.000000000 -0500 @@ -1,3 +1,5 @@ +additional text In addition, you may include the --topdir option to compare config files in RHN with those located in an arbitrary (and unused) location on the client system, like so: [root@ root]# rhncfg-client diff --topdir /home/test/blah/ /usr/bin/ diff: /home/test/blah/etc/example-config.txt: No such file or directory /...
Page 253: B.3.1. Creating A Config Channel
Creating a Config Channel When the Red Hat Network Configuration Manager is run as root, it attempts to pull in needed configuration values from the Red Hat Update Agent. When run as a user other than root, you may have to make configuration changes within the ~/.rhncfgrc file. The session file is cached in ~/.rhncfg-manager-session to prevent logging in for every command.
Page 254: B.3.3. Differentiating Between Latest Config Files
Appendix B. Command Line Config Management Tools rhncfg-manager add --channel=channel-label /path/to/file In addition to the required channel label and the path to the file, you may use the available options for modifying the file during its addition. For instance, you may alter the path and file name by including the --dest-file option in the command, like: rhncfg-manager add --channel=channel-label--dest-file=/new/path/to/ file.txt/path/to/file...
Page 255: B.3.4. Differentiating Between Various Versions
Differentiating between Various Versions /tmp/dest_path/example-config.txt /home/test/blah/hello_world.txt --- / tmp/dest_path/example-config.txt config_channel: example-channel revision: 1 +++ /home/test/blah/hello_world.txt 2003-12-14 19:08:59.000000000 -0500 @@ -1 +1 @@ -foo +hello, world The following table lists the options available for rhncfg-manager diff: Option Description -cCHANNEL, --channel=CHANNEL Get file(s) from this config channel -rREVISION, --revision=REVISION Use this revision -dDEST_FILE, --dest-file=DEST_FILE...
Page 256: B.3.5. Downloading All Files In A Channel
Appendix B. Command Line Config Management Tools B.3.5. Downloading All Files in a Channel To download all the files in a channel to disk, create a directory and issue the following command: rhncfg-manager download-channel channel-label --topdir . The output resembles the following: Copying /tmp/dest_path/example-config.txt ->...
Page 257: B.3.8. Listing All Config Channels
Listing All Config Channels Option Description -rREVISION, --revision=REVISION Get this file revision -h, --help Show help message and exit Table B.8. rhncfg-manager get options B.3.8. Listing All Config Channels To list all of your organization's configuration channels, issue the command: rhncfg-manager list-channels The output resembles the following: Available config channels: example-channel example-channel2 example-...
Page 258: B.3.11. Determining The Number Of File Revisions
Appendix B. Command Line Config Management Tools rhncfg-manager remove-channel channel-label The output resembles the following: Removing config channel example-channel Config channel example-channel removed B.3.11. Determining the Number of File Revisions To find out how many revisions (revisions go from 1 to N where N is an integer greater than 0) of a file/ path are in a channel, issue the following command: rhncfg-manager revisions channel-label /tmp/dest_path/example-config.txt The output resembles the following:...
Page 259: B.3.13. Uploading Multiple Files At Once
Uploading Multiple Files at Once Option Description -h, --help Show help message and exit Table B.10. rhncfg-manager update options B.3.13. Uploading Multiple Files at Once To upload multiple files to a config channel from local disk at once, issue the command: rhncfg-manager upload-channel --topdir=topdir channel-label The output resembles the following: Using config channel example-channel4 Uploading /tmp/ola_world.txt from...
Page 261: C.2. Obtaining The System_Id
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. The RHN API is based upon XML-RPC, which allows distinct pieces of software on disparate systems to make remote procedure calls using XML over HTTP.
Page 262: C.6. Channel Labels
Appendix C. RHN API Access follows the "=" symbol, as part of a string that resembles the following: "details.pxt?sgid=334958". Note that the member parameter within the set_group_membership method requires only yes or no as input to make the association. C.6. Channel Labels The architecture of a channel is not always clear from the channel label.
Page 263 Sample API Script # http://www.xmlrpc.com/ # We use the Frontier modules, available from: # http://theoryx5.uwinnipeg.ca/mod_perl/cpan-search?dist=Frontier-RPC ############################################################################ ############################################################################ Defining an XMLRPC session. ############################################################################ # Define the host first. This will be the FQDN of your satellite system. my $HOST = 'satellite.server.yourdomain.com'; # Now we create the client object that will be used throughout the session.
Page 264 Appendix C. RHN API Access print Dumper($system); print "\n\nCapturing ID of system @$systems[0]->{name}\n\n"; my $systemid = @$systems[0]->{id}; # This next call returns a list of packages present on this system. # syntax of this call is described at: http://$HOST/rpc/api/system/list_packages/ # This will probably be a pretty long list. my $packages = $client->call('system.list_packages', $session, $systemid);...
Page 265: D.1. Probe Guidelines
Appendix D. Probes Section 7.10, “Monitoring — As described in ”, Monitoring-entitled systems can have probes applied to them that constantly confirm their health and full operability. This appendix lists the available probes broken down by command group, such as Apache.
Page 266: D.2. Apache 1.3.X And 2.0.X
Appendix D. Probes While adding probes, select meaningful thresholds that, when crossed, notify you and your administrators of problems within your infrastructure. Timeout periods are entered in seconds unless otherwise indicated. Exceptions to these rules are noted within the individual probe references. Important Some probes have thresholds based on time.
Page 267: D.2.2. Apache::traffic
Apache::Traffic Field Value Warning Maximum Megabytes Transferred Per Slot Table D.1. Apache::Processes settings D.2.2. Apache::Traffic The Apache::Traffic probe monitors the requests on an Apache Web server and collects the following metrics: • Current Requests — The number of requests being processed by the server at probe runtime. •...
Page 268: D.3. Bea Weblogic 6.X And Higher
Appendix D. Probes Field Value Timeout* Table D.3. Apache::Uptime settings D.3. BEA WebLogic 6.x and higher The probes in this section (with the exception of JDBC Connection Pool) can be configured to monitor the properties of any BEA WebLogic 6.x and higher server (Administration or Managed) running on a given host, even in a clustered environment.
Page 269: D.3.2. Bea Weblogic::heap Free
BEA WebLogic::Heap Free Field Value BEA Server Name* myserver Queue Name* default Critical Maximum Idle Execute Threads Warning Maximum Idle Execute Threads Critical Maximum Queue Length Warning Maximum Queue Length Critical Maximum Request Rate Warning Maximum Request Rate Table D.4. BEA WebLogic::Execute Queue settings D.3.2.
Page 270: D.3.4. Bea Weblogic::server State
Appendix D. Probes Field Value SNMP Port* SNMP Version* BEA Domain Admin Server BEA Server Name* myserver JDBC Pool Name* MyJDBC Connection Pool Critical Maximum Connections Warning Maximum Connections Critical Maximum Connection Rate Warning Maximum Connection Rate Critical Maximum Waiters Warning Maximum Waiters Table D.6.
Page 271: D.4. General
General This probe's transport protocol is User Datagram Protocol (UDP). Field Value SNMP Community String* public SNMP Port* SNMP Version* BEA Domain Admin Server BEA Server Name* myserver Servlet Name* Critical Maximum High Execution Time Warning Maximum High Execution Time Critical Maximum Execution Time Moving Average Warning Maximum Execution Time Moving Average Table D.8.
Page 272: D.4.3. General::snmp Check
Appendix D. Probes • <item key =" "> </item> The remote program will need to output some iteration of the following code to STDOUT: <perldata> <hash> <item key="data">10</item> <item key="status_message">status message here</item> </hash> </perldata> The required value for data is the data point to be inserted in the database for time-series trending. The status_message is optional and can be whatever text string is desired with a maximum length of 1024 bytes.
Page 273: D.4.4. General::tcp Check
General::TCP Check Field Value Warning Minimum Value Critical Minimum Value Table D.11. General::SNMP Check settings D.4.4. General::TCP Check The General::TCP Check probe tests your TCP server by verifying that it can connect to a system via the specified port number. It collects the following metric: •...
Page 274: D.4.6. General::uptime (Snmp)
Appendix D. Probes D.4.6. General::Uptime (SNMP) The General::Uptime (SNMP) probe records the time since the device was last started. It uses the SNMP object identifier (OID) to obtain this value. The only error status it will return is UNKNOWN. Requirements — SNMP must be running on the monitored system and access to the OID must be enabled to perform this probe.
Page 275: D.5.3. Linux::disk Usage
Linux::Disk Usage Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe. Also, the Disk number or disk name parameter must match the format visible when the iostat command is run. If the format is not identical, the configured probe enters an UNKNOWN state.
Page 276: D.5.5. Linux::interface Traffic
Appendix D. Probes • Inodes — The percentage of inodes currently in use. An inode is a data structure that holds information about files in a Linux file system. There is an inode for each file, and a file is uniquely identified by the file system on which it resides and its inode number on that system.
Page 277: D.5.7. Linux::memory Usage
Linux::Memory Usage Field Value Timeout* Critical CPU Load 1-minute average Warning CPU Load 1-minute average Critical CPU Load 5-minute average Warning CPU Load 5-minute average Critical CPU Load 15-minute average Warning CPU Load 15-minute average Table D.20. Linux::Load settings D.5.7. Linux::Memory Usage The Linux::Memory Usage probe monitors the memory on a system and collects the following metric: •...
Page 278: D.5.9. Linux::process Count Total
Appendix D. Probes Field Value 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 D.22.
Page 279: D.5.11. Linux::process Running
Linux::Process Running Specify the process by its command name or process ID. (PID). Entering a PID overrides the entry of a command name. If no command name or PID is entered, the error Command not found is displayed and the probe will be set to a CRITICAL state. Requirements —...
Page 280: D.5.12. Linux::swap Usage
Appendix D. Probes Field Value Critical Maximum Number Running Critical Minimum Number Running Table D.25. Linux::Process Running settings D.5.12. Linux::Swap Usage The Linux::Swap Usage probe monitors the swap partitions running on a system and reports the following metric: • Swap Free — The percent of swap memory currently free. Requirements —...
Page 281: D.5.14. Linux::users
Linux::Users Field Value Remote IP address filter pattern list Remote port number filter Timeout* Critical Maximum Total Connections Warning Maximum Total Connections Critical Maximum TIME_WAIT Connections Warning Maximum TIME_WAIT Connections Critical Maximum CLOSE_WAIT Connections Warning Maximum CLOSE_WAIT Connections Critical Maximum FIN_WAIT Connections Warning Maximum FIN_WAIT Connections Critical Maximum ESTABLISHED Connections Warning Maximum ESTABLISHED Connections...
Page 282: D.6. Logagent
Appendix D. Probes Field Value Critical Minimum Virtual Memory Free Table D.29. Linux::Virtual Memory settings D.6. LogAgent The probes in this section monitor the log files on your systems. You can use them to query logs for certain expressions and track the sizes of files. For LogAgent probes to run, the nocpulse user must be granted read access to your log files.
Page 283: D.6.2. Logagent::log Size
LogAgent::Log Size Field Value Basic regular expression* Timeout* 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 D.30. LogAgent::Log Pattern Match settings D.6.2.
Page 284: D.7. Mysql 3.23 - 3.33
Appendix D. Probes Field Value Critical Maximum Line Rate Warning Maximum Line Rate Warning Minimum Line Rate Critical Minimum Line Rate Table D.31. LogAgent::Log Size settings D.7. MySQL 3.23 - 3.33 The probes in this section monitor aspects of the MySQL database using the mysqladmin binary. No specific user privileges are needed for these probes.
Page 285: D.7.3. Mysql::open Tables
MySQL::Open Tables D.7.3. MySQL::Open Tables The MySQL::Open Tables probe monitors the MySQL server and collects the following metric: • Open Tables — The number of tables open when the probe runs. Field Value Username Password MySQL Port* 3306 Timeout Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects Critical Minimum Open Objects...
Page 286: D.8. Network Services
Appendix D. Probes Field Value Warning Maximum Threads Running Warning Minimum Threads Running Critical Minimum Threads Running Table D.36. MySQL::Threads Running settings D.8. Network Services The probes in this section monitor various services integral to a functioning network. When applying them, ensure that their timed thresholds do not exceed the amount of time allotted to the timeout period.
Page 287: D.8.3. Network Services::imap Mail
Network Services::IMAP Mail Field Value Timeout* Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table D.38. Network Services::FTP settings D.8.3. Network Services::IMAP Mail The Network Services::IMAP Mail probe determines if it can connect to the IMAP 4 service on the system.
Page 288: D.8.6. Network Services::pop Mail
Appendix D. Probes • Round-Trip Average — The time it takes in milliseconds for the ICMP ECHO packet to travel to and from the monitored system. • Packet Loss — The percent of data lost in transit. Although optional, the IP Address field can be instrumental in collecting metrics for systems that have multiple IP addresses.
Page 289: D.8.7. Network Services::remote Ping
Network Services::Remote Ping D.8.7. Network Services::Remote Ping The Network Services::Remote Ping probe determines if the monitored system can ping a specified IP address. It also monitors the packet loss and compares the round trip 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 address.
Page 290: D.8.9. Network Services::secure Web Server (Https)
Appendix D. Probes Field Value Protocol (TCP/UDP) Service Name* Timeout* Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table D.44. Network Services::RPCService settings D.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: •...
Page 291: D.8.11. Network Services::web Server (Http)
Network Services::Web Server (HTTP) Upon successfully contacting the SSH server and receiving a valid response, the probe displays the protocol and server version information. If the probe receives an invalid response, it displays the message returned from the server and generates a WARNING state. Field Value SSH Port*...
Page 292: D.9. Oracle 8I, 9I, And 10G
Appendix D. Probes D.9. Oracle 8i, 9i, and 10g The probes in this section may be applied to instances of the Oracle database matching the versions supported. Oracle probes require the configuration of the database and associations made by running the following command: $ORACLE_HOME/rdbms/admin/catalog.sql In addition, for these probes to function properly, the Oracle user configured in the probe must have...
Page 293: D.9.2. Oracle::availability
Oracle::Availability D.9.2. Oracle::Availability The Oracle::Availability probe determines the availability of the database from the RHN Satellite. Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* Table D.49. Oracle::Availability settings D.9.3. Oracle::Blocking Sessions The Oracle::Blocking Sessions probe monitors an Oracle instance and collects the following metric: •...
Page 294: D.9.5. Oracle::client Connectivity
Appendix D. Probes Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port 1521 Timeout* Warning Minimum Buffer Cache Hit Ratio Critical Minimum Buffer Cache Hit Ratio Table D.51. Oracle::Buffer Cache settings D.9.5. Oracle::Client Connectivity The Oracle::Client Connectivity probe determines if the database is up and capable of receiving connections from the monitored system.
Page 295: D.9.7. Oracle::disk Sort Ratio
Oracle::Disk Sort Ratio Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* Warning Minimum Data Dictionary Hit Ratio Critical Minimum Data Dictionary Hit Ratio Table D.53. Oracle::Data Dictionary Cache settings D.9.7. Oracle::Disk Sort Ratio The Oracle::Disk Sort Ratio probe monitors an Oracle database instance and collects the following metric: •...
Page 296: D.9.9. Oracle::index Extents
Appendix D. Probes Field Value Warning Maximum Idle Sessions Table D.55. Oracle::Idle Sessions settings D.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 297: D.9.11. Oracle::locks
Oracle::Locks Field Value Timeout* Critical Maximum Library Cache Miss Ratio Warning Maximum Library Cache Miss Ratio Table D.57. Oracle::Library Cache settings D.9.11. Oracle::Locks The Oracle::Locks probe monitors an Oracle database instance and collects the following metric: • Active Locks — The current number of active locks as determined by the value in the v$locks table. Database administrators should be aware of high numbers of locks present in a database instance.
Page 298: D.9.13. Oracle::table Extents
Appendix D. Probes Field Value Critical Maximum Redo Log Space Request Rate Warning Maximum Redo Log Space Request Rate Critical Maximum Redo Buffer Allocation Retry Rate Warning Maximum Redo Buffer Allocation Retry Rate Table D.59. Oracle::Redo Log settings D.9.13. Oracle::Table Extents The Oracle::Table Extents probe monitors an Oracle database instance and collects the following metrics: •...
Page 299: D.9.15. Oracle::tns Ping
Oracle::TNS Ping • Available Space Used — The percentage of available space in each tablespace that has been used. Tablespace is the shared pool of space in which a set of tables live. This probe alerts the user when the total amount of available space falls below the threshold. Tablespace is measured in bytes, so extents do not factor into it directly (though each extension removes available space from the shared pool).
Page 300: D.10.2. Rhn Satellite::execution Time
Appendix D. Probes • Space Available — The file size available to the current file system. Field Value Device Pathname* /dev/hda1 Critical Maximum File System Used Warning Maximum File System Used Critical Maximum Space Used Warning Maximum Space Used Critical Maximum Space Available Warning Maximum Space Available Table D.63.
Page 301: D.10.5. Rhn Satellite::load
RHN Satellite::Load a Satellite is overloaded (because it has too many probes with respect to their average execution time), the number goes up. Field Value Critical Maximum Probe Latency Average Warning Maximum Probe Latency Average Table D.66. RHN Satellite::Latency settings D.10.5.
Page 302: D.10.8. Rhn Satellite::processes
Appendix D. Probes • Stopped — The number of processes that have stopped before their executions could be completed. • Sleeping — A process that is in the Interruptible sleep state and that can later be reintroduced into memory, resuming execution where it left off. Field Value Critical Maximum Blocked Processes...
Page 303: D.10.10. Rhn Satellite::process Running
RHN Satellite::Process Running • Virtual Memory Used — The amount of virtual memory in kilobytes being used by the specified process, or the size of the process in real memory plus swap. Specify the process by its command name or process ID. (PID). Entering a PID overrides the entry of a command name.
Page 304: D.10.12. Rhn Satellite::users
Appendix D. Probes D.10.12. RHN Satellite::Users The RHN Satellite::Users probe monitors the number of users currently logged into a Satellite. A CRITICAL status results if the value exceeds the Critical threshold. A WARNING status results if the value exceeds the Warning threshold. Field Value Critical Maximum Users...
Page 305 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 packages.
Page 306 The information includes the topics of the Errata, Bugzilla bug IDs, relevant releases/architectures, solutions including required RPMs, and MD5 checksums for verification. Errata are also available at http://www.redhat.com/errata/. Each RHN Errata Alert is based on the Red Hat Enterprise Linux Errata List.
Page 307 Red Hat Network Daemon The RHN client daemon (rhnsd) that periodically polls Red Hat Network for scheduled actions. Red Hat Network The RHN client application (rhn_register) that collects information Registration Client System Profile Digital about the client system, creates a Certificate , establishes a connection with the Red Hat Network servers, and registers the system with Red Hat Network.
Page 308 Glossary Errata Alert The System Profile is used to determine every relevant to each client system. System Set Manager Interface that allows users to perform actions on multiple systems. Actions include applying Errata Updates, upgrading packages, and adding/removing systems to/from system groups. Update One of the RHN service level offerings.
Page 309 Appendix E. Revision History Revision 1.0 Fri Feb 27 2009...
Page 311 Index Red Hat, 124 Shared, 124 Channels and Packages Channel List, 122 child channel, 122 account client applications deactivate, 65 obtaining, 5 action redirecting, 212 completed systems, 138 client systems details, 138 configuring, 212 failed systems, 138 registering, 213 in progress systems, 138 updating, 214 activation key, 98 Cobbler, 195...
Page 312 Index Errata notifications Process Count Total, 266 automatic updates, 4 Process Counts by State, 265 Errata Updates Process Health, 266 applying, 118 Process Running, 267 searching, 120 Swap Usage, 268 viewing details, 119 TCP Connections by State, 268 viewing list of all errata, 118 Users, 269 viewing list of applicable errata, 117 Virtual Memory, 269...
Page 313 Your Account, 64 Your Preferences, 65 navigation, 55 overview of website, 56 Network Services DNS Lookup, 274 FTP, 274 package installation IMAP Mail, 275 scheduled, 4 Mail Transfer (SMTP), 275 package list Ping, 275 Updating on server, 40, 78 POP Mail, 276 Package Updater (pup) probes, 274 complete description, 15...
Page 314 Index LogAgent Execute Queue, 256 Log Pattern Match, 270 Heap Free, 257 Log Size, 271 JDBC Connection Pool, 257 MySQL Server State, 258 Database Accessibility, 272 Servlet, 258 Open Tables, 273 Probes Opened Tables, 272 Monitoring, 163 Query Rate, 273 probes Threads Running, 273 Apache, 254...
Page 315 applying Errata Updates, 54 synchronizing system profile, 40 configuring, 51 reference guide icons, 53 bug reporting, xii launching RHN website, 54 conventions, xi requirements, 51 introduction to the, xi with a proxy server, 52 registering Red Hat Network Configuration Client with activation keys, 46 rhncfg-client, 238 Registration, 221...
Page 316 Index system list, 68 System Profile, 228 Satellite Administrator, 141 Custom Information, 77 Schedule, 136 Notes, 77 Scheduled Actions Reactivation, 76 Action Details, 138 Updating hardware profile, 77 Actions List, 137 Updating package list, 40, 78 Archived Actions, 137 Updating Properties, 75 Completed Actions, 137 System Set Manager, 89 Failed Actions, 137...
Page 317 in configuration files, 133 WebLogic Execute Queue, 256 Heap Free, 257 JDBC Connection Pool, 257 probes, 256 Server State, 258 Servlet, 258 website, 55 activation keys, 98 All Errata, 118 Channel List, 122 Channels, 122 custom system information, 101 Errata, 116 Erratum Search, 120 Help, 152 language, 65...

Red Hat NETWORK SATELLITE 5.3.0 Reference Manual

Quick Links

Troubleshooting

Related Manuals for Red Hat NETWORK SATELLITE 5.3.0

Summary of Contents for Red Hat NETWORK SATELLITE 5.3.0