Page 1 Red Hat Network 3.6 Reference Guide...
Page 2 All other trademarks referenced herein are the property of their respective owners. The GPG ﬁngerprint 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........................60 6.2. Logging into the RHN Website..................60 6.3.
Page 5 6.9.4. Global Conﬁg — ..................117 A. Command Line Conﬁg Management Tools ................119 A.1. Red Hat Network Conﬁguration Client ..............119 A.1.1. Listing Conﬁg Files..................119 A.1.2. Getting a Conﬁg File..................119 A.1.3. Viewing Conﬁg Channels ................119 A.1.4. Differentiating between Conﬁg Files ............. 120 A.1.5.
Page 6 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 .................. 145 C.5.11. Linux::Process Running ................146 C.5.12. Linux::Swap Usage ..................146 C.5.13. Linux::TCP Connections by State..............147 C.5.14.
Page 7 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............... 173 Glossary ............................175 Index..............................181...
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 ﬁle in your home directory contains bash shell deﬁnitions and aliases for your own .bashrc use. ﬁle contains information about different system devices and ﬁle systems. /etc/fstab Install the RPM if you want to use a Web server log ﬁle 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 reﬂects 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 ﬁnd it? Have you ever tried to ﬁnd 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 ﬁnd an RPM but instead found only the source ﬁles 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 ﬁelds. 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
Chapter 1. Red Hat Network Overview ever an action takes place on a system. These snapshots identify groups, channels, packages, and conﬁguration ﬁles. Custom System Information — Provisioning customers may identify any type of information they • choose about their systems. This differs from the more rigorous System Proﬁle information and the completely arbitrary Notes in that it allows you to develop speciﬁc keys of your choosing and then assign searchable values for that key to each Provisioning-entitled system.
Page 17: Before You Begin
Chapter 1. Red Hat Network Overview 1. Your System Proﬁle available at http://rhn.redhat.com is accessible only with an RHN-veriﬁed username and password. 2. A Digital Certiﬁcate 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 ﬁle is only readable by the root user on the client system.
Page 18 Chapter 1. Red Hat Network Overview Package Name Description Package Name Description Provides the Red Hat Network Registration Client program and the rhn_register text mode interface 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...
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 Proﬁles, and alter the settings by which your organization and RHN interact. Once registered, your systems can use the Red Hat Update Agent to retrieve the latest software packages from Red Hat.
Page 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. Conﬁgure 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 Proﬁle.
Page 24 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).
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 Proﬁle
Chapter 2. Red Hat Update Agent Figure 2-7. Register a User Account Once satsﬁed with the information supplied, click Forward to continue. 2.2.2. Registering a System Proﬁle Now that you have a user account, you can create a System Proﬁle 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 proﬁle 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 ﬁnd it more helpful.
Page 28 Chapter 2. Red Hat Update Agent you must include packages in your proﬁle 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 Proﬁle By default, all RPM packages in your RPM database are included in your System Proﬁle 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 Proﬁle Figure 2-13 shows the progress bar you will see while your proﬁle 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 Certiﬁcate ) 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 ﬁnished 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 Conﬁgure Red Hat Update Agent options. Refer to Section 2.4 --configure Conﬁguration 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 ﬁrst, 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: Conﬁguration
Chapter 2. Red Hat Update Agent =yOVZ -----END PGP PUBLIC KEY BLOCK----- Save the text ﬁle 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 Conﬁguration Tool You must be root to run the Red Hat Update Agent Conﬁguration Tool. If you start the Red Hat Update Agent Conﬁguration 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 conﬁguration ﬁle has been modiﬁed —...
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 deﬁne which packages to exclude from the list of updated RPM packages according to the package name or ﬁle name (see Figure 2-26). To deﬁne a set of packages to be excluded according to the package name, enter a character string including wild cards (*) in the Add new text ﬁeld 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 speciﬁed, 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
Red Hat Network. Make certain: your client is conﬁgured correctly. • your system can communicate with RHN via SSL (port 443). You may test this by running the • following command from a shell prompt: telnet xmlrpc.rhn.redhat.com 443...
Page 50 Chapter 3. Red Hat Network Daemon the Red Hat Network Daemon is activated and running. You may ensure this by running the follow- • ing commands: chkconfig --level 345 rhnsd on service rhnsd start If these are correct and your systems still indicate they are not checking in, please contact our technical support team.
Page 51: Red Hat Network Alert Notiﬁcation Tool
Chapter 4. Red Hat Network Alert Notiﬁcation Tool The Red Hat Network Alert Notiﬁcation Tool is a notiﬁer 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: Notiﬁcation Icons
Chapter 4. Red Hat Network Alert Notiﬁcation Tool Figure 4-2. HTTP Proxy Conﬁguration If your network connection requires you to use an HTTP Proxy Server to make HTTP connec- tions, on the Proxy Conﬁguration screen, type your proxy server in the text ﬁeld with the for- mat HOST:PORT.
Page 53: Viewing Updates
Chapter 4. Red Hat Network Alert Notiﬁcation 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 Notiﬁcation 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 Proﬁle. 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 conﬁguration 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 proﬁle 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 Proﬁle. The System Proﬁle is essential if you wish to receive update notiﬁcations 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 Proﬁle, 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 Proﬁle.
Page 61: Registering A System Proﬁle
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 ﬁelds.
Page 62: Software System Proﬁle
Chapter 5. Red Hat Network Registration Client Figure 5-8. System Proﬁle - Hardware 5.4.2. Software System Proﬁle The software System Proﬁle consists of a list of RPM packages for which you wish to receive notiﬁ- 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 Proﬁle By default, all RPM packages in your RPM database are included in your System Proﬁle 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 Proﬁle 5.5. Finishing Registration As seen in Figure 5-12, the last step of registration is to conﬁrm that you want to send your System Proﬁle to the Red Hat Network.
Page 65 Chapter 5. Red Hat Network Registration Client Figure 5-12. Finished Collecting Information for System Proﬁle Figure 5-13 shows the progress bar you will see while your proﬁle 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 notiﬁcations 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 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 •...
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 conﬁgure Red Hat Network options, including: Email Notiﬁcations — 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.5.7. Outage Policy The Outage Policy page identiﬁes 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 notiﬁed of emergency and other unscheduled outages. 6.3.5.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.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) certiﬁcates if you are using an older version of Red Hat Enterprise Linux that shipped with a certiﬁcate that is now expired.
Page 78: Systems
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 sum- mary of your system groups. It identiﬁes 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.
Page 79 Chapter 6. Red Hat Network Website perform actions on them simultaneously. Refer to Section 6.4.4 System Set Manager — details. Status — Shows which type of Errata Alerts are applicable to the system or conﬁrms 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 Conﬁrmation page.
Page 80: System Details
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.
Page 81 Chapter 6. Red Hat Network Website 6.4.2.6.1. System Details Details Displays information about the system. This is the ﬁrst 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.
Page 82 Chapter 6. Red Hat Network Website schedule a Hardware Proﬁle update for your system. The next time the RHN Daemon connects to RHN, it will update your System Proﬁle with the latest list of hardware. 6.4.2.6.1.4. System Details Details Notes A place to create notes about the system.
Page 83 Chapter 6. Red Hat Network Website You may then identify a speciﬁc 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 Com- mand.
Page 84 Chapter 6. Red Hat Network Website 6.4.2.6.3.3. System Details 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.
Page 85 Chapter 6. Red Hat Network Website 6.4.2.6.4.1. System Details Channels Software Software channels provide a well-deﬁned 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.
Page 86 Chapter 6. Red Hat Network Website 6.4.2.6.5. System Details 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 Sys- tem Group Administrators and Organization Administrator can add and remove the system from groups.
Page 87 Chapter 6. Red Hat Network Website 6.4.2.6.7.1. System Details Kickstart Session Status — The default display of the Kickstart tab, if you’ve scheduled a kickstart, shows where the system’s kickstart stands. Details include the kickstart proﬁle used, its state, and pending and latest actions. Kickstarts that do not complete within approximately two hours will be marked as failed here.
Page 88: System Groups
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 speciﬁc action.
Page 89 Chapter 6. Red Hat Network Website 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.
Page 90 Chapter 6. Red Hat Network Website Group Name — The name of the group as conﬁgured 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.
Page 91: System Set Manager
Chapter 6. Red Hat Network Website System Set Manager or System Details pages. Refer to Section 6.4.4 System Set Manager — Section 6.4.2.6 System Details, respectively. 6.4.3.3.3. System Group Details Target Systems — Target Systems — List of all systems in your organization. This tab enables you to add systems to the speciﬁed system group.
Page 92 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 predeﬁned system group.
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 Conﬁg Channels Verify — Use this subtab to validate conﬁguration ﬁles on the selected systems against copies in your central repository on RHN. The table lists the conﬁguration ﬁles associated with any of the selected systems. Clicking the name of a ﬁle opens its Conﬁguration File Details page.
Page 95 Chapter 6. Red Hat Network Website 6.4.4.8. System Set Manager Misc — Misc — Tools to update System Proﬁles and preferences for the system set. Here are the tools broken down by section: 6.4.4.8.1. System Set Manager Misc System Proﬁle Updates — Clicking Update Hardware Proﬁle, then the Conﬁrm Refresh button schedules a hardware proﬁle update.
Page 96: System Entitlements
Chapter 6. Red Hat Network Website Receive Notiﬁcations of Updates/Errata — This setting keeps you abreast of all advisories per- • taining to your systems. Anytime an update is produced and released for a system under your supervision, a notiﬁcation is sent via email. Include system in Daily Summary —...
Page 97: Advanced Search
Chapter 6. Red Hat Network Website 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, ﬁrst make sure you have enough Management entitlements available.
Page 98 Chapter 6. Red Hat Network Website Description — User-deﬁned 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 —...
Page 99: Stored Proﬁles
Chapter 6. Red Hat Network Website 6.4.8. Stored Proﬁles — RHN Provisioning customers can create package proﬁles through the Proﬁles subtab of the Packages tab within the System Details page. Those proﬁles end up here, on the Stored Proﬁles page, where they may be edited and even deleted.
Page 100 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.
Page 101 Chapter 6. Red Hat Network Website for descriptions of the page and its tabs. Take note that RHN supports including separate ﬁles within the Partition Details section of the kickstart proﬁle. For instance, you may dynamically generate a partition ﬁle based on the machine type and number of disks at kickstart time. This ﬁle can be created via %pre script and placed on the system, such as .
Page 102 Chapter 6. Red Hat Network Website interface for the box (as identiﬁed in the network ﬁeld on this page). When done, click the Update Kickstart button. 6.4.10.4.4. Kickstart Details Packages — Allows the addition or removal of speciﬁc software packages from the kickstart proﬁle. To include packages, enter them in the text ﬁeld.
Page 103 Chapter 6. Red Hat Network Website Caution When kickstarting systems receiving updates through either an RHN Proxy Server or RHN Satellite Server:, you must import that server’s SSL certiﬁcate at the Kickstart/GPG and SSL Keys page and associate it with all relevant kickstart proﬁles. This association should be made on the GPG and SSL keys subtab of the Kickstart Details page.
Page 104 Chapter 6. Red Hat Network Website 6.4.10.8. Kickstart GPG and SSL Keys — Lists keys and certiﬁcates available for inclusion in kickstart proﬁles 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 proﬁles.
Page 105 Chapter 6. Red Hat Network Website Important Although ﬁle preservation is useful, it does have limitations. First, each list is limited to a total size of 1 MB. Further, special devices like are not supported. Finally, only actual /dev/hda1 /dev/sda1 ﬁle and directory names may be entered.
Page 106: Errata
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 Envi- ronment (PXE). This is less error prone than CDs, enables kickstarting from bare metal, and integrates with existing PXE/DHCP environments.
Page 107: All Errata
Chapter 6. Red Hat Network Website 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.
Page 108 Chapter 6. Red Hat Network Website To apply a speciﬁc Errata Update to one or more systems, ﬁnd 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.
Page 109: Advanced Search
Chapter 6. Red Hat Network Website 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 identiﬁes 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).
Page 110 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.
Page 111 Chapter 6. Red Hat Network Website — In addition, a Globally Subscribable checkbox can be seen by Organization Administrators and Channel Administrators. This signiﬁes the default behavior of every channel allowing any user to sub- scribe 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.
Page 112: 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 113: Package Search
Chapter 6. Red Hat Network Website 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 chan- nels.
Page 114 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.
Page 115: Manage Conﬁg Channels
Chapter 6. Red Hat Network Website 6.6.5.3.1.4. Package Details Details File List A list of the ﬁles that comprise this package, including their MD5 Sums and sizes. (This information is similar to issuing the command rpm -ql packagename 6.6.5.3.2. Package Details Newer Versions List of newer versions of the packages released via Errata Alerts.
Page 116 Chapter 6. Red Hat Network Website diff — Display differences between conﬁguration ﬁles on the system and those associated with it • in the central repository. upload — Send any ﬁles from the system to the central repository. This is similar to granting root •...
Page 117 Chapter 6. Red Hat Network Website can access tabs of the Conﬁguration Channel Details page. Clicking the number in the Latest Revi- sion column takes you to the Conﬁguration File Details page. Refer to Section 6.6.6.6 Conﬁguration File Details — for instructions.
Page 118 Chapter 6. Red Hat Network Website 6.6.6.5.2.3. Conﬁguration Channel Details Files Create — Allows you to create a conﬁguration ﬁle from scratch within the interface. The ﬁelds here work simi- larly to those on the Upload subtab: Path is the location to which the ﬁle will be deployed. The user, group, and mode ﬁelds allow you to set the ﬁle’s ownership and permissions.
Page 119 Chapter 6. Red Hat Network Website 6.6.6.6.4. Conﬁguration File Details Copy — A list of conﬁguration channels that may receive a copy of the ﬁle. To copy the ﬁle to a channel, select the channel’s checkbox, and click the Copy File button. Copy to Conﬁg Channel —...
Page 120: 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 Proﬁle, 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 121: 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 122: 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 123: User Roles
Chapter 6. Red Hat Network Website 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 dif- ferences between them: User —...
Page 124 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 ﬁelds before clicking Send.
Page 125 Chapter 6. Red Hat Network Website 6.8.2.2.1. User Details Details — The username, ﬁrst name, last name, email address, and user roles for the user. All of this information is modiﬁable. 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 126: Monitoring
Chapter 6. Red Hat Network Website 6.8.2.2.5. User Details Preferences — Modiﬁable Red Hat Network options. These include: Email Notiﬁcation — 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.
Page 127 Chapter 6. Red Hat Network Website Figure 6-9. Probe Status The Probe Status page displays the probes by state. The following list describes each state and iden- tiﬁes the icons associated with them: — Critical - The probe has crossed a CRITICAL threshold. •...
Page 128: Notiﬁcation
Chapter 6. Red Hat Network Website 6.9.1.2. Probe Status Warning — The probes that have surpassed their WARNING thresholds. 6.9.1.3. Probe Status Unknown — 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.
Page 129: Global Conﬁg
Chapter 6. Red Hat Network Website Clicking the name of the scout opens its RHNMD SSH Public Key. 6.9.4. Global Conﬁg — Collects information that is universally applicable to your Monitoring infrastructure. Typically, the defaults provided will do. Nevertheless, you may use the ﬁelds on this page to alter your Monitoring conﬁguration.
Page 130 Chapter 6. Red Hat Network Website...
Page 131: Command Line Conﬁg Management Tools
Appendix A. Command Line Conﬁg Management Tools In addition to the options provided in the RHN website, Red Hat Network offers two command line tools for managing conﬁguration ﬁles: the Red Hat Network Conﬁguration Client and the Red Hat Network Conﬁguration 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 132: Differentiating Between Conﬁg Files
Appendix A. Command Line Conﬁg Management Tools Config channels: Label Name ----- ---- config-channel-17 config chan 2 config-channel-14 config chan 1 A.1.4. Differentiating between Conﬁg Files To obtain a difference between the conﬁg ﬁles deployed on the system and those for it stored by RHN, issue the command: rhncfg-client diff You should see output resembling:...
Page 133: Creating A Conﬁg Channel
Appendix A. Command Line Conﬁg Management Tools When the Red Hat Network Conﬁguration Manager is run as root, it attempts to pull in needed conﬁguration values from the Red Hat Update Agent. When run as something other than root, you may have to make conﬁguration changes within the ﬁle.
Page 134: Differentiating Between Latest Conﬁg Files
Appendix A. Command Line Conﬁg 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 Display this list of options and exits. --help Required - Use this conﬁg channel.
Page 135: Downloading All Files In A Channel
Appendix A. Command Line Conﬁg 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)
Page 136: Removing A File From A Channel
Appendix A. Command Line Conﬁg Management Tools A.2.8. Listing All Conﬁg Channels To list all of your organization’s conﬁguration 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.
Page 137: Updating A File In A Channel
Appendix A. Command Line Conﬁg Management Tools A.2.12. Updating a File in a Channel To create a new revision of a ﬁle in a channel (or add the ﬁrst 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...
Page 138 Appendix A. Command Line Conﬁg Management Tools...
Page 139: 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 140: 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 141 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 142 Appendix B. RHN API Access...
Page 143: Probes
Appendix C. Probes As described in Section 6.9 Monitoring — , systems entitled with Monitoring can have probes applied against them to constantly conﬁrm 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 144: 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 145: 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 Trafﬁc (kilobytes per second) Warning Maximum Trafﬁc (kilobytes per second) Table C-2.
Page 146: 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 speciﬁed 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 147: 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 148: 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 149: 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 150: 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 151: 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 speciﬁed port number.
Page 152: 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 identiﬁer (OID) to obtain this value. The only error status it will return is UNKNOWN. Requirements —...
Page 153: 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 154: 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 155: 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 Trafﬁc settings C.5.6.
Page 156: 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 157: 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 158: 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 159: 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 160: Linux::users
Appendix C. Probes Field 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 —...
Page 161: Logagent::log Pattern Match
Appendix C. Probes be granted read access to your log ﬁles. Note that data from the ﬁrst run of these probes will not be measured against the thresholds to prevent spurious notiﬁcations caused by incomplete metric data. Measurements will begin on the second run. C.6.1.
Page 162: Logagent::log Size
Appendix C. Probes Field 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 ﬁle growth and collects the following metrics: Size — The size the log ﬁle has grown in bytes since the probe last ran. •...
Page 163: Mysql 3.23 - 3.33
Appendix C. Probes C.7. MySQL 3.23 - 3.33 The probes in this section monitor aspects of the MySQL database using the binary. No mysqladmin speciﬁc 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.
Page 164: Mysql::query Rate
Appendix C. Probes Field Value Username Password MySQL Port* 3306 Timeout Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects Critical Minimum Open Objects Table C-34. MySQL::Open Tables settings C.7.4. MySQL::Query Rate The MySQL::Query Rate probe monitors the MySQL server and collects the following metric: Query Rate —...
Page 165: Network Services
Appendix C. Probes Field Value 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 166: Network Services::imap Mail
Appendix C. Probes Field Value Expect Username Password FTP Port* Timeout* 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.
Page 167: Network Services::ping
Appendix C. Probes Field 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 the monitored system or a ping speciﬁed IP address.
Page 168: Network Services::remote Ping
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.
Page 169: Network Services::rpcservice
Appendix C. Probes 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 — The time it takes in seconds for the RPC server to answer a connection •...
Page 170: Network Services::ssh
Appendix C. Probes Field Value 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 speciﬁed port and collects the following metric: Remote Service Latency —...
Page 171: Oracle 8I And 9I
Appendix C. Probes This probe supports authentication. Provide a username and password in the appropriate ﬁelds to use this feature. Also, the optional Virtual Host ﬁeld 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 conﬁgured to use virtual hosts (which is typically the case), you should leave this ﬁeld blank.
Page 172: 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 173: 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 174: 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 ﬁles.
Page 175: 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 176: 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 ﬁeld contains a default value of % that will match any index name. Field Value Oracle SID*...
Page 177: 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 conﬂict.
Page 178: 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 179: 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 180: Rhn Satellite Server::disk Space
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 Monitoring- enabled Satellite. It reports the following metrics: Probe Count — The number of probes conﬁgured on the Satellite. •...
Page 181: Rhn Satellite Server::execution Time
Appendix C. Probes 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 —...
Page 182: Rhn Satellite Server::load
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.
Page 183: Rhn Satellite Server::processes
Appendix C. Probes 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 •...
Page 184: Rhn Satellite Server::process Running
Appendix C. Probes CPU Usage — The CPU usage percent for a given process. • Child Process Groups — The number of child processes spawned from the speciﬁed parent process. • A child process inherits most of its attributes, such as open ﬁles, from its parent. Threads —...
Page 185: Rhn Satellite Server::swap
Appendix C. Probes Field 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.
Page 186 Appendix C. Probes...
Page 187: Glossary
An Errata Alert that pertains to a bug ﬁx. 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 188 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 veriﬁcation. 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 189 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 190 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 191 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 ﬁrst Service Level offering for Red Hat Network. Software Manager is now known as RHN Update .
Page 192 Glossary...
Page 193: Index
Index obtaining, 5 Conﬁg Channel List, 103 conﬁg channels details, 105, 106 global, 104 account list of, 103 deactivate, 62 Conﬁg Channels and Files action Conﬁg Channel List, 103 completed systems, 110 conﬁg management details, 110 system preparation, 103 failed systems, 110 Conﬁguration in progress systems, 110 Channel List...
Page 194 viewing list of applicable errata, 94 Process Counts by State, 144 Errata notiﬁcations Process Health, 145 automatic updates, 4 Process Running, 146 Swap Usage, 146 TCP Connections by State, 147 Users, 148 General Virtual Memory, 148 probes, 137 Remote Program, 137 List Navigation Remote Program with Data, 137 explanation of, 60...
Page 195 preferences change, 63 navigation, 57 probe Network Services guidelines, 131 DNS Lookup, 153 probe list FTP, 153 Apache IMAP Mail, 154 Processes, 132 Mail Transfer (SMTP), 154 Trafﬁc, 132 Ping, 155 Uptime, 133 POP Mail, 155 General probes, 153 Remote Program, 137 Remote Ping, 156 Remote Program with Data, 137 RPCService, 157...
Page 196 Blocking Sessions, 160 Buffer Cache, 161 quality assurance Client Connectivity, 161 overview, 4 Data Dictionary Cache, 162 Quick Search Disk Sort Ratio, 163 explanation of, 59 Idle Sessions, 163 Index Extents, 163 Library Cache, 164 Locks, 165 reactivating Redo Log, 165 systems, 70 Table Extents, 166 Red Hat Enterprise Linux 2.1...
Page 197 initial description, 1 installing GPG keys, 28 Schedule, 108 installing packages, 24 Scheduled Actions log ﬁle, 30 Action Details, 110 registering a hardware proﬁle, 14 Actions List, 109 registering a package proﬁle, 15 Archived Actions, 109 registering a System Proﬁle, 14 Completed Actions, 109 registering an organization account, 13 Failed Actions, 109...
Page 198 Entitlements, 84 Channels, 97 entitling, 84 Conﬁg Channel List, 103 overview, 65 Conﬁguration Channel Details, 105 Conﬁguration File Details, 106 searching, 85 custom system information, 87 System Details, 68 Errata, 94 System List, 66 Errata Search, 97 Systems Overview, 65 Help, 63 viewing a list of, 66 kickstart proﬁles, 87...

Red Hat NETWORK 3.6 Reference Manual

Quick Links

Related Manuals for Red Hat NETWORK 3.6

Summary of Contents for Red Hat NETWORK 3.6

Table of Contents