Page 1 Red Hat Network Satellite Reference Guide 5.1.0 ISBN: Publication date:...
Page 2 Red Hat Network Satellite...
Page 3 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
Page 4 Red Hat Network Satellite...
Page 5: Table Of Contents
Introduction to the Guide ..................xiii 1. More to Come ....................xiii 1.1. Send in Your Feedback ..............xiv 1. Red Hat Network Overview ..................1 1. Update ......................2 2. Management ....................3 3. Provisioning ....................4 4. Monitoring ..................... 4 5.
Page 6 Red Hat Network Satellite 4. Registering a System Profile ................52 4.1. Hardware System Profile ..............53 4.2. Software System Profile ..............54 5. Finishing Registration ..................56 6. Entitling Your System ..................58 7. Text Mode RHN Registration Client ..............59 6. Red Hat Network Website ..................61 1.
Page 7 7.3. Configuration Channels ..............132 7.4. Configuration Files ................134 7.5. Locally-Managed Files ..............135 7.6. Systems ..................137 8. Schedule ....................138 8.1. Pending Actions ................139 8.2. Failed Actions ..................139 8.3. Completed Actions ................139 8.4. Archived Actions ................139 8.5. Actions List ..................139 9. Users — .....................141 9.1.
Page 8 Red Hat Network Satellite 2.4. Installing the SSH key ..............166 package ................167 mysql-server 4. Notifications ....................167 4.1. Creating Notification Methods ............167 4.2. Receiving Notifications ..............168 4.3. Redirecting Notifications ..............169 4.4. Filtering Notifications ................170 4.5. Deleting Notification Methods ............170 5. Probes .......................171 5.1.
Page 9 1. Red Hat Network Actions Control .............207 1.1. General command line options ............207 2. Red Hat Network Configuration Client ............208 2.1. Listing Config Files ................208 2.2. Getting a Config File .................209 2.3. Viewing Config Channels ..............209 2.4. Differentiating between Config Files ..........210 2.5.
Page 10 Red Hat Network Satellite 4.5. General::UDP Check ................233 4.6. General::Uptime (SNMP) ..............234 5. Linux ......................234 5.1. Linux::CPU Usage ................234 5.2. Linux::Disk IO Throughput ..............235 5.3. Linux::Disk Usage ................235 5.4. Linux::Inodes ...................236 5.5. Linux::Interface Traffic ..............236 5.6. Linux::Load ..................237 5.7. Linux::Memory Usage ...............238 5.8.
Page 11 9.8. Oracle::Idle Sessions ................261 9.9. Oracle::Index Extents ...............261 9.10. Oracle::Library Cache ..............262 9.11. Oracle::Locks .................263 9.12. Oracle::Redo Log ................263 9.13. Oracle::Table Extents ..............264 9.14. Oracle::Tablespace Usage ..............265 9.15. Oracle::TNS Ping ................265 10. RHN Satellite Server .................266 10.1. RHN Satellite Server::Disk Space ............266 10.2.
Page 13: Introduction To The Guide
The Red Hat Network Reference Guide is constantly expanding as new Red Hat Network features and service plans are launched. HTML and PDF versions of this and other manuals are available within the Help section of the RHN website and at http://www.redhat.com/docs/. Note...
Page 14: Send In Your Feedback
1.1. Send in Your Feedback If you would like to make suggestions about the Red Hat Network Reference Guide, please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component Documentation_Reference_Guide (Product: Red Hat Network Satellite, Version: 510). http://www.redhat.com/docs/...
Page 15: Red Hat Network Overview
Chapter 1. Red Hat Network Overview Have you ever read about a new version of a software package and wanted to install it but could not find it? Have you ever tried to find an RPM through an Internet search engine or an RPM repository and been linked to an unknown site? Have you ever tried to find an RPM but instead found only source files that you had to compile yourself?
Page 16: Update
The RHN Update service is ideal for a user with one Red Hat Enterprise Linux system or a small number of Red Hat Enterprise Linux systems. Updated Subscription to Update can be purchased at https://www.redhat.com/apps/commerce/rhn/. With each Update subscription, you receive the following services: •...
Page 17: Management
To create an account that can be used to entitle systems to RHN Management, go to https://rhn.redhat.com/ and click on the Create Login link under the Sign In fields. On the Create a Red Hat Login page, click Create a new Business Login. After creating a business account, you may add users within your organization to it.
Page 18: Provisioning
Chapter 1. Red Hat Network Overview 3. Provisioning As the highest management service level, RHN Provisioning encompasses all of the features offered in the RHN Update and Management subscription levels. It is designed to allow you to deploy and manage your network of Red Hat Enterprise Linux systems, users, and system groups.
Page 19: Errata Notifications And Scheduled Package Installations
Errata Notifications and Scheduled Package • 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.
Page 20: Before You Begin
Chapter 1. Red Hat Network Overview Red Hat Network incorporates the following security measures: 1. Your System Profile, available at http://rhn.redhat.com, is accessible only with an RHN-verified username and password. 2. A Digital Certificate is written to the client system after registration and is used to authenticate the system during each transaction between the client and Red Hat Network.
Page 21 Installations If the Red Hat Network Registration Client is installed, it will return something similar to: rhn_register-2.9.3-1 The version number might differ slightly. If you do not have the Red Hat Network Registration Client installed, the command will return: package rhn_register is not installed Perform this check for every package in Table 1.1, “Red Hat Network Packages”...
Page 23: Red Hat Update Agent
Chapter 2. Red Hat Update Agent The Red Hat Update Agent is your connection to Red Hat Network. It enables you to register your systems, create System Profiles, and alter the settings by which your organization and RHN interact. Once registered, your systems can use the Red Hat Update Agent to retrieve the latest software packages from Red Hat.
Page 24 Chapter 2. Red Hat Update Agent • At a shell prompt (for example, an xterm or gnome-terminal), type the command up2date For Red Hat Enterprise Linux 2.1: • On the GNOME desktop, go to the Main Menu Button (on the Panel) => Programs => System =>...
Page 25 Starting the Red Hat Update Agent The first time you run the Red Hat Update Agent, two dialog boxes appear that you will not see in subsequent startups: Configure Proxy Server and Install GPG Key. As shown in Figure 2.1, “Configure Proxy Server”, the first dialog box to appear prompts you for HTTP Proxy Server information.
Page 26: Registration
Chapter 2. Red Hat Update Agent Figure 2.2, “Install GPG Key”. This key is used to verify the packages you download for security purposes. Click Yes to install the key, and you will not see this message again. Figure 2.2. Install GPG Key 2.
Page 27: Registering A User Account
2.1. Registering a User Account Before you create a System Profile, you must create a user account. Red Hat recommends that you do so through the website at https://rhn.redhat.com/newlogin/, but you may also do so via Red Hat Update Agent (...
Page 28 Chapter 2. Red Hat Update Agent Users that have registered at least one system with Red Hat Network can add new machines to the same account. To do so, run the Red Hat Update Agent on the new machine and enter the existing Red Hat username and password at this screen.
Page 29 Activate • Must be at least four characters long • Cannot contain any tabs • Cannot contain any line feeds Passwords are case-sensitive for obvious reasons. Note You must choose a unique username. If you enter one already in use, you will see an error message.
Page 30: Activate
Chapter 2. Red Hat Update Agent 2.2. Activate The Activation screen allows you to select various details of your registration. If you have a subscription number, enter it in the appropriate field. If not, select the Use one of my existing, active subscriptions radio button.
Page 31: Channels
Channels Figure 2.6. Activate Figure 2.7, “Sending System Profile to Red Hat Network” shows the progress bar displayed as the System Profile is sent. Figure 2.7. Sending System Profile to Red Hat Network 2.3. Channels...
Page 32 Chapter 2. Red Hat Update Agent Red Hat Update Agent next displays all package channels to which you have access. The channels you select from this screen must match the base operating system of the system you are registering. if any child channels are available, such as the RHEL AS (v.4 for x86) Extras channel in the figure, you may select them as well.
Page 33: Packages Flagged To Be Skipped
Packages Flagged to be Skipped Figure 2.9. Fetching package list Note If the version of on your system is older than the one in your selected up2date 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 package.
Page 34: Available Package Updates
Chapter 2. Red Hat Update Agent Figure 2.10. Packages Flagged to be Skipped 2.5. Available Package Updates The Red Hat Update Agent next displays all available updates except those you chose to skip in the previous screen. Select those you wish to download and click Forward to continue.To view the complete Errata Advisory text for an update, highlight the relevant package and click the View Advisory button.
Page 35 Available Package Updates Figure 2.11. Available Package Updates...
Page 36: Retrieving Packages
Chapter 2. Red Hat Update Agent Figure 2.12. Example Errata Advisory 2.6. Retrieving Packages The Red Hat Update Agent tests the packages you selected to be certain that the requirements of each RPM are met. If any additional packages are required, Red Hat Update Agent displays an error message.
Page 37: Installing Packages
Installing Packages Figure 2.13. Retrieving Packages 2.7. Installing Packages The packages must be installed after downloading them via the Red Hat Update Agent. If you chose not to install the packages via the Red Hat Update Agent, skip to Section 3.2, “Manual Package Installation”...
Page 38 Chapter 2. Red Hat Update Agent Figure 2.14. Installing Packages When the Red Hat Update Agent has finished downloading the desired packages (and installing them if you chose the install option), it displays the screen in Figure 2.15, “All Finished”. Click Finish to exit the Red Hat Update Agent.
Page 39: Command Line Version
Command Line Version Figure 2.15. All Finished 3. Command Line Version If you are not running X, you can still run the Red Hat Update Agent from a virtual console or remote terminal. If you are running X but want to use the command line version, you can force it not to display the graphical interface with the following command: up2date --nox The command line version of the Red Hat Update Agent allows you to perform advanced...
Page 40 Chapter 2. Red Hat Update Agent The command line version of the Red Hat Update Agent accepts the following arguments: Option Description Briefly describe the available options. --usage List the available options and exit. --help Force to install this architecture of the --arch=architecture up2date package.
Page 41 Command Line Version Option Description Do not download packages at all. This is useful in --nodownload testing. Do not use GPG to check package signatures. This --nosig option temporarily overrides the saved configuration option. Do not download source packages (SRPMs). --nosrc Do not attempt to run in X.
Page 42: Installing The Red Hat Gpg Key
Chapter 2. Red Hat Update Agent Option Description Show additional output while updating. --verbose Show version information. --version up2date Show the packages that resolve the comma-separated --whatprovides=dependencies list of dependencies. Table 2.2. Update Agent Command Line Arguments Note options can be used to solve the --solvedeps --whatprovides dependencies for an RPM regardless even if your system does not currently...
Page 43: Manual Package Installation
Manual Package Installation /usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY To download the Red Hat GPG key first, you may obtain it from https://www.redhat.com/security/team/key.html . Here's an example: 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)
Page 44: Synchronizing Your System Profile
Chapter 2. Red Hat Update Agent finish installing, you can delete them if you wish. You do not need them anymore. After installing the packages, you must update your System Profile so that you are not prompted to download them again. Refer to Section 3.3, “Synchronizing Your System Profile”...
Page 45 Using the Red Hat Update Agent 4.1.1. General Settings The General tab allows you to enable an HTTP Proxy Server. If your network connection requires you to use an HTTP Proxy Server to make HTTP connections, select the Enable HTTP Proxy option and type your proxy server in the text field with the format http://HOST:PORT.
Page 46 Chapter 2. Red Hat Update Agent Warning You must use Red Hat Update Agent Version 2.5.4 or higher to upgrade your kernel automatically. Red Hat Update Agent will install the updated kernel and configure LILO or GRUB to boot the new kernel the next time the system is rebooted.
Page 47 Configuration Tool 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 ) and the binary ( ) files *.src.rpm *.[architecture].rpm The following installation options are configurable (see Figure 2.17, “Retrieval/Installation Settings”): •...
Page 48: Command Line Version
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...
Page 49: Registering With Activation Keys
Registering with Activation Keys /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.
Page 50 Chapter 2. Red Hat Update Agent to be registered: rhnreg_ks --activationkey=7202f3b7d218cf59b764f9f6e9fa281b The precise value of the activation key varies. Systems running Red Hat Enterprise Linux 2.1 substitute the option for the --serialnumber option: --activationkey rhnreg_ks --serialnumber=7202f3b7d218cf59b764f9f6e9fa281b In addition, Provisioning-entitled systems may use multiple activation keys at once, either at the command line or within kickstart profiles.
Page 51: Registering A System To An Organization
Registering a System to an Organization • 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.
Page 53: Red Hat Network Daemon
Chapter 3. Red Hat Network Daemon The Red Hat Network Daemon ( ) periodically connects to Red Hat Network to check for rhnsd updates and notifications. The daemon, which runs in the background, is typically started from the initialization scripts in /etc/init.d/rhnsd /etc/rc.d/init.d/rhnsd To check for updates,...
Page 54 Chapter 3. Red Hat Network Daemon 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.
Page 55: Red Hat Network Alert Notification Tool
Chapter 4. Red Hat Network Alert Notification Tool The Red Hat Network Alert Notification Tool is a notifier that appears on the panel and alerts users when software package updates are available for their systems. The list of updates is retrieved from the RHN Servers.
Page 56 Chapter 4. Red Hat Network Alert Notification Tool Figure 4.2. HTTP Proxy Configuration If your network connection requires you to use an HTTP Proxy Server to make HTTP connections, on the Proxy Configuration screen, type your proxy server in the text field with the format HOST:PORT.
Page 57: Notification Icons
Notification Icons Or, for SSL: server_url=https://YourRHN_Satellite.com/APPLET You can also configure the Red Hat Network Alert Notification Tool to ignore specific packages. To select these packages, click on the applet and select the Ignored Packages tab. 2. Notification Icons The applet displays a different icon, depending on the status of the updates. Table 4.1, “Red Hat Network Alert Notification Tool Icons”...
Page 58: Viewing Updates
Chapter 4. Red Hat Network Alert Notification Tool 3. Viewing Updates Clicking on the Red Hat Network Alert Notification Tool displays a list of available updates. To alter your list of excluded packages, click the Ignored Packages tab and make your modifications.
Page 59: Red Hat Network Registration Client
Chapter 5. Red Hat Network Registration Client Before you begin using Red Hat Network, you must create a username, password, and System Profile. The Red Hat Network Registration Client walks you through this process. Warning Only systems running Red Hat Enterprise Linux 2.1 need to use the Red Hat Network Registration Client before starting the Red Hat Update Agent.
Page 60 2. oemInfoFile /etc/sysconfig/rhn/oeminfo 3. enableProxy No 4. networkSetup Yes 5. httpProxy 6. proxyUser 7. serverURL https://xmlrpc.rhn.redhat.com/XMLRPC 8. proxyPassword 9. debug No Enter number of item to edit <return to exit, q to quit without saving>: Enter the number of the item to modify and enter a new value for the option. When finished changing your configuration, press Enter to save your changes and exit.
Page 61: Starting The Red Hat Network Registration Client
Starting the Red Hat Network Registration The most common options configured are to enable a proxy enableProxy httpProxy server. To enable a proxy server, change the value for and the value of enableProxy to the name of the proxy server and port number in the format HOST:PORT. For httpProxy example, to use the proxy server squid.mysite.org on port 3128, you would change the value to squid.mysite.org:3128...
Page 62 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. If you overwrite an existing system registration, you can delete the unused profile via the website at https://rhn.redhat.com. Figure 5.3. Warning: This System Already Registered...
Page 63 Client The opening screen for the Red Hat Network Registration Client provides a brief overview of the services available and the steps required to register (see Figure 5.4, “Welcome Screen”). Click Next to continue with the registration process. If you click Cancel, the registration process ends and no information is sent.
Page 64: Registering A User Account
Chapter 5. Red Hat Network Registration Client Figure 5.5. Red Hat Privacy Statement 3. Registering a User Account Before you can create a System Profile, you must create a user account. The only required information in this section is a unique username, password, and a valid email address. In the screen shown in Figure 5.7, “Create a Unique Username and Password”, you must...
Page 65 Registering a User Account Figure 5.6. Error: Username Already Exists Note If you are already a member of redhat.com, you can use the same user name and password. However, you must continue with the registration process to create your System Profile.
Page 66: Registering A System Profile
Chapter 5. Red Hat Network Registration Client machine is added to your existing account, and you can log into Red Hat Network with your username and password to view all your systems simultaneously. Figure 5.7. Create a Unique Username and Password Most users can leave the Org Info section blank.
Page 67: Hardware System Profile
Hardware System Profile 4.1. Hardware System Profile After creating a username and password for your Red Hat Network account, the Red Hat Network Registration Client probes your system for the following information: • Red Hat Enterprise Linux version • Hostname •...
Page 68: Software System Profile
Chapter 5. Red Hat Network Registration Client Figure 5.8. System Profile - Hardware 4.2. Software System Profile The software System Profile consists of a list of RPM packages for which you wish to receive notifications. The Red Hat Network Registration Client displays a list of all RPM packages listed in the RPM database on your system and then allows you to customize the list by deselecting packages.
Page 69 Software System Profile Figure 5.9. Registration Wizard Once the RPM package list is built, the list is displayed as shown in Figure 5.10, “RPM Package Information”. Deselecting Include RPM Packages installed on this system in my System Profile omits this information from your System Profile. Figure 5.10.
Page 70: Finishing Registration
Chapter 5. Red Hat Network Registration Client Choose which packages to exclude, if any, from the System Profile, and click Next to continue with the registration process. Figure 5.11. Choose which RPM Packages to Exclude from System Profile 5. Finishing Registration As seen in Figure 5.12, “Finished Collecting Information for System Profile”, the last step of...
Page 71 Finishing Registration Figure 5.12. Finished Collecting Information for System Profile Figure 5.13, “Send System Profile to Red Hat Network” shows the progress bar displayed while your profile is sent. This process may take some time depending on your connection speed. Figure 5.13.
Page 72: Entitling Your System
In other words, you must subscribe it to a service level offering. To entitle a system, go to http://rhn.redhat.com and log in using the same username and password you just used in the Red Hat Network Registration Client. Click Systems on the top navigation bar and then Systems Entitlements in the left navigation bar.
Page 73: Text Mode Rhn Registration Client
Text Mode RHN Registration Client change entitlements to any available level at any time. Note Removing a required entitlement (such as Provisioning) will not cancel a previously scheduled action (such as a kickstart). As you change the selected entitlements for your systems, the number of available entitlements is updated at the bottom of the screen.
Page 74 Chapter 5. Red Hat Network Registration Client Figure 5.15. Text Mode Welcome Screen...
Page 75: Red Hat Network Website
Chapter 6. Red Hat Network Website You can use the Red Hat Network website to manage multiple Red Hat Enterprise Linux systems simultaneously, including viewing Errata Alerts, applying Errata Updates, and installing packages. This chapter seeks to identify all of categories, pages, and tabs within the website and explain how to use them.
Page 76: Entitlement Views
Chapter 6. Red Hat Network Website 1.1. Entitlement Views Keep in mind, since this guide covers all entitlement levels, some tabs, pages, and even whole categories described here may not be visible to you. For this reason, icons are used here to identify which functions are available to each entitlement level.
Page 77 Categories and Pages • Subscription Management — Manage base and add-on system entitlements, such as Management, Provisioning, and Virtualization. • Systems — Manage all of your systems (including virtual guest systems) here. • Overview — — View a summary of your systems or system groups showing how many Errata Alerts each system has and which systems are entitled.
Page 78 Chapter 6. Red Hat Network Website • Channels — View and manage the available RHN channels and the files they contain. • Software Channels — View a list of all software channels and those applicable to your systems. • Package Search — Search packages using all or some portion of the package name, description, or summary, with support for limiting searches to supported platforms.
Page 79: Errata Alert Icons
Errata Alert Icons • Satellite Tools (visible only to Satellite administrators) — List, create, and manage one or more Satellite organizations, from which the Satellite administrator can assign channel entitlements, create and assign administrators for each organization, and other tasks. •...
Page 80: Systems Selected
2. Logging into the RHN Website Use a web browser to navigate to http://rhn.redhat.com. RHN displays the login page shown below unless one of two things is true: •...
Page 81 Logging into the RHN Website Figure 6.4. RHN Website If you have not registered a system yet or do not have a redhat.com account, create a new account by following the Learn More link, then selecting Create Login on the resulting page.
Page 82: Your Rhn
Chapter 6. Red Hat Network Website Note You must accept both the Site Terms and the T7 agreement in order to use RHN. Once you have accepted the agreements and pressed the Continue button, RHN displays the Your RHN page. 3.
Page 83 Your RHN Figure 6.5. Your Red Hat Network This page is broken into functional areas, with the most critical areas displayed first. Users can control which of the following areas are displayed by making selections on the Your RHN # Your Preferences page.
Page 84: Your Account
Remember, if you change your Red Hat Network password (the one used to log into RHN and redhat.com), you will not see your new one as you type it for security reasons. Also for security, your password is represented by 12 asterisks no matter how many characters it actually contains.
Page 85: Your Preferences
Your Preferences modified, make the changes, and click Update. 3.1.2. Change Email The email address listed in the Your Account page is the address to which Red Hat Network sends email notifications if you select to receive Errata Alerts or daily summaries for your systems on the Your Preferences page.
Page 86: Locale Preferences
Chapter 6. Red Hat Network Website Start Page. Check the box to the left of the information area you would like to include. After making changes to any of these options, click the Save Preferences button in the bottom right-hand corner. 3.3.
Page 87 Subscription Management 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.
Page 88: Systems
Chapter 6. Red Hat Network Website manner. The first table on this page displays any Virtualization-entitled hosts that have more guest systems than are allowed in the Red Hat Network service level agreement. If you would like to upgrade these systems to any available Virtualization Platform entitlements, click the profile name of that system.
Page 89 Systems The Systems page displays a list of all of your registered systems. The Systems list contains several columns of information for each system: • 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.
Page 90 Chapter 6. Red Hat Network Website 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 the configuration file.
Page 91 Systems This column indicates whether a guest is running, paused, or stopped. Base Channel This column indicates the base channel to which the guest is currently subscribed. Only those guests that are registered with RHN are displayed in blue text. Clicking on the hostname of such a guest system displays that system's System Details page.
Page 92 Chapter 6. Red Hat Network Website • The system is not on the network. • Some other barrier exists between the system and the RHN Servers. 4.2.7. Recently Registered The Recently Registered page displays any new systems that have been registered in a given period of time.
Page 93 Systems • Events The following sections discuss these tabs and their sub-tabs in detail. 4.2.9.1. System Details # Details This page is not accessible from any of the standard navigation bars. However, clicking on the name of a system anywhere in the web interface brings you to this page. The default tab displayed on this page is the Details # Overview subtab.
Page 94 Chapter 6. Red Hat Network Website The IP address of the client. Kernel The kernel that is installed and operating on the client system. Registered The date and time at which the system registered with RHN and created this profile. Checked In The date and time at which the system last checked in with RHN.
Page 95 Systems 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 4.3, “System Groups — ” for more information about System Groups.
Page 96 Chapter 6. Red Hat Network Website Profile Name This editable name for the system profile is set to the system's hostname by default. It serves to distinguish this system profile from others. Entitlement The base entitlement currently applied to this system. Notifications Indicates the the notification options for this system.
Page 97 Systems 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.
Page 98 Chapter 6. Red Hat Network Website allow remote commands: touch /etc/sysconfig/rhn/allowed-actions/script/run Once the setup is complete, refresh the page in order to view the text fields for remote commands. You may then identify a specific user, group, and timeout period, as well as the script itself on this page.
Page 99 Systems This subtab, available for systems with a Provisioning entitlement, provides completely customizable information about the system. Unlike Notes, Custom Info is structured, formalized, and can be searched upon. Before you can provide custom information about a system, you must first have Custom Information Keys. This is done via the Custom System Info page, available from the left navigation bar.
Page 100 Chapter 6. Red Hat Network Website — When selecting packages to install, upgrade, or remove, Provisioning customers have the option of running a remote command automatically before or after the package installation. Refer to Section 4.2.9.1.3, “System Details # Details # Remote Command — ”...
Page 101 Systems 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.
Page 102 Chapter 6. Red Hat Network Website useful to a system at any given time. Remember, only the latest version can be deployed. 4.2.9.3.1. System Details # Configuration # Overview This subtab provides access to the configuration statistics of your system and to the most common tasks used to manage configuration files.
Page 103 Systems 4.2.9.3.3. System Details # Configuration # Compare Files This subtab compares a configuration file as stored on the Satellite with the file as it exists on the client. (It does not, for example, compare versions of the same file stored in different channels.) Select the files to be diffed, click the Compare Files button, select a time to perform the diff, and click the Schedule Compare button to confirm.
Page 104 Chapter 6. Red Hat Network Website This tab and its subtabs allow you to schedule and monitor kickstarts and to return your system to a previous state. Kickstart is a Red Hat utility that allows you to automate the reinstallation of a system.
Page 105 Systems • channel subscriptions • installed packages • configuration channel subscriptions • configuration files • snapshot tags When satisfied with the reversion, return to the Rollback subtab and click the Rollback to Snapshot button. To see the list again, click Return to snapshot list. 4.2.9.4.3.
Page 106 Chapter 6. Red Hat Network Website If a guest system has not registered to the Satellite, this information appears as plain text in the table. If you have System Group Administrator responsibilities assigned for your guest systems, it is possible that a user could see the message You do not have permission to access this system within the table.
Page 107: System Groups
System Groups — Refer to Section 4.3.3, “System Group Details — ” for more information. 4.2.9.5.3.2. System Details # Groups # Join — Lists groups that the system may be subscribed to. Only System Group Administrators and Satellite Administrators can add the system to groups. Non-admins see a Review this system's group membership page.
Page 108 Chapter 6. Red Hat Network Website System Groups list. Only System Group Administrators and Satellite Administrators may perform the following additional tasks: 1. Create system groups. (Refer to Section 4.3.1, “Creating Groups”.) 2. Add systems to system groups. (Refer to Section 4.3.2, “Adding and Removing Systems in Groups”.) 3.
Page 109 System Groups — • 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 4.3.3, “System Group Details — ”...
Page 110: System Set Manager
Chapter 6. Red Hat Network Website done through the System Set Manager or System Details pages. Refer to Section 4.4, “System Set Manager — ” Section 4.2.9, “System Details”, respectively. 4.3.3.3. System Group Details # Target Systems — Target Systems — Lists all systems in your organization. This tab enables you to add systems to the specified system group.
Page 111 System Set Manager — • 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 •...
Page 112 Chapter 6. Red Hat Network Website Refer to Section 4.2.9.1.3, “System Details # Details # Remote Command — ” for more information. 4.4.4.1. System Set Manager # Packages # Upgrade — A list of all the packages installed on the selected systems that might be upgraded. Systems must be subscribed to a channel providing the package for the system to be able to upgrade the package.
Page 113 System Set Manager — 4.4.8. System Set Manager # Groups — Tools to create groups and manage group membership. These functions are limited to Satellite Administrators and System Group Administrators. To add a new group, click create new group on the top-right corner. In the resulting page, type its name and description in the identified fields and click the Create Group button.
Page 114 Chapter 6. Red Hat Network Website Use this subtab to validate configuration files on the selected systems against copies in your central repository on RHN. The table lists the configuration files associated with any of the selected systems. Clicking its system count displays the systems already subscribed to the file. To compare the configuration files deployed on the systems with those in RHN, select the checkbox for each file to be validated.
Page 115 System Set Manager — also schedule the action by clicking the Schedule package installs for no sooner than radio button and using the drop-down menus to configure date and time, then clicking Enable RHN Configuration Management. 4.4.11. System Set Manager # Provisioning — Options for provisioning systems through the following subtabs: 4.4.11.1.
Page 116 Chapter 6. Red Hat Network Website 4.4.12.1. System Set Manager # Misc # System Profile Updates — Click Update Hardware Profile followed by the Confirm Refresh button to schedule a hardware profile update. Clicking Update Package Profile,followed by the Confirm Refresh button schedules a package profile update.
Page 117: Advanced Search
Advanced Search — • 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. •...
Page 118 Chapter 6. Red Hat Network Website System Details page are not part of this list because they are not reusable across systems. 4.6.1. Managing Activation Keys To generate an activation key: 1. Select Systems => Activation Keys from the top and left navigation bars. 2.
Page 119 Activation Keys — Figure 6.6. Activation Keys After creating the unique key, it appears in the list of activation keys along with the number of times it has been used. Note that only Activation Key Administrators can see this list. At this point, you may associate child channels and groups with the key so that systems registered with it automatically subscribe to them.
Page 120: Stored Profiles
Chapter 6. Red Hat Network Website To disable system activations with a key, unselect the corresponding checkbox under the Enabled column in the key list. The key can be re-enabled by selecting the checkbox. After making these changes, click the Update Keys button on the bottom right-hand corner of the page.
Page 121: Custom System Info
Kickstart — 4.8. Custom System Info — RHN Provisioning customers may include completely customizable information about their systems. Unlike notes, the information here is more formal and may be searched upon. For instance, you may decide to identify an asset tag for each system. To do this, you must create key within the Custom System Info page.
Page 122 Chapter 6. Red Hat Network Website Figure 6.7. Kickstart Overview This overview page displays the status of kickstart on your client systems: the types and number of profiles you have created and the progress of systems that are scheduled to be kickstarted.
Page 123 Kickstart — The Red Hat Enterprise Linux System Administration Guide contains an in-depth discussion of kickstart and is available here: http://www.redhat.com/docs/manuals/enterprise/. 4.9.1.1. Kickstart Explained When a machine is to receive a network-based kickstart, the following events must occur in this order: 1.
Page 124 Chapter 6. Red Hat Network Website Although Red Hat Network has taken great pains to ease the provisioning of systems, some preparation is still required for your infrastructure to handle kickstarts. For instance, before creating kickstart profiles, you may consider: •...
Page 125 Kickstart — label. Note that you cannot move between versions (2.1 to 3) or between updates (U1 to U2). Next, you may customize further for your needs, such as by adding multiple isolinux.cfg kickstart options, different boot messages, shorter timeout periods, etc. Next, create the ISO as described in the Making an Installation Boot CD-ROM section of the Red Hat Enterprise Linux 3 Installation Guide.
Page 126 Chapter 6. Red Hat Network Website Figure 6.8. Kickstart Profiles This page lists all profiles for your organization, whether those profiles are active, and the boot image to which that profile points. You can either create a new kickstart profile by clicking the create new kickstart profile link in the upper right or edit existing profiles by clicking in the name of the profile.
Page 127 Kickstart — Security Guide, available at http://www.redhat.com/docs/manuals/enterprise/. The final stage of the wizard presents the Kickstart Details # Details tab. On this tab and the other sub-tabs, nearly every option for the new kickstart profile can be customized. The following sections describe the options available on each sub-tab.
Page 128 Chapter 6. Red Hat Network Website 4.9.3.3. Kickstart Details # Advanced Options — From this page, you can toggle several installation options on and off by checking and unchecking the boxes to the left of the option. For most installations, the default options are correct.
Page 129 Kickstart — partition swap --size=2000 partition pv.01 --size=1000 --grow volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 --grow 4.9.3.8. System Details # File Preservation — If you have previously created a file preservation list, you may include that list as part of the kickstart.
Page 130 RedHat/base/ kickstart tree. Satellite customers will most likely locate this file here: /var/www/satellite/rhn/kickstart/<kickstart label>/RedHat/base/comps.xml 4.9.3.12. Software # Package Profiles — If you have previously created a Package Profile from one of your registered systems, you can use that profile as a template for the files to be installed on a kickstarted system. Refer to Section 4.2.9.2.2, “System Details # Software # Packages”...
Page 131 Kickstart — 4. Indicate whether this script is to be executed in the %pre or %post section of the kickstart process 5. 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 option nochroot...
Page 132 Chapter 6. Red Hat Network Website then make the profile association in the GPG and SSL keys subtab of the Kickstart Details page. To develop a new key/certificate, click the create new stored key/cert link in the upper-right corner of the page. Enter a description, select the type, upload the file, and click the Update Key button.
Page 133: Errata
Errata menus, such as Red Hat Enterprise Linux AS (v.4 for x86) Red Hat Enterprise , respectively. When finished, click the Create button. Linux 4 4.9.7. Kickstart # File Preservation — Collects lists of files to be protected and re-deployed on systems during kickstart. For instance, if you have many custom configuration files located on a system to be kickstarted, enter them here as a list and associate that list with the kickstart profile to be used.
Page 134: Relevant Errata
(for Security Updates), and subject of the erratum, as well as the number of affected systems. In addition to the pages described within this chapter, you may view Errata by product line from the following location: https://rhn.redhat.com/errata. 5.1. Relevant Errata As shown in Figure 6.15, “Errata...
Page 135: All Errata
All Errata Figure 6.15. Errata List Clicking on the Advisory takes you to the Details tab of the Errata Details page. Clicking on the number of associated systems takes you to the Affected Systems tab of the Errata Details page. Refer to Section 5.2.2, “Errata Details”...
Page 136 Chapter 6. Red Hat Network Website and left navigation bars. Click on the name of an entitled system, and click the Errata tab of the resulting System Details page. When the Relevant Errata list appears, click Select All then the Apply Errata button on the bottom right-hand corner of the page.
Page 137: Advanced Search
Below Fixes, the specific Bugzilla entries resolved by this erratum are listed. Clicking on any summary text opens that Bugzilla entry at http://bugzilla.redhat.com. Note that you must have a Bugzilla account to view the entry. Security updates list the specific vulnerability as tracked by http://cve.mitre.org. This information is listed below the CVEs label.
Page 138: Channels
Chapter 6. Red Hat Network Website • Erratum Advisory — The way Red Hat Security Response Team codifies Advisories, such RHBA-2007:0530 Searches can be by done year (such as 2007), by type of Advisory (RHBA for Bug fixes, RHEA for Enhancements, and RHSA for Security advisories), or full Advisory name, such as the example above.
Page 139 Software Channels and customize their package updates for their particular version, rather than upgrade their systems to a new update version that installs new software, hardware drivers, and features on production systems. For example, administrators can standardize their desktop systems to Red Hat Enterprise Linux 5.1 for x86, while managing servers on Red Hat Enterprise Linux 4.5 for AMD64 and EM64T.
Page 140 Chapter 6. Red Hat Network Website Figure 6.16. Relevant Channels 6.1.4. Retired Channels The Retired Channels page displays channels available to your organization that have reached their end-of-life dates. These channels do not receive updates. 6.1.5. All Channels The All Channels page can be retrieved by clicking All below Software Channels in the left navigation bar.
Page 141 Software Channels first tab displayed when you click on a channel. It displays essential information about the channel, such as summary, description, and architecture. —In addition, a Globally Subscribable checkbox can be seen by Satellite Administrators and Channel Administrators. This signifies the default behavior of every channel allowing any user to subscribe systems to it.
Page 142: Package Search
Chapter 6. Red Hat Network Website . The filter is case-insensitive. links 6.1.6.4. Software Channel Details # Subscribed Systems List of entitled systems subscribed to the channel. The list displays system names, base channels, and their levels of entitlement. Clicking on a system name takes you to its System Details page.
Page 143: Manage Software Channels
Manage Software Channels The Package Search page allows you to search through packages using various criteria: • Free Form — a general keyword search for users that are unsure of the details of particular package and its contents. • Name Only — Targeted search for users that need to find a specific packages and do not want to sift through more generalized search results.
Page 144 Chapter 6. Red Hat Network Website This screen lists the selections you made during the channel creation process. This page includes the Globally Subscribable checkbox that permits all users to subscribe to the channel. 6.3.1.2. Manage Software Channels # Channel Details # Managers This subtab allows you to select which users may alter or delete this channel.
Page 145: Configuration
Configuration This tab allows you to manage custom software packages owned by your organization. You may view a list of all custom software or view only those packages in a selected custom channel. To select the channel whose custom packages you wish to view, select the channel from the drop-down menu and click the View button.
Page 146: Configuration Channels
Chapter 6. Red Hat Network Website 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.
Page 147 Configuration Channels 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.
Page 148: Configuration Files
Chapter 6. Red Hat Network Website 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.
Page 149: Locally-Managed Files
Locally-Managed Files Note By default, the maximum file size for confiugration files is 128KB. If you need to change that value, find or create the following line in the /etc/rhn/rhn.conf file: web.maximum_config_file_size=128 Change the value from 128 to whatever limit you want in bytes. 7.4.1.
Page 150 Chapter 6. Red Hat Network Website In traditional file management, you would be required to upload and distribute each file separately, even if the distinction is nominal and the number of variations is in the hundreds or thousands. RHN addresses this by allowing the inclusion of macros, or variables, within the configuration files it manages for Provisioning-entitled systems.
Page 151: Systems
Systems deployed version resembles the following: hostname=test.example.domain.com ip_address=177.18.54.7 To capture custom system information, insert the key label into the custom information macro (rhn.system.custom_info). For instance, if you developed a key labeled "asset" you can add it to the custom information macro in a configuration file to have the value substituted on any system containing it.
Page 152: Schedule
Chapter 6. Red Hat Network Website Details # Configuration # List/Unsubscribe from Channels page. This allows you to unsubscribe from any channels you wish. 7.6.2. Target Systems This page displays the systems that are either not prepared for configuration file deployment or have not yet been subscribed to a configuration channel.
Page 153: Pending Actions
Failed Actions 8.1. Pending Actions As shown in Figure 6.18, “Schedule - Pending Actions”, the Pending Actions page is shown by default when you click Schedule in the top navigation bar. It displays actions that have not started or are in progress. Figure 6.18.
Page 154 Chapter 6. Red Hat Network Website In each page, each row in the list represents a single scheduled event or action that might affect multiple systems and involve various packages. The list contains several columns of information: • Select — 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.
Page 155: Users
Users — 8.5.1.4. Action Details # Failed Systems List of systems on which the action has been attempted and failed. The actions can be rescheduled here. Clicking a system name takes you to its System Details page. Refer to Section 4.2.9, “System Details” for more information.
Page 156 Chapter 6. Red Hat Network Website • 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.19.
Page 157 User List # Active — Satellite Administrators may not be deactivated until that role is removed from their account. Actions scheduled by a user prior to their deactivation remain in the action queue. For added flexibility, deactivated users may be reactivated by Satellite Administrators. User deletion from the web interface is available exclusively to RHN Satellite Server customers.
Page 158 Chapter 6. Red Hat Network Website with varying degrees of responsibility and access. This list describes the permissions of each and the differences between them: • User — Also known as a System Group User, this is the standard role associated with any newly created user.
Page 159 User List # Active — 9.1.1.2. User List # Active # User Details # System Groups — This tab displays a list of system groups that the user may administer. Satellite Administrators may use the check boxes to set this user's access permissions to each system group. Check or uncheck the box to the left of the system group and click the Update Permissions button to save the changes.
Page 160: User List # Deactivated
Chapter 6. Red Hat Network Website Administrators and Channel Administrators can subscribe to or manage any channel. 9.1.1.5. User List # Active # User Details # Preferences — This page allows you to configure whether the user receives email notifications, the number of entries displayed per list page, and the timezone of the user.
Page 161: User List # All
User List # All — This page lists all users who have been deactivated. To reactivate any of the users listed here, click the check box to the left of their name and click the Reactivate button followed by the Confirm button.
Page 162 Chapter 6. Red Hat Network Website • — Pending - The probe has been scheduled but has not yet run or is unable to run. • — OK - The probe is running successfully. The Probe Status page contains tabs for each of the possible states, as well as one that lists all probes.
Page 163: Notification
Notification — The probes whose data have not been received by RHN. This state is expected for a probe that has just been scheduled but has not yet run. If all probes go into a pending state, your monitoring infrastructure may be failing. 10.1.5.
Page 164 Chapter 6. Red Hat Network Website 10.2.1.1. Notification # Notification Filters # Active Filters This is the default screen for the Notification Filters tab. It lists all active filters available for your organization. Click the name of the filter to edit the properties of the filter. To create a notification filter, click the create new notification filter link in the upper right of the screen.
Page 165: Probe Suites
Probe Suites 13. R ecurring Frequency: How often the filter activates. Notification filters cannot be deleted. However, a filter may be canceled by setting the end date to some time in the past. (Note that the end date must be equal to or later than the start date, or the change fails.) Another method is to select a set of filters from the Active page and click the Expire Notification Filters button in the lower right.
Page 166 Chapter 6. Red Hat Network Website 5. 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.
Page 167: Scout Config Push
Scout Config Push — This action deletes all of the Probe Suites' probes from the system as well as all of the historical Time Series and Event Log data. This action is irreversible. To remove a system from the Probe Suite and delete all associated probes from the system: 1.
Page 168: Satellite Tools
Chapter 6. Red Hat Network Website click Update Config. 11. Satellite Tools This page allows RHN Satellite Server customers to manage the basic configuration of the Satellite, including creating and managing the Organizations feature of RHN Satellite Server. Only the Satellite Administrator can access the Satellite Tools page. 11.1.
Page 169 Satellite Tools # Organizations 11.1.1. Create New Organization Administrators can create a new organization within a Satellite and assign entitlements, groups, systems, and users to the group so that organizations can perform administrative tasks within their own network without possibly affecting the entire Satellite. Figure 6.21.
Page 170 Chapter 6. Red Hat Network Website d. Enter the First Name and Last Name of the organization administrator. 3. Click the Create Organization button to complete the process. Once the new organization is created, the Organizations page will display with the new organization listed.
Page 171 Satellite Tools # Organizations 11.1.2.2. Satellite Tools # Organizations # Details # Subscriptions The Subscriptions tab has two subtabs for managing the software channel and system entitlements for the organization. 11.1.2.2.1. Satellite Tools # Organizations # Details # Subscriptions # System Entitlements The System Entitlements subtab enables administrators to set the number of allocations to an organization per system entitlement.
Page 172: Satellite Tools # Satellite Configuration
Chapter 6. Red Hat Network Website Satellite, throughout all organizations, as well their usage. Click on a Entitlement Name for a more detailed view. The Details subtab for the software channel entitlement contains information about the software channel access granted when subscribed to the entitlement. The Organizations subtab allows Satellite administrators to adjust the number of software channels available to each organization.
Page 173 Satellite Tools # Satellite Configuration The Satellite Configuration # General Configuration page allows you to alter the most basic Satellite settings, such as the admin email address and whether Monitoring is enabled. 11.2.2. Satellite Tools # Satellite Configuration # Monitoring The RHN Satellite Configuration # Monitoring page allows you to configure the monitoring aspects of this Satellite.
Page 174: Help
Chapter 6. Red Hat Network Website minutes for the restart to finish. 12. Help The Help pages provide access to the full suite of documentation and support available to RHN users. Click Help in the Your RHN category to see a list of options available to you. 12.1.
Page 175: Client Configuration Guide
Channel Management Guide 12.8. Client Configuration Guide Documentation for setting up clients to connect to an RHN Proxy or Satellite server. 12.9. Channel Management Guide Documentation for the creation and maintenance of custom channels using RHN. 12.10. API Documentation for using the Red Hat Network Application Programming Interface (API) for creating tools and programs to automate common tasks via Red Hat Network.
Page 177: Monitoring
Chapter 7. Monitoring The Red Hat Network Monitoring entitlement allows you to perform a whole host of actions designed to keep your systems running properly and efficiently. With it, you can keep close watch on system resources, network services, databases, and both standard and custom applications.
Page 178: Probes Requiring The Daemon
Chapter 7. Monitoring To get the most out of your Monitoring entitlement, Red Hat suggests installing the Red Hat Network Monitoring Daemon on your client systems. Based upon OpenSSH, enables the rhnmd RHN Satellite Server to communicate securely with the client system to access internal processes and retrieve probe status.
Page 179: Installing The Red Hat Network Monitoring Daemon
Installing the Red Hat Network Monitoring • General::Remote Program • General::Remote Program with Data Note that all probes in the Linux group have this requirement. 2.2. Installing the Red Hat Network Monitoring Daemon Install the Red Hat Network Monitoring Daemon to prepare systems for monitoring with the probes identified in Section 2.1, “Probes requiring the daemon”.
Page 180: Installing The Ssh Key
Chapter 7. Monitoring rpm -qi openssh-server 2. 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. 3.
Page 181: Package
Daemon Note If valid entries already exist in , add the daemon key to the file authorized_keys rather than replacing the existing key. To do so, save the copied text to in the same directory and then run the following command: id_dsa.pub .ssh/ cat ~/.ssh/id_dsa.pub >>...
Page 182: Receiving Notifications
These notifications come in the form of brief text messages sent to either email or pager addresses. Here is an example of an email notification: Subject: CRITICAL: [hostname]: Satellite: Users at 1 From: "Monitoring Satellite Notification" (rogerthat01@redhat.com) Date: Mon, 6 Dec 2004 13:42:28 -0800 To: user@organization.com This is RHN Monitoring Satellite notification 01dc8hqw.
Page 183: Redirecting Notifications
Redirecting Notifications As you can see, the longer email notifications contain virtually everything you would need to know about the associated probe. In addition to the probe command, run time, system monitored, and state, the message contains the Send ID, which is a unique character string representing the precise message and probe.
Page 184: Filtering Notifications
Chapter 7. Monitoring Note You can halt or redirect almost all probe notifications by replying to a notification emails with a variation of the command . However, you ack suspend host cannot halt Satellite probe notifications by responding to a probe with or other redirect responses.
Page 185: Probes
Probes 6. You may now return to the Monitoring # Notifications page and delete the notification method. 5. Probes Now that the Red Hat Network Monitoring Daemon has been installed and notification methods have been created, you may begin installing probes on your Monitoring-entitled systems. If a system is entitled to Monitoring, a Probes tab appears within its System Details page.
Page 186: Establishing Thresholds
Chapter 7. Monitoring 8. 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 5.2, “Establishing Thresholds” for best practices regarding these thresholds. 9.
Page 187: Troubleshooting
The output will rhn-catalog nocpulse resemble: 2 ServiceProbe on example1.redhat.com (199.168.36.245): test 2 3 ServiceProbe on example2.redhat.com (199.168.36.173): rhel2.1 test 4 ServiceProbe on example3.redhat.com (199.168.36.174): SSH 5 ServiceProbe on example4.redhat.com (199.168.36.175): HTTP The probe ID is the first number, while the probe name (as entered in the RHN website) is the final entry on the line.
Page 188: Viewing The Output Of
Chapter 7. Monitoring Now that you have the ID, you use it with to examine the probe's output. Refer to rhn-runprobe Section 6.2, “Viewing the output of ” for instructions. rhn-runprobe 6.2. Viewing the output of rhn-runprobe Now that you have obtained the probe ID with , use it in conjunction with rhn-catalog to examine the complete output of the probe.
Page 189: Virtualization
Chapter 8. Virtualization In order to manage and provision your client systems, you must first synchronize content from RHN's central servers to your Satellite. RHN recommends that you sync at least the following channels: • Red Hat Network Tools for RHEL Server (v. 5 for 32-bit x86) — rhn-tools-rhel-i386-server-5 •...
Page 190: Kickstart Your Host System
Chapter 8. Virtualization run the 32-bit version of Red Hat Enterprise Linux. c. In the Kickstartable Tree field, select where $ARCH is the ks-rhel-$ARCH-server-5 architecture of your host system. d. Please select Para-Virtualized Host for the Virtualization Type field. e. Finally, click the Next button in the lower right of the screen to continue on to the next step.
Page 191 Kickstart Your Host System below, and follow the instructions for the scenario that applies best to you: 1.2.1. Your Host System Has Red Hat Enterprise Linux 4 or Earlier Installed In this case, register your host system to your Satellite and schedule the kickstart process via the Satellite's web interface.
Page 192 Chapter 8. Virtualization registered. If this is the case, open the kickstart profile by navigating to Systems # Kickstart # Profiles within the Satellite web interface, and clicking on the label for the host system's kickstart profile. Click on the Kickstart Detail # Operating System tab, and select items under the Base Channel and Available Trees selections that match the architecture of your host system.
Page 193 It is possible to use a flash-memory USB key to boot your system in order to kickstart it. Refer to the Red Hat Enterprise Linux System Administration Guide (available at http://www.redhat.com/docs/manuals/enterprise/) for tips on how to do this. Note that your host system's hardware must support boot via these devices.
Page 194 Chapter 8. Virtualization system for your virtual guest and registered it to you Satellite. 1.2.3. Your Host System Has Red Hat Enterprise Linux 5 Installed You should register your host system to your Satellite and check to see if the required packages are installed on the system.
Page 195: Setting Up Your Virtual Systems
Setting Up Your Virtual Systems You will then need to edit the configuration file to boot the new xen kernel /etc/grub.conf by default. To do this, select the lines in that pertain to the xen kernel from the grub.conf beginning of the line to the end of the line, copy the lines, delete them, and title...
Page 196 Chapter 8. Virtualization Kickstart Actions widget in the upper right corner. 3. The next page displayed is Step 1 of the kickstart profile creation process: a. Enter a label for the profile that will allow you to distinguish it from the other profiles. A good choice would be guest-system.
Page 197: Provision Your Guest Systems
Provision Your Guest Systems system you are provisioning, and click Next to finish creation of the profile. 6. This completes kickstart profile creation. After completing Step 3 you should be taken to the profile details. You may browse through the various tabs of the profile and modify the settings as you see fit, but this is not necessary as the default settings should work well for the majority of cases.
Page 198: Working With Your Virtual Systems
Chapter 8. Virtualization You may receive the following message from the page Kickstart Status during the guest's kickstart: The install process on the guest system has not communicated to RHN in the past n minutes. This may be due to a hung install process, or it may just be due to a slow install because of hardware constraints.
Page 199: Gaining Console Access Via The Host
Installing Software Via the Satellite Web 3.2. Gaining Console Access Via the Host 1. First you will need to connect to the host system and determine the ID number of the guest you would like to work with. Connect to the host system via and run the following command: xm list...
Page 200: Installing Software Via Yum From The Virtual System
Chapter 8. Virtualization To force the install to take place immediately, you may run the command on the rhn_check guest system. 3.4. Installing Software Via Yum From the Virtual System Your virtual system registered to your Satellite as part of the guest provisioning process, so you may simply use the command to install and update software.
Page 201 Interface 4. Finally, you must delete the RHN configuration files from the host system. To locate the RHN configuration file for guest1, run the following command: grep guest1 /etc/sysconfig/rhn/virt/*.xml Then delete the file indicated. For example: rm /etc/sysconfig/rhn/virt/14e5cfbf72342515236ad74b260c2f6b.xml 5. You have successfully deleted a guest system from your host system and from Satellite.
Page 203: Unix Support Guide
Chapter 9. UNIX Support Guide 1. Introduction This chapter documents the installation procedure for, and identifies differences in, Red Hat Network functionality when used to manage UNIX-based client systems. RHN offers UNIX support to help customers migrate from UNIX to Linux. Because of the limited scope of this task, the features offered for UNIX client management are not as comprehensive as those available for managing Red Hat Enterprise Linux systems.
Page 204: Differences In Functionality
Chapter 9. UNIX Support Guide • The Red Hat Network Configuration Client ( ), which executes all rhncfg-client configuration actions scheduled from the Satellite • The Red Hat Network Configuration Manager ( ), which allows command rhncfg-manager line administration of RHN configuration channels •...
Page 205: Satellite Server Preparation/Configuration
Satellite Server Preparation/Configuration exception of configuration file management • All Errata-related options, since the concept of Errata Updates is not understood in UNIX • Source files for packages In addition, answer files are not yet supported. Support for such files is planned for a future release.
Page 206 Chapter 9. UNIX Support Guide Figure 9.1. Enabling UNIX Support During Satellite Installation 2. After the Satellite has been installed: Enable UNIX support by configuring the Satellite after it has been installed. To do so, select Satellite Tools in the top menubar, then select Satellite Configuration in the left navigation bar.
Page 207: Client System Preparation
Client System Preparation 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. 3. Client System Preparation Before your UNIX-based client systems benefit from Red Hat Network, they must be prepared for connection: 1.
Page 208 Chapter 9. UNIX Support Guide • libgcc • openssl • zlib utility is provided by the SUNWgzip package and may be downloaded from gzip http://www.sunfreeware.com. On recent versions of Solaris, the necessary libraries are provided by the following natively installed packages: •...
Page 209 Download and Install Additional Packages add their location to the library search path. To do so, first check the current library search path": # crle -c /var/ld/ld.config Make a note of the current Default Library Path. Next, modify the path to also include the components shown below.
Page 210 3.1.5. Include RHN Packages in the PATH In order to make the RHN packages available at each login, you may wish to add them to your PATH. To do so, add these commands to your login script: # 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 To enable access to the RHN client command man pages, add them to your MANPATH.
Page 211: Deploying Client Ssl Certificates
# export MANPATH Alternatively, you can also access the man pages from the command line, with the following command: # man -M /opt/redhat/rhn/solaris/man <man page> Finally, add the Red Hat Libraries to your PATH as you did with libgcc openssl zlib crle -c /var/ld/ld.config -l <current library...
Page 212: Registration And Updates
Update Agent, which provides registration and update functionality. Follow these steps on each client system: 1. As root, change to the RHN configuration directory for the system. For Solaris, the full path is /opt/redhat/rhn/solaris/etc/sysconfig/rhn/ 2. Open the configuration file in a text editor.
Page 213: Obtaining Updates
Obtaining Updates This section describes the RHN registration process for UNIX systems. You must use the command to accomplish this; the use of activation keys for registering your systems rhnreg_ks 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.
Page 214 Chapter 9. UNIX Support Guide software channels designed to serve UNIX variants can be constructed almost exactly as the custom channels described in the RHN Channel Management Guide. The most significant difference is the architecture. When creating a UNIX software channel, ensure you select the base channel architecture appropriate for the systems to be served.
Page 215 Obtaining Updates # 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 Because no other directory was specified, the resulting .mpm files are written to the /tmp/ directory.
Page 216 It can be started from the rhnsd command line in this way: rhnsd --foreground --interval=240 The default location for rhnsd /opt/redhat/rhn/solaris/usr/sbin/rhnsd Below are the available options for on Solaris: rhnsd Option Description...
Page 217 Obtaining Updates Option Description Give this help list -h, --help Give this help list -u, --usage Print program version -V, --version Table 9.2. Options rhnsd 4.2.3. Updating From the Command Line Like the website, command line use of the Red Hat Update Agent is affected by the limitations of UNIX package management.
Page 218: Remote Commands
, and both must be located in the /etc/sysconfig/rhn/allowed-actions/ directory specific to your UNIX variant. For instance, in Solaris, issue this command to create the directory: mkdir -p /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script To create the requisite file in Solaris, issue this command: touch /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script/run 5.2. Issuing Commands You may schedule a remote command in a variety of ways: on an individual system, on multiple systems at once, and to accompany a package action.
Page 219 Issuing Commands identify a specific user, group, and timeout period, as well as the script itself. Select a date and time to begin attempting the command, and click the Schedule Remote Command link. Similarly, you may issue a remote command on multiple systems at once through the System Set Manager.
Page 221: Command Line Config Management Tools
Appendix A. Command Line Config Management Tools In addition to the options provided in the RHN website, Red Hat Network offers two command line tools for managing a system's configuration files: the Red Hat Network Configuration Client and the Red Hat Network Configuration Manager. There is a complementary Red Hat Network Actions Control tool that is used to enable and disable configuration management on client systems.
Page 222: Red Hat Network Configuration Client
Appendix A. Command Line Config Management Tools Option Description --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...
Page 223: Getting A Config File
Getting a Config File rhncfg-manager list config-channel-14 and observe the following output: Files in config channel 'config-channel-14' /etc/example-config.txt /etc/rhn/rhn.conf You may then wonder where the second version of went. The rank /etc/example-config.txt of the file in was higher than that of the same /etc/example-config.txt config-channel-17 file in...
Page 224: Differentiating Between Config Files
Appendix A. Command Line Config Management Tools Option Description --topdir=TOPDIR Make all file operations relative to this string. -h, --help Show help message and exit Table A.2. options rhncfg-client get 2.4. Differentiating between Config Files To view the differences between the config files deployed on the system and those stored by RHN, issue the command: rhncfg-client diff The output resembles the following:...
Page 225: Red Hat Network Configuration Manager
Red Hat Network Configuration Manager 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 Table A.3. options rhncfg-client verify 3.
Page 226: Creating A Config Channel
Appendix A. Command Line Config Management Tools You can see such a list of options for the add mode at Table A.4, “ rhncfg-manager add options”. 3.1. Creating a Config Channel To create a config channel for your organization, issue the command: rhncfg-manager create-channel channel-label If prompted for your RHN username and password, provide them.
Page 227: Differentiating Between Latest Config Files
Differentiating between Latest Config Files Option Description --delim-end=DELIM_END End delimiter for variable interpolation -h, --help show help message and exit Table A.4. options rhncfg-manager add Note By default, the maximum file size for confiugration files is 128KB. If you need to change that value, find or create the following line in the /etc/rhn/rhn.conf file:...
Page 228: Differentiating Between Various Versions
Appendix A. Command Line Config Management Tools Table A.5. options rhncfg-manager diff 3.4. Differentiating between Various Versions To compare different versions of a file across channels and revisions, use the flag to indicate which revision of the file should be compared and the flag to identify the two channels to be checked.
Page 229: Getting The Contents Of A File
Getting the Contents of a File Copying /tmp/dest_path/example-config.txt -> \ blah2/tmp/dest_path/example-config.txt The following table lists the options available for rhncfg-manager download-channel 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 Table A.7.
Page 230: Listing All Config Channels
Appendix A. Command Line Config Management Tools 3.8. Listing All Config Channels To list all of your organization's configuration channels, issue the command: rhncfg-manager list-channels The output resembles the following: Available config channels: example-channel example-channel2 example-channel3 config-channel-14 config-channel-17 Note that this does not list channels.
Page 231: Determining The Number Of File Revisions
Determining the Number of File Revisions Removing config channel example-channel Config channel example-channel removed 3.11. Determining the Number of File Revisions To find out how many revisions (revisions go from 1 to N where N is an integer greater than 0) of a file/path are in a channel, issue the following command: rhncfg-manager revisions channel-label /tmp/dest_path/example-config.txt The output resembles the following:...
Page 232: Uploading Multiple Files At Once
Appendix A. Command Line Config Management Tools 3.13. Uploading Multiple Files at Once To upload multiple files to a config channel from local disk at once, issue the command: rhncfg-manager upload-channel --topdir=topdirchannel-label The output resembles the following: Using config channel example-channel4 Uploading /tmp/ola_world.txt from blah4/tmp/ola_world.txt The following table lists the options available for rhncfg-manager upload-channel...
Page 233: Rhn Api Access
RHN website, then clicking API in the left navigation bar. Or you may go directly to: https://rhn.redhat.com/rpc/api/. Use this URL for your XMLRPC server and your browser. The RHN API is based upon XML-RPC, which allows distinct pieces of software on disparate systems to make remote procedure calls using XML over HTTP.
Page 234: Getting The Sgid
Appendix B. RHN API Access the end of the URL. It follows the "=" symbol, as part of a string that resembles the following: "details.pxt?cid=54". 5. Getting the sgid System groups also have their own IDs. This value, the , is a required parameter for the sgid method, for instance.
Page 235 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:...
Page 236 Appendix B. RHN API Access my $systemid = @$systems[0]->{id}; # This next call returns a list of packages present on this system. # syntax of this call is described at: http://$HOST/rpc/api/system/list_packages/ # This will probably be a pretty long list. my $packages = $client->call('system.list_packages', $session, $systemid);...
Page 237: Probes
Appendix C. Probes As described in Section 10, “Monitoring — ”, Monitoring-entitled systems can have probes applied to them that constantly confirm their health and full operability. This appendix lists the available probes broken down by command group, such as Apache. Many probes that monitor internal system aspects (such as the Linux::Disk Usage probe) rather than external aspects (such as the Network Services::SSH probe) require the installation of the Red Hat Network Monitoring Daemon (...
Page 238: Apache 1.3.X And 2.0.X
Appendix C. Probes 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.) While adding probes, select meaningful thresholds that, when crossed, notify you and your administrators of problems within your infrastructure.
Page 239: Apache::traffic
Apache::Traffic directive in the file of the Web server must be set to ExtendedStatus httpd.conf this probe to function properly. Field Value Application Protocol* http Port* Pathname* /server-status UserAgent* NOCpulse-ApacheUptime/1.0 Username Password Timeout* Critical Maximum Megabytes Transferred Per Child Warning Maximum Megabytes Transferred Per Child Critical Maximum Megabytes Transferred Per Slot Warning Maximum Megabytes Transferred Per Slot...
Page 240: Apache::uptime
Appendix C. Probes Field Value Password Timeout* 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) Table C.2.
Page 241: Bea Weblogic::execute Queue
BEA WebLogic::Execute Queue must be used to differentiate between the Administration Server receiving SNMP queries and the Managed Server undergoing the specified probe. If the host to be probed is the Administration Server, then the BEA Domain Admin Server parameter can be left blank, and both the SNMP queries and the probe will be sent to it only.
Page 242: Bea Weblogic::heap Free
Appendix C. Probes Field Value Critical Maximum Request Rate Warning Maximum Request Rate Table C.4. BEA WebLogic::Execute Queue settings 3.2. BEA WebLogic::Heap Free The BEA WebLogic::Heap Free probe collects the following metric: • Heap Free — The percentage of free heap space. This probe's transport protocol is User Datagram Protocol (UDP).
Page 243: Bea Weblogic::server State
BEA WebLogic::Server State This probe's transport protocol is User Datagram Protocol (UDP). Field Value SNMP Community String* public SNMP Port* SNMP Version* BEA Domain Admin Server BEA Server Name* myserver JDBC Pool Name* MyJDBC Connection Pool Critical Maximum Connections Warning Maximum Connections Critical Maximum Connection Rate Warning Maximum Connection Rate Critical Maximum Waiters...
Page 244: General
Appendix C. Probes • 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.
Page 245: General::remote Program With Data
General::Remote Program with Data Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the rhnmd monitored system to execute this probe. Field Value Command* OK Exit Status* Warning Exit Status* Critical Exit Status* Timeout Table C.9. General::Remote Program settings 4.2.
Page 246: General::snmp Check
Appendix C. Probes Field Value OK Exit Status* Warning Exit Status* Critical Exit Status* Timeout Table C.10. General::Remote Program with Data settings 4.3. General::SNMP Check The General::SNMP Check probe tests your SNMP server by specifying a single object identifier (OID) in dotted notation (such as ) and a threshold associated 1.3.6.1.2.1.1.1.0 with the return value.
Page 247: General::udp Check
General::UDP Check • Remote Service Latency — The time it takes in seconds for the TCP server to answer a connection request. The probe passes the string specified in the Send field upon making a connection. The probe anticipates a response from the system, which should include the substring specified in the Expect field.
Page 248: General::uptime (Snmp)
Appendix C. Probes 4.6. General::Uptime (SNMP) The General::Uptime (SNMP) probe records the time since the device was last started. It uses the SNMP object identifier (OID) to obtain this value. The only error status it will return is UNKNOWN. Requirements — SNMP must be running on the monitored system and access to the OID must be enabled to perform this probe.
Page 249: Linux::disk Io Throughput
Linux::Disk IO Throughput Table C.15. Linux::CPU Usage settings 5.2. Linux::Disk IO Throughput The Linux::Disk IO Throughput probe monitors a given disk and collects the following metric: • Read Rate — The amount of data that is read in kilobytes per second. •...
Page 250: Linux::inodes
Appendix C. Probes • Space Available — The amount of the file system in megabytes currently available. Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the rhnmd monitored system to execute this probe. Field Value File system* /dev/hda1...
Page 251: Linux::load
Linux::Load The Linux::Interface Traffic probe measures the amount of traffic into and out of the specified interface (such as eth0) and collects the following metrics: • Input Rate — The traffic in bytes per second going into the specified interface. •...
Page 252: Linux::memory Usage
Appendix C. Probes Field Value Critical CPU Load 15-minute average Warning CPU Load 15-minute average Table C.20. Linux::Load settings 5.7. Linux::Memory Usage The Linux::Memory Usage probe monitors the memory on a system and collects the following metric: • RAM Free — The amount of free random access memory (RAM) in megabytes on a system. You can also include the reclaimable memory in this metric by entering in the Include reclaimable memory field.
Page 253: Linux::process Count Total
Linux::Process Count Total reintroduced into memory, resuming execution where it left off. Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the rhnmd monitored system to execute this probe. Field Value Timeout* Critical Maximum Blocked Processes Warning Maximum Blocked Processes Critical Maximum Defunct Processes Warning Maximum Defunct Processes...
Page 254 Appendix C. Probes metrics: • CPU Usage — The CPU usage rate for a given process in milliseconds per second. This metric reports the column of output, which is the cumulative CPU time used by the time process. This makes the metric independent of probe interval, allows sane thresholds to be set, and generates usable graphs (i.e.
Page 255: Linux::process Running
Linux::Process Running Table C.24. Linux::Process Health settings 5.11. Linux::Process Running The Linux::Process Running probe verifies that the specified process is functioning properly. It counts either processes or process groups, depending on whether the Count process groups checkbox is selected. By default, the checkbox is selected, thereby indicating that the probe should count the number of process group leaders independent of the number of children.
Page 256: Linux::tcp Connections By State
Appendix C. Probes Field Value Timeout* Warning Minimum Swap Free Critical Minimum Swap Free Table C.26. Linux::Swap Usage settings 5.13. Linux::TCP Connections by State The Linux::TCP Connections by State probe identifies the total number of TCP connections, as well as the quantity of each in the following states: •...
Page 257: Linux::users
Linux::Users Field Value 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 Table C.27.
Page 258: Logagent
Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the rhnmd monitored system to execute this probe. Field Value Timeout* Warning Minimum Virtual Memory Free Critical Minimum Virtual Memory Free Table C.29. Linux::Virtual Memory settings 6.
Page 259: Logagent::log Size
LogAgent::Log Size [^] 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 Do not include single quotation marks (') within the expression. Doing so causes to fail silently and the probe to time out.
Page 260: Mysql 3.23 - 3.33
Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the rhnmd monitored system to execute this probe. For this probe to run, the user must be nocpulse granted read access to your log files. Field Value Log file*...
Page 261: Mysql::opened Tables
MySQL::Opened Tables Field Value Username* Password MySQL Port 3306 Database* mysql Timeout Table C.32. MySQL::Database Accessibility settings 7.2. MySQL::Opened Tables The MySQL::Opened Tables probe monitors the MySQL server and collects the following metric: • Opened Tables — The tables that have been opened since the server was started. Field Value Username...
Page 262: Mysql::query Rate
Appendix C. Probes Field Value MySQL Port* 3306 Timeout Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects Critical Minimum Open Objects Table C.34. MySQL::Open Tables settings 7.4. MySQL::Query Rate The MySQL::Query Rate probe monitors the MySQL server and collects the following metric: •...
Page 263: Network Services
Network Services Field Value Password MySQL Port* 3306 Timeout Critical Maximum Threads Running Warning Maximum Threads Running Warning Minimum Threads Running Critical Minimum Threads Running Table C.36. MySQL::Threads Running settings 8. Network Services The probes in this section monitor various services integral to a functioning network. When applying them, ensure that their timed thresholds do not exceed the amount of time allotted to the timeout period.
Page 264: Network Services::imap Mail
Appendix C. Probes The Network Services::FTP probe uses network sockets to test FTP port availability. It collects the following metric: • Remote Service Latency — The time it takes in seconds for the FTP server to answer a connection request. This probe supports authentication.
Page 265: Network Services::mail Transfer (Smtp)
Network Services::Mail Transfer (SMTP) Field Value Warning Maximum Remote Service Latency Table C.39. Network Services::IMAP Mail settings 8.4. Network Services::Mail Transfer (SMTP) The Network Services::Mail Transfer (SMTP) probe determines if it can connect to the SMTP port on the system. Specifying an optional port number overrides the default port 25. It collects the following metric: •...
Page 266: Network Services::pop Mail
Appendix C. Probes Note that this probe conducts the from an RHN Server and not the monitored system. ping 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.
Page 267: Network Services::remote Ping
Network Services::RPCService 8.7. Network Services::Remote Ping The Network Services::Remote Ping probe determines if the monitored system can ping specified IP address. It also monitors the packet loss and compares the round trip average against the Warning and Critical threshold levels. The required Packets to send value allows you to control how many ICMP ECHO packets are sent to the address.
Page 268: Network Services::secure Web Server (Https)
Appendix C. Probes the RPC network by declaring a program ID and a program name. NFS is an example of a service that works via the RPC mechanism. Client programs that wish to use the resources of RPC server programs do so by asking the machine on which the server program resides to provide access to RPC functions within the RPC program number or program name.
Page 269: Network Services::ssh
Network Services::SSH Field Value Username Password Timeout* HTTPS Port* Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C.45. Network Services::Secure Web Server (HTTPS) settings 8.10. Network Services::SSH The Network Services::SSH probe determines the availability of SSH on the specified port and collects the following metric: •...
Page 270: Oracle 8I And 9I
Appendix C. Probes specified URL. If no URL is specified, the probe will fetch the root document. The probe looks for a HTTP/1. message from the system, unless you alter that value. Specifying another port number will override the default port of 80. Unlike most other probes, this probe will return a CRITICAL status if it cannot contact the system within the timeout period.
Page 271: Oracle::active Sessions
Oracle::Active Sessions representation, de-emphasizing anomalies that can occur at shorter time intervals. This applies to following probes: Buffer Cache, Data Dictionary Cache, Disk Sort Ratio, Library Cache, and Redo Log. For CRITICAL and WARNING thresholds based upon time to work as intended, their values cannot exceed the amount of time allotted to the timeout period.
Page 272: Oracle::blocking Sessions
Appendix C. Probes Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* Table C.49. Oracle::Availability settings 9.3. Oracle::Blocking Sessions The Oracle::Blocking Sessions probe monitors an Oracle instance and collects the following metric: • 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.
Page 273: Oracle::client Connectivity
Oracle::Client Connectivity • 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.
Page 274: Oracle::data Dictionary Cache
Appendix C. Probes Table C.52. Oracle::Client Connectivity settings 9.6. Oracle::Data Dictionary Cache The Oracle::Data Dictionary Cache probe computes the Data Dictionary Cache Hit Ratio so as to optimize the SHARED_POOL_SIZE in . It collects the following metrics: init.ora • Data Dictionary Hit Ratio — The ratio of cache hits to cache lookup attempts in the data dictionary cache.
Page 275: Oracle::idle Sessions
Oracle::Idle Sessions Field Value Oracle Password* Oracle Port* 1521 Timeout* Critical Maximum Disk Sort Ratio Warning Maximum Disk Sort Ratio Table C.54. Oracle::Disk Sort Ratio settings 9.8. Oracle::Idle Sessions The Oracle::Idle Sessions probe monitors an Oracle instance and collects the following metric: •...
Page 276: Oracle::library Cache
Appendix C. Probes Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Index Owner* Index Name* Timeout* Critical Maximum of Allocated Extents Warning Maximum of Allocated Extents Critical Maximum of Available Extents Warning Maximum of Available Extents Table C.56. Oracle::Index Extents settings 9.10.
Page 277: Oracle::locks
Oracle::Redo Log 9.11. Oracle::Locks The Oracle::Locks probe monitors an Oracle database instance and collects the following metric: • Active Locks — The current number of active locks as determined by the value in the v$locks table. Database administrators should be aware of high numbers of locks present in a database instance.
Page 278: Oracle::table Extents
Appendix C. Probes Field Value Oracle Password* Oracle Port* 1521 Timeout* Critical Maximum Redo Log Space Request Rate Warning Maximum Redo Log Space Request Rate Critical Maximum Redo Buffer Allocation Retry Rate Warning Maximum Redo Buffer Allocation Retry Rate Table C.59. Oracle::Redo Log settings 9.13.
Page 279: Oracle::tablespace Usage
Oracle::Tablespace Usage Field Value Table Name* Timeout* Critical Maximum Allocated Extents Warning Maximum Allocated Extents Critical Maximum Available Extents Warning Maximum Available Extents Table C.60. Oracle::Table Extents settings 9.14. Oracle::Tablespace Usage The Oracle::Tablespace Usage probe monitors an Oracle database instance and collects the following metric: •...
Page 280: Rhn Satellite Server
Appendix C. Probes The Oracle::TNS Ping probe determines if an Oracle listener is alive and collects the following metric: • Remote Service Latency — The time it takes in seconds for the Oracle server to answer a connection request. Field Value TNS Listener Port* 1521...
Page 281: Rhn Satellite Server::execution Time
RHN Satellite Server::Execution Time Table C.63. RHN Satellite Server::Disk Space settings 10.2. RHN Satellite Server::Execution Time The RHN Satellite Server::Execution Time probe monitors the execution time for probes run from a Satellite and collects the following metric: • Probe Execution Time Average — The seconds required to fully execute a probe. Field Value Critical Maximum Probe Execution Time Average...
Page 282: Rhn Satellite Server::load
Appendix C. Probes second. When a Satellite is overloaded (because it has too many probes with respect to their average execution time), the number goes up. Field Value Critical Maximum Probe Latency Average Warning Maximum Probe Latency Average Table C.66. RHN Satellite Server::Latency settings 10.5.
Page 283: Rhn Satellite Server::process Counts
RHN Satellite Server::Processes 10.7. RHN Satellite Server::Process Counts The RHN Satellite Server::Process Counts probe monitors the number of processes on a Satellite and collects the following metrics: • Blocked — The number of processes that have been switched to the waiting queue and waiting state.
Page 284: Rhn Satellite Server::process Health
Appendix C. Probes Field Value Critical Maximum Processes Warning Maximum Processes Table C.70. RHN Satellite Server::Processes settings 10.9. RHN Satellite Server::Process Health The RHN Satellite Server::Process Health probe monitors customer-specified processes and collects the following metrics: • CPU Usage — The CPU usage percent for a given process. •...
Page 285: Rhn Satellite Server::process Running
RHN Satellite Server::Process Running Field Value Critical Maximum Virtual Memory Used Warning Maximum Virtual Memory Used Table C.71. RHN Satellite Server::Process Health settings 10.10. RHN Satellite Server::Process Running The RHN Satellite Server::Process Running probe verifies that the specified process is running. Specify the process by its command name or process ID.
Page 286 Appendix C. Probes Field Value Warning Maximum Users Table C.74. RHN Satellite Server::Users settings...
Page 287: Glossary
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.
Page 288 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.
Page 289 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.
Page 290 Glossary 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. Registered System A system that is registered with Red Hat Network.
Page 291 Security Alert Errata Alert that pertains to system security. Sibling Siblings are virtual guests running on the same host. Virtual guests that run on separate hosts are not siblings. 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.
Page 292 Glossary systems. The virtual host may also be referred to as domain 0, or dom0. Yellowdog Updater Modified The Yellowdog Updater Modified is the Red Hat Network client (yum) application ( ) that allows users to retrieve and install new or updated packages for the client system on which the application is run.
Page 293: Index
child, 124 Index errata, 127 list of, 124 packages, 127 relevant, 125 retired, 126 account Channels and Packages deactivate, 71 Channel List, 124 action child channel, 124 completed systems, 140 client applications details, 140 obtaining, 6 failed systems, 141 redirecting, 197 in progress systems, 140 client systems activation key, 103...
Page 294 Index Errata, 119 Linux Advanced Search, 123 CPU Usage, 234 All Errata, 121 Disk IO Throughput, 235 apply applicable, 85 Disk Usage, 235 Relevant Errata, 120 Inodes, 236 Errata Alert Icons Interface Traffic, 236 explanation of, 65 Load, 237 Errata notifications Memory Usage, 238 automatic updates, 5 probes...
Page 295 Status, 147 Availability, 257 Unknown, 148 Blocking Sessions, 258 Warning, 148 Buffer Cache, 258 monitoring Client Connectivity, 259 list of probes, 223 Data Dictionary Cache, 260 MySQL, 167 Disk Sort Ratio, 260 Database Accessibility, 246 Idle Sessions, 261 Open Tables, 247 Index Extents, 261 Opened Tables, 247 Library Cache, 262...
Page 296 Index Linux Library Cache, 262 CPU Usage, 234 Locks, 263 Disk IO Throughput, 235 Redo Log, 263 Disk Usage, 235 Table Extents, 264 Inodes, 236 Tablespace Usage, 265 Interface Traffic, 236 TNS Ping, 265 Load, 237 RHN Satellite Server Memory Usage, 238 Disk Space, 266 Process Count Total, 239 Execution Time, 267...
Page 297 Red Hat Network packages with Red Hat Update Agent, 31 comparison, 7 Red Hat Network Registration Client (rhn)_register) initial description, 2 quality assurance Red Hat packages overview, 5 for UNIX, 193 Quick Search installing, 193 explanation of, 65 Red Hat Update Agent, 44 Command Line Arguments, 25 configuration, 30 reactivating...
Page 298 Index with a proxy server, 46 security with activation key, 103 overview, 5 remote commands service levels enabling, 204 Management, 3 issuing, 204 Monitoring, 4 RHN Satellite Server Provisioning, 4 Disk Space, 266 Update, 2 Execution Time, 267 Software Interface Traffic, 267 Channel List Latency, 267 Channel Details, 126...
Page 299 System Set Manager, 96 WebLogic systems Execute Queue, 227 deleting, 79 Heap Free, 228 entitling, 72 JDBC Connection Pool, 228 overview, 74 probes, 226 searching, 103 Server State, 229 viewing a list of, 74 Servlet, 229 viewing details for, 78 website, 61 Systems activation keys, 103...
Page 300 Index Your Preferences, 71...

Red Hat NETWORK SATELLITE 5.1.0 Reference Manual

Red hat Update Agent

Starting the Red hat Update Agent

Red hat Network Alert Notification Tool

Red hat Network Registration Client

Configuring the Red hat Network Registration Client

Starting the Red hat Network Registration Client

Red hat Network Satellite

Red hat Network Satellite

Red hat Network Actions Control

Red hat Network Configuration Client

Red hat Network Configuration Manager

Red hat Network Satellite

Quick Links

Troubleshooting

Related Manuals for Red Hat NETWORK SATELLITE 5.1.0

Summary of Contents for Red Hat NETWORK SATELLITE 5.1.0