-
Language:
English
-
Language:
English
Red Hat Training
A Red Hat training course is available for Red Hat Satellite
Reference Guide
Red Hat Network Satellite
Edition 2
Abstract
Introduction to the Guide
Warning
1. More to Come
Note
1.1. Send in Your Feedback
Chapter 1. Red Hat Network Overview
- the Red Hat Update Agent
- the Red Hat Network website, whether this is hosted by the central RHN Servers, an RHN Satellite, 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.
up2date
) provides your initial connection to Red Hat Network. Red Hat Enterprise Linux 3 and newer systems use the Red Hat Update Agent to register with RHN. 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. Once registered, the Red Hat Update Agent enables channel subscription, package installs, and management of System Profiles. See Chapter 4, Red Hat Update Agent for further information.
rhnsd
) runs in the background as a service and probes the Red Hat Network for notifications and updates at set time intervals (see Chapter 5, Red Hat Network Daemon for further information). This daemon is necessary in order to schedule updates or other actions through the website.
rhn_register
application documented in Chapter 2, The rhn_register
Client, while Red Hat Enterprise Linux 3 and 4 have registration functionality built into the Red Hat Update Agent.
Note
1.1. Update
- Download Software — For customers who have purchased subscriptions to Red Hat Network, ISO images are available for immediate download.
- Priority Access during periods of high load — When Red Hat releases a large erratum, 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 notification for Errata to all of those systems. Note that only one email is distributed per each Erratum, 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.2. Management
- 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 systems 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 — Compiling 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.3. Provisioning
- 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 — RHN Satellite Customers may use RHN to manage the configuration files on Provisioning-entitled systems. Users can upload files to custom configurations channels on the Satellite, verify local configuration files against those stored on the Satellite, and deploy files from the Satellite.
- Snapshot Rollbacks — Provisioning-level users have the ability to revert the package profile and RHN settings of systems. RHN Satellite customers can also roll back local configurations files. This is possible because snapshots are captured whenever 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 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. For instance, this feature allows you to identify the cubicle in which each system is located and search through all registered systems according to their cubicle.
1.4. Monitoring
- 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 can be sent to email and pager addresses with contact methods identified by you when a probe changes state. Each probe notification can be sent to a different method, or address.
- Central Status — 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. This can be instrumental in predicting and preventing costly system failures.
- Probe Suites — Groups of probes may be assigned to a system or set of systems at once rather than individually. This allows Administrators to be certain that similar systems are monitored in the same way and saves time configuring individual probes.
- Notification Filters — Probe notifications may be redirected to another recipient, halted, or sent to an additional recipient for a specified time based on probe criteria, notification method, scout or organization.
1.5. Errata Notifications and Scheduled Package Installations
- Reduced time and effort required by system administrators to stay on top of the Red Hat Errata list
- Minimized security vulnerabilities in your network through the application of updates 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.6. Security, Quality Assurance, and Red Hat Network
- Your System Profile, available at http://rhn.redhat.com, is accessible only with an RHN-verified username and password.
- The Red Hat Quality Assurance Team tests and verifies all packages before they are added to the Red Hat Errata list and Red Hat Network.
1.7. Before You Begin
up2date
) and possibly the Red Hat Network Registration Client (rhn_register
). In Red Hat Enterprise Linux 3 and later, 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
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
rhn_register-2.9.3-1
package rhn_register is not installed
gnome
are not required..
Table 1.1. Red Hat Network Packages
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 |
Chapter 2. The rhn_register
Client
rhn_register
. This application works with the yum
-based RHN Hosted and RHN Satellite client called Package Updater (or pup
)that replaces up2date
. For more information about pup
, refer to Chapter 3, Package Updater.
rhn_register
application normally runs as part of the firstboot
configuration process just after installation. The first time a newly-installed Red Hat Enterprise Linux 5 system is booted, firstboot
uses rhn_register
to register your system with RHN.
2.1. Using rhn_register
firstboot
), you can use rhn_register
to do so. You can execute the command rhn_register
from the command line as root. If you have never registered, you can start rhn_register
by selecting Applications (the main menu on the panel) ⇒ System Tools ⇒ Package Updater. (You will be asked to enter the root password.) The Package Updater, when run on a system that has not yet been registered, triggers rhn_register
if there is no /etc/sysconfig/rhn/systemid
file on the system.
/etc/sysconfig/rhn/systemid
exists on the system, rhn_register
first asks if you are sure that you would like to register again. Doing so may create a duplicate system profile in RHN Satellite. Consider using rhnreg_ks
and activation keys to re-register a system without creating a duplicate entry. Refer to Section 7.4.2.9.1.4, “System Details ⇒ Details ⇒ Reactivation —
” for more information.
Figure 2.1. Verifying Registration
Figure 2.2. Registering for Software Updates
Figure 2.3. Choose an Update Location
Figure 2.4. Enter Your Account Information
Note
Figure 2.5. Create Your System Profile
rhn_register
uploads to RHN or Satellite in this step.
Note
rhnreg_ks
and activation keys to do so.
Figure 2.6. Review System Subscription Details
Figure 2.7. Finish Setting Up Software Updates
Note
2.1.1. Command-line version of rhn_register
rhn_register
that allows you to register your system for access to RHN or Satellite without a graphical desktop environment.
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
rhn_register
has the same configuration screens as the graphical desktop version. However, to navigate the screen, use the directional keys on the keyboard to move left or right and highlight the selections. Press the Space Bar to select an action. Press Tab to move through different navigational elements such as text boxes, checkboxes (which are marked with an x
when selected), and radio buttons (which when selected will be marked with an asterisk).
Chapter 3. Package Updater
pup
) to keep systems updated.
pup
) is the desktop update application for Red Hat Enterprise Linux 5. Using this tool, you can update packages and read details on the updated packages, such as bug fix information, security alerts, enhancements, and more.
3.1. Using the Package Updater
pup
to open the Package Updater.
Figure 3.1. Package Updater Interface
Figure 3.2. Package Dependency
Figure 3.3. Import the GPG Key
Figure 3.4. Reboot Prompt
3.2. The Package Updater Applet
Figure 3.5. Package Updater Applet
- Refresh — Check RHN or the Satellite for new updates
- View Updates — launches the Package Updater application so that you can see any available updates in more detail and configure the updates to your specifications
- Apply Updates — Download and Install all updated packages.
- Quit — close the applet
3.3. Updating Packages from the Command Line with yum
yum
searches supported repositories for packages and their dependencies so they may be installed together in an effort to alleviate dependency issues. Red Hat Enterprise Linux 5 uses yum
to fetch packages and install packages.
up2date
is not available on Red Hat Enterprise Linux 5, which uses Yum (Yellowdog Updater Modified). The entire stack of tools that installs and updates software in Red Hat Enterprise Linux 5 is now based on Yum. This includes everything from the initial installation via Anaconda
installation program to host software management tools like pirut.
3.3.1. yum
Commands
yum command [package_name]
yum
commands. For a complete list of available yum commands, refer to man yum
.
yum install package_name
- Used to install the latest version of a package or group of packages. If no package matches the specified package name(s), they are assumed to be a shell wildcard, and any matches are then installed.
- yum update package_name
- Used to update the specified packages to the latest available version. If no packages are specified, then
yum
will attempt to update all installed packages.If the--obsoletes
option is used (i.e.yum --obsoletes package_name
), yum will process obsolete packages. As such, packages that are obsoleted across updates will be removed and replaced accordingly. - yum check-update
- This command allows you to determine whether any updates are available for your installed packages.
yum
returns a list of all package updates from all repositories if any are available. - yum remove package_name
- Used to remove specified packages, along with any other packages dependent on the packages being removed.
- yum provides package_name
- Used to determine which packages provide a specific file or feature.
- yum search keyword
- This command is used to find any packages containing the specified keyword in the description, summary, packager and package name fields of RPMs in all supported repositories.
- yum localinstall absolute path to filename
- Used when using yum to install a package located locally in the machine.
Chapter 4. Red Hat Update Agent
Warning
rhn_register
Client for instructions, then return to this chapter for Red Hat Update Agent instructions.
Important
up2date up2date
. If you do not have the latest version installed, this command updates it.
4.1. Starting the Red Hat Update Agent
- On the GNOME and KDE desktops, Applications (the main menu on the panel) => Add/Remove Software.
- At a shell prompt (for example, an xterm or gnome-terminal), type the command
system-config-packages
.
- On the GNOME and KDE desktops, go to Applications (the main menu on the panel) => System Tools => Red Hat Network.
- At a shell prompt (for example, an xterm or gnome-terminal), type the command
up2date
.
up2date --help
.
up2date --tmpdir=/tmp/up2date/
Table 4.1. Graphical Update Agent Options
Option | Description |
---|---|
--configure | Configure Red Hat Update Agent options. Refer to Section 4.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 in which 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. |
--dbpath=dir | Specify an alternate RPM database to use temporarily. |
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.
Figure 4.1. Configure Proxy Server
Figure 4.2. Install GPG Key
4.2. Registration
up2date --register
Important
Figure 4.3. Welcome Screen
4.2.1. Registering a User Account
up2date
).
Important
Figure 4.4. Red Hat Login Screen
- Cannot contain any spaces
- Cannot contain the characters & +, %, or '
- Is not case-sensitive, thereby eliminating the possibility of duplicate usernames differing only by capitalization
- Must be at least four characters long
- Cannot contain any tabs
- Cannot contain any line feeds
Note
Figure 4.5. Create a User Account
4.2.2. Activate
- Red Hat Enterprise Linux version
- Hostname
- IP address
- CPU model
- CPU speed
- Amount of RAM
- PCI devices
- Disk sizes
- Mount points
Note
Figure 4.6. Activate
Figure 4.7. Sending System Profile to Red Hat Network
4.2.3. Channels
Figure 4.8. Channels
Figure 4.9. Fetching package list
Note
up2date
on your system is older than the one in your selected channel, the Red Hat Update Agent asks whether you would like to update it. If you agree, the only package that will be updated is the up2date
package. This is equivalent to executing the up2date up2date
command from a shell prompt. Once the updated process has completed, the Red Hat Update Agent restarts and completes the initial update of the system.
4.2.4. Packages Flagged to be Skipped
Figure 4.10. Packages Flagged to be Skipped
4.2.5. Available Package Updates
Figure 4.11. Available Package Updates
Figure 4.12. Example Errata Advisory
4.2.6. Retrieving Packages
/var/spool/up2date/
.
Figure 4.13. Retrieving Packages
4.2.7. Installing Packages
Figure 4.14. Installing Packages
Figure 4.15. All Finished
4.3. Command Line Version
up2date --nox
up2date -u
Table 4.2. Update Agent Command Line Arguments
Option | Description |
---|---|
-? , --usage | Briefly describe the available options. |
-h , --help | List the available options and exit. |
--arch=architecture | Force up2date to install this architecture of the package. Not valid with --update , --list , or --dry-run . |
--channel=channel | Specify from which channels to update using channel labels. |
--configure | Configure Red Hat Update Agent options. Refer to Section 4.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. |
--dbpath=dir | Specify an alternate RPM database to use temporarily. |
--dry-run | Do everything but download and install packages. This is useful in checking dependencies and other requirements prior to actual installation. |
-f , --force | Force package installation. This option temporarily overrides the file, package, and configuration skip lists. |
--firstboot | Pop up in the center of the screen for Firstboot. |
--get | Fetch the package specified without resolving dependencies. |
--get-source | Fetch the source package specified without resolving dependencies. |
--gpg-flags | Show the flags with which GPG is invoked, such as the keyring. |
--hardware | Update this system's hardware profile on RHN. |
-i , --install | Install packages after they are downloaded. This argument temporarily overrides the configuration option Do not install packages after retrieval. |
--installall=<channel-label> | Install all available packages from a given channel |
--justdb | Only add packages to the database and do not install them. |
-k , --packagedir | Specify a colon-separated path of directories in which to look for packages before trying to download them. |
-l , --list | List packages relevant to the system. |
--list-rollbacks | Show the package rollbacks available. |
--nodownload | Do not download packages at all. This is useful in testing. |
--nosig | Do not use GPG to check package signatures. This option temporarily overrides the saved configuration option. |
--nosrc | Do not download source packages (SRPMs). |
--nox | Do not attempt to run in X. This launches the command line version of the Red Hat Update Agent. |
-p , --packages | Update packages associated with this System Profile. |
--proxy=proxy URL | Specify an HTTP proxy to use. |
--proxyPassword=proxy password | Specify a password to use with an authenticated HTTP proxy. |
--proxyUser=proxy user ID | Specify a username to use with an authenticated HTTP proxy. |
--register | Register (or re-register) this system with RHN. Refer to Section 4.2, “Registration” for detailed instructions. |
--serverUrl=server URL | Specify an alternate server from which to retrieve packages. |
--showall | List all packages available for download. |
--show-available | List all packages available that are not currently installed. |
--show-channels | Show the channel name associated with each package. |
--show-orphans | List all packages currently installed that are not in channels to which the system is subscribed. |
--show-package-dialog | Show the package installation dialog in GUI mode. |
--solvedeps=dependencies | Find, download, and install the packages necessary to resolve dependencies. |
--src | Download source packages, as well as binary RPMs. |
--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. |
-u , --update | Update system with all relevant packages. |
--undo | Reverse the last package set update. |
--upgrade-to-release=release version | Upgrade to the channel specified. |
--uuid=uuid | Pass in a Unique User ID generated by the Alert Notification tool. |
-v , --verbose | Show additional output while updating. |
--version | Show up2date version information. |
--whatprovides=dependencies | Show the packages that resolve the comma-separated list of dependencies. |
Note
--solvedeps
and --whatprovides
options can be used to solve the dependencies for an RPM regardless even if your system does not currently have access to a channel that contains that package.
4.3.1. Installing the Red Hat GPG key
Your GPG keyring does not contain the Red Hat, Inc. public key. Without it, you will be unable to verify that packages Update Agent downloads are securely signed by Red Hat.
Note
rpm --import /usr/share/doc/rpm-4.1/RPM-GPG-KEY
gpg
command (as root):
/usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY
Type bits/keyID Date User ID pub 1024D/650D5882 2001-11-21 Red Hat, Inc. (Security Response Team) sub 2048g/7EAB9AFD 2001-11-21 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.1 (GNU/Linux) mQGiBDv70vQRBADh701rf8WUzDG88kqlV/N5KQ1PF0amnODB/1EeuAD7n6bCBRmV ekQWJCdfab0Rf1S+VsFg6IAAAmDIarVnacTLQzqCdGJqTpXm/rGVpLv+mCh+OmT9 QRFbjSzB0uPJOpiIvJwSS00D/wJ8XKzHkVNgW3DiJ9Qz2BHYszU2ISI6FwCgxY6d IVjWT5jblkLNjtD3+fR024ED/i0e2knetTX3S9LjC+HdGvP8Eds92Ti2CnJLaFJk Rp749PucnK9mzxPcO2jSHgdtjWAXst/st+gWFVbFmkjBQDVSd00B/xEwI1T1+LN8 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-----
4.3.2. Manual Package Installation
/var/spool/up2date
. Type the command rpm -Uvh *.rpm
. When the packages finish installing, you can delete them if you wish. You do not need them anymore.
4.3.3. Synchronizing Your System Profile
rhn-profile-sync
up2date -p
4.3.4. Log File
/var/log/up2date
. It uses the standard rotating log method. Thus, older logs are in /var/log/up2date.1
, /var/log/up2date.2
, and /var/log/up2date.3
. The log files store actions performed by the Red Hat Update Agent such as when your RPM database is opened, when it connects to Red Hat Network to retrieve information from your System Profile, which packages are downloaded, which packages are installed using the Red Hat Update Agent, and which packages are deleted from your system after installation. If you choose to install and delete packages yourself, it is not logged in this file. Red Hat Network recommends that you keep a log of actions not performed with the Red Hat Update Agent.
4.4. Configuration
4.4.1. Using the Red Hat Update Agent Configuration Tool
up2date --config
at a shell prompt (for example, an xterm or a gnome-terminal).
4.4.1.1. General Settings
squid.mysite.org:3128
in the text field. Additionally, if your proxy server requires a username and password, select the Use Authentication option and enter your username and password in the respective text fields.
Figure 4.16. General Settings
4.4.1.2. Retrieval/Installation Settings
Warning
Figure 4.17. Retrieval/Installation Settings
- Do not install packages after retrieval — download selected RPM packages to the desired directory and ignore the installation preferences
- Do not upgrade packages when local configuration file has been modified — if the configuration file has been modified for a package such as
apache
orsquid
, do not attempt to upgrade it. This option is useful if you are installing custom RPMs on your system and you do not want them updated or reverted to the default Red Hat Enterprise Linux packages. - Retrieve source RPM along with binary package — download both the source (
*.src.rpm
) and the binary (*.[architecture].rpm
) files
- Use GPG to verify package integrity — before installing packages, verify Red Hat's GPG signature (highly recommended for security reasons)
- After installation, keep binary packages on disk — save binary packages in the desired directory instead of deleting them after installation
- 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. Package Exceptions Settings
kernel*
is in the Package Names to Skip section, the Red Hat Update Agent will not display any packages beginning with kernel.
Figure 4.18. Package Exceptions Settings
4.4.2. Command Line Version
/etc/sysconfig/rhn/up2date
.
up2date --nox --configure
0. debug No 1. isatty Yes 2. depslist [] 3. networkSetup Yes 4. retrieveOnly No 5. enableRollbacks No 6. pkgSkipList ['kernel*'] 7. storageDir /var/spool/up2date 8. adminAddress ['root@localhost'] 9. noBootLoader No 10. serverURL https://xmlrpc.rhn.redhat.com/XMLRPC 11. fileSkipList [] 12. sslCACert /usr/share/rhn/RHNS-CA-CERT 13. noReplaceConfig Yes 14. useNoSSLForPackage No 15. systemIdPath /etc/sysconfig/rhn/systemid 16. enableProxyAuth No 17. retrieveSource No 18. versionOverride 19. headerFetchCount 10 20. networkRetries 5 21. enableProxy No 22. proxyPassword 23. noSSLServerURL http://xmlrpc.rhn.redhat.com/XMLRPC 24. keepAfterInstall No 25. proxyUser 26. removeSkipList ['kernel*'] 27. useGPG Yes 28. gpgKeyRing /etc/sysconfig/rhn/up2date-keyring.gpg 29. httpProxy 30. headerCacheSize 40 31. forceInstall No Enter number of item to edit <return to exit, q to quit without saving>:
Important
up2date
uses SSL only. For this reason, users should ensure that their firewalls allow connections over port 443. To bypass SSL, change the protocol for serverURL from https
to http
in the /etc/sysconfig/rhn/up2date
configuration file.
4.5. Registering with Activation Keys
up2date
offers a utility aimed at batch processing system registrations: activation keys. Each unique key can be used to register Red Hat Enterprise Linux systems, entitle them to an RHN service level, and subscribe them to specific channels and system groups, all in one action. This automation bypasses entitlement and registration via Red Hat Network Registration Client and Red Hat Update Agent.
rhnreg_ks
as part of their packages.
Note
rhn_register
package. It is highly recommended that you obtain the latest version before using activation keys.
rhnreg_ks --activationkey=7202f3b7d218cf59b764f9f6e9fa281b
--serialnumber
option for the --activationkey
option:
rhnreg_ks --serialnumber=7202f3b7d218cf59b764f9f6e9fa281b
rhnreg_ks --activationkey=7202f3b7d218cf59b764f9f6e9fa281b,\ 39f41081f0329c20798876f37cb9p6a3
Note
\
) in this command example is a continuation character; it may safely be omitted.
rhnreg_ks
.
/etc/sysconfig/rhn/systemid
.
- A key may specify either zero or one base channel. If specified, it must be a custom base channel. If not, the base channel corresponding to the system's Red Hat distribution is chosen. For instance, you may not subscribe a Red Hat Enterprise Linux 2.1 system to the Red Hat Enterprise Linux 3 channel.
- A key may specify any number of child channels. For each child channel, subscription is attempted. If the child channel matches the system's base channel, subscription succeeds. If it does not, the subscription fails silently. Refer to Section 7.6, “Channels” for more information.
- Keys may be modified by any user with the role of Activation Key Administrator or Satellite Administrator (or both). These permissions are set through the Users tab of the RHN website. Refer to Section 7.9, “Users — ” for details.
- 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.
4.6. Registering a System to an Organization
salesadmin
and password abc123
, using these credentials assures that a system is registered to the proper organization.
rhnreg_ks --user=salesadmin --password=abc123
Important
--orgid
option (for RHEL 4 and 5) and the --orgpassword
option (in RHEL 4) in the rhnreg_ks
command are not related to the Organizations feature and should not be used in the context of registering systems to organizations.
Chapter 5. Red Hat Network Daemon
rhnsd
) periodically connects to Red Hat Network Satellite to check for updates and notifications. The daemon, which runs in the background, is typically started from the initialization scripts in /etc/init.d/rhnsd
or /etc/rc.d/init.d/rhnsd
.
rhnsd
runs an external program called rhn_check
located in /usr/sbin/
. This is a small application that makes the network connection to RHN. The Red Hat Network Daemon does not listen on any network ports or talk to the network directly. All network activity is done via the rhn_check
utility.
5.1. Configuring
/etc/sysconfig/rhn/rhnsd
configuration file. This is actually the configuration file the rhnsd
initialization script uses. The most important setting offered by the daemon is its check-in frequency. The default interval time is four hours (240 minutes). If you modify the configuration file, you must (as root) restart the daemon with the command service rhnsd restart
or /etc/rc.d/init.d/rhnsd restart
.
Important
5.2. Viewing Status
service rhnsd status
or /etc/rc.d/init.d/rhnsd status
at a shell prompt.
5.3. Disabling
chkconfig rhnsd off
. Using these two methods only disables the service the next time the system is started. To stop the service immediately, use the command service rhnsd stop
or /etc/rc.d/init.d/rhnsd stop
.
5.4. Troubleshooting
- 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
- 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.
Chapter 6. Red Hat Network Alert Notification Tool
rhn-applet
RPM package and use the X Window System.
Figure 6.1. GNOME Panel with Red Hat Network Alert Notification Tool
- In Red Hat Enterprise Linux 4 and later, select Applications (the main menu on the panel) => System Tools => Red Hat Network Alert Icon. To ensure the icon appears on subsequent sessions, select the Save current setup checkbox when logging out.
- In Red Hat Enterprise Linux 2.1, select the Main Menu Button => Panel => Add to Panel => Applet => Red Hat Network Monitor. To move it around the panel, right-click on the applet, select Move, move the mouse left and right until it is in the desired location, and click the mouse to place the applet.
6.1. Configuring the Applet
Figure 6.2. HTTP Proxy Configuration
squid.mysite.org:3128
in the text field. Additionally, if your proxy server requires a username and password, select the Use Authentication option and enter your username and password in the respective text fields.
Note
.rhn-applet.conf
file in your home directory. The Red Hat Network Alert Notification Tool also uses the system-wide configuration file /etc/sysconfig/rhn/rhn-applet
. The setting for server_url should be set to your satellite server. For example:
server_url=http://YourRHN_Satellite.com/APPLET
server_url=https://YourRHN_Satellite.com/APPLET
6.2. Notification Icons
Table 6.1. Red Hat Network Alert Notification Tool Icons
Icon | Description |
---|---|
Updates are available | |
System is up-to-date | |
Checking for updates | |
Error has occurred |
6.3. Viewing Updates
Figure 6.3. Available Updates
6.4. Applying Updates
6.5. Launching the RHN Website
Chapter 7. Red Hat Network Website
7.1. Navigation
Figure 7.1. Top Navigation bar — RHN Satellite
Figure 7.2. Left Navigation Bar — Users
Figure 7.3. Sub-Tabs — System Details
7.1.1. Entitlement Views
Table 7.1. Entitlement Icons
Icon | Entitlement |
---|---|
Management or higher | |
Provisioning | |
Monitoring |
7.1.2. Categories and Pages
- Overview — View and manage your primary account information and obtain help.
- Overview — Obtain a quick overview of your account. It notifies you if your systems need attention, provides a quick link to go directly to them, and displays the most recent Errata Alerts for your account.
- Your Account — Update your personal profile and addresses.
- Your Preferences — Indicate if you wish to receive email notifications about Errata Alerts for your systems, set how many items are displayed at one time for lists such as system lists and system group lists, set your time zone, and identify your contact options.
- Locale Preferences — Configure language, timezone, and other customizations for your particular locale.
- Subscription Management — Manage base and add-on system entitlements, such as Management, Provisioning, and Virtualization.
- Systems — Manage all of your systems (including virtual guest systems) here.
- Overview — — View a summary of your systems or system groups showing how many Errata Alerts each system has and which systems are entitled.
- Systems — Select and view subsets of your systems by specific criteria, such as Virtual Systems, Unentitled, Recently Registered, Proxy, and Inactive.
- System Groups — — List your system groups. Create additional groups.
- 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.
- Activation Keys — — Generate an activation key for an RHN-entitled system. This activation key can be used to grant a specified level of entitlement or group membership to a newly registered system with the
rhnreg_ks
command. - Stored Profiles — — View system profiles used to provision systems.
- Custom System Info — — Create and edit system information keys containing completely customizable values that can be assigned while provisioning systems.
- Kickstart — — Display and modify various aspects of kickstart profiles used in provisioning systems.
- Errata — View and manage Errata Alerts here.
- Errata — List Errata Alerts and download associated RPMs.
- Advanced Search — Search Errata Alerts based on specific criteria, such as synopsis, advisory type, and package name.
- Manage Errata — Manage the errata for an organization's channels.
- Clone Errata — Clone errata for an organization for ease of replication and distribution across an organization.
- Channels — View and manage the available RHN channels and the files they contain.
- Software Channels — View a list of all software channels and those applicable to your systems.
- Package Search — Search packages using all or some portion of the package name, description, or summary, with support for limiting searches to supported platforms.
- 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
- Configuration Channels — List and create configuration channels from which any subscribed system can receive configuration files
- Configuration Files — List and create files from which systems receive configuration input
- Systems — List the systems that have RHN-managed configuration files.
- Schedule — Keep track of your scheduled actions.
- Pending Actions — List scheduled actions that have not been completed.
- Failed Actions — List scheduled actions that have failed.
- Completed Actions — List scheduled actions that have been completed. Completed actions can be archived at any time.
- Archived Actions — List completed actions that have been selected to archive.
- Users — — View and manage users for your organization.
- User List — — List users for your organization.
- Monitoring — — Run probes and receive notifications regarding systems.
- Status — — View probes by state.
- Notification — — View contact methods established for your organization.
- Probe Suites — — 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.
- Organizations — List and create new organizations
- Subscriptions — List and manage the software and system entitlements for all organizations across the Satellite.
- Users — List all users on the Satellite, across all organizations. Click individual usernames to change administrative privileges for the user.
Note
Users created for organization administration can only be configured by the organization administrator, not the Satellite administrator. - Satellite Configuration — Make general configuration changes to the Satellite, including Proxy settings, Certificate configuration, Bootstrap Script configuration, Organization changes, and Restart the Satellite Server.
- Task Engine Status — configures the daemon that runs on the Satellite server itself and performs routine operations, such as database cleanup, Errata mailings, and other tasks that are performed in the background.
7.1.3. Errata Alert Icons
7.1.4. Quick Search
test-1.example.com
that is registered to the Satellite, but you misspell your query tset
, the test-1.example.com system still appears in the search results
Note
7.1.5. Systems Selected
7.1.6. Lists
7.2. Logging into the RHN Website
- You have recently logged into your account at http://www.redhat.com.
- You have recently either logged into RHN or recently visited the new account verification page.
Figure 7.4. RHN Website
Note
Note
7.3. Overview
Note
Figure 7.5. Overview
- The Tasks area lists the most common tasks that an administrator performs via the web. Click on any of the links to be taken to the page within RHN that allows you to accomplish that task.
- To the right is the Inactive System listing. If any systems have not been checking in to RHN, they are listed here. Highlighting them in this way allows an administrator to quickly select those systems for troubleshooting.
- — Customers with Monitoring enabled on their Satellite can also choose to include a list of all probes in the Warning state.
- — Customers with Monitoring enabled on their Satellite can also choose to include a list of all probes in the Critical state.
- The Critical Systems section lists the most critical systems within your organization. It provides a link to quickly view those systems, and displays a summary of the errata updates that have yet to be applied to those systems. Click on the name of the system to be taken to the System Details page of that system and apply the errata updates. Below the list is a link to the Out of Date systems page.
- Next is the Recently Scheduled Actions section. Action that are less than thirty days old are considered recent. This section allows you to see all actions and their status: whether they have failed, completed, or are still pending. Click on the label of any given actions to view the details page for that action. Below the list is a link to the Pending Actions page, which lists all actions that have not yet been picked up by your client systems.
- The Relevant Security Errata section lists the security errata that are available and have yet to be applied to some or all of your client systems. It is critical that you apply these security errata to keep your systems secure. Below this section are links to all errata and to those errata that apply to your systems.
- The System Groups section lists the groups (if any) and indicates whether the systems in those groups are fully updated. Click on the link below this section to be taken to the System Groups page, from which you can chose System Groups to use with the System Set Manager.
- The Recently Registered Systems lists the systems that have been added to the Satellite in the past 30 days. Click the system's name to go the System Details page for that particular system.
7.3.1. Your Account
7.3.1.1. Addresses
7.3.1.2. Change Email
7.3.1.3. Account Deactivation
7.3.2. Your Preferences
- Email Notifications — Determine whether you want to receive email every time an Errata Alert is applicable to one or more systems in your RHN account.
Important
This setting also enables Management and Provisioning customers to receive a daily summary of system events. These include actions affecting packages, such as scheduled Errata Updates, system reboots, or failures to check in. In addition to selecting this checkbox, you must identify each system to be included in this summary email. (By default, all Management and Provisioning systems are included in the summary.) This can be done either individually through the System Details page or for multiple systems at once through the System Set Manager interface. Note that RHN sends these summaries only to verified email addresses. To disable all messages, simply deselect this checkbox. - RHN List Page Size — Maximum number of items that appear in a list on a single page. If more items are in the list, clicking the Next button displays the next group of items. This preference applies to system lists, Errata lists, package lists, and so on.
- "Overview" Start Page — select the information areas that are displayed on the Overview Start Page. Check the box to the left of the information area you would like to include.
7.3.3. Locale Preferences
7.3.4. Subscription Management
- Update — manages a single Red Hat Enterprise Linux system. It includes Errata Alerts, Scheduled Errata Updates, Package Installation, and the Red Hat Update Agent.
- Management — manages multiple systems with multiple system administrators. In addition to the features of the Update offering, it includes system group management, user management, and the System Set Manager interface to quickly perform actions on multiple systems.
- Provisioning — offers the highest level of functionality. It should be used to provision multiple systems that will need to be re-installed and reconfigured regularly. The Provisioning offering provides tools for kickstarting machines, managing their configuration files, conducting snapshot rollbacks, and inputting searchable custom system information, as well as all of the functionality included in the Management service level.
- Monitoring — monitors the health of multiple systems. The Monitoring offering provides probes that watch system metrics and notify Administrators when changes occur. Such notifications alert Administrators to system performance degradation before it becomes critical.
- Virtualization — applies to virtual host systems. Virtual hosts with this entitlement may register as many as four guest systems without violating RHN's Service Level Agreement. Guest systems may be subscribed to any channel with the virtualization-free channel group label without consuming channel entitlements. Subscribing a guest to any channel that does not belong to virtualization-free, such as a Directory Server or RHN Satellite channel, consumes an additional channel entitlement.
- Virtualization Platform — also applies to virtual host systems. Host systems to which this entitlement apply may register an unlimited number of virtual guests without invalidating your Service Level Agreement. Guests of a host with this entitlement may subscribe to any channel that has the virtualization-platform-free content group label without consuming any channel entitlements. Subscribing a guest to any channel that does not belong to virtualization-platform-free, such as a Directory Server or RHN Satellite channel, consumes an additional channel entitlement.
Note
7.3.4.1. System Entitlements
7.3.4.2. Virtualization Entitlements
7.3.4.3. Software Channel Entitlements
7.3.5. Organization Trusts
7.4. Systems
7.4.1. Overview —
7.4.2. Systems
- Select — Update or unentitled systems cannot be selected. To select systems, mark the appropriate checkboxes. Selected systems are added to the System Set Manager. After adding systems to the System Set Manager, you can use it to perform actions on them simultaneously. Refer to Section 7.4.4, “System Set Manager — ” for details.
- Status — Shows which type of Errata Alerts are applicable to the system or confirms that it is up-to-date. Some icons are linked to pages providing resolution. For instance, the standard Updates icon is linked to the Upgrade subtab of the packages list, while the Critical Updates icon links directly to the Update Confirmation page. Also, the Not Checking In icon is linked to instructions for resolving the issue.
- — System is up-to-date
- — Critical Errata available, update strongly recommended
- — Updates available and recommended
- — 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
- Errata — Total number of Errata Alerts applicable to the system.
- Packages — Total number of package updates for the system. Includes packages from Errata Alerts as well as newer packages that are not from Errata Alerts. For example, imagine a client system that has an early version of a package installed. If this client is then subscribed to the appropriate base channel of RHN (such as Red Hat Enterprise Linux 5), that channel may have an updated version of the package. If so, the package appears in the list of available package updates.
Important
If the RHN website identifies package updates for the system, yet the Red Hat Update Agent responds with "Your system is fully updated" when run, a conflict likely exists in the system's package profile or in theup2date
configuration file. To resolve the conflict, either schedule a package list update or remove the packages from the Package Exceptions list for the Red Hat Update Agent. Refer to Section 7.4.2.9, “System Details” or Section 4.4.1.3, “Package Exceptions Settings”, respectively, for instructions. - System — The name of the system as configured when registering it. The default name is the hostname of the system. Clicking on the name of a system takes you to the System Details page for the system. Refer to Section 7.4.2.9, “System Details” for more information.
- Base Channel — The primary channel for the system, based upon its operating system distribution. Refer to Section 7.6.1, “Software Channels” for more information.
- Entitlement — Whether or not the system is entitled and at what service level.
7.4.2.1. All
7.4.2.2. Virtual Systems
- System
- This column displays the name of each guest system.
- Updates
- This column indicates whether the guest systems have any errata that have not yet been applied to them.
- Status
- This column indicates whether a guest is running, paused, or stopped.
- Base Channel
- This column indicates the base channel to which the guest is currently subscribed.
7.4.2.3. Out of Date
7.4.2.4. Unentitled —
7.4.2.5. Ungrouped
7.4.2.6. Inactive
- 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.
- The system is behind a firewall that does not allow connections over https (port 443).
- The system is behind an HTTP proxy server that has not been properly configured.
- The system is connected to an RHN Proxy Server or RHN Satellite that has not been properly configured.
- The system itself has not been properly configured, perhaps pointing at the wrong RHN Server.
- The system is not on the network.
- Some other barrier exists between the system and the RHN Servers.
7.4.2.7. Recently Registered
7.4.2.8. Proxy
7.4.2.9. System Details
Note
- Details
- Software
- Configuration
- Provisioning —
- Monitoring —
- Groups
- Events
7.4.2.9.1. System Details ⇒ Details
7.4.2.9.1.1. System Details ⇒ Details ⇒ Overview
- System Status Message
- This message indicates the current state of your system in relation to RHN.
Note
If updates are available for any entitled system, the message Critical updates available appears. To apply these updates, click the update now link. - system ID
- A unique identifier generated each time a system registers with RHN.
Note
The system ID can be used to eliminate duplicate profiles from RHN. Compare the system ID listed on this page with the information stored on the client system in the/etc/sysconfig/rhn/systemid
file. In that file, the system's current ID is listed under "system_id". The value starts after the characters "ID-" If the value stored in the file does not match the value listed in the profile, the profile is not the most recent one and may be removed. - Hostname
- The hostname as defined by the client system. This information is often found in
/etc/hostname
for Red Hat Enterprise Linux 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.
Note
Systems with a Management entitlement can be rebooted from this screen.- Select Schedule system reboot
- Provide the earliest date and time at which the reboot may take place.
- Click the Schedule Reboot button in the lower right.
When the client checks in after the scheduled start time, RHN will instruct the system to restart itself. - Locked
- Indicates whether a system has been locked.Actions cannot be scheduled for locked systems through the web interface until the lock is removed manually. This does not include preventing auto-errata updates scheduled through the web interface. To prevent the application of auto-errata updates, de-select Auto Errata Update from the System Details ⇒ Details ⇒ Properties subtab.Locking a system can help to prevent you from accidentally making any changes to a system until you are ready to do so. For example, the system may be a production system that you do not wish to receive updates or new packages until you decide to unlock it.
Important
Locking a system in the web interface will not prevent any actions that originate from the client system. For example, if a user logs into the client directly and runsup2date
,up2date
will install available errata whether or not the system is locked in the web interface.Further, locking a system does not restrict the number of users who can access the system via the web interface. If you wish to restrict access to the system, associate that system with a System Group and assign it a System Group Administrator. Refer to Section 7.4.3, “System Groups — ” for more information about System Groups.It is also possible to lock multiple systems via the System Set Manager. Refer to Section 7.4.4.12.4, “System Set Manager ⇒ Misc ⇒ Lock Systems — ” to learn how to do so.
osad
package installed and its service started. Refer to the Enabling Push to Clients section of the RHN Satellite 5.2.0 Installation Guide for details.
- Base Channel
- The first line indicates the base channel to which this client is subscribed. The base channel should match the operating system of the system.
- Child Channels
- The subsequent lines of text, which depend from the base channel, are child channels. Examples are the Red Hat Network Tools channel and the RHEL AS Extras channel.
Note
- Profile Name
- This editable name for the system profile is set to the system's hostname by default. It serves to distinguish this system profile from others.
- Entitlement
- The base entitlement currently applied to this system.
- 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.
- Description
- This information is automatically generated at registration. You can edit this to include any information you wish.
- Location
- If entered, this field displays the physical address of the system.
7.4.2.9.1.2. System Details ⇒ Details ⇒ Properties
- Profile Name
- By default, this is the hostname of the system. You can however alter the profile name to anything that allows you to distinguish this profile from others.
- Base Entitlement
- Select a base channel for the system from the available base entitlements.
- Add-on entitlements
- If available, apply a Monitoring, Provisioning, Virtualization, or Virtualization Platform entitlement to the system.
- Notifications
- Toggle whether notifications about this system are sent and whether this system is included in the daily summary. (By default, all Management and Provisioning systems are included in the summary.) This setting keeps you abreast of all advisories pertaining to the system. Anytime an update is produced and released for the system, a notification is sent via email.The daily summary reports system events that affect packages, such as scheduled Errata Updates, system reboots, or failures to check in. In addition to including the system here, you must choose to receive email notification in the Your Preferences page of the Overview category.
- Auto-errata update
- If this box is checked, available errata are automatically applied to the system when it checks in. This action takes place without user intervention. Customers should note that Red Hat does not recommend the use of the auto-update feature for production systems because conflicts between packages and environments can cause system failures. The Red Hat Network Daemon must be enabled on the system for this feature to work.
- Description
- By default, this text box records the operating system, release, and architecture of the system when it first registers. You may edit this information to include anything you like.
Note
7.4.2.9.1.3. System Details ⇒ Details ⇒ Remote Command —
- First, subscribe the system to the RHN Tools channel and use
up2date
to install therhncfg
,rhncfg-client
, andrhncfg-actions
packages.up2date rhncfg rhncfg-client rhncfg-actions
- Log into the system as root and add the following file to the local RHN configuration directory:
allowed-actions/scripts/run
.- Create the necessary directory on the target system:
mkdir -p /etc/sysconfig/rhn/allowed-actions/script
- Create an empty
run
file in that directory to act as a flag to RHN signaling permission to allow remote commands:touch /etc/sysconfig/rhn/allowed-actions/script/run
7.4.2.9.1.4. System Details ⇒ Details ⇒ Reactivation —
rhnreg_ks
command line utility to re-register this system and regain all Red Hat Network settings. Refer to Section 4.5, “Registering with Activation Keys” 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.
rhnreg_ks --server=<server-url> --activationkey=<reactivation-key>,<activationkey> --force
Warning
rhnreg_ks
) while a profile-based kickstart is in progress. If you do, the kickstart will fail.
7.4.2.9.1.5. System Details ⇒ Details ⇒ Hardware
7.4.2.9.1.6. System Details ⇒ Details ⇒ Notes
7.4.2.9.1.7. System Details ⇒ Details ⇒ Custom Info —
7.4.2.9.1.8. System Details ⇒ Details ⇒ Proxy
7.4.2.9.1.9. System Details ⇒ Details ⇒ Satellite
7.4.2.9.2. System Details ⇒ Software
7.4.2.9.2.1. System Details ⇒ Software ⇒ Errata
7.4.2.9.2.2. System Details ⇒ Software ⇒ Packages
- Packages
- The default display of the Packages tab describes the options available to you and provides the means to update your package list. To update or complete a potentially outdated list, possibly due to the manual installation of packages, click the Update Package List button on the bottom right-hand corner of this page. The next time the RHN Daemon connects to RHN, it updates your System Profile with the latest list of installed packages.
- 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. A confirmation page appears with the packages listed. Click the Confirm button to remove the packages.
- Upgrade
- Displays a list of packages that have a new version available based on the package versions in the channels for the system. Click on the latest package name to view its Package Details page. To upgrade packages immediately, select them and click the Upgrade Packages button. To download the packages as a .tar file, select them and click the Download Packages button.
- Install
- Enables you to install new packages on the system from the available channels. Click on the package name to view its Package Details page. To install packages, select them and click the Install Selected Packages button.
- Verify
- Validates the packages installed on the system against its RPM database. This is the equivalent of running
rpm -V
. Specifically, this tab allows you to compare the metadata of the system's packages with information from the database, such as MD5 sum, file size, permissions, owner, group and type. To verify a package or packages, select them, click the Verify Selected Packages button, and confirm this action. Once finished, you can view the results by selecting this action within the History subtab under Events. - Profiles
- Gives you the ability to compare the packages on this system with the packages of stored profiles and other Management and Provisioning systems. To make the comparison with a stored profile, select that profile from the pulldown menu and click the Compare button. To make the comparison with another system, select it from the associated pulldown menu and click the Compare button. To create a stored profile based upon the existing system, click the Create System Profile button, enter any additional information you desire, and click the Create Profile button. These profiles are kept within the Stored Profiles page linked from the left navigation bar.— Once package profiles have been compared, Provisioning customers have the ability to synchronize the packages of the selected system with the package manifest of the compared profile. Note that this action may delete packages on the system not in the profile, as well as install packages from the profile. To install specific packages, select the checkboxes of packages from the profile. To remove specific packages already installed on the system itself, select the checkboxes of packages showing a difference of This system only. To synchronize fully the system's packages with the compared profile, select the master checkbox at the top of the column. Then click the Sync Packages to button. On the confirmation screen, review the changes, select a time frame for the action, and click the Schedule Sync button.
7.4.2.9.2.3. System Details ⇒ Software ⇒ Software Channels
7.4.2.9.3. System Details ⇒ Configuration —
Note
rhncfg*
packages installed. Refer to Section 7.7.1, “Preparing Systems for Config Management” for instructions on enabling and disabling scheduled actions for a system.
7.4.2.9.3.1. System Details ⇒ Configuration ⇒ Overview
7.4.2.9.3.2. System Details ⇒ Configuration ⇒ Managed Files
- Filename
- This column shows both the name and the deployment path for this file.
- Revision
- This column increments any time you make a change to the managed file.
- From Config Channel
- This column indicates the name of the channel that contains the file, or displays (system override) for files available to this system only.
- Overrides
- If this configuration file overrides another, the overridden file is listed in this column along with its host channel.
Note
7.4.2.9.3.3. System Details ⇒ Configuration ⇒ Compare Files
7.4.2.9.3.4. System Details ⇒ Configuration ⇒ Manage Configuration Channels
httpd.conf
file that will take precedence over the file on lower-ranked channel)
7.4.2.9.3.5. System Details ⇒ Configuration ⇒ Local Overrides
7.4.2.9.3.6. System Details ⇒ Configuration ⇒ Sandbox
7.4.2.9.4. System Details ⇒ Provisioning —
7.4.2.9.4.1. System Details ⇒ Provisioning ⇒ Kickstart —
Note
IPADDR=192.168.0.28 GATEWAY=192.168.0.1
network
portion of a kickstart file could look like the following:
network --bootproto=static --device=eth0 --onboot=on --ip=$IPADDR --gateway=$GATEWAY
$IPADDR
will be 192.168.0.28
, and the $GATEWAY
will be 192.168.0.1
Note
7.4.2.9.4.2. System Details ⇒ Provisioning ⇒ Snapshots —
- group memberships
- channel subscriptions
- installed packages
- configuration channel subscriptions
- configuration files
- snapshot tags
7.4.2.9.4.3. System Details ⇒ Provisioning ⇒ Snapshot Tags —
7.4.2.9.5. System Details ⇒ Virtualization
7.4.2.9.5.1. System Details ⇒ Virtualization ⇒ Details
- Status
- This field indicates whether the virtual system is running, paused, stopped, or has crashed.
- Updates
- This field indicates whether errata applicable to the guest have yet to be applied.
- Base Software Channel
- This field indicates the Base Channel to which the guest is subscribed.
Note
7.4.2.9.5.2. System Details ⇒ Monitoring —
7.4.2.9.5.3. System Details ⇒ Groups —
7.4.2.9.5.3.1. System Details ⇒ Groups ⇒ List/Leave —
7.4.2.9.5.3.2. System Details ⇒ Groups ⇒ Join —
7.4.2.9.5.4. System Details ⇒ Events
7.4.2.9.5.4.1. System Details ⇒ Events ⇒ Pending
- — Package Event
- — Errata Event
- — Preferences Event
- — System Event
7.4.2.9.5.4.2. System Details ⇒ Events ⇒ History
7.4.3. System Groups —
- Create system groups. (Refer to Section 7.4.3.1, “Creating Groups”.)
- Add systems to system groups. (Refer to Section 7.4.3.2, “Adding and Removing Systems in Groups”.)
- Remove systems from system groups. (Refer to Section 7.4.2.9, “System Details”.)
- Assign system group permissions to users. (Refer to Section 7.9, “Users — ”.)
- Select — These checkboxes enable you to add systems in groups to the System Set Manager. To select groups, mark the appropriate checkboxes and click the Update button below the column. All systems in the selected groups are added to the System Set Manager. You can 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. To add all systems in all selected groups, select them and click the Work with Union button. Each system will show up once, regardless of the number of groups to which it belongs. Refer to Section 7.4.4, “System Set Manager — ” for details.
- Updates — Shows which type of Errata Alerts are applicable to the group or confirms that it is up-to-date. Clicking on a group's status icon takes you to the Errata tab of its System Group Details page. Refer to Section 7.4.3.3, “System Group Details — ” for more information.The status icons call for differing degrees of attention:
- — All systems within group are up-to-date
- — Critical Errata available, update strongly recommended
- — Updates available and recommended
- Group Name — The name of the group as configured during its creation. The name should be explicit enough to easily differentiate between it and other groups. Clicking on the name of a group takes you to Details tab of its System Group Details page. Refer to Section 7.4.3.3, “System Group Details — ” for more information.
- Systems — Total number of systems contained by the group. Clicking on the number takes you to the Systems tab of the System Group Details page for the group. Refer to Section 7.4.3.3, “System Group Details — ” for more information.
- Use in SSM — Clicking the Use Group button in this column loads the group from that row and launches the System Set Manager immediately. Refer to Section 7.4.4, “System Set Manager — ” for more information.
7.4.3.1. Creating Groups
7.4.3.2. Adding and Removing Systems in Groups
7.4.3.3. System Group Details —
7.4.3.3.1. System Group Details ⇒ Details —
7.4.3.3.2. System Group Details ⇒ Systems —
7.4.3.3.3. System Group Details ⇒ Target Systems —
7.4.3.3.4. System Group Details ⇒ Errata —
7.4.3.3.5. System Group Details ⇒ Admins —
7.4.3.3.6. System Group Details ⇒ Probes —
7.4.4. System Set Manager —
- Apply Errata updates
- Upgrade packages to the most recent versions available
- Add/remove systems to/from system groups
- Subscribe/unsubscribe systems to/from channels
- Update system profiles
- Modify system preferences such as scheduled download and installation of packages
- Kickstart several Provisioning-entitled systems at once
- Set the subscription and rank of configuration channels for Provisioning-entitled systems
- 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
- Click the System Set Manager link in the left gray navigation area.
- Click the Use Group button in the System Groups list.
- Check the Work with Group link on the System Group Details page.
7.4.4.1. System Set Manager ⇒ Overview —
7.4.4.2. System Set Manager ⇒ Systems —
7.4.4.3. System Set Manager ⇒ Errata —
7.4.4.4. System Set Manager ⇒ Packages —
7.4.4.4.1. System Set Manager ⇒ Packages ⇒ Upgrade —
7.4.4.4.2. System Set Manager ⇒ Packages ⇒ Install —
7.4.4.4.3. System Set Manager ⇒ Packages ⇒ Remove —
7.4.4.5. System Set Manager ⇒ Verify
rpm --verify
for the specified package. If there are any discrepancies, they are displayed in the System Details page for each system.
7.4.4.6. System Set Manager ⇒ Patches
7.4.4.7. System Set Manager ⇒ Patch Clusters
7.4.4.8. System Set Manager ⇒ Groups —
7.4.4.9. System Set Manager ⇒ Channels —
7.4.4.9.1. System Set Manager ⇒ Channels ⇒ Channel Subscriptions —
7.4.4.10. System Set Manager ⇒ Configuration —
rhncfg*
packages. Refer to Section 7.7.1, “Preparing Systems for Config Management” for instructions on enabling and disabling scheduled actions for a system.
7.4.4.10.1. System Set Manager ⇒ Configuration ⇒ Deploy Files —
7.4.4.10.2. System Set Manager ⇒ Configuration ⇒ Compare Files —
7.4.4.10.3. System Set Manager ⇒ Configuration ⇒ Subscribe to Channels —
7.4.4.10.4. System Set Manager ⇒ Configuration ⇒ Unsubscribe from Channels —
7.4.4.10.5. System Set Manager ⇒ Configuration ⇒ Enable Configuration —
7.4.4.11. System Set Manager ⇒ Provisioning —
7.4.4.11.1. System Set Manager ⇒ Provisioning ⇒ Kickstart —
7.4.4.11.2. System Set Manager ⇒ Provisioning ⇒ Tag Systems —
7.4.4.11.3. System Set Manager ⇒ Provisioning ⇒ Rollback —
7.4.4.11.4. System Set Manager ⇒ Provisioning ⇒ Remote Command —
run
file on the client systems to allow this function to operate. Refer to the description of the Configuration subtab of the Channels tab for instructions. You may then identify a specific user, group, timeout period, and the script on this page. Select a date and time to perform the command, and click Schedule Remote Command.
7.4.4.12. System Set Manager ⇒ Misc —
7.4.4.12.1. System Set Manager ⇒ Misc ⇒ System Profile Updates —
7.4.4.12.2. System Set Manager ⇒ Misc ⇒ Custom System Information —
7.4.4.12.3. System Set Manager ⇒ Misc ⇒ Reboot Systems —
7.4.4.12.4. System Set Manager ⇒ Misc ⇒ Lock Systems —
7.4.4.12.5. System Set Manager ⇒ Misc ⇒ Delete Systems —
7.4.4.12.6. System Set Manager ⇒ Misc ⇒ Add or Remove Add-On Entitlements —
7.4.4.12.7. System Set Manager ⇒ Misc ⇒ System Preferences —
- Receive Notifications of Updates/Errata — This setting keeps you abreast of all advisories pertaining to your systems. Any time an update is produced and released for a system under your supervision, a notification is sent via email.
- Include system in Daily Summary — This setting includes the selected systems in a daily summary of system events. (By default, all Management and Provisioning systems are included in the summary.) These system events are actions that affect packages, such as scheduled Errata Updates, system reboots, or failures to check in. In addition to including the systems here, you must choose to receive email notifications in the Your Preferences page of Your RHN. Refer to Section 7.3.2, “Your Preferences” for instructions. Note that RHN sends these summaries only to verified email addresses.
- Automatic application of relevant Errata — This setting enables the automatic application of Errata Updates to the selected systems. This means packages associated with Errata are updated without any user intervention. Customers should note that Red Hat does not recommend the use of the auto-update feature for production systems because conflicts between packages and environments can cause system failures.
7.4.5. Advanced Search —
- DMI Info — The Desktop Management Interface (DMI) is a standard for management of components on computer system. You can search for RHN Satellite systems using the following DMI retrieval methods:
- System — Product names or numbers, Manufacturer names, Serial numbers, and other information that may be unique to a system
- BIOS — BIOS support information such as BIOS vendor name and version, hardware support enabled in the BIOS, and more
- Asset Tag — A unique identifier assigned by an IT department (or vendor) to a system for better tracking, management and inventory
- Location — The physical location of a system, which includes the following:
- 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.
- Details — The unique identifiers assigned to a system by sytem administrators and particularly Satellite Administrators, including the following:
- Name/Description — The name assigned to a system by the Satellite Administrator upon adding it to the RHN Satellite server.
- ID — An identifier that is unique to a system or system set.
- Custom Info — Information about the system that is unique only to that system.
- Snapshot Tag — The name assigned to a new or previous system snapshot
- Running Kernel — The currently running kernel on a system registered to the Satellite
- Hardware — Systems can be searched by particular components in the system, including the following:
- CPU Model — The CPU model name (such as Pentium or Athlon
- CPU MHz Less Than — Search systems with a processor less than a user-designated speed in Megahertz.
- CPU MHz More Than — Search systems with a processor more than a user-designated speed in Megahertz.
- Number of CPUs Less Than — Search systems with a sum of processors less than a user-designated quantity.
- Number of CPUs Greater Than — Search systems with a sum of processors greater than a user-designated quantity.
- RAM Less Than — Search systems with a sum of memory less than a user-designated quantity in megabytes.
- RAM More Than — Search systems with a sum of memory more than a user-designated quantity in megabytes.
- Packages — Systems can be searched by the packages installed (and not yet installed) on the system.
- Installed Packages — Filter systems based on particular installed packages
- Needed Packages — Filter systems based on particular packages that have yet to be installed
- Activity — Systems can be searched by the amount of time since first or last check-in with the RHN Satellite
- 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
- Network Info — Systems can be searched based on specific networking details such as IP address.
- Hostname — The name associated with a system registered to RHN Satellite
- IP Address — The network address of the system registered to RHN Satellite
- Hardware Devices — Systems can be searched by specific hardware details such as driver names and Device or Vendor IDs
- Description — Device summary information, such as brand or model name/number (such as
Intel 82801HBM/HEM
) - Driver — The kernel driver or module name (such as
tulip.o
oriwl3945
) - Device ID — The hexadecimal number corresponding to the device installed in the system.
- Vendor ID — The hexadecimal number corresponding to the vendor of the device installed in the system.
7.4.6. Activation Keys —
rhnreg_ks
. Refer to Section 4.5, “Registering with Activation Keys” for instructions on use.
Note
7.4.6.1. Managing Activation Keys
- Select Systems => Activation Keys from the top and left navigation bars.
- 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. This user-defined string of characters can then be supplied withrhnreg_ks
to register client systems with the Satellite. Do not insert commas in the key. All other characters are accepted. Commas are problematic since they are the separator used when including two or more activation keys at once. Refer to Section 7.4.6.2, “Using Multiple Activation Keys at Once — ” for details. - Provide the following information:
- Description — User-defined description to identify the generated activation key.
- Usage Limit — The maximum number of registered systems that can be registered to the activation key at any one time. Leave blank for unlimited use. Deleting a system profile reduces the usage count by one and registering a system profile with the key increases the usage count by one.
- Base Channel — The primary channel for the key. Selecting nothing will enable you to select from all child channels, although systems can be subscribed to only those that are applicable.
- Add-on Entitlements — The supplemental entitlements for the key, which includes Monitoring, Provisioning, Virtualization, and Virtualization Platform. All systems will be given these entitlements with the key.
- Universal default — Whether or not this key should be considered the primary activation key for your organization.
Click Create Key.
Figure 7.6. Activation Keys
7.4.6.2. Using Multiple Activation Keys at Once —
- base software channels — registration fails
- entitlements — registration fails
- enable config flag — configuration management is set
rhnreg_ks
or in a kickstart profile within the Post tab of the Kickstart Details page. Refer to Section 4.5, “Registering with Activation Keys” and Section 7.4.9.3, “Create a New Kickstart Profile”, respectively, for instructions.
7.4.7. Stored Profiles —
7.4.8. Custom System Info —
asset
key within the Custom System Info page.
Asset
and Precise location of each system
, and click the Create Key. The key will then show up in the custom info keys list.
7.4.8.1. rhn-custom-info
rhn-custom-info
that performs the same actions at a shell prompt, for administrators who may not have access to the web interface.
rhn-custom-info
is as follows:
rhn-custom-info options key1 value1
rhn-custom-info --username=admin --password=f00b4rb4z --server-url=satellite.example.com --list-values
rhn-custom-info -h
.
7.4.9. Kickstart —
Important
/var/www/html/pub/
on the Proxy. RHN Satellites already have a tree for each Red Hat distribution and therefore do not require separate trees. Even if the system connects through an RHN Proxy Server to get to the Satellite, these trees will be available for kickstart. Refer to Section 7.4.9.6, “Kickstart ⇒ Distributions —
” for instructions on setting up installation trees.
Figure 7.7. Kickstart Overview
7.4.9.1. Introduction to Kickstart
7.4.9.1.1. Kickstart Explained
- After being placed on the network and turned on, the machine's PXE logic broadcasts its MAC address and a request to be discovered.
- If a static IP address is not being used, the DHCP server recognizes the discovery request and extends an offer of network information needed for the new machine to boot. This includes an IP address, the default gateway to be used, the netmask of the network, the IP address of the TFTP or HTTP server holding the bootloader program, and the full path and file name of that program (relative to the server's root).
- The machine applies the networking information and initiates a session with the server to request the bootloader program.
- The bootloader, once loaded, searches for its configuration file on the server from which it was itself loaded. This file dictates which kernel and kernel options, such as the initial RAM disk (initrd) image, should be executed on the booting machine. Assuming the bootloader program is SYSLINUX, this file is located in the
pxelinux.cfg
directory on the server and named the hexadecimal equivalent of the new machine's IP address. For example, a bootloader configuration file for Red Hat Enterprise Linux AS 2.1 should contain:port 0 prompt 0 timeout 1 default My_Label label My_Label kernel vmlinuz append ks=http://myrhnsatellite/ initrd=initrd.img network apic
- The machine accepts and uncompresses the init image and kernel, boots the kernel, and initiates a kickstart installation with the options supplied in the bootloader configuration file, including the server containing the kickstart configuration file.
- This kickstart configuration file in turn directs the machine to the location of the installation files.
- The new machine is built based upon the parameters established within the kickstart configuration file.
7.4.9.1.2. Kickstart Prerequisites
- A DHCP server is not required for kickstarting, but it can make things easier. If you are using static IP addresses, you should select static IP while developing your kickstart profile.
- An FTP server can be used in place of hosting the kickstart distribution trees via HTTP.
- If conducting a bare metal kickstart, you should 1)Configure DHCP to assign required networking parameters and the bootloader program location. 2)Specify within the bootloader configuration file the kernel to be used and appropriate kernel options.
7.4.9.1.3. Building Bootable Kickstart ISOs
/isolinux
from the first CD-ROM of the target distribution. Then edit the isolinux.cfg
file to default to 'ks'. Change the 'ks' section to the following template:
label ks kernel vmlinuz append text ks={url} initrd=initrd.img lang= devfs=nomount ramdisk_size=16438 \ {ksdevice}
http://my.sat.server/kickstart/ks/mode/ip_range
ksdevice=eth0
isolinux.cfg
further for your needs, such as by adding multiple kickstart options, different boot messages, shorter timeout periods, etc.
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/
isolinux/
is the relative path to the directory containing the isolinux files from the distribution CD, while file.iso
is the output ISO file, which is placed into the current directory.
7.4.9.1.4. Integrating Kickstart with PXE
Note
7.4.9.2. Kickstart Profiles
Figure 7.8. Kickstart Profiles
7.4.9.3. Create a New Kickstart Profile
- On the first line, enter a kickstart profile label. This label cannot contain spaces, so use dashes (-) or underscores (_) as separators.
- Select a Base Channel for this profile, which consists of packages based on a specific architecture and Red Hat Enterprise Linux release, such as Red Hat Enterprise Linux (v.5 for 32-bit x86).
- Select a kickstartable tree for this profile. The kickstartable tree drop-down menu is only populated if one or more distributions have been created for the selected base channel.
- Select the Virtualization Type from the drop-down menu. For more information about virtualization, refer to Chapter 10, Virtualization.
Note
If you do not intend to use the kickstart profile to create virtual guest systems, you can leave the drop-down at the default KVM Virtualized Guest choice. - On the second page, select (or enter) the URL of the kickstart tree.
- 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/.
pyOpenSSL
, rhnlib
, libxml2-python
, and spacewalk-koan
and associated packages.
- Make sure that the rhn-tools child software channel for the kickstart profile's base channel is available to your organization. If it is not, you must request entitlements for the rhn-tools software channel from the Satellite administrator.
- Make sure that the rhn-tools child channel for this kickstart profile's base channel is available to your RHN Satellite. If it is not, contact the Satellite administrator and request a
satellite-sync
of the rhn-tools. - Make sure that the
rhn-kickstart
and associated packages corresponding to this kickstart are available in the kickstart rhn-tools child channel. If it is not, you must make them available for this kickstart profile to function properly.
7.4.9.3.1. Kickstart Details ⇒ Details —
Figure 7.9. Kickstart Details
- Rename the profile
- Change the operating system it installs by clicking (Change)
- 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
- Change the number of Virtual CPUs for each virtual guest
- Change the the Virtual Storage Path from the default in
/var/lib/xen/
- Change the amount of Virtual Disk Space (in Gigabytes) alloted to each virtual guest
- Change the Virtual Bridge for networking of the virtual guest
- Deactivate the profile so that it cannot be used to schedule a kickstart by removing the Active checkmark
- Check whether to enable logging for custom
%post
scripts to the/root/ks-post.log
file - Check whether to enable logging for custom
%pre
scripts to the/root/ks-pre.log
file - Check whether to preserve the
ks.cfg
file and all%include
fragments to the/root/
directory of all systems kickstarted with this profile. - Select whether this profile is the default for all of your organization's kickstarts by checking or unchecking the box.
- Add any Kernel Options in the corresponding text box.
- Add any Post Kernel Options in the corresponding text box.
- Enter comments that are useful to you in distinguishing this profile from others
7.4.9.3.2. Kickstart Details ⇒ Operating System —
- Change the base channel
- Select from the available base channels, such as Red Hat Enterprise Linux v.5 for 32-bit x86. Satellite administrators can see a list of all base channels that are currently synced to the Satellite.
- Child Channels
- Subscribe to any available child channels of the base channel, such as the rhn-tools* channel.
- Available Trees
- Use the drop-down menu to choose the available trees that are associated with the base channel.
- 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
IPADDR=192.168.0.28 GATEWAY=192.168.0.1
network
portion of a kickstart file looks like the following:
network --bootproto=static --device=eth0 --onboot=on --ip=$IPADDR --gateway=$GATEWAY
$IPADDR
will be 192.168.0.28
, and the $GATEWAY
will be 192.168.0.1
Note
7.4.9.3.4. Kickstart Details ⇒ Advanced Options —
7.4.9.3.5. Kickstart Details ⇒ Bare Metal Kickstart —
7.4.9.3.6. System Details ⇒ Details —
Figure 7.10. System Details
- Select from DHCP and static IP, depending on your network
- Choose the level of SELinux that is configured on kickstarted systems
- Enable configuration management or remote command execution on kickstarted systems
- Change the root password associated with this profile
7.4.9.3.7. System Details ⇒ Locale —
7.4.9.3.8. System Details ⇒ Partitioning —
partition /boot --fstype=ext3 --size=200 partition swap --size=2000 partition pv.01 --size=1000 --grow volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 --grow
7.4.9.3.9. System Details ⇒ File Preservation —
7.4.9.3.10. System Details ⇒ GPG and SSL —
Note
7.4.9.3.11. System Details ⇒ Troubleshooting —
- Bootloader
- For some headless systems, it is better to select the non-graphic LILO bootloader.
- Kernel Parameters
- Enter kernel parameters here that may help to narrow down the source of hardware issues.
7.4.9.3.12. Software ⇒ Package Groups —
Figure 7.11. Software
@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 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 —
7.4.9.3.14. Activation Keys —
Figure 7.12. Activation Keys
7.4.9.3.15. Scripts —
Figure 7.13. Scripts
- Click the add new kickstart script link in the upper right
- Enter the path to the scripting language used to create the script, such as /usr/bin/perl
- Enter the full script in the large text box
- Indicate whether this script is to be executed in the %pre or %post section of the kickstart process
- Indicate whether this script is to run outside of the chroot environment. Refer to the Post-installation Script section of the Red Hat Enterprise Linux System Administration Guide for further explanation of the
nochroot
option
Note
/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
7.4.9.3.16. Kickstart File —
Figure 7.14. Kickstart File
7.4.9.4. Kickstart ⇒ Bare Metal —
7.4.9.5. Kickstart ⇒ GPG and SSL Keys —
Important
7.4.9.6. Kickstart ⇒ Distributions —
Note
Important
satellite-sync
are made available automatically and do not require the creation of a separate installation tree. These trees are available to client systems that kickstart through the Satellite. While you may be able to access the files from a non-kickstarting client, this functionality is not supported and may be removed at any time in the future.
my-orgs-rhel-as-5
. In the Tree Path field, paste the path or URL to the base of the installation tree. (You can test this by appending "README" to the URL in a Web browser, pressing Enter, and ensuring that the distribution's readme file appears.)
Red Hat Enterprise Linux (v. 5 for 32-bit x86)
and Red Hat Enterprise Linux 5
, respectively. When finished, click the Create Kickstart Distribution button.
7.4.9.6.1. Kickstart ⇒ Distributions ⇒ Variables
IPADDR=192.168.0.28 GATEWAY=192.168.0.1
network
portion of a kickstart file looks like the following:
network --bootproto=static --device=eth0 --onboot=on --ip=$IPADDR --gateway=$GATEWAY
$IPADDR
will be 192.168.0.28
, and the $GATEWAY
will be 192.168.0.1
Note
7.4.9.7. Kickstart ⇒ File Preservation —
Important
/dev/hda1
and /dev/sda1
are not supported. Finally, only file and directory names may be entered. No regular expression wildcards can be included.
7.5. Errata
Note
- — Security Updates available, update strongly recommended
- — Bug Fix Updates available and recommended
- — Enhancement Updates available
7.5.1. Relevant Errata
Figure 7.15. Errata List
7.5.2. All Errata
7.5.2.1. Apply Errata Updates
- To apply a specific Errata Update to one or more systems, find the update within the Errata lists. In the table, click on the number of systems affected, which takes you to the Affected Systems tab of the Errata Details page. Select the individual systems to be updated and click the Apply Errata button. Double-check the systems to be updated on the confirmation page, then click the Confirm button.
- To apply more than one Errata Update to one or more systems, select the systems from a Systems list and click the Update List button. Click the System Set Manager link in the left navigation bar, then click the Systems tab. After ensuring the appropriate systems are selected, click the Errata tab, select the Errata Updates to apply, and click the Apply Errata button. You can select to apply the Errata as soon as possible (the next time the Red Hat Network Daemon on the client systems connect to RHN) or schedule a date and time for the Errata Updates to occur. Then click the Schedule Updates button. You can follow the progress of the Errata Updates through the Pending Actions list. Refer to Section 7.8, “Schedule” for more details.
Important
- Each package is a member of one or more channels. If a selected system is not subscribed to a channel containing the package, the package will not be installed on that system.
- If a newer version of the package is already on the system, the package will not be installed on that system.
- If an older version of the package is installed, the package will be upgraded.
7.5.2.2. Errata Details
7.5.2.2.1. Errata Details ⇒ Details
7.5.2.2.2. Errata Details ⇒ Packages
7.5.2.2.3. Errata Details ⇒ Affected Systems
7.5.3. 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. - Package Name — Users concerned with particular packages can search by package name, such as:
kernel
Package search can be beneficial because search results will be grouped by advisory. For example, searching for kernel-related bugs return results where all packages with the termkernel
appear grouped by the advisory for which the bug is related. - CVE Name — The name assigned to the Security advisory (RHSA) by the Common Vulnerabilities and Exposures project at http://cve.mitre.org. For example:
CVE-2006-4535
- Bug Fix Advisory — Errata that contains fixes to issues that were reported by users or discovered during development or testing
- Security Advisory — Errata that fixes a security issue found during development, testing, or reported by users or a software security clearing house. A security advisory usually has one or more CVE names associated with each vulnerability found in each erratum.
- Product Enhancement Advisory — Errata that contains new features, improved functionality, or enhanced performance in the package's software.
7.6. Channels
7.6.1. Software Channels
7.6.1.1. Base Channels
7.6.1.1.1. Extended Update Support (EUS)
7.6.1.2. Child Channels
7.6.1.3. All Channels
Figure 7.17. All Channels
7.6.1.4. Red Hat Channels
7.6.1.5. Popular Channels
7.6.1.6. My Channels
7.6.1.7. Shared Channels
7.6.1.8. Retired Channels
7.6.1.9. Software Channel Details
7.6.1.9.1. Software Channel Details ⇒ Details
- Customers with a custom base channel may assign the system to that base channel.
- Customers may revert system subscriptions from a custom base channel to the appropriate distribution-based base channel.
Note
7.6.1.9.2. Software Channel Details ⇒ Errata
7.6.1.9.3. Software Channel Details ⇒ Packages
ks
in the filter might return: ksconfig
, krb5-workstation
, and links
. The filter is case-insensitive.
7.6.1.9.4. Software Channel Details ⇒ Subscribed Systems
7.6.1.9.5. Software Channel Details ⇒ Target Systems
7.6.2. Package Search
Figure 7.18. Package Search
- Free Form — a general keyword search for users that are unsure of the details of particular package and its contents.
- Name Only — Targeted search for users that need to find a specific packages and do not want to sift through more generalized search results.
- Name and Description — Specified searches for a certain package name or program that, while not in the name of the package, may be in the one-line description of the package (for example, searching for the Apache HTTP Server when the actual Red Hat Enterprise Linux package name is
httpd
. - Name and Summary — Similar to a Name and Description search, this search criteria searches package names and the longer Summary for the package. So, a search for "web browser" could result in several results that includes both graphical and text-based browsers.
java
in the description and summary, type the follwing using the Free Form field:
summary:java and description:java
name
— Search the package names for a particular keywordversion
— Search for a particular package's versionfilename
— Search the package filenames for a particular keyworddescription
— Search the packages' detailed description field for a particular keywordsummary
— Search the packages' brief summary for a particular keywordarch
— Search the packages by their architecture (such as x86, x86_64, or s390)
7.6.3. Manage Software Channels
7.6.3.1. Manage Software Channels ⇒ Channel Details
7.6.3.1.1. Manage Software Channels ⇒ Channel Details ⇒ Channel Details
7.6.3.1.2. Manage Software Channels ⇒ Channel Details ⇒ Managers
7.6.3.1.3. Manage Software Channels ⇒ Channel Details ⇒ Errata
7.6.3.1.4. Manage Software Channels ⇒ Channel Details ⇒ Packages
7.6.3.2. Manage Software Channels ⇒ Manage Software Packages
7.7. Configuration
7.7.1. Preparing Systems for Config Management
config-enable
file installed. These tools may already be installed on your system, especially if you kickstarted the system with configuration management functionality. If not, they can be found within the RHN Tools child channel for your distribution. Download and install the latest rhncfg*
packages. They are:
rhncfg
— The base libraries and functions needed by allrhncfg-*
packages.rhncfg-actions
— The code required to run configuration actions scheduled via the RHN website.rhncfg-client
— A command line interface to the client features of the RHN Configuration Management system.rhncfg-management
— A command line interface used to manage RHN configuration.
rhn-actions-control
command on the client system. This command is included in the rhncfg-actions
RPM. The RHN Actions Control (rhn-actions-control
) enables or disables specific modes of allowable actions. Refer to Section B.1, “Red Hat Network Actions Control” for instructions.
7.7.2. Overview
- Configuration Summary
- This panel provides quick reference information about your configuration files. Clicking on any of the blue text to the right displays an appropriate list of either relevant systems, channel details, or configuration files.
- Configuration Actions
- This panel offers direct access to the most common configuration management tasks. You can view or create files or channels, or enable configuration management on your systems.
- Recently Modified Configuration Files
- The list displayed here indicates which files have changed, to which channel they belong, and when they were changed. If no files have been recently changed, no list appears. Click on the name of the file to be taken to that file's Details page. Click on the channel name to be taken to the Channel Details page for that channel.
- Recently Scheduled Configuration Deployments
- Each action that has been scheduled is listed here along with the status of the action. Any configuration task that is scheduled, from enabling configuration management on a system to deploying a specific configuration file, is displayed here. This allows you to quickly assess if your tasks have succeeded, and to take action to correct any issues. Clicking on any blue text displays the System Details ⇒ Schedule page for the specified system.
7.7.3. Configuration Channels
- Click the create new config channel link in the upper right of this screen.
- Enter a name for the channel.
- Enter a label for the channel. This field must contain only alphanumeric characters, "-", "_", and "."
- Enter a description for the channel. You must enter a description, though there is no character restriction. This field can contain any brief information that allows you to distinguish this channel from others.
- Press the Create Config Channel button to create the new channel.
- The following page is a subset of the Channel Details page, and has three sub-tabs: Overview, Add Files, and Systems. The Channel Details page is discussed fully in Section 7.7.3.1, “Configuration ⇒ Configuration Channels ⇒ Configuration Channel Details”.
7.7.3.1. Configuration ⇒ Configuration Channels ⇒ Configuration Channel Details
- Overview
- This sub-tab is very similar to the Configuration Overview page. The Channel Information panel provides status information for the contents of the channel. The Configuration Actions panel provides access to the most common configuration tasks. The main difference is the Channel Properties panel. By clicking on the Edit Properties link, you can edit the name, label, and description of the channel.
- List/Remove Files
- This tab, which only appears if there are files in the configuration channel, lists the files that this configuration channel contains. You can remove a file or files, or copy the latest version into a set of local overrides or into other central configuration channels. Check the box next to any files you wish to manipulate and click the button corresponding to the desired action at the bottom of the screen.
- Add Files
- The Add Files sub-tab has three sub-tabs of its own, which allow you to Upload, Import, or Create configuration files to be included in the channel.
- 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. Finally, if the configuration file includes a macro, enter the symbol that marks the beginning and end of the macro.
- Import Files
- From this page you can import files from other configuration channels, including any locally-managed channels. Check the box to the left of any file you wish to import and press the Import Configuration File(s) button.
Note
A sandbox icon indicates that the listed file is currently located in a local sandbox channel. Files in a system's sandbox channel are considered experimental and could be unstable. Use caution when selecting them for a central configuration channel. - Create File
- From this page you can create a configuration file from scratch to be included in the configuration channel. Indicate the absolute path along which the file should be deployed, enter the ownership and permissions for the file, and enter the configuration file content in the appropriate fields. Finally, press the Create Configuration File button to create the new file.
- Deploy Files
- This sub-tab only appears when there are files present in the channel. You can deploy all files by pressing the Deploy All Files button, or you can check selected files and press the Deploy Selected Files button. You will then be asked to select to which systems the file(s) should be applied. The listed systems are those that are subscribed to this channel. If you wish to apply the file to a system not listed here, first subscribe that system to the channel. When ready, press the Confirm and Deploy to Selected Systems button to deploy the files.
- Systems
- This tab, which consists of two sub-tabs, allows you to manage the systems that are subscribed to the configuration channel.
- Subscribed Systems
- This sub-tab displays a list of all systems that are subscribed to the current channel. Clicking on the name of the system takes you to the System Details page for that system.
- Target Systems
- This sub-tab displays a list of systems that have been enabled for configuration management and that are not yet subscribed to the channel. To add a system to the configuration channel, check the box to the left of the system's name and press the Subscribe System button.
7.7.4. Configuration Files
Note
/etc/rhn/default/rhn_web.conf
file:
web.maximum_config_file_size=128
/etc/rhn/default/rhn_server.conf
file to the same value:
maximum_config_file_size=128
128
to the desired value in kilobytes.
7.7.4.1. Centrally-Managed Files
7.7.5. Locally-Managed Files
7.7.5.1. Including Macros in your Configuration Files
- rhn.system.sid
- rhn.system.profile_name
- rhn.system.description
- rhn.system.hostname
- rhn.system.ip_address
- rhn.system.custom_info(key_name)
- rhn.system.net_interface.ip_address(eth_device)
- rhn.system.net_interface.netmask(eth_device)
- rhn.system.net_interface.broadcast(eth_device)
- rhn.system.net_interface.hardware_address(eth_device)
- rhn.system.net_interface.driver_module(eth_device)
server.conf
, with the IP address and hostname macros included, like so:
hostname={| rhn.system.hostname |} ip_address={| rhn.system.net_interface.ip_address(eth0) |}
rhncfg-client
), the variables will be replaced with the hostname and IP address of the system, as recorded in RHN's System Profile. In the above configuration file, for example, the deployed version resembles the following:
hostname=test.example.domain.com ip_address=177.18.54.7
asset={@ rhn.system.custom_info(asset) @}
asset=Example#456
asset={@ rhn.system.custom_info(asset) = 'Asset #' @}
rhncfg-manager
) will not translate or alter files, as that tool is system agnostic — rhncfg-manager
does not depend on system settings. Binary files cannot be interpolated.
7.7.6. Systems
7.7.6.1. Managed Systems
7.7.6.2. Target Systems
Note
7.8. Schedule
- Package Alteration (installation, upgrade, and removal)
- Rollback Package Actions
- System Reboots
- Errata Updates
- Configuration File Alteration (deploy, upload, and diff)
- Hardware Profile Updates
- Package List Profile Updates
- Kickstart Initiation
- Remote Commands
7.8.1. Pending Actions
Figure 7.19. Schedule - Pending Actions
7.8.2. Failed Actions
7.8.5. Actions List
- Select — Use the checkboxes in this column to select actions. After selecting actions, you can either add them to your selection list or move them to the Archived Actions list. If you archive a pending action, it is not canceled; the action item moves from the Pending Actions list to the Archived Actions list.
- 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.
- Earliest — The earliest day and time the action will be performed.
- Succeeded — Number of systems on which this action was successful.
- Failed — Number of systems on which this action has been tried and failed.
- In Progress — Number of systems on which this action is taking place.
- Total — Total number of systems on which this action has been scheduled.
7.8.5.1. Action Details
7.8.5.1.1. Action Details ⇒ Details
7.8.5.1.2. Action Details ⇒ Completed Systems
7.8.5.1.3. Action Details ⇒ In Progress Systems
7.8.5.1.4. Action Details ⇒ Failed Systems
7.9. Users —
7.9.1. User List ⇒ Active —
- Username — The login name of the user. If you click on a username, the User Details page for the user is displayed. Refer to Section 7.9.1.1, “User List ⇒ Active ⇒ User Details — ” for more information.
- Real Name — The full name of the user (last name first).
- Roles — List of the user's privileges, such as Organization Administrator, Channel Administrator and normal user. Users can have multiple roles.
- Last Sign In — Shows when the user last logged into RHN.
Figure 7.20. User List
7.9.1.1. User List ⇒ Active ⇒ User Details —
Warning
- Navigate to the user's User Details tab.
- Verify that the user is not an Satellite Administrator. If they are, uncheck the box to the left of that role and click the Submit button in the lower right of the screen.
- Click the deactivate user link in the upper right of the screen.
- Click the Deactivate User button in the lower right to confirm.
- Navigate to the user's User Details tab.
- Verify that the user is not an Satellite Administrator and remove that role if necessary.
- Click the delete user link in the upper right.
- Click the Delete User button to permanently delete the user.
7.9.1.1.1. User List ⇒ Active ⇒ User Details ⇒ Details —
- User — Also known as a System Group User, this is the standard role associated with any newly created user. This person may be granted access to manage system groups and software channels. The systems must be in system groups to which the user has permissions for them to be manageable or even visible. Remember, however, all globally subscribable channels may be used by anyone.
- Activation Key Administrator — This role is designed to manage your organization's collection of activation keys. This person can create, modify, and delete any key within your overarching account.
- Channel Administrator — This role has complete access to the software channels and related associations within your organization. It requires RHN Satellite or RHN Proxy Server. This person may change the base channels of systems, make channels globally subscribable, and create entirely new channels.
- Configuration Administrator — This role enables the user to manage the configuration of systems in the organization using either the RHN Satellite web-based interface or the Red Hat Network Configuration Manager.
- Monitoring Administrator — This role allows for the scheduling of probes and oversight of other Monitoring infrastructure. This role is available only on Monitoring-enabled RHN Satellite version 3.6 or later.
- Satellite Administrator — This role can perform any function available within Red Hat Network. As the master account for your organization, the person holding this role can alter the privileges of all other accounts, as well as conduct any of the tasks available to the other roles. Like the other roles, multiple Satellite Administrators may exist.
- System Group Administrator — This role is one step below Satellite Administrator in that it has complete authority over the systems and system groups to which it is granted access. This person can create new system groups, delete any assigned systems groups, add systems to groups, and manage user access to groups.
7.9.1.1.2. User List ⇒ Active ⇒ User Details ⇒ System Groups —
7.9.1.1.3. User List ⇒ Active ⇒ User Details ⇒ Systems —
7.9.1.1.4. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions —
7.9.1.1.4.1. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions ⇒ Subscription —
7.9.1.1.4.2. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions ⇒ Management —
7.9.1.1.5. User List ⇒ Active ⇒ User Details ⇒ Preferences —
- Email Notification — Determine whether this user should receive email every time an Errata Alert is applicable to one or more systems in his or her RHN account, as well as daily summaries of system events.
- RHN List Page Size — Maximum number of items that appear in a list on a single page. If more items are in the list, clicking the Next button displays the next group of items. This preference applies to the user's view of system lists, Errata lists, package lists, and so on.
- Time Zone — Set this user's time zone so that scheduled actions are arranged according to the time in the relevant time zone.
- Red Hat Contact Options — Identify what ways (email, phone, fax, or mail) Red Hat may contact the user.
7.9.1.1.6. User List ⇒ Active ⇒ User Details ⇒ Addresses —
7.9.1.1.7. User List ⇒ Active ⇒ User Details ⇒ Notification Methods —
7.9.2. User List ⇒ Deactivated —
7.9.3. User List ⇒ All —
7.10. Monitoring —
7.10.1. Probe Status —
- — Critical - The probe has crossed a CRITICAL threshold.
- — Warning - The probe has crossed a WARNING threshold.
- — Unknown - The probe is not able to accurately report metric or state data.
- — Pending - The probe has been scheduled but has not yet run or is unable to run.
- — OK - The probe is running successfully.
- Probe status
- All probes in a given state (OK, WARN, UNKNOWN, CRITICAL, PENDING)
- A Probe Event history
7.10.1.1. Probe Status ⇒ Critical —
7.10.1.3. Probe Status ⇒ Unknown —
7.10.1.4. Probe Status ⇒ Pending —
7.10.1.5. Probe Status ⇒ OK —
7.10.1.6. Probe Status ⇒ All —
7.10.1.7. Current State —
NO DATA SELECTED TIME PERIOD AND METRIC
.
7.10.2. Notification —
7.10.2.1. Notification ⇒ Filters
7.10.2.1.1. Notification ⇒ Notification Filters ⇒ Active Filters
- Description: Enter a value that allows you to distinguish this filter from others.
- Type: Determine what action the filter should take: redirect, acknowledge, suspend, or supplement the incoming notification.
- Send to: The Redirect Notification and Supplemental Notification options in step two require an email address to which to send the notifications. The remaining options require no email address.
- Scope: Determine which monitoring components are subject to the filter.
- 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. To select a range of items, hold the Shift key while clicking on the first and last items in the range.
- Probes in State: Select which probe state(s) relate to the filter. For example, you may choose to create a supplemental notification for critical probes only. Un-check the box to the left of any state you want the filter to ignore.
- Notifications sent to: This is the method to which the notification would be sent if no filter were in place. You may, for example, redirect notifications that would normally go to a user should that individual go on vacation, leaving all other notifications from the probe unchanged.
- Match Output: Select precise notification results by entering a regular expression here. If the "Message:" portion of the notification does not match the regular expression, the filter is not applied.
- Recurring: Select whether a filter runs continuously or on a recurring basis. A recurring filter runs multiple times for a period of time smaller than the duration of the filter. For example, a recurring filter could run for 10 minutes of every hour between the start and end times of the filter. A non-recurring filter runs continuously between the start and end times of the filter.
- Beginning: Enter a date and time for the filter to begin operation.
- Ending: Enter an end date and time for the filter.
- Recurring Duration: How long a recurring filter instance is active. This field, applicable to recurring filters only, begins at the Beginning time specified above. Any notification generated outside of the specified duration is not filtered.
- Recurring Frequency: How often the filter activates.
7.10.2.1.2. Notification ⇒ Notification Filters ⇒ Expired Filters
7.10.3. Probe Suites
- From the Monitoring ⇒ Probe Suites page, select the create probe suite link. Enter an easily 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.
- Add and configure the probes that comprise the Suite. Click the create new probe link in the upper right.
- As described in Section 7.4.2.9.5.2, “System Details ⇒ Monitoring — ”, configure the probe and click the Create Probe button in the lower right. Repeat this process until all desired probes have been added.
Note
Sendmail must be configured correctly on your RHN Satellite and each client system to which the Probe Suite is applied must have therhnmd
daemon installed and running. Refer to the RHN Satellite 5.2.0 Installation Guide for additional information. - Add the systems to which the Probe Suite applies. Click the add systems to probe suite link in the upper right of the screen to continue.
- The next page displays a list of all systems with Monitoring entitlements. Check the box to the left of the system(s) to which you wish to apply the Probe Suite, select the monitoring scout you wish to use, and click the Add systems to probe suite button to complete the creation of the Probe Suite.
- From the Monitoring ⇒ Probe Suites page, click on the title of the Probe Suite you wish to alter.
- Select the Probes sub-tab.
- Check the box next to the probe you wish to remove.
- Click the Delete probes from Probe Suites button.
- From the Monitoring ⇒ Probe Suites page, click on the title of the Probe Suite you wish to alter.
- Select the Systems sub-tab.
- Check the box next to the system(s) you wish to remove from the Probe Suite.
- Click the Detach System(s) from Probe Suite button
Note
- From the Monitoring ⇒ Probe Suites page, click on the title of the Probe Suite you wish to alter.
- Select the Systems sub-tab.
- Check the box next to the system(s) you wish to remove from the Probe Suite.
- Click the Remove System(s) from Probe Suite button.
7.10.4. Scout Config Push —
7.10.5. General Config —
7.11. Admin
7.11.1. Admin ⇒ Organizations
7.11.2. Admin ⇒ RHN Satellite Configuration
7.11.2.1. Admin ⇒ Satellite Configuration ⇒ General
7.11.2.2. Admin ⇒ Satellite Configuration ⇒ Monitoring
7.11.2.3. Admin ⇒ Satellite Configuration ⇒ Certificate
7.11.2.4. Admin ⇒ Satellite Configuration ⇒ Bootstrap Script
/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.
7.11.2.5. Admin ⇒ Satellite Configuration ⇒ Organizations
7.11.2.6. Admin ⇒ Satellite Configuration ⇒ Restart
7.12. Help
7.12.1. Reference Guide
7.12.2. Satellite Installation Guide
7.12.3. Proxy Guide
7.12.4. Client Configuration Guide
7.12.5. Channel Management Guide
7.12.6. Release Notes
7.12.7. API
7.12.8. Search
Figure 7.21. Documentation Search
- Content & Title — Search both the title heading or body content of all available documents
- Free Form — Search documents and indices for any keyword matches, which broadens search results.
- Content — Search only the body content of documentation for more specific matches
- Title — Search only the titles heading of the documentation for targeted, specific search results.
Virtualization
in the title and kickstart
in the content, type the follwing in the Free Form field:
title:Virtualization and content:kickstart
url
— Search the URL for a particular keywordtitle
— Search titles for a particular keywordcontent
— Search the body of the documentation for a particular keyword
Chapter 8. Monitoring
8.1. Prerequisites
- Monitoring entitlements — These entitlements are required for all systems that are to be monitored. Monitoring is supported only on Red Hat Enterprise Linux systems.
- RHN Satellite with Monitoring — Monitoring systems must be connected to a Satellite with a base operating system of Red Hat Enterprise Linux AS 4, Red Hat Enterprise Linux 5 or later. Refer to the RHN Satellite Installation Guide within Help for installation instructions.
- Monitoring Administrator — This role must be granted to users installing probes, creating notification methods, or altering the monitoring infrastructure in any way. (Remember, the Satellite Administrator automatically inherits the abilities of all other roles within an organization and can therefore conduct these tasks.). Assign this role through the User Details page for the user.
- Red Hat Network Monitoring Daemon — This daemon, along with the SSH key for the scout, is required on systems that are monitored in order for the internal process monitors to be executed. You may, however, be able to run these probes using the systems' existing SSH daemon (
sshd
). Refer to Section 8.2, “Red Hat Network Monitoring Daemon (rhnmd
)” for installation instructions and a quick list of probes requiring this secure connection. Refer to Appendix D, Probes for the complete list of available probes.
8.2. Red Hat Network Monitoring Daemon (rhnmd
)
rhnmd
enables the RHN Satellite to communicate securely with the client system to access internal processes and retrieve probe status.
sshd
instead. Refer to Section 8.2.3, “Configuring SSH” for details.
8.2.1. Probes requiring the daemon
sshd
, is required on client systems for the following probes to run:
- Linux::CPU Usage
- Linux::Disk IO Throughput
- Linux::Disk Usage
- Linux::Inodes
- Linux::Interface Traffic
- Linux::Load
- Linux::Memory Usage
- Linux::Process Counts by State
- Linux::Process Count Total
- Linux::Process Health
- Linux::Process Running
- Linux::Swap Usage
- Linux::TCP Connections by State
- Linux::Users
- Linux::Virtual Memory
- LogAgent::Log Pattern Match
- LogAgent::Log Size
- Network Services::Remote Ping
- Oracle::Client Connectivity
- General::Remote Program
- General::Remote Program with Data
8.2.2. Installing the Red Hat Network Monitoring Daemon
sshd
to allow secure connections between the RHN monitoring infrastructure and the monitored systems. Refer to Section 8.2.3, “Configuring SSH” for instructions.
rhnmd
package can be found in the RHN Tools channel for all Red Hat Enterprise Linux distributions. To install it:
- 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 ⇒ Target Systems tab.
- Once subscribed, open the Channel Details ⇒ Packages tab and find the
rhnmd
package (under 'R'). - Click the package name to open the Package Details page. Go to the Target Systems tab, select the desired systems, and click Install Packages.
- Install the SSH public key on all client systems to be monitored, as described in Section 8.2.4, “Installing the SSH key”.
- Start the Red Hat Network Monitoring Daemon on all client systems using the command:
service rhnmd start
- When adding probes requiring the daemon, accept the default values for RHNMD User and RHNMD Port:
nocpulse
and4545
, respectively.
8.2.3. Configuring SSH
sshd
to provide the encrypted connection required between the systems and RHN. This may be especially desirable if you already have sshd
running. To configure the daemon for monitoring use:
- Ensure the SSH package is installed on the systems to be monitored:
rpm -qi openssh-server
- Identify the user to be associated with the daemon. This can be any user available on the system, as long as the required SSH key can be put in the user's
~/.ssh/authorized_keys
file. - Install the SSH public key on all client systems to be monitored, as described in Section 8.2.4, “Installing the SSH key”.
- Start the
sshd
on all client systems using the command:service sshd start
- When adding probes requiring the daemon, insert the values derived from steps 2 and 3 in the RHNMD User and RHNMD Port fields.
8.2.4. Installing the SSH key
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:
- Copy the character string (beginning with
ssh-dss
and ending with the hostname of the RHN Server). - On the command line of the system to be monitored, switch to the user aligned with the daemon. This is accomplished for
rhnmd
with the command:su - nocpulse
- Paste the key character string into the
~/.ssh/authorized_keys
file for the daemon's user. Forrhnmd
, this is/var/lib/nocpulse/.ssh/authorized_keys
.If config management is enabled on the systems to be monitored, you may deploy this file across systems using a config channel. Refer to Section 7.7.1, “Preparing Systems for Config Management” for details.Note
If valid entries already exist inauthorized_keys
, add the daemon key to the file rather than replacing the existing key. To do so, save the copied text toid_dsa.pub
in the same.ssh/
directory and then run the following command:cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
. - Finally, ensure the
.ssh/
directory andauthorized_keys
file have the appropriate permissions set. This can be done as the daemon's user with the following commands:chmod 700 ~/.ssh chmod 600 ~/.ssh/authorized_keys
ssh
connections between the Monitoring infrastructure and the monitored system. You may then schedule probes requiring the monitoring daemon to run against the newly configured systems.
8.3. mysql
package
mysql
package on the RHN Satellite. Refer to Appendix D, Probes for a listing of all available probes.
mysql
package either through the up2date
, yum
or RHN Hosted.
8.4. Notifications
8.4.1. Creating Notification Methods
- Log into the RHN website as either an Satellite Administrator or Monitoring Administrator.
- Navigate to the User Details ⇒ Notification Methods tab and click create new method.
- Enter an intuitive, descriptive label for the method name, such as
DBA day email
, and provide the correct email or pager address. Remember, the labels for all notification methods are available in a single list during probe creation, so they should be unique to your organization. - Select the checkbox if you desire abbreviated messages to be sent to the pager. This shorter format contains only the probe state, system hostname, probe name, time of message, and Send ID. The standard, longer format displays additional message headers, system and probe details, and instructions for response.
- When finished, click Create Method. The new method shows up in the User Details ⇒ Notification Methods tab and the Notification page under the top Monitoring category. Click its name to edit or delete it.
- While adding probes, select the Probe Notifications checkbox and select the new notification method from the resulting dropdown menu. Notification methods assigned to probes cannot be deleted until they are dis-associated from the probe.
8.4.2. Receiving Notifications
Subject: CRITICAL: [hostname]: Satellite: Users at 1 From: "Monitoring Satellite Notification" (rogerthat01@redhat.com) Date: Mon, 6 Dec 2004 13:42:28 -0800 To: user@organization.com This is RHN Monitoring Satellite notification 01dc8hqw. 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
01dc8hqw
.
CRITICAL: [hostname]: Satellite: Users at 21:42 PST, notification 01dc8hqw
8.4.3. Redirecting Notifications
- ACK METOO — Sends the notification to the redirect destination(s) in addition to the default destination.
- ACK SUSPEND — Suspends the notification method for a specified time period.
- ACK AUTOACK — Does not change the destination of the notification, but automatically acknowledges matching alerts as soon as they are sent.
- ACK REDIR — Sends the notification to the redirect destination(s) instead of the default destination.
ACK METOO system 1h boss@domain.com
email ack redirect by user@domain.com
where user equals the sender of the email.
Note
ack suspend host
. However, you cannot halt Satellite probe notifications by responding to a probe with ack suspend host
or other redirect responses. These probes require you to change the notifications within the web interface of the Satellite.
8.4.4. Filtering Notifications
8.4.5. Deleting Notification Methods
- Log into the RHN website as an Satellite Administrator or Monitoring Administrator.
- Navigate to the Monitoring ⇒ Notifications page and click the name of the method to be removed.
- On the User Details ⇒ Notification Methods tab, click delete method. If the method is not associated with any probes, you are presented with a confirmation page. Click Confirm Deletion. The notification method is removed.
Note
Since both the notification method name and address can be edited, consider updating the method rather than deleting it. This redirects notifications from all probes using the method without having to edit each probe and create a new notification method. - If the method is associated with one or more probes, you are presented with a list of the probes using the method and the systems to which the probes are attached instead of a confirmation page. Click the probe name to go directly to the System Details ⇒ Probes tab.
- On the System Details ⇒ Probes tab, select another notification method and click Update Probe.
- You may now return to the Monitoring ⇒ Notifications page and delete the notification method.
8.5. Probes
8.5.1. Managing Probes
- Log into the RHN website as either an Satellite Administrator or the System Group Administrator for the system.
- Navigate to the System Details ⇒ Probes tab and click create new probe.
- On the System Probe Creation page, complete all required fields. First, select the Probe Command Group. This alters the list of available probes and other fields and requirements. Refer to Appendix D, Probes for the complete list of probes by command group. Remember that some probes require the Red Hat Network Monitoring Daemon to be installed on the client system.
- Select the desired Probe Command and the Monitoring Scout, typically
RHN Monitoring Satellite
but possibly an RHN Proxy Server. Enter a brief but unique description for the probe. - Select the Probe Notifications checkbox to receive notifications when the probe changes state. Use the Probe Check Interval dropdown menu to determine how often notifications should be sent. Selecting
1 minute
(and the Probe Notification checkbox) means you will receive notifications every minute the probe surpasses its CRITICAL or WARNING thresholds. Refer to Section 8.4, “Notifications” to find out how to create notification methods and acknowledge their messages. - Use the RHNMD User and RHNMD Port fields, if they appear, to force the probe to communicate via
sshd
, rather than the Red Hat Network Monitoring Daemon. Refer to Section 8.2.3, “Configuring SSH” for details. Otherwise, accept the default values ofnocpulse
and4545
, respectively. - If the Timeout field appears, review the default value and adjust to meet your needs. Most but not all timeouts result in an UNKNOWN state. If the probe's metrics are time-based, ensure the timeout is not less than the time allotted to thresholds. Otherwise, the metrics serve no purpose, as the probe will time out before any thresholds are crossed.
- Use the remaining fields to establish the probe's alert thresholds, if applicable. These CRITICAL and WARNING values determine at what point the probe has changed state. Refer to Section 8.5.2, “Establishing Thresholds” for best practices regarding these thresholds.
- When finished, click Create Probe. Remember, you must commit your Monitoring configuration change on the Scout Config Push page for this to take effect.
8.5.2. Establishing Thresholds
8.5.3. Monitoring the RHN Server
Satellite
Probe Command Group. Next, complete the remaining fields as you would for any other probe. Refer to Section 8.5.1, “Managing Probes” for instructions.
Note
8.6. Troubleshooting
nocpulse
user on the RHN Server conducting the monitoring.
nocpulse
user with the following command:
su - nocpulse
8.6.1. Examining Probes with rhn-catalog
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 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
5
probe ID corresponds to the probe named HTTP
.
--commandline
(-c
) and --dump
(-d
) options along with a probe ID to rhn-catalog
to obtain additional details about the probe, like so:
rhn-catalog --commandline --dump 5
--commandline
option yields the command parameters set for the probe, while --dump
retrieves everything else, including alert thresholds and notification intervals and methods.
5 ServiceProbe on example4.redhat.com (199.168.36.175 ): linux:cpu usage Run as: Unix::CPU.pm --critical=90 --sshhost=199.168.36.175 --warn=70 --timeout=15 --sshuser=nocpulse --shell=SSHRemoteCommandShell --sshport=4545
rhn-runprobe
to examine the probe's output. Refer to Section 8.6.2, “Viewing the output of rhn-runprobe
” for instructions.
8.6.2. Viewing the output of rhn-runprobe
rhn-catalog
, use it in conjunction with rhn-runprobe
to examine the complete output of the probe. Note that by default, rhn-runprobe
works in test mode, meaning no results are entered in the database. Here are its options:
Table 8.1. rhn-runprobe
Options
Option | Description |
---|---|
--help | List the available options and exit. |
--probe=PROBE_ID | Run the probe with this ID. |
--prob_arg=PARAMETER | Override any probe parameters from the database. |
--module=PERL_MODULE | Package name of alternate code to run. |
--log=all=LEVEL | Set log level for a package or package prefix. |
--debug=LEVEL | Set numeric debugging level. |
--live | Execute the probe, enqueue data and send out notifications (if needed). |
--probe
option, the --log
option, and values for each. The --probe
option takes the probeID as its value and the --log
option takes the value "all" (for all run levels) and a numeric verbosity level as its values. Here is an example:
rhn-runprobe --probe=5 --log=all=4
rhn-catalog
, like so:
rhn-runprobe 5 --log=all=4 --sshuser=nocpulse --sshport=4545
Chapter 9. Multiple Organizations
9.1. Recommended Models for Using Multiple Organizations
9.1.1. Centrally-Managed Satellite for A Multi-Department Organization
Figure 9.1. Centralized Satellite Management for Multi-Department Organization
9.1.2. Decentralized Management of Multiple Third Party Organizations
Figure 9.2. Decentralized Satellite Management for Multi-Department Organization
9.1.3. General Tips for Multi-Org Usage
- The administrative organization is treated as a special case with respect to entitlements. You can only add or remove entitlements to this organization implicitly by removing them or adding them from the other organizations on the Satellite.
- The administrative organization is intended to be a staging area for subscriptions and entitlements. When you associate the Satellite with a new certificate, any new entitlements will by granted to this organization by default. In order to make those new entitlements available to other organizations on the Satellite, you will need to explicitly allocate those entitlements to the other organizations from the administrative organization.
9.1.3.1. Certificate Has Less Entitlements Than I Am Using
rhn-satellite-activate
command. You will get an error stating that there are insufficient entitlements in the certificate.
- In the
/etc/rhn/rhn.conf
file, set web.force_unentitlement=1 - Restart the Satellite
- Reduce the allocated entitlements to the desired organizations either via each organization's Subscriptions tab or via individual entitlement's Organizations tabs.
- A number of systems in the organization should now be in an unentitled state. The number of systems unentitled in the organization will be equal to the difference between the total number of entitlements you removed from the organization and the number of entitlements the organization did not have applied to the systems.For example, if you removed 10 entitlements from the organization in step 3, and the organization has 4 entitlements that were not in use by systems, then 6 systems in the organization will be unentitled.
web.force_unentitlement
variable is only necessary to decrement an organization's allocated entitlements below what they are using. If an organization has more entitlements than are being actively used, you do not need to set this variable to remove them.
9.1.3.2. Certificate Has More Entitlements Than I Am Using
9.2. Admin ⇒ Organizations
Figure 9.3. Admin
9.2.1. Admin ⇒ Organizations ⇒ Details
- Active Users — The number of users in the organization
- Systems — The number of systems subscribed to the organization.
- System Groups — The number of groups subscribed to the organization.
- Activation Keys — The number of activation keys available to the organization.
- Kickstart Profiles — The number of kickstart profiles available to the organization.
- Configuration Channels — The number of Configuration Channels available to the organization.
9.3. Creating an Organization
Figure 9.4. Create New Organization
- Input the Organization Name in the provided text box. The name should be between 3 and 128 characters.
- Create an administrator for the organization:
- Enter a Desired Login for the organization administrator, which should be between 3 and 128 characters long.
- Create a Desired Password and Confirm the password.
- Type in the Email for the organization administrator.
- Enter the First Name and Last Name of the organization administrator.
- Click the Create Organization button to complete the process.
Note
orgadmin-mktg
or eng-dept-admin
), to match admin login names with the organization.
9.4. Managing Entitlements
rhn-virtualization
package, which is necessary for the entitlements of Xen virtual guests to be counted correctly corresponding to the number of Red Hat Enterprise Linux subscriptions to which they are associated.
9.4.1. Admin ⇒ Subscriptions ⇒ Software Channel Entitlements
Note
- Total — The total number of channel entitlements for the Satellite.
- Available — The number of entitlements currently available for allocation.
- Usage — The number of entitlements currently in use by all organizations (aside from the base organization), compared to the total number of entitlements allocated.
9.4.2. Admin ⇒ Subscriptions ⇒ System Entitlements
- Total Allocated — The number of total entitlements available for the entire Satellite.
- Entitlement Usage — The number of entitlements currently being used.
- Organization Usage shows the number of organizations that have access to the entitlement.
9.5. Configuring Systems in an Organization
- Registering Using Login and Password — If you provide a login and password created for a specified organization, the system will be registered to that organization. For example, if
user-123
is a member of the Central IT organization on the Satellite, the following command on any system would register that system to the Central IT organization on your Satellite:rhnreg_ks --username=user-123 --password=foobaz
Note
The--orgid
(for Red Hat Enterprise Linux 4 and 5) and--orgpassword
(in RHEL 4) parameters inrhnreg_ks
are not related to Satellite registration or RHN Satellite's multiple organizations support. - Registering Using An Activation Key — You can also register a system to an organization using an activation key from the organization. Activation keys will register systems to the organization in which the activation key was created. Activation keys are a good registration method to use if you want to allow users to register systems into an organization without providing them login access to that organization. If you want to move systems between organizations, you may also automate the move with scripts using the activation keys.
Note
Activation keys have a new format since RHN Satellite 5.1.0, so the first few characters of the activation key are used to indicate which organization (by ID number) owns the activation.
9.6. Organizational Trusts
Note
9.6.1. Establishing an Organizational Trust
Figure 9.5. Organizational Trusts
9.6.2. Sharing Content Channels between Organizations in a Trust
Note
- Login to the Satellite with the username of the Organization Administrator.
- Click on the Channels tab.
- On the side menu, click Manage Software Channels.
- Click the custom channel that you want to share with the other organizations.
- From the Channel Access Control section of the Details page, there are three choices for sharing in Organizational Sharing.
- 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 and Confirm. - Public — Allow all organizations within the trust to access the custom channel.
Click the radio button next to your selection and click Update Channel.
Note
9.6.3. Migrating Systems from One Trusted Organization to Another
migrate-system-profile
.
migrate-system-profile
usage is based on the command-line, and uses systemIDs and orgIDs as arguments to specify what what is being moved and its destination organization.
migrate-system-profile
command, you must have the spacewalk-backend-tools
package installed. You do not need to be logged into the Satellite server to use migrate-system-profile
; however, if you do not you will need specify the hostname or IP address of the server as a command-line switch.
Note
migrate-system-profile
command, the system does not carry any of the previous entitlements or channel subscriptions from the source organization. However, the system's history is preserved, and can be accessed by the new Organization Administrator in order to simplify the rest of the migration process, which includes subscribing to a base channels and granting entitlements.
9.6.3.1. Using migrate-system-profile
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.
migrate-system-profile --satellite {SATELLITE HOSTNAME OR IP} --systemId={SYSTEM ID} --to-org-id={DESTINATION ORGANIZATION ID}
migrate-system-profile --satellite satserver.example.com --systemId=10001020 --to-org-id=2
--username=
and --password=
at the command-line).
Figure 9.6. System History
Note
--csv
option of migrate-system-profile
to automate the process using a simple comma-separated list of systems to migrate.
systemId,to-org-id
systemId
, for example could be 1000010000
, while the to-org-id
could be 4
. So, a compatible CSV could look like the following:
1000010000,3 1000010020,1 1000010010,4
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
Note
9.7.1. Admin ⇒ Organizations ⇒ Details ⇒ Users
Note
Chapter 10. Virtualization
- Red Hat Network Tools for RHEL Server (v. 5 for 32-bit x86) — rhn-tools-rhel-i386-server-5
- RHN Tools — rhn-tools-rhel-4-as-i386
- Red Hat Enterprise Linux Server (v. 5 for 32-bit x86) — rhel-i386-server-5 (and all child channels)
- Red Hat Enterprise Linux Server Virtualization (v. 5 for 32-bit x86) — rhel-i386-server-vt-5 (and all child channels)
10.1. Setting Up the Host System for Your Virtual Systems
10.1.1. Create a Kickstart Profile for the Guest Systems
- Login to the Satellite's web interface. Navigate to the Kickstart Overview screen by clicking the Manage Kickstarts link in the Tasks widget in Your RHN, or by clicking on the Systems tab, followed by the Kickstart subtab in the left navigation bar.
- On the Kickstart Overview page, click the Create a New Kickstart Profile link in the Kickstart Actions widget in the upper right corner.
- You should now find yourself on Step 1 of the kickstart profile creation process:
- Enter a label for your profile that will enable you to distinguish it from your other profiles. For the remaining instructions, we'll assume the label is host-system-for-virtual-guests.
- For the Base Channel field, select Red Hat Enterprise Linux (v.5 for $ARCH) (where $ARCH is the architecture of your host system).
Note
You may install 32-bit Red Hat Enterprise Linux 5 on a 64-bit host system. If you choose to do this, however, please be aware that your guest systems must also run the 32-bit version of Red Hat Enterprise Linux. - In the Kickstartable Tree field, select
ks-rhel-$ARCH-server-5
where $ARCH is the architecture of your host system. - Please select Para-Virtualized Host for the Virtualization Type field.
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. - Finally, click the Next button in the lower right of the screen to continue on to the next step.
Note
If any of the fields are missing the options indicated above, you may not have successfully synced software channel content to your Satellite from Red Hat's servers.
- For Step 2 of the kickstart profile creation process, select the location of the distribution files for the installation of your host system. There should already be a Default Download Location filled out and selected for you on this screen. Click the Next button on this screen to continue to Step 3.
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 server. - For Step 3 of the kickstart profile creation process, please choose a root password to set on the host system you will be provisioning, and click Finish to finish creation of the profile.
- This completes kickstart profile creation. After completing Step 3, you are taken to the newly-created kickstart profile. You may browse through the various tabs of the profile and modify the settings as you see fit, but this is not necessary as the default settings should work well for the majority of cases.
10.1.2. Kickstart Your Host System
10.1.2.1. Your Host System Has Red Hat Enterprise Linux 4 or Earlier Installed
- First, register your host system to your Satellite. Use
ssh
to connect to your host system. Register your host system to your satellite issuing the following command as root: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, add the--force
option to the command above. - 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/. Click on the Systems tab in the top navigation bar. You should see the host system you just registered — click on its profile name to access its system profile page.
- Add a provisioning entitlement to your host system. From your host system profile page, click on Details ⇒ Properties tab. Check the Provisioning checkbox in the Add-On Entitlements field, and click the Update Properties button in the lower right hand corner of the screen.
- Next, schedule the kickstart. You are brought back to the host system's profile page. You should now see a Provisioning tab in the system profile. Click on this tab. This should bring up the Schedule Kickstart page for the system.
- Select the kickstart profile we created for this host earlier. Then, select the Schedule Kickstart and Finish button in the lower right-hand corner of the screen.
Note
If you do not see the kickstart profile you created earlier on the host system's Schedule Kickstart page, you may have created a kickstart profile for an architecture that does not match the architecture of the host system you have registered. If this is the case, open the kickstart profile by navigating to Systems ⇒ Kickstart ⇒ Profiles within the Satellite web interface, and clicking on the label for the host system's kickstart profile. Click on the Kickstart Detail ⇒ Operating System tab, and select items under the Base Channel and Available Trees selections that match the architecture of your host system. Click on the Update Kickstart button in the lower right hand corner of the screen, and navigate back to the host system's Schedule Kickstart page, following the steps above this note. - After scheduling the kickstart, you will be taken to a Kickstart Status screen in the Satellite's web interface. Keep your web browser open to that page to follow along with the host system's progress.
- Use
ssh
to connect to the host system, and run the commandrhn_check
. This should cause the kickstart process to run immediately rather than the next time therhn_check
process runs on the system. You should immediately see output indicating the start of a kickstart process on the host system, and it will eventually warn you that the system is going down for reboot in three minutes. - After three minutes have passed, the system will reboot. Follow the progress of the kickstart via the Satellite web interface.
- Depending on various factors, the kickstart process may take between ten and thirty minutes. At the end of this time period, the Satellite kickstart status page should indicate if the kickstart finished successfully.
Note
If the kickstart fails, the Satellite kickstart status page should indicate that there was a failure. For more details on why the kickstart failed, click on the Events ⇒ History tab in the host system's profile, and click on the name of the kickstart event that failed to get more details on the failure. It may also be useful to consult/var/log/up2date
on the host system for troubleshooting purposes.
10.1.2.2. Your Host System Does Not have Red Hat Enterprise Linux Installed
- You will find an ISO to create a boot CD for you host by using
ssh
to log into your Satellite. It is at the following location on your satellite:/var/satellite/rhn/kickstart/ks-rhel-i386-server-5/images/boot.iso
For details on how to use this ISO image to burn a CD using Linux, please refer to the following Red Hat Knowledgebase Article:If you must burn this ISO image to CD using another operating system, please refer to the following Knowledgebase Article:Note
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. - Insert the boot CD in the drive and reboot the system, making sure the CD-ROM drive is set as the primary boot device in the system's' BIOS.
- After reboot, you should find yourself at a boot prompt. Type the following command at this prompt to start your kickstart:
linux \ ks=http://your-satellite.example.com/ks/label/the profile label you created earlier
Note
For some systems you may either need to addksdevice=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. - The kickstart for your host system should begin. It should take around fifteen minutes to complete. Upon successful completion of this kickstart, you will have provisioned a host system for your virtual guest and registered it to you Satellite.
10.1.2.3. Your Host System Has Red Hat Enterprise Linux 5 Installed
xen
packages are installed on the system. If they are not, install them using the Satellite
- Fist, register your host system to your Satellite. Use
ssh
to connect to your host system. Register your host system to your satellite issuing the following command as root: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, add the--force
to the command above. - 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/. Click on the Systems tab in the top navigational bar. You should see the host system you just registered - click on its profile name to access its system profile page.
- Make sure your system has access to the software channels it needs to access the software required for hosting virtual guests. From your host system's profile page, click on the Alter Channel Subscriptions link on the profile page under the Subscribed Channels header. Check the RHEL Virtualization and Red Hat Network Tools for RHEL Server checkboxes and click the Change Subscriptions button underneath the list of channels.
- Next, check to see if you have the necessary software installed for hosting virtual guest on the system. On the host system, issue the following command as root:
rpm -q xen kernel-xen rhn-virtualization-host
Ifrpm
indicates these packages are not installed, you must install them by running the following command as root on the system: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 ingrub.conf
that pertain to the xen kernel from the beginning of thetitle
line to the end of theinitrd
line, copy the lines, delete them, and paste them so they are the first kernel entry ingrub.conf
. Also ensure that the value of the default variable at the top ofgrub.conf
is set to a value of '0'.Note
If you ever update the kernel on the host system, the standard kernel is the default choice upon reboot. To ensure that the Xen kernel is chosen by default, change the following value in the/etc/sysconfig/kernel
file:DEFAULTKERNEL=kernel
Change the value tokernel-xen
:DEFAULTKERNEL=kernel-xen
- Reboot the system, boot it into the xen kernel. The system should not automatically boot into the xen kernel on reboot but if you would like to make sure it has for troubleshooting purposes, use the command
uname -r
to see if the running kernel is a xen kernel. If you do not see thexen
string in the name of the kernel, you have not booted into the correct kernel.Note
If the system already hasxen
andkernel-xen
installed you do not need to reboot after installingrhn-virtualization-host
. - You will also need to install and run the
osad
package in order for your host system to be responsive to commands sent from the Satellite, such as start, pause, resume, and shutdown. To install:yum install -y osad
after installation, you should then start theosad
process:/sbin/service osad restart
- Your host system should now be ready for RHN virtual guest provisioning.
10.2. Setting Up Your Virtual Systems
10.2.1. Create a Kickstart Profile for the Guest Systems
- Log on to the Satellite's web interface. Navigate to the Kickstart Overview screen by clicking on the Manage Kickstarts link in the Tasks widget in Overview, or by clicking on Systems in the top navigation bar ⇒ Kickstart from the left navigation bar.
- On the Kickstart Overview page, click the Create a new Kickstart Profile link in the Kickstart Actions widget in the upper right corner.
- The next page displayed is Step 1 of the kickstart profile creation process:
- Enter a label for the profile that will allow you to distinguish it from the other profiles. A good choice would be guest-system.
- For the Base Channel field, select Red Hat Enterprise Linux $PRODUCT (v.5 for $ARCH) where $ARCH is the architecture of your host system's operating system and $PRODUCT is either Server or Client.
Note
Red Hat Enterprise Linux Client 5 may not be available for selection if you did not sync the Client software channels to your Satellite.Note
Please note that the channel labels for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 5 Desktop refer to 'server' and 'client' respectively. - For the Kickstartable Tree field, you should select ks-rhel-$ARCH-$PRODUCT-5 where $ARCH is the architecture of your host system and $PRODUCT is either 'server' or 'client', depending on which product with which you would like to provision your guest.
- Select Para-Virtualized Guest for the Virtualization Type field.
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. - Finally, click the Next button in the lower right of the screen to continue on to the next step.
- For Step 2 of the kickstart profile creation process, select the location of the distribution files for the installation of your guest system. There should already be a Default Download Location filled out and selected for you on this screen. Click the Next button on this screen to continue to Step 3.
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. - 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.
- This completes kickstart profile creation. After completing Step 3 you should be taken to the profile details. You may browse through the various tabs of the profile and modify the settings as you see fit, but this is not necessary as the default settings should work well for the majority of cases. While the interface allows you to allocate less, we strongly recommend allocating at least 2 GB of storage for your guest system with this kickstart profile.
10.2.2. Provision Your Guest Systems
- Log into the Satellite's web interface. Browse to your host system's profile by clicking on the Systems tab in the top navigation bar, and click on the system's name.
- To schedule a kickstart for a guest system, go to the Virtualization ⇒ Provisioning tab in the host system's profile. For the Guest Name field choose guest1. For the Memory Allocation, Virtual CPUs, and Storage fields, the default values should be fine. Feel free to change these as desired, taking note of the advice provided for each field in the interface. For the Kickstart Profile field, select the guest system profile we created in the last step.
- Finally, click on the Schedule Kickstart and Finish button in the lower-right corner of the screen. You will be taken to the Kickstart Status page where you can follow along with the guest's kickstart progress. After ten to fifteen minutes the status screen should indicate the kickstart successfully completed. To view your new guest, click on the Virtualization tab of the host system's profile on the Satellite. To view a list of virtual systems, navigate to Systems ⇒ Systems ⇒ Virtual Systems.
Note
If you do not see the Initiate a kickstart for a Xen guest message on the Kickstart Status page shortly after scheduling the kickstart of the guest, you may be missingosad
on your host.Host systems require theosad
package in order to be responsive to commands sent from the Satellite, such as start, pause, resume, and shutdown. Ifosad
is not installed and running, the host system will not receive these commands from the web interface for 2.5 hours, or the next time that the RHN daemon runs.You can check whether or notosad
is installing and running by checking the OSA Status field in the host system's profile on the Satellite. If the field does not exist or indicates a failure of that the system has not contact Satellite in several minutes, then you will need to installyum
(using the commandyum install -y osad
) before you can successfully provision a guest on the host.Note
You may receive the following message from theKickstart 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. A log of the installation process is available, you may wish to review it to troubleshoot this issue.
Be patient and do not worry if you see this message unless more than twenty minutes have passed. To check if the kickstart is continuing, check the installation log to make sure there are no errors, and as you reload the Kickstart Status page check to see that the Last File Request field continues to be updated. - If you would like to register additional guests to your host, repeat the steps above. It is important to remember that you can only provision one guest at a time. If you attempt to schedule a guest kickstart while another is currently taking place, the current guest kickstart process will be canceled and the new guest kickstart process will begin.
- View your newly-created virtual guest's system in the Satellite's web interface by clicking on the Virtualization tab in the host system's profile. Then, click on the profile name of your virtual system. You will be brought to its Satellite system profile.
10.3. Working With Your Virtual Systems
10.3.1. Logging into Virtual Systems Directly via SSH
- You will need to locate the virtual system's IP address. Locate it by navigating to the Systems ⇒ Virtual Systems tab and clicking on the virtual system's profile name.
- On the virtual system's profile page, you'll find the IP address in the left-hand informational column in the IP Address field.
- Connect to the IP address by using
ssh
as root, using the password you set for the virtual system in the kickstart profile you created for it earlier.
10.3.2. Gaining Console Access Via the Host
- 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. look for the guest,guest1
, that we created earlier in this list. If, for example, this guest has been assigned an ID of 2, then: - Run the following command to access the console of this virtual system:
xm console 2
You should immediately be able to view a login prompt onguest1
. - Login to
guest1
as root using the same password you set in the kickstart profile you used to provision the system.(There may be some messages on the screen. In this case, hit the Enter key on your keyboard to receive a fresh login prompt.) - To exit the guest console and return to the host system's command prompt, you may hit the Ctrl and ] keys on your keyboard simultaneously.
10.3.3. Installing Software Via the Satellite Web Interface
- Browse to the virtual system's profile in your Satellite's web interface by logging in and navigating to Systems ⇒ Systems ⇒ Virtual Systems and clicking on the name of your virtual system's profile.
- In the virtual system's profile, click on the Software ⇒ Packages tab.
- Click on Install New Packages in the Packages tab menu.
- Select the packages you wish to install and click the Install Selected Packages button in the lower right-hand corner of the screen.
- Review the package install details and click on the Confirm button in the lower right-hand corner of the screen.
- The package install will take place the next time the guest system checks in with the Satellite. To force the install to take place immediately, you may run the
rhn_check
command on the guest system.
10.3.4. Installing Software Via Yum From the Virtual System
yum
command to install and update software. For example, to install the text editor vim, issue the following command:
yum install -y vim-enhanced
10.3.5. Restarting Guests when Host Reboots
rhn-virtualization-host
service can restart guests automatically in the event of a host system reboot.
- Locate the guest's config file on the host in
/etc/sysconfig/rhn/virt/
. It will be named by UUID, but the correct file can be found by using thegrep
command to search for the guest name within the UUID files. - When you have found the UUID file corresponding to your guest system, create a symbolic link from the UUID file to the
/etc/sysconfig/rhn/virt/auto/
directory.ln -s /etc/sysconfig/rhn/virt/GUEST_UUID.xml /etc/sysconfig/rhn/virt/auto/
10.3.6. Deleting Virtual Systems
- First you must shut down the virtual system that you wish to delete. You may do this by browsing to the host system's profile in the Satellite web interface, clicking on the virtualization tab, and checking off the virtual systems that you would like to delete. Finish shutting down by clicking the Shutdown Systems button at the bottom of the screen.
- Next, delete the virtual system from Satellite. This is accomplished by checking off the virtual system's checkbox and clicking the Delete System button at the bottom of the screen>
Note
Please allow for at least two minutes between shutting down a virtual system and deleting it. Otherwise, the virtual system may not shut down properly and you will delete it while it is running. If you delete a virtual system from Satellite while it is running, it will reappear on the Satellite the next time it checks in. If this happens, simply shutdown the system, wait two minutes, and delete it again. - Delete the disk image for the virtual system you would like to delete. You will find the disk image for guest1, for example, at the following location on the host system:
/var/lib/xen/disk-images/guest1.disk
Delete it with the following command:rm /var/lib/xen/disk-images/guest1.disk
- 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
- You have successfully deleted a guest system from your host system and from Satellite.
Chapter 11. Cobbler
- Installation environment analysis using the
cobbler check
command - Multi-site installation server configuration with
cobbler replicate
- Automation of kickstart file creation using
kickstart import
- Kickstart template creation and management using the Cheetah template engine and Kickstart Snippets
- Virtual machine guest installation automation with the
koan
client-side tool.
11.1. Cobbler Requirements
- If you plan to use Cobbler to install systems using PXE, you must have
tftp-server
installed and configured. - If you plan to use Cobbler to PXE boot systems for installation, you must have either the ability to act as a DHCP server for Cobbler PXE booting or access to your network DHCP server
/etc/dhcp.conf
to changenext-server
to the hostname or IP address of your Cobbler server.
11.1.1. Using cobbler check
cobbler check
command can be run at a shell prompt as root. It will automatically run checks on several services' runtime status and configuration files for proper configuration. The following lists the services and configuration files that cobbler check
tests.
/etc/cobbler/settings
— The central cobbler configuration file;cobbler check
will check to see if you have set theserver
setting to the addressable IP or hostname of the Cobbler server, as well as thenext_server
field set to the hostname or IP of the Cobbler server if it will be also be managing DHCP services for PXE boots.- SELinux — Will verify that you have the correct SELinux setting for HTTPD services and the proper content rules for
tftp
and files in/var/www/cobbler/images/
. cobblerd
— Will check to see if you have the Cobbler daemon running.xinetd
— Will inform you that Xinetd services running and that you have changed the parameterdisabled
tono
in/etc/xinetd.d/tftp
.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).
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.
Note
/etc/cobbler/settings
file, you must run service cobblerd restart
and cobbler sync
for the changes to take effect.
11.1.2. Configuring Cobbler with /etc/cobbler/settings
/etc/cobbler/settings
file. The file contains several configurable settings, and offers detailed explanations for each setting regarding how it affects the functionality of Cobbler and whether it is recommended for users to change the setting for their environment.
/etc/cobbler/settings
file, which documents each setting in detail.
11.1.3. Cobbler and DHCP
11.1.3.1. Configuring an Existing DHCP Server
allow booting; allow bootp; class "PXE" { match if substring(option vendor-class-identifier, 0, 9) = "PXEClient"; next-server 192.168.2.1; filename "pxelinux.0"; }
- The administrator enables network booting with the
bootp
protocol. - 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 asPXEClient
. - Then DHCP server then directs the system to the Cobbler server at 192.168.2.1.
- Finally, the DHCP server refers to the boot image file (in this case, at
/var/lib/tftpboot/pxelinux.0
.
11.1.4. Xinetd and TFTP
/etc/xinetd.d/tftp
as root and change the disable = yes
line to disable = no
.
pxelinux.0
boot image, you must start the Xinetd service.
chkconfig --level 345 xinetd on /sbin/service xinetd start
chkconfig
command turns on the xinetd
service for all user runlevels, while the /sbin/service
command turns on xinetd
immediately.
11.1.5. Configuring SELinux and IPTables for Cobbler Support
11.1.5.1. SELinux Configuration
setsebool -P httpd_can_network_connect true
-P
switch is essential, as it enables HTTPD connection persistently across all system reboots.
semanage fcontext -a -t public_content_t "var/lib/tftpboot/.*"
11.1.5.2. IPTables Configuration
- For TFTP:
/sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 69 -j ACCEPT /sbin/iptables -A INPUT -m state --state NEW -m udp -p udp --dport 69 -j ACCEPT
- For HTTPD:
/sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT /sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
- For Cobbler:
/sbin/iptables -A INPUT -m state --state NEW -m tcp -p udp --dport 25150 -j ACCEPT
- For Koan:
/sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 25151 -j ACCEPT
/sbin/iptables-save
11.1.6. Syncing and Starting the Cobbler Service
cobbler check
are met, you can now start the Cobbler service.
cobbler sync
/usr/sbin/rhn-satellite start
Warning
cobblerd
service independent of the Satellite service, as doing so may cause errors and other issues.
/usr/sbin/rhn-satellite
to start or stop RHN Satellite.
11.2. Adding a Distribution to Cobbler
cobbler
to create a distribution from the command line is as follows:
cobbler distro add --name=string --kernel=path --initrd=path
--name=string
switch is a label used to differentiate one distro choice from another (for example, rhel5server
)
--kernel=path
switch specifies the path to the kernel image file
--initrd=path
switch specifies the path to the initial ramdisk (initrd) image file.
11.3. Adding a Profile to Cobbler
cobbler
to create profiles from the command line is as follows:
cobbler profile add --name=string --distro=string [--kickstart=url] [--virt-file-size=gigabytes] [--virt-ram=megabytes]
--name=string
is the unique label for the profile, such as rhel5webserver
or rhel4workstation
.
--distro=string
switch specifes the distribution that will be used for this particular profile. Distributions were added in Section 11.2, “Adding a Distribution to Cobbler”.
--kickstart=url
option specifies the location of the kickstart file (if available).
--virt-file-size=gigabytes
option allows you to set the size of the virtual guest file image. The default is 5 gigabytes if left unspecified.
--virt-ram=megabytes
option specifies how many megabytes of physical RAM that a virtual guest system can consume. The default is 512 megabytes if left unspecified.
11.4. Adding a System to Cobbler
Note
koan
and PXE menus alone, it is not required to create system records, though they are useful when system-specific kickstart templating is required or to establish that a specific system should always recieve a specific content installed. If there is a specific role inteded for a specified client, system records should be created for it.
cobbler system add --name=string --profile=string --mac=AA:BB:CC:DD:EE:FF
--name=string
is the unique label for the system, such as engineeringserver
or frontofficeworkstation
.
--profile=string
specifies one of the profile names added in Section 11.3, “Adding a Profile to Cobbler”.
--mac=AA:BB:CC:DD:EE:FF
option allows systems with the specified MAC address to automatically be provisioned to the profile associated with the system record if they are being kickstarted.
man cobbler
at a shell prompt.
11.5. Cobbler Templates
- Robust features that allow administrators to create and manage large amounts of profiles or systems without duplication of effort or manually creating kickstarts for every unique situation
- While templates can become complex and involve loops, conditionals and other enhanced features and syntax, it can also be used simply to make kickstart files without such complexity.
11.5.1. Using Templates
/etc/sysconfig/network-scripts/
. However, where templates differ from standard kickstart files are in their use of variables.
network --device=eth0 --bootproto=static --ip=192.168.100.24 --netmask=255.255.255.0 --gateway=192.168.100.1 --nameserver=192.168.100.2
network --device=$net_dev --bootproto=static --ip=$ip_addr --netmask=255.255.255.0 --gateway=$my_gateway --nameserver=$my_nameserver
11.5.2. Kickstart Snippets
$SNIPPET()
function that will be parsed by Cobbler and substitute that function call with the contents of the snippet.
clearpart --all part /boot --fstype ext3 --size=150 --asprimary part / --fstype ext3 --size=40000 --asprimary part swap --recommended part pv.00 --size=1 --grow volgroup vg00 pv.00 logvol /var --name=var vgname=vg00 --fstype ext3 --size=5000
my_partition
), and place the file in /var/lib/cobbler/snippets/
so that Cobbler can access them.
$SNIPPET()
function in your kickstart templates. For example:
$SNIPPET('my_partition')
my_partition
file.
11.6. Using Koan
11.6.1. Using Koan to Provision Virtual Systems
koan
to initiate the installation of a virtual guest on a system.
cobbler add profile --name=virtualfileserver --distro=rhel-i386-server-5 --virt-file-size=20 --virt-ram=1000
koan
:
koan --server=hostname --list=profiles
cobbler profile add
.
koan --virt --server=cobbler-server.example.com --profile=virtualfileserver --virtname=marketingfileserver
virtualfileserver
profile. The virtname
option specifies a label for the virtual guest, which by default is labeled with the system's MAC address.
11.6.2. Using Koan to Re-install Running Systems
koan
can help you by destructively replacing a running system with a new installation from the available Cobbler profiles.
koan --replace-self --server=hostname --profile=name
--profile=name
on the Cobbler server specified in --server=hostname
.
Chapter 12. UNIX Support Guide
12.1. Introduction
12.1.1. Supported UNIX Variants
Table 12.1. Supported Solaris Architectures and Versions
Solaris Version | sun4m | sun4d | sun4u | sun4v | sun4us | x86 |
---|---|---|---|---|---|---|
Solaris 8 | yes | no | yes | n/a | no | no |
Solaris 9 | yes | n/a | yes | n/a | no | yes |
Solaris 10 | n/a | n/a | yes | yes | no | yes |
12.1.2. Prerequisites
- RHN Satellite 5.0.0 or later
- A Satellite certificate with Management entitlements
- Management entitlements for each UNIX client
- RHN packages for UNIX including python, pyOpenSSL, and the Red Hat Network Client packages.
- Sunfreeware packages that provide supporting libraries. Some of these packages are available via the RHN Satellite. Refer to Section 12.3.1, “Download and Install Additional Packages” for the complete list.
12.1.3. Included Features
- The Red Hat Network Service Daemon (
rhnsd
), which triggersrhn_check
according to a configurable interval - The Red Hat Network Configuration Client (
rhncfg-client
), which executes all configuration actions scheduled from the Satellite - The Red Hat Network Configuration Manager (
rhncfg-manager
), which allows command line administration of RHN configuration channels - 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
- A Provisioning feature called Remote Command that enables users to schedule root-level commands on any managed client through the Satellite's website, if the client allows this action
12.1.4. Differences in Functionality
- The Red Hat Update Agent for UNIX offers a much smaller set of options than its Linux counterpart and relies upon the operating system's native toolset for package installation, rather than
rpm
- Refer to Section 12.4.2.4, “Updating From the Command Line” for the precise list of options. - The RHN Push application has been similarly modified to upload native UNIX file types, including packages, patches, and patch clusters.Since Solaris package, patch and patch cluster files are different from RPM files, the channel upload mechanism is somewhat different.There are two applications in the
rhnpush
package for Solaris:- The first,
solaris2mpm
, is an RHN utility that create an MPM file for each Solaris package or patch. The neutral format of the MPM file allows the Satellite to understand and manage the uploaded files. - The second,
rhnpush
, has been extended so that it can handle MPM as well as RPM files. Otherwise, it operates identically to the Linux version ofrhnpush
.
- The Channels tab of the RHN website has been augmented to accommodate the storage and installation of native UNIX file types.
12.1.5. Excluded Features
- All Provisioning-level functionality, such as kickstarting and package rollback, with the exception of configuration file management
- All Errata-related options, since the concept of Errata Updates is not understood in UNIX
- Source files for packages
RHAT*.pkg
files during installation is not yet supported.
12.2. Satellite Server Preparation/Configuration
- During the Satellite installation: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
- 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. In the screen that follows, check the Enable Solaris Support box, as pictured:
Figure 12.2. Enabling UNIX Support After Satellite Installation
Click the Update Configuration button to confirm the change. - 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.To create a Solaris channel, login to the web interface of the Satellite as either an Satellite Administrator or a certificate authority. Navigate to the Channel tab, followed by the Manage Software Channels from the left navigation bar. Click the create new channel link in the upper right of the resulting screen. Provide a name and label for your new channel, and select either Sparc Solaris or i386 Solaris as the architecture, depending on the architecture of your client.
12.3. Client System Preparation
- Download and install
gzip
and required third-party libraries. - Download the RHN application tarball from the Satellite to the client and install the contents.
- Next, deploy the SSL certificates required for a secure connection.
- Configure the client applications to connect to the RHN Satellite.
12.3.1. Download and Install Additional Packages
up2date
), which provides the link between your client systems and Red Hat Network. The UNIX-specific version of the Red Hat Update Agent is limited in functionality compared to its Linux counterpart but still enables system registration and facilitates package installs and patches. Refer to Section 12.4, “Registration and Updates” for a full description of the tool's options.
Note
bash
when first logging into the Solaris client. If the BASH shell is available, it will make the system's behavior as Linux-like as possible.
12.3.1.1. Install Third-Party Packages
gzip
libgcc
openssl
zlib
gzip
utility is provided by the SUNWgzip package and may be downloaded from http://www.sunfreeware.com.
SUNWgccruntime
SUNWopenssl*
SUNWzlib
SMClibgcc
orSMCgcc
SMCossl
SMCzlib
pkginfo
command. For example, to check for a package that contains "zlib" in the name, run the following command:
# pkginfo | grep zlib
Note
libgcc<version>-sol<solaris-version>-sparc-local.gz
becomes SMClibgcc after installation
12.3.1.2. Configure the Library Search Path
# crle -c /var/ld/ld.config
-l
option resets the value, rather than appending it, so if there already were values set on your system, prepend them to the -l parameter.
# crle -c /var/ld/ld.config -l /other/existing/path:/lib:/usr/lib:/usr/local/lib
# crle -c /var/ld/ld.config -l /other/existing/path:/lib:/usr/lib:/usr/local/lib:/usr/sfw/lib
12.3.1.3. Download RHN Client Packages
/var/www/html/pub/
directory of your Satellite. If you are able to use a GUI web browser like Mozilla, navigate to the /pub
directory of the Satellite and save the appropriate tarball to your client:
http://your-satellite.example.com/pub/rhn-solaris-bootstrap-<version>-<solaris-arch>-<solaris-version>.tar.gz
ftp
to transfer the file from the Satellite to the client.
gzip
, decompress the tarball. You should have the following packages:
RHATpossl
RHATrcfg
RHATrcfga
RHATrcfgc
THATrcfgm
RHATrhnc
RHATrhnl
RHATrpush
RHATsmart
SMClibgcc
and SMCosslg
may also be included in the tarball.
12.3.1.4. Install the RHN Packages
pkgadd
command. Answer "yes" to any prompts during package install.
# pkgadd -d RHATpossl-0.6-1.p24.6.pkg all # pkgadd -d RHATpythn-2.4.1-2.rhn.4.sol9.pkg all # pkgadd -d RHATrhnl-1.8-7.p23.pkg all ...
Note
-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 10.
/opt/redhat/rhn/solaris/
.
12.3.1.5. Include RHN Packages in the PATH
# PATH=$PATH:/opt/redhat/rhn/solaris/bin # PATH=$PATH:/opt/redhat/rhn/solaris/usr/bin # PATH=$PATH:/opt/redhat/rhn/solaris/usr/sbin # export PATH
# MANPATH=$MANPATH:/opt/redhat/rhn/solaris/man # export MANPATH
# man -M /opt/redhat/rhn/solaris/man <man page>
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
/pub/
directory of the Satellite's Web server.
- Download the SSL certificate from the
/var/www/html/pub/
directory of the RHN Satellite onto the client system. The certificate will be named something similar toRHN-ORG-TRUSTED-SSL-CERT
. It is accessible via the web at the following URL:https://your-satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT
. - Move the client SSL certificate to the RHN-specific directory for your UNIX variant. For Solaris, this can be accomplished with a command similar to:
mv /path/to/RHN-ORG-TRUSTED-SSL-CERT /opt/redhat/rhn/solaris/usr/share/rhn/
12.3.3. Configuring the clients
- As root, change to the RHN configuration directory for the system. For Solaris, the full path is
/opt/redhat/rhn/solaris/etc/sysconfig/rhn/
. - Open the
up2date
configuration file in a text editor. - Find the
serverURL
entry and set its value to the fully qualified domain name (FQDN) of your RHN Satellite:serverURL[comment]=Remote server URL serverURL=https://your-satellite.example.com/XMLRPC
- Ensure the application refers to the RHN Satellite even when SSL is turned off by also setting the
noSSLServerURL
value to the Satellite:noSSLServerURL[comment]=Remote server URL without SSL noSSLServerURL=http://your-satellite.example.com/XMLRPC
- With the
up2date
configuration file still open, find thesslCACert
entry and set its value to the name and location of the SSL certificate described in Section 12.3.2, “Deploying Client SSL Certificates”, for example:sslCACert[comment]=The CA cert used to verify the ssl server sslCACert=/opt/redhat/rhn/solaris/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
12.4. Registration and Updates
12.4.1. Registering Systems
rhnreg_ks
command to accomplish this; the use of activation keys for registering your systems is optional. These keys allow you to predetermine settings within RHN, such as base channels and system groups, and to apply those automatically to systems during their registration.
- 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.
- On the following page, select the base channel you created at the end of Section 12.2, “Satellite Server Preparation/Configuration”.
- After creating the key, click its name in the Activation Keys list to enhance its RHN settings by associating software and configuration channels and system groups.
- Open a terminal on the client system to be registered and switch user to root.
- Use
rhnreg_ks
along with the--activationkey
option to register the client with the Satellite. The string of characters that make up the key may be copied directly from the Activation Keys list on the website. The resulting command will look something like the following:rhnreg_ks --activationkey=b25fef0966659314ef9156786bd9f3af
- Go back to the website, click the name of the activation key, and ensure the new system appears within the Activated Systems tab.
12.4.2. Obtaining Updates
12.4.2.1. Uploading Packages to the Satellite
solaris2mpm
to translate Solaris packages, patches, and patch clusters to a format that the Satellite can understand.
12.4.2.1.1. solaris2mpm
solaris2mpm
is part of RHN Push for Solaris. The content that is pushed to a Solaris channel on the Satellite must first be in .mpm format.
Note
/tmp/
will be used for this purpose. However, the --tempdir
option allows you to specify another directory if necessary.
# solaris2mpm RHATrpush-3.1.5-21.pkg RHATrpush-3.1.5-23.pkg Opening archive, this may take a while Writing out RHATrpush-3.1.5-21.sparc-solaris.mpm Opening archive, this may take a while Writing out RHATrpush-3.1.5-23.sparc-solaris.mpm
name-version-release.arch.mpm
Table 12.2. solaris2mpm options
Option | Description |
---|---|
--version
|
Displays the program's version number and exits
|
-h, --help
|
Displays this information and exits
|
-?, --usage
|
Prints program usage information and exits
|
--tempdir=<tempdir>
|
Temporary directory to work from
|
--select-arch=<arch>
|
Selects the architecture (i386 or Sparc) for multi-arch packages.
|
12.4.2.1.2. rhnpush
with .mpm Files
rhnpush
works like the standard utility, but with the added ability to handle .mpm files. Below is a usage example:
% rhnpush -v --server testbox.example.com --username myuser -c solaris-8 \ RHATrpush-3.1.5-*.mpm Red Hat Network password: Connecting to http://testbox.example.com/APP Uploading package RHATrpush-3.1.5-21.sparc-solaris.mpm Uploading package RHATrpush-3.1.5-23.sparc-solaris.mpm
Note
12.4.2.2. Updating Through the Website
12.4.2.3. rhnsd
rhnsd
daemon, which instructs the client system to check in with RHN, automatically starts at boot time. On Solaris systems, rhnsd
does not start at boot time by default. It can be started from the command line in this way:
rhnsd --foreground --interval=240
rhnsd
is /opt/redhat/rhn/solaris/usr/sbin/rhnsd
. Below are the available options for rhnsd
on Solaris:
Table 12.3. rhnsd
Options
Option | Description |
---|---|
-f, --foreground
|
Run in foreground
|
-i, --interval=MINS
|
Connect to Red Hat Network every MINS minutes
|
-v, --verbose
|
Log all actions to syslog
|
-h, --help
|
Give this help list
|
-u, --usage
|
Give this help list
|
-V, --version
|
Print program version
|
12.4.2.4. Updating From the Command Line
up2date
command. The most significant difference is the absence of all options regarding source files. Refer to Table 12.4, “Update Agent Command Line Arguments” for the precise list of options available for UNIX systems.
Table 12.4. Update Agent Command Line Arguments
Argument | Description |
---|---|
--version | Show program version information. |
-h , --help | Show this help message and exit. |
-v , --verbose | Show additional output. |
-l , --list | List the latest versions of all packages installed. |
-p , --packages | Update packages associated with this System Profile. |
--hardware | Update this system's hardware profile on RHN. |
--showall | List all packages available for download. |
--show-available | List all the packages available that are not currently installed. |
--show-orphans | List all the packages currently installed that are not in channels the system is subscribed to. |
--show-channels | Show the channel names along with the package names where appropriate. |
--installall | Install all available packages. Use with --channel . |
--channel=CHANNEL | Specify which channels to update from using channel labels. |
--get | Fetch the package specified without resolving dependencies. |
12.5. Remote Commands
12.5.1. Enabling Commands
script
, the file must be named run
, and both must be located in the /etc/sysconfig/rhn/allowed-actions/
directory specific to your UNIX variant.
mkdir -p /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script
touch /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script/run
12.5.2. Issuing Commands
Appendix A. Red Hat Network Registration Client
Warning
A.1. Configuring the Red Hat Network Registration Client
rhn_register --configure
Figure A.1. Red Hat Network Registration Client Configuration
rhn_register --nox --configure
0. enableProxyAuth No 1. noSSLServerURL http://xmlrpc.rhn.redhat.com/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>:
enableProxy
and httpProxy
to enable a proxy server. To enable a proxy server, change the value for enableProxy
to Yes
and the value of 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
.
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.
serverURL
from https
to http
in the /etc/sysconfig/rhn/rhn_register
file.
A.2. Starting the Red Hat Network Registration Client
Important
- On the GNOME desktop, go to Applications (the main menu on the panel) => Programs => System => Red Hat Network
- On the KDE desktop, go to Applications (the main menu on the panel) => System => Red Hat Network
- Type the command
rhn_register
at a shell prompt (for example an XTerm or GNOME terminal) - If you are not running the X Window System, type the command
rhn_register
at a shell prompt. Refer to Section A.7, “Text Mode RHN Registration Client” for further details.
Warning
rpm -q python
. It is strongly recommended that you use Python 1.5.2-24 or later.
Figure A.2. Use Python 1.5.2-24 or later
/etc/sysconfig/rhn/systemid
), and creates a different System Profile. You will no longer be able to use your previous System Profile — be sure this is what you want to do before you choose Yes.
Figure A.3. Warning: This System Already Registered
Figure A.4. Welcome Screen
Figure A.5. Red Hat Privacy Statement
A.3. Registering a User Account
Figure A.6. Error: Username Already Exists
Note
- Cannot contain any spaces
- Cannot contain the characters & +, %, or '
- Is not case-sensitive, thereby eliminating the possibility of duplicate usernames differing only by capitalization
- Must be at least four characters long
- Cannot contain any tabs
- Cannot contain any line feeds
Figure A.7. Create a Unique Username and Password
A.4. Registering a System Profile
A.4.1. Hardware System Profile
- Red Hat Enterprise Linux version
- Hostname
- IP address
- CPU model
- CPU speed
- Amount of RAM
- PCI devices
- Disk sizes
- Mount points
Email Server for Support Team
. Optionally, you can enter a computer serial or identification number for the system.
Figure A.8. System Profile - Hardware
A.4.2. Software System Profile
A.4.2.1. Gathering RPM Database Information
Figure A.9. Registration Wizard
Figure A.10. RPM Package Information
A.4.2.2. Choosing RPM Packages to Exclude from the System Profile
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
Figure A.13. Send System Profile to Red Hat Network
Figure A.14. Registration Finished
A.6. Entitling Your System
- a list of the system for which the user can choose an entitlement level
- the current entitlements applied to each of these systems
- buttons that allow the user to change entitlement level
- an overview of the number and types of purchased entitlements that remain available to the organization
Note
A.7. Text Mode RHN Registration Client
rhn_register --nox
Figure A.15. Text Mode Welcome Screen
Appendix B. Command Line Config Management Tools
Note
/var/lib/rhncfg/backups/
directory on the affected system. The backup retains its filename but has a .rhn-cfg-backup
extension appended.
B.1. Red Hat Network Actions Control
rhn-actions-control
) application is used to enable and disable configuration management of a system. Client systems cannot be managed in this fashion by default. This tool allows Satellite Administrators to enable or disable specific modes of allowable actions such as: deploying a configuration file onto the system, uploading a file from the system, diffing what is currently managed on a system and what is available, or allowing running arbitrary remote commands. These various modes are enabled/disabled by placing/removing files and directories in the /etc/sysconfig/rhn/allowed-actions/
directory. Due to the default permissions on the /etc/sysconfig/rhn/
directory, RHN Actions Control will most likely have to be run by someone with root access.
B.1.1. General command line options
man
page available, as there are for most command line tools, though the use of this tool is simple enough to describe here briefly. Simply decide what RHN scheduled actions should be enabled for use by system administrators. The following options enable the various scheduled action modes:
Table B.1. rhn-actions-control
options
Option | Description |
---|---|
--enable-deploy | Allow rhncfg-client to deploy files. |
--enable-diff | Allow rhncfg-client to diff files. |
--enable-upload | Allow rhncfg-client to upload files. |
--enable-mtime-upload | Allow rhncfg-client to upload mtime. |
--enable-all | Allow rhncfg-client to do everything. |
--enable-run | Enable script.run |
--disable-deploy | Disable deployment. |
--disable-diff | Disable diff |
--disable-upload | Disable upload |
--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 |
rhn-actions-control --enable-all
is common — your system is now ready for config management through RHN.
B.2. Red Hat Network Configuration Client
rhncfg-client
) is installed and run from an individual client system. From there you may use it to gain knowledge about how RHN deploys configuration files to the client.
B.2.1. Listing Config Files
rhncfg-client list
Config Channel File config-channel-17 /etc/example-config.txt config-channel-17 /var/spool/aalib.rpm config-channel-14 /etc/rhn/rhn.conf
rhncfg-manager list config-channel-14
Files in config channel 'config-channel-14' /etc/example-config.txt /etc/rhn/rhn.conf
/etc/example-config.txt
went. The rank of the /etc/example-config.txt
file in config-channel-17
was higher than that of the same 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. Getting a Config File
rhncfg-client get /etc/example-config.txt
Deploying /etc/example-config.txt
less
or another pager. Note that the file is selected as the most relevant based upon the rank of the config channel containing it. This is accomplished within the Configuration tab of the System Details page. Refer to Section 7.4.2.9, “System Details” for instructions.
B.2.3. Viewing Config Channels
rhncfg-client channels
Config channels: Label Name ----- ---- config-channel-17 config chan 2 config-channel-14 config chan 1
rhncfg-client get
:
Table B.2. rhncfg-client get
options
Option | Description |
---|---|
--topdir=TOPDIR | Make all file operations relative to this string. |
-h, --help | Show help message and exit |
B.2.4. Differentiating between Config Files
rhncfg-client diff
--- /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
--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 /usr/bin/diff: /home/test/blah/var/spool/aalib.rpm: No such file or directory
B.2.5. Verifying Config Files
rhncfg-client verify
modified /etc/example-config.txt /var/spool/aalib.rpm
example-config.txt
is locally modified, while aalib.rpm
is not.
rhncfg-client verify
:
Table B.3. rhncfg-client verify
options
Option | Description |
---|---|
-v, --verbose | Increase the amount of output detail. Displays differences in the mode, owner, and group permissions for the specified config file. |
-h, --help | Show help message and exit |
B.3. Red Hat Network Configuration Manager
rhncfg-manager
) is designed to maintain RHN's central repository of config files and channels, not those located on client systems. This tool offers a command line alternative to the configuration management features within the RHN website, as well as the ability to script some or all of the related maintenance.
/etc/sysconfig/rhn/rhncfg-manager.conf
or in the [rhncfg-manager] section of ~/.rhncfgrc
.
~/.rhncfgrc
file. The session file is cached in ~/.rhncfg-manager-session
to prevent logging in for every command.
server.session_lifetime
option and new value to the /etc/rhn/rhn.conf
file on the server running the manager, like so:
server.session_lifetime = 120
rhncfg-manager mode --help
rhncfg-manager diff-revisions --help
rhncfg-manager add
options”.
B.3.1. Creating a Config Channel
rhncfg-manager create-channel channel-label
Red Hat Network username: rhn-user Password: Creating config channel channel-label Config channel channel-label created
B.3.2. Adding Files to a Config Channel
rhncfg-manager add --channel=channel-label
/path/to/file
--dest-file
option in the command, like:
rhncfg-manager add --channel=channel-label
--dest-file=/new/path/to/file.txt
/path/to/file
Pushing to channel example-channel Local file >/path/to/file -> remote file /new/path/to/file.txt
rhncfg-manager add
:
Table B.4. rhncfg-manager add
options
Option | Description |
---|---|
-cCHANNEL --channel=CHANNEL | Upload files in this config channel |
-dDEST_FILE --dest-file=DEST_FILE | Upload the file as this path |
--delim-start=DELIM_START | Start delimiter for variable interpolation |
--delim-end=DELIM_END | End delimiter for variable interpolation |
-h, --help | show help message and exit |
Note
/etc/rhn/rhn.conf
file:
web.maximum_config_file_size=128
B.3.3. Differentiating between Latest Config Files
rhncfg-manager diff --channel=channel-label
--dest-file=/path/to/file.txt
\ /local/path/to/file
/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
rhncfg-manager diff
:
Table B.5. rhncfg-manager diff
options
Option | Description |
---|---|
-cCHANNEL, --channel=CHANNEL | Get file(s) from this config channel |
-rREVISION, --revision=REVISION | Use this revision |
-dDEST_FILE, --dest-file=DEST_FILE | Upload the file as this path |
-tTOPDIR, --topdir=TOPDIR | Make all files relative to this string |
-h, --help | Show help message and exit |
B.3.4. Differentiating between Various Versions
-r
flag to indicate which revision of the file should be compared and the -n
flag to identify the two channels to be checked. Refer to Section B.3.11, “Determining the Number of File Revisions” for related instructions. Specify only one file name here, since you are comparing the file against another version of itself. For example:
rhncfg-manager diff-revisions -n=channel-label1
-r=1
-n=channel-label2
-r=1
/path/to/file.txt
--- /tmp/dest_path/example-config.txt 2004-01-13 14:36:41 \ config channel: example-channel2 revision: 1 --- /tmp/dest_path/example-config.txt 2004-01-13 14:42:42 \ config channel: example-channel3 revision: 1 @@ -1 +1,20 @@ -foo +blaaaaaaaaaaaaaaah +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.0.6 (GNU/Linux) +Comment: For info see http://www.gnupg.org + +iD8DBQA9ZY6vse4XmfJPGwgRAsHcAJ9ud9dabUcdscdcqB8AZP7e0Fua0NmKsdhQCeOWHX +VsDTfen2NWdwwPaTM+S+Cow= +=Ltp2 +-----END PGP SIGNATURE-----
rhncfg-manager diff-revisions
:
Table B.6. rhncfg-manager diff-revisions
options
Option | Description |
---|---|
-cCHANNEL, --channel=CHANNEL | Use this config channel |
-rREVISION, --revision=REVISION | Use this revision |
-h, --help | Show help message and exit |
B.3.5. Downloading All Files in a Channel
rhncfg-manager download-channel channel-label --topdir .
Copying /tmp/dest_path/example-config.txt -> \ blah2/tmp/dest_path/example-config.txt
rhncfg-manager download-channel
:
Table B.7. rhncfg-manager download-channel
options
Option | Description |
---|---|
-tTOPDIR, --topdir=TOPDIR | Directory all the file paths are relative to. This option must be set. |
-h, --help | Show help message and exit |
B.3.6. Getting the Contents of a File
rhncfg-manager get --channel=channel-label
\ /tmp/dest_path/example-config.txt
B.3.7. Listing All Files in a Channel
rhncfg-manager list channel-label
Files in config channel `example-channel3': /tmp/dest_path/example-config.txt
rhncfg-manager get
:
Table B.8. rhncfg-manager get
options
Option | Description |
---|---|
-cCHANNEL, --channel=CHANNEL | Get file(s) from this config channel |
-tTOPDIR, --topdir=TOPDIR | Make all files relative to this string |
-rREVISION, --revision=REVISION | Get this file revision |
-h, --help | Show help message and exit |
B.3.8. Listing All Config Channels
rhncfg-manager list-channels
Available config channels: example-channel example-channel2 example-channel3 config-channel-14 config-channel-17
local_override
or server_import
channels.
B.3.9. Removing a File from a Channel
rhncfg-manager remove --channel=channel-label
/tmp/dest_path/example-config.txt
Red Hat Network username: rhn-user Password: Removing from config channel example-channel3 /tmp/dest_path/example-config.txt removed
rhncfg-manager remove
:
Table B.9. rhncfg-manager remove
options
Option | Description |
---|---|
-cCHANNEL, --channel=CHANNEL | Remove files from this config channel |
-tTOPDIR, --topdir=TOPDIR | Make all files relative to this string |
-h, --help | Show help message and exit |
B.3.10. Deleting a Config Channel
rhncfg-manager remove-channel channel-label
Removing config channel example-channel Config channel example-channel removed
B.3.11. Determining the Number of File Revisions
rhncfg-manager revisions channel-label /tmp/dest_path/example-config.txt
Analyzing files in config channel example-channel \ /tmp/dest_path/example-config.txt: 1
B.3.12. Updating a File in a Channel
rhncfg-manager update \ --channel=channel-label
--dest-file=/path/to/file.txt
/local/path/to/file
Pushing to channel example-channel: Local file example-channel/tmp/dest_path/example-config.txt -> \ remote file /tmp/dest_path/example-config.txt
rhncfg-manager update
:
Table B.10. rhncfg-manager update
options
Option | Description |
---|---|
-cCHANNEL, --channel=CHANNEL | Upload files in this config channel |
-dDEST_FILE, --dest-file=DEST_FILE | Upload the file as this path |
-tTOPDIR, --topdir=TOPDIR | Make all files relative to this string |
--delim-start=DELIM_START | Start delimiter for variable interpolation |
--delim-end=DELIM_END | End delimiter for variable interpolation |
-h, --help | Show help message and exit |
B.3.13. Uploading Multiple Files at Once
rhncfg-manager upload-channel --topdir=topdir
channel-label
Using config channel example-channel4 Uploading /tmp/ola_world.txt from blah4/tmp/ola_world.txt
rhncfg-manager upload-channel
:
Table B.11. rhncfg-manager upload-channel
options
Option | Description |
---|---|
-tTOPDIR, --topdir=TOPDIR | Directory all the file paths are relative to |
-cCHANNEL, --channel=CHANNEL | List of channels the config info will be uploaded into. Channels delimited by ','. Example: --channel=foo,bar,baz |
-h, --help | Show help message and exit |
Appendix C. RHN API Access
C.1. Using the auth Class and Getting the Session
C.2. Obtaining the system_id
system_id
parameter. This is the unique alphanumeric value assigned to each system when registered to RHN. It can be found within the /etc/sysconfig/rhn/systemid
file on each machine. In addition, you may use the download_system_id
method within the system class to obtain the value.
C.3. Determining the sid
sid
, or server ID, parameter. Note that this is different from the system_id
. You may determine the sid
of a machine in two different ways. First, you can log into the RHN website, click the name of a system, and view the sid
at the end of the URL in the location bar. It follows the "=" symbol and is part of a string that resembles the following: "index.pxt?sid=1003486534". Second, you may use the list_user_systems
method within the system class to obtain a list of systems available to the user that contains the associated sid
s.
C.4. Viewing the cid
cid
, is a required parameter for some methods, including set_base_channel
and set_child_channels
. Also like the sid
, the cid
can be obtained through the RHN website. Just click on the name of a channel and view the end of the URL. It follows the "=" symbol, as part of a string that resembles the following: "details.pxt?cid=54".
C.5. Getting the sgid
sgid
, is a required parameter for the set_group_membership
method, for instance. Like the sid
and cid
, the sgid
can be obtained through the RHN website. Just click on the name of a system group and view the end of the URL. It 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
Table C.1. Channel Labels
Channel Label | Platform |
---|---|
channel-i386-sun-solaris | i386 Solaris |
channel-ia32 | IA-32 |
channel-ia64 | IA-64 |
channel-sparc | Sparc |
channel-alpha | Alpha |
channel-s390 | IBM S/390 |
channel-s390x | IBM System z |
channel-iSeries | IBM eServer System i |
channel-pSeries | IBM eServer System p |
channel-x86_64 | AMD64 and Intel EM64T |
channel-ppc | PPC |
channel-sparc-sun-solaris | Sparc Solaris |
C.7. Sample API Script
#!/usr/bin/perl -w use strict; use Frontier::Client; use Data::Dumper; ############################################################################ # This is a sample script for use of the experimental RHN Management APIs. # # The API is currently available using XMLRPC only, which is described in # # depth at: # # # # 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. my $client = new Frontier::Client(url => "http://$HOST/rpc/api"); # Next, we execute a login call, which returns a session identifier that will # be passed in all subsequent calls. The syntax of this call is described at: # # http://$HOST/rpc/api/auth/login/ my $session = $client->call('auth.login', 'username', 'password'); ############################################################################ # System calls. # ############################################################################ # This next call returns a list of systems available to the user. The # syntax of this call is described at: # # http://$HOST/rpc/api/system/list_user_systems/ # # In the code snippet below, we dump data about our systems, and we # capture the ID of the first system we find for future operations. my $systems = $client->call('system.list_user_systems', $session); for my $system (@$systems) { 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. The # 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); for my $package (@$packages) { print Dumper($package); } # Additional system calls are described at: # http://$HOST/rpc/api/system/
Appendix D. Probes
rhnmd
). This requirement is noted within the individual probe reference.
Note
D.1. Probe Guidelines
- Unknown
- The probes that cannot collect the metrics needed to determine probe state. Most (though not all) probes enter this state when exceeding their timeout period. Probes in this state may be configured incorrectly, as well.
- Pending
- The probes whose data has not been received by the RHN Satellite. It is normal for new probes to be in this state. However, if all probes move into this state, your monitoring infrastructure may be failing.
- OK
- The probes that have run successfully without error. This is the desired state for all probes.
- Warning
- The probes that have crossed their WARNING thresholds.
- Critical
- The probes that have crossed their CRITICAL thresholds or reached a critical status by some other means. (Some probes become critical when exceeding their timeout period.)
Important
D.2. Apache 1.3.x and 2.0.x
https
and the port to 443
.
D.2.1. Apache::Processes
- Data Transferred Per Child — Records data transfer information only on individual children. A child process is one that is created from the parent process or another process.
- Data Transferred Per Slot — The cumulative amount of data transferred by a child process that restarts. The number of slots is configured in the
httpd.conf
file using theMaxRequestsPerChild
setting.
ExtendedStatus
directive in the httpd.conf
file of the Web server must be set to On
for this probe to function properly.
Table D.1. Apache::Processes settings
Field | Value |
---|---|
Application Protocol* | http |
Port* | 80 |
Pathname* | /server-status |
UserAgent* | NOCpulse-ApacheUptime/1.0 |
Username | |
Password | |
Timeout* | 15 |
Critical Maximum Megabytes Transferred Per Child | |
Warning Maximum Megabytes Transferred Per Child | |
Critical Maximum Megabytes Transferred Per Slot | |
Warning Maximum Megabytes Transferred Per Slot |
D.2.2. Apache::Traffic
- Current Requests — The number of requests being processed by the server at probe runtime.
- Request Rate — The accesses to the server per second since the probe last ran.
- Traffic — The kilobytes per second of traffic the server has processed since the probe last ran.
ExtendedStatus
directive in the httpd.conf
file of the Web server must be set to On
for this probe to function properly.
Table D.2. Apache::Traffic settings
Field | Value |
---|---|
Application Protocol* | http |
Port* | 80 |
Pathname* | /server-status |
UserAgent* | NOCpulse-ApacheUptime/1.0 |
Username | |
Password | |
Timeout* | 15 |
Critical Maximum Current Requests (number) | |
Warning Maximum Current Requests (number) | |
Critical Maximum Request Rate (events per second) | |
Warning Maximum Request Rate (events per second) | |
Critical Maximum Traffic (kilobytes per second) | |
Warning Maximum Traffic (kilobytes per second) |
D.2.3. Apache::Uptime
Table D.3. Apache::Uptime settings
Field | Value |
---|---|
Application Protocol* | http |
Port* | 80 |
Pathname* | /server-status |
UserAgent* | NOCpulse-ApacheUptime/1.0 |
Username | |
Password | |
Timeout* | 15 |
D.3. BEA WebLogic 6.x and higher
community_prefix@managed_server_name
in order for the SNMP query to return results for the desired Managed Server. Finally, SNMP must be enabled on each monitored system. SNMP support can be enabled and configured through the WebLogic Console.
D.3.1. BEA WebLogic::Execute Queue
- Idle Execute Threads — The number of execution threads in an idle state.
- Queue Length — The number of requests in the queue.
- Request Rate — The number of requests per second.
Table D.4. BEA WebLogic::Execute Queue settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 1 |
BEA Domain Admin Server | |
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 |
D.3.2. BEA WebLogic::Heap Free
- Heap Free — The percentage of free heap space.
Table D.5. BEA WebLogic::Heap Free settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 1 |
BEA Domain Admin Server | |
BEA Server Name* | myserver |
Critical Maximum Heap Free | |
Warning Maximum Heap Free | |
Warning Minimum Heap Free | |
Critical Minimum Heap Free |
D.3.3. BEA WebLogic::JDBC Connection Pool
- Connections — The number of connections to the JDBC.
- Connections Rate — The speed at which connections are made to the JDBC, measured in connections per second.
- Waiters — The number of sessions waiting to connect to the JDBC.
Table D.6. BEA WebLogic::JDBC Connection Pool settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 1 |
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 |
D.3.4. BEA WebLogic::Server State
Table D.7. BEA WebLogic::Server State settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 1 |
BEA Domain Admin Server | |
BEA Server Name* |
D.3.5. BEA WebLogic::Servlet
- High Execution Time — The highest amount of time in milliseconds that the servlet takes to execute since the system was started.
- Low Execution Time — The lowest amount of time in milliseconds that the servlet takes to execute since the system was started.
- Execution Time Moving Average — A moving average of the execution time.
- Execution Time Average — A standard average of the execution time.
- Reload Rate — The number of times the specified servlet is reloaded per minute.
- Invocation Rate — The number of times the specified servlet is invoked per minute.
Table D.8. BEA WebLogic::Servlet settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 1 |
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 |
D.4. General
D.4.1. General::Remote Program
rhnmd
) must be running on the monitored system to execute this probe.
Table D.9. General::Remote Program settings
Field | Value |
---|---|
Command* | |
OK Exit Status* | 0 |
Warning Exit Status* | 1 |
Critical Exit Status* | 2 |
Timeout | 15 |
D.4.2. General::Remote Program with Data
- <perldata> </perldata>
- <hash> </hash>
- <item key =" "> </item>
STDOUT
:
<perldata> <hash> <item key="data">10</item> <item key="status_message">status message here</item> </hash> </perldata>
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. Remote programs that do not include a status_message
still report the value and status returned.
rhnmd
) must be running on the monitored system to execute this probe. XML is case-sensitive. The data
item key name cannot be changed and it must collect a number as its value.
Table D.10. General::Remote Program with Data settings
Field | Value |
---|---|
Command* | |
OK Exit Status* | 0 |
Warning Exit Status* | 1 |
Critical Exit Status* | 2 |
Timeout | 15 |
D.4.3. General::SNMP Check
1.3.6.1.2.1.1.1.0
) and a threshold associated with the return value. It collects the following metric:
- Remote Service Latency — The time it takes in seconds for the SNMP server to answer a connection request.
Table D.11. General::SNMP Check settings
Field | Value |
---|---|
SNMP OID* | |
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 2 |
Timeout* | 15 |
Critical Maximum Value | |
Warning Maximum Value | |
Warning Minimum Value | |
Critical Minimum Value |
D.4.4. General::TCP Check
- Remote Service Latency — The time it takes in seconds for the TCP server to answer a connection request.
Table D.12. General::TCP Check settings
Field | Value |
---|---|
Send | |
Expect | |
Port* | 1 |
Timeout* | 10 |
Critical Maximum Latency | |
Warning Maximum Latency |
D.4.5. General::UDP Check
- Remote Service Latency — The time it takes in seconds for the UDP server to answer a connection request.
Table D.13. General::UDP Check settings
Field | Value |
---|---|
Port* | 1 |
Send | |
Expect | |
Timeout* | 10 |
Critical Maximum Latency | |
Warning Maximum Latency |
D.4.6. General::Uptime (SNMP)
Table D.14. General::Uptime (SNMP) settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 2 |
Timeout* | 15 |
D.5. Linux
rhnmd
daemon be running on the monitored system.
D.5.1. Linux::CPU Usage
- CPU Percent Used — The five-second average of the percent of CPU usage at probe execution.
rhnmd
) must be running on the monitored system to run this probe.
Table D.15. Linux::CPU Usage settings
Field | Value |
---|---|
Timeout* | 15 |
Critical Maximum CPU Percent Used | |
Warning Maximum CPU Percent Used |
D.5.2. Linux::Disk IO Throughput
- Read Rate — The amount of data that is read in kilobytes per second.
- Write Rate — The amount of data that is written in kilobytes per second.
iostat
on the system to be monitored and see what name has been assigned to the disk you desire. The default value of 0
usually provides statistics from the first hard drive connected directly to the system.
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.
Table D.16. Linux::Disk IO Throughput settings
Field | Value |
---|---|
Disk number or disk name* | 0 |
Timeout* | 15 |
Critical Maximum KB read/second | |
Warning Maximum KB read/second | |
Warning Minimum KB read/second | |
Critical Minimum KB read/second | |
Critical Maximum KB written/second | |
Warning Maximum KB written/second | |
Warning Minimum KB written/second | |
Critical Minimum KB written/second |
D.5.3. Linux::Disk Usage
- File System Used — The percentage of the file system currently in use.
- Space Used — The amount of the file system in megabytes currently in use.
- Space Available — The amount of the file system in megabytes currently available.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.17. Linux::Disk Usage settings
Field | Value |
---|---|
File system* | /dev/hda1 |
Timeout* | 15 |
Critical Maximum File System Percent Used | |
Warning Maximum File System Percent Used | |
Critical Maximum Space Used | |
Warning Maximum Space Used | |
Warning Minimum Space Available | |
Critical Minimum Space Available |
D.5.4. Linux::Inodes
- Inodes — The percentage of inodes currently in use.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.18. Linux::Inodes settings
Field | Value |
---|---|
File system* | / |
Timeout* | 15 |
Critical Maximum Inodes Percent Used | |
Warning Maximum Inodes Percent Used |
D.5.5. Linux::Interface Traffic
- Input Rate — The traffic in bytes per second going into the specified interface.
- Output Rate — The traffic in bytes per second going out of the specified interface.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.19. Linux::Interface Traffic settings
Field | Value |
---|---|
Interface* | |
Timeout* | 30 |
Critical Maximum Input Rate | |
Warning Maximum Input Rate | |
Warning Minimum Input Rate | |
Critical Minimum Input Rate | |
Critical Maximum Output Rate | |
Warning Maximum Output Rate | |
Warning Minimum Output Rate | |
Critical Minimum Output Rate |
D.5.6. Linux::Load
- Load — The average load on the system CPU over various periods.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.20. Linux::Load settings
Field | Value |
---|---|
Timeout* | 15 |
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 |
D.5.7. Linux::Memory Usage
- RAM Free — The amount of free random access memory (RAM) in megabytes on a system.
yes
or no
in the Include reclaimable memory field.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.21. Linux::Memory Usage settings
Field | Value |
---|---|
Include reclaimable memory | no |
Timeout* | 15 |
Warning Maximum RAM Free | |
Critical Maximum RAM Free |
D.5.8. Linux::Process Counts by State
- Blocked — A process that has been switched to the waiting queue and whose state has been switched to
waiting
. - Defunct — A process that has terminated (either because it has been killed by a signal or because it has called
exit()
) and whose parent process has not yet received notification of its termination by executing some form of thewait()
system call. - Stopped — A process that has been stopped before its execution 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.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.22. Linux::Process Counts by State settings
Field | Value |
---|---|
Timeout* | 15 |
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 |
D.5.9. Linux::Process Count Total
- Process Count — The total number of processes currently running on the system.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.23. Linux::Process Count Total settings
Field | Value |
---|---|
Timeout* | 15 |
Critical Maximum Process Count | |
Warning Maximum Process Count |
D.5.10. Linux::Process Health
- CPU Usage — The CPU usage rate for a given process in milliseconds per second. This metric reports the
time
column ofps
output, which is the cumulative CPU time used by the process. This makes the metric independent of probe interval, allows sane thresholds to be set, and generates usable graphs (i.e. a sudden spike in CPU usage shows up as a spike in the graph). - Child Process Groups — The number of child processes spawned from the specified parent process. A child process inherits most of its attributes, such as open files, from its parent.
- Threads — The number of running threads for a given process. A thread is the basic unit of CPU utilization, and consists of a program counter, a register set, and a stack space. A thread is also called a lightweight process.
- Physical Memory Used — The amount of physical memory (or RAM) in kilobytes used by the specified process.
- Virtual Memory Used — The amount of virtual memory in kilobytes used by the specified process, or the size of the process in real memory plus swap.
Command not found
is displayed and the probe will be set to a CRITICAL state.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.24. Linux::Process Health settings
Field | Value |
---|---|
Command Name | |
Process ID (PID) file | |
Timeout* | 15 |
Critical Maximum CPU Usage | |
Warning Maximum CPU Usage | |
Critical Maximum Child Process Groups | |
Warning Maximum Child Process Groups | |
Critical Maximum Threads | |
Warning Maximum Threads | |
Critical Maximum Physical Memory Used | |
Warning Maximum Physical Memory Used | |
Critical Maximum Virtual Memory Used | |
Warning Maximum Virtual Memory Used |
D.5.11. Linux::Process Running
Command not found
is displayed and the probe enters a CRITICAL state.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.25. Linux::Process Running settings
Field | Value |
---|---|
Command name | |
PID file | |
Count process groups | (checked) |
Timeout* | 15 |
Critical Maximum Number Running | |
Critical Minimum Number Running |
D.5.12. Linux::Swap Usage
- Swap Free — The percent of swap memory currently free.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.26. Linux::Swap Usage settings
Field | Value |
---|---|
Timeout* | 15 |
Warning Minimum Swap Free | |
Critical Minimum Swap Free |
D.5.13. Linux::TCP Connections by State
- TIME_WAIT — The socket is waiting after close for remote shutdown transmission so it may handle packets still in the network.
- CLOSE_WAIT — The remote side has been shut down and is now waiting for the socket to close.
- FIN_WAIT — The socket is closed, and the connection is now shutting down.
- ESTABLISHED — The socket has a connection established.
- SYN_RCVD — The connection request has been received from the network.
netstat -ant
command to retrieve data. The Local IP address and Local port parameters use values in the Local Address column of the output; the Remote IP address and Remote port parameters use values in the Foreign Address column of the output for reporting.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.27. Linux::TCP Connections by State settings
Field | Value |
---|---|
Local IP address filter pattern list | |
Local port number filter | |
Remote IP address filter pattern list | |
Remote port number filter | |
Timeout* | 15 |
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 | |
Critical Maximum SYN_RCVD Connections | |
Warning Maximum SYN_RCVD Connections |
D.5.14. Linux::Users
- Users — The number of users currently logged in.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.28. Linux::Users settings
Field | Value |
---|---|
Timeout* | 15 |
Critical Maximum Users | |
Warning Maximum Users |
D.5.15. Linux::Virtual Memory
- Virtual Memory — The percent of total system memory - random access memory (RAM) plus swap - that is free.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.29. Linux::Virtual Memory settings
Field | Value |
---|---|
Timeout* | 15 |
Warning Minimum Virtual Memory Free | |
Critical Minimum Virtual Memory Free |
D.6. LogAgent
nocpulse
user must be granted read access to your log files.
D.6.1. LogAgent::Log Pattern Match
- Regular Expression Matches — The number of matches that have occurred since the probe last ran.
- Regular Expression Match Rate — The number of matches per minute since the probe last ran.
rhnmd
) must be running on the monitored system to execute this probe. For this probe to run, the nocpulse
user must be granted read access to your log files.
egrep
, which is equivalent to grep -E
and supports extended regular expressions. This is the regular expression set for egrep
:
^ beginning of line $ end of line . match one char * match zero or more chars [] match one character set, e.g. '[Ff]oo' [^] match not in set '[^A-F]oo' + match one or more of preceding chars ? match zero or one of preceding chars | or, e.g. a|b () groups chars, e.g., (foo|bar) or (foo)+
Warning
egrep
to fail silently and the probe to time out.
Table D.30. LogAgent::Log Pattern Match settings
Field | Value |
---|---|
Log file* | /var/log/messages |
Basic regular expression* | |
Timeout* | 45 |
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 |
D.6.2. LogAgent::Log Size
- Size — The size the log file has grown in bytes since the probe last ran.
- Output Rate — The number of bytes per minute the log file has grown since the probe last ran.
- Lines — The number of lines written to the log file since the probe last ran.
- Line Rate — The number of lines written per minute to the log file since the probe last ran.
rhnmd
) must be running on the monitored system to execute this probe. For this probe to run, the nocpulse
user must be granted read access to your log files.
Table D.31. LogAgent::Log Size settings
Field | Value |
---|---|
Log file* | /var/log/messages |
Timeout* | 20 |
Critical Maximum Size | |
Warning Maximum Size | |
Warning Minimum Size | |
Critical Minimum Size | |
Critical Maximum Output Rate | |
Warning Maximum Output Rate | |
Warning Minimum Output Rate | |
Critical Minimum Output Rate | |
Critical Maximum Lines | |
Warning Maximum Lines | |
Warning Minimum Lines | |
Critical Minimum Lines | |
Critical Maximum Line Rate | |
Warning Maximum Line Rate | |
Warning Minimum Line Rate | |
Critical Minimum Line Rate |
D.7. MySQL 3.23 - 3.33
mysqladmin
binary. No specific user privileges are needed for these probes.
mysql-server
package must be installed on the system conducting the monitoring for these probes to complete. Refer to the MySQL Installation section of the RHN Satellite Installation Guide for instructions.
D.7.1. MySQL::Database Accessibility
Table D.32. MySQL::Database Accessibility settings
Field | Value |
---|---|
Username* | |
Password | |
MySQL Port | 3306 |
Database* | mysql |
Timeout | 15 |
D.7.2. MySQL::Opened Tables
- Opened Tables — The tables that have been opened since the server was started.
Table D.33. MySQL::Opened Tables settings
Field | Value |
---|---|
Username | |
Password | |
MySQL Port* | 3306 |
Timeout | 15 |
Critical Maximum Opened Objects | |
Warning Maximum Opened Objects | |
Warning Minimum Opened Objects | |
Critical Minimum Opened Objects |
D.7.3. MySQL::Open Tables
- Open Tables — The number of tables open when the probe runs.
Table D.34. MySQL::Open Tables settings
Field | Value |
---|---|
Username | |
Password | |
MySQL Port* | 3306 |
Timeout | 15 |
Critical Maximum Open Objects | |
Warning Maximum Open Objects | |
Warning Minimum Open Objects | |
Critical Minimum Open Objects |
D.7.4. MySQL::Query Rate
- Query Rate — The average number of queries per second per database server.
Table D.35. MySQL::Query Rate settings
Field | Value |
---|---|
Username | |
Password | |
MySQL Port* | 3306 |
Timeout | 15 |
Critical Maximum Query Rate | |
Warning Maximum Query Rate | |
Warning Minimum Query Rate | |
Critical Minimum Query Rate |
D.7.5. MySQL::Threads Running
- Threads Running — The total number of running threads within the database.
Table D.36. MySQL::Threads Running settings
Field | Value |
---|---|
Username | |
Password | |
MySQL Port* | 3306 |
Timeout | 15 |
Critical Maximum Threads Running | |
Warning Maximum Threads Running | |
Warning Minimum Threads Running | |
Critical Minimum Threads Running |
D.8. Network Services
D.8.1. Network Services::DNS Lookup
dig
command to see if it can resolve the system or domain name specified in the Host or Address to look up field. It collects the following metric:
- Query Time — The time in milliseconds required to execute the
dig
request.
Table D.37. Network Services::DNS Lookup settings
Field | Value |
---|---|
Host or Address to look up | |
Timeout* | 10 |
Critical Maximum Query Time | |
Warning Maximum Query Time |
D.8.2. Network Services::FTP
- Remote Service Latency — The time it takes in seconds for the FTP server to answer a connection request.
Table D.38. Network Services::FTP settings
Field | Value |
---|---|
Expect | FTP |
Username | |
Password | |
FTP Port* | 21 |
Timeout* | 10 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.3. Network Services::IMAP Mail
- Remote Service Latency — The time it takes in seconds for the IMAP server to answer a connection request.
Table D.39. Network Services::IMAP Mail settings
Field | Value |
---|---|
IMAP Port* | 143 |
Expect* | OK |
Timeout* | 5 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.4. Network Services::Mail Transfer (SMTP)
- Remote Service Latency — The time it takes in seconds for the SMTP server to answer a connection request.
Table D.40. Network Services::Mail Transfer (SMTP) settings
Field | Value |
---|---|
SMTP Port* | 25 |
Timeout* | 10 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.5. Network Services::Ping
ping
the monitored system or a specified IP address. It also checks 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 system. This probe collects the following metrics:
- 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.
ping
from an RHN Server and not the monitored system. Populating the IP Address field does not test connectivity between the system and the specified IP address but between the RHN Server and the IP address. Therefore, entering the same IP address for Ping probes on different systems accomplishes precisely the same task. To conduct a ping
from a monitored system to an individual IP address, use the Remote Ping probe instead. Refer to Section D.8.7, “Network Services::Remote Ping”.
Table D.41. Network Services::Ping settings
Field | Value |
---|---|
IP Address (defaults to system IP) | |
Packets to send* | 20 |
Timeout* | 10 |
Critical Maximum Round-Trip Average | |
Warning Maximum Round-Trip Average | |
Critical Maximum Packet Loss | |
Warning Maximum Packet Loss |
D.8.6. Network Services::POP Mail
- Remote Service Latency — The time it takes in seconds for the POP server to answer a connection request.
+OK
. If the expected string is not found, the probe returns a CRITICAL state.
Table D.42. Network Services::POP Mail settings
Field | Value |
---|---|
Port* | 110 |
Expect* | +OK |
Timeout* | 10 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.7. Network Services::Remote Ping
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. This probe collects the following metrics:
- Round-Trip Average — The time it takes in milliseconds for the ICMP ECHO packet to travel to and from the IP address.
- Packet Loss — The percent of data lost in transit.
rhnmd
) must be running on the monitored system to execute this probe.
Table D.43. Network Services::Remote Ping settings
Field | Value |
---|---|
IP Address* | |
Packets to send* | 20 |
Timeout* | 10 |
Critical Maximum Round-Trip Average | |
Warning Maximum Round-Trip Average | |
Critical Maximum Packet Loss | |
Warning Maximum Packet Loss |
D.8.8. Network Services::RPCService
- Remote Service Latency — The time it takes in seconds for the RPC server to answer a connection request.
Table D.44. Network Services::RPCService settings
Field | Value |
---|---|
Protocol (TCP/UDP) | udp |
Service Name* | nfs |
Timeout* | 10 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.9. Network Services::Secure Web Server (HTTPS)
- Remote Service Latency — The time it takes in seconds for the HTTPS server to answer a connection request.
Table D.45. Network Services::Secure Web Server (HTTPS) settings
Field | Value |
---|---|
URL Path | / |
Expect Header | HTTP/1 |
Expect Content | |
UserAgent* | NOCpulse-check_http/1.0 |
Username | |
Password | |
Timeout* | 10 |
HTTPS Port* | 443 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.10. Network Services::SSH
- Remote Service Latency — The time it takes in seconds for the SSH server to answer a connection request.
Table D.46. Network Services::SSH settings
Field | Value |
---|---|
SSH Port* | 22 |
Timeout* | 5 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.8.11. Network Services::Web Server (HTTP)
- Remote Service Latency — The time it takes in seconds for the HTTP server to answer a connection request.
Table D.47. Network Services::Web Server (HTTP) settings
Field | Value |
---|---|
URL Path | / |
Virtual Host | |
Expect Header | HTTP/1 |
Expect Content | |
UserAgent* | NOCpulse-check_http/1.0 |
Username | |
Password | |
Timeout* | 10 |
HTTP Port* | 80 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.9. Oracle 8i, 9i, and 10g
$ORACLE_HOME/rdbms/admin/catalog.sql
D.9.1. Oracle::Active Sessions
- Active Sessions — The number of active sessions based on the value of
V$PARAMETER.PROCESSES
. - Available Sessions — The percentage of active sessions that are available based on the value of
V$PARAMETER.PROCESSES
.
Table D.48. Oracle::Active Sessions settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
Critical Maximum Active Sessions | |
Warning Maximum Active Sessions | |
Critical Maximum Available Sessions Used | |
Warning Maximum Available Sessions Used |
D.9.2. Oracle::Availability
Table D.49. Oracle::Availability settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
D.9.3. Oracle::Blocking Sessions
- Blocking Sessions — The number of sessions preventing other sessions from committing changes to the Oracle database, as determined by the required Time Blocking value you provide. Only those sessions that have been blocking for this duration, which is measured in seconds, are counted as blocking sessions.
Table D.50. Oracle::Blocking Sessions settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Time Blocking (seconds)* | 20 |
Timeout* | 30 |
Critical Maximum Blocking Sessions | |
Warning Maximum Blocking Sessions |
D.9.4. Oracle::Buffer Cache
- Db Block Gets — The number of blocks accessed via single block gets (not through the consistent get mechanism).
- Consistent Gets — The number of accesses made to the block buffer to retrieve data in a consistent mode.
- Physical Reads — The cumulative number of blocks read from disk.
- Buffer Cache Hit Ratio — The rate at which the database goes to the buffer instead of the hard disk to retrieve data. A low ratio suggests more RAM should be added to the system.
Table D.51. Oracle::Buffer Cache settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port | 1521 |
Timeout* | 30 |
Warning Minimum Buffer Cache Hit Ratio | |
Critical Minimum Buffer Cache Hit Ratio |
D.9.5. Oracle::Client Connectivity
rhnmd
connection to the system and issues a sqlplus connect
command on the monitored system.
V$DATABASE.NAME
. This value is case-insensitive. A CRITICAL status is returned if this value is not found.
rhnmd
) must be running on the monitored system to execute this probe. For this probe to run, the nocpulse
user must be granted read access to your log files.
Table D.52. Oracle::Client Connectivity settings
Field | Value |
---|---|
Oracle Hostname or IP address* | |
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
ORACLE_HOME* | /opt/oracle |
Expected DB Name* | |
Timeout* | 30 |
D.9.6. Oracle::Data Dictionary Cache
init.ora
. It collects the following metrics:
- Data Dictionary Hit Ratio — The ratio of cache hits to cache lookup attempts in the data dictionary cache. In other words, the rate at which the database goes to the dictionary instead of the hard disk to retrieve data. A low ratio suggests more RAM should be added to the system.
- Gets — The number of blocks accessed via single block gets (not through the consistent get mechanism).
- Cache Misses — The number of accesses made to the block buffer to retrieve data in a consistent mode.
Table D.53. Oracle::Data Dictionary Cache settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
Warning Minimum Data Dictionary Hit Ratio | |
Critical Minimum Data Dictionary Hit Ratio |
D.9.7. Oracle::Disk Sort Ratio
- Disk Sort Ratio — The rate of Oracle sorts that were too large to be completed in memory and were instead sorted using a temporary segment.
Table D.54. Oracle::Disk Sort Ratio settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
Critical Maximum Disk Sort Ratio | |
Warning Maximum Disk Sort Ratio |
D.9.8. Oracle::Idle Sessions
- Idle Sessions — The number of Oracle sessions that are idle, as determined by the required Time Idle value you provide. Only those sessions that have been idle for this duration, which is measured in seconds, are counted as idle sessions.
Table D.55. Oracle::Idle Sessions settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Time Idle (seconds)* | 20 |
Timeout* | 30 |
Critical Maximum Idle Sessions | |
Warning Maximum Idle Sessions |
D.9.9. Oracle::Index Extents
- Allocated Extents — The number of allocated extents for any index.
- Available Extents — The percentage of available extents for any index.
%
that matches any index name.
Table D.56. Oracle::Index Extents settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Index Owner* | % |
Index Name* | % |
Timeout* | 30 |
Critical Maximum of Allocated Extents | |
Warning Maximum of Allocated Extents | |
Critical Maximum of Available Extents | |
Warning Maximum of Available Extents |
D.9.10. Oracle::Library Cache
init.ora
. It collects the following metrics:
- Library Cache Miss Ratio — The rate at which a library cache pin miss occurs. This happens when a session executes a statement that it has already parsed but finds that the statement is no longer in the shared pool.
- Executions — The number of times a pin was requested for objects of this namespace.
- Cache Misses — The number of pins of objects with previous pins since the object handle was created that must now retrieve the object from disk.
Table D.57. Oracle::Library Cache settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
Critical Maximum Library Cache Miss Ratio | |
Warning Maximum Library Cache Miss Ratio |
D.9.11. Oracle::Locks
- 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.
Table D.58. Oracle::Locks settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
Critical Maximum Active Locks | |
Warning Maximum Active Locks |
D.9.12. Oracle::Redo Log
- Redo Log Space Request Rate — The average number of redo log space requests per minute since the server has been started.
- Redo Buffer Allocation Retry Rate — The average number of buffer allocation retries per minute since the server was started.
Table D.59. Oracle::Redo Log settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
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 |
D.9.13. Oracle::Table Extents
- Allocated Extents-Any Table — The total number of extents for any table.
- Available Extents-Any Table — The percentage of available extents for any table.
%
that matches any table owner or name.
Table D.60. Oracle::Table Extents settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Table Owner* | % |
Table Name* | % |
Timeout* | 30 |
Critical Maximum Allocated Extents | |
Warning Maximum Allocated Extents | |
Critical Maximum Available Extents | |
Warning Maximum Available Extents |
D.9.14. Oracle::Tablespace Usage
- Available Space Used — The percentage of available space in each tablespace that has been used.
%
that matches any table name.
Table D.61. Oracle::Tablespace Usage settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Tablespace Name* | % |
Timeout* | 30 |
Critical Maximum Available Space Used | |
Warning Maximum Available Space Used |
D.9.15. Oracle::TNS Ping
- Remote Service Latency — The time it takes in seconds for the Oracle server to answer a connection request.
Table D.62. Oracle::TNS Ping settings
Field | Value |
---|---|
TNS Listener Port* | 1521 |
Timeout* | 15 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
D.10. RHN Satellite
D.10.1. RHN Satellite::Disk Space
- File System Used — The percent of the current file system now in use.
- Space Used — The file size used by the current file system.
- Space Available — The file size available to the current file system.
Table D.63. RHN Satellite::Disk Space settings
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 |
D.10.2. RHN Satellite::Execution Time
- Probe Execution Time Average — The seconds required to fully execute a probe.
Table D.64. RHN Satellite::Execution Time settings
Field | Value |
---|---|
Critical Maximum Probe Execution Time Average | |
Warning Maximum Probe Execution Time Average |
D.10.3. RHN Satellite::Interface Traffic
- Input Rate — The amount of traffic in bytes per second the device receives.
- Output Rate — The amount of traffic in bytes per second the device sends.
Table D.65. RHN Satellite::Interface Traffic settings
Field | Value |
---|---|
Interface* | eth0 |
Timeout (seconds)* | 30 |
Critical Maximum Input Rate | |
Critical Maximum Output Rate |
D.10.4. RHN Satellite::Latency
- Probe Latency Average — The lag in seconds between the time a probe becomes ready to run and the time it is actually run. Under normal conditions, this is generally less than a second. When a Satellite is overloaded (because it has too many probes with respect to their average execution time), the number goes up.
Table D.66. RHN Satellite::Latency settings
Field | Value |
---|---|
Critical Maximum Probe Latency Average | |
Warning Maximum Probe Latency Average |
D.10.5. RHN Satellite::Load
- Load — The load average on the CPU for a 1-, 5-, and 15-minute period.
Table D.67. RHN Satellite::Load settings
Field | Value |
---|---|
Critical Maximum 1-minute Average | |
Warning Maximum 1-minute Average | |
Critical Maximum 5-minute Average | |
Warning Maximum 5-minute Average | |
Critical Maximum 15-minute Average | |
Warning Maximum 15-minute Average |
D.10.6. RHN Satellite::Probe Count
- Probes — The number of individual probes running on a Satellite.
Table D.68. RHN Satellite::Probe Count settings
Field | Value |
---|---|
Critical Maximum Probe Count | |
Warning Maximum Probe Count |
D.10.7. RHN Satellite::Process Counts
- Blocked — The number of processes that have been switched to the waiting queue and waiting state.
- Child — The number of processes spawned by another process already running on the machine.
- Defunct — The number of processes that have terminated (either because they have been killed by a signal or have called
exit()
) and whose parent processes have not yet received notification of their termination by executing some form of thewait()
system call. - 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.
Table D.69. RHN Satellite::Process Counts settings
Field | Value |
---|---|
Critical Maximum Blocked Processes | |
Warning Maximum Blocked Processes | |
Critical Maximum Child Processes | |
Warning Maximum Child Processes | |
Critical Maximum Defunct Processes | |
Warning Maximum Defunct Processes | |
Critical Maximum Stopped Processes | |
Warning Maximum Stopped Processes | |
Critical Maximum Sleeping Processes | |
Warning Maximum Sleeping Processes |
D.10.8. RHN Satellite::Processes
- Processes — The number of processes running simultaneously on the machine.
Table D.70. RHN Satellite::Processes settings
Field | Value |
---|---|
Critical Maximum Processes | |
Warning Maximum Processes |
D.10.9. RHN Satellite::Process Health
- CPU Usage — The CPU usage percent for a given process.
- Child Process Groups — The number of child processes spawned from the specified parent process. A child process inherits most of its attributes, such as open files, from its parent.
- Threads — The number of running threads for a given process. A thread is the basic unit of CPU utilization, and consists of a program counter, a register set, and a stack space. A thread is also called a lightweight process.
- Physical Memory Used — The amount of physical memory in kilobytes being used by the specified process.
- 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.
Command not found
is displayed and the probe is set to a CRITICAL state.
Table D.71. RHN Satellite::Process Health settings
Field | Value |
---|---|
Command Name | |
Process ID (PID) file | |
Timeout* | 15 |
Critical Maximum CPU Usage | |
Warning Maximum CPU Usage | |
Critical Maximum Child Process Groups | |
Warning Maximum Child Process Groups | |
Critical Maximum Threads | |
Warning Maximum Threads | |
Critical Maximum Physical Memory Used | |
Warning Maximum Physical Memory Used | |
Critical Maximum Virtual Memory Used | |
Warning Maximum Virtual Memory Used |
D.10.10. RHN Satellite::Process Running
Table D.72. RHN Satellite::Process Running settings
Field | Value |
---|---|
Command Name | |
Process ID (PID) file | |
Critical Number Running Maximum | |
Critical Number Running Minimum |
D.10.11. RHN Satellite::Swap
Table D.73. RHN Satellite::Swap settings
Field | Value |
---|---|
Critical Minimum Swap Percent Free | |
Warning Minimum Swap Percent Free |
D.10.12. RHN Satellite::Users
Table D.74. RHN Satellite::Users settings
Field | Value |
---|---|
Critical Maximum Users | |
Warning Maximum Users |
Glossary
- Action
- A task that is scheduled by a system administrator using Red Hat Network to be performed on one or more client systems. For example, an action can be scheduled to update the kernel packages on all the systems within a selected group.
- Activation Key
- RHN Management and Provisioningcustomers can generate activation keys through the RHN website. Each unique key can then be used to register a Red Hat system, entitle the system to RHN, subscribe the system to specific channels, and subscribe the system to RHN system groups through the command line utility
rhnreg_ks
from therhn_register
package. - Base Channel
- A base channel is a type of Channel that consists of a list of packages based on a specific architecture and Red Hat release. For example, all the packages in Red Hat Enterprise Linux AS 3 for the x86 architecture make a base channel.
- Bug Fix Alert
- An Errata Alert that pertains to a bug fix.
- Bugzilla
- Bugzilla is an online application (http://www.redhat.com/bugzilla) that allows users to communicate directly with the developers. From Bugzilla, users can submit bug reports and feature requests for Red Hat Enterprise Linux and related open source packages.
- Channel
- A channel is a list of packages. Channels are used to choose packages to be installed from client systems. Every client system must be subscribed to one Base Channel and can be subscribed to one or more Child Channel .
- Child Channel
- A child channel is a Channel associated with a Base Channel but contains extra packages.
- Client System
- See Registered System .
- Digital Certificate
- A client component in XML format that is stored in the
/etc/sysconfig/rhn/systemid
file on registered systems. Red Hat Network verifies this certificate to authenticate the registered system before each connection. This certificate is issued by Red Hat and passed to the system as part of the registration process. It includes unique information about the registered system to avoid fraudulent use. - Email Notification
- Similar to an Errata Alert , except the information is delivered via email. If the email notifications option is selected, notifications are sent for every Red Hat Network Errata Alert . The email includes the type of Errata Alert, summary of the Errata, description of the Errata, and a list of which systems are affected by the report.
- Enhancement Alert
- An Errata Alert that pertains to a package enhancement request.
- Entitled Server
- A server that is subscribed to an RHN service level. Because the server is entitled, the RHN website can be used to manage its packages.
- Errata
- Information published by Red Hat describing security fixes, bug fixes, and package enhancements for Red Hat Enterprise Linux. 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.Security issues and bug fixes are submitted by Red Hat engineers as well as the Linux community through Bugzilla which generates a bug report for each issue. Red Hat engineering evaluates the reports, resolves the bug, and generates new RPM packages. After the Red Hat quality assurance team tests new packages they are placed on the Red Hat Public File Server and on the Red Hat Network Server and an Errata is generated.
- Errata Alert
- RHN Errata Alert that updated packages based on Red Hat Errata are available for one or more systems within an organization. There are three types of Errata Alerts: Security Alerts, Bug Fix Alerts, and Enhancement Alerts.
- Management
- One of the RHN service level offerings. It has more features than the Update service level, including user management, system groups, and enhanced system details.
- Notification Method
- An email address to which RHN Monitoring messages will be sent.
- Package
- All software in Red Hat Enterprise Linux is divided into software packages. Software updates are released in the form of RPM packages that can be installed on a Red Hat Enterprise Linux system.
- Probe
- A set of criteria that is either a template or a set of values assigned to a system that is used to measure the performance of a system.
- Probe State
- The measure of a probe's adherence to its defined criteria. States include: OK, Warning, Critical, Pending, Unknown
- Probe Suite
- collection or group of RHN Monitoring Probes.
- Provisioning
- One of the RHN service level offerings. It has more features than the Management service level, including kickstarting, reconfiguring, tracking, and reverting systems.
- Red Hat Network Daemon
- The RHN client daemon (
rhnsd
) that periodically polls Red Hat Network for scheduled actions. - Red Hat Network Registration Client
- The RHN client application (
rhn_register
) that collects information about the client system, creates a System Profile and Digital Certificate , establishes a connection with the Red Hat Network servers, and registers the system with Red Hat Network. - Red Hat Update Agent
- The RHN client application (
up2date
) that allows users to retrieve and install all updated packages for the client system on which the application is run. Use the Red Hat Update Agent Configuration Tool to configure its preferences, including whether to install the packages after they are downloaded. - Registered System
- A system that is registered with Red Hat Network. Also known as a client system.
- RPM
- A software package manager that was developed by Red Hat Inc.. It can be used to build, install, query, verify, update, and uninstall software packages. All software updates from RHN are delivered in RPM format.
- RPM Database
- Each Red Hat Enterprise Linux system has an RPM database that stores information about all the RPM packages installed on the system. This information includes the version of the package, which files were installed with the package, a brief description of the package, the installation date, and more.
- RPM Update
- Red Hat Network option to deliver the RPM packages based on the Errata Alert list to a client system without user intervention. If this feature is selected, packages are delivered through the Red Hat Network Daemon running on the client system.
- Satellite Administrator
- Satellite Administrator are sets of users that have the highest level of control over an organization's Red Hat Network account. Members of this group can add users, systems, and system groups to the organization as well as remove them. An Satellite Administrator can also give users administrative privileges to system groups. An RHN organization must have at least one member of the Satellite Administrator group.
- Security Alert
- An Errata Alert that pertains to system security.
- Service Level
- A Red Hat Network subscription service. Different service levels offer different features of RHN. There are three paid service levels currently available: RHN Update, RHN Management, and RHN Provisioning.
- Sibling
- Siblings are virtual guests running on the same host. Virtual guests that run on separate hosts are not siblings.
- Software Manager
- The name of the first Service Level offering for Red Hat Network. Software Manager is now known as RHN Update .
- System Directory
- The System Directory section of Red Hat Network allows an organization to divide its client systems into system groups. Only members of the Satellite Administrator group can add systems to the organization.
- System ID
- A unique string of characters and numbers that identifies a registered system. It is stored in the system's Digital Certificate .
- System Profile
- Hardware and software information about the client system. It is created during the registration process. The software information is a list of RPM packages and their versions installed on the client system. The System Profile is used to determine every Errata Alert 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. Update was formerly called Basic. Update offers the same services as the Basic subscription did, plus more new features.
- Virtual Guest
- Any of the virtual instances running on the virtual host, under the control of the hypervisor. Also referred to as domain U or domU.
- Virtual Host
- The physical system that supports the hypervisor and all guest systems. The virtual host may also be referred to as domain 0, or dom0.
- Yellowdog Updater Modified (yum)
- The Yellowdog Updater Modified is the Red Hat Network client application (
yum
) that allows users to retrieve and install new or updated packages for the client system on which the application is run.
Appendix E. Revision History
Revision History | |||
---|---|---|---|
Revision 2-60.400 | 2013-10-31 | Rüdiger Landmann | |
| |||
Revision 2-60 | 2012-07-18 | Anthony Towns | |
| |||
Revision 2-58 | Tue April 19 2011 | Lana Brindley | |
| |||
Revision 1.0-0 | Fri Feb 27 2009 | ||
|
Index
A
- account
- deactivate, Account Deactivation
- action
- completed systems, Action Details ⇒ Completed Systems
- details, Action Details ⇒ Details
- failed systems, Action Details ⇒ Failed Systems
- in progress systems, Action Details ⇒ In Progress Systems
- activation key, Activation Keys —
- deleting, Managing Activation Keys
- disabling, Managing Activation Keys
- editing, Managing Activation Keys
- activation keys
- creating, editing, and deleting, Managing Activation Keys
- multiple use, Using Multiple Activation Keys at Once —
- registration, Registering with Activation Keys
- using, Registering with Activation Keys
- addresses
- change, Addresses
- Apache
- probes, Apache 1.3.x and 2.0.x
- Processes, Apache::Processes
- Traffic, Apache::Traffic
- Uptime, Apache::Uptime
- application programming interface
- API, RHN API Access
B
- base channel, Software Channels
C
- changing email address, User List ⇒ Active ⇒ User Details ⇒ Details —
- changing password, User List ⇒ Active ⇒ User Details ⇒ Details —
- channel
- configuration
- create, Configuration Channels
- Channel List , Software Channels
- Channels
- Software and Configuration Files, Channels
- channels, Channels
- all, All Channels
- base, Software Channels
- child, Software Channels
- errata, Software Channel Details ⇒ Errata
- list of, Software Channels
- My, My Channels
- packages, Software Channel Details ⇒ Packages
- Popular, Popular Channels
- Red Hat, Red Hat Channels
- Shared, Shared Channels
- Channels and Packages
- Channel List, Software Channels
- child channel, Software Channels
- client applications
- obtaining, Before You Begin
- redirecting, Configuring the clients
- client systems
- configuring, Configuring the clients
- registering, Registering Systems
- updating, Obtaining Updates
- Cobbler, Cobbler
- cobbler , Cobbler
- config management
- system preparation, Preparing Systems for Config Management
- configuration
- actions, Configuration
- channel
- create, Configuration Channels
- files, Configuration
- Schedule, Configuration
- Configuration Management
- command line tools, Command Line Config Management Tools
- create
- configuration
- channel, Configuration Channels
- custom information
- about systems, System Details ⇒ Details ⇒ Custom Info —
D
- deactivate
- delete
- user (RHN Satellite only), User List ⇒ Active ⇒ User Details —
- deleting a system, System Details ⇒ Details
- Digital Certificate, Security, Quality Assurance, and Red Hat Network
E
- email address
- change, Change Email
- changing, User List ⇒ Active ⇒ User Details ⇒ Details —
- entitlement
- with activation key, Activation Keys —
- Errata, Errata
- Advanced Search, Advanced Search
- All Errata, All Errata
- apply applicable, System Details ⇒ Software ⇒ Errata
- Relevant Errata, Relevant Errata
- Errata Alert Icons
- explanation of, Errata Alert Icons
- Errata notifications
- automatic updates, Errata Notifications and Scheduled Package Installations
- Errata Updates
- applying, Apply Errata Updates
- searching, Advanced Search
- viewing details, Errata Details
- viewing list of all errata, All Errata
- viewing list of applicable errata, Relevant Errata
- EUS (see Extended Update Support)
- Extended Update Support, Extended Update Support (EUS)
G
- General
- probes, General
- Remote Program, General::Remote Program
- Remote Program with Data, General::Remote Program with Data
- SNMP Check, General::SNMP Check
- TCP Check, General::TCP Check
- UDP Check, General::UDP Check
- Uptime (SNMP), General::Uptime (SNMP)
- getting started, Before You Begin
- GNU Privacy Guard, Security, Quality Assurance, and Red Hat Network
H
- hardware profile
- Updating on server, System Details ⇒ Details ⇒ Hardware
- Help Desk, Help
- HTTP Proxy, Configuring the Applet
I
- initialization script
- /etc/init.d/rhnsd , Red Hat Network Daemon
- /etc/rc.d/init.d/rhnsd , Red Hat Network Daemon
K
- kickstart
- explained, Kickstart Explained
- Koan, Cobbler
- koan, Cobbler
L
- Linux
- CPU Usage, Linux::CPU Usage
- Disk IO Throughput, Linux::Disk IO Throughput
- Disk Usage, Linux::Disk Usage
- Inodes, Linux::Inodes
- Interface Traffic, Linux::Interface Traffic
- Load, Linux::Load
- Memory Usage, Linux::Memory Usage
- probes
- nocpulse, Linux
- Process Count Total, Linux::Process Count Total
- Process Counts by State, Linux::Process Counts by State
- Process Health, Linux::Process Health
- Process Running, Linux::Process Running
- Swap Usage, Linux::Swap Usage
- TCP Connections by State, Linux::TCP Connections by State
- Users, Linux::Users
- Virtual Memory, Linux::Virtual Memory
- List Navigation
- explanation of, Lists
- LogAgent
- Log Pattern Match, LogAgent::Log Pattern Match
- Log Size, LogAgent::Log Size
- probes
- nocpulse, LogAgent
M
- macros
- within configuration Files
- interpolation, Including Macros in your Configuration Files
- Management
- service level, Management
- manual installation
- System Profile, Manual Package Installation
- Monitoring, Monitoring —
- All, Probe Status ⇒ All —
- Critical, Probe Status ⇒ Critical —
- Current State, Current State —
- General Config, General Config —
- introduction, Monitoring
- Notification, Notification —
- OK, Probe Status ⇒ OK —
- Pending, Probe Status ⇒ Pending —
- prerequisites, Prerequisites
- Scout Config Push, Scout Config Push —
- service level, Monitoring
- Status, Probe Status —
- Unknown, Probe Status ⇒ Unknown —
- Warning, Probe Status ⇒ Warning —
- monitoring
- list of probes, Probes
- MySQL , mysql package
- Database Accessibility, MySQL::Database Accessibility
- Open Tables, MySQL::Open Tables
- Opened Tables, MySQL::Opened Tables
- probes, MySQL 3.23 - 3.33
- Query Rate, MySQL::Query Rate
- Threads Running, MySQL::Threads Running
- mysql package, mysql package
N
- navigation, Navigation
- Network Services
- DNS Lookup, Network Services::DNS Lookup
- FTP, Network Services::FTP
- IMAP Mail, Network Services::IMAP Mail
- Mail Transfer (SMTP), Network Services::Mail Transfer (SMTP)
- Ping, Network Services::Ping
- POP Mail, Network Services::POP Mail
- probes, Network Services
- Remote Ping, Network Services::Remote Ping
- RPCService, Network Services::RPCService
- Secure Web Server (HTTPS), Network Services::Secure Web Server (HTTPS)
- SSH, Network Services::SSH
- Web Server (HTTP), Network Services::Web Server (HTTP)
- notes
- about systems, System Details ⇒ Details ⇒ Notes
- Notification
- filter, General Config —
- Notifications
- Monitoring, Notifications
- notifications
- creating methods, Creating Notification Methods
- deleting methods, Deleting Notification Methods
- filtering, Filtering Notifications
- receiving, Receiving Notifications
- redirecting, Redirecting Notifications
- ntsysv , Disabling
O
- Oracle
- Active Sessions, Oracle::Active Sessions
- Availability, Oracle::Availability
- Blocking Sessions, Oracle::Blocking Sessions
- Buffer Cache, Oracle::Buffer Cache
- Client Connectivity, Oracle::Client Connectivity
- Data Dictionary Cache, Oracle::Data Dictionary Cache
- Disk Sort Ratio, Oracle::Disk Sort Ratio
- Idle Sessions, Oracle::Idle Sessions
- Index Extents, Oracle::Index Extents
- Library Cache, Oracle::Library Cache
- Locks, Oracle::Locks
- probes, Oracle 8i, 9i, and 10g
- Redo Log, Oracle::Redo Log
- Table Extents, Oracle::Table Extents
- Tablespace Usage, Oracle::Tablespace Usage
- TNS Ping, Oracle::TNS Ping
- Overview, Overview
- Account Deactivation, Account Deactivation
- Addresses, Addresses
- Email, Change Email
- Help, Help
- Your Account, Your Account
- Your Preferences, Your Preferences
- overview of website, Categories and Pages
P
- package installation
- package list
- Updating on server, Synchronizing Your System Profile, System Details ⇒ Software ⇒ Packages
- Package Updater (pup)
- complete description, Package Updater
- packages
- password
- change, Your Account
- port 22, Configuring SSH
- port 4545, Red Hat Network Monitoring Daemon (rhnmd)
- preferences
- change, Your Preferences
- language, Locale Preferences
- locale, Locale Preferences
- probe
- guidelines, Probe Guidelines
- probe list
- Apache
- Processes, Apache::Processes
- Traffic, Apache::Traffic
- Uptime, Apache::Uptime
- General
- Remote Program, General::Remote Program
- Remote Program with Data, General::Remote Program with Data
- SNMP Check, General::SNMP Check
- TCP Check, General::TCP Check
- UDP Check, General::UDP Check
- Uptime (SNMP), General::Uptime (SNMP)
- Linux
- CPU Usage, Linux::CPU Usage
- Disk IO Throughput, Linux::Disk IO Throughput
- Disk Usage, Linux::Disk Usage
- Inodes, Linux::Inodes
- Interface Traffic, Linux::Interface Traffic
- Load, Linux::Load
- Memory Usage, Linux::Memory Usage
- Process Count Total, Linux::Process Count Total
- Process Counts by State, Linux::Process Counts by State
- Process Health, Linux::Process Health
- Process Running, Linux::Process Running
- Swap Usage, Linux::Swap Usage
- TCP Connections by State, Linux::TCP Connections by State
- Users, Linux::Users
- Virtual Memory, Linux::Virtual Memory
- LogAgent
- Log Pattern Match, LogAgent::Log Pattern Match
- Log Size, LogAgent::Log Size
- MySQL
- Database Accessibility, MySQL::Database Accessibility
- Open Tables, MySQL::Open Tables
- Opened Tables, MySQL::Opened Tables
- Query Rate, MySQL::Query Rate
- Threads Running, MySQL::Threads Running
- Network Services
- DNS Lookup, Network Services::DNS Lookup
- FTP, Network Services::FTP
- IMAP Mail, Network Services::IMAP Mail
- Mail Transfer (SMTP), Network Services::Mail Transfer (SMTP)
- Ping, Network Services::Ping
- POP Mail, Network Services::POP Mail
- Remote Ping, Network Services::Remote Ping
- RPCService, Network Services::RPCService
- Secure Web Server (HTTPS), Network Services::Secure Web Server (HTTPS)
- SSH, Network Services::SSH
- Web Server (HTTP), Network Services::Web Server (HTTP)
- Oracle
- Active Sessions, Oracle::Active Sessions
- Availability, Oracle::Availability
- Blocking Sessions, Oracle::Blocking Sessions
- Buffer Cache, Oracle::Buffer Cache
- Client Connectivity, Oracle::Client Connectivity
- Data Dictionary Cache, Oracle::Data Dictionary Cache
- Disk Sort Ratio, Oracle::Disk Sort Ratio
- Idle Sessions, Oracle::Idle Sessions
- Index Extents, Oracle::Index Extents
- Library Cache, Oracle::Library Cache
- Locks, Oracle::Locks
- Redo Log, Oracle::Redo Log
- Table Extents, Oracle::Table Extents
- Tablespace Usage, Oracle::Tablespace Usage
- TNS Ping, Oracle::TNS Ping
- RHN Satellite
- Disk Space, RHN Satellite::Disk Space
- Execution Time, RHN Satellite::Execution Time
- Interface Traffic, RHN Satellite::Interface Traffic
- Latency, RHN Satellite::Latency
- Load, RHN Satellite::Load
- Probe Count, RHN Satellite::Probe Count
- Process Counts, RHN Satellite::Process Counts
- Process Health, RHN Satellite::Process Health
- Process Running, RHN Satellite::Process Running
- Processes, RHN Satellite::Processes
- Swap, RHN Satellite::Swap
- Users, RHN Satellite::Users
- WebLogic
- Execute Queue, BEA WebLogic::Execute Queue
- Heap Free, BEA WebLogic::Heap Free
- JDBC Connection Pool, BEA WebLogic::JDBC Connection Pool
- Server State, BEA WebLogic::Server State
- Servlet, BEA WebLogic::Servlet
- Probes
- Monitoring, Probes
- probes
- Apache, Apache 1.3.x and 2.0.x
- General, General
- Linux, Linux
- LogAgent
- nocpulse, LogAgent
- managing, Managing Probes
- MySQL, MySQL 3.23 - 3.33
- Network Services, Network Services
- on the RHN Server, Monitoring the RHN Server
- Oracle, Oracle 8i, 9i, and 10g
- RHN Satellite, RHN Satellite
- thresholds, Establishing Thresholds
- WebLogic, BEA WebLogic 6.x and higher
- Provisioning
- service level, Provisioning
- proxy server
- with Red Hat Network Alert Notification Tool , Configuring the Applet
- with Red Hat Network Registration Client, Configuring the Red Hat Network Registration Client
- with Red Hat Update Agent, General Settings
Q
- quality assurance
- Quick Search
- explanation of, Quick Search
R
- reactivating
- Red Hat Enterprise Linux 2.1
- requiring the Red Hat Network Registration Client, Introduction to the Guide, Red Hat Update Agent
- Red Hat Enterprise Linux 5
- rhn_register, The rhn_register Client
- Red Hat Network
- an introduction to, Red Hat Network Overview
- components
- primary, Red Hat Network Overview
- Red Hat Network Actions Control
- rhn-actions-control , Red Hat Network Actions Control
- Red Hat Network Alert Notification Tool
- adding to panel, Red Hat Network Alert Notification Tool
- applying Errata Updates, Applying Updates
- configuring, Configuring the Applet
- icons, Notification Icons
- launching RHN website, Launching the RHN Website
- requirements, Red Hat Network Alert Notification Tool
- with a proxy server, Configuring the Applet
- Red Hat Network Configuration Client
- rhncfg-client , Red Hat Network Configuration Client
- Red Hat Network Configuration Manager
- rhncfg-manager , Red Hat Network Configuration Manager
- Red Hat Network Daemon, Red Hat Network Daemon
- configuring, Configuring
- disabling, Disabling
- initial description, Red Hat Network Overview
- troubleshooting, Troubleshooting
- using to apply Errata Updates, Apply Errata Updates
- viewing status, Viewing Status
- Red Hat Network Monitoring Daemon
- (rhnmd) monitoring daemon, Red Hat Network Monitoring Daemon (rhnmd)
- installation, Installing the Red Hat Network Monitoring Daemon
- probes requiring the daemon, Probes requiring the daemon
- SSH key installation, Installing the SSH key
- using sshd instead, Configuring SSH
- Red Hat Network packages
- comparison, Before You Begin
- Red Hat Network Registration Client
- initial description, Red Hat Network Overview
- Red Hat packages
- for UNIX, Download and Install Additional Packages
- installing, Download and Install Additional Packages
- Red Hat Update Agent, Applying Updates
- Command Line Arguments, Command Line Version
- configuration, Configuration
- UNIX Command Line Arguments, Updating From the Command Line
- with a proxy server, General Settings
- Red Hat Update Agent (up2date)
- activation keys, Registering with Activation Keys
- command line options, Command Line Version
- command line version, Command Line Version, Command Line Version
- complete description, Red Hat Update Agent
- configuration tool, Using the Red Hat Update Agent Configuration Tool
- configuring general settings, General Settings
- configuring package exceptions, Package Exceptions Settings
- configuring retrieval and installation, Retrieval/Installation Settings
- excluding packages, Package Exceptions Settings
- graphical options, Starting the Red Hat Update Agent
- initial description, Red Hat Network Overview
- installing GPG keys, Installing the Red Hat GPG key
- log file, Log File
- registering with, Registration
- starting, Starting the Red Hat Update Agent
- synchronizing system profile, Synchronizing Your System Profile
- reference guide
- bug reporting, Send in Your Feedback
- conventions, Introduction to the Guide
- introduction to the, Introduction to the Guide
- registering
- with activation keys, Registering with Activation Keys
- Registration, Red Hat Network Registration Client
- as part of an organization, Registering a User Account
- Configuration, Configuring the Red Hat Network Registration Client
- Email notification, Registering a User Account
- Hardware System Profile, Hardware System Profile
- Password, Registering a User Account
- RPM Package List, Software System Profile
- Software System Profile, Software System Profile
- System Profile, Registering a User Account, Registering a System Profile
- text mode, Text Mode RHN Registration Client
- through the Web, Logging into the RHN Website
- username, Registering a User Account
- with a proxy server, Configuring the Red Hat Network Registration Client
- with activation key, Activation Keys —
- remote commands
- enabling, Enabling Commands
- issuing, Issuing Commands
- RHN Satellite
- Disk Space, RHN Satellite::Disk Space
- Execution Time, RHN Satellite::Execution Time
- Interface Traffic, RHN Satellite::Interface Traffic
- Latency, RHN Satellite::Latency
- Load, RHN Satellite::Load
- Probe Count, RHN Satellite::Probe Count
- probes, RHN Satellite
- Process Counts, RHN Satellite::Process Counts
- Process Health, RHN Satellite::Process Health
- Process Running, RHN Satellite::Process Running
- Processes, RHN Satellite::Processes
- Swap, RHN Satellite::Swap
- Users, RHN Satellite::Users
- RHN Tools channel, Installing the Red Hat Network Monitoring Daemon
- RHN website, Launching the RHN Website
- initial description, Red Hat Network Overview
- rhn-catalog
- troubleshooting with, Examining Probes with rhn-catalog
- rhn-runprobe
- options, Viewing the output of rhn-runprobe
- troubleshooting with, Viewing the output of rhn-runprobe
- rhnmd daemon, Installing the Red Hat Network Monitoring Daemon
- rhnreg_ks , Activation Keys —
- rhnsd , Red Hat Network Daemon
- rhn_register (see Registration)
- complete description, The rhn_register Client
S
- Satellite Administrator, User List ⇒ Active ⇒ User Details ⇒ Details —
- Schedule, Schedule
- Scheduled Actions
- Action Details, Action Details
- Actions List, Actions List
- Archived Actions, Archived Actions
- Completed Actions, Completed Actions
- Failed Actions, Failed Actions
- Pending Actions, Pending Actions
- Scout Config Push , Monitoring
- Secure Sockets Layer, Security, Quality Assurance, and Red Hat Network
- security
- service levels
- Management, Management
- Monitoring, Monitoring
- Provisioning, Provisioning
- Update, Update
- Software
- Channel List
- Channel Details, Software Channel Details
- Package Search, Package Search
- software
- searching, Package Search
- software channels
- details, Software Channel Details ⇒ Details
- SSH, Configuring SSH
- SSH key, Installing the SSH key
- sshd , Configuring SSH
- SSL
- setting up, Configuring the clients
- SSL certificates
- deploying, Deploying Client SSL Certificates
- SSL expiration errors
- connection
- certificate verification, Before You Begin
- system group, System Groups —
- adding and removing, Adding and Removing Systems in Groups
- creating, Creating Groups
- deleting, System Group Details ⇒ Details —
- editing details, System Group Details ⇒ Details —
- list of, System Groups —
- viewing details, System Group Details —
- system group list
- status, System Groups —
- System Groups
- assigning and removing, System Details ⇒ Groups —
- System Group List, System Groups —
- system groups
- joining and leaving, System Details ⇒ Groups —
- system list, Systems
- System Profile, Registering a System Profile
- Custom Information, System Details ⇒ Details ⇒ Custom Info —
- Notes, System Details ⇒ Details ⇒ Notes
- Reactivation, System Details ⇒ Details ⇒ Reactivation —
- Updating hardware profile, System Details ⇒ Details ⇒ Hardware
- Updating package list, Synchronizing Your System Profile, System Details ⇒ Software ⇒ Packages
- Updating Properties, System Details ⇒ Details ⇒ Properties
- System Set Manager, System Set Manager —
- systems
- deleting, System Details ⇒ Details
- entitling, Subscription Management
- overview, Overview —
- searching, Advanced Search —
- viewing a list of, Systems
- viewing details for, System Details
- Systems
- Advanced Search, Advanced Search —
- Entitlements, Subscription Management
- System Details, System Details
- System List, Systems
- Systems Overview, Overview —
- systems list
- status, Systems
- Systems Selected
- explanation of, Systems Selected
T
- Troubleshooting
- Monitoring, Troubleshooting
U
- UNIX variants (see supported)
- Update
- service level, Update
- updating
- via command line, Updating From the Command Line
- via website, Updating Through the Website
- user
- deactivate, User List ⇒ Active ⇒ User Details —
- delete (RHN Satellite only), User List ⇒ Active ⇒ User Details —
- user account, Registering a User Account
- user roles, User List ⇒ Active ⇒ User Details ⇒ Details —
- users, Users —
- changing email address, User List ⇒ Active ⇒ User Details ⇒ Details —
- changing password, User List ⇒ Active ⇒ User Details ⇒ Details —
- roles, User List ⇒ Active ⇒ User Details ⇒ Details —
V
- variables
- macros
- in configuration files, Including Macros in your Configuration Files
W
- WebLogic
- Execute Queue, BEA WebLogic::Execute Queue
- Heap Free, BEA WebLogic::Heap Free
- JDBC Connection Pool, BEA WebLogic::JDBC Connection Pool
- probes, BEA WebLogic 6.x and higher
- Server State, BEA WebLogic::Server State
- Servlet, BEA WebLogic::Servlet
- website, Red Hat Network Website
- activation keys, Activation Keys —
- All Errata, All Errata
- Channel List, Software Channels
- Channels, Channels
- custom system information, Custom System Info —
- Errata, Errata
- Erratum Search, Advanced Search
- Help, Help
- language, Locale Preferences
- locale, Locale Preferences
- logging in, Logging into the RHN Website
- Monitoring, Monitoring —
- navigation bar, Navigation
- overview, Navigation
- Overview, Overview
- Relevant Errata, Relevant Errata
- Schedule, Schedule
- Software Channel Details, Software Channel Details
- Software Search, Package Search
- stored profiles, Stored Profiles —
- System Details, System Details
- System Entitlements, Subscription Management
- System Group List, System Groups —
- System Groups, System Groups —
- System List, Systems
- System Search, Advanced Search —
- Systems, Systems
- Systems Overview, Overview —
- Users, Users —
- Your Account, Your Account