Page 1 Red Hat Network Satellite 5.1.1 Reference Guide Red Hat Network Satellite...
Page 2 Reference Guide Red Hat Network Satellite 5.1.1 Reference Guide Red Hat Network Satellite Edition 5.1.1...
Page 3: Table Of Contents
Introduction to the Guide 1. More to Come ........................ xi 1.1. Send in Your Feedback ..................xii 1. Red Hat Network Overview 1.1. Update ......................... 2 1.2. Management ........................ 2 1.3. Provisioning ......................... 3 1.4. Monitoring ........................4 1.5. Errata Notifications and Scheduled Package Installations ..........4 1.6.
Page 4 Reference Guide 5.5. Finishing Registration ....................52 5.6. Entitling Your System ....................54 5.7. Text Mode RHN Registration Client ................55 6. Red Hat Network Website 6.1. Navigation ........................57 6.1.1. Entitlement Views .................... 57 6.1.2. Categories and Pages ..................58 6.1.3.
Page 5 6.5. Errata ........................112 6.5.1. Relevant Errata ....................113 6.5.2. All Errata ....................... 113 6.5.3. Advanced Search ..................115 6.6. Channels ........................116 6.6.1. Software Channels ..................116 6.6.2. Package Search .................... 119 6.6.3. Manage Software Channels ................120 6.7. Configuration ......................121 6.7.1.
Page 6 Reference Guide 6.10.4. Scout Config Push — ..........................141 6.10.5. General Config — ..........................142 6.11. Satellite Tools ......................142 6.11.1. Satellite Tools Organizations ..............142 6.11.2. Satellite Tools Satellite Configuration ............147 6.12. Help ........................148 6.12.1. Help Desk ....................148 6.12.2.
Page 7 8.3. Working With Your Virtual Systems ................171 8.3.1. Logging into Virtual Systems Directly via SSH ..........171 8.3.2. Gaining Console Access Via the Host ............. 171 8.3.3. Installing Software Via the Satellite Web Interface ..........172 8.3.4. Installing Software Via Yum From the Virtual System ........172 8.3.5.
Page 8 Reference Guide B.3. Determining the sid ....................199 B.4. Viewing the cid ......................199 B.5. Getting the sgid ....................... 199 B.6. Channel Labels ......................200 B.7. Sample API Script ....................200 C. Probes C.1. Probe Guidelines ..................... 203 C.2. Apache 1.3.x and 2.0.x .................... 204 C.2.1.
Page 9 C.8.2. Network Services::FTP .................. 224 C.8.3. Network Services::IMAP Mail ................. 225 C.8.4. Network Services::Mail Transfer (SMTP) ............225 C.8.5. Network Services::Ping .................. 225 C.8.6. Network Services::POP Mail ................226 C.8.7. Network Services::Remote Ping ..............227 C.8.8. Network Services::RPCService ............... 227 C.8.9.
Page 11: Introduction To The Guide
The Red Hat Network Reference Guide is constantly expanding as new Red Hat Network features and service plans are launched. HTML and PDF versions of this and other manuals are available within the Help section of the RHN website and at http://www.redhat.com/docs/. Note...
Page 12: Send In Your Feedback
Management Guide, and RHN Satellite Release Notes. Translated documentation is available at rhn.redhat.com/help/ 1.1. Send in Your Feedback If you would like to make suggestions about the Red Hat Network Reference Guide, please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component Documentation_Reference_Guide (Product: Red Hat Network Satellite, Version: 510).
Page 13: Red Hat Network Overview
Chapter 1. Red Hat Network Overview Have you ever read about a new version of a software package and wanted to install it but could not find it? Have you ever tried to find an RPM through an Internet search engine or an RPM repository and been linked to an unknown site? Have you ever tried to find an RPM but instead found only source files that you had to compile yourself?
Page 14: Update
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. http://www.redhat.com/software/ For a comparison chart of RHN service levels, refer to rhn/table/. 1.1. Update The RHN Update service is ideal for a user with one Red Hat Enterprise Linux system or a small number of Red Hat Enterprise Linux systems.
Page 15: Provisioning
Provisioning Hat Login page, click Create a new Business Login. After creating a business account, you may add users within your organization to it. The Red Hat Network features available to you depend on the subscription level for each Red Hat Enterprise Linux system.
Page 16: Monitoring
Chapter 1. Red Hat Network Overview • Custom System Information — Provisioning customers may identify any type of information they choose about their registered systems. This differs from System Profile information, which is generated automatically, and the Notes, which are unrestricted, in that the Custom System Information allows you to develop specific keys of your choosing and assign searchable values for that key to each Provisioning-entitled system.
Page 17: Security, Quality Assurance, And Red Hat Network
RPM packages are signed with Red Hat's GNU Privacy Guard (GPG) signature to ensure authenticity. Red Hat Network incorporates the following security measures: 1. Your System Profile, available at http://rhn.redhat.com, is accessible only with an RHN-verified username and password. 2. A Digital Certificate is written to the client system after registration and is used to authenticate the system during each transaction between the client and Red Hat Network.
Page 18 Chapter 1. Red Hat Network Overview If the Red Hat Network Registration Client is installed, it will return something similar to: rhn_register-2.9.3-1 The version number might differ slightly. If you do not have the Red Hat Network Registration Client installed, the command will return: package rhn_register is not installed Table 1.1, “Red Hat Network Packages”...
Page 19: Red Hat Update Agent
Chapter 2. Red Hat Update Agent The Red Hat Update Agent is your connection to Red Hat Network. It enables you to register your systems, create System Profiles, and alter the settings by which your organization and RHN interact. Once registered, your systems can use the Red Hat Update Agent to retrieve the latest software packages from Red Hat.
Page 20 Chapter 2. Red Hat Update Agent • At a shell prompt (for example, an xterm or gnome-terminal), type the command up2date. If you choose the last option and start the application from a shell prompt, you can specify the options Table 2.1, “Graphical Update Agent Options”.
Page 21 Starting the Red Hat Update Agent is actually the General tab of the Red Hat Update Agent Configuration Tool. Refer to Section 2.4, “Configuration” for detailed instructions. Figure 2.1. Configure Proxy Server Figure 2.2, The second dialog box to appear prompts you to install the Red Hat GPG key, as shown in “Install GPG Key”.
Page 22: Registration
Chapter 2. Red Hat Update Agent 2.2. Registration Before you begin using Red Hat Network, you must create a username, password, and System Profile. Upon launch, the Red Hat Update Agent senses whether these tasks have been accomplished. If not, it guides you through the registration process. If you ever need to force the Red Hat Update Agent into registration mode, such as to re-register an existing system, you may do so by issuing the following command at a shell prompt: up2date --register...
Page 23: Registering A User Account
2.2.1. Registering a User Account Before you create a System Profile, you must create a user account. Red Hat recommends that you do so through the website at https://rhn.redhat.com/newlogin/, but you may also do so via Red Hat Update Agent (up2date).
Page 24 Chapter 2. Red Hat Update Agent Figure 2.4. Red Hat Login Screen New users must select the I don't have a Red Hat login. I need to create one. radio button and click the Forward button. Add details about yourself and your business to the screen shown in Figure 2.5, “Create a User Account”, and identify the methods by which you may be reached.
Page 25: Activate
Activate Note You must choose a unique username. If you enter one already in use, you will see an error message. Try different usernames until you find one that has not been used. Complete all fields marked by an asterisk (*). The address and email addresses are required so that Red Hat may communicate with you regarding your account.
Page 26 Chapter 2. Red Hat Update Agent • CPU model • CPU speed • Amount of RAM • PCI devices • Disk sizes • Mount points The software System Profile consists of a list of RPM packages for which you wish to receive notifications.
Page 27: Channels
Channels Figure 2.6. Activate Figure 2.7, “Sending System Profile to Red Hat Network” shows the progress bar displayed as the System Profile is sent. Figure 2.7. Sending System Profile to Red Hat Network 2.2.3. Channels Red Hat Update Agent next displays all package channels to which you have access. The channels you select from this screen must match the base operating system of the system you are registering.
Page 28 Chapter 2. Red Hat Update Agent Figure 2.8. Channels Red Hat Update Agent now compares the packages in your RPM database with those available from Figure 2.9, “Fetching package list” the Channel you selected. The progress bar shown in is displayed during this process.
Page 29: Packages Flagged To Be Skipped
Packages Flagged to be Skipped 2.2.4. Packages Flagged to be Skipped The next step in the initial update is the selection of files to be skipped. Any packages checked here will not be downloaded and updated by the Red Hat Update Agent. This screen is displayed whenever packages are available that are currently selected to be ignored.
Page 30 Chapter 2. Red Hat Update Agent Figure 2.11. Available Package Updates...
Page 31: Retrieving Packages
Retrieving Packages Figure 2.12. Example Errata Advisory 2.2.6. Retrieving Packages The Red Hat Update Agent tests the packages you selected to be certain that the requirements of each RPM are met. If any additional packages are required, Red Hat Update Agent displays an error message.
Page 32: Installing Packages
Chapter 2. Red Hat Update Agent Figure 2.13. Retrieving Packages 2.2.7. Installing Packages The packages must be installed after downloading them via the Red Hat Update Agent. If you chose not to install the packages via the Red Hat Update Agent, skip to Section 2.3.2, “Manual Package Installation”...
Page 33 Installing Packages Figure 2.14. Installing Packages When the Red Hat Update Agent has finished downloading the desired packages (and installing them Figure 2.15, “All Finished”. Click Finish to exit if you chose the install option), it displays the screen in the Red Hat Update Agent.
Page 34: Command Line Version
Chapter 2. Red Hat Update Agent Figure 2.15. All Finished 2.3. Command Line Version If you are not running X, you can still run the Red Hat Update Agent from a virtual console or remote terminal. If you are running X but want to use the command line version, you can force it not to display the graphical interface with the following command: up2date --nox The command line version of the Red Hat Update Agent allows you to perform advanced functions...
Page 35 Command Line Version Option Description Briefly describe the available options. -?, --usage List the available options and exit. -h, --help Force up2date to install this architecture of the package. --arch=architecture Not valid with --update, --list, or --dry-run. Specify from which channels to update using channel --channel=channel labels.
Page 36 Chapter 2. Red Hat Update Agent Option Description Update packages associated with this System Profile. -p, --packages Specify an HTTP proxy to use. --proxy=proxy URL Specify a password to use with an authenticated HTTP --proxyPassword=proxy proxy. password Specify a username to use with an authenticated HTTP --proxyUser=proxy user ID proxy.
Page 37: Installing The Red Hat Gpg Key
For older versions of RPM, such as the one that came with Red Hat Enterprise Linux 2.1, use the gpg command (as root): /usr/bin/gpg --import /usr/share/rhn/RPM-GPG-KEY https://www.redhat.com/security/team/ To download the Red Hat GPG key first, you may obtain it from key.html .
Page 38: Manual Package Installation
Chapter 2. Red Hat Update Agent ZMAPJWTs2bB+0QaXxUgWlwW84GVf2rA6RSbvMLTbDjTH8t7J1RGP9zAqu8SgraTA QbQdao6TNxVt+ohGBBMRAgAGBQI+3LjCAAoJECGRgM3bQqYOf5MAoIjiJDe+hDOj 9+jlR0qDs9lIi/C2AJ9SBBfd4A8hyR4z3lY7e0LzjWF51LkCDQQ7+9O3EAgA8tMs xdUmuTfA+X78fMXh7LCvrL4Hi28CqvNM+Au81XJjDLNawZvpVmFlMmd9h0Xb5Jt2 BZWLR13rcDUByNdw1EWhVAzCz6Bp9Z3MIDhcP00iIBctIHn7YP9fi5vV0G03iryT XE01mhWoBlC233wr3XHwsqxFfZzaCZqqNKTl0+PNfEAIzJRgtYiW8nzFTPpIR05E oRn6EvmQfayOF2uYDX9Sk//lOD7T7RLtKjM/hPW/9NoCGwwROaG+VUzVv4aelh1L dJGEjpFtdxcrOUMD8xbkuGMznu0mpDI+J2BUDh5n57yOyEMaGrQ0jfY1ZqdqDvZg osY1ZHa6KlmuCWNTnwADBQf/XYhCicp6iLetnPv6lYtyRfFRpnK98w3br+fThywC t81P2nKv8lio6OsRbksGc1gX8Zl6GoHQYfDe7hYsCHZPoWErobECFds5E9M7cmzV TTyNTvrELrs07jyuPb4Q+mHcsYPILGR3M+rnXKGjloz+05kOPRJaBEBzP6B8SZKy QNqEfTkTYU4Rbhkzz/UxUxZoRZ+tqVjNbPKFpRraiQrUDsZFbgksBCzkzd0YURvi CegO2K7JPKbZJo6eJA10qiBQvAx2EUijZfxIKqZeLx40EKMaL7Wa2CM/xmkQmCgg Hyu5bmLSMZ7cxFSWyXOst78dehCKv9WyPxHV3m4iANWFL4hGBBgRAgAGBQI7+9O3 AAoJEF5UgINlDViCKWcAoMCeYStWVKXJTytzHEL6Wl8rXr8WAKCHuapJIA4/eFsf 4ciWtjY8cO0v8Q== =yOVZ -----END PGP PUBLIC KEY BLOCK----- Save the text file and import it into your keyring using the method applicable to your version of RPM. 2.3.2.
Page 39: Configuration
Configuration log/up2date.1, /var/log/up2date.2, and /var/log/up2date.3. The log files store actions performed by the Red Hat Update Agent such as when your RPM database is opened, when it connects to Red Hat Network to retrieve information from your System Profile, which packages are downloaded, which packages are installed using the Red Hat Update Agent, and which packages are deleted from your system after installation.
Page 40 Chapter 2. Red Hat Update Agent Figure 2.16. General Settings In addition, RHN Proxy and Satellite customers have the option of selecting Red Hat Network Servers here. These customers should refer to the RHN Client Configuration Guide for detailed instructions. 2.4.1.2.
Page 41 Using the Red Hat Update Agent Configuration Tool Figure 2.17. Retrieval/Installation Settings Figure 2.17, “Retrieval/Installation The following package retrieval options can be selected (see Settings”): • Do not install packages after retrieval — download selected RPM packages to the desired directory and ignore the installation preferences •...
Page 42 Chapter 2. Red Hat Update Agent • Override version stored in System Profile — override the Red Hat Linux version in your System Profile • Package storage directory — change the directory where packages are downloaded; the default location is /var/spool/up2date/ 2.4.1.3.
Page 43: Command Line Version
16. enableProxyAuth No 17. retrieveSource No 18. versionOverride 19. headerFetchCount 10 20. networkRetries 5 21. enableProxy No 22. proxyPassword 23. noSSLServerURL http:// xmlrpc.rhn.redhat.com/XMLRPC 24. keepAfterInstall No 25. proxyUser 26. removeSkipList ['kernel*'] 27. useGPG Yes 28. gpgKeyRing /etc/ sysconfig/rhn/up2date-keyring.gpg 29. httpProxy 30. headerCacheSize 40 31.
Page 44 Chapter 2. Red Hat Update Agent Note Systems running Red Hat Enterprise Linux 2.1 need version 2.9.3-1 or higher of the rhn_register package. It is highly recommended that you obtain the latest version before using activation keys. Before using an activation key you must first generate one through Section 6.4.6, “Activation Keys —...
Page 45: Registering A System To An Organization
Registering a System to an Organization channels that contain packages unsuitable for the system. For example, a Red Hat Enterprise Linux 2.1 system cannot be subscribed to the Red Hat Enterprise Linux 3 channel. The unique Digital Certificate for the system is generated on the system in the file /etc/sysconfig/ rhn/systemid.
Page 47: Red Hat Network Daemon
• your system can communicate with RHN via SSL (port 443). You may test this by running the following command from a shell prompt: telnet xmlrpc.rhn.redhat.com 443 • the Red Hat Network Daemon is activated and running. You may ensure this by running the...
Page 48 Chapter 3. Red Hat Network Daemon 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 49: Red Hat Network Alert Notification Tool
Chapter 4. Red Hat Network Alert Notification Tool The Red Hat Network Alert Notification Tool is a notifier that appears on the panel and alerts users when software package updates are available for their systems. The list of updates is retrieved from the RHN Servers.
Page 50 Chapter 4. Red Hat Network Alert Notification Tool Figure 4.2. HTTP Proxy Configuration If your network connection requires you to use an HTTP Proxy Server to make HTTP connections, on the Proxy Configuration screen, type your proxy server in the text field with the format HOST:PORT.
Page 51: Notification Icons
Notification Icons You can also configure the Red Hat Network Alert Notification Tool to ignore specific packages. To select these packages, click on the applet and select the Ignored Packages tab. 4.2. Notification Icons Table 4.1, “Red Hat The applet displays a different icon, depending on the status of the updates. Network Alert Notification Tool Icons”...
Page 52: Applying Updates
Chapter 4. Red Hat Network Alert Notification Tool Figure 4.3. Available Updates 4.4. Applying Updates If the system is registered with RHN and entitled to a service offering, you can apply the Errata Updates with the Red Hat Update Agent. To launch the Red Hat Update Agent, click on the applet, and then click on the Launch up2date button.
Page 53: Red Hat Network Registration Client
Chapter 5. Red Hat Network Registration Client Before you begin using Red Hat Network, you must create a username, password, and System Profile. The Red Hat Network Registration Client walks you through this process. Warning Only systems running Red Hat Enterprise Linux 2.1 need to use the Red Hat Network Registration Client before starting the Red Hat Update Agent.
Page 54 XMLRPC 2. oemInfoFile /etc/sysconfig/rhn/oeminfo 3. enableProxy No 4. networkSetup Yes 5. httpProxy 6. proxyUser 7. serverURL https:// xmlrpc.rhn.redhat.com/XMLRPC 8. proxyPassword 9. debug No Enter number of item to edit <return to exit, q to quit without saving>: Enter the number of the item to modify and enter a new value for the option. When finished changing your configuration, press Enter to save your changes and exit.
Page 55: Starting The Red Hat Network Registration Client
Starting the Red Hat Network Registration Client If you require a proxy username and password, set enableProxyAuth to Yes to enable username/ password authentication for the proxy, and set proxyUser and proxyPassword to the appropriate username and password for the proxy. To bypass SSL, change the protocol for serverURL from https to http in the /etc/sysconfig/ rhn/rhn_register file.
Page 56 Yes. If you overwrite an existing system registration, you can delete the unused profile via the website at https://rhn.redhat.com. Figure 5.3. Warning: This System Already Registered The opening screen for the Red Hat Network Registration Client provides a brief overview of the Figure 5.4, “Welcome...
Page 57 Starting the Red Hat Network Registration Client Figure 5.4. Welcome Screen Figure 5.5, “Red Hat Privacy Statement”). The Red Hat is committed to protecting your privacy (see information gathered during the Red Hat Network registration process is used to create a System Profile.
Page 58: Registering A User Account
Chapter 5. Red Hat Network Registration Client Figure 5.5. Red Hat Privacy Statement 5.3. Registering a User Account Before you can create a System Profile, you must create a user account. The only required information in this section is a unique username, password, and a valid email address. Figure 5.7, “Create a Unique Username and Password”, you must choose In the screen shown in...
Page 59 Registering a User Account Figure 5.6. Error: Username Already Exists Note If you are already a member of redhat.com, you can use the same user name and password. However, you must continue with the registration process to create your System Profile.
Page 60: Registering A System Profile
Chapter 5. Red Hat Network Registration Client Figure 5.7. Create a Unique Username and Password Most users can leave the Org Info section blank. If you have an existing organization account, work with your Satellite Administrator to ensure that your system is added to that account.This requires entering your organization's ID and password in the provided text fields.
Page 61 Hardware System Profile • Hostname • IP address • CPU model • CPU speed • Amount of RAM • PCI devices • Disk sizes • Mount points Figure 5.8, “System Profile The next step is choosing a profile name for your system as shown in Hardware”.
Page 62: Software System Profile
Chapter 5. Red Hat Network Registration Client 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 displays a list of all RPM packages listed in the RPM database on your system and then allows you to customize the list by deselecting packages.
Page 63 Software System Profile 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 Figure 5.11, “Choose which RPM Packages the checkbox beside the package name.
Page 64: Finishing Registration
Chapter 5. Red Hat Network Registration Client Figure 5.11. Choose which RPM Packages to Exclude from System Profile 5.5. Finishing Registration Figure 5.12, “Finished Collecting Information for System Profile”, the last step of As seen in 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 is sent.
Page 65 Finishing Registration Figure 5.12. Finished Collecting Information for System Profile Figure 5.13, “Send System Profile to Red Hat Network” shows the progress bar displayed while your profile is sent. This process may take some time depending on your connection speed. Figure 5.13.
Page 66: 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. http://rhn.redhat.com To entitle a system, go to and log in using the same username and password you just used in the Red Hat Network Registration Client.
Page 67: Text Mode Rhn Registration Client
Text Mode RHN Registration Client Note Removing a required entitlement (such as Provisioning) will not cancel a previously scheduled action (such as a kickstart). As you change the selected entitlements for your systems, the number of available entitlements is updated at the bottom of the screen. 5.7.
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: Categories And
Chapter 6. Red Hat Network Website Icon Entitlement Provisioning Monitoring Table 6.1. Entitlement Icons If no icon follows a category, page, or tab label within this chapter, the area described is available to all Red Hat Network users. If an icon does follow, the associated entitlement is needed. Remember that Provisioning inherits all of the functions of Management.
Page 71 Categories and Pages • System Groups — — List your system groups. Create additional groups. • System Set Manager — — Perform various actions on collective sets of systems, including scheduling errata updates, package management, listing and creating new groups, and managing channel entitlements. •...
Page 72 Chapter 6. Red Hat Network Website • Software Channels — View a list of all software channels and those applicable to your systems. • Package Search — Search packages using all or some portion of the package name, description, or summary, with support for limiting searches to supported platforms. •...
Page 73: Errata Alert Icons
Errata Alert Icons • Probe Suites — — Manage your monitoring infrastructure using suites of monitoring probes that apply to one or more assigned systems. • Scout Config Push — — Displays the status of your monitoring infrastructure. • Satellite Tools (visible only to Satellite administrators) — List, create, and manage one or more Satellite organizations, from which the Satellite administrator can assign channel entitlements, create and assign administrators for each organization, and other tasks.
Page 74: Quick Search
6.2. Logging into the RHN Website Use a web browser to navigate to http://rhn.redhat.com. RHN displays the login page shown below unless one of two things is true: • You have recently logged into your account at http://1www.redhat.com.
Page 75 Figure 6.4. RHN Website If you have not registered a system yet or do not have a redhat.com account, create a new account by following the Learn More link, then selecting Create Login on the resulting page. After creating a Chapter 2, Red Hat Update new user account, you must register a system before using RHN.
Page 76: Your Rhn
Chapter 6. Red Hat Network Website Once you have accepted the agreements and pressed the Continue button, RHN displays the Your RHN page. 6.3. Your RHN After logging into the web interface of Red Hat Network, the first page to appear is Your RHN. This page contains important information about your systems, including summaries of system status, actions, and Errata Alerts.
Page 77: Your Account
Remember, if you change your Red Hat Network password (the one used to log into RHN and redhat.com), you will not see your new one as you type it for security reasons. Also for security, your password is represented by 12 asterisks no matter how many characters it actually contains. Replace...
Page 78: Your Preferences
Chapter 6. Red Hat Network Website 6.3.1.1. Addresses The Addresses page allows you to manage your mailing, billing and shipping addresses, as well as the associated phone numbers. Just click Edit this address below the address to be modified, make the changes, and click Update.
Page 79: Locale Preferences
Locale Preferences 6.3.3. Locale Preferences The Your RHN Locale Preferences page allows each user to tailor their RHN interface to the local time and their preferred language. Select the appropriate timezone from the Time Zone dropdown box, then click the Save Preferences button to apply the selection. When the language preference is set to Use Browser Settings, RHN uses the language preference from the user's browser (such as Firefox) to determine which language to use for the web interface.
Page 80 Chapter 6. Red Hat Network Website The two virtualization entitlements specifically apply to host systems. Guest systems that exist on unregistered hosts are treated the same as any physical system — each guest consumes a channel and a system entitlement. 6.3.4.1.
Page 81: Systems
Systems 6.4. Systems If you click the Systems tab on the top navigation bar, the Systems category and links appear. The pages in the Systems category allow you to select systems so that you can perform actions on them and create System Profiles. 6.4.1.
Page 82 Chapter 6. Red Hat Network Website • — Critical Errata available, update strongly recommended • — Updates available and recommended • — System is locked; Actions prohibited • — System is being kickstarted • — Updates have been scheduled • —...
Page 83 Systems • Entitlement — Whether or not the system is entitled and at what service level. Links in the left navigation bar below Systems enable you to select and view predefined sets of your systems. All of the options described above can be applied within these pages. 6.4.2.1.
Page 84 Chapter 6. Red Hat Network Website have been scheduled, this is considered a check-in. If you are seeing a message indicating checkins are not taking place, the RHN client on your system is not successfully reaching Red Hat Network for some reason.
Page 85 Systems • Configuration • Provisioning — • Monitoring — • Groups • Events The following sections discuss these tabs and their sub-tabs in detail. 6.4.2.9.1. System Details Details This page is not accessible from any of the standard navigation bars. However, clicking on the name of a system anywhere in the web interface brings you to this page.
Page 86 Chapter 6. Red Hat Network Website Hostname The hostname as defined by the client system. This information is often found in /etc/hostname for Red Hat Enterprise Linux systems. IP Address The IP address of the client. Kernel The kernel that is installed and operating on the client system. Registered The date and time at which the system registered with RHN and created this profile.
Page 87 Systems the system, associate that system with a System Group and assign it a Section 6.4.3, “System Groups — System Group Administrator. Refer to ” for more information about System Groups. It is also possible to lock multiple systems via the System Set Manager. Section 6.4.4.12.4, “System Set Manager Misc Lock Systems —...
Page 88 Chapter 6. Red Hat Network Website Notifications Indicates the the notification options for this system. You can choose whether you wish to receive email notifying you of available errata updates for this system. In addition, you may choose to include Management-entitled systems in the daily summary email. Auto Errata Update Indicates whether this system is configured to accept updates automatically.
Page 89 Systems The remaining fields record the physical address at which the system is stored. To confirm any changes to these fields, click the Update Properties button. Note Many of these properties can be set for multiple systems at once through the Section 6.4.4, “System Set Manager —...
Page 90 Chapter 6. Red Hat Network Website Unlike typical activation keys, which are not associated with a specific system ID, keys created here do not show up within the Activation Keys page. Warning When kickstarting a system with its existing RHN profile, the kickstart profile uses the system-specific activation key created here to re-register the system and return its other RHN settings.
Page 91 Systems 6.4.2.9.1.9. System Details Details Satellite Displays the certificate of an active Red Hat Network. You can deactivate an old certificate here and upload a new one if necessary. This tab requires a Provisioning entitlement. For detailed information on activating a Satellite, refer to the RHN Satellite Installation Guide. 6.4.2.9.2.
Page 92 Chapter 6. Red Hat Network Website 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 93 Systems 6.4.2.9.3. System Details Configuration — This tab and its subtabs, which do not appear without a Provisioning entitlement, assist in managing the configuration files associated with the system. These configuration files may be managed solely for the current system, or may be distributed widely via a Configuration Channel. The following section describe these and other available options on the System Details Configuration subtabs.
Page 94 Chapter 6. Red Hat Network Website Note If you click on the Filename of a (system override) file, you can edit its contents. The Overrides column identifies the config file from which channel will apply if the system is unsubscribed from the config channel that provides the file now. For instance, if a system has '/etc/ foo' from channel 'bar' and '/etc/foo' from channel 'baz' is in the Overrides column, then unsubscribing from channel 'bar' will mean that the file from channel 'baz' will be applicable.
Page 95 Systems 6.4.2.9.3.6. System Details Configuration Sandbox This subtab allows you to manipulate configuration files without deploying them. This sandbox provides you with an area in which to experiment with files without affecting your systems. To add files, click the import new files link, enter the path to the file on you local system, and click the Add button.
Page 96 Chapter 6. Red Hat Network Website Each subtab provides the specific changes that will be made to the system during the rollback: • group memberships • channel subscriptions • installed packages • configuration channel subscriptions • configuration files • snapshot tags When satisfied with the reversion, return to the Rollback subtab and click the Rollback to Snapshot button.
Page 97 Systems If a guest system has not registered to the Satellite, this information appears as plain text in the table. If you have System Group Administrator responsibilities assigned for your guest systems, it is possible that a user could see the message You do not have permission to access this system within the table.
Page 98 Chapter 6. Red Hat Network Website remove the system from groups. Non-admins just see a Review this system's group membership page. To remove the system from groups, select the groups' checkboxes and click the Leave Selected Groups button. Click on a group's name to go to its System Group Details page.
Page 99: System Groups
System Groups — 6.4.2.9.5.4.2. System Details Events History The default display of the Events tab lists the type and status of events that have failed, occurred or are occurring. To view details of an event, click its summary in the System History list. To again view the table, click Return to history list at the bottom of the page.
Page 100 Chapter 6. Red Hat Network Website • — Critical Errata available, update strongly recommended • — Updates available and recommended • Group Name — The name of the group as configured during its creation. The name should be explicit enough to easily differentiate between it and other groups.
Page 101 System Groups — ” for more information. The System Group Details page is broken down into tabs: 6.4.3.3.1. System Group Details Details — Provides the group name and group description. To change this information, click Edit Group Properties, make your changes in the appropriate fields, and click the Modify Details button. 6.4.3.3.2.
Page 102 Chapter 6. Red Hat Network Website 6.4.3.3.6. System Group Details Probes — List all probes assigned to systems in the system group. The State shows the status of the probe. Click the individual System for details on the probe and to make changes to the probe configuration. Click the Probe to generate a customizable report on the monitoring.
Page 103 ystem Set Manager — 6.4.4.2. System Set Manager Systems — List of systems now selected. To remove systems from this set, select them and click the Remove button. 6.4.4.3. System Set Manager Errata — List of Errata Updates applicable to the current system set. Click the number in the Systems column to see to which systems in the System Set Manager the given Errata applies.
Page 104 Chapter 6. Red Hat Network Website 6.4.4.4.3. System Set Manager Packages Remove — A list of all the packages installed on the selected systems that might be removed. Multiple versions appear if systems in the System Set Manager have more than one version installed. Select the packages to be deleted, then click the Remove Packages button.
Page 105 ystem Set Manager — 6.4.4.9.1. System Set Manager Channels Channel Subscriptions — To subscribe or unsubscribe the selected systems in any of the channels, toggle the appropriate checkboxes and click the Alter Subscriptions button. Keep in mind that subscribing to a channel uses a channel entitlement for each system in the selected group.
Page 106 Chapter 6. Red Hat Network Website 6.4.4.10.3. System Set Manager Configuration Subscribe to Channels — Subscribe systems to configuration channels according to order of preference. This tab is available only to Satellite Administrators and Configuration Administrators. Enter a number in the Rank column to subscribe to a channel.
Page 107 ystem Set Manager — 6.4.4.11.1. System Set Manager Provisioning Kickstart — Use this subtab to re-install Red Hat Enterprise Linux on the selected Provisioning-entitled systems. To schedule kickstarts for these systems, select a distribution, identify the type (IP address or manual), and click Continue.
Page 108 Chapter 6. Red Hat Network Website 6.4.4.12.2. System Set Manager Misc Custom System Information — Click Set a custom value for selected systems followed by the name of a key to allow you to provide values for all selected systems. Enter the information and click the Set Values button. Click Remove a custom value from selected systems followed by the name of a key to allow you to remove values for all selected systems.
Page 109 Advanced Search — • Include system in Daily Summary — This setting includes the selected systems in a daily summary of system events. (By default, all Management and Provisioning systems are included in the summary.) These system events are actions that affect packages, such as scheduled Errata Updates, system reboots, or failures to check in.
Page 110 Chapter 6. Red Hat Network Website Warning In addition to the fields listed below, RHN Satellite Server customers may also populate the Key field itself. This user-defined string of characters can then be supplied with rhnreg_ks to register client systems with the Satellite. Do not insert commas in the key.
Page 111 Activation Keys — Figure 6.6. Activation Keys After creating the unique key, it appears in the list of activation keys along with the number of times it has been used. Note that only Activation Key Administrators can see this list. At this point, you may associate child channels and groups with the key so that systems registered with it automatically subscribe to them.
Page 112 Chapter 6. Red Hat Network Website 6.4.6.2. Using Multiple Activation Keys at Once — Provisioning customers should note that multiple activation keys can be included at the command line or in a single kickstart profile. This allows you to aggregate the aspects of various keys without recreating a new key specific to the desired systems, simplifying the registration and kickstart processes while slowing the growth of your key list.
Page 113 Kickstart — Click create new key at the upper-right corner of the page. Enter a descriptive label and description, such as Asset and Precise location of each system, and click the Create Key. The key will then show up in the custom info keys list. Once the key exists, you may assign a value to it through the Custom Info tab of the System Details page.
Page 114 Enterprise Linux on multiple machines, making it ideal for network and system administrators. The Red Hat Enterprise Linux System Administration Guide contains an in-depth discussion of kickstart and is available here: http://1www.redhat.com/1docs/1manuals/1enterprise/. 6.4.9.1.1. Kickstart Explained When a machine is to receive a network-based kickstart, the following events must occur in this order:...
Page 115 Kickstart — 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. If a static IP address is not being used, the DHCP server recognizes the discovery request and extends an offer of network information needed for the new machine to boot.
Page 116 Chapter 6. Red Hat Network Website 6.4.9.1.3. Building Bootable Kickstart ISOs While you can schedule a registered system to be kickstarted to a new operating system and package profile, it is also useful to be able to kickstart a system that is not registered with RHN, or does not yet have an operating system installed.
Page 117 Kickstart — To use this method, make sure your systems have network interface cards (NIC) that support PXE, install and configure a PXE server, ensure DHCP is running, and then place the appropriate files on an HTTP server for deployment. Once the kickstart profile has been created, use the URL from the Kickstart Details page, as for CD-ROM-based installs.
Page 118 3. On the third page, select a root password for the system. Be sure to follow the password recommendations from the Password Security section of the Red Hat Enterprise Linux Security Guide, available at http://1www.redhat.com/1docs/1manuals/1enterprise/. The final stage of the wizard presents the Kickstart Details Details tab.
Page 119 Kickstart — Change the base channel Select from the available base channels, such as Red Hat Enterprise Linux AS version 4. Satellite customers see a list of all base channels that are currently synced to their Satellite. File Location The exact location from which the kickstart tree is mounted. This value is determined when the profile is created.
Page 120 Chapter 6. Red Hat Network Website 6.4.9.3.7. System Details Partitioning — From this sub-tab, you can indicate the partitions that you wish to be created during installation. For example: partition /boot --fstype=ext3 --size=200 partition swap --size=2000 partition pv.01 --size=1000 --grow volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 -- grow 6.4.9.3.8.
Page 121 If you would like to know what package groups are available, and what packages they contain, refer to the RedHat/base/ file of your kickstart tree. Satellite customers will most likely locate this file here: /var/www/satellite/rhn/ kickstart/<kickstart label>/RedHat/base/comps.xml.
Page 122 Chapter 6. Red Hat Network Website 1. Click the add new kickstart script link in the upper right 2. Enter the path to the scripting language used to create the script, such as /usr/bin/perl 3. Enter the full script in the large text box 4.
Page 123 Kickstart — To develop a new key/certificate, click the create new stored key/cert link in the upper-right corner of the page. Enter a description, select the type, upload the file, and click the Update Key button. Note that a unique description is required. Important The GPG key you upload to RHN must be in ASCII format.
Page 124: Errata
A summary of each erratum is provided in list form. This view instantly informs you of the type, severity (for Security Updates), and subject of the erratum, as well as the number of affected systems. In addition to the pages described within this chapter, you may view Errata by product line from the following location: https://rhn.redhat.com/errata.
Page 125: Relevant Errata
Relevant Errata 6.5.1. Relevant Errata List”, the Relevant Errata page displays a customized list of Errata Figure 6.15, “Errata As shown in Updates that applies to your registered systems. The list provides a summary of each Errata Update, including its type, severity (for Security Updates), advisory number, synopsis, systems affected, and date updated.
Page 126 Chapter 6. Red Hat Network Website 6.5.2.1. Apply Errata Updates Errata Updates include a list of updated packages that are required to apply the Errata Update. To apply Errata Updates to a system, the system must be entitled. Apply all applicable Errata Updates to a system by clicking on Systems Systems in the top and left navigation bars.
Page 127: Advanced Search
Below Fixes, the specific Bugzilla entries resolved by this erratum are listed. Clicking on any summary text opens that Bugzilla entry at http://1bugzilla.redhat.com. Note that you must have a Bugzilla account to view the entry. Security updates list the specific vulnerability as tracked by http://1cve.mitre.org. This information is listed below the CVEs label.
Page 128: Channels
Chapter 6. Red Hat Network Website 6.6. Channels If you click the Channels tab on the top navigation bar, the Channels category and links appear. The pages in the Channels category enable you to view and manage the channels and packages associated with your systems.
Page 129 Software Channels Channels can be further broken down by their relevance to your systems. Two such lists emerge: Relevant and All. 6.6.1.3. Relevant Channels Figure 6.16, “Relevant Channels”, the Relevant Channels page is shown by default As shown in when you click Software Channels in the left navigation bar. It displays a list of channels now associated with your systems.
Page 130 Chapter 6. Red Hat Network Website 6.6.1.6. Software Channel Details If you click on the name of a channel, the Software Channel Details page appears. This page is broken down into the following tabs: 6.6.1.6.1. Software Channel Details Details General information about the channel and the parent channel, if it is a child channel. This is the first tab displayed when you click on a channel.
Page 131: Package Search
Package Search example, typing ks in the filter might return: ksconfig, krb5-workstation, and links. The filter is case-insensitive. 6.6.1.6.4. Software Channel Details Subscribed Systems List of entitled systems subscribed to the channel. The list displays system names, base channels, and their levels of entitlement. Clicking on a system name takes you to its System Details page. Refer Section 6.4.2.9, “System Details”...
Page 132: Manage Software Channels
Chapter 6. Red Hat Network Website The Package Search page allows you to search through packages using various criteria: • Free Form — a general keyword search for users that are unsure of the details of particular package and its contents. •...
Page 133: Configuration
Configuration To allow a user to alter the channel, select the checkbox next to the user's name and click the Update button. To allow all users to manage the channel, click the Select All button at the bottom of the list followed by the Update button.
Page 134: Preparing Systems For Config Management
Chapter 6. Red Hat Network Website to as an override channel) and a Sandbox channel. Both central and local configuration management are discussed in detail later in this chapter. 6.7.1. Preparing Systems for Config Management For a system to have its configuration managed through RHN, it must have the appropriate tools and config-enable file installed.
Page 135: Configuration Channels
Configuration Channels 6.7.3. Configuration Channels As mentioned above, RHN manages both central and local configuration channels and files. Central configuration management allows you to deploy configuration files to multiple systems. Local configuration management allows you to specify overrides, or configuration files that are not changed by subscribing the system to a central channel.
Page 136: Configuration Files
Chapter 6. Red Hat Network Website Upload File To upload a file into the configuration channel, browse for the file on your local system, populate all fields, and click the Upload Configuration File button. The Filename/Path field is the absolute path where the file will be deployed. You can also indicate the ownership and permissions to be attached to the file when it is deployed.
Page 137: Locally-Managed Files
Locally-Managed Files Note By default, the maximum file size for confiugration files is 128KB. If you need to change that value, find or create the following line in the /etc/rhn/rhn.conf file: web.maximum_config_file_size=128 Change the value from 128 to whatever limit you want in bytes. 6.7.4.1.
Page 138 Chapter 6. Red Hat Network Website • rhn.system.description • rhn.system.hostname • rhn.system.ip_address • rhn.system.custom_info(key_name) • rhn.system.net_interface.ip_address(eth_device) • rhn.system.net_interface.netmask(eth_device) • rhn.system.net_interface.broadcast(eth_device) • rhn.system.net_interface.hardware_address(eth_device) • rhn.system.net_interface.driver_module(eth_device) To use this powerful feature, either upload or create a configuration file through the Configuration Channel Details page. Then, open its Configuration File Details page and include the supported macros of your choosing.
Page 139: Systems
Systems To include a default value, for instance if one is required to prevent errors, you can append it to the custom information macro, like so: asset={@ rhn.system.custom_info(asset) = 'Asset #' @} This default is overridden by the value on any system containing it. Using the Red Hat Network Configuration Manager (rhncfg-manager) will not translate or alter files, as that tool is system agnostic —...
Page 140: Pending Actions
Chapter 6. Red Hat Network Website 2. Rollback Package Actions 3. System Reboots 4. Errata Updates 5. Configuration File Alteration (deploy, upload, and diff) 6. Hardware Profile Updates 7. Package List Profile Updates 8. Kickstart Initiation 9. Remote Commands Each page in the Schedule category represents an action status. 6.8.1.
Page 141: Failed Actions
Failed Actions 6.8.2. Failed Actions Actions that could not be completed. If the action returns an error, it is displayed here. 6.8.3. Completed Actions Actions that have succeeded. 6.8.4. Archived Actions Actions that you have selected to store for review. 6.8.5.
Page 142 Chapter 6. Red Hat Network Website 6.8.5.1.3. Action Details In Progress Systems List of systems on which the action is now being undertaken. To cancel an action, select the system using the appropriate checkbox and click the Unschedule Action button. Clicking a system name takes you to its System Details page.
Page 143 User List Active — ” for more information. • Real Name — The full name of the user (last name first). • Roles — List of the user's privileges, such as Organization Administrator, Channel Administrator and normal user. Users can have multiple roles. •...
Page 144 Chapter 6. Red Hat Network Website Customer Service to delete a user. Users may be deactivated or deleted by Satellite Administrators, or users may deactivate their own accounts. Deactivated users cannot log in to the RHN web interface, nor may they schedule any actions. Satellite Administrators may not be deactivated until that role is removed from their account.
Page 145 User List Active — channels. The systems must be in system groups to which the user has permissions for them to be manageable or even visible. Remember, however, all globally subscribable channels may be used by anyone. • Activation Key Administrator — This role is designed to manage your organization's collection of activation keys.
Page 146 Chapter 6. Red Hat Network Website 6.9.1.1.3. User List Active User Details Systems — This tab lists all systems to which the user has access permission. These systems come from the system groups assigned to the user on the previous tab. You may choose a set of systems to work with by checking the boxes to the left of the systems and clicking the Update List button.
Page 147 List Deactivated — • Time Zone — Set this user's time zone so that scheduled actions are arranged according to the time in the relevant time zone. • Red Hat Contact Options — Identify what ways (email, phone, fax, or mail) Red Hat may contact the user.
Page 148 Chapter 6. Red Hat Network Website 6.10. Monitoring — If you click the Monitoring tab on the top navigation bar, the Monitoring category and links appear. These pages, which require Monitoring entitlements, enable you to view the results of probes you have set to run against Monitoring-entitled systems and manage the configuration of your monitoring infrastructure.
Page 149 Probe Status — In these tables, clicking the name of the system takes you to the Probes tab of the System Details page. Clicking the name of the probe takes you to its Current State page. From there, you may edit the probe, delete it, and generate reports based upon its results.
Page 150 Chapter 6. Red Hat Network Website 6.10.1.6. Probe Status All — All probes scheduled on systems in your account, listed in alphabetical order by the name of system. 6.10.1.7. Current State — Identifies the selected probe's status and when it last ran, while providing the ability to generate a report on the probe.
Page 151 Notification — 2. Type: Determine what action the filter should take: redirect, acknowledge, suspend, or supplement the incoming notification. 3. Send to: The Redirect Notification and Supplemental Notification options in step two require an email address to which to send the notifications. The remaining options require no email address. 4.
Page 152 Chapter 6. Red Hat Network Website 6.10.3. Probe Suites Probe Suites allow you to configure and apply one or more probes to a system or systems. Probe Suites may be configured once and then applied to any number of systems in a batch. This results in time savings and consistency for Monitoring customers.
Page 153 Scout Config Push — probes individually without affecting any other systems. For more information about removing Section 6.4.2.9.5.2, “System Details Monitoring — probes from an individual system, refer to ”. To detach a system from the suite: 1. From the Monitoring Probe Suites page, click on the title of the Probe Suite you wish to alter.
Page 154: Satellite Tools
Chapter 6. Red Hat Network Website 6.10.5. General Config — Collects information that is universally applicable to your Monitoring infrastructure.Modifying anything on this page causes the Monitoring services on the RHN Satellite Server to reset. It also schedules restart events for the Monitoring services on all Monitoring-enabled RHN Proxy Servers that connect to this Satellite.
Page 155 Satellite Tools Organizations Figure 6.20. Satellite Tools The Organizations page contains a listing of organizations across the Satellite, with User and System counts assigned to each organization. 6.11.1.1. Create New Organization Administrators can create a new organization within a Satellite and assign entitlements, groups, systems, and users to the group so that organizations can perform administrative tasks within their own network without possibly affecting the entire Satellite.
Page 156 Chapter 6. Red Hat Network Website Figure 6.21. Create New Organization 1. Input the Organization Name in the provided text box. The name should be between 3 and 128 characters. 2. Create an administrator for the organization: a. Enter a Desired Login for the organization administrator, which should be between 5 and 64 characters long.
Page 157 Satellite Tools Organizations • Active Users — The number of users in the organization • Systems — The number of systems subscribed to the organization. • System Groups — The number of groups subscribed to the organization. • Activation Keys — The number of activation keys available to the organization. •...
Page 158 Chapter 6. Red Hat Network Website 6.11.1.2.2.2. Satellite Tools Organizations Details Subscriptions Software Channel Entitlements The Software Channel Entitlements subtab enables administrators to set the number of allocations per software channel. Enter the number of allocations of each software entitlement in the text box, not to exceed the limit indicated in the Possible Values below the text box.
Page 159 Satellite Tools Satellite Configuration • Organization Usage shows the number of organizations that have access to the entitlement. 6.11.1.4.2. Satellite Tools Subscriptions System Entitlements The System Entitlements Across Satellite page lists all system entitlements on this Satellite, across all organizations, as well as their usage. Click on the entitlement's name for more details about it. The Details subtab for the system entitlement contains information about the entitlement and what access it grants.
Page 160: Help
Chapter 6. Red Hat Network Website the /var/www/html/pub/bootstrap/ directory of the Satellite, significantly reduces the effort involved in reconfiguring all systems, which by default obtain packages from the central RHN Servers. The required fields are pre-populated with values derived from previous installation steps. Ensure this information is accurate.
Page 161: Release Notes
Release Notes 6.12.4. Release Notes The Release Notes page lists the notes accompanying every recent release of Red Hat Network. These notes describe all significant changes occurring in a given release cycle, from major enhancements to the user interface to minor changes to the related documentation. 6.12.5.
Page 163 Chapter 7. Monitoring The Red Hat Network Monitoring entitlement allows you to perform a whole host of actions designed to keep your systems running properly and efficiently. With it, you can keep close watch on system resources, network services, databases, and both standard and custom applications. Monitoring provides both real-time and historical state-change information, as well as specific metric data.
Page 164: Probes Requiring The Daemon
Chapter 7. Monitoring 7.2.1. Probes requiring the daemon An encrypted connection, either through the Red Hat Network Monitoring Daemon or sshd, is required on client systems for the following probes to run: • Linux::CPU Usage • Linux::Disk IO Throughput • Linux::Disk Usage •...
Page 165: Configuring Ssh
Configuring SSH The rhnmd package can be found in the RHN Tools channel for all Red Hat Enterprise Linux distributions. To install it: 1. Subscribe the systems to be monitored to the RHN Tools channel associated with the system. This can be done individually through the System Details Channels Software subtab or for multiple systems at once through the Channel Details...
Page 166: Installing The Ssh Key
Chapter 7. Monitoring 7.2.4. Installing the SSH key Whether you use rhnmd or sshd, you must install the Red Hat Network Monitoring Daemon public SSH key on the systems to be monitored to complete the secure connection. To install it: 1.
Page 167: Notifications
These notifications come in the form of brief text messages sent to either email or pager addresses. Here is an example of an email notification: Subject: CRITICAL: [hostname]: Satellite: Users at 1 From: "Monitoring Satellite Notification" (rogerthat01@redhat.com) Date: Mon, 6 Dec 2004 13:42:28 -0800 To: user@organization.com...
Page 168: Redirecting Notifications
Chapter 7. Monitoring This is RHN Monitoring Satellite notification 01dc8hqw. Time: Mon Dec 06, 21:42:25 PST State: CRITICAL System: [hostname] ([IP address]) Probe: Satellite: Users Message: Users 6 (above critical threshold of 2) Notification #116 for Users Run from: RHN Monitoring Satellite As you can see, the longer email notifications contain virtually everything you would need to know about the associated probe.
Page 169: Filtering Notifications
Filtering Notifications Note You can halt or redirect almost all probe notifications by replying to a notification emails with a variation of the command ack suspend host. However, you cannot halt Satellite probe notifications by responding to a probe with ack suspend host or other redirect responses.
Page 170: Managing Probes
Chapter 7. Monitoring 7.5.1. Managing Probes To add a probe to a system, the system must be entitled to Monitoring. Further, you must have access to the system itself, either as the system's root user, through the System Group Administrator role, or as the Satellite Administrator.
Page 171: Monitoring The Rhn Server
To thoroughly troubleshoot a probe, you must first obtain its probe ID. You may obtain this information by running rhn-catalog on the RHN Server as the nocpulse user. The output will resemble: 2 ServiceProbe on example1.redhat.com (199.168.36.245): test 2 3 ServiceProbe on example2.redhat.com (199.168.36.173): rhel2.1 test 4 ServiceProbe on example3.redhat.com (199.168.36.174): SSH...
Page 172: Viewing The Output Of Rhn-Runprobe
The --commandline option yields the command parameters set for the probe, while --dump retrieves everything else, including alert thresholds and notification intervals and methods. The command above will result in output similar to: 5 ServiceProbe on example4.redhat.com (199.168.36.175 linux:cpu usage Run as: Unix::CPU.pm --critical=90 --sshhost=199.168.36.175...
Page 173 Viewing the output of rhn-runprobe This yields verbose output depicting the probe's attempted execution. Errors are clearly identified.
Page 175: Setting Up The Host System For Your Virtual Systems
Chapter 8. Virtualization In order to manage and provision your client systems, you must first synchronize content from RHN's central servers to your Satellite. RHN recommends that you sync at least the following channels: • Red Hat Network Tools for RHEL Server (v. 5 for 32-bit x86) — rhn-tools-rhel-i386-server-5 •...
Page 176: Kickstart Your Host System
Chapter 8. Virtualization Note If you are changing the Virtualization Type of an existing kickstart profile, it may also modify the bootloader and partition options, potentially overwriting any user customizations. Be sure to review the Partitioning tab to verify these settings when changing the Virtualization Type.
Page 177 Kickstart Your Host System rhnreg_ks --serverUrl=htt://your-satellite.example.com/XMLRPC \ --username=username --password=password Note If your host system is already registered to a different Red Hat Network server, asdd the --force option to the command above. 2. Next, open up the host system's profile in the Satellite web interface. Log into the web interface of your Satellite at https://your-satellite.example.com/.
Page 178 It is possible to use a flash-memory USB key to boot your system in order to kickstart it. Refer to the Red Hat Enterprise Linux System Administration Guide (available at http://www.redhat.com/docs/manuals/enterprise/) for tips on how to do this. Note that your host system's hardware must support boot via these devices.
Page 179 Kickstart Your Host System Note For some systems you may either need to add ksdevice=eth0 to the command above or disable one of two or more NICs in the system's BIOS to avoid confusion during the kickstart process. 4. The kickstart for your host system should begin. It should take around fifteen minutes to complete. Upon successful completion of this kickstart, you will have provisioned a host system for your virtual guest and registered it to you Satellite.
Page 180: Setting Up Your Virtual Systems
Chapter 8. Virtualization You will then need to edit the /etc/grub.conf configuration file to boot the new xen kernel by default. To do this, select the lines in grub.conf that pertain to the xen kernel from the beginning of the title line to the end of the initrd line, copy the lines, delete them, and paste them so they are the first kernel entry in grub.conf.
Page 181: Provision Your Guest Systems
Provision Your Guest Systems Note Red Hat Enterprise Linux Client 5 may not be available for selection if you did not sync the Client software channels to your Satellite. Please note that the channel labels for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 5 Desktop refer to 'server' and 'client' respectively.
Page 182 Chapter 8. Virtualization 2. To schedule a kickstart for a guest system, go to the Virtualization Provisioning tab in the host system's profile. For the Guest Name field choose guest1. For the Memory Allocation, Virtual CPUs, and Storage fields, the default values should be fine. Feel free to change these as desired, taking note of the advice provided for each field in the interface.
Page 183: Working With Your Virtual Systems
Working With Your Virtual Systems 4. If you would like to register additional guests to your host, repeat the steps above. It is important to remember that you can only provision one guest at a time. If you attempt to schedule a guest kickstart while another is currently taking place, the current guest kickstart process will be canceled and the new guest kickstart process will begin.
Page 184: Installing Software Via The Satellite Web Interface
Chapter 8. Virtualization 8.3.3. Installing Software Via the Satellite Web Interface 1. Browse to the virtual system's profile in your Satellite's web interface by logging in and navigating to Systems Systems Virtual Systems and clicking on the name of your virtual system's profile. 2.
Page 185 Deleting Virtual Systems Delete it with the following command: rm /var/lib/xen/disk-images/guest1.disk 4. Finally, you must delete the RHN configuration files from the host system. To locate the RHN configuration file for guest1, run the following command: grep guest1 /etc/sysconfig/rhn/virt/*.xml Then delete the file indicated. For example: rm /etc/sysconfig/rhn/virt/14e5cfbf72342515236ad74b260c2f6b.xml 5.
Page 187: Unix Support Guide 9.1. Introduction
Chapter 9. UNIX Support Guide 9.1. Introduction This chapter documents the installation procedure for, and identifies differences in, Red Hat Network functionality when used to manage UNIX-based client systems. RHN offers UNIX support to help customers migrate from UNIX to Linux. Because of the limited scope of this task, the features offered for UNIX client management are not as comprehensive as those available for managing Red Hat Enterprise Linux systems.
Page 188: Differences In Functionality
Chapter 9. UNIX Support Guide • All Management-level functionality, such as system grouping, package profile comparison, and use of the System Set Manager to administer multiple systems at once • A Provisioning feature called Remote Command that enables users to schedule root-level commands on any managed client through the Satellite's website, if the client allows this action 9.1.4.
Page 189 Satellite Server Preparation/Configuration Figure 9.1. Enabling UNIX Support During Satellite Installation 2. After the Satellite has been installed: Enable UNIX support by configuring the Satellite after it has been installed. To do so, select Satellite Tools in the top menubar, then select Satellite Configuration in the left navigation bar. In the screen that follows, check the Enable Solaris Support box, as pictured:...
Page 190: Client System Preparation
Chapter 9. UNIX Support Guide Figure 9.2. Enabling UNIX Support After Satellite Installation Click the Update Configuration button to confirm the change. 3. Finally, you must create a base channel to which your client systems may subscribe. This is because RHN does not provide UNIX content; as a result, you cannot use satellite-sync to create the channel.
Page 191: Download And Install Additional Packages
Download and Install Additional Packages 3. Next, deploy the SSL certificates required for a secure connection. 4. Configure the client applications to connect to the RHN Satellite Server. Once finished, your systems will be ready to begin receiving RHN updates. The following three section explain these steps in detail.
Page 192 Chapter 9. UNIX Support Guide • SMCzlib To verify if a package is installed on the client, use the pkginfo command. For example, to check for a package that contains "zlib" in the name, run the following command: # pkginfo | grep zlib Note Solaris package archive names differ from the name of the installed package.
Page 193 However, this may cause the installation of some packages to fail silently on Solaris 10. Continue until each package is installed in the RHN-specific path: /opt/redhat/rhn/solaris/. 9.3.1.5. Include RHN Packages in the PATH In order to make the RHN packages available at each login, you may wish to add them to your PATH.
Page 194: Deploying Client Ssl Certificates
# man -M /opt/redhat/rhn/solaris/man <man page> Finally, add the Red Hat Libraries to your PATH as you did with libgcc, openssl and zlib. crle -c /var/ld/ld.config -l <current library paths>:/opt/redhat/rhn/ solaris/lib 9.3.2. Deploying Client SSL Certificates To ensure secure data transfer, Red Hat strongly recommends the use of SSL. The RHN Satellite Server eases implementation of SSL by generating the necessary certificates during its installation.
Page 195: Registration And Updates
SSL certificate described in Certificates”, for example: sslCACert[comment]=The CA cert used to verify the ssl server sslCACert=/opt/redhat/rhn/solaris/usr/share/rhn/RHN-ORG-TRUSTED-SSL- CERT Your client systems are now ready for registration with Red Hat Network and management by your Satellite.
Page 196: Obtaining Updates
Chapter 9. UNIX Support Guide 3. After creating the key, click its name in the Activation Keys list to enhance its RHN settings by associating software and configuration channels and system groups. 4. Open a terminal on the client system to be registered and switch user to root. 5.
Page 197 Obtaining Updates 9.4.2.1.1. solaris2mpm Section 9.1.4, “Differences in Functionality”, solaris2mpm is part of RHN As mentioned briefly in Push for Solaris. The content that is pushed to a Solaris channel on the Satellite must first be in .mpm format. A .mpm file is an archive containing a description of the package data and the package or patch itself. The solaris2mpm command must be run on the client, never the Satellite.
Page 198 It can be started from the command line in this way: rhnsd --foreground --interval=240 The default location for rhnsd is /opt/redhat/rhn/solaris/usr/sbin/rhnsd. Below are the available options for rhnsd on Solaris: Option Description...
Page 199: Remote Commands
Remote Commands 9.4.2.3. Updating From the Command Line Like the website, command line use of the Red Hat Update Agent is affected by the limitations of UNIX package management. That said, most core functions can still be accomplished through the up2date command.
Page 200: Issuing Commands
/etc/sysconfig/rhn/allowed-actions/ directory specific to your UNIX variant. For instance, in Solaris, issue this command to create the directory: mkdir -p /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/ script To create the requisite file in Solaris, issue this command: touch /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script/ 9.5.2.
Page 201: A.1.1. General Command Line Options
Appendix A. Command Line Config Management Tools In addition to the options provided in the RHN website, Red Hat Network offers two command line tools for managing a system's configuration files: the Red Hat Network Configuration Client and the Red Hat Network Configuration Manager. There is a complementary Red Hat Network Actions Control tool that is used to enable and disable configuration management on client systems.
Page 202: A.2. Red Hat Network Configuration Client
Appendix A. Command Line Config Management Tools Option Description --disable-mtime-upload Disable mtime upload --disable-all Disable all options --disable-run Disable script.run --report Report whether the modes are enabled or disabled -f, --force Force the operation without asking first -h, --help show help message and exit Table A.1.
Page 203: A.2.2. Getting A Config File
Getting a Config File A.2.2. Getting a Config File To download the most relevant configuration file for the machine, issue the command: rhncfg-client get /etc/example-config.txt You should see output resembling: Deploying /etc/example-config.txt You may then view the contents of the file with less or another pager. Note that the file is selected as the most relevant based upon the rank of the config channel containing it.
Page 204: A.2.5. Verifying Config Files
Appendix A. Command Line Config Management Tools [root@ root]# rhncfg-client diff --topdir /home/test/blah/ /usr/bin/ diff: /home/test/blah/etc/example-config.txt: No such file or directory / usr/bin/diff: /home/test/blah/var/spool/aalib.rpm: No such file or directory A.2.5. Verifying Config Files To quickly determine if client configuration files are different than those associated with it via RHN, issue the command: rhncfg-client verify The output resembles the following:...
Page 205: A.3.1. Creating A Config Channel
Creating a Config Channel The Red Hat Network Configuration Manager offers these primary modes: add, create-channel, diff, diff-revisions, download-channel, get, list, list-channels, remove, remove-channel, revisions, update, and upload-channel. Each mode offers its own set of options, which can be seen by issuing the following command: rhncfg-manager mode --help Replace mode with the name of the mode to be inspected: rhncfg-manager diff-revisions --help...
Page 206: A.3.3. Differentiating Between Latest Config Files
Appendix A. Command Line Config Management Tools Option Description -cCHANNEL --channel=CHANNEL Upload files in this config channel -dDEST_FILE --dest-file=DEST_FILE Upload the file as this path --delim-start=DELIM_START Start delimiter for variable interpolation --delim-end=DELIM_END End delimiter for variable interpolation -h, --help show help message and exit Table A.4.
Page 207: A.3.5. Downloading All Files In A Channel
Downloading All Files in a Channel Section A.3.11, “Determining the Number of File Revisions” checked. Refer to for related instructions. Specify only one file name here, since you are comparing the file against another version of itself. For example: rhncfg-manager diff-revisions -n=channel-label1-r=1-n=channel-label2- r=1/path/to/file.txt The output resembles the following: --- /tmp/dest_path/example-config.txt 2004-01-13 14:36:41...
Page 208: A.3.7. Listing All Files In A Channel
Appendix A. Command Line Config Management Tools rhncfg-manager get --channel=channel-label \ /tmp/dest_path/example- config.txt You should see the contents of the file as output. A.3.7. Listing All Files in a Channel To list all the files in a channel, issue the command: rhncfg-manager list channel-label You should see output resembling: Files in config channel `example-channel3': /tmp/dest_path/example-...
Page 209: A.3.10. Deleting A Config Channel
Deleting a Config Channel Red Hat Network username: rhn-user Password: Removing from config channel example-channel3 /tmp/dest_path/example-config.txt removed The following table lists the options available for rhncfg-manager remove: Option Description -cCHANNEL, --channel=CHANNEL Remove files from this config channel -tTOPDIR, --topdir=TOPDIR Make all files relative to this string -h, --help Show help message and exit Table A.9.
Page 210: A.3.13. Uploading Multiple Files At Once
Appendix A. Command Line Config Management Tools The following table lists the options available for rhncfg-manager update: Option Description -cCHANNEL, --channel=CHANNEL Upload files in this config channel -dDEST_FILE, --dest-file=DEST_FILE Upload the file as this path -tTOPDIR, --topdir=TOPDIR Make all files relative to this string --delim-start=DELIM_START Start delimiter for variable interpolation --delim-end=DELIM_END...
Page 211: B.2. Obtaining The System_Id
RHN website, then clicking API in the left navigation bar. Or you may go directly to: https:// rhn.redhat.com/rpc/api/. Use this URL for your XMLRPC server and your browser. The RHN API is based upon XML-RPC, which allows distinct pieces of software on disparate systems to make remote procedure calls using XML over HTTP.
Page 212: B.6. Channel Labels
Appendix B. RHN API Access follows the "=" symbol, as part of a string that resembles the following: "details.pxt?sgid=334958". Note that the member parameter within the set_group_membership method requires only yes or no as input to make the association. B.6. Channel Labels The architecture of a channel is not always clear from the channel label.
Page 213 Sample API Script # We use the Frontier modules, available from: # http://theoryx5.uwinnipeg.ca/mod_perl/cpan-search?dist=Frontier-RPC ############################################################################ ############################################################################ Defining an XMLRPC session. ############################################################################ # Define the host first. This will be the FQDN of your satellite system. my $HOST = 'satellite.server.yourdomain.com'; # Now we create the client object that will be used throughout the session.
Page 214 Appendix B. RHN API Access print "\n\nCapturing ID of system @$systems[0]->{name}\n\n"; my $systemid = @$systems[0]->{id}; # This next call returns a list of packages present on this system. # syntax of this call is described at: http://$HOST/rpc/api/system/list_packages/ # This will probably be a pretty long list. my $packages = $client->call('system.list_packages', $session, $systemid);...
Page 215 Appendix C. Probes Section 6.10, “Monitoring — As described in ”, Monitoring-entitled systems can have probes applied to them that constantly confirm their health and full operability. This appendix lists the available probes broken down by command group, such as Apache.
Page 216: C.2. Apache 1.3.X And 2.0.X
Appendix C. Probes While adding probes, select meaningful thresholds that, when crossed, notify you and your administrators of problems within your infrastructure. Timeout periods are entered in seconds unless otherwise indicated. Exceptions to these rules are noted within the individual probe references. Important Some probes have thresholds based on time.
Page 217: C.2.2. Apache::traffic
Apache::Traffic Field Value Warning Maximum Megabytes Transferred Per Slot Table C.1. Apache::Processes settings C.2.2. Apache::Traffic The Apache::Traffic probe monitors the requests on an Apache Web server and collects the following metrics: • Current Requests — The number of requests being processed by the server at probe runtime. •...
Page 218: C.3. Bea Weblogic 6.X And Higher
Appendix C. Probes Field Value Timeout* Table C.3. Apache::Uptime settings C.3. BEA WebLogic 6.x and higher The probes in this section (with the exception of JDBC Connection Pool) can be configured to monitor the properties of any BEA WebLogic 6.x and higher server (Administration or Managed) running on a given host, even in a clustered environment.
Page 219: C.3.2. Bea Weblogic::heap Free
BEA WebLogic::Heap Free Field Value BEA Server Name* myserver Queue Name* default Critical Maximum Idle Execute Threads Warning Maximum Idle Execute Threads Critical Maximum Queue Length Warning Maximum Queue Length Critical Maximum Request Rate Warning Maximum Request Rate Table C.4. BEA WebLogic::Execute Queue settings C.3.2.
Page 220: C.3.4. Bea Weblogic::server State
Appendix C. Probes Field Value SNMP Port* SNMP Version* BEA Domain Admin Server BEA Server Name* myserver JDBC Pool Name* MyJDBC Connection Pool Critical Maximum Connections Warning Maximum Connections Critical Maximum Connection Rate Warning Maximum Connection Rate Critical Maximum Waiters Warning Maximum Waiters Table C.6.
Page 221: C.4. General
General This probe's transport protocol is User Datagram Protocol (UDP). Field Value SNMP Community String* public SNMP Port* SNMP Version* BEA Domain Admin Server BEA Server Name* myserver 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.
Page 222: C.4.3. 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 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.
Page 223: C.4.4. General::tcp Check
General::TCP Check Field 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 that it can connect to a system via the specified port number. It collects the following metric: •...
Page 224: C.4.6. General::uptime (Snmp)
Appendix C. Probes 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.
Page 225: C.5.3. Linux::disk Usage
Linux::Disk Usage Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the monitored system to execute this probe. Also, the Disk number or disk name parameter must match the format visible when the iostat command is run. If the format is not identical, the configured probe enters an UNKNOWN state.
Page 226: C.5.5. Linux::interface Traffic
Appendix C. Probes • Inodes — The percentage of inodes currently in use. An inode is a data structure that holds information about files in a Linux file system. There is an inode for each file, and a file is uniquely identified by the file system on which it resides and its inode number on that system.
Page 227: C.5.7. Linux::memory Usage
Linux::Memory Usage Field Value Timeout* Critical CPU Load 1-minute average Warning CPU Load 1-minute average Critical CPU Load 5-minute average Warning CPU Load 5-minute average Critical CPU Load 15-minute average Warning CPU Load 15-minute average Table C.20. Linux::Load settings C.5.7. Linux::Memory Usage The Linux::Memory Usage probe monitors the memory on a system and collects the following metric: •...
Page 228: C.5.9. Linux::process Count Total
Appendix C. Probes Field Value Critical Maximum Blocked Processes Warning Maximum Blocked Processes Critical Maximum Defunct Processes Warning Maximum Defunct Processes Critical Maximum Stopped Processes Warning Maximum Stopped Processes Critical Maximum Sleeping Processes Warning Maximum Sleeping Processes Critical Maximum Child Processes Warning Maximum Child Processes Table C.22.
Page 229: C.5.11. Linux::process Running
Linux::Process Running Specify the process by its command name or process ID. (PID). Entering a PID overrides the entry of a command name. If no command name or PID is entered, the error Command not found is displayed and the probe will be set to a CRITICAL state. Requirements —...
Page 230: C.5.12. Linux::swap Usage
Appendix C. Probes Field Value Critical Maximum Number Running Critical Minimum Number Running Table C.25. Linux::Process Running settings C.5.12. Linux::Swap Usage The Linux::Swap Usage probe monitors the swap partitions running on a system and reports the following metric: • Swap Free — The percent of swap memory currently free. Requirements —...
Page 231: C.5.14. Linux::users
Linux::Users Field Value Remote IP address filter pattern list Remote port number filter Timeout* Critical Maximum Total Connections Warning Maximum Total Connections Critical Maximum TIME_WAIT Connections Warning Maximum TIME_WAIT Connections Critical Maximum CLOSE_WAIT Connections Warning Maximum CLOSE_WAIT Connections Critical Maximum FIN_WAIT Connections Warning Maximum FIN_WAIT Connections Critical Maximum ESTABLISHED Connections Warning Maximum ESTABLISHED Connections...
Page 232: C.6. Logagent
Appendix C. Probes Field Value Critical Minimum Virtual Memory Free Table C.29. Linux::Virtual Memory settings C.6. LogAgent The probes in this section monitor the log files on your systems. You can use them to query logs for certain expressions and track the sizes of files. For LogAgent probes to run, the nocpulse user must be granted read access to your log files.
Page 233: C.6.2. Logagent::log Size
LogAgent::Log Size Field Value Timeout* Critical Maximum Matches Warning Maximum Matches Warning Minimum Matches Critical Minimum Matches Critical Maximum Match Rate Warning Maximum Match Rate Warning Minimum Match Rate Critical Maximum Match Rate 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: •...
Page 234: C.7. Mysql 3.23 - 3.33
Appendix C. Probes Field Value Warning Maximum Line Rate Warning Minimum Line Rate Critical Minimum Line Rate Table C.31. LogAgent::Log Size settings C.7. MySQL 3.23 - 3.33 The probes in this section monitor aspects of the MySQL database using the mysqladmin binary. No specific user privileges are needed for these probes.
Page 235: C.7.3. Mysql::open Tables
MySQL::Open Tables C.7.3. MySQL::Open Tables The MySQL::Open Tables probe monitors the MySQL server and collects the following metric: • Open Tables — The number of tables open when the probe runs. Field Value Username Password MySQL Port* 3306 Timeout Critical Maximum Open Objects Warning Maximum Open Objects Warning Minimum Open Objects Critical Minimum Open Objects...
Page 236: C.8. Network Services
Appendix C. Probes Field Value 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 that their timed thresholds do not exceed the amount of time allotted to the timeout period.
Page 237: C.8.3. Network Services::imap Mail
Network Services::IMAP Mail Field Value 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 238: C.8.6. Network Services::pop Mail
Appendix C. Probes • Round-Trip Average — The time it takes in milliseconds for the ICMP ECHO packet to travel to and from the monitored system. • Packet Loss — The percent of data lost in transit. Although optional, the IP Address field can be instrumental in collecting metrics for systems that have multiple IP addresses.
Page 239: C.8.7. Network Services::remote Ping
Network Services::Remote Ping C.8.7. Network Services::Remote Ping The Network Services::Remote Ping probe determines if the monitored system can ping a specified IP address. It also monitors the packet loss and compares the round trip average against the Warning and Critical threshold levels. The required Packets to send value allows you to control how many ICMP ECHO packets are sent to the address.
Page 240: C.8.9. Network Services::secure Web Server (Https)
Appendix C. Probes Field Value Protocol (TCP/UDP) Service Name* Timeout* Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency Table C.44. Network Services::RPCService settings C.8.9. Network Services::Secure Web Server (HTTPS) The Network Services::Secure Web Server (HTTPS) probe determines the availability of the secure Web server and collects the following metric: •...
Page 241: C.8.11. Network Services::web Server (Http)
Network Services::Web Server (HTTP) Upon successfully contacting the SSH server and receiving a valid response, the probe displays the protocol and server version information. If the probe receives an invalid response, it displays the message returned from the server and generates a WARNING state. Field Value SSH Port*...
Page 242: C.9. Oracle 8I And 9I
Appendix C. Probes C.9. Oracle 8i and 9i The probes in this section may be applied to instances of the Oracle database matching the versions supported. Oracle probes require the configuration of the database and associations made by running the following command: $ORACLE_HOME/rdbms/admin/catalog.sql In addition, for these probes to function properly, the Oracle user configured in the probe must have minimum privileges of CONNECT and SELECT_CATALOG_ROLE.
Page 243: C.9.2. Oracle::availability
Oracle::Availability C.9.2. Oracle::Availability The Oracle::Availability probe determines the availability of the database from the RHN Satellite Server. Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* Table C.49. Oracle::Availability settings C.9.3. Oracle::Blocking Sessions The Oracle::Blocking Sessions probe monitors an Oracle instance and collects the following metric: •...
Page 244: C.9.5. Oracle::client Connectivity
Appendix C. Probes Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port 1521 Timeout* Warning Minimum Buffer Cache Hit Ratio Critical Minimum Buffer Cache Hit Ratio Table C.51. Oracle::Buffer Cache settings C.9.5. Oracle::Client Connectivity The Oracle::Client Connectivity probe determines if the database is up and capable of receiving connections from the monitored system.
Page 245: C.9.7. Oracle::disk Sort Ratio
Oracle::Disk Sort Ratio Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Timeout* Warning Minimum Data Dictionary Hit Ratio Critical Minimum Data Dictionary Hit Ratio Table C.53. Oracle::Data Dictionary Cache settings C.9.7. Oracle::Disk Sort Ratio The Oracle::Disk Sort Ratio probe monitors an Oracle database instance and collects the following metric: •...
Page 246: C.9.9. Oracle::index Extents
Appendix C. Probes Field Value Warning Maximum Idle Sessions Table C.55. Oracle::Idle Sessions settings C.9.9. Oracle::Index Extents The Oracle::Index Extents probe monitors an Oracle instance and collects the following metric: • Allocated Extents — The number of allocated extents for any index. •...
Page 247: C.9.11. Oracle::locks
Oracle::Locks Field Value Timeout* Critical Maximum Library Cache Miss Ratio Warning Maximum Library Cache Miss Ratio Table C.57. Oracle::Library Cache settings 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.
Page 248: C.9.13. Oracle::table Extents
Appendix C. Probes Field Value Critical Maximum Redo Log Space Request Rate Warning Maximum Redo Log Space Request Rate Critical Maximum Redo Buffer Allocation Retry Rate Warning Maximum Redo Buffer Allocation Retry Rate Table C.59. Oracle::Redo Log settings C.9.13. Oracle::Table Extents The Oracle::Table Extents probe monitors an Oracle database instance and collects the following metrics: •...
Page 249: C.9.15. Oracle::tns Ping
Oracle::TNS Ping • 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 do not factor into it directly (though each extension removes available space from the shared pool).
Page 250: C.10.2. Rhn Satellite Server::execution Time
Appendix C. Probes • Space Available — The file size available to the current file system. Field Value Device Pathname* /dev/hda1 Critical Maximum File System Used Warning Maximum File System Used Critical Maximum Space Used Warning Maximum Space Used Critical Maximum Space Available Warning Maximum Space Available Table C.63.
Page 251: C.10.5. Rhn Satellite Server::load
RHN Satellite Server::Load a Satellite is overloaded (because it has too many probes with respect to their average execution time), the number goes up. Field Value Critical Maximum Probe Latency Average Warning Maximum Probe Latency Average Table C.66. RHN Satellite Server::Latency settings C.10.5.
Page 252: C.10.8. Rhn Satellite Server::processes
Appendix C. Probes • Stopped — The number of processes that have stopped before their executions could be completed. • Sleeping — A process that is in the Interruptible sleep state and that can later be reintroduced into memory, resuming execution where it left off. Field Value Critical Maximum Blocked Processes...
Page 253: C.10.10. Rhn Satellite Server::process Running
RHN Satellite Server::Process Running • Virtual Memory Used — The amount of virtual memory in kilobytes being used by the specified process, or the size of the process in real memory plus swap. Specify the process by its command name or process ID. (PID). Entering a PID overrides the entry of a command name.
Page 254: C.10.12. Rhn Satellite Server::users
Appendix C. Probes C.10.12. RHN Satellite Server::Users The RHN Satellite Server::Users probe monitors the number of users currently logged into a Satellite. A CRITICAL status results if the value exceeds the Critical threshold. A WARNING status results if the value exceeds the Warning threshold. Field Value Critical Maximum Users...
Page 255 Bugzilla Bugzilla is an online application (http://www.redhat.com/bugzilla that allows users to communicate directly with the developers. From Bugzilla, users can submit bug reports and feature requests for Red Hat Enterprise Linux and related open source packages.
Page 256 The information includes the topics of the Errata, Bugzilla bug IDs, relevant releases/architectures, solutions including required RPMs, and MD5 checksums for verification. Errata are also available at http://www.redhat.com/errata/. Each RHN Errata Alert is based on the Red Hat Enterprise Linux Errata List.
Page 257 RHN organization must have at least one member of the Satellite Administrator group. Package All software in Red Hat Enterprise Linux is divided into software packages. Software updates are released in the form of RPM packages that can be installed on a Red Hat Enterprise Linux system. Probe A set of criteria that is either a template or a set of values assigned to a system that is used to measure the performance of a system.
Page 258 Glossary Errata Alert Security Alert that pertains to system security. Sibling Siblings are virtual guests running on the same host. Virtual guests that run on separate hosts are not siblings. Service Level A Red Hat Network subscription service. Different service levels offer different features of RHN.
Page 259 Appendix D. Revision History Revision History Revision 1.0...
Page 261 Index Channels and Packages Channel List, 116 child channel, 116 client applications obtaining, 5 account redirecting, 182 deactivate, 66 client systems action configuring, 182 completed systems, 129 registering, 183 details, 129 updating, 184 failed systems, 130 config management in progress systems, 130 system preparation, 122 activation key, 97 configuration...
Page 262 Index searching, 115 Users, 219 viewing details, 114 Virtual Memory, 219 viewing list of all errata, 113 List Navigation viewing list of applicable errata, 113 explanation of, 62 EUS (see Extended Update Support) LogAgent Extended Update Support, 116 Log Pattern Match, 220 Log Size, 221 probes nocpulse, 220...
Page 263 Ping, 225 port 22, 153 POP Mail, 226 port 4545, 151 probes, 224 preferences Remote Ping, 227 change, 66 RPCService, 227 language, 67 Secure Web Server (HTTPS), 228 locale, 67 SSH, 228 probe Web Server (HTTP), 229 guidelines, 203 notes probe list about systems, 78 Apache...
Page 264 Index POP Mail, 226 Network Services, 224 Remote Ping, 227 on the RHN Server, 159 RPCService, 227 Oracle, 230 Secure Web Server (HTTPS), 228 RHN Satellite Server, 237 SSH, 228 thresholds, 158 Web Server (HTTP), 229 WebLogic, 206 Oracle Provisioning Active Sessions, 230 service level, 3 Availability, 231...
Page 265 Red Hat Network Monitoring Daemon through the Web, 63 (rhnmd) monitoring daemon, 151 username, 46 installation, 152 with a proxy server, 42 probes requiring the daemon, 152 with activation key, 97 SSH key installation, 154 remote commands using sshd instead, 153 enabling, 187 Red Hat Network packages issuing, 188...
Page 266 Index Management, 2 viewing details for, 72 Monitoring, 4 Systems Provisioning, 3 Advanced Search, 97 Update, 2 Entitlements, 67 Software System Details, 72 Channel List System List, 69 Channel Details, 118 Systems Overview, 69 Package Search, 119 systems list software status, 69 searching, 119 Systems Selected...
Page 267 custom system information, 100 Errata, 112 Errata Search, 115 Help, 148 language, 67 locale, 67 logging in, 62 Monitoring, 136 navigation bar, 57 overview, 57 Relevant Errata, 113 Schedule, 127 Software Channel Details, 118 Software Search, 119 stored profiles, 100 System Details, 72 System Entitlements, 67 System Group List, 87...

Red Hat NETWORK SATELLITE 5.1.1 Reference Manual

Quick Links

Troubleshooting

Related Manuals for Red Hat NETWORK SATELLITE 5.1.1

Summary of Contents for Red Hat NETWORK SATELLITE 5.1.1

Table of Contents