Reference Guide
Red Hat Network
Red Hat Inc.
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 Server, or fed through an RHN Proxy Server
- Red Hat Network Daemon
- the Red Hat Network Registration Client - for systems running Red Hat Enterprise Linux 2.1 only.
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 2, 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 3, Red Hat Network Daemon for further information). This daemon is necessary in order to schedule updates or other actions through the website.
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 Server 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 Server 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. Red Hat Update Agent
Warning
Important
up2date up2date
. If you do not have the latest version installed, this command updates it.
2.1. Starting the Red Hat Update Agent
- On the GNOME and KDE desktops, go to Applications (the main menu on the panel) => System Tools => Red Hat Network.
- At a shell prompt (for example, an xterm or gnome-terminal), type the command
up2date
.
- On the GNOME desktop, go to the Main Menu Button (on the Panel) => Programs => System => Update Agent.
- On the KDE desktop, go to the Main Menu Button (on the Panel) => Update Agent.
- At a shell prompt (for example, an xterm or gnome-terminal), type the command
up2date
.
up2date --help
.
up2date --tmpdir=/tmp/up2date/
Table 2.1. Graphical Update Agent Options
Option | Description |
---|---|
--configure | Configure Red Hat Update Agent options. Refer to Section 2.4, “Configuration” for detailed instructions. |
-d , --download | Download packages only; do not install them. This argument temporarily overrides the configuration option Do not install packages after retrieval. Use this option if you prefer to install the packages manually. |
-f , --force | Force package installation. This option temporarily overrides the file, package, and configuration skip lists. |
-i , --install | Install packages after they are downloaded. This argument temporarily overrides the configuration option Do not install packages after retrieval. |
-k , --packagedir | Specify a colon separated path of directories 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 2.1. Configure Proxy Server
Figure 2.2. Install GPG Key
2.2. Registration
up2date --register
Important
Figure 2.3. Welcome Screen
2.2.1. Registering a User Account
up2date
).
Important
Figure 2.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 2.5. Create a User Account
2.2.2. Activate
package rhn_register is not installed
Red Hat Enterprise Linux version- Hostname
- IP address
- CPU model
- CPU speed
- Amount of RAM
- PCI devices
- Disk sizes
- Mount points
Note
Figure 2.6. Activate
Figure 2.7. Sending System Profile to Red Hat Network
2.2.3. Channels
Figure 2.8. Channels
Figure 2.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.
2.2.4. Packages Flagged to be Skipped
Figure 2.10. Packages Flagged to be Skipped
2.2.5. Available Package Updates
Figure 2.11. Available Package Updates
Figure 2.12. Example Errata Advisory
2.2.6. Retrieving Packages
/var/spool/up2date/
.
Figure 2.13. Retrieving Packages
2.2.7. Installing Packages
Figure 2.14. Installing Packages
Figure 2.15. All Finished
2.3. Command Line Version
up2date --nox
up2date -u
Table 2.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 2.4, “Configuration” for detailed instructions. |
-d , --download | Download packages only; do not install them. This argument temporarily overrides the configuration option Do not install packages after retrieval. Use this option if you prefer to install the packages manually. |
--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 2.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.
2.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-----
2.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.
2.3.3. Synchronizing Your System Profile
up2date -p
2.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.
2.4. Configuration
2.4.1. Using the Red Hat Update Agent Configuration Tool
up2date --config
at a shell prompt (for example, an xterm or a gnome-terminal).
2.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 2.16. General Settings
2.4.1.2. Retrieval/Installation Settings
Warning
Figure 2.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/
2.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 2.18. Package Exceptions Settings
2.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.
2.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 6.6, “Channels” for more information.
- Keys may be modified by any user with the role of Activation Key Administrator or Organization Administrator (or both). These permissions are set through the Users tab of the RHN website. Refer to Section 6.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.
Chapter 3. Red Hat Network Daemon
rhnsd
) periodically connects to Red Hat Network 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
.
Note
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.
3.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
3.2. Viewing Status
service rhnsd status
or /etc/rc.d/init.d/rhnsd status
at a shell prompt.
3.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
.
3.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 4. Red Hat Network Alert Notification Tool
rhn-applet
RPM package and use the X Window System.
Figure 4.1. GNOME Panel with Red Hat Network Alert Notification Tool
- In Red Hat Enterprise Linux 3 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.
4.1. Configuring the Applet
Figure 4.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
4.2. Notification Icons
Table 4.1. Red Hat Network Alert Notification Tool Icons
Icon | Description |
---|---|
Updates are available | |
System is up-to-date | |
Checking for updates | |
Error has occurred |
4.3. Viewing Updates
Figure 4.3. Available Updates
4.4. Applying Updates
4.5. Launching the RHN Website
Chapter 5. Red Hat Network Registration Client
Warning
5.1. Configuring the Red Hat Network Registration Client
rhn_register --configure
Figure 5.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.
5.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 5.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 5.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 5.3. Warning: This System Already Registered
Figure 5.4. Welcome Screen
Figure 5.5. Red Hat Privacy Statement
5.3. Registering a User Account
Figure 5.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 5.7. Create a Unique Username and Password
5.4. Registering a System Profile
5.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 5.8. System Profile - Hardware
5.4.2. Software System Profile
5.4.2.1. Gathering RPM Database Information
Figure 5.9. Registration Wizard
Figure 5.10. RPM Package Information
5.4.2.2. Choosing RPM Packages to Exclude from the System Profile
Figure 5.11. Choose which RPM Packages to Exclude from System Profile
5.5. Finishing Registration
Figure 5.12. Finished Collecting Information for System Profile
Figure 5.13. Send System Profile to Red Hat Network
Figure 5.14. Registration Finished
5.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
5.7. Text Mode RHN Registration Client
rhn_register --nox
Figure 5.15. Text Mode Welcome Screen
5.8. Red Hat Enterprise Linux 5 rhn_register
Client
rhn_register
. The new version of this application works with the yum-based RHN client that will replace up2date
. The rhn_register
application included as part of Red Hat Enterprise Linux 4 and earlier will continue to operate as expected.
rhn_register
application runs as part of the firstboot process. The first time a newly-installed Red Hat Enterprise Linux 5 system is booted, an application that performs the initial configuration of your system uses rhn_register
to register your system with RHN.
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 yum-based client then 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 in this way. Doing so may create a duplicate system profile in RHN. Consider using rhnreg_ks
and activation keys to re-register a system without creating a duplicate entry.
Figure 5.16. Verify Re-Registration
Figure 5.17. Registering for Software Updates
This first page describes the purpose of the application. To learn more about the benefits of RHN, press the Why Should I Connect to RHN? button. Otherwise, press the Forward button to continue.Figure 5.18. Choose an Update Location
This page allows you to select the source of your software updates - either from RHN's Hosted environment or from an RHN Satellite Server or RHN Proxy Server. If your organization has a Satellite or Proxy, select the second radio button and enter the URL of your Satellite or Proxy into the Red Hat Network Location field.If you connect to the internet through an HTTP Proxy, press the Advanced Network Configuration button. In the next window, use the appropriate fields for your HTTP proxy; if your proxy requires authentication, enter the username and password here. When finished, press the Close button to continue. You are returned to the Choose an Update Location page. Press Forward to continue.Figure 5.19. Enter Your Account Information
This page requires you to enter your account information, if you already have an RHN account, or to create a new account if you do not. To create a new RHN account, press the Create a New Account button. Fill in the fields that are marked with an asterisk and any other information you wish to enter. Press the Create New Login button to create your new login.Note
If you are registering to RHN Hosted as part of an organization, please do not create a new account through this screen. Contact your Organization Administrator and request that they create an account for you, then provide that information in the Enter Your Account Information page. Otherwise, you may not be correctly associated with your organization or its resources.Figure 5.20. Create Your System Profile
This page allows you to select a profile name for the system you are registering. The default name for any system is that system's hostname, although you may change it as you like. You can also select whether to report hardware and package information to RHN. It is recommended that you choose to report this information; doing so allows RHN to automatically subscribe your system to the base and child channels most appropriate to your system. If you wish, you may press either the View Hardware Profile or View Package Profile button to view the information thatrhn_register
uploads to RHN in this step.Note
This automatic registration does not automatically subscribe your system to optional child channels, such as the RHN Tools channel. If you wish to register a system and have them automatically subscribed to a set of channels of your choice, consider using a kickstart profile orrhnreg_ks
and activation keys to do so.Figure 5.21. Review System Subscription Details
This page displays the base and child channel information to which your system has been subscribed. Take a moment to review the channels, and then press Forward to continue.Figure 5.22. Finish Setting Up Software Updates
This page indicates that you have successfully registered a Red Hat Enterprise Linux 5 system with RHN. From this point, you do not have to do anything to receive software updates. A package icon will appear in the upper right corner of your desktop when updates are available. Click on this icon to apply available updates. Click Finish to exit the wizard.If you do not have any entitlements available for this system, this final page indicates that the registration has failed. This does not mean that the system profile has not been stored with RHN, only that you will not receive automatic updates without manual intervention. You can always login to the RHN web interface and either purchase additional entitlements or shift an entitlement from another system in order to entitle this one. Click the Exit software update setup button to exit the wizard.
Chapter 6. Red Hat Network Website
6.1. Navigation
Figure 6.1. Top Navigation bar — RHN Satellite Server
Figure 6.2. Top Navigation bar — RHN's Hosted Environment
Figure 6.3. Left Navigation Bar — Users
Figure 6.4. Sub-Tabs — System Details
6.1.1. Entitlement Views
Table 6.1. Entitlement Icons
Icon | Entitlement |
---|---|
Management or higher | |
Provisioning | |
Monitoring |
6.1.2. Categories and Pages
- Your RHN — View and manage your primary account information and obtain help.
- Your RHN — 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.
- Purchase History — View a history of your entitlements, including the expiration date and the number available.
- Help — Learn how to use Red Hat Network and receive support if needed.
- Systems — Manage your 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 Out of Date, Unentitled, Ungrouped, and Inactive.
- System Groups — — List your system groups. Create additional groups.
- System Set Manager — — Perform actions on currently selected systems.
- System Entitlements — Change the entitlement levels of systems.
- 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.
- 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.
- Channel Entitlements — View a list of software channels for which you have paid, as well as the systems associated with each.
- Download Software — Access priority downloading of Red Hat ISO images. ISO images are used to write to CD.
- Package Search — Search packages using all or some portion of the package name.
- Manage Config Channels — — Create and edit channels used to deploy configuration files.
- Configuration — Manage configuration files globally and for each individual system with a Provisioning entitlement.
- Overview — Provides status information for your configuration files and actions, as well as quick links to the most common configuration management tasks.
- Configuration Channels — Provides status information about your centrally-managed (or global) configuration channels, including the number of files they contain.
- Configuration Files — Provides status information about your global and local configuration files on two sub-tabs.
- Systems — Provides configuration management information about your systems, including which systems have enabled configuration management and which systems are not prepared for configuration management.
- Quota — Provides information about the used and remaining storage quota for your 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.
- Probe Status — — View probes by state.
- Notification — — View contact methods established for your organization.
- Scout Config Push — — Reconfigure your monitoring infrastructure.
- Global Config — — Change organization-wide monitoring settings.
6.1.3. Errata Alert Icons
6.1.4. Quick Search
6.1.5. Systems Selected
6.1.6. Lists
6.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 6.5. RHN Website
Note
Note
6.3. Your RHN
Note
Figure 6.6. Your Red Hat Network
- 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 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 section below 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. Any action that is less than thirty days old is considered to be 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 following 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 final section lists your System Groups 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.
6.3.1. Your Account
6.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.
- "Your RHN" Start Page — select the information areas that are displayed on the Your RHN Start Page. Check the box to the left of the information area you would like to include.
6.3.3. Locale Preferences
6.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
6.3.4.1. System Entitlements
6.3.4.2. Virtualization Entitlements
6.3.4.3. Software Channel Entitlements
6.3.4.4. Purchase or Renew
6.4. Systems
6.4.1. Overview —
Figure 6.7. Systems Overview
6.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 6.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 sub-tab 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 4), 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 6.4.2.9, “System Details” or Section 2.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 6.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 6.6.1, “Software Channels” for more information.
- Entitlement — Whether or not the system is entitled and at what service level.
6.4.2.1. All
6.4.2.2. Virtual Systems
Note
6.4.2.3. Out of Date
6.4.2.4. Unentitled —
6.4.2.5. Ungrouped
6.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 3, 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 Server 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.
6.4.2.7. Satellite
6.4.2.8. Proxy
6.4.2.9. System Details
Note
- Details
- Software
- Configuration
- Provisioning —
- Monitoring —
- Groups
- Events
6.4.2.9.1. System Details ⇒ Details
6.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. - Hostname
- The hostname as defined by the client system. This information is often found in
/etc/hostname
for Red Hat Enterprise Linux systems. - Virtualization
- If the system is a virtual guest, the type of virtualization used to create the guest is displayed here.
- UUID
- If the system is a virtual guest, the UUID of the guest system is displayed here.
- IP Address
- The IP address of the client.
- Kernel
- The kernel that is installed and operating on the client system.
- RHN 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. - 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 sub-tab.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 6.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 6.4.4.11.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 Server 5.0.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
- Checked In
- The date and time at which the system last checked in with RHN.
- Registered
- The date and time at which the system registered with RHN and created this profile.
- 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.
- Entitlements
- A list of the base and add-on entitlements applied to this system. Virtual hosts should have the Virtualization or Virtualization Platform entitlement; guest systems should not.
Note
Base and add-on entitlements are inherited by guest systems from the host system. If you change the entitlements of the host, those of the guest change accordingly. - 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.
- System 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.
- 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.
Important
- The system is subscribed to the RHEL Virtualization (v.5) child channel that is appropriate to that system's architecture.
- The system is subscribed to the Red Hat Network Tools for RHEL Server (v.5) child channel that is appropriate to that system's architecture.
- A package install is scheduled for the
rhn-virtualization-host
package. The installation takes place the next time the system checks in with RHN.
6.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 or Provisioning 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 sin the Your Preferences page of the Your RHN 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
6.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
6.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 2.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.
Warning
rhnreg_ks
) while a profile-based kickstart is in progress. If you do, the kickstart will fail.
6.4.2.9.1.5. System Details ⇒ Details ⇒ Hardware
6.4.2.9.1.6. System Details ⇒ Details ⇒ Notes
6.4.2.9.1.7. System Details ⇒ Details ⇒ Custom Info —
6.4.2.9.1.8. System Details ⇒ Details ⇒ Proxy
6.4.2.9.1.9. System Details ⇒ Details ⇒ Satellite
6.4.2.9.2. System Details ⇒ Software
6.4.2.9.2.1. System Details ⇒ Software ⇒ Errata
6.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 sub-tab 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.
6.4.2.9.2.3. System Details ⇒ Software ⇒ Software Channels
Note
- Subscribing a guest to a layered product channel, such as Red Hat Directory Server, consumes a channel entitlement.
- If a guest is the fifth or later guest on a host that has a Virtualization entitlement, channel subscriptions are not consumed - however, it is important to note that this violates your organization's Service Level Agreement.
6.4.2.9.3. System Details ⇒ Configuration —
6.4.2.9.3.1. System Details ⇒ Configuration ⇒ Overview
- Configuration Overview
- This panel provides information about the numbers and types of configuration files that apply to this system. For centrally-managed files, the total number of central files and the number of files that are not overridden by local files are listed. The number of central (global) channels to which the system is subscribed is also displayed.
- Recent Events
- Recently scheduled configuration events appear here, along with their status. You can see the results of recent file comparisons by clicking the blue [View Details] link.
- Configuration Actions
- Any configuration actions scheduled from this page apply to this system only.
- Deploy Files
- Selecting one of the Deploy Files links allows you to deploy any of the configuration files to which this system has access. In each case, RHN allows you to select the time at which the deployment occurs. (Note that the deployed files will always be the latest revisions.) Press the Schedule Deploy button to confirm the action.
- Compare Files
- The Compare Files actions issue a
diff
command between the files stored with RHN and those on the system in question. As with deployed files, the files that are compared are the latests revisions only. Select the time at which the comparison should take place, then press the Schedule Compare button to confirm the action. - Add/Create Files
- The Add/Create Files actions allow you to place files in the Sandbox channel for this system by either uploading a file, importing a file from another channel, or creating a file from scratch. A configuration file that is in a system's Sandbox channel is considered to be experimental or potentially unstable. Without intervention, a Sandbox file cannot be deployed to any system. This is to prevent accidental deployment of the file.
Note
If you wish to deploy and test a Sandbox file, you must first copy it to another channel. You can copy the file to the local (override) channel by selecting the Copy Latest to System Config Channel button, or to a central configuration channel using the Copy Latest to Central Config Channell button. Select the channels into which you want to import it, then selectg the Copy To Central Channel button.The file is not deleted from the Sandbox when you copy it to another channel. When you copy a configuration file to other channels, you store multiple copies of the file. You can delete Sandbox files by selecting the box next to the file and then pressing the Delete Files button. This action only deletes the file from the Sandbox, not from any other channels.
6.4.2.9.3.2. System Details ⇒ Configuration ⇒ View/Modify Files
- Centrally-Managed Files
- From this page, you can examine the centrally-managed configuration files that apply to this system. If the are overridden by a local file, the Overridden By column displays the revision number of the local file that overrides it. This makes it easy to see if the local file is an older version of a configuration file, or if perhaps it has custom options.You can choose to view the contents of each file, compare it to the file that exists on the system ,or view the contents of the channel form which if comes. You can also import a copy of the centrally-managed file to the local override channel or to the local Sandbox by selecting the file and pressing the appropriate button in the lower right.
- Locally-Managed Files
- This list is similar in layout to the Central and Local tables described above. You can copy files from the Sandbox to the Local Override channel or to a Centrally-Managed configuration channel by pressing the appropriate button in the lower right.
- Local Sandbox
- If this configuration file overrides another, the overridden file is listed in this column along with its host channel.
6.4.2.9.3.3. System Details ⇒ Configuration ⇒ Add Files
- 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 the system by entering the absolute path to any desired files in the Import New Files text box. You can also import files from other configuration channels. Check the box to the left of any file you wish to import and press the Import Configuration File(s) button.
- 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.
6.4.2.9.3.4. System Details ⇒ Configuration ⇒ Deploy Files
Note
6.4.2.9.3.5. System Details ⇒ Configuration ⇒ Compare Files
6.4.2.9.3.6. System Details ⇒ Configuration ⇒ Manage Configuration Channels
- List/Unsubscribe from Channels
- This page displays the various centrally-managed configuration channels to which the system is subscribed. You can choose to unsubscribe from any listed channels by selecting the box to the left of the channel and pressing the Unsubscribe button.
- Subscribe to Channels
- This page displays all centrally-managed configuration channels. Those channels to which the system is subscribed are marked with a check. You can subscribe the system to additional channels by checking the box to the left of them and pressing the Continue button.
- View/Modify Rankings
- It is possible for different global configuration channels to contain different versions of the same file. If a system is subscribed to two or more such channels, it is necessary to know which of the files will be deployed to the system. This is accomplished through ranking. On this page, you can select which of the centrally-managed configuration channels has the highest precedence. (Remember, however, that local overrides always take the very highest priority.) On this page, the various channels to which the system is subscribed are displayed. The channel that is highest on the list has the highest priority; a file contained in this channel will be deployed rather than a similar file in any other global channel. To re-order the channels, highlight the name of the channel you wish to move, then use the up and down arrows to reposition it. When finished, press the Update button to make the changes permanent.
6.4.2.9.4. System Details ⇒ Provisioning —
6.4.2.9.4.1. System Details ⇒ Provisioning ⇒ Kickstart —
- Schedule
- This sub-tab allows you to schedule the selected system for kickstart. Choose from the list of available kickstart profiles, select a time for the kickstart to begin, and click the Schedule Kickstart and Finish button to begin the kickstart. You may first alter kickstart settings by clicking the Advanced Configuration button.
Note
You must first create a kickstart profile before it appears on this sub-tab. If you have not created any profiles, refer to Section 6.4.9.3, “Create a New Kickstart Profile” before scheduling a kickstart for a system. - Session Status
- If you have scheduled a kickstart, this sub-tab shows the progress of the kickstart. The provided details include the kickstart profile used, its state, the next action and the number of requested packages. Kickstarts that do not complete within approximately two hours are marked Kickstart Failed. The page refreshes itself periodically, or you can force a refresh using your browser's controls.
6.4.2.9.4.2. System Details ⇒ Provisioning ⇒ Snapshots —
- group memberships
- channel subscriptions
- installed packages
- configuration channel subscriptions
- configuration files
- snapshot tags
6.4.2.9.4.3. System Details ⇒ Provisioning ⇒ Snapshot Tags —
6.4.2.9.5. System Details ⇒ Monitoring —
6.4.2.9.6. System Details ⇒ Groups —
6.4.2.9.6.1. System Details ⇒ Groups ⇒ List/Leave —
6.4.2.9.6.2. System Details ⇒ Groups ⇒ Join —
6.4.2.9.7. System Details ⇒ Events
6.4.2.9.7.1. System Details ⇒ Events ⇒ Pending
- — Package Event
- — Errata Event
- — Preferences Event
- — System Event
6.4.2.9.7.2. System Details ⇒ Events ⇒ History
6.4.3. System Groups —
- Create system groups. (Refer to Section 6.4.3.1, “Creating Groups”.)
- Add systems to system groups. (Refer to Section 6.4.3.2, “Adding and Removing Systems in Groups”.)
- Remove systems from system groups. (Refer to Section 6.4.2.9, “System Details”.)
- Assign system group permissions to users. (Refer to Section 6.9, “Users — ”.)
Figure 6.8. System Group List
- 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 6.4.4, “System Set Manager — ” for details.
- Status — 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 6.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 6.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 6.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 6.4.4, “System Set Manager — ” for more information.
6.4.3.1. Creating Groups
6.4.3.2. Adding and Removing Systems in Groups
6.4.3.3. System Group Details —
6.4.3.3.1. System Group Details ⇒ Details —
6.4.3.3.2. System Group Details ⇒ Systems —
6.4.3.3.3. System Group Details ⇒ Target Systems —
6.4.3.3.4. System Group Details ⇒ Errata —
6.4.3.3.5. System Group Details ⇒ Admins —
6.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.
6.4.4.1. System Set Manager ⇒ Overview —
6.4.4.2. System Set Manager ⇒ Systems —
6.4.4.3. System Set Manager ⇒ Errata —
6.4.4.4. System Set Manager ⇒ Packages —
6.4.4.4.1. System Set Manager ⇒ Packages ⇒ Upgrade —
6.4.4.4.2. System Set Manager ⇒ Packages ⇒ Install —
6.4.4.4.3. System Set Manager ⇒ Packages ⇒ Remove —
6.4.4.5. System Set Manager ⇒ Patches
6.4.4.6. System Set Manager ⇒ Patch Clusters
6.4.4.7. System Set Manager ⇒ Groups —
6.4.4.8. System Set Manager ⇒ Channels —
6.4.4.8.1. System Set Manager ⇒ Channels ⇒ Channel Subscriptions —
6.4.4.8.2. System Set Manager ⇒ Channels ⇒ Config Channels —
6.4.4.9. System Set Manager ⇒ Channels ⇒ Config Channels —
6.4.4.9.1. System Set Manager ⇒ Channels ⇒ Config Channels ⇒ Deploy —
6.4.4.9.2. System Set Manager ⇒ Channels ⇒ Config Channels ⇒ Compare Files —
6.4.4.9.3. System Set Manager ⇒ Channels ⇒ Config Channels ⇒ Subscribe to Channels —
Note
6.4.4.9.4. System Set Manager ⇒ Channels ⇒ Config Channels ⇒ Unsubscribe from Channels —
6.4.4.9.5. System Set Manager ⇒ Channels ⇒ Config Channels ⇒ Enable Configuration —
- First, select the checkbox to the left of the systems you wish to enable. Indicate the time at which you would like necessary files to be deployed, and press the Enable RHN Configuration Management button.
- RHN subscribes the systems to the proper channels in order to deploy the
rhncfg-*
packages, then schedules the deployment of these files according to the time you selected. - If you wish to install these files immediately, run the
rhn_check
command on the selected systems. Otherwise, the deployment will not occur until they next check in with RHN. - Once the
rhncfg-*
packages have been successfully deployed, run therhn-actions-control --enable-all
command as root on each system.
6.4.4.10. System Set Manager ⇒ Provisioning —
6.4.4.10.1. System Set Manager ⇒ Provisioning ⇒ Kickstart —
6.4.4.10.2. System Set Manager ⇒ Provisioning ⇒ Tag Systems —
6.4.4.10.3. System Set Manager ⇒ Provisioning ⇒ Rollback —
6.4.4.10.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 sub-tab of the Channels tab for instructions. You may then identify a specific user, group, timeout period, and the script on this page. Select a date and time to perform the command, and click Schedule Remote Command.
6.4.4.11. System Set Manager ⇒ Misc —
6.4.4.11.1. System Set Manager ⇒ Misc ⇒ System Profile Updates —
6.4.4.11.2. System Set Manager ⇒ Misc ⇒ Custom System Information —
6.4.4.11.3. System Set Manager ⇒ Misc ⇒ Reboot Systems —
6.4.4.11.4. System Set Manager ⇒ Misc ⇒ Lock Systems —
6.4.4.11.5. System Set Manager ⇒ Misc ⇒ Delete Systems —
6.4.4.11.6. System Set Manager ⇒ Misc ⇒ Add or Remove Add-On Entitlements —
6.4.4.11.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 6.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.
6.4.5. Advanced Search —
6.4.6. Activation Keys —
rhnreg_ks
. Refer to Section 2.5, “Registering with Activation Keys” for instructions on use.
Note
6.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-left corner.
Warning
In addition to the fields listed below, RHN Satellite Server 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 6.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.
- Entitlement — The service level for the key, either Management or Provisioning. All systems will be subscribed at this level with the key.
- Universal default — Whether or not this key should be considered the primary activation key for your organization.
Click Create Key.
6.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 2.5, “Registering with Activation Keys” and Section 6.4.9.3, “Create a New Kickstart Profile”, respectively, for instructions.
6.4.7. Stored Profiles —
6.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.
6.4.9. Kickstart —
Important
/var/www/html/pub/
on the Proxy. RHN Satellite Servers 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 6.4.9.6, “Kickstart ⇒ Distributions —
” for instructions on setting up installation trees.
Figure 6.9. Kickstart Overview
6.4.9.1. Introduction to Kickstart
6.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.
6.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.
6.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.
6.4.9.1.4. Integrating Kickstart with PXE
Note
6.4.9.2. View a List of Kickstart Profiles
Figure 6.10. Kickstart Profiles
6.4.9.3. Create a New Kickstart Profile
- On the first page, enter a kickstart profile label and 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.
- 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/.
6.4.9.3.1. Kickstart Details ⇒ Details —
Figure 6.11. Kickstart Details
- Rename the profile
- Change the operating system it installs by clicking (Change)
- Deactivate the profile so that it cannot be used to schedule a kickstart by removing the Active checkmark
- Select whether this profile is the default for all of your organization's kickstarts by checking or unchecking the box.
- Enter comments that are useful to you in distinguishing this profile from others
6.4.9.3.2. Kickstart Details ⇒ Operating System —
- Change the base channel
- Select from the available base channels, such as Red Hat Enterprise Linux AS version 4. Satellite customers see a list of all base channels that are currently synced to their Satellite.
- 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.
6.4.9.3.3. Kickstart Details ⇒ Advanced Options —
6.4.9.3.4. Kickstart Details ⇒ Bare Metal Kickstart —
Important
ks=https://your-proxy.example.com/ks/org/410672xa19ccBf33f628fd2d94465Beae5aB656/mode/ip_range
6.4.9.3.5. System Details ⇒ Details —
Figure 6.12. 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
6.4.9.3.6. System Details ⇒ Locale —
6.4.9.3.7. 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
6.4.9.3.8. System Details ⇒ File Preservation —
6.4.9.3.9. System Details ⇒ GPG and SSL —
Note
6.4.9.3.10. 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.
6.4.9.3.11. Software ⇒ Package Groups —
Figure 6.13. 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
.
6.4.9.3.12. Software ⇒ Package Profiles —
6.4.9.3.13. Activation Keys —
Figure 6.14. Activation Keys
6.4.9.3.14. Scripts —
Figure 6.15. 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 LinuxSystem Admin 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
6.4.9.3.15. Kickstart File —
Figure 6.16. Kickstart File
6.4.9.4. Kickstart ⇒ Bare Metal —
6.4.9.5. Kickstart ⇒ GPG and SSL Keys —
Important
6.4.9.6. Kickstart ⇒ Distributions —
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-4
. In the External Location field, paste the 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 AS (v.4 for x86)
and Red Hat Enterprise Linux 4
, respectively. When finished, click the Create button.
6.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.
6.5. Errata
Note
- — Security Updates available, update strongly recommended
- — Bug Fix Updates available and recommended
- — Enhancement Updates available
6.5.1. Relevant Errata
Figure 6.17. Errata List
6.5.2. All Errata
6.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 6.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.
6.5.2.2. Errata Details
6.5.2.2.1. Errata Details ⇒ Details
6.5.2.2.2. Errata Details ⇒ Packages
6.5.2.2.3. Errata Details ⇒ Affected Systems
6.6. Channels
6.6.1. Software Channels
6.6.1.1. Relevant Channels
Figure 6.18. Relevant Channels
6.6.1.2. Retired Channels
6.6.1.3. All Channels
6.6.1.4. Software Channel Details
6.6.1.4.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
6.6.1.4.2. Software Channel Details ⇒ Subscribers —
6.6.1.4.3. Software Channel Details ⇒ Managers —
6.6.1.4.4. Software Channel Details ⇒ Errata
6.6.1.4.5. Software Channel Details ⇒ Packages
ks
in the filter might return: ksconfig
, krb5-workstation
, and links
. The filter is case-insensitive.
6.6.1.4.6. Software Channel Details ⇒ Subscribed Systems
6.6.1.4.7. Software Channel Details ⇒ Target Systems
6.6.1.4.8. Software Channel Details ⇒ Downloads
6.6.1.4.9. Software Channel Details ⇒ License
6.6.2. Channel Entitlements
6.6.3. Download Software
6.6.3.1. Relevant ISOs
6.6.3.2. All ISOs
6.6.4. Package Search
6.6.5. Manage Software Channels
6.6.5.1. Manage Software Channels ⇒ Channel Details
6.6.5.1.1. Manage Software Channels ⇒ Channel Details ⇒ Channel Details
6.6.5.1.2. Manage Software Channels ⇒ Channel Details ⇒ Managers
6.6.5.1.3. Manage Software Channels ⇒ Channel Details ⇒ Errata
6.6.5.1.4. Manage Software Channels ⇒ Channel Details ⇒ Packages
6.6.5.2. Manage Software Channels ⇒ Manage Software Packages
6.7. Configuration
6.7.1. 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.
6.7.2. 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 6.7.2.1, “Configuration ⇒ Configuration Channels ⇒ Configuration Channel Details”.
6.7.2.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 then press one of the buttons 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.
6.7.3. Configuration Files
6.7.3.1. Centrally-Managed Files
6.7.4. Locally-Managed Files
6.7.5. Systems
6.7.5.1. Managed Systems
6.7.5.2. Target Systems
Note
6.7.6. Quota for File Storage
6.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
6.8.1. Pending Actions
Figure 6.19. Schedule - Pending Actions
6.8.2. Failed Actions
6.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 6.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.
6.8.5.1. Action Details
6.8.5.1.1. Action Details ⇒ Details
6.8.5.1.2. Action Details ⇒ Completed Systems
6.8.5.1.3. Action Details ⇒ In Progress Systems
6.8.5.1.4. Action Details ⇒ Failed Systems
6.9. Users —
6.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 6.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 6.20. User List
6.9.1.1. User List ⇒ Active ⇒ User Details —
6.9.1.1.1. User List ⇒ Active ⇒ User Details ⇒ Details —
- 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 Server or RHN Proxy Server. This person may change the base channels of systems, make channels globally subscribable, and create entirely new channels.
- Configuration Administrator — This role enables the user to manage the configuration of systems in the organization using either the RHN website 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 Server version 3.6 or later.
- Organization 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 Organization Administrators may exist.
- System Group Administrator — This role is one step below Organization 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.
6.9.1.1.2. User List ⇒ Active ⇒ User Details ⇒ System Groups —
6.9.1.1.3. User List ⇒ Active ⇒ User Details ⇒ Systems —
6.9.1.1.4. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions —
6.9.1.1.4.1. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions ⇒ Subscription —
6.9.1.1.4.2. User List ⇒ Active ⇒ User Details ⇒ Channel Permissions ⇒ Management —
6.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.
6.9.2. User List ⇒ Deactivated —
6.9.3. User List ⇒ All —
6.10. Monitoring —
6.10.1. Probe Status —
Figure 6.21. 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
6.10.1.1. Probe Status ⇒ Critical —
6.10.1.3. Probe Status ⇒ Unknown —
6.10.1.4. Probe Status ⇒ Pending —
6.10.1.5. Probe Status ⇒ OK —
6.10.1.6. Probe Status ⇒ All —
6.10.1.7. Current State —
NO DATA SELECTED TIME PERIOD AND METRIC
.
6.10.2. Notification —
6.10.2.1. Notification ⇒ Filters
6.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.
6.10.2.1.2. Notification ⇒ Notification Filters ⇒ Expired Filters
6.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 6.4.2.9.5, “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 Server and each client system to which the Probe Suite is applied must have therhnmd
daemon installed and running. Refer to the RHN Satellite Server 5.0.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.
6.10.4. Scout Config Push —
6.10.5. General Config —
6.11. Satellite Tools
Figure 6.22. Satellite Tools
6.11.1. Satellite Tools ⇒ Satellite Configuration
6.11.1.1. Satellite Tools ⇒ Satellite Configuration ⇒ General
6.11.1.2. Satellite Tools ⇒ Satellite Configuration ⇒ Monitoring
6.11.1.3. Satellite Tools ⇒ Satellite Configuration ⇒ Certificate
6.11.1.4. Satellite Tools ⇒ Satellite Configuration ⇒ Bootstrap
/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.
6.11.1.5. Satellite Tools ⇒ Satellite Configuration ⇒ Restart
6.11.2. Satellite Tools ⇒ Satellite Configuration ⇒ String Manager
6.12. Help
6.12.1. Help Desk
6.12.2. Quick Start Guide
6.12.3. FAQ
6.12.4. Migration FAQ
6.12.5. Reference Guide
6.12.6. Best Practices Guide
6.12.7. Contact RHN
6.12.8. Satellite Installation Guide
6.12.9. Proxy Guide
6.12.10. Client Configuration Guide
6.12.11. Channel Management Guide
6.12.12. Terms &Conditions
6.12.13. Outage Policy
6.12.14. Release Notes
6.12.15. Get RHN Software
Chapter 7. Monitoring
7.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 Server with Monitoring — Monitoring systems must be connected to a Satellite with a base operating system of Red Hat Enterprise Linux AS 3 Update 5, Red Hat Enterprise Linux AS 4, or later. Refer to the RHN Satellite Server Installation Guide within Help for installation instructions. Contact a Red Hat sales representative to purchase Satellite.
- Monitoring Administrator — This role must be granted to users installing probes, creating notification methods, or altering the monitoring infrastructure in any way. (Remember, the Organization 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 7.2, “Red Hat Network Monitoring Daemon (rhnmd
)” for installation instructions and a quick list of probes requiring this secure connection. Refer to Appendix C, Probes for the complete list of available probes.
7.2. Red Hat Network Monitoring Daemon (rhnmd
)
rhnmd
enables the RHN Satellite Server to communicate securely with the client system to access internal processes and retrieve probe status.
sshd
instead. Refer to Section 7.2.3, “Configuring SSH” for details.
7.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
7.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 7.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 sub-tab 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 7.2.4, “Installing the SSH key”.
- Start the Red Hat Network Monitoring Daemonon 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.
7.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 7.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.
7.2.4. Installing the SSH key
rhnmd
or sshd
, you must install the Red Hat Network Monitoring Daemonpublic 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/opt/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.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.
7.3. mysql-server
package
mysql-server
package on the RHN Satellite Server. Refer to Appendix C, Probes for a listing of all available probes.
mysql-server
package either through the RHN website or via up2date
.
mysql-server
package to be installed and run successfully. Once finished, your Satellite may be used to schedule MySQL probes.
7.4. Notifications
7.4.1. Creating Notification Methods
- Log into the RHN website as either an Organization 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 pulldown menu. Notification methods assigned to probes cannot be deleted until they are dis-associated from the probe.
7.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
7.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.
7.4.4. Filtering Notifications
7.4.5. Deleting Notification Methods
- Log into the RHN website as an Organization 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.
7.5. Probes
7.5.1. Managing Probes
- Log into the RHN website as either an Organization 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 C, Probes for the complete list of probes by command group. Remember that some probes require the Red Hat Network Monitoring Daemonto 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 pulldown 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 7.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 7.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 alloted 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 7.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.
7.5.2. Establishing Thresholds
7.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 7.5.1, “Managing Probes” for instructions.
Note
7.6. Troubleshooting
nocpulse
user on the RHN Server conducting the monitoring.
nocpulse
user with the following command:
su - nocpulse
7.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-rhnprobe
to examine the probe's output. Refer to Section 7.6.2, “Viewing the output of rhn-runprobe
” for instructions.
7.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 7.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 8. UNIX Support Guide
8.1. Introduction
8.1.1. Supported UNIX Variants
- Solaris 8, 9, 10 (sparc)
- Solaris 9, 10 (x86)
8.1.2. Prerequisites
- RHN Satellite Server 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 Server. Refer to Section 8.2.2.1, “Download and Install Additional Packages” for the complete list.
8.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
8.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 8.3.2.3, “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 MOM 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.
8.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
8.2. Preparation
8.2.1. 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 8.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 8.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 Organization 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.
8.2.2. 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 Server.
8.2.2.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 8.3, “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.
8.2.2.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
8.2.2.1.2. Configure the Library Search Path
# crle -c /var/ld/ld.conifg -l /lib:/usr/lib:/usr/local/lib
# crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/local/lib:/usr/sfw/lib
8.2.2.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.
8.2.2.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/
.
8.2.2.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
8.2.2.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 Server 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/
8.2.2.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 Server:serverURL[comment]=Remote server URL serverURL=https://your-satellite.example.com/XMLRPC
- Ensure the application refers to the RHN Satellite Server 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 8.2.2.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
8.3. Registration and Updates
8.3.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 8.2.1, “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
Be sure to replace the argument of each option with values appropriate to your organization. - Go back to the website, click the name of the activation key, and ensure the new system appears within the Activated Systems tab.
8.3.2. Obtaining Updates
8.3.2.1. Uploading Packages to the Satellite
solaris2mpm
to translate Solaris packages, patches, and patch clusters to a format that the Satellite can understand.
8.3.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 8.1. 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.
|
8.3.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
8.3.2.2. Updating Through the Website
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 8.2. 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
|
8.3.2.3. Updating From the Command Line
up2date
command. The most significant difference is the absence of all options regarding source files. Refer to Table 8.3, “Update Agent Command Line Arguments” for the precise list of options available for UNIX systems.
Table 8.3. 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. |
8.4. Remote Commands
8.4.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
8.4.2. Issuing Commands
Appendix A. 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.
A.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 Organization 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.
A.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 A.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.
A.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.
A.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.
A.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 6.4.2.9, “System Details” for instructions.
A.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 A.2. rhncfg-client get
options
Option | Description |
---|---|
--topdir=TOPDIR | Make all file operations relative to this string. |
-h, --help | Show help message and exit |
A.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
A.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 A.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 |
A.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”.
A.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
A.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 A.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 |
A.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 A.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 |
A.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 A.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 A.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 |
A.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 A.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 |
A.3.6. Getting the Contents of a File
rhncfg-manager get
\--channel=channel-label
/tmp/dest_path/example-config.txt
A.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 A.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 |
A.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.
A.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 A.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 |
A.3.10. Deleting a Config Channel
rhncfg-manager remove-channel channel-label
Removing config channel example-channel Config channel example-channel removed
A.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
A.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 A.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 |
A.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 A.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 B. RHN API Access
B.1. Using the auth Class and Getting the Session
B.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.
B.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.
B.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".
B.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.
B.6. Channel Labels
Table B.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 |
B.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 C. Probes
rhnmd
). This requirement is noted within the individual probe reference.
Note
C.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 Server. 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
C.2. Apache 1.3.x and 2.0.x
https
and the port to 443
.
C.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 C.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 |
C.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 C.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) |
C.2.3. Apache::Uptime
Table C.3. Apache::Uptime settings
Field | Value |
---|---|
Application Protocol* | http |
Port* | 80 |
Pathname* | /server-status |
UserAgent* | NOCpulse-ApacheUptime/1.0 |
Username | |
Password | |
Timeout* | 15 |
C.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.
C.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 C.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 |
C.3.2. BEA WebLogic::Heap Free
- Heap Free — The percentage of free heap space.
Table C.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 |
C.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 C.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 |
C.3.4. BEA WebLogic::Server State
Table C.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* |
C.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 C.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 |
C.4. General
C.4.1. General::Remote Program
rhnmd
) must be running on the monitored system to execute this probe.
Table C.9. General::Remote Program settings
Field | Value |
---|---|
Command* | |
OK Exit Status* | 0 |
Warning Exit Status* | 1 |
Critical Exit Status* | 2 |
Timeout | 15 |
C.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 C.10. General::Remote Program with Data settings
Field | Value |
---|---|
Command* | |
OK Exit Status* | 0 |
Warning Exit Status* | 1 |
Critical Exit Status* | 2 |
Timeout | 15 |
C.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 C.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 |
C.4.4. General::TCP Check
- Remote Service Latency — The time it takes in seconds for the TCP server to answer a connection request.
Table C.12. General::TCP Check settings
Field | Value |
---|---|
Send | |
Expect | |
Port* | 1 |
Timeout* | 10 |
Critical Maximum Latency | |
Warning Maximum Latency |
C.4.5. General::UDP Check
- Remote Service Latency — The time it takes in seconds for the UDP server to answer a connection request.
Table C.13. General::UDP Check settings
Field | Value |
---|---|
Port* | 1 |
Send | |
Expect | |
Timeout* | 10 |
Critical Maximum Latency | |
Warning Maximum Latency |
C.4.6. General::Uptime (SNMP)
Table C.14. General::Uptime (SNMP) settings
Field | Value |
---|---|
SNMP Community String* | public |
SNMP Port* | 161 |
SNMP Version* | 2 |
Timeout* | 15 |
C.5. Linux
rhnmd
daemon be running on the monitored system.
C.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 C.15. Linux::CPU Usage settings
Field | Value |
---|---|
Timeout* | 15 |
Critical Maximum CPU Percent Used | |
Warning Maximum CPU Percent Used |
C.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 C.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 |
C.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 C.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 |
C.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 C.18. Linux::Inodes settings
Field | Value |
---|---|
File system* | / |
Timeout* | 15 |
Critical Maximum Inodes Percent Used | |
Warning Maximum Inodes Percent Used |
C.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 C.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 |
C.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 C.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 |
C.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 C.21. Linux::Memory Usage settings
Field | Value |
---|---|
Include reclaimable memory | no |
Timeout* | 15 |
Warning Maximum RAM Free | |
Critical Maximum RAM Free |
C.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 C.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 |
C.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 C.23. Linux::Process Count Total settings
Field | Value |
---|---|
Timeout* | 15 |
Critical Maximum Process Count | |
Warning Maximum Process Count |
C.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 C.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 |
C.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 C.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 |
C.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 C.26. Linux::Swap Usage settings
Field | Value |
---|---|
Timeout* | 15 |
Warning Minimum Swap Free | |
Critical Minimum Swap Free |
C.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 C.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 |
C.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 C.28. Linux::Users settings
Field | Value |
---|---|
Timeout* | 15 |
Critical Maximum Users | |
Warning Maximum Users |
C.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 C.29. Linux::Virtual Memory settings
Field | Value |
---|---|
Timeout* | 15 |
Warning Minimum Virtual Memory Free | |
Critical Minimum Virtual Memory Free |
C.6. LogAgent
nocpulse
user must be granted read access to your log files.
C.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 C.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 |
C.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 C.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 |
C.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 Server Installation Guide for instructions.
C.7.1. MySQL::Database Accessibility
Table C.32. MySQL::Database Accessibility settings
Field | Value |
---|---|
Username* | |
Password | |
MySQL Port | 3306 |
Database* | mysql |
Timeout | 15 |
C.7.2. MySQL::Opened Tables
- Opened Tables — The tables that have been opened since the server was started.
Table C.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 |
C.7.3. MySQL::Open Tables
- Open Tables — The number of tables open when the probe runs.
Table C.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 |
C.7.4. MySQL::Query Rate
- Query Rate — The average number of queries per second per database server.
Table C.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 |
C.7.5. MySQL::Threads Running
- Threads Running — The total number of running threads within the database.
Table C.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 |
C.8. Network Services
C.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 C.37. Network Services::DNS Lookup settings
Field | Value |
---|---|
Host or Address to look up | |
Timeout* | 10 |
Critical Maximum Query Time | |
Warning Maximum Query Time |
C.8.2. Network Services::FTP
- Remote Service Latency — The time it takes in seconds for the FTP server to answer a connection request.
Table C.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 |
C.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 C.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 |
C.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 C.40. Network Services::Mail Transfer (SMTP) settings
Field | Value |
---|---|
SMTP Port* | 25 |
Timeout* | 10 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
C.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 C.8.7, “Network Services::Remote Ping”.
Table C.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 |
C.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 C.42. Network Services::POP Mail settings
Field | Value |
---|---|
Port* | 110 |
Expect* | +OK |
Timeout* | 10 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
C.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 C.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 |
C.8.8. Network Services::RPCService
- Remote Service Latency — The time it takes in seconds for the RPC server to answer a connection request.
Table C.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 |
C.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 C.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 |
C.8.10. Network Services::SSH
- Remote Service Latency — The time it takes in seconds for the SSH server to answer a connection request.
Table C.46. Network Services::SSH settings
Field | Value |
---|---|
SSH Port* | 22 |
Timeout* | 5 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
C.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 C.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 |
C.9. Oracle 8i and 9i
$ORACLE_HOME/rdbms/admin/catalog.sql
C.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 C.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 |
C.9.2. Oracle::Availability
Table C.49. Oracle::Availability settings
Field | Value |
---|---|
Oracle SID* | |
Oracle Username* | |
Oracle Password* | |
Oracle Port* | 1521 |
Timeout* | 30 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.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 C.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 |
C.9.15. Oracle::TNS Ping
- Remote Service Latency — The time it takes in seconds for the Oracle server to answer a connection request.
Table C.62. Oracle::TNS Ping settings
Field | Value |
---|---|
TNS Listener Port* | 1521 |
Timeout* | 15 |
Critical Maximum Remote Service Latency | |
Warning Maximum Remote Service Latency |
C.10. RHN Satellite Server
C.10.1. RHN Satellite Server::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 C.63. RHN Satellite Server::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 |
C.10.2. RHN Satellite Server::Execution Time
- Probe Execution Time Average — The seconds required to fully execute a probe.
Table C.64. RHN Satellite Server::Execution Time settings
Field | Value |
---|---|
Critical Maximum Probe Execution Time Average | |
Warning Maximum Probe Execution Time Average |
C.10.3. RHN Satellite Server::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 C.65. RHN Satellite Server::Interface Traffic settings
Field | Value |
---|---|
Interface* | eth0 |
Timeout (seconds)* | 30 |
Critical Maximum Input Rate | |
Critical Maximum Output Rate |
C.10.4. RHN Satellite Server::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 C.66. RHN Satellite Server::Latency settings
Field | Value |
---|---|
Critical Maximum Probe Latency Average | |
Warning Maximum Probe Latency Average |
C.10.5. RHN Satellite Server::Load
- Load — The load average on the CPU for a 1-, 5-, and 15-minute period.
Table C.67. RHN Satellite Server::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 |
C.10.6. RHN Satellite Server::Probe Count
- Probes — The number of individual probes running on a Satellite.
Table C.68. RHN Satellite Server::Probe Count settings
Field | Value |
---|---|
Critical Maximum Probe Count | |
Warning Maximum Probe Count |
C.10.7. RHN Satellite Server::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 C.69. RHN Satellite Server::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 |
C.10.8. RHN Satellite Server::Processes
- Processes — The number of processes running simultaneously on the machine.
Table C.70. RHN Satellite Server::Processes settings
Field | Value |
---|---|
Critical Maximum Processes | |
Warning Maximum Processes |
C.10.9. RHN Satellite Server::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 C.71. RHN Satellite Server::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 |
C.10.10. RHN Satellite Server::Process Running
Table C.72. RHN Satellite Server::Process Running settings
Field | Value |
---|---|
Command Name | |
Process ID (PID) file | |
Critical Number Running Maximum | |
Critical Number Running Minimum |
C.10.11. RHN Satellite Server::Swap
Table C.73. RHN Satellite Server::Swap settings
Field | Value |
---|---|
Critical Minimum Swap Percent Free | |
Warning Minimum Swap Percent Free |
C.10.12. RHN Satellite Server::Users
Table C.74. RHN Satellite Server::Users settings
Field | Value |
---|---|
Critical Maximum Users | |
Warning Maximum Users |
Appendix D. Revision History
Revision History | |||
---|---|---|---|
Revision 2.0-1.400 | 2013-12-18 | Rüdiger Landmann | |
| |||
Revision 2.0-1 | Fri Nov 1 2013 | Zac Dover | |
|
Glossary
A
- 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.
B
- 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.
C
- 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 .
D
- 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.
E
- 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.
M
- 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.
N
- Notification Method
- An email address to which RHN Monitoring messages will be sent.
O
- Organization Administrator
- Organization 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 Organization Administrator can also give users administrative privileges to system groups. An RHN organization must have at least one member of the Organization Administrator group.
P
- 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.
R
- Red Hat Network Daemon
- The RHN client daemon (
rhnsd
) that periodically polls Red Hat Network for scheduled actions. - 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.
- 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.
S
- 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.
- 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 Organization 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.
U
- 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.
V
- 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.
Y
- 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.
Index
A
- 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
- 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 Entitlements, Channel Entitlements
- Channel List , Software Channels
- Channels
- Software and Configuration Files, Channels
- channels, Channels
- all, All Channels
- base, Software Channels
- child, Software Channels
- entitling, Channel Entitlements
- errata, Software Channel Details ⇒ Errata
- list of, Software Channels
- packages, Software Channel Details ⇒ Packages
- relevant, Relevant Channels
- retired, Retired 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
- 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
- deleting a system, System Details ⇒ Details
- Digital Certificate, Security, Quality Assurance, and Red Hat Network
- download ISO images, Download Software
E
- email address
- entitlement
- with activation key, Activation Keys —
- entitlements
- purchase history, Expiration Dates &Purchase History
- 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
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
- ISO images
- all, All ISOs
- download, Download Software
- relevant, Relevant ISOs
K
- kickstart
- explained, Kickstart Explained
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
- 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-server 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-server package, mysql-server 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 and 9i
- Redo Log, Oracle::Redo Log
- Table Extents, Oracle::Table Extents
- Tablespace Usage, Oracle::Tablespace Usage
- TNS Ping, Oracle::TNS Ping
- Organization Administrator, User List ⇒ Active ⇒ User Details ⇒ Details —
- overview of website, Categories and Pages
P
- package installation
- package list
- Updating on server, Synchronizing Your System Profile, System Details ⇒ Software ⇒ Packages
- packages
- 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 Server
- Disk Space, RHN Satellite Server::Disk Space
- Execution Time, RHN Satellite Server::Execution Time
- Interface Traffic, RHN Satellite Server::Interface Traffic
- Latency, RHN Satellite Server::Latency
- Load, RHN Satellite Server::Load
- Probe Count, RHN Satellite Server::Probe Count
- Process Counts, RHN Satellite Server::Process Counts
- Process Health, RHN Satellite Server::Process Health
- Process Running, RHN Satellite Server::Process Running
- Processes, RHN Satellite Server::Processes
- Swap, RHN Satellite Server::Swap
- Users, RHN Satellite Server::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 and 9i
- RHN Satellite Server, RHN Satellite Server
- 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 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 (rhn)_register)
- 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
- 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 Server
- Disk Space, RHN Satellite Server::Disk Space
- Execution Time, RHN Satellite Server::Execution Time
- Interface Traffic, RHN Satellite Server::Interface Traffic
- Latency, RHN Satellite Server::Latency
- Load, RHN Satellite Server::Load
- Probe Count, RHN Satellite Server::Probe Count
- probes, RHN Satellite Server
- Process Counts, RHN Satellite Server::Process Counts
- Process Health, RHN Satellite Server::Process Health
- Process Running, RHN Satellite Server::Process Running
- Processes, RHN Satellite Server::Processes
- Swap, RHN Satellite Server::Swap
- Users, RHN Satellite Server::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)
- RHUA; (up2date)
- complete description, Red Hat Update Agent
S
- 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
- managers, Software Channel Details ⇒ Managers —
- subscribers, Software Channel Details ⇒ Subscribers —
- 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
- subscribe to channel, Software Channels
- 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)
- unsubscribe to channel, Software Channels
- Update
- service level, Update
- updating
- via command line, Updating From the Command Line
- via website, Updating Through the Website
- 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 —
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
- Errata 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
- Purchase History, Expiration Dates &Purchase History
- 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
- Your RHN, Your RHN
Y
- Your RHN, Your RHN
- Help, Help
- Purchase History, Expiration Dates &Purchase History
- Your Account, Your Account
- Your Preferences, Your Preferences