Red Hat Network 3.
Red Hat Network 3.6: Reference Guide Copyright © 2004 by Red Hat, Inc. Red Hat, Inc. 1801 Varsity Drive Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA RHNref(EN)-3.6-Print-RHI (2004-11-09T17:22) Copyright © 2005 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.
Table of Contents Introduction to the Guide.................................................................................................................... i 1. Document Conventions.......................................................................................................... i 2. More to Come ...................................................................................................................... iv 2.1. Send in Your Feedback .....................................................
6. Red Hat Network Website............................................................................................................ 57 6.1. Navigation........................................................................................................................ 57 6.1.1. Entitlement Views ............................................................................................. 57 6.1.2. Categories and Pages .....................................................................................
6.9.4. Global Config — ...................................................................................... 117 A. Command Line Config Management Tools ............................................................................. 119 A.1. Red Hat Network Configuration Client .................................................................... 119 A.1.1. Listing Config Files........................................................................................ 119 A.1.2. Getting a Config File.............
C.5.6. Linux::Load.................................................................................................... 143 C.5.7. Linux::Memory Usage ................................................................................... 143 C.5.8. Linux::Process Counts by State ..................................................................... 144 C.5.9. Linux::Process Count Total ............................................................................ 144 C.5.10. Linux::Process Health .................
C.10.9. RHN Satellite Server::Processes .................................................................. 171 C.10.10. RHN Satellite Server::Process Health........................................................ 171 C.10.11. RHN Satellite Server::Process Running..................................................... 172 C.10.12. RHN Satellite Server::Swap....................................................................... 173 C.10.13. RHN Satellite Server::Users............................................
Introduction to the Guide Welcome to the Red Hat Network 3.6 Reference Guide. The RHN Reference Guide will guide you through registering your system with Red Hat Network and using its many features. Since Red Hat Network offers a variety of service levels, from the most basic Update module to the most advanced Monitoring package, some content of this guide may be inapplicable to you.
ii Introduction to the Guide The .bashrc file in your home directory contains bash shell definitions and aliases for your own use. The /etc/fstab file contains information about different system devices and file systems. Install the webalizer RPM if you want to use a Web server log file analysis program. application This style indicates that the program is an end-user application (as opposed to system software). For example: Use Mozilla to browse the Web.
Introduction to the Guide iii The output returned in response to the command (in this case, the contents of the directory) is shown in this style. prompt A prompt, which is a computer’s way of signifying that it is ready for you to input something, is shown in this style. Examples: $ # [stephen@maturin stephen]$ leopard login: user input Text that the user has to type, either on the command line, or into a text box on a GUI screen, is displayed in this style.
iv Introduction to the Guide Caution Do not perform routine tasks as root — use a regular user account unless you need to use the root account for system administration tasks. Warning Be careful to remove only the necessary INCLUDE partitions. Removing other partitions could result in data loss or a corrupted system environment. 2. More to Come The Red Hat Network Reference Guide is constantly expanding as new Red Hat Network features and service plans are launched.
Chapter 1.
2 Chapter 1. Red Hat Network Overview Many Red Hat Network terms are used throughout this manual. As you read the Red Hat Network Reference Guide, refer to the Glossary as necessary for an explanation of common terms. Tip For a comparison chart of RHN service levels, refer to http://www.redhat.com/software/rhn/table/. 1.1. Demo The RHN Demo service level is the complimentary service level. All users receive one free subscription to RHN Demo.
Chapter 1. Red Hat Network Overview 3 RHN Management is based upon the concept of an organization. Each Management-level Red Hat customer has the ability to establish users who have administration privileges to system groups. An Organization Administrator has overall control over each Red Hat Network organization with the ability to add and remove systems and users.
4 Chapter 1. Red Hat Network Overview ever an action takes place on a system. These snapshots identify groups, channels, packages, and configuration files. • Custom System Information — Provisioning customers may identify any type of information they choose about their systems.
Chapter 1. Red Hat Network Overview 5 1. Your System Profile available at http://rhn.redhat.com is accessible only with an RHN-verified username and password. 2. A Digital Certificate is written to the client system after registration and is used to authenticate the system during each transaction between the client and Red Hat Network. The file is only readable by the root user on the client system. 3. All notifications and information messages are signed by Red Hat with an electronic signature using GPG.
6 Chapter 1.
Chapter 2. Red Hat Update Agent The Red Hat Update Agent is your connection to Red Hat Network. It enables you to register your systems, create System Profiles, and alter the settings by which your organization and RHN interact. Once registered, your systems can use the Red Hat Update Agent to retrieve the latest software packages from Red Hat. This tool will allow you to always have the most up-to-date Red Hat Linux systems with all security patches, bug fixes, and software package enhancements.
8 Chapter 2. Red Hat Update Agent If you choose the last option and start the application from a shell prompt, you can specify the options in Table 2-1 to the Red Hat Update Agent. To view these options, type the command up2date --help. For example, use the following command to specify the directory in which to download the updated packages (temporarily overriding your saved configuration): up2date --tmpdir=/tmp/up2date Argument Description --configure Configure Red Hat Update Agent options.
Chapter 2. Red Hat Update Agent 9 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. Figure 2-2. Install GPG Key 2.2. Registration Before you begin using Red Hat Network, you need to create a username, password, and System Profile.
10 Chapter 2. Red Hat Update Agent Important If your username is part of a larger organizational account, you should take caution when registering 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. To ensure you retain management of these systems, Red Hat recommends your organization create an activation key associated with a specific system group and grant you permissions to that group.
Chapter 2. Red Hat Update Agent 11 Figure 2-4. Red Hat Privacy Statement 2.2.1. Registering a User Account Before you can create a System Profile, you must create a user account. Red Hat recommends you create your account through the RHN website, but you may also do so through up2date. All that is required is a unique username-password combination and a valid email address. In the screen shown in Figure 2-5, choose a username and password.
12 Chapter 2. Red Hat Update Agent • Must be at least four characters long • Are case-insensitive • Cannot contain any tabs • Cannot contain any line feeds Figure 2-5. Create a User Account You must choose a unique username. If you enter one already in use, you will see an error message (see Figure 2-6). Try different usernames until you find one that has not been used.
Chapter 2. Red Hat Update Agent 13 Figure 2-6. Error: Username Already Exists Most users can leave the Org Info section blank. If you have an existing organization account, enter your organization’s ID and password in the provided text fields. If the values are valid, the system will be added to the organization’s Red Hat Network account. If you have already registered a machine and created a System Profile, you can add a new machine to your account.
14 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. The System Profile information is used by Red Hat Network to determine what software update notifications you receive. 2.2.2.1.
Chapter 2. Red Hat Update Agent • Disk sizes • Mount points 15 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. Optionally, you can enter a computer serial or identification number for the system.
16 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. This RPM list can be modified through the Red Hat Network Web interface or by using the Red Hat Update Agent. Figure 2-9 shows the progress bar you will see while the Red Hat Update Agent gathers a list of the RPM packages installed on your system.
Chapter 2. Red Hat Update Agent 17 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 checkbox beside the package name. For example, Figure 2-11 shows that the Canna-devel and Canna-libs packages have been omitted from the package list.
18 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. Send System Profile to Red Hat Network You will know your System Profile has been successfully sent when you see the Channels screen (Figure 2-14) appear. Refer to Section 2.3.1 Choosing a Software Channel for continued instructions. 2.3.
Chapter 2. Red Hat Update Agent 19 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. Shut down the GUI version and run this command in a terminal (as root), like so: up2date up2date 2.3.1. Choosing a Software Channel The first step is to select the channel from which you want the updated packages to be retrieved.
20 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 (/etc/sysconfig/rhn/systemid) to determine if there are any updated packages available for your system. If there are no updated packages available for your system, the dialog box in Figure 2-16 appears. Click OK to exit the Red Hat Update Agent. Figure 2-16.
Chapter 2. Red Hat Update Agent 21 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. Click Finished when you are finished selecting packages to include.
22 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.
Chapter 2. Red Hat Update Agent 23 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.
24 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. If you configured it to install the packages (the default setting), the selected packages are installed.
Chapter 2. Red Hat Update Agent 25 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.
26 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.
Chapter 2. Red Hat Update Agent 27 Argument Description --arch=architecture Force up2date to install this architecture of the package. Not valid with --update, --list, or --dry-run. --channel=channel Specify which channels to update from using channel labels. --configure Configure Red Hat Update Agent options. Refer to Section 2.4 Configuration for detailed instructions. -d, --download Download packages only; do not install them.
28 Chapter 2. Red Hat Update Agent Argument Description --proxyUser=proxy user ID Specify a username to use with an authenticated HTTP proxy. --register Register (or re-register) this system with RHN. Refer to Section 2.2 Registration for detailed instructions. --serverUrl=server URL Specify an alternate server from which to retrieve packages. --showall List all packages available for download. --show-available List all packages available that are not currently installed.
Chapter 2. Red Hat Update Agent 29 Note GPG keys must be installed for each user. To install the key to use with Red Hat Network, import the key while logged in as root. The method for installing the key varies depending on your version of RPM. Starting with version 4.1, which shipped with Red Hat Enterprise Linux 3, you may import GPG keys using rpm, like so (as root): rpm --import /usr/share/doc/rpm-4.1/RPM-GPG-KEY For older versions of RPM, such as the one that came with Red Hat Enterprise Linux 2.
30 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. To install them, change to the directory that contains the downloaded packages. The default directory is /var/spool/up2date.
Chapter 2. Red Hat Update Agent 31 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. The Red Hat Update Agent Configuration Tool can be started by typing the command up2date-config at a shell prompt (for example, an xterm or a gnome-terminal). 2.4.1.1.
32 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 — if the configuration file has been modified for a package such as apache or squid, do not attemp to upgrade it.
Chapter 2. Red Hat Update Agent 33 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.
34 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. Chapter 2.
Chapter 2. Red Hat Update Agent 35 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 rhnreg_ks as part of their packages. Note Systems running Red Hat Enterprise Linux 2.1 need version 2.9.3-1 or higher of the rhn_register package.
36 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. • A key may specify any number of child channels. For each child channel, subscription is attempted.
Chapter 3. Red Hat Network Daemon The Red Hat Network Daemon (rhnsd) periodically connects to Red Hat Network to check for updates and notifications. The daemon, which runs in the background, is typically started from the initialization scripts in /etc/init.d/rhnsd or /etc/rc.d/init.d/rhnsd. To check for updates, rhnsd runs an external program called rhn_check located in /usr/sbin/. This is a small application that actually makes the network connection to RHN.
38 • Chapter 3. Red Hat Network Daemon the Red Hat Network Daemon is activated and running. You may ensure this by running the following commands: chkconfig --level 345 rhnsd on service rhnsd start If these are correct and your systems still indicate they are not checking in, please contact our technical support team.
Chapter 4. Red Hat Network Alert Notification Tool 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.
40 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. For example, to use the proxy server http://squid.mysite.org on port 3128, enter squid.mysite.org:3128 in the text field.
Chapter 4. Red Hat Network Alert Notification Tool 41 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. The icon changes to the icon after the Errata Updates are applied.
42 Chapter 4.
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. Systems running Red Hat Enterprise Linux 3 have this registration functionality built into the Red Hat Update Agent.
44 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: 0. 1. 2. 3. 4. 5. 6. 7. 8. 9. enableProxyAuth noSSLServerURL oemInfoFile enableProxy networkSetup httpProxy proxyUser serverURL proxyPassword debug No http://xmlrpc.rhn.redhat.com/XMLRPC /etc/sysconfig/rhn/oeminfo No Yes https://xmlrpc.rhn.redhat.
Chapter 5. Red Hat Network Registration Client 45 3. Type the command rhn_register at a shell prompt (for example an XTerm or GNOME terminal) 4. If you are not running the X Window System, type the command rhn_register at a virtual console or remote terminal. Refer to Section 5.7 Text Mode RHN Registration Client for further details. Caution You must use Python 1.5.2-24 or later with Secure Sockets Layer (SSL) support. If not, the information you transfer will not be encrypted.
46 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.
Chapter 5. Red Hat Network Registration Client 47 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.
48 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. However, you will still need to continue with the registration process to create your System Profile.
Chapter 5. Red Hat Network Registration Client 49 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 require entering your organization’s ID and password in the provided text fields. If the values are valid, the system will be added to the organization’s Red Hat Network account.
50 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 notifications. 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. 5.4.2.1.
Chapter 5. Red Hat Network Registration Client 51 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 updated by Red Hat Network. To exclude a package, uncheck the package from the list by clicking the checkbox beside the package name. For example, Figure 5-11 shows that the procmail, procps, and psgml packages have been omitted from the package list.
52 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. If you choose Cancel at this point, no information will be sent. Clicking Next will submit your RHN System Profile.
Chapter 5. Red Hat Network Registration Client 53 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. Send System Profile to Red Hat Network You will know your System Profile has been successfully sent when you see the Registration Finished screen (Figure 5-14). Click Finish to exit the Red Hat Network Registration Client.
54 Chapter 5. Red Hat Network Registration Client Figure 5-14. Registration Finished 5.6. Entitling Your System Now that you have registered your system, it must be entitled before you can receive updated packages. In other words, you must subscribe it to a service level offering. Everyone automatically receives one free 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.
Chapter 5. Red Hat Network Registration Client 55 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.
56 Chapter 5.
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. 6.1. Navigation The top navigation bar is divided into tabs of primary categories containing pages linked from the left navigation bar. 6.1.1.
58 • • • 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. • Buy Now — Purchase Update entitlements and Management entitlements. • Purchase History — View a history of your entitlements, including the expiration date and the number available.
Chapter 6. Red Hat Network Website • • Schedule — Keep track of your scheduled actions. • Pending Actions — List scheduled actions that have not been completed. • Failed Actions — List scheduled actions that have failed. • Completed Actions — List scheduled actions that have been completed. Completed actions can be archived at any time. • Archived Actions — List completed actions that have been selected to archive. Users — • • 59 — View and manage users for your organization.
60 Chapter 6. Red Hat Network Website 6.1.6. Lists The information within most categories is presented as lists. These lists have some common features for navigation. For instance, you can navigate through virtually all lists by clicking the back and next arrows above and below the right side of the table. Some lists also offer the ability to retrieve items alphabetically by clicking the letters above the table. 6.2. Logging into the RHN Website In a Web browser, go to http://rhn.redhat.com.
Chapter 6. Red Hat Network Website 61 Tip 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. Refer to Section 6.4.2 Systems for information on using the Systems pages.
62 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. • Recently Completed Actions — Number of scheduled actions that succeeded. The System Groups section gives you access to the groups of systems you establish.
Chapter 6. Red Hat Network Website 63 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.
64 Chapter 6. Red Hat Network Website 6.3.5.2. Quick Start Guide The Quick Start Guide page contains a brief overview of Red Hat Network and its many features. If you are unfamiliar with RHN, it is recommended you read this guide in its entirety. Topics covered include registering your systems, applying Errata Updates, using one-click updates, and troubleshooting. 6.3.5.3. FAQ The FAQ page lists Frequently Asked Questions and answers to those questions.
Chapter 6. Red Hat Network Website 65 6.3.5.9. Get RHN Software The RHN Software page provides direct links to the Red Hat Update Agent and Red Hat Network Registration Client for every supported distribution. In addition, it describes how to resolve expired Secure Sockets Layers (SSL) certificates if you are using an older version of Red Hat Enterprise Linux that shipped with a certificate that is now expired. 6.4.
66 Chapter 6. Red Hat Network Website Figure 6-3. Systems Overview Clicking the View System Groups link at the top of the Overview page takes you to a similar summary of your system groups. It identifies group status and displays the number of systems contained. Clicking on the number of systems takes you to the Systems tab of the System Group Details page, while clicking on the system name takes you to the Details tab. Refer to Section 6.4.3.3 System Group Details — for more information.
Chapter 6. Red Hat Network Website perform actions on them simultaneously. Refer to Section 6.4.4 System Set Manager — details. • 67 for Status — Shows which type of Errata Alerts are applicable to the system or confirms that it is up-to-date. Some icons are linked to pages providing resolution. For instance, the standard Updates icon is linked to the Upgrade subtab of the packages list, while the Critical Updates icon goes directly to the Update Confirmation page.
68 Chapter 6. Red Hat Network Website 6.4.2.1. All The All page contains the default set of your systems. It displays every system you have permission to manage. A user has permission to manage a system if he is the only user in his organization, if he is an Organization Administrator, or if the system is a member of a group to which he has admin rights. 6.4.2.2. Out of Date The Out of Date page displays the systems that have applicable Errata Alerts that have not been applied. 6.4.2.3.
Chapter 6. Red Hat Network Website 6.4.2.6.1. System Details 69 Details Displays information about the system. This is the first tab you see when you click on a system. It offers direct access to some of the functionality provided in subsequent tabs. For instance, under the System Info heading, a message should appear describing the status of this machine.
70 Chapter 6. Red Hat Network Website schedule a Hardware Profile update for your system. The next time the RHN Daemon connects to RHN, it will update your System Profile with the latest list of hardware. 6.4.2.6.1.4. System Details Details Notes A place to create notes about the system. To add a new note, click the create new note button, type a subject and details, and click the Create button. To modify a note, click on its subject in the list of notes, make your changes, and click the Update button.
Chapter 6. Red Hat Network Website 71 You may then identify a specific user, 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.2.6.1.8. System Details Details Connection The system’s path to the package repository. This tab appears for any system in an organization that has a registered RHN Proxy Server version 3.1 or later.
72 6.4.2.6.3.3. System Details Chapter 6. Red Hat Network Website Packages Upgrade Displays a list of packages that have a new version available based on the package versions in the channels for the system. Click on the latest package name to view its Package Details page. To upgrade packages immediately, select them and click the Upgrade Packages button. If the system is Provisioning-entitled and set to allow remote commands, you then have the option of running a remote command with the package action.
Chapter 6. Red Hat Network Website 6.4.2.6.4.1. System Details Channels 73 Software Software channels provide a well-defined method to determine which packages should be available to a system for installation or upgrade, based upon its operating systems, packages and, functionality. Click a channel name to view its Channel Details page. To modify the child channels associated with this system, use the checkboxes next to the channels and click the Change Subscriptions button.
74 6.4.2.6.5. System Details Chapter 6. Red Hat Network Website Groups — Lists the system’s associated groups and enables you to change these associations. 6.4.2.6.5.1. System Details Groups List/Remove — Lists groups to which the system belongs and enables you to cancel those associations. Only System Group Administrators and Organization Administrator can add and remove the system from groups. To remove the system from groups, select the groups’ checkboxes and click the Leave Selected Groups button.
Chapter 6. Red Hat Network Website 75 Kickstart Kickstart Kickstart 6.4.2.6.7.1. System Details Session Status — Session History — Schedule — The default display of the Kickstart tab, if you’ve scheduled a kickstart, shows where the system’s kickstart stands. Details include the kickstart profile used, its state, and pending and latest actions. Kickstarts that do not complete within approximately two hours will be marked as failed here.
76 Chapter 6. Red Hat Network Website 6.4.2.6.8.2. System Details Events Pending Lists events that are scheduled but have not begun. A prerequisite action is required to complete successfully before a given action will be attempted. If an action has a prerequisite, there will not be a checkbox available to cancel that specific action. Instead, there will be a checkbox next to the prerequisite action; Cancelling the prerequisite action will cause the action in question to fail.
Chapter 6. Red Hat Network Website 77 2. Add systems to system groups. (Refer to Section 6.4.3.2 Adding and Removing Systems in Groups.) 3. Remove systems from system groups. (Refer to Section 6.4.2.6 System Details.) 4. Assign system group permissions to users. (Refer to Section 6.8 Users — .) As shown in Figure 6-4, the System Groups list displays all of your system groups. Figure 6-4.
78 • Chapter 6. Red Hat Network Website Group Name — The name of the group as configured during its creation. The name should be explicit enough to easily differentiate between it and other groups. Clicking on the name of a group takes you to Details tab of its System Group Details page. Refer to Section 6.4.3.3 System Group Details — for more information. • Systems — Total number of systems contained by the group.
Chapter 6. Red Hat Network Website 79 System Set Manager or System Details pages. Refer to Section 6.4.4 System Set Manager — Section 6.4.2.6 System Details, respectively. or Target Systems — Errata — Admins — 6.4.3.3.3. System Group Details Target Systems — List of all systems in your organization. This tab enables you to add systems to the specified system group.
80 Chapter 6. Red Hat Network Website You can access the System Set Manager page in two ways: 1)Add systems and groups from their respective lists to the System Set Manager and click System Set Manager in the left navigation bar. 2)Click Use Group in the System Groups list or Work with Group on the System Group Details page to work with a predefined system group. The System Set Manager page is broken down into tabs: Overview — Systems — Errata — Packages — 6.4.4.1.
Chapter 6. Red Hat Network Website 6.4.4.6. System Set Manager 81 Channels — Options to manage channel associations through the following subtabs: Channels Channels 6.4.4.6.1. System Set Manager Channel Subscriptions — Config Channels — To subscribe or unsubscribe the selected systems in any of the channels, toggle the appropriate radio buttons and click the Alter Subscriptions button. 6.4.4.6.2.
82 Chapter 6. Red Hat Network Website 6.4.4.6.2.3. System Set Manager Channels Config Channels Verify — 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 the name of a file opens its Configuration File Details page. Clicking its system count displays the systems already subscribed to the file.
Chapter 6. Red Hat Network Website 6.4.4.8. System Set Manager 83 Misc — Misc — Tools to update System Profiles and preferences for the system set. Here are the tools broken down by section: Misc Misc Misc Misc Misc Misc Misc 6.4.4.8.1.
84 Chapter 6. Red Hat Network Website • Receive Notifications of Updates/Errata — This setting keeps you abreast of all advisories pertaining to your systems. Anytime an update is produced and released for a system under your supervision, a notification is sent via email. • Include system in Daily Summary — This setting includes the selected systems in a daily summary of system events. (By default, all Management and Provisioning systems are included in the summary.
Chapter 6. Red Hat Network Website 85 In addition, you may entitle all newly registered systems to the Managements service level at once by clicking the Auto-Entitle Newest Servers Now link at the bottom of the page. To use this link, which appears only when new, unentitled systems exist, first make sure you have enough Management entitlements available. If you need to purchase additional entitlements, click the Buy them now link at the top of the page.
86 Chapter 6. Red Hat Network Website • Description — User-defined description to identify the generated activation key. • Usage Limit — The number of times the key can be used to register a system before the activation key is disabled. Leave blank for unlimited use. • Base Channel — The primary channel for the key. Selecting nothing will enable you to select from all child channels, although systems can be subscribed to only those that are applicable.
Chapter 6. Red Hat Network Website 87 6.4.8. Stored Profiles — RHN Provisioning customers can create package profiles through the Profiles subtab of the Packages tab within the System Details page. Those profiles end up here, on the Stored Profiles page, where they may be edited and even deleted. To edit a profile, click its name in the list, alter its name and description, and click the Update Profile. To view software associated with the profile, click the Packages subtab.
88 Chapter 6. Red Hat Network Website For a decription of the innerworkings of the kickstart process, refer to Section 6.4.10.2 Kickstart Explained. 6.4.10.2. Kickstart Explained When a machine is to receive a network-based kickstart, the following events must occur in this order: 1. After being placed on the network and turned on, the machine’s PXE logic broadcasts its MAC address and a request to be discovered. 2.
Chapter 6. Red Hat Network Website 89 for descriptions of the page and its tabs. Take note that RHN supports including separate files within the Partition Details section of the kickstart profile. For instance, you may dynamically generate a partition file based on the machine type and number of disks at kickstart time. This file can be created via %pre script and placed on the system, such as /tmp/part-include.
90 Chapter 6. Red Hat Network Website interface for the box (as identified in the network field on this page). When done, click the Update Kickstart button. Packages — 6.4.10.4.4. Kickstart Details Allows the addition or removal of specific software packages from the kickstart profile. To include packages, enter them in the text field. To remove packages, precede them with with a dash (-). You may also enter entire components and exclude specific packages, such as @ X Window System and -filename.
Chapter 6. Red Hat Network Website 91 Caution When kickstarting systems receiving updates through either an RHN Proxy Server or RHN Satellite Server:, you must import that server’s SSL certificate at the Kickstart/GPG and SSL Keys page and associate it with all relevant kickstart profiles. This association should be made on the GPG and SSL keys subtab of the Kickstart Details page. Not doing this will result in SSL_CERTIFICATE errors, and the kickstart will never report as complete in the RHN website.
92 Chapter 6. Red Hat Network Website GPG and SSL Keys — 6.4.10.8. Kickstart Lists keys and certificates available for inclusion in kickstart profiles and provides a means to create new ones. This is especially important for customers of RHN Satellite Server or RHN Proxy Server because systems being kickstarted by them will need to have the server key imported into RHN and associated with the relevant kickstart profiles.
Chapter 6. Red Hat Network Website 93 Important Although file preservation is useful, it does have limitations. First, each list is limited to a total size of 1 MB. Further, special devices like /dev/hda1 and /dev/sda1 are not supported. Finally, only actual file and directory names may be entered. No regular-expression wildcards can be included. When finished, you may include the file preservation list in the kickstart profile to be used on systems containing those files. Refer to Section 6.4.10.
94 Chapter 6. Red Hat Network Website 6.4.10.12. Integrating Kickstart with PXE In addition to CD-ROM-based installs, RHN supports kickstarts through a Pre-Boot Execution Environment (PXE). This is less error prone than CDs, enables kickstarting from bare metal, and integrates with existing PXE/DHCP environments.
Chapter 6. Red Hat Network Website 95 Figure 6-5. 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 6.5.2.2 Errata Details for more information. 6.5.2. All Errata The All Errata page displays a list of all Errata Alerts released by Red Hat.
96 Chapter 6. Red Hat Network Website • To apply a specific Errata Update to one or more systems, find the update within the Errata lists or by searching. In the table, click on the number of systems affected, which will take you to the Affected Systems tab of the Errata Details page. Then, individually select the systems to be updated and click the Apply Errata button. Double-check the systems to be updated on the confirmation page, then click the Confirm button.
Chapter 6. Red Hat Network Website 97 To help users determine whether an update has been scheduled, a Status column exists within the affected systems table. Possible values are: None, Pending, Picked Up, Completed, and Failed. This column identifies only the latest action related to an Errata. For instance, if an action fails and you reschedule it, this column will show the status of the Errata as Pending only (with no mention of the previous failure).
98 Chapter 6. Red Hat Network Website name takes you to the Details tab. Clicking on the packages number takes you to the Packages tab. And clicking on the systems number takes you to the Subscribed Systems tab. Refer to Section 6.6.1.3 Software Channel Details for details. Figure 6-6. Relevant Channels 6.6.1.2. All Channels The All Channels page can be retrieved by clicking All below Software Channels in the left navigation bar.
Chapter 6. Red Hat Network Website 99 — In addition, a Globally Subscribable checkbox can be seen by Organization Administrators and Channel Administrators. This signifies the default behavior of every channel allowing any user to subscribe systems to it. Unchecking this box and clicking Update causes the appearance of a Subscribers tab, which may then be used to grant certain users subscription permissions to the channel.
100 6.6.1.3.6. Software Channel Details Chapter 6. Red Hat Network Website Target Systems List of entitled systems that are eligible to be subscribed to the channel. This tab appears only for child channels. Use the checkboxes to select the systems, then click the Subscribe button on the bottom right-hand corner. You will receive a success message or be notified of any errors. This can also be accomplished through the Channels tab of the System Details page. Refer to Section 6.4.2.
Chapter 6. Red Hat Network Website 101 6.6.3.2. All ISOs The All ISOs page can be retrieved by clicking All below Easy ISOs in the left navigation bar. It works identically to the Relevant button with one exception; It displays all ISOs available to you through Red Hat Network, regardless of whether you have systems associated with the related channels. Refer to Section 6.6.3 Easy ISOs for instructions on use. 6.6.4.
102 Chapter 6. Red Hat Network Website 9. The action is added to the Pending Actions list under the Schedule tab in the top navigation bar. 6.6.5.2. Package Download If you do not want to schedule a package installation, you can download the packages immediately. If you download the packages, you must install them manually. To download packages through the Systems category, refer to Section 6.4.2.6 System Details. To download individual RPMs and SRPMs through the Channels category, follow these steps: 1.
Chapter 6. Red Hat Network Website 6.6.5.3.1.4. Package Details " Details 103 " File List A list of the files that comprise this package, including their MD5 Sums and sizes. (This information is similar to issuing the command rpm -ql packagename.) " Newer Versions " Installed Systems " Target Systems — 6.6.5.3.2. Package Details List of newer versions of the packages released via Errata Alerts. 6.6.5.3.3. Package Details List of systems with this package installed. 6.6.5.3.4.
104 Chapter 6. Red Hat Network Website • diff — Display differences between configuration files on the system and those associated with it in the central repository. • upload — Send any files from the system to the central repository. This is similar to granting root privileges on the machine. • mtime_upload — Send files modified since a certain date and time from the system to the central repository. • all — Enable all of these modes for configuration management on the system.
Chapter 6. Red Hat Network Website 105 can access tabs of the Configuration Channel Details page. Clicking the number in the Latest Revision column takes you to the Configuration File Details page. Refer to Section 6.6.6.6 Configuration File Details — for instructions. 6.6.6.4. Manage Config Channels $ Quota — The Quota page displays the amount of disk space alloted and used for storing configuration files.
106 Chapter 6. Red Hat Network Website 6.6.6.5.2.3. Configuration Channel Details % Files % Create — Allows you to create a configuration file from scratch within the interface. The fields here work similarly to those on the Upload subtab: Path is the location to which the file will be deployed. The user, group, and mode fields allow you to set the file’s ownership and permissions. Include the actual file in the contents field. When finished, click the Create Config File button.
Chapter 6. Red Hat Network Website 6.6.6.6.4. Configuration File Details & 107 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 — Displays the global config channels for your organization. To copy the latest revision of this file to channels, select the appropriate checkboxes, and click the Copy File button.
108 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).
Chapter 6. Red Hat Network Website 109 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. Schedule - Pending Actions 6.7.2. Failed Actions Actions that could not be completed. If the action returns an error, it will be displayed. 6.7.3. Completed Actions Actions that have succeeded. 6.7.4.
110 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; The action item just moves from the Pending Actions list to the Archived Actions list. • Action — Type of action to perform such as Errata Update or Package Install. Clicking an action name takes you to its Action Details page.
Chapter 6. Red Hat Network Website 111 6.8.1. User Roles To delegate responsibilities within your organization, Red Hat Network provides several roles 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.
112 Chapter 6. Red Hat Network Website Figure 6-8. User List 6.8.2.1. Create User — Click the create new user link on the top-right corner of the page to add new users to the organization. When registering a system, a user account can be created and added to the organization, as well. This should be coordinated by the Organization Administrator. Refer to Section 5.3 Registering a User Account for instructions. On the Create User page, complete all required fields, including all login information.
Chapter 6. Red Hat Network Website ( 113 Details — 6.8.2.2.1. User 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. To assign a user a new role, select the appropriate checkbox.
114 Chapter 6. Red Hat Network Website ) Preferences — 6.8.2.2.5. User Details Modifiable Red Hat Network options. These include: • Email Notification — Determine whether you want to receive email every time an Errata Alert is applicable to one or more systems in your RHN account, as well as daily summaries of system events. • RHN List Page Size — Maximum number of items that will appear in a list on a single page.
Chapter 6. Red Hat Network Website 115 Figure 6-9. Probe Status The Probe Status page displays the probes by state. The following list describes each state and identifies the icons associated with them: • — Critical - The probe has crossed a CRITICAL threshold. • — Warning - The probe has crossed a WARNING threshold. • — The probe is in an unidentifiable state. • — The probe has been scheduled but is unable to run. • — The probe is running successfully.
116 Chapter 6. Red Hat Network Website + Warning — + Unknown — + Pending — + OK — + All — 6.9.1.2. Probe Status The probes that have surpassed their WARNING thresholds. 6.9.1.3. Probe Status The probes that cannot collect the metrics needed to determine probe state. Most but not all probes enter an unknown state when exceeding their timeout period. 6.9.1.4. Probe Status The probes whose data have not been received by RHN.
Chapter 6. Red Hat Network Website 117 Clicking the name of the scout opens its RHNMD SSH Public Key. 6.9.4. Global Config — Collects information that is universally applicable to your Monitoring infrastructure. Typically, the defaults provided will do. Nevertheless, you may use the fields on this page to alter your Monitoring configuration. For instance, you may change your mail exchange server here. This page also allows you to alter the destination of all administrative emails from the Satellite.
118 Chapter 6.
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. A.1.
120 Config channels: Label ----config-channel-17 config-channel-14 Appendix A. Command Line Config Management Tools Name ---config chan 2 config chan 1 A.1.4. Differentiating between Config Files To obtain a difference between the config files deployed on the system and those for it stored by RHN, issue the command: rhncfg-client diff You should see output resembling: --- /tmp/@3603.0.rhn-cfg-tmp 2004-01-13 14:18:31.000000000 -0500 +++ /etc/foo.txt 2003-12-16 21:35:32.
Appendix A. Command Line Config Management Tools 121 When the Red Hat Network Configuration Manager is run as root, it attempts to pull in needed configuration values from the Red Hat Update Agent. When run as something other than root, you may have to make configuration changes within the ~/.rhncfgrc file. The session file is cached in ~/.rhncfg-manager-session to prevent logging in for every command. The default timeout for the Red Hat Network Configuration Manager is 30 minutes.
122 Appendix A. Command Line Config Management Tools Pushing to channel blah Local file >/path/to/file -> remote file /new/path/to/file.txt A.2.2.1. Add Options The following options are applicable to the add mode: Option Description -h, --help Display this list of options and exits. -c=, --channel=CHANNEL_LABEL Required - Use this config channel. -d=, --dest-file=DEST_FILE Conflicts with --topdir - Identify the destination path and filename of a single file.
Appendix A. Command Line Config Management Tools -n=channel-label1 -r=1 -n=channel-label2 -r=1 /path/to/file.txt You should see output resembling: --- /tmp/dest_path/foo.txt 2004-01-13 14:36:41 config channel: blah2 revision: 1 --- /tmp/dest_path/foo.txt 2004-01-13 14:42:42 config channel: blah3 revision: 1 @@ -1 +1,20 @@ -foo +blaaaaaaaaaaaaaaah +-----BEGIN PGP SIGNATURE----+Version: GnuPG v1.0.6 (GNU/Linux) +Comment: For info see http://www.gnupg.
124 Appendix A. Command Line Config Management Tools 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: Available config channels: blah blah2 blah3 config-channel-14 config-channel-17 Note that this does not list local_override or server_import channels. A.2.9.
Appendix A. Command Line Config Management Tools 125 A.2.12. Updating a File in a Channel To create a new revision of a file in a channel (or add the first revision to that channel if none existed before for the given path), issue the command: rhncfg-manager update --channel=channel-label --dest-file=/path/to/file.txt /local/path/to/file You should see output resembling: Pushing to channel blah: Local file blah/tmp/dest_path/foo.txt -> remote file /tmp/dest_path/foo.txt A.2.13.
126 Appendix A.
Appendix B. RHN API Access In an effort to provide customers with added flexibility, RHN makes an application programming interface (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.
128 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 methods, including set_base_channel and set_child_channels. Also like the sid, the cid can be obtained through the RHN website. Just click on the name of a channel and view the end of the URL, something like, "details.pxt?cid=54". B.5. Getting the sgid System groups join servers and channels in having their own IDs.
Appendix B. RHN API Access 129 ############################################################################ # System calls. # ############################################################################ # # # # # # # This next call returns a list of systems available to the user. syntax of this call is described at: The 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.
130 Appendix B.
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 httpd, require the installation of the Red Hat Network Monitoring Daemon (rhnmd).
132 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. C.2.1.
Appendix C. Probes 133 Field Value Application Protocol* http Port* 80 Pathname* /server-status UserAgent* NOCpulse-ApacheUptime/1.0 Username Password Timeout* 15 Critical Maximum Current Requests (number) Warning Maximum Current Requests (number) Critical Maximum Request Rate (events per second) Warning Maximum Request Rate (events per second) Critical Maximum Traffic (kilobytes per second) Warning Maximum Traffic (kilobytes per second) Table C-2. Apache::Traffic settings C.2.3.
134 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.
Appendix C. Probes 135 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* 161 SNMP Version* 1 BEA Domain Admin Server BEA Server Name* myserver Critical Maximum Heap Free Warning Maximum Heap Free Warning Minimum Heap Free Critical Minimum Heap Free Table C-5.
136 Field Appendix C. Probes 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. This probe’s transport protocol is User Datagram Protocol (UDP).
Appendix C. Probes 137 Field Value SNMP Version* 1 BEA Domain Admin Server BEA Server Name* myserver Servlet Name* Critical Maximum High Execution Time Warning Maximum High Execution Time Critical Maximum Execution Time Moving Average Warning Maximum Execution Time Moving Average Table C-8. BEA WebLogic::Servlet settings C.4. General The probes in this section are designed to monitor basic aspects of your systems.
138 • 0 Appendix C. Probes item key =" " 1/0 /item 1 The remote program will need to output some iteration of the following code to STDOUT: 22 22 22 3 3 3 3 perldata hash item key="data" 10 /item item key="status_message" status message here /item /hash /perldata 3 2 33 2 3 The required value for data is the data point to be inserted in the database for time-series trending. The status_message is optional and can be whatever text string is desired with a maximum length of 1024 bytes.
Appendix C. Probes Field 139 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. It collects the following metric: • Remote Service Latency — The time it takes in seconds for the TCP server to answer a connection request.
140 Field Appendix C. Probes Value Send Expect Timeout* 10 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 — SNMP must be running on the monitored system and access to the OID must be enabled to perform this probe.
Appendix C. Probes 141 Field Value Timeout* 15 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. • Write Rate — The amount of data that is written in kilobytes per second.
142 Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe. Field Value File system* /dev/hda1 Timeout* 15 Critical Maximum File System Percent Used Warning Maximum File System Percent Used Critical Maximum Space Used Warning Maximum Space Used Warning Minimum Space Available Critical Minimum Space Available Table C-17. Linux::Disk Usage settings C.5.4.
Appendix C. Probes Field 143 Value Interface* Timeout* 30 Critical Maximum Input Rate Warning Maximum Input Rate Warning Minimum Input Rate Critical Minimum Input Rate Critical Maximum Output Rate Warning Maximum Output Rate Warning Minimum Output Rate Critical Minimum Output Rate Table C-19. Linux::Interface Traffic settings C.5.6. Linux::Load The Linux::Load probe monitors the CPU of a system and collects the following metric: • Load — The average load on the system CPU over various periods.
144 Appendix C. Probes Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe. Field Value Include reclaimable memory no Timeout* 15 Warning Maximum RAM Free Critical Maximum RAM Free Table C-21. Linux::Memory Usage settings C.5.8.
Appendix C. Probes 145 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 (rhnmd) must be running on the monitored system to execute this probe. Field Value Timeout* 15 Critical Maximum Process Count Warning Maximum Process Count Table C-23. Linux::Process Count Total settings C.5.10.
146 Field Appendix C. Probes 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. Linux::Process Health settings C.5.11. Linux::Process Running The Linux::Process Running probe verifies the specified process is functioning properly.
Appendix C. Probes • 147 Swap Free — The percent of swap memory currently free. Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe. Field Value Timeout* 15 Warning Minimum Swap Free Critical Minimum Swap Free Table C-26. Linux::Swap Usage settings C.5.13.
148 Field Appendix C. Probes Value 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. Linux::Users The Linux::Users probe monitors the users of a system and reports the following metric: • Users — The number of users currently logged in. Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe.
Appendix C. Probes 149 be granted read access to your log files. Note that data from the first run of these probes will not be measured against the thresholds to prevent spurious notifications caused by incomplete metric data. Measurements will begin on the second run. C.6.1.
150 Field Appendix C. Probes Value 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 — The size the log file has grown in bytes since the probe last ran. • Output Rate — The number of bytes per minute the log file has grown since the probe last ran.
Appendix C. Probes 151 C.7. MySQL 3.23 - 3.33 The probes in this section monitor aspects of the MySQL database using the mysqladmin binary. No specific user privileges are needed for these probes. C.7.1. MySQL::Database Accessibility The MySQL::Database Accessibility probe tests connectivity through a database account that has no database privileges. If no connection is made then a CRITICAL status results. Field Value Username* Password MySQL Port 3306 Database* mysql Timeout 15 Table C-32.
152 Field Appendix C. Probes Value Username Password MySQL Port* 3306 Timeout 15 Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects Critical Minimum Open Objects Table C-34. MySQL::Open Tables settings C.7.4. MySQL::Query Rate The MySQL::Query Rate probe monitors the MySQL server and collects the following metric: • Query Rate — The average number of queries per second per database server.
Appendix C. Probes 153 Field Value Timeout 15 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.
154 Appendix C. Probes Field Value Expect FTP Username Password FTP Port* 21 Timeout* 10 Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C-38. Network Services::FTP settings C.8.3. Network Services::IMAP Mail The Network Services::IMAP Mail probe determines if it can connect to the IMAP 4 service on the system. Specifying an optional port will override the default port 143.
Appendix C. Probes Field 155 Value 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 ping the monitored system or a specified IP address. It will also check the packet loss and compare the round trip average against the Warning and Critical threshold levels.
156 • Appendix C. Probes 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. The probe will look for the string in the first line of the response from the system. The default is +OK. If the expected string is not found, the probe will return a CRITICAL state.
Appendix C. Probes 157 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) programs on a given IP address. It collects the following metric: • Remote Service Latency — The time it takes in seconds for the RPC server to answer a connection request.
158 Appendix C. Probes Field Value Expect Header HTTP/1 Expect Content UserAgent* NOCpulse-check_http/1.0 Username Password Timeout* 10 HTTPS Port* 443 Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C-45. Network Services::Secure Web Server (HTTPS) settings C.8.10.
Appendix C. Probes 159 This probe supports authentication. Provide a username and password in the appropriate fields to use this feature. Also, the optional Virtual Host field can be used to monitor a separate documentation set located on the same physical machine presented as a standalone server. If your Web server is not configured to use virtual hosts (which is typically the case), you should leave this field blank. If you do have virtual hosts configured, enter the domain name of the first host here.
160 Appendix C. Probes C.9.1. Oracle::Active Sessions The Oracle::Active Sessions probe monitors an Oracle instance and collects the following metrics: • Active • Available Sessions — The V$PARAMETER.PROCESSES. number of active sessions based on the value of Sessions — The percentage of active sessions based on the value of V$PARAMETER.PROCESSES.
Appendix C. Probes Field 161 Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Time Blocking (seconds)* 20 Timeout* 30 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.
162 Appendix C. Probes insensitive. A CRITICAL status is returned if this value is not found. Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe. For this probe to run, the nocpulse user must be granted read access to your log files. Field Value Oracle Hostname or IP address* Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 ORACLE_HOME* Expected DB Name* Timeout* 30 Table C-52.
Appendix C. Probes 163 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 instead sorted using a temporary segment. Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* 30 Critical Maximum Disk Sort Ratio Warning Maximum Disk Sort Ratio Table C-54. Oracle::Disk Sort Ratio settings C.
164 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.
Appendix C. Probes 165 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.
166 Field Appendix C. Probes 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 — The total number of extents for any table. • Available Extents-Any Table — The percentage of available extents for any table.
Appendix C. Probes 167 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. Tablespace is measured in bytes, so extents don’t factor into it directly (though each extension removes available space from the shared pool).
168 Appendix C. Probes C.10.1. RHN Satellite Server::Check Alive The RHN Satellite Server::Check Alive probe is useful in ensuring the viability of your Monitoringenabled Satellite. It reports the following metrics: • Probe Count — The number of probes configured on the Satellite. • Percent OK — The percent of probes in an OK state. • Percent WARNING — The percent of probes in a WARNING state. • Percent CRITICAL — The percent of probes in a CRITICAL state.
Appendix C. Probes 169 Field Value Warning Maximum Space Used Critical Maximum Space Available Warning Maximum Space Available Table C-64. RHN Satellite Server::Disk Space settings C.10.3. 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 it takes to fully execute a probe.
170 Appendix C. Probes 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-67. RHN Satellite Server::Latency settings C.10.6. RHN Satellite Server::Load The RHN Satellite Server::Load probe monitors the CPU load on a Satellite and collects the following metric: • Load — The load average on the CPU for a 1-, 5-, and 15-minute period.
Appendix C. Probes • 171 Blocked — The number of processes that have been switched to the waiting queue and waiting state. • Child — The number of processes spawned by another process already running on the machine. • Defunct — The number of processes that have terminated (either because they have been killed by a signal or have called exit()) and whose parent processes have not yet received notification of their termination by executing (some form of) the wait() system call.
172 Appendix C. Probes • CPU Usage — The CPU usage percent for a given process. • Child Process Groups — The number of child processes spawned from the specified parent process. A child process inherits most of its attributes, such as open files, from its parent. • Threads — The number of running threads for a given process. A thread is the basic unit of CPU utilization, and consists of a program counter, a register set, and a stack space. A thread is also called a lightweight process.
Appendix C. Probes Field 173 Value Critical Number Running Minimum Table C-73. RHN Satellite Server::Process Running settings C.10.12. RHN Satellite Server::Swap The RHN Satellite Server::Swap probe monitors the percent of free swap space available on a Satellite. A CRITICAL status results if the value falls below the Critical threshold. A WARNING status results if the value falls below the Warning threshold. Field Value Critical Minimum Swap Percent Free Warning Minimum Swap Percent Free Table C-74.
174 Appendix C.
Glossary A Action A task that is scheduled by a system administrator using Red Hat Network to be performed on one or more client systems. For example, an action can be scheduled to update the kernel packages on all the systems within a selected group. Activation Key RHN Management and Provisioning customers can generate activation keys through the RHN website.
176 Glossary Child Channel A child channel is a Channel associated with a Base Channel but contains extra packages. Client System See Registered System . D Digital Certificate A client component in XML format that is stored in the /etc/sysconfig/rhn/systemid file on registered systems. Red Hat Network verifies this certificate to authenticate the registered system before each connection. This certificate is issued by Red Hat and passed to the system as part of the registration process.
Glossary 177 team tests new packages they are placed on the Red Hat Public File Server and on the Red Hat Network Server and an Errata is generated. Errata Alert RHN Errata Alert that updated packages based on Red Hat Errata are available for one or more systems within an organization. There are three types of Errata Alerts: Security Alerts, Bug Fix Alerts, and Enhancement Alerts. M Management One of the RHN service level offerings.
178 Glossary R 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 (rhnsd) that periodically polls Red Hat Network for scheduled actions.
Glossary 179 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 . System Directory The System Directory section of Red Hat Network allows an organization to divide its client systems into system groups.
180 Glossary
Index A account deactivate, 62 action completed systems, 110 details, 110 failed systems, 110 in progress systems, 110 activation key, 85 deleting, 86 disabling, 86 editing, 86 activation keys creating, editing, and deleting, 85 multiple use, 86 registration, 34 using, 35 addresses change, 62 Apache probes, 132 Processes, 132 Traffic, 132 Uptime, 133 application programming interface API, 127 B base channel, 97 C changing email address, 113 changing password, 113 Channel Entitlements, 100 Channel List, 97
182 viewing list of applicable errata, 94 Errata notifications automatic updates, 4 Process Counts by State, 144 G TCP Connections by State, 147 General probes, 137 Remote Program, 137 Remote Program with Data, 137 SNMP Check, 138 TCP Check, 139 UDP Check, 139 Uptime (SNMP), 140 getting started, 5 GNU Privacy Guard, 5 Users, 148 Process Health, 145 Process Running, 146 Swap Usage, 146 Virtual Memory, 148 List Navigation explanation of, 60 LogAgent Log Pattern Match, 149 Log Size, 150 probes nocpulse,
183 N navigation, 57 Network Services DNS Lookup, 153 FTP, 153 IMAP Mail, 154 Mail Transfer (SMTP), 154 Ping, 155 POP Mail, 155 probes, 153 Remote Ping, 156 RPCService, 157 Secure Web Server (HTTPS), 157 SSH, 158 Web Server (HTTP), 158 notes about systems, 70 O Oracle Active Sessions, 160 Availability, 160 Blocking Sessions, 160 Buffer Cache, 161 Client Connectivity, 161 Data Dictionary Cache, 162 Disk Sort Ratio, 163 Idle Sessions, 163 Index Extents, 163 Library Cache, 164 Locks, 165 probes, 159 Redo Log
184 Blocking Sessions, 160 Buffer Cache, 161 Client Connectivity, 161 Data Dictionary Cache, 162 Disk Sort Ratio, 163 Idle Sessions, 163 Index Extents, 163 Library Cache, 164 Locks, 165 Redo Log, 165 Table Extents, 166 Tablespace Usage, 166 TNS Ping, 167 RHN Satellite Server Check Alive, 168 Disk Space, 168 Execution Time, 169 Interface Traffic, 169 Latency, 169 Load, 170 Probe Count, 170 Process Counts, 170 Process Health, 171 Process Running, 172 Processes, 171 Swap, 173 Users, 173 WebLogic Execute Queue,
185 initial description, 1 installing GPG keys, 28 installing packages, 24 log file, 30 registering a hardware profile, 14 registering a package profile, 15 registering a System Profile, 14 registering an organization account, 13 registering with, 9 setup and use, 18 starting, 7 synchronizing system profile, 30 reference guide bug reporting, iv conventions, i introduction to the, i registering with activation keys, 34 Registration, 43 as part of an organization, 48 Configuration, 43 Email notification, 47 H
186 Channels, 97 Config Channel List, 103 Configuration Channel Details, 105 Configuration File Details, 106 custom system information, 87 Errata, 94 Errata Search, 97 Help, 63 kickstart profiles, 87 logging in, 60 Monitoring, 114 navigation bar, 57 overview, 57 Purchase History, 63 Relevant Errata, 94 Schedule, 108 Software Channel Details, 98 Software Search, 101 stored profiles, 87 System Details, 68 System Entitlements, 84 System Group List, 76 System Groups, 76 System List, 66 System Search, 85 Systems
