Red Hat Satellite 5.
Red Hat Satellite 5.
Legal Notice Copyright © 2013 Red Hat, Inc. T his document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Table of Contents Table of Contents .Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . 1. Document Conventions 3 1.1. T ypographic Conventions 3 1.2. Pull-quote Conventions 5 1.3. Notes and Warnings 5 2. Getting Help and Giving Feedback 6 2.1. Do You Need Help? 6 2.2. We Need Feedback! 6 . . . . . . . . . 1. Chapter . . .Introduction . . . . . . . .
Red Hat Satellite 5.
Preface Preface Red Hat Network (https://access.redhat.com/home) provides system-level support and management of Red Hat systems and networks. It brings together the tools, services, and information repositories needed to maximize the reliability, security, and performance of Red Hat systems. T o use Red Hat Network, system administrators register software and hardware profiles, known as System Profiles, of their client systems with Red Hat Network.
Red Hat Satellite 5.6 Client Configuration Guide T he first example highlights a particular key to press. T he second example highlights a key combination: a set of three keys pressed simultaneously. If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in m ono-spaced bold. For example: File-related classes include filesystem for file systems, file for files, and dir for directories.
Preface 1.2. Pull-quote Conventions T erminal output and source code listings are set off visually from the surrounding text.
Red Hat Satellite 5.6 Client Configuration Guide Warning Warnings should not be ignored. Ignoring warnings will most likely cause data loss. 2. Getting Help and Giving Feedback 2.1. Do You Need Help? If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at http://access.redhat.com. T hrough the customer portal, you can: search or browse through a knowledgebase of technical support articles about Red Hat products.
Chapter 1. Introduction Chapter 1. Introduction T his guide is designed to help users of Red Hat Satellite and Red Hat Satellite Proxy to configure their client systems. By default, all Red Hat Network client applications are configured to communicate with central Red Hat Network servers. When clients connect to a Red Hat Satellite or Red Hat Satellite Proxy instead, the default settings change.
Red Hat Satellite 5.6 Client Configuration Guide Chapter 2. Configuring Client Applications In order to use most enterprise-class features of Red Hat Network, such as registering with Red Hat Satellite, configuration of the latest client applications is required. Obtaining these applications before the client has registered with Red Hat Network can be difficult. T his paradox is especially problematic for customers migrating large numbers of older systems to Red Hat Network.
Chapter 2. Configuring Client Applications Note Systems running Red Hat Enterprise Linux 5 or 6 must be registered as part of the firstboot process after installation or by using the rhn_register command. 2.1.1. The Package Updater Applet Red Hat Enterprise Linux 5 and later feature a running program on the graphical desktop panel that periodically checks for updates from the Red Hat Network or Satellite server and alerts users when updates are available. Figure 2.1.
Red Hat Satellite 5.6 Client Configuration Guide # rhn_register 2.3. Using Activation Keys to Register Clients with Red Hat Satellite Red Hat recommends using activation keys for registering and configuring client systems that access Red Hat Proxy or Red Hat Satellite. You can use activation keys to register, entitle, and subscribe multiple systems in a single operation. See the relevant section in the Red Hat Satellite Getting Started Guide for more information about activation keys. Procedure 2.2.
Chapter 2. Configuring Client Applications serverURL[comment]=Remote server URL serverURL=https://your_primary.your_domain.com/XMLRPC noSSLServerURL[comment]=Remote server URL without SSL noSSLServerURL=http://your_primary.your_domain.com/XMLRPC Warning T he httpProxy setting in /etc/sysconfig/rhn/up2date does not refer to the Red Hat Proxy. It is used to configure an optional HT T P proxy for the client. With a Red Hat Proxy in place, the httpProxy setting must be blank (not set to any value). 2.5.
Red Hat Satellite 5.6 Client Configuration Guide Chapter 3. Registering Red Hat Systems with Red Hat Network Red Hat Enterprise Linux features an application called rhn_register. T his application works with the yum -based Red Hat Network Hosted and Red Hat Satellite client called Package Updater (or pup) that replaces up2date. T he rhn_register application normally runs as part of the firstboot configuration process just after installation.
Chapter 3. Registering Red Hat Systems with Red Hat Network organization or its resources. Click Forward to continue. 4. Use the Create Your System Profile page to select a profile name for the system you are registering. T he default profile name is the system's host name, but you can change it to any valid profile name. You can also select whether to report hardware and package information to Red Hat Network.
Red Hat Satellite 5.6 Client Configuration Guide elements such as text boxes, check boxes, and radio buttons.
Chapter 4. SSL Infrastructure Chapter 4. SSL Infrastructure For Red Hat Satellite customers, security concerns are of the utmost importance. One of the strengths of Red Hat Satellite is its ability to process every single request over Secure Sockets Layer, or SSL. T o maintain this level of security, customers installing Red Hat Satellite within their infrastructures must generate custom SSL keys and certificates. Manual creation and deployment of SSL keys and certificates can be quite involved.
Red Hat Satellite 5.6 Client Configuration Guide establish a connection to their respective upstream servers. Each server has its own SSL key set that is specifically tied to that server's host name and generated using its own SSL private key and the CA SSL private key in combination. T his establishes a digitally verifiable association between the Web server's SSL public certificate and the CA SSL key pair and server's private key. T he Web server's key set cannot be shared with other web servers.
Chapter 4. SSL Infrastructure process. T he SSL keys and certificate are built and deployed automatically. During installation of a Red Hat Proxy Server 3.6 or later if connected to a Red Hat Satellite Server 3.6 or later as its top-level service. T he Red Hat Satellite Server contains all of the SSL information needed to configure, build and deploy the Red Hat Proxy Server's SSL keys and certificates.
Red Hat Satellite 5.6 Client Configuration Guide Note When additional Web server SSL key sets are needed, restore the build tree on a system running the Red Hat Satellite SSL Maintenance T ool and repeat steps 3 through 7. 4.2.2. Red Hat Satellite SSL Maintenance Tool Options T he Red Hat Satellite SSL Maintenance T ool offers numerous command line options for generating Certificate Authority SSL key pair and managing your server SSL certificates and keys.
Chapter 4. SSL Infrastructure latest.txt: lists the latest versions of the relevant files. When this process is complete, distribute the RPM file to the client systems. See Section 4.3, “Deploying the CA SSL Public Certificate to Clients” for more information. 4.2.4. Generating Web Server SSL Key Sets At this point, a CA SSL key pair should already be generated. However there is a likelihood of generating web server SSL key sets more frequently, especially if more than one Proxy or Satellite is deployed.
Red Hat Satellite 5.6 Client Configuration Guide # service httpd restart 4.3. Deploying the CA SSL Public Certificate to Clients T he Red Hat Satellite Proxy Server and Red Hat Satellite Server installation processes generate a CA SSL public certificate and package it in an RPM file. T hese installation processes make the certificate and RPM file publicly available by placing a copy of one or both into the /var/www/htm l/pub/ directory of the Satellite or Proxy Server.
Chapter 5. Reporting Software Failures Chapter 5. Reporting Software Failures You can take advantage of Red Hat Satellite's software failure reporting capabilities and the Automatic Bug Reporting T ool (ABRT ) to extend the overall reporting functionality of your systems. T his extended functionality allows your clients to automatically report software failures captured by ABRT to the Satellite server, and also to process the captured failures in a centralized fashion.
Red Hat Satellite 5.6 Client Configuration Guide # abrt-cli list @0 Directory: /var/tmp/abrt/ccpp-2013-02-28-15:48:50-8820 count: 2 executable: /usr/bin/python2.7 package: python-2.7.3-13.fc16 time: Thu 28 Feb 2013 03:48:50 PM CET uid: 0 @1 Directory: /var/tmp/abrt/oops-2013-02-27-14:16:03-8107-1 count: 3 package: kernel time: Wed 27 Feb 2013 02:16:03 PM CET 2. After you have identified the failure that you want to report, use the --report option to send the report to the Satellite server.
Revision History Revision History Revision 3-21.4 00 Rebuild with publican 4.0.
Red Hat Satellite 5.6 Client Configuration Guide Remove chapter on Bootstraps and Scripting. Remove redundant tables that reproduce man pages. Revision 3-5 Final packaging for 5.5 Wed Sept 19 2012 Dan Macpherson Revision 3-4 Staging for review Fri Aug 10 2012 Athene Chan Revision 3-0 T ue Jun 28 2012 Prepared for Red Hat Satellite Server 5.
