1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. NETWORK 3.7 -
  6. Reference manual

Red Hat NETWORK 3.7 Reference Manual

Hide thumbs Also See for NETWORK 3.7:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Manual
Red Hat Network 3.7
Reference Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETWORK 3.7 and is the answer not in the manual?

Questions and answers

Related Manuals for Red Hat NETWORK 3.7

Summary of Contents for Red Hat NETWORK 3.7

  • Page 1 Red Hat Network 3.7 Reference Guide...
  • Page 2 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 3: Table Of Contents

    Table of Contents Introduction to the Guide........................i 1. Document Conventions......................i 2. More to Come ........................iv 2.1. Send in Your Feedback ..................iv 1. Red Hat Network Overview ......................1 1.1. Demo..........................2 1.2. Update ..........................2 1.3. Management........................2 1.4.
  • Page 4 6. Red Hat Network Website......................57 6.1. Navigation........................57 6.1.1. Entitlement Views ..................... 57 6.1.2. Categories and Pages ..................57 6.1.3. Errata Alert Icons....................59 6.1.4. Quick Search..................... 59 6.1.5. Systems Selected....................59 6.1.6. Lists........................59 6.2. Logging into the RHN Website..................60 6.3.
  • Page 5 7. Monitoring ........................... 119 7.1. Prerequisites........................119 7.2. Red Hat Network Monitoring Daemon ( ) ............119 rhnmd 7.2.1. Probes requiring the daemon ................120 7.2.2. Installing the Red Hat Network Monitoring Daemon........120 7.2.3. Configuring SSH..................... 121 7.2.4. Installing the SSH key ..................121 7.3.
  • Page 6 C. Probes ............................141 C.1. Probe guidelines ......................141 C.2. Apache 1.3.x and 2.0.x....................141 C.2.1. Apache::Processes..................142 C.2.2. Apache::Traffic....................142 C.2.3. Apache::Uptime ..................... 143 C.3. BEA WebLogic 6.x and higher ..................143 C.3.1. BEA WebLogic::Execute Queue..............144 C.3.2. BEA WebLogic::Heap Free ................144 C.3.3.
  • Page 7 C.9. Oracle 8i and 9i ......................169 C.9.1. Oracle::Active Sessions.................. 169 C.9.2. Oracle::Availability ..................170 C.9.3. Oracle::Blocking Sessions................170 C.9.4. Oracle::Buffer Cache..................171 C.9.5. Oracle::Client Connectivity................171 C.9.6. Oracle::Data Dictionary Cache ..............172 C.9.7. Oracle::Disk Sort Ratio .................. 172 C.9.8. Oracle::Idle Sessions ..................173 C.9.9.

  • Page 9: Introduction To The Guide

    Red Hat Update Agent, which has registration functionality built in. Refer to Chapter 2 Red Hat Update Agent for instructions. For an overview of Red Hat Network offerings, please review the descriptions available at http://www.redhat.com/software/rhn/ . 1. Document Conventions When you read this manual, certain words are represented in different fonts, typefaces, sizes, and weights.
  • Page 10 Introduction to the Guide file in your home directory contains bash shell definitions and aliases for your own .bashrc use. file contains information about different system devices and file systems. /etc/fstab Install the RPM if you want to use a Web server log file analysis program. webalizer application This style indicates that the program is an end-user application (as opposed to system software).

  • Page 11: User Input

    Introduction to the Guide The output returned in response to the command (in this case, the contents of the directory) is shown in this style. prompt A prompt, which is a computer’s way of signifying that it is ready for you to input something, is shown in this style.

  • Page 12: More To Come

    The Red Hat Network Reference Guide is constantly expanding as new Red Hat Network features and service plans are launched. HTML and PDF versions of this and other manuals are available within the Help section of the RHN website and at http://www.redhat.com/docs/. Note Although this manual reflects the most current information possible, read the RHN Release Notes for...

  • Page 13: Red Hat Network Overview

    Chapter 1. Red Hat Network Overview Have you ever read about a new version of a software package and wanted to install it but could not find it? Have you ever tried to find an RPM through an Internet search engine or an RPM repository and been linked to a site that you have never heard of? Have you ever tried to find an RPM but instead found only the source files that you had to compile yourself?

  • Page 14: Demo

    Many Red Hat Network terms are used throughout this manual. As you read the Red Hat Network Reference Guide, refer to the Glossary as necessary for an explanation of common terms. For a comparison chart of RHN service levels, refer to http://www.redhat.com/software/rhn/table/. 1.1. Demo The RHN Demo service level is the complimentary service level.

  • Page 15: Provisioning

    To create an account that can be used to entitle systems to RHN Management, go to https://rhn.redhat.com/ and click on the Create Account link under the Sign In fields. On the Sign Up for Red Hat Network page, click Create a new Corporate Login. After creating a corporate account, you may add users within your organization to it.

  • Page 16: Monitoring

    All transactions made between you and Red Hat Network are encrypted, and all RPM packages are signed with Red Hat’s GNU Privacy Guard (GPG) signature to ensure authenticity. Red Hat Network incorporates the following security measures: 1. Your System Profile available at http://rhn.redhat.com is accessible only with an RHN-verified username and password.

  • Page 17: Before You Begin

    Chapter 1. Red Hat Network Overview 2. A Digital Certificate is written to the client system after registration and is used to authenticate the system during each transaction between the client and Red Hat Network. The file is only readable by the root user on the client system. 3.
  • Page 18 Chapter 1. Red Hat Network Overview Package Name Description Provides the GNOME interface (graphical version) for the Red Hat rhn_register-gnome Network Registration Client; runs if the X Window System is available Provides the Red Hat Update Agent command line version and the Red up2date Hat Network Daemon Provides the GNOME interface (graphical version) for the Red Hat...

  • Page 19: 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 pack- ages from Red Hat.
  • Page 20 Chapter 2. Red Hat Update Agent If you choose the last option and start the application from a shell prompt, you can specify the options in Table 2-1 to the Red Hat Update Agent. To view these options, type the command up2date --help For example, use the following command to specify the directory in which to download the updated...

  • Page 21: Registration

    Chapter 2. Red Hat Update Agent Figure 2-1. Configure Proxy Server The second dialog box to appear will prompt you to install the Red Hat GPG key, as shown in Figure 2-2. This key is used to verify the packages you download for security purposes. Click Yes to install the key, and you will not see this message again.
  • Page 22 Chapter 2. Red Hat Update Agent Important If your username is part of a larger organizational account, you should take caution when regis- tering your systems. By default, all systems registered with the Red Hat Update Agent end up in the Ungrouped section of systems visible only to Organization Administrators.

  • Page 23: Registering A User Account

    Red Hat software packages. Note If you are already a member of redhat.com, you can and should use the same username and pass- word. However, you will still need to continue with the registration process to create your System Profile.
  • Page 24 Chapter 2. Red Hat Update Agent Is not case-sensitive, thereby eliminating the possibility of duplicate usernames differing only by • capitalization In addition, the following restrictions apply to both your username and password: Must be at least four characters long •...
  • Page 25 Note Unlike other details, your company name can be changed only through Red Hat Customer Service, so enter it carefully. If you do need to have your company name changed, send your request to customerservice@redhat.com.

  • Page 26: Registering A System Profile

    Chapter 2. Red Hat Update Agent Figure 2-7. Register a User Account Once satsfied with the information supplied, click Forward to continue. 2.2.2. Registering a System Profile Now that you have a user account, you can create a System Profile that consists of hardware and software information about your Red Hat Enterprise Linux system.
  • Page 27 Chapter 2. Red Hat Update Agent Disk sizes • Mount points • The next step is choosing a profile name for your system as shown in Figure 2-8. The default value is the hostname for the system. You may modify this to be a more descriptive string, such as Email Server for Support Team, if you find it more helpful.
  • Page 28 Chapter 2. Red Hat Update Agent you must include packages in your profile to have RHN send you Errata regarding them. You should also note if you use an older version of a package and deselect it from the list, it will not be replaced with a newer version.
  • Page 29 Chapter 2. Red Hat Update Agent 2.2.2.2.2. Choosing RPM Packages to Exclude from the System Profile By default, all RPM packages in your RPM database are included in your System Profile to be updated by Red Hat Network. To exclude a package, uncheck the package from the list by clicking the check- box beside the package name.

  • Page 30: Setup And Use

    Chapter 2. Red Hat Update Agent Figure 2-12. Finished Collecting Information for System Profile Figure 2-13 shows the progress bar you will see while your profile is being sent. This process may take some time depending on your connection speed. Figure 2-13.

  • Page 31: Choosing A Software Channel

    Chapter 2. Red Hat Update Agent Before you proceed, however, you should consider ensuring you have the latest version of the Red Hat Update Agent, as development on it is continuous. This task is as simple as running the tool against its own package.
  • Page 32 Chapter 2. Red Hat Update Agent Figure 2-15. Retrieve Update Information While you see this dialog box, the Red Hat Update Agent uses your unique Digital Certificate ) to determine if there are any updated packages available for /etc/sysconfig/rhn/systemid your system. If there are no updated packages available for your system, the dialog box in Figure 2-16 appears.
  • Page 33 Chapter 2. Red Hat Update Agent Figure 2-17. Packages Flagged to be Skipped If you want to view the advisory for the RPM Alert, click the View Advisory button. This will display what type of Errata Alert it is and what problem(s) it addresses as shown in Figure 2-18. Click OK to close the advisory.
  • Page 34 Chapter 2. Red Hat Update Agent Figure 2-18. View Advisory The Available Package Updates screen is the next to appear. If your system is not up-to-date, your customized list of available updated packages is displayed as shown in Figure 2-19.
  • Page 35 Chapter 2. Red Hat Update Agent Figure 2-19. List of Available Updates By default, no packages are selected for download. To select a package for download (and installation, if you chose that option), click its checkbox. To select all the packages listed, click the checkbox next to Select all packages.

  • Page 36: Installing Updated Packages

    Chapter 2. Red Hat Update Agent Figure 2-21. Retrieval Finished 2.3.3. Installing Updated Packages After downloading the packages through the Red Hat Update Agent, they must be installed. If you chose not to have the packages installed via the Red Hat Update Agent, skip to Section 2.3.5.2 Manual Package Installation for further instructions.

  • Page 37: Update Agent Finished

    Chapter 2. Red Hat Update Agent Figure 2-22. Installation Finished 2.3.4. Update Agent Finished When the Red Hat Update Agent has finished downloading the desired packages (and installing them if you chose the install option), you will see the screen in Figure 2-23. Click Finish to exit the Red Hat Update Agent.

  • Page 38: Command Line Version

    Chapter 2. Red Hat Update Agent Figure 2-23. Update Agent Finished 2.3.5. Command Line Version If you are not running X, you can still run the Red Hat Update Agent from a virtual console or remote terminal. If you are running X but want to use the command line version, you can force it not to display the graphical interface with the following command: up2date --nox The command line version of the Red Hat Update Agent allows you to perform advanced functions...
  • Page 39 Chapter 2. Red Hat Update Agent Argument Description Force to install this architecture of the package. Not --arch=architecture up2date valid with , or --update --list --dry-run Specify which channels to update from using channel labels. --channel=channel Configure Red Hat Update Agent options. Refer to Section 2.4 --configure Configuration for detailed instructions.
  • Page 40 Chapter 2. Red Hat Update Agent Argument Description Specify a username to use with an authenticated HTTP proxy. --proxyUser=proxy user Register (or re-register) this system with RHN. Refer to Section --register 2.2 Registration for detailed instructions. Specify an alternate server from which to retrieve packages. --serverUrl=server URL List all packages available for download.
  • Page 41 (as root): /usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY If you need 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 1024D/650D5882 2001-11-21 Red Hat, Inc. (Security Response Team)

  • Page 42: Configuration

    Chapter 2. Red Hat Update Agent =yOVZ -----END PGP PUBLIC KEY BLOCK----- Save the text file and import it into your keyring using the method applicable for your version of RPM. 2.3.5.2. Manual Package Installation If you chose to download the software updates with the Red Hat Update Agent or from the RHN website, you must install them manually using RPM.
  • Page 43 Chapter 2. Red Hat Update Agent 2.4.1. Using the Red Hat Update Agent Configuration Tool You must be root to run the Red Hat Update Agent Configuration Tool. If you start the Red Hat Update Agent Configuration Tool as a standard user, you will be prompted to enter the root password before proceeding.
  • Page 44 Chapter 2. Red Hat Update Agent Figure 2-25. Retrieval/Installation Settings The following package retrieval options can be selected (see Figure 2-25): Do not install packages after retrieval — download selected RPM packages to desired directory • and ignore the installation preferences Do not upgrade packages when local configuration file has been modified —...

  • Page 45: Command Line Version

    Chapter 2. Red Hat Update Agent 2.4.1.3. Package Exceptions Settings The Package Exceptions tab allows you to define which packages to exclude from the list of updated RPM packages according to the package name or file name (see Figure 2-26). To define a set of packages to be excluded according to the package name, enter a character string including wild cards (*) in the Add new text field under in the Package Names to Skip section.

  • Page 46: Registering With Activation Keys

    Chapter 2. Red Hat Update Agent depslist networkSetup retrieveOnly enableRollbacks pkgSkipList [’kernel*’] storageDir /var/spool/up2date adminAddress [’root@localhost’] noBootLoader 10. serverURL https://xmlrpc.rhn.redhat.com/XMLRPC 11. fileSkipList 12. sslCACert /usr/share/rhn/RHNS-CA-CERT 13. noReplaceConfig 14. useNoSSLForPackage No 15. systemIdPath /etc/sysconfig/rhn/systemid 16. enableProxyAuth 17. retrieveSource 18. versionOverride 19. headerFetchCount 20. networkRetries 21.
  • Page 47 Chapter 2. Red Hat Update Agent Thus, channel and group subscriptions can be automated along with registration, thereby bypassing entitlement and registration through either the Red Hat Network Registration Client or the Red Hat Update Agent, both of which offer the activation keys utility as part of their packages.
  • Page 48 Chapter 2. Red Hat Update Agent 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 will be chosen. For instance, you may not take a Red Hat Enterprise Linux 2.1 system and subscribe it to the Red Hat Enterprise Linux 3 channel.

  • Page 49: Red Hat Network Daemon

    Chapter 3. Red Hat Network Daemon The Red Hat Network Daemon ( ) periodically connects to Red Hat Network to check for up- rhnsd dates and notifications. The daemon, which runs in the background, is typically started from the ini- tialization scripts in /etc/init.d/rhnsd /etc/rc.d/init.d/rhnsd...

  • Page 50: Troubleshooting

    RHN via SSL (port 443). You may test this by running the • following command from a shell prompt: telnet xmlrpc.rhn.redhat.com 443 the Red Hat Network Daemon is activated and running. You may ensure this by running the follow- •...

  • Page 51: 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 52: Notification Icons

    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 connec- tions, on the Proxy Configuration screen, type your proxy server in the text field with the for- mat HOST:PORT.

  • Page 53: Viewing Updates

    Chapter 4. Red Hat Network Alert Notification Tool If you see the icon, it is highly recommended that you apply the updates. Refer to Section 4.4 Applying Updates for information on applying updates. If you have scheduled updates to be installed, you can watch the applet icon to determine when updates are applied.
  • Page 54 Chapter 4. Red Hat Network Alert Notification Tool...

  • Page 55: Red Hat Network Registration Client

    Chapter 5. Red Hat Network Registration Client Before you begin using Red Hat Network, you need to 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 this separate Red Hat Network Registration Client before starting the Red Hat Update Agent.

  • Page 56: Starting The Red Hat Network Registration Client

    Chapter 5. Red Hat Network Registration Client It has more configuration options than the graphical version. You will be presented with a list of options and their current values: enableProxyAuth noSSLServerURL http://xmlrpc.rhn.redhat.com/XMLRPC oemInfoFile /etc/sysconfig/rhn/oeminfo enableProxy networkSetup httpProxy proxyUser serverURL https://xmlrpc.rhn.redhat.com/XMLRPC...
  • Page 57 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 The opening screen for the Red Hat Network Registration Client gives you a brief overview of the services available and the steps required to register (see Figure 5-4).
  • Page 58 Chapter 5. Red Hat Network Registration Client Figure 5-4. Welcome Screen Red Hat is committed to protecting your privacy (see Figure 5-5). The information gathered during the Red Hat Network registration process is used to create a System Profile. The System Profile is essential if you wish to receive update notifications about your system.

  • Page 59: Registering A User Account

    Chapter 5. Red Hat Network Registration Client Figure 5-5. Red Hat Privacy Statement 5.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, you must choose a username and password.
  • Page 60 Chapter 5. Red Hat Network Registration Client Note If you are already a member of redhat.com, you can use the same user name and password. How- ever, you will still need to continue with the registration process to create your System Profile.

  • Page 61: Registering A System Profile

    Chapter 5. Red Hat Network Registration Client Most users can leave the Org Info section blank. If you have an existing organization account, work with your Organization Administrator to ensure your system is added to that account. This will re- quire entering your organization’s ID and password in the provided text fields.

  • Page 62: Software System Profile

    Chapter 5. Red Hat Network Registration Client Figure 5-8. System Profile - Hardware 5.4.2. Software System Profile The software System Profile consists of a list of RPM packages for which you wish to receive notifi- cations. The Red Hat Network Registration Client shows you 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 63 Chapter 5. Red Hat Network Registration Client Figure 5-10. RPM Package Information 5.4.2.2. Choosing RPM Packages to Exclude from the System Profile By default, all RPM packages in your RPM database are included in your System Profile to be up- dated by Red Hat Network.

  • Page 64: Finishing Registration

    Chapter 5. Red Hat Network Registration Client Figure 5-11. Choose which RPM Packages to Exclude from System Profile 5.5. Finishing Registration As seen in Figure 5-12, the last step of registration is to confirm that you want to send your System Profile to the Red Hat Network.
  • Page 65 Chapter 5. Red Hat Network Registration Client Figure 5-12. Finished Collecting Information for System Profile Figure 5-13 shows the progress bar you will see while your profile is being sent. This process may take some time depending on your connection speed. Figure 5-13.

  • Page 66: Entitling Your System

    Demo entitlement after creating an account by registering a system for RHN or creating a redhat.com account. 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 67 Chapter 5. Red Hat Network Registration Client 5.7. Text Mode RHN Registration Client If you are not running the X Window System, the Red Hat Network Registration Client starts in text mode. You can force the Red Hat Network Registration Client to run in text mode with the command: rhn_register --nox The screens for the text mode Red Hat Network Registration Client are almost identical to the screens for the graphical Red Hat Network Registration Client.
  • Page 68 Chapter 5. Red Hat Network Registration Client...

  • Page 69: 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 70 Chapter 6. Red Hat Network Website Your Preferences — Indicate if you wish to receive email notifications about Errata Alerts for • your systems, set how many items are displayed at one time for lists such as system lists and system group lists, set your time zone, and identify your contact options.

  • Page 71: Errata Alert Icons

    Chapter 6. Red Hat Network Website Pending Actions — List scheduled actions that have not been completed. • Failed Actions — List scheduled actions that have failed. • Completed Actions — List scheduled actions that have been completed. Completed actions can •...

  • Page 72: Lists

    In a Web browser, go to http://rhn.redhat.com. The page shown in Figure 6-1 will be displayed. Figure 6-1. RHN Website If you have not registered a system yet or do not have a redhat.com account, create a new account by clicking Create Account. After creating a new user account, you must register your system before using RHN.
  • Page 73 Chapter 6. Red Hat Network Website If you are new to the RHN website, it is recommended that you read Section 6.1 Navigation to become familiar with the layout and symbols used throughout the website. Figure 6-2. Your Red Hat Network The top of the page shows how many systems need attention, provides a link to quickly view those systems, and displays a summary of scheduled actions.

  • Page 74: Your Account

    Chapter 6. Red Hat Network Website The Action Summary section provides the following information about events scheduled in the past week: Recently Failed Actions — Number of scheduled actions that did not succeed. • Pending Actions — Number of scheduled actions that have not yet been completed. •...

  • Page 75: Your Preferences

    Chapter 6. Red Hat Network Website 6.3.2. Your Preferences The Your Preferences page allows you to configure Red Hat Network options, including: Email Notifications — Determine whether you want to receive email every time an Errata Alert is • applicable to one or more systems in your RHN account. Important This setting also enables Management and Provisioning customers to receive a daily summary of system events.
  • Page 76 6.3.4.7. Outage Policy The Outage Policy page identifies scheduled maintenance windows for Red Hat Network and pro- vides the means to subscribe to the Email Outage List (rhn-outage-list@redhat.com) to be notified of emergency and other unscheduled outages. 6.3.4.8. Release Notes The Release Notes page lists the notes accompanying every recent release of Red Hat Network.

  • Page 77: Systems

    Chapter 6. Red Hat Network Website 6.4. Systems If you click the Systems tab on the top navigation bar, the Systems category and links appear. The pages in the Systems category allow you to select systems so that you can perform actions on them and create System Profiles.

  • Page 78: Systems

    Chapter 6. Red Hat Network Website You can also click the Use Group button in the System Groups section of the Overview page to go directly to the System Set Manager. Refer to Section 6.4.4 System Set Manager — for more information.
  • Page 79 Chapter 6. Red Hat Network Website System — The name of the system as configured when registering it. The default name is the • hostname of the system. Clicking on the name of a system takes you to the System Details page for the system.
  • Page 80 Chapter 6. Red Hat Network Website 6.4.2.6. System Details If you click on the name of a system on any page, it will display the System Details page for the system. From here, you may modify this information or remove the system altogether by clicking the delete system link on the top-right corner.
  • Page 81 Chapter 6. Red Hat Network Website Include system in daily summary report calculations — This setting includes the system in • a daily summary of system events. (By default, all Management and Provisioning systems are included in the summary.) These are actions affecting packages, such as scheduled Errata Updates, and system reboots or failures to check in.
  • Page 82 Chapter 6. Red Hat Network Website not regenerate, delete, or use this key (with ) while a profile-based kickstart is in progress. rhnreg_ks If you do, the kickstart will fail. 6.4.2.6.1.7. System Details Details Remote Command — The method for running a remote command on the system. To allow remote commands to be run on the client through RHN, first install the latest packages available within the RHN Provision- rhncfg*...
  • Page 83 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 6.4.2.6.1.7 System Details Details Remote Command — for more information.
  • Page 84 Chapter 6. Red Hat Network Website 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 syn- chronize the packages of the selected system with the package manifest of the compared profile.
  • Page 85 Chapter 6. Red Hat Network Website Diff — Validate the configuration files installed on the system by comparing them to versions stored • in RHN’s central configuration manager. Select the files to be diffed and click Analyze Differences. Config Channels — Set the subscription and rank of configuration channels that may be associated •...
  • Page 86 Chapter 6. Red Hat Network Website 6.4.2.6.6. System Details Snapshots — Provides snapshots enabling rollback of the system’s package profile, configuration files, and RHN settings. These snapshots are captured whenever an action takes place on the system. 6.4.2.6.6.1. System Details Snapshots Snapshots —...
  • Page 87 Chapter 6. Red Hat Network Website but you insert an IP address kickstart CD-ROM built for Red Hat Enterprise Linux 3. This would result in errors and cause the kickstart to fail. 6.4.2.6.7.2. System Details Kickstart Session Status — If you’ve scheduled a kickstart, this subtab shows where the system’s kickstart stands. Details include the kickstart profile used, its state, and pending and latest actions.

  • Page 88: System Groups

    Chapter 6. Red Hat Network Website — System Event • 6.4.2.6.9. System Details Probes — Displays all of the probes monitoring the system. You must be logged into an RHN Satellite Server with Monitoring enabled to see this tab. The State column shows icons representing the status of each probe.
  • Page 89 Chapter 6. Red Hat Network Website Figure 6-4. System Group List The System Groups list contains several columns for each group: Select — These checkboxes enable you to add systems in groups to the System Set Manager. To • select groups, mark the appropriate checkboxes and click the Update button below the column. All systems in the selected groups are added to the System Set Manager.
  • Page 90 Chapter 6. Red Hat Network Website Systems — Total number of systems contained by the group. Clicking on the number takes you to • the Systems tab of the System Group Details page for the group. Refer to Section 6.4.3.3 System Group Details —...

  • Page 91: System Set Manager

    Chapter 6. Red Hat Network Website 6.4.3.3.4. System Group Details Errata — List of relevant Errata for systems in the system group. Clicking the Advisory takes you to the Details tab of the Errata Details page. (Refer to Section 6.5.2.2 Errata Details for more information.) Click- ing the Affected Systems number lists all of the systems addressed by the Errata.
  • Page 92 Chapter 6. Red Hat Network Website 6.4.4.2. System Set Manager Systems — List of systems now selected. To remove systems from this set, select them and click the Remove button. 6.4.4.3. System Set Manager Errata — List of Errata Updates applicable to the current system set. Click the number in the Systems column to see to which systems in the System Set Manager the given Errata applies to.
  • Page 93 Chapter 6. Red Hat Network Website 6.4.4.6. System Set Manager Channels — Options to manage channel associations through the following subtabs: 6.4.4.6.1. System Set Manager Channels Channel Subscriptions — To subscribe or unsubscribe the selected systems in any of the channels, toggle the appropriate radio buttons and click the Alter Subscriptions button.
  • Page 94 Chapter 6. Red Hat Network Website 6.4.4.6.2.3. System Set Manager Channels Config Channels Diff — Use this subtab to validate configuration files on the selected systems against copies in your central repository on RHN. The table lists the configuration files associated with any of the selected systems. Clicking its system count displays the systems already subscribed to the file.
  • Page 95 Chapter 6. Red Hat Network Website group, and timeout period, as well as the script itself on this page. Select a date and time to begin attempting the command, and click Schedule Remote Command. 6.4.4.8. System Set Manager Misc — Misc —...

  • Page 96: System Entitlements

    Chapter 6. Red Hat Network Website 6.4.4.8.7. System Set Manager Misc System Preferences — Toggling the Yes and No radio buttons and then clicking the Change Preferences button alters your notification preferences for the selected systems. All of these preferences may also be applied to systems individually through the Properties subtab of the System Details page.

  • Page 97: Advanced Search

    Chapter 6. Red Hat Network Website Warning Changing a system’s entitlement is an irreversible action. You may be unable to change the entitle- ment levels of some systems. For more information, refer to the RHN entitlement policy linked from the System Entitlements page. In addition, you may entitle all newly registered systems to the Management service level at once by clicking the Auto-Entitle Newest Servers Now link at the bottom of the page.
  • Page 98 Chapter 6. Red Hat Network Website 2. Click the create new key link at the top-left corner. Warning In addition to the fields listed below, RHN Satellite Server customers may also populate the Key field itself. This user-defined string of characters can then be supplied with rhnreg_ks register client systems with the Satellite.

  • Page 99: Stored Profiles

    Chapter 6. Red Hat Network Website base software channels — registration fails • entitlements — registration fails • enable config flag — configuration management is set • Also remember, using a system-specific re-activation key along with a normal activation key will fail. You’re now ready to use multiple activation keys at once.
  • Page 100 Chapter 6. Red Hat Network Website 6.4.10.1. Kickstart Prerequisites Although Red Hat Network has taken great pains to ease the provisioning of systems, some prepara- tion is still required for your infrastructure to handle kickstarts. For instance, before creating kickstart profiles, you may consider: A DHCP server is not required for kickstarting, but it can make things easier.
  • Page 101 Chapter 6. Red Hat Network Website 6.4.10.3. Creating Kickstarts To develop a new kickstart profile, and you are not using RHN Satellite Server, first create a distribu- tion through the Distributions page. Refer to Section 6.4.10.9 Kickstart Distributions — instructions. Once that is done, return to the Kickstart page and click create new kickstart in the upper-right corner of the page.
  • Page 102 Chapter 6. Red Hat Network Website 6.4.10.4.2. Kickstart Details Options — Collects the precise values to be applied against the kickstart process, including bootloader type, time zone, root password, and partition details. Keep in mind, the kickstart network configuration value here is used by the bootloader to determine the network configuration for the kickstart process, unlike the network setting on the Advanced Options tab, which is used to generate the kickstart configuration file.
  • Page 103 Chapter 6. Red Hat Network Website 6.4.10.4.6.1. Kickstart Details Post Details — Allows editing of the %post script and inclusion of other options to be set after initial kickstart. You may alter individual commands within the script, identify the package profile to be used during synchronization, and include the activation key to be used for registration.
  • Page 104 Chapter 6. Red Hat Network Website 6.4.10.5. Kickstart Profiles — Lists the kickstart profiles created by your organization. Click a name to see the Kickstart Details page. To enable inactive profiles, select the appropriate checkboxes and click the Update Profiles. 6.4.10.6.
  • Page 105 Chapter 6. Red Hat Network Website based upon the distribution to be kickstarted. It should look something like, "auto-kickstart-ks-rhel- i386-as-3". Then, strip everything preceding the "ks" to derive the boot image. For instance, in the above example, you would put "ks-rhel-i386-as-3" in the Autokickstart RPM field. Then select the matching distribution from the Base Channel and Installer Generation dropdown menus, such as Red Hat Enterprise Linux AS (v.3 for x86) and Red Hat Enterprise Linux 3, respectively.

  • Page 106: Errata

    Chapter 6. Red Hat Network Website ksdevice=eth0 It is possible to change the distribution for a kickstart profile within a family, such as RHEL AS3 to RHEL ES3, by specifying the new distribution label. Note that you cannot move between versions (2.1 to 3) and between updates (U1 to U2).

  • Page 107: Relevant Errata

    • 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. 6.5.1. Relevant Errata As shown in Figure 6-5, the Relevant Errata page displays a customized list of Errata Alerts that applies to your registered systems.

  • Page 108: All Errata

    Chapter 6. Red Hat Network Website 6.5.2. All Errata The All Errata page displays a list of all Errata Alerts released by Red Hat. It works much the same as the Relevant Errata page in that clicking either the Advisory or the number of systems affected takes you to related tabs of the Errata Details page.

  • Page 109: Advanced Search

    Chapter 6. Red Hat Network Website 6.5.2.2. Errata Details If you click on the Advisory of an Errata Alert in the Relevant or All pages, its Errata Details page appears. This page is further divided into the following tabs: 6.5.2.2.1. Errata Details Details Provides the Errata Report issued by Red Hat.
  • Page 110 Chapter 6. Red Hat Network Website different base channel. A child channel is a channel associated with a base channel but contains extra packages. For instance, an organization can create a child channel associated with Red Hat Enterprise Linux 2.1 for the x86 architecture that contains extra packages needed only for the organization, such as a custom engineering application.
  • Page 111 Chapter 6. Red Hat Network Website 6.6.1.2. 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.6.1.3. All Channels The All Channels page can be retrieved by clicking All below Software Channels in the left nav- igation bar.
  • Page 112 Chapter 6. Red Hat Network Website channel means that a user is a Channel Administrator but only for that channel. He cannot create new channels or clone them. 6.6.1.4.4. Software Channel Details Errata List of Errata affecting the channel. The list displays advisory types, names, summaries, and the dates issued.

  • Page 113: Channel Entitlements

    URL from the location bar, and paste it into the curl or wget command. Once downloaded, either burn the images to CD-Rs or CD-RWs or copy them to the machine for direct installation. Refer to http://www.redhat.com/download/howto_download.html for additional download instructions and steps to burn images to discs. Refer to the operating system’s respective installation guide for instructions on installing from CD-ROM or hard drive, available at http://www.redhat.com/docs/.

  • Page 114: Software Packages

    Chapter 6. Red Hat Network Website 6.6.5. Software Packages A software package is the smallest essential ingredient of any Red Hat Enterprise Linux system. Pack- ages, commonly known as RPMs because of their oversight by RPM Package Manager, are the pieces of software that, when installed, enable your system to operate.
  • Page 115 Chapter 6. Red Hat Network Website 6.6.5.3. Package Details If you click on the name of any package in the website, the Package Details page will appear. This page contains the following tabs: 6.6.5.3.1. Package Details Details Details about the package, including subtabs for overview, dependencies, change log, and file list: 6.6.5.3.1.1.

  • Page 116: Manage Config Channels

    Chapter 6. Red Hat Network Website 6.6.6. Manage Config Channels — Provides the means to create and oversee channels containing configuration files. You must be an Configuration Administrator or Organization Administrator to view this section of the website. Like software channels, configuration channels store files to be installed on systems. Unlike software pack- ages, various versions of configuration files may prove useful to a system at any given time.
  • Page 117 Chapter 6. Red Hat Network Website touch /etc/sysconfig/rhn/allowed-actions/configfiles/mode To grant full configuration management access, issue this command: touch /etc/sysconfig/rhn/allowed-actions/configfiles/all Your system should now be ready for config management through RHN. Command line options also exist for many of these functions. Refer to Appendix A Command Line Config Management Tools for instructions.
  • Page 118 Chapter 6. Red Hat Network Website 6.6.6.6 Configuration File Details — for instructions. Click the config channel name to access the Configuration Channel Details page. Refer to Section 6.6.6.5 Configuration Channel Details — for instructions. 6.6.6.5. Configuration Channel Details — If you click on the name of a channel in a list, the Configuration Channel Details page will appear.
  • Page 119 Chapter 6. Red Hat Network Website 6.6.6.5.2.4. Configuration Channel Details Files Create Directory — Allows you to create a configuration directory within the interface. The fields resemble those on the Upload and Create File subtab: Path is the absolute location of the directory on the system. The user, group, and mode fields allow you to set the directory’s ownership and permissions.
  • Page 120 Chapter 6. Red Hat Network Website 6.6.6.6.4. Configuration File Details Copy — A list of configuration channels that may receive a copy of the file. To copy the file to a channel, select the channel’s checkbox, and click the Copy File button. Copy to Config Channel —...

  • Page 121: Schedule

    Chapter 6. Red Hat Network Website the variables will be substituted with the actual hostname and IP address of the system, as recorded in RHN’s System Profile, such as: 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).

  • Page 122: Pending Actions

    Chapter 6. Red Hat Network Website 6.7.1. Pending Actions As shown in Figure 6-7, 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-7.

  • Page 123: Users

    Chapter 6. Red Hat Network Website Select — Use the checkboxes in this column to select actions. After selecting actions, you can • either add them to your selection list or move them to the Archived Actions list. If you archive a pending action, it is not canceled;...

  • Page 124: User Roles

    Chapter 6. Red Hat Network Website for those who will administer your system groups. Click in the User List to modify users within your organization. 6.8.1. User Roles To delegate responsibilities within your organization, Red Hat Network provides several roles with varying degrees of responsibility and access.
  • Page 125 RHN Satellite Server customer, you must contact Customer Service to have user accounts disabled. Go to the Contact RHN page at https://rhn.redhat.com/help/contact.pxt, select the Customer Service radio button, and enter your request containing the username to be removed and the overall account affected in the text fields before clicking Send.
  • Page 126 Chapter 6. Red Hat Network Website 6.8.2.2.1. User Details Details — The username, first name, last name, email address, and user roles for the user. All of this information is modifiable. To do so, make your changes and click the Update button. Remember, when changing a user’s password, you will see only asterisks as you type the password.

  • Page 127: Monitoring

    Chapter 6. Red Hat Network Website 6.8.2.2.5. User Details Preferences — Modifiable Red Hat Network options. These include: Email Notification — Determine whether this user should receive email every time an Errata Alert • is applicable to one or more systems in his or her RHN account, as well as daily summaries of system events.

  • Page 128: Probe Status

    Chapter 6. Red Hat Network Website 6.9.1. Probe Status — As shown in Figure 6-9, the Probe Status page is shown by default when you click Monitoring in the top navigation bar. Figure 6-9. Probe Status The Probe Status page displays the summary count of probes in the various states and provides a simple interface to find problematic probes quickly.
  • Page 129 Chapter 6. Red Hat Network Website The Probe Status page contains tabs for each of the possible states, as well as one that lists all probes. The tables are identical in that each contains columns indicating probe state, the system being monitored, the probes used, and the date and time the status was last updated.

  • Page 130: Notification

    Chapter 6. Red Hat Network Website the results should be shown in a graph, an error log, or both. Then click Generate report at the bottom of the page. If no data exist for the probe’s metrics, you are presented with a message indicating time series data found for specified time period 6.9.2.

  • Page 131: 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 sys- tem resources, network services, databases, and both standard and custom applications. (During the Monitoring technology preview, Provisioning-entitled systems are treated as if they have Monitoring entitlements.) Monitoring provides both real-time and historical state-change information, as well as specific metric...

  • Page 132: Probes Requiring The Daemon

    Chapter 7. Monitoring Please note the Red Hat Network Monitoring Daemon requires monitored systems allow connections on port 4545. You may avoid opening this port and installing the daemon altogether by using sshd instead. Refer to Section 7.2.3 Configuring SSH for details. 7.2.1.

  • Page 133: Configuring Ssh

    Chapter 7. Monitoring 2. Once subscribed, open the Channel Details Packages tab and find the package (un- rhnmd der ’R’). 3. Click the package name to open the Package Details page. Go to the Target Systems tab, select the desired systems, and click Install Packages. 4.

  • Page 134: Notifications

    Chapter 7. Monitoring If config management is enabled on the systems to be monitored, you may deploy this file across systems using a config channel. Refer to Section 6.6.6.1 Preparing Systems for Config Management for details. Note If valid entries already exist in , add the daemon key to the file rather than authorized_keys use it to replace it.

  • Page 135: Receiving Notifications

    These notifications will 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 136: Filtering Notifications

    Chapter 7. Monitoring ACK METOO system 1h boss@domain.com Capitalization is not required. Duration can be listed in minutes (m), hours (h), or days (d). Email addresses are needed only for redirects (REDIR) and supplemental (METOO) notifications. The description of the action contained in the resulting email will default to the precise command entered by the user.

  • Page 137: Probes

    Chapter 7. Monitoring 7.4. 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. It is here where you will conduct most probe-related work.

  • Page 138: Monitoring The Rhn Server

    To thoroughly troubleshoot a probe, you must first obtain its probe ID. You may get this by running on the RHN Server as the nocpulse user. The output will resemble: rhn-catalog 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...

  • Page 139: Viewing The Output Of Rhn-Runprobe

    Chapter 7. Monitoring The command above will result in output similar to: 5 ServiceProbe on example4.redhat.com (199.168.36.175 linux:cpu usage Run as: Unix::CPU.pm --critical=90 --sshhost=199.168.36.175 --warn=70 --timeout=15 --sshuser=nocpulse --shell=SSHRemoteCommandShell --sshport=4545 Now that you have the ID, you use it with to examine the probe’s output. Refer to rhn-rhnprobe Section 7.5.2 Viewing the output of...
  • Page 140 Chapter 7. Monitoring...

  • Page 141: 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 configuration files: the Red Hat Network Configuration Client and the Red Hat Network Configuration Manager. If you don’t yet have these these tools installed, they can be found within the RHN Provisioning child channel for your operating system.

  • Page 142: Differentiating Between Config Files

    Appendix A. Command Line Config Management Tools A.1.3. Viewing Config Channels To view the labels and names of the config channels that apply to the system, issue the command: rhncfg-client channels You should see output resembling: Config channels: Label Name ----- ---- config-channel-17...

  • Page 143: Red Hat Network Configuration Manager

    Appendix A. Command Line Config Management Tools A.2. Red Hat Network Configuration Manager Unlike the Red Hat Network Configuration Client, the Red Hat Network Configuration Manager ) is designed to maintain RHN’s central repository of config files and channels, rhncfg-manager not those located on client systems.

  • Page 144: Differentiating Between Latest Config Files

    Appendix A. Command Line Config Management Tools In addition to the required channel label and path to the file, you may use the available options for modifying the file during its addition. For instance, you may alter the path and filename by including option in the command, like: --dest-file rhncfg-manager add...

  • Page 145: Downloading All Files In A Channel

    Appendix A. Command Line Config Management Tools A.2.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. Refer to Section A.2.11 Determining the Number of File Revisions for related instructions.

  • Page 146: Listing All Config Channels

    Appendix A. Command Line Config Management Tools A.2.7. Listing All Files in a Channel To list all the files in a channel, issue the command: rhncfg-manager list channel-label You should see output resembling: Files in config channel ‘blah3’: /tmp/dest_path/foo.txt A.2.8. Listing All Config Channels To list all of your organization’s configuration channels, issue the command: rhncfg-manager list-channels You should see output resembling:...

  • Page 147: Determining The Number Of File Revisions

    Appendix A. Command Line Config Management Tools A.2.11. Determining the Number of File Revisions To find out how many revisions (revisions go from 1 to N with N being an integer greater than 0) of a file/path are in a channel, issue the command: rhncfg-manager revisions channel-label /tmp/dest_path/foo.txt You should see output resembling: Analyzing files in config channel blah...
  • Page 148 Appendix A. Command Line Config Management Tools...

  • Page 149: Rhn Api Access

    (API) available. This interface can be found by clicking Help at the top-right corner of the RHN website, then clicking API in the left navigation bar. Or you may go directly to: https://rhn.redhat.com/rpc/api/. You should use this URL for your XMLRPC server, as well as your browser.

  • Page 150: Viewing The Cid

    Appendix B. RHN API Access B.4. Viewing the cid Like servers, channels have their own IDs. This value, the cid, is a required parameter for some meth- ods, including set_base_channel and set_child_channels. Also like the sid, the cid can be obtained through the RHN website.
  • Page 151 Appendix B. RHN API Access ############################################################################ System calls. ############################################################################ # This next call returns a list of systems available to the user. # syntax of this call is described at: http://$HOST/rpc/api/system/list_user_systems/ # In the code snippet below, we dump data about our systems, and we # capture the ID of the first system we find for future operations.
  • Page 152 Appendix B. RHN API Access...

  • Page 153: Probes

    Appendix C. Probes As described in Section 6.9 Monitoring — , systems entitled with Monitoring can have probes applied against them to 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 aspects of your systems, rather than externally facing components such as , require the installation of the Red Hat Network Monitoring Daemon (...

  • Page 154: Apache 1.3.X And 2.0.X

    Appendix C. Probes C.2. Apache 1.3.x and 2.0.x The probes in this section may be applied to instances of the Apache HTTP Server. Although the default values presume you will apply these probes using standard HTTP, you may also use them over secure connections by changing the application protocol to https and the port to 443.

  • Page 155: Apache::uptime

    Appendix C. Probes Field Value Application Protocol* http Port* Pathname* /server-status UserAgent* NOCpulse-ApacheUptime/1.0 Username 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 156: Bea Weblogic::execute Queue

    Appendix C. Probes In order to obtain this higher level of granularity, the BEA Domain Admin Server parameter 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 157: Bea Weblogic::heap Free

    Appendix C. Probes C.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). Field Value SNMP Community String* public SNMP Port* SNMP Version*...

  • Page 158: Bea Weblogic::server State

    Appendix C. Probes Field Value Critical Maximum Connection Rate Warning Maximum Connection Rate Critical Maximum Waiters Warning Maximum Waiters Table C-6. BEA WebLogic::JDBC Connection Pool settings C.3.4. BEA WebLogic::Server State The BEA WebLogic::Server State probe monitors the current state of a BEA Weblogic Web server. If the probe is unable to make a connection to the server, a CRITICAL status results.

  • Page 159: General

    Appendix C. Probes Field Value SNMP Version* BEA Domain Admin Server BEA Server Name* myserver Servlet Name* Critical Maximum High Execution Time Warning Maximum High Execution Time Critical Maximum Execution Time Moving Average Warning Maximum Execution Time Moving Average Table C-8. BEA WebLogic::Servlet settings C.4.

  • Page 160: General::snmp Check

    Appendix C. Probes item key =" " /item • The remote program will need to output some iteration of the following code to STDOUT perldata hash item key="data" 10 /item item key="status_message" status message here /item /hash /perldata The required value for is the data point to be inserted in the database for time-series trending.

  • Page 161: General::tcp Check

    Appendix C. Probes Field Value Critical Maximum Value Warning Maximum Value Warning Minimum Value Critical Minimum Value Table C-11. General::SNMP Check settings C.4.4. General::TCP Check The General::TCP Check probe tests your TCP server by verifying it can connect to a system via the specified port number.

  • Page 162: General::uptime (Snmp)

    Appendix C. Probes Field Value Send Expect Timeout* Critical Maximum Latency Warning Maximum Latency Table C-13. General::UDP Check settings C.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 —...

  • Page 163: Linux::disk Io Throughput

    Appendix C. Probes Field Value Timeout* Critical Maximum CPU Percent Used Warning Maximum CPU Percent Used Table C-15. Linux::CPU Usage settings C.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 164: Linux::inodes

    Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the moni- rhnmd tored system to execute this probe. Field Value File system* /dev/hda1 Timeout* Critical Maximum File System Percent Used Warning Maximum File System Percent Used Critical Maximum Space Used Warning Maximum Space Used Warning Minimum Space Available...

  • Page 165: Linux::load

    Appendix C. Probes Field Value Interface* Timeout* Critical Maximum Input Rate Warning Maximum Input Rate Warning Minimum Input Rate Critical Minimum Input Rate Critical Maximum Output Rate Warning Maximum Output Rate Warning Minimum Output Rate Critical Minimum Output Rate Table C-19. Linux::Interface Traffic settings C.5.6.

  • Page 166: Linux::process Counts By State

    Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the moni- rhnmd tored system to execute this probe. Field Value Include reclaimable memory Timeout* Warning Maximum RAM Free Critical Maximum RAM Free Table C-21.

  • Page 167: Linux::process Count Total

    Appendix C. Probes C.5.9. Linux::Process Count Total The Linux::Process Count Total probe monitors a system and collects the following metric: Process Count — The total number of processes currently running on the system. • Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the moni- rhnmd tored system to execute this probe.

  • Page 168: Linux::process Running

    Appendix C. Probes Field Value Critical Maximum Child Process Groups Warning Maximum Child Process Groups Critical Maximum Threads Warning Maximum Threads Critical Maximum Physical Memory Used Warning Maximum Physical Memory Used Critical Maximum Virtual Memory Used Warning Maximum Virtual Memory Used Table C-24.

  • Page 169: Linux::tcp Connections By State

    Appendix C. Probes Swap Free — The percent of swap memory currently free. • Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the moni- rhnmd tored system to execute this probe. Field Value Timeout* Warning Minimum Swap Free Critical Minimum Swap Free Table C-26.

  • Page 170: Linux::users

    Appendix C. Probes Field Value 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. Linux::TCP Connections by State settings C.5.14.

  • Page 171: Logagent

    Appendix C. Probes C.6. LogAgent The probes in this section monitor the log files on your systems. You can use them to query logs for certain expressions and track the sizes of files. For LogAgent probes to run, the nocpulse user must be granted read access to your log files.

  • Page 172: Logagent::log Size

    Appendix C. Probes Field Value Critical Maximum Match Rate Warning Maximum Match Rate Warning Minimum Match Rate Critical Maximum Match Rate Table C-30. LogAgent::Log Pattern Match settings C.6.2. LogAgent::Log Size The LogAgent::Log Size probe monitors log file growth and collects the following metrics: Size —...

  • Page 173: Mysql 3.23 - 3.33

    Appendix C. Probes Table C-31. LogAgent::Log Size settings C.7. MySQL 3.23 - 3.33 The probes in this section monitor aspects of the MySQL database using the binary. No mysqladmin specific user privileges are needed for these probes. Note that the package must be installed on the system conducting the monitoring mysql-server for these probes to complete.

  • Page 174: Mysql::query Rate

    Appendix C. Probes C.7.3. MySQL::Open Tables The MySQL::Open Tables probe monitors the MySQL server and collects the following metric: Open Tables — The number of tables open when the probe runs. • Field Value Username Password MySQL Port* 3306 Timeout Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects...

  • Page 175: Network Services

    Appendix C. Probes Field Value Username 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 C.8. Network Services The probes in this section monitor various services integral to a functioning network. When applying them, ensure their timed thresholds do not exceed the amount of time allotted to the timeout period.

  • Page 176: Network Services::imap Mail

    Appendix C. Probes This probe supports authentication. Provide a username and password in the appropriate fields to use this feature.The optional Expect value is the string to be matched against after a successful connection is made to the FTP server. If the expected string is not found, the probe will return a CRITICAL state. Field Value Expect...

  • Page 177: Network Services::ping

    Appendix C. Probes Field Value SMTP Port* Timeout* Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C-40. Network Services::Mail Transfer (SMTP) settings C.8.5. Network Services::Ping The Network Services::Ping probe determines if the RHN Server can the monitored system or a ping specified IP address.

  • Page 178: Network Services::remote Ping

    Appendix C. Probes collects the following metric: Remote Service Latency — The time it takes in seconds for the POP server to answer a connection • request. The required Expect value is the string to be matched against after a successful connection is made to the POP server.

  • Page 179: Network Services::rpcservice

    Appendix C. Probes Field Value Warning Maximum Packet Loss Table C-43. Network Services::Remote Ping settings C.8.8. Network Services::RPCService The Network Services::RPCService probe tests the availability of remote procedure call (RPC) pro- grams on a given IP address. It collects the following metric: Remote Service Latency —...

  • Page 180: Network Services::ssh

    Appendix C. Probes Field Value URL Path Expect Header HTTP/1 Expect Content UserAgent* NOCpulse-check_http/1.0 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 C.8.10. Network Services::SSH The Network Services::SSH probe determines the availability of SSH on the specified port and collects the following metric: Remote Service Latency —...

  • Page 181: Oracle 8I And 9I

    Appendix C. Probes 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. This probe supports authentication. Provide a username and password in the appropriate fields to use this feature.

  • Page 182: Oracle::active Sessions

    Appendix C. Probes C.9.1. Oracle::Active Sessions The Oracle::Active Sessions probe monitors an Oracle instance and collects the following metrics: Active Sessions — number active sessions based value • V$PARAMETER.PROCESSES Available Sessions — The percentage of active sessions based on the value of •...

  • Page 183: Oracle::buffer Cache

    Appendix C. Probes Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Time Blocking (seconds)* Timeout* Critical Maximum Blocking Sessions Warning Maximum Blocking Sessions Table C-50. Oracle::Blocking Sessions settings C.9.4. Oracle::Buffer Cache The Oracle::Buffer Cache probe computes the Buffer Cache Hit Ratio so as to optimize the system global area (SGA) Database Buffer Cache size.

  • Page 184: Oracle::data Dictionary Cache

    Appendix C. Probes insensitive. A CRITICAL status is returned if this value is not found. Requirements — The Red Hat Network Monitoring Daemon ( ) must be running on the moni- rhnmd tored system to execute this probe. For this probe to run, the nocpulse user must be granted read access to your log files.

  • Page 185: Oracle::disk Sort Ratio

    Appendix C. Probes C.9.7. Oracle::Disk Sort Ratio The Oracle::Disk Sort Ratio probe monitors an Oracle database instance and collects the following metric: Disk Sort Ratio — The rate of Oracle sorts that were too large to be completed in memory and were •...

  • Page 186: Oracle::library Cache

    Appendix C. Probes Allocated Extents — The number of allocated extents for any index. • Available Extents — The percentage of available extents for any index. • The required Index Name field contains a default value of % that will match any index name. Field Value Oracle SID*...

  • Page 187: Oracle::locks

    Appendix C. Probes C.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. Locks are used so that multiple users or processes updating the same data in the database do not conflict.

  • Page 188: Oracle::table Extents

    Appendix C. Probes Field Value Critical Maximum Redo Buffer Allocation Retry Rate Warning Maximum Redo Buffer Allocation Retry Rate Table C-59. Oracle::Redo Log settings C.9.13. Oracle::Table Extents The Oracle::Table Extents probe monitors an Oracle database instance and collects the following metrics: Allocated Extents-Any Table —...

  • Page 189: Oracle::tns Ping

    Appendix C. Probes metric: Available Space Used — The percentage of available space in each tablespace that has been used. • Tablespace is the shared pool of space in which a set of tables live. This probe alerts the user when the total amount of available space falls below the threshold.

  • Page 190: Rhn Satellite Server::execution Time

    Appendix C. Probes C.10.1. RHN Satellite Server::Disk Space The RHN Satellite Server::Disk Space probe monitors the free disk space on a Satellite and collects the following metrics: File System Used — The percent of the current filesystem now in use. •...

  • Page 191: Rhn Satellite Server::latency

    Appendix C. Probes Field Value Timeout (seconds)* Critical Maximum Input Rate Critical Maximum Output Rate Table C-65. RHN Satellite Server::Interface Traffic settings C.10.4. RHN Satellite Server::Latency The RHN Satellite Server::Latency probe monitors the latency of probes on a Satellite and collects the following metric: Probe Latency Average —...

  • Page 192: Rhn Satellite Server::process Counts

    Appendix C. Probes Probes — The number of individual probes running on a Satellite. • Field Value Critical Maximum Probe Count Warning Maximum Probe Count Table C-68. RHN Satellite Server::Probe Count settings C.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 —...

  • Page 193: Rhn Satellite Server::process Health

    Appendix C. Probes Processes — The number of processes running simultaneously on the machine. • Field Value Critical Maximum Processes Warning Maximum Processes Table C-70. RHN Satellite Server::Processes settings C.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 —...

  • Page 194: Rhn Satellite Server::process Running

    Appendix C. Probes Table C-71. RHN Satellite Server::Process Health settings C.10.10. RHN Satellite Server::Process Running The RHN Satellite Server::Process Running probe verifies that the specified process is running. Spec- ify the process by either command name or process I.D. (PID). Entering a PID will override the entry of a command name.

  • Page 195: Glossary

    An Errata Alert that pertains to a bug fix. Bugzilla Bugzilla is an online application (http://www.redhat.com/bugzilla) that allows users to commu- nicate 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 196 Red Hat Enterprise Linux. The information includes the topics of the Errata, Bugzilla bug IDs, relevant releases/architectures, solutions including required RPMs, and MD5 check- sums for verification. Errata are also available at http://www.redhat.com/errata/. Each RHN Er- rata Alert is based on the Red Hat Enterprise Linux Errata List.
  • Page 197 Glossary team tests new packages they are placed on the Red Hat Public File Server and on the Red Hat Network Server and an Errata is generated. Errata Alert RHN Errata Alert that updated packages based on Red Hat Errata are available for one or more systems within an organization.
  • Page 198 Glossary Registered System A system that is registered with Red Hat Network. Also known as a client system. Red Hat Network Daemon The RHN client daemon ( ) that periodically polls Red Hat Network for scheduled actions. rhnsd Red Hat Network Registration Client The RHN client application ( ) that collects information about the client system, rhn_register...
  • Page 199 Glossary 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. Software Manager The name of the first Service Level offering for Red Hat Network. Software Manager is now known as RHN Update .
  • Page 200 Glossary...

  • Page 201: Index

    Index client applications obtaining, 5 Config Channel List, 104 config channels details, 106, 107 account global, 105 deactivate, 62 list of, 104 action Config Channels and Files completed systems, 111 Config Channel List, 104 details, 111 config management failed systems, 111 system preparation, 104 in progress systems, 111 Configuration...
  • Page 202 viewing list of applicable errata, 95 Process Counts by State, 154 Errata notifications Process Health, 155 automatic updates, 4 Process Running, 156 Swap Usage, 156 TCP Connections by State, 157 Users, 158 General Virtual Memory, 158 probes, 147 List Navigation Remote Program, 147 Remote Program with Data, 147 explanation of, 60...
  • Page 203 package installation navigation, 57 scheduled, 4 Network Services package list DNS Lookup, 163 Updating on server, 30, 70 FTP, 163 packages IMAP Mail, 164 details, 103 Mail Transfer (SMTP), 164 downloading, 102 Ping, 165 filter, 100 POP Mail, 165 installing, 102 probes, 163 overview, 102 password...
  • Page 204 DNS Lookup, 163 on the RHN Server, 126 FTP, 163 Oracle, 169 IMAP Mail, 164 RHN Satellite Server, 177 Mail Transfer (SMTP), 164 thresholds, 125 WebLogic, 143 Ping, 165 POP Mail, 165 Provisioning Remote Ping, 166 service level, 3 RPCService, 167 proxy server Secure Web Server (HTTPS), 167 with Red Hat Network Alert Notification Tool, 40...
  • Page 205 Red Hat Update Agent, 41 Load, 179 Command Line Arguments, 26 Probe Count, 179 configuration, 30 probes, 177 with a proxy server, 31 Process Counts, 180 Red Hat Update Agent (up2date) Process Health, 181 activation keys, 34 Process Running, 182 choosing packages for update, 19 Processes, 180 choosing software channels, 19...
  • Page 206 adding and removing, 78 changing password, 114 creating, 78 creating, 113 deleting, 78 general address, 115 editing details, 78 list of, 112 list of, 76 roles, 112, 114 viewing details, 78 shipping address, 115 system group list User List, 112 status, 77 System Groups assigning and removing, 73...
  • Page 207 Your Account, 62 Your RHN, 60 Your RHN, 60 Account Deactivation, 62 Addresses, 62 Email, 62 Help, 63 Purchase History, 63 Your Account, 62 Your Preferences, 63...

Table of Contents