Red Hat NETWORK 3.6 - User manual

Red Hat Network 3.6
Reference Guide

Red Hat Network 3.6: Reference Guide
Copyright © 2004 by Red Hat, Inc.
Red Hat, Inc.
1801 Varsity Drive
Raleigh NC 27606-2072 USA
Phone: [phone]
Phone: [phone]
Fax: [phone]
PO Box 13588
Research Triangle Park NC 27709 USA
RHNref(EN)-3.6-Print-RHI (2004-11-09T17:22)
Copyright © 2005 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the
Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright
holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited
unless prior permission is obtained from the copyright holder.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other
countries.
All other trademarks referenced herein are the property of their respective owners.
The GPG fingerprint of the [email protected] key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E

Table of Contents
Introduction to the Guide.................................................................................................................... i
1. Document Conventions.......................................................................................................... i
2. More to Come ...................................................................................................................... iv
2.1. Send in Your Feedback ......................................................................................... iv
1. Red Hat Network Overview ........................................................................................................... 1
1.1. Demo.................................................................................................................................. 2
1.2. Update................................................................................................................................ 2
1.3. Management....................................................................................................................... 2
1.4. Provisioning ....................................................................................................................... 3
1.5. Monitoring ......................................................................................................................... 4
1.6. Errata Notifications and Scheduled Package Installations................................................. 4
1.7. Security, Quality Assurance, and Red Hat Network.......................................................... 4
1.8. Before You Begin............................................................................................................... 5
2. Red Hat Update Agent.................................................................................................................... 7
2.1. Starting the Red Hat Update Agent ................................................................................. 7
2.2. Registration ........................................................................................................................ 9
2.2.1. Registering a User Account .............................................................................. 11
2.2.2. Registering a System Profile............................................................................. 14
2.3. Setup and Use .................................................................................................................. 18
2.3.1. Choosing a Software Channel........................................................................... 19
2.3.2. Choosing Packages to Update........................................................................... 19
2.3.3. Installing Updated Packages ............................................................................. 24
2.3.4. Update Agent Finished ..................................................................................... 25
2.3.5. Command Line Version .................................................................................... 26
2.4. Configuration ................................................................................................................... 30
2.4.1. Using the Red Hat Update Agent Configuration Tool.................................. 30
2.4.2. Command Line Version .................................................................................... 33
2.5. Registering with Activation Keys .................................................................................... 34
3. Red Hat Network Daemon ........................................................................................................... 37
3.1. Configuring ...................................................................................................................... 37
3.2. Viewing Status ................................................................................................................. 37
3.3. Disabling.......................................................................................................................... 37
3.4. Troubleshooting ............................................................................................................... 37
4. Red Hat Network Alert Notification Tool ................................................................................... 39
4.1. Configuring the Applet .................................................................................................... 39
4.2. Notification Icons............................................................................................................. 40
4.3. Viewing Updates .............................................................................................................. 41
4.4. Applying Updates ............................................................................................................ 41
4.5. Launching the RHN Website ........................................................................................... 41
5. Red Hat Network Registration Client......................................................................................... 43
5.1. Configuring the Red Hat Network Registration Client................................................ 43
5.2. Starting the Red Hat Network Registration Client ...................................................... 44
5.3. Registering a User Account ............................................................................................. 47
5.4. Registering a System Profile............................................................................................ 49
5.4.1. Hardware System Profile .................................................................................. 49
5.4.2. Software System Profile.................................................................................... 50
5.5. Finishing Registration...................................................................................................... 52
5.6. Entitling Your System...................................................................................................... 54
5.7. Text Mode RHN Registration Client ............................................................................... 54

6. Red Hat Network Website............................................................................................................ 57
6.1. Navigation........................................................................................................................ 57
6.1.1. Entitlement Views ............................................................................................. 57
6.1.2. Categories and Pages ........................................................................................ 57
6.1.3. Errata Alert Icons.............................................................................................. 59
6.1.4. Quick Search..................................................................................................... 59
6.1.5. Systems Selected............................................................................................... 59
6.1.6. Lists................................................................................................................... 60
6.2. Logging into the RHN Website........................................................................................ 60
6.3. Your RHN ........................................................................................................................ 60
6.3.1. Your Account .................................................................................................... 62
6.3.2. Your Preferences ............................................................................................... 63
6.3.3. Buy Now ........................................................................................................... 63
6.3.4. Purchase History ............................................................................................... 63
6.3.5. Help................................................................................................................... 63
6.4. Systems ............................................................................................................................ 65
6.4.1. Overview — ............................................................................................... 65
6.4.2. Systems ............................................................................................................. 66
6.4.3. System Groups — ...................................................................................... 76
6.4.4. System Set Manager — .............................................................................. 79
6.4.5. System Entitlements ......................................................................................... 84
6.4.6. Advanced Search — ................................................................................... 85
6.4.7. Activation Keys — ..................................................................................... 85
6.4.8. Stored Profiles — ....................................................................................... 87
6.4.9. Custom System Info — .............................................................................. 87
6.4.10. Kickstart — .............................................................................................. 87
6.5. Errata................................................................................................................................ 94
6.5.1. Relevant Errata.................................................................................................. 94
6.5.2. All Errata........................................................................................................... 95
6.5.3. Advanced Search............................................................................................... 97
6.6. Channels........................................................................................................................... 97
6.6.1. Software Channels ............................................................................................ 97
6.6.2. Channel Entitlements ...................................................................................... 100
6.6.3. Easy ISOs........................................................................................................ 100
6.6.4. Package Search ............................................................................................... 101
6.6.5. Software Packages .......................................................................................... 101
6.6.6. Manage Config Channels — .................................................................... 103
6.7. Schedule......................................................................................................................... 108
6.7.1. Pending Actions .............................................................................................. 108
6.7.2. Failed Actions ................................................................................................. 109
6.7.3. Completed Actions.......................................................................................... 109
6.7.4. Archived Actions ............................................................................................ 109
6.7.5. Actions List..................................................................................................... 109
6.8. Users — ................................................................................................................... 110
6.8.1. User Roles....................................................................................................... 110
6.8.2. User List — .............................................................................................. 111
6.9. Monitoring — .......................................................................................................... 114
6.9.1. Probe Status — ......................................................................................... 114
6.9.2. Notification — .......................................................................................... 116
6.9.3. Scout Config Push — ............................................................................... 116

6.9.4. Global Config — ...................................................................................... 117
A. Command Line Config Management Tools ............................................................................. 119
A.1. Red Hat Network Configuration Client .................................................................... 119
A.1.1. Listing Config Files........................................................................................ 119
A.1.2. Getting a Config File...................................................................................... 119
A.1.3. Viewing Config Channels .............................................................................. 119
A.1.4. Differentiating between Config Files............................................................. 120
A.1.5. Verifying Config Files.................................................................................... 120
A.2. Red Hat Network Configuration Manager............................................................... 120
A.2.1. Creating a Config Channel............................................................................. 121
A.2.2. Adding Files to a Config Channel.................................................................. 121
A.2.3. Differentiating between Latest Config Files .................................................. 122
A.2.4. Differentiating between Various Versions...................................................... 122
A.2.5. Downloading All Files in a Channel.............................................................. 123
A.2.6. Getting the Contents of a File ........................................................................ 123
A.2.7. Listing All Files in a Channel ........................................................................ 123
A.2.8. Listing All Config Channels .......................................................................... 123
A.2.9. Removing a File from a Channel ................................................................... 124
A.2.10. Deleting a Config Channel........................................................................... 124
A.2.11. Determining the Number of File Revisions ................................................. 124
A.2.12. Updating a File in a Channel........................................................................ 124
A.2.13. Uploading Multiple Files at Once................................................................ 125
B. RHN API Access......................................................................................................................... 127
B.1. Using the auth Class and Getting the Session ............................................................... 127
B.2. Obtaining the system_id................................................................................................ 127
B.3. Determining the sid ....................................................................................................... 127
B.4. Viewing the cid.............................................................................................................. 127
B.5. Getting the sgid ............................................................................................................. 128
B.6. Sample API Script......................................................................................................... 128
C. Probes .......................................................................................................................................... 131
C.1. Probe guidelines ............................................................................................................ 131
C.2. Apache 1.3.x and 2.0.x.................................................................................................. 131
C.2.1. Apache::Processes.......................................................................................... 132
C.2.2. Apache::Traffic............................................................................................... 132
C.2.3. Apache::Uptime ............................................................................................. 133
C.3. BEA WebLogic 6.x and higher ..................................................................................... 133
C.3.1. BEA WebLogic::Execute Queue.................................................................... 134
C.3.2. BEA WebLogic::Heap Free ........................................................................... 134
C.3.3. BEA WebLogic::JDBC Connection Pool ...................................................... 135
C.3.4. BEA WebLogic::Server State......................................................................... 136
C.3.5. BEA WebLogic::Servlet................................................................................. 136
C.4. General .......................................................................................................................... 137
C.4.1. General::Remote Program.............................................................................. 137
C.4.2. General::Remote Program with Data ............................................................. 137
C.4.3. General::SNMP Check................................................................................... 138
C.4.4. General::TCP Check ...................................................................................... 139
C.4.5. General::UDP Check...................................................................................... 139
C.4.6. General::Uptime (SNMP) .............................................................................. 140
C.5. Linux ............................................................................................................................. 140
C.5.1. Linux::CPU Usage ......................................................................................... 140
C.5.2. Linux::Disk IO Throughput ........................................................................... 141
C.5.3. Linux::Disk Usage.......................................................................................... 141
C.5.4. Linux::Inodes ................................................................................................. 142
C.5.5. Linux::Interface Traffic .................................................................................. 142

C.5.6. Linux::Load.................................................................................................... 143
C.5.7. Linux::Memory Usage ................................................................................... 143
C.5.8. Linux::Process Counts by State ..................................................................... 144
C.5.9. Linux::Process Count Total............................................................................ 144
C.5.10. Linux::Process Health .................................................................................. 145
C.5.11. Linux::Process Running ............................................................................... 146
C.5.12. Linux::Swap Usage ...................................................................................... 146
C.5.13. Linux::TCP Connections by State................................................................ 147
C.5.14. Linux::Users................................................................................................. 148
C.5.15. Linux::Virtual Memory ................................................................................ 148
C.6. LogAgent....................................................................................................................... 148
C.6.1. LogAgent::Log Pattern Match ....................................................................... 149
C.6.2. LogAgent::Log Size ....................................................................................... 150
C.7. MySQL 3.23 - 3.33 ....................................................................................................... 150
C.7.1. MySQL::Database Accessibility.................................................................... 151
C.7.2. MySQL::Opened Tables................................................................................. 151
C.7.3. MySQL::Open Tables .................................................................................... 151
C.7.4. MySQL::Query Rate ...................................................................................... 152
C.7.5. MySQL::Threads Running............................................................................. 152
C.8. Network Services .......................................................................................................... 153
C.8.1. Network Services::DNS Lookup.................................................................... 153
C.8.2. Network Services::FTP .................................................................................. 153
C.8.3. Network Services::IMAP Mail....................................................................... 154
C.8.4. Network Services::Mail Transfer (SMTP) ..................................................... 154
C.8.5. Network Services::Ping.................................................................................. 155
C.8.6. Network Services::POP Mail ......................................................................... 155
C.8.7. Network Services::Remote Ping .................................................................... 156
C.8.8. Network Services::RPCService...................................................................... 157
C.8.9. Network Services::Secure Web Server (HTTPS)........................................... 157
C.8.10. Network Services::SSH................................................................................ 158
C.8.11. Network Services::Web Server (HTTP)....................................................... 158
C.9. Oracle 8i and 9i ............................................................................................................. 159
C.9.1. Oracle::Active Sessions.................................................................................. 159
C.9.2. Oracle::Availability ........................................................................................ 160
C.9.3. Oracle::Blocking Sessions.............................................................................. 160
C.9.4. Oracle::Buffer Cache...................................................................................... 161
C.9.5. Oracle::Client Connectivity............................................................................ 161
C.9.6. Oracle::Data Dictionary Cache ...................................................................... 162
C.9.7. Oracle::Disk Sort Ratio .................................................................................. 162
C.9.8. Oracle::Idle Sessions ...................................................................................... 163
C.9.9. Oracle::Index Extents..................................................................................... 163
C.9.10. Oracle::Library Cache .................................................................................. 164
C.9.11. Oracle::Locks ............................................................................................... 165
C.9.12. Oracle::Redo Log ......................................................................................... 165
C.9.13. Oracle::Table Extents ................................................................................... 166
C.9.14. Oracle::Tablespace Usage ............................................................................ 166
C.9.15. Oracle::TNS Ping ......................................................................................... 167
C.10. RHN Satellite Server................................................................................................... 167
C.10.1. RHN Satellite Server::Check Alive.............................................................. 167
C.10.2. RHN Satellite Server::Disk Space................................................................ 168
C.10.3. RHN Satellite Server::Execution Time ........................................................ 169
C.10.4. RHN Satellite Server::Interface Traffic........................................................ 169
C.10.5. RHN Satellite Server::Latency..................................................................... 169
C.10.6. RHN Satellite Server::Load ......................................................................... 170
C.10.7. RHN Satellite Server::Probe Count.............................................................. 170
C.10.8. RHN Satellite Server::Process Counts ......................................................... 170

C.10.9. RHN Satellite Server::Processes .................................................................. 171
C.10.10. RHN Satellite Server::Process Health........................................................ 171
C.10.11. RHN Satellite Server::Process Running..................................................... 172
C.10.12. RHN Satellite Server::Swap....................................................................... 173
C.10.13. RHN Satellite Server::Users....................................................................... 173
Glossary ........................................................................................................................................... 175
Index................................................................................................................................................. 181

Introduction to the Guide
Welcome to the Red Hat Network 3.6 Reference Guide. The RHN Reference Guide will guide you
through registering your system with Red Hat Network and using its many features.
Since Red Hat Network offers a variety of service levels, from the most basic Update module to the
most advanced Monitoring package, some content of this guide may be inapplicable to you. This is
particularly true of the RHN website, which displays selected categories, pages, and tabs depending
on the entitlement level of the account used to log in. Refer to Chapter 6 Red Hat Network Website to
determine what is available to you.
Depending on which version of Red Hat Enterprise Linux you have installed, the Red Hat Network
Registration Client and the Red Hat Update Agent might be different than the ones described in
this manual as new features are added. Once you use Red Hat Network to update these applications,
you can use the latest version of this manual.
All versions of this manual are available in HTML and PDF formats at
http://www.redhat.com/docs/manuals/RHNetwork/.
This version of the manual covers version 4.2.38 of the Red Hat Enterprise Linux 3 Red Hat Update
Agent and versions 2.9.14 and 2.9.12 of the Red Hat Enterprise Linux 2.1 Red Hat Update Agent
and Red Hat Network Registration Client, respectively.
Warning
Systems running Red Hat Enterprise Linux 2.1 will need to use the separate Red Hat Network
Registration Client before starting the Red Hat Update Agent. Refer to Chapter 5 Red Hat Network
Registration Client for instructions. Systems running Red Hat Enterprise Linux 3 can go directly to
the Red Hat Update Agent, which has registration functionality built in. Refer to Chapter 2 Red Hat
Update Agent for instructions.
For an overview of Red Hat Network offerings, please review the descriptions available at
http://www.redhat.com/software/rhn/ .
1. Document Conventions
When you read this manual, certain words are represented in different fonts, typefaces, sizes, and
weights. This highlighting is systematic; different words are represented in the same style to indicate
their inclusion in a specific category. The types of words that are represented this way include the
following:
command
Linux commands (and other operating system commands, when used) are represented this way.
This style should indicate to you that you can type the word or phrase on the command line
and press [Enter] to invoke a command. Sometimes a command contains words that would be
displayed in a different style on their own (such as file names). In these cases, they are considered
to be part of the command, so the entire phrase is displayed as a command. For example:
Use the cat testfile command to view the contents of a file, named testfile, in the current
working directory.
file name
File names, directory names, paths, and RPM package names are represented this way. This style
should indicate that a particular file or directory exists by that name on your system. Examples:

ii Introduction to the Guide
The .bashrc file in your home directory contains bash shell definitions and aliases for your own
use.
The /etc/fstab file contains information about different system devices and file systems.
Install the webalizer RPM if you want to use a Web server log file analysis program.
application
This style indicates that the program is an end-user application (as opposed to system software).
For example:
Use Mozilla to browse the Web.
[key]
A key on the keyboard is shown in this style. For example:
To use [Tab] completion, type in a character and then press the [Tab] key. Your terminal displays
the list of files in the directory that start with that letter.
[key]-[combination]
A combination of keystrokes is represented in this way. For example:
The [Ctrl]-[Alt]-[Backspace] key combination exits your graphical session and return you to the
graphical login screen or the console.
text found on a GUI interface
A title, word, or phrase found on a GUI interface screen or window is shown in this style. Text
shown in this style is being used to identify a particular GUI screen or an element on a GUI
screen (such as text associated with a checkbox or field). Example:
Select the Require Password checkbox if you would like your screensaver to require a password
before stopping.
top level of a menu on a GUI screen or window
A word in this style indicates that the word is the top level of a pulldown menu. If you click on
the word on the GUI screen, the rest of the menu should appear. For example:
Under File on a GNOME terminal, the New Tab option allows you to open multiple shell
prompts in the same window.
If you need to type in a sequence of commands from a GUI menu, they are shown like the
following example:
Go to Main Menu Button (on the Panel) => Programming => Emacs to start the Emacs text
editor.
button on a GUI screen or window
This style indicates that the text can be found on a clickable button on a GUI screen. For example:
Click on the Back button to return to the webpage you last viewed.
computer output
Text in this style indicates text displayed to a shell prompt such as error messages and responses
to commands. For example:
The ls command displays the contents of a directory. For example:
Desktop about.html logs paulwesterberg.png
Mail backupfiles mail reports

Introduction to the Guide iii
The output returned in response to the command (in this case, the contents of the directory) is
shown in this style.
prompt
A prompt, which is a computer’s way of signifying that it is ready for you to input something, is
shown in this style. Examples:
$
#
[stephen@maturin stephen]$
leopard login:
user input
Text that the user has to type, either on the command line, or into a text box on a GUI screen, is
displayed in this style. In the following example, text is displayed in this style:
To boot your system into the text based installation program, you must type in the text com-
mand at the boot: prompt.
replaceable
Text used for examples, which is meant to be replaced with data provided by the user, is displayed
in this style. In the following example,

version-number

is displayed in this style:
The directory for the kernel source is /usr/src/

version-number

/, where

version-number

is the version of the kernel installed on this system.
Additionally, we use several different strategies to draw your attention to certain pieces of information.
In order of how critical the information is to your system, these items are marked as a note, tip,
important, caution, or warning. For example:
Note
Remember that Linux is case sensitive. In other words, a rose is not a ROSE is not a rOsE.
Tip
The directory /usr/share/doc/ contains additional documentation for packages installed on your
system.
Important
If you modify the DHCP configuration file, the changes do not take effect until you restart the DHCP
daemon.

iv Introduction to the Guide
Caution
Do not perform routine tasks as root — use a regular user account unless you need to use the root
account for system administration tasks.
Warning
Be careful to remove only the necessary INCLUDE partitions. Removing other partitions could result
in data loss or a corrupted system environment.
2. More to Come
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 website and at http://www.redhat.com/docs/.
Note
Although this manual reflects the most current information possible, read the RHN Release Notes for
information that may not have been available prior to our documentation being finalized. The notes
can be found on the RHN website and at http://www.redhat.com/docs/.
2.1. Send in Your Feedback
If you would like to make suggestions about the Red Hat Network Reference Guide, please submit a
report in Bugzilla: http://bugzilla.redhat.com/bugzilla/
Be sure to select the Red Hat Network product and the Documentation component. To easily associate
the problem with this guide, mention its identifier:
RHNref(EN)-3.6-Print-RHI (2004-11-09T17:22)

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 a site that you have never heard of?
Have you ever tried to find an RPM but instead found only the source files that you had to compile
yourself?
Have you ever spent hours or even days visiting different websites to see if you have the latest packages
installed on your system, only to have to do it again in a few months?
Those days are over with Red Hat Network (RHN). RHN provides the solution to all your system
software management needs.
Red Hat Network is an Internet solution for managing a Red Hat Enterprise Linux system or a network
of Red Hat Enterprise Linux systems. All Security Alerts, Bug Fix Alerts, and Enhancement Alerts
(collectively known as Errata Alerts) can be downloaded directly from Red Hat or your own custom
collection. You can even have updates scheduled to be delivered directly to your system as soon as
they are released.
The main components of Red Hat Network are as follows:
•the Red Hat Update Agent
•the Red Hat Network website, whether this is hosted by the central RHN Servers, an RHN Satellite
Server or fed through an RHN Proxy Server
•Red Hat Network Daemon
•the Red Hat Network Registration Client - for systems running Red Hat Enterprise Linux 2.1
only.
The Red Hat Update Agent (up2date) provides your initial connection to Red Hat Network. Once
registered, it enables channel subscription, package installs, and management of System Profiles. Red
Hat Enterprise Linux 3 and newer systems will even use the Red Hat Update Agent to register with
RHN. See Chapter 2 Red Hat Update Agent for further information.
Although both the RHN website and the Red Hat Update Agent allow you to view Errata Alerts
from the Red Hat Errata list and apply updates, the website offers a much more granular view of your
account and provides added functionality required for management and provisioning of systems. For
enterprise deployments of Red Hat Network, the website is a must.
The Red Hat Network Daemon (rhnsd) runs in the background as a service and probes the Red Hat
Network for notifications and updates at set time intervals (see Chapter 3 Red Hat Network Daemon
for further information). This daemon is necessary if you want to schedule updates or other actions
through the website.
The Red Hat Network Registration Client allows you to register your Red Hat Enterprise Linux
2.1 systems with RHN. (Newer versions of Red Hat Enterprise Linux have registration functionality
built into the Red Hat Update Agent.) Registration involves creating a unique RHN username and
password, probing the hardware on your system to create a Hardware Profile, and probing the software
packages installed on your system to create a Package Profile. This information is sent to RHN, and
RHN returns a unique System ID to your system. See Chapter 5 Red Hat Network Registration Client
for more information.

2 Chapter 1. Red Hat Network Overview
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.
Tip
For a comparison chart of RHN service levels, refer to http://www.redhat.com/software/rhn/table/.
1.1. Demo
The RHN Demo service level is the complimentary service level. All users receive one free subscrip-
tion to RHN Demo. All that is required is the completion of a brief survey once every 60 days.
With each Demo subscription, you receive:
•Errata Notifications — Be the first to know about Red Hat’s patches. Subscribe to email errata
notification through Red Hat Network.
•Errata Updates — Immediately bring individual systems up-to-date with the click of a button.
•Search Packages — Search through the full repository of RPMs available to Red Hat Network
users.
•Search Errata — Search through the collection of all errata ever released through Red Hat Network.
1.2. Update
The RHN Update service is ideal for a user with one Red Hat Enterprise Linux system or a small num-
ber of Red Hat Enterprise Linux systems to keep updated. Subscription to Update can be purchased
at http://rhn.redhat.com/purchase_info.pxt.
With each Update subscription, you receive the essential functionality provided to Demo users, plus:
•Easy ISOs — For customers who have purchased subscriptions to Red Hat Network, ISO images
are available for immediate download. Beat the rush to the FTP servers by downloading directly
from Red Hat Network.
•Priority Access during periods of high load — When Red Hat releases a large errata, users with
Priority Access can be guaranteed that they will be able to access the updated packages immediately.
•RHN Support Access — All paying customers of Red Hat Network receive web based support for
their RHN questions.
•Errata Notification, Multiple Systems — Subscriptions for multiple systems means Errata notifi-
cation for Errata to all of those systems. Note that only one email is distributed per each Errata,
regardless of the number of systems affected.
•Errata Updates, Multiple Systems — Get quick updates for multiple systems with an easy button
click for each system.
1.3. Management
In addition to the features offered in the RHN Demo and Update subscription levels, the RHN Manage-
ment subscription service allows you to manage your network of Red Hat Enterprise Linux systems,
users, and system groups through its System Set Manager interface.

Chapter 1. Red Hat Network Overview 3
RHN Management is based upon the concept of an organization. Each Management-level Red Hat
customer has the ability to establish users who have administration privileges to system groups. An
Organization Administrator has overall control over each Red Hat Network organization with the
ability to add and remove systems and users. When users other than the Organization Administrator
log into the Red Hat Network website, they see only the systems they have permission to administer.
To create an account that can be used to entitle systems to RHN Management, go to
https://rhn.redhat.com/ and click on the Create Account link under the Sign In fields. On the Sign
Up for Red Hat Network page, click Create a new Corporate Login. After creating a corporate
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. With each Management subscription, you receive the functionality provided
to Demo and Update users, plus:
•Package Profile Comparison — Compare the package set on a system with the package sets of
similar systems with one click.
•Search Systems — Search through systems based on a number of criteria: packages, networking
information, even hardware asset tags.
•System Grouping — Web servers, database servers, workstations and other workload-focused sys-
tems may be grouped so that each set can be administered in common ways.
•Multiple Administrators — Administrators may be given rights to particular system groups, easing
the burden of system management over very large organizations.
•System Set Manager — You may now apply actions to sets of systems instead of single systems.
Work with members of a predefined system group, or work with an ad-hoc collection of systems.
Install a single software package to each, subscribe the systems to a new channel, or apply all Errata
to them with a single action.
•Batch Processing — Figuring out a list of outdated packages for a thousand systems would take
days for a dedicated sysadmin. Red Hat Network Management service can do it for you in seconds.
1.4. Provisioning
As the highest management service level, RHN Provisioning encompasses all of the features offered
in the RHN Demo, Update, and Management subscription levels. It is designed to allow you to deploy
and manage your network of Red Hat Enterprise Linux systems, users, and system groups.
Like, Management, Provisioning is based upon an organization. But it takes this concept a step fur-
ther by enabling customers with Provisioning entitlements to kickstart, reconfigure, track, and revert
systems on the fly.
In addition to all of the features mentioned in lower service levels, Provisioning provides:
•Kickstarting — Systems with Provisioning entitlements may be re-installed through RHN with a
whole host of options established in kickstart profiles. Options include everything from the type of
bootloader and time zone to packages included/excluded and IP address ranges allowed. Even GPG
and SSL keys can be pre-configured.
•Client Configuration — Customers may use RHN to manage the configuration files on
Provisioning-entitled systems. Users can upload files to RHN’s central configuration manager,
verify local configuration files against those stored by RHN, and deploy files from RHN. Further,
custom configuration channels can be created to help manage this process.
•Snapshot Rollbacks — Provisioning-level users have the ability to revert the package profile, con-
figuration files, and RHN settings of systems. This is possible because snapshots are captured when-

4 Chapter 1. Red Hat Network Overview
ever an action takes place on a system. These snapshots identify groups, channels, packages, and
configuration files.
•Custom System Information — Provisioning customers may identify any type of information they
choose about their systems. This differs from the more rigorous System Profile information and the
completely arbitrary Notes in that it allows you to develop specific keys of your choosing and then
assign searchable values for that key to each Provisioning-entitled system. For instance, this feature
would allow you to identify the cubicle in which each system is located.
1.5. Monitoring
Unlike the other service levels, RHN Monitoring does not include the systems management functions
of other entitlements. Instead it is a separate entitlement available to Management- and Provisioning-
level customers with Red Hat Enterprise Linux systems.
Monitoring allows an organization to install probes that can immediately detect failures and identify
performance degradation before it becomes critical. Used properly, the Monitoring entitlement can
give you insight into the applications, services, and devices on each system.
Specifically, Monitoring provides:
•Probes — Dozens of probes can be run against each system. These range from simple ping checks
to custom remote programs designed to return valuable data.
•Notification — Alerts resulting from probes entering WARNING and CRITICAL states can be sent
to email and pager addresses with contact methods identified by you. Each probe notification can
be sent to a different method, or address.
•Central Status — The results of all probes are summarized in a single Probe Status page, with the
systems affected broken down by state.
•Reporting — By selecting a probe and identifying the particular metric and a range of time, you
can generate graphs and event logs depicting precisely how the probe has performed.
1.6. Errata Notifications and Scheduled Package Installations
You can configure Red Hat Network to send you email notifications of new and updated software
packages as soon as the packages are available through RHN. You receive one email per Errata,
regardless of the number of your systems affected. You can also schedule package installs or package
updates. The benefits include:
•Reduced time and effort required by system administrators to stay on top of the Red Hat Errata list
•Minimized security vulnerabilities in your network by providing the patches as soon as Red Hat
releases them
•Filtered list of package updates (packages not relevant to your network are not included)
•Reliable method of managing multiple systems with similar configurations
1.7. Security, Quality Assurance, and Red Hat Network
Red Hat Network provides significant benefits to your network including security and quality assur-
ance. All transactions made between you and Red Hat Network are encrypted, and all RPM packages
are signed with Red Hat’s GNU Privacy Guard (GPG) signature to ensure authenticity.
Red Hat Network incorporates the following security measures:

Chapter 1. Red Hat Network Overview 5
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. The file is only
readable by the root user on the client system.
3. All notifications and information messages are signed by Red Hat with an electronic signature
using GPG. RPM can be used to verify the authenticity of the package before it is installed.
4. All transactions are encrypted using a Secure Sockets Layer (SSL) connection.
5. All packages are tested and verified by the Red Hat Quality Assurance Team before they are
added to the Red Hat Errata list and Red Hat Network.
1.8. Before You Begin
By default, all the software packages you need to use Red Hat Network are installed with Red Hat
distributions. However, if you chose not to install them during the installation process, you will need
to obtain the Red Hat Update Agent (up2date) and possibly the Red Hat Network Registration
Client (rhn_register). In Red Hat Enterprise Linux 3, registration functionality is built into the
Red Hat Update Agent, while Red Hat Enterprise Linux 2.1 users will need the Red Hat Network
Registration Client.
Warning
The SSL certificate packaged with older versions of the Red Hat Update Agent and the Red Hat
Network Registration Client reached its end of life August 28, 2003. Users attempting to connect
using this certificate will receive SSL connection or certificate verification errors. You may view and
obtain the versions of these applications containing new certificates at the RHN Client Software page.
In the RHN website, click Help at the top-right corner, Get RHN Software in the left navigation bar,
and scroll down to examine the packages and versions.
To determine the versions of the client applications installed, run the rpm -q command followed by
the package name. For instance, for the Red Hat Network Registration Client, type the following
command:
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
Perform this check for every package in Table 1-1 relevant to your system. Remember, only Red Hat
Enterprise Linux 2.1 users need the separate Red Hat Network Registration Client. If you prefer to
use the command line versions, you do not have to install the two packages ending in gnome.

6 Chapter 1. Red Hat Network Overview
Package Name Description
Package Name Description
rhn_register Provides the Red Hat Network Registration Client program and the
text mode interface
rhn_register-gnome Provides the GNOME interface (graphical version) for the Red Hat
Network Registration Client; runs if the X Window System is available
up2date Provides the Red Hat Update Agent command line version and the Red
Hat Network Daemon
up2date-gnome Provides the GNOME interface (graphical version) for the Red Hat
Update Agent; runs if the X Window System is available
Table 1-1. Red Hat Network Packages

Chapter 2.
Red Hat Update Agent
The Red Hat Update Agent is your connection to Red Hat Network. It enables you to register your
systems, create System Profiles, and alter the settings by which your organization and RHN interact.
Once registered, your systems can use the Red Hat Update Agent to retrieve the latest software
packages from Red Hat. This tool will allow you to always have the most up-to-date Red Hat Linux
systems with all security patches, bug fixes, and software package enhancements.
Remember, this tool must be run on the system you wish to update. You cannot use the Red Hat
Update Agent on the system if it is not entitled to an RHN service offering.
Warning
Only systems running Red Hat Enterprise Linux 3 can use the Red Hat Update Agent to register
with RHN. Systems running Red Hat Enterprise Linux 2.1 will need to use the separate Red Hat
Network Registration Client before starting the Red Hat Update Agent. Refer to Chapter 5 Red
Hat Network Registration Client for instructions. Then return to this chapter for instructions on
using the Red Hat Update Agent.
Important
You must use Red Hat Update Agent Version 2.5.4 or higher to upgrade your kernel automatically.
It will install the updated kernel and configure LILO or GRUB to boot the new kernel the next time
the system is rebooted. To ensure you are running the latest version, execute the command up2date
up2date. If you do not have the latest version installed, this command will update it.
2.1. Starting the Red Hat Update Agent
If you are not running the X Window System or prefer the command line version of the Red Hat
Update Agent, skip to Section 2.3.5 Command Line Version.
You must be root to run the Red Hat Update Agent. If you start it as a standard user, you will be
prompted to enter the root password before proceeding. The Red Hat Update Agent can be started
using one of the following methods:
For Red Hat Enterprise Linux 3:
•On the GNOME and KDE desktops, go to the Main Menu Button (on the Panel) => System Tools
=> Red Hat Network.
•At a shell prompt (for example, an xterm or gnome-terminal), type the command up2date.
For Red Hat Enterprise Linux 2.1:
•On the GNOME desktop, go to the Main Menu Button (on the Panel) => Programs => System
=> Update Agent.
•On the KDE desktop, go to the Main Menu Button (on the Panel) => Update Agent.
•At a shell prompt (for example, an xterm or gnome-terminal), type the command up2date.

8 Chapter 2. Red Hat Update Agent
If you choose the last option and start the application from a shell prompt, you can specify the options
in Table 2-1 to the Red Hat Update Agent. 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
Argument Description
--configure Configure Red Hat Update Agent options. Refer to Section 2.4
Configuration for detailed instructions.
-d,--download Download packages only; do not install them. This argument
temporarily overrides the configuration option Do not install
packages after retrieval. Use this option if you prefer to install
the packages manually.
-f,--force Force package installation. This option temporarily overrides the
file, package, and configuration skip lists.
-i,--install Install packages after they are downloaded. This argument
temporarily overrides the configuration option Do not install
packages after retrieval.
-k,--packagedir Specify a colon separated path of directories to look for packages
before trying to download them.
--nosig Do not use GPG to check package signatures. This option
temporarily overrides the saved configuration option.
--tmpdir=directory Temporarily override the configured package directory. The
default location is /var/spool/up2date. This option is useful
if you do not have enough space in the configured location.
--justdb Only add packages to the database and do not install them.
--dbpath=dir Specify an alternate RPM database to use temporarily.
Table 2-1. Graphical Update Agent Options
The first time you run the Red Hat Update Agent, two dialog boxes will appear that you will not see
in subsequent startups: Configure Proxy Server and Install GPG Key.
As shown in Figure 2-1, the first dialog box to appear will prompt you for HTTP Proxy Server informa-
tion. This is useful if your network connection requires you to use a proxy server to make HTTP con-
nections. To use this feature, select the Enable HTTP Proxy checkbox and type your proxy server in
the text field with the format http://HOST:PORT, such as http://squid.mysite.org:3128.
Additionally, if your proxy server requires a username and password, select the Use Authentication
checkbox and enter your username and password in the respective text fields.
An HTTP Proxy Server is not required by Red Hat Network. If you do not want to use this feature,
click the OK button without making any selections. Note that the Red Hat Network Server dropdown
menu at the top of the dialog box is only useful to RHN Proxy and Satellite customers. These cus-
tomers should refer to the RHN Client Configuration Guide for registration steps. Also note this dialox
box is actually the General tab of the Red Hat Update Agent Configuration Tool. Refer to Section
2.4 Configuration for detailed instructions.