Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Red Hat NETWORK PROXY SERVER 3.7
Summary of Contents for Red Hat NETWORK PROXY SERVER 3.7
- Page 1 RHN Proxy Server 3.7 Installation Guide...
- Page 2 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
-
Page 3: Table Of Contents
Table of Contents 1. Introduction............................. 1 1.1. Red Hat Network ....................... 1 1.2. RHN Proxy Server ......................1 1.3. Terms to Understand ......................2 1.4. How it Works ........................2 2. Requirements........................... 5 2.1. Software Requirements...................... 5 2.2. Hardware Requirements..................... 6 2.3. -
Page 5: Introduction
Internet. The clients’ System Profiles and user information are stored on the secure, central RHN Servers, which also serve the RHN website (rhn.redhat.com). The Proxy does not serve the website itself; It acts as a go-between for client systems and Red Hat Network. -
Page 6: Terms To Understand
RHN Proxy Server. Tracebacks are automatically generated when a critical error occurs and are mailed to the individual(s) designated in the RHN Proxy Server’s configuration file. For more detailed explanations of these terms and others, refer to the Red Hat Network Reference Guide available at http://www.redhat.com/docs/. -
Page 7: How It Works
Chapter 1. Introduction 1.4. How it Works The Red Hat Update Agent on the client systems does not directly contact a Red Hat Network Server. Instead, the client (or clients) connects to an RHN Proxy Server that connects to the Red Hat Network Servers. - Page 8 Chapter 1. Introduction Network Server). If the RHN Package Manager is used, the client systems must be subscribed to the private RHN channel.
-
Page 9: Requirements
Chapter 2. Requirements These requirements must be met before installation. To install RHN Proxy Server version 3.6 or later from RHN Satellite Server, the Satellite itself must be version 3.6 or later. 2.1. Software Requirements To perform an installation, the following software components must be available: Base operating system —... -
Page 10: Hardware Requirements
Chapter 2. Requirements Configuration of the system to accept remote commands and configuration management through • Red Hat Network. Refer to Section 4.2 RHN Proxy Server Installation Process for instructions. 2.2. Hardware Requirements The following hardware configuration is required for the RHN Proxy Server: Pentium III processor, 1.26GHz, 512K cache or equivalent •... - Page 11 Chapter 2. Requirements A Red Hat Network Account • Customers who will be connecting to the central Red Hat Network Servers to receive incremental updates will need an account with Red Hat Network. This account should be set up at the time of purchase with the sales representative.
- Page 12 Chapter 2. Requirements...
-
Page 13: Example Topologies
Chapter 3. Example Topologies The RHN Proxy Server can be configured in multiple ways. Select one method depending on the following factors: 1. The total number of client systems to be served by the RHN Proxy Server. 2. The maximum number of clients expected to connect concurrently to the RHN Proxy Server. 3. -
Page 14: Multiple Proxy Vertically Tiered Topology
Chapter 3. Example Topologies can be used to synchronize packages between the Proxies. Second, a Network File System (NFS) share can be established between the Proxies and the custom channel repository. Either of these solutions will allow any client of any RHN Proxy Servers to have all custom packages delivered to them. -
Page 15: Proxies With Rhn Satellite Server
Chapter 3. Example Topologies Figure 3-3. Multiple Proxy Vertically Tiered Topology 3.4. Proxies with RHN Satellite Server In addition to the methods described in detail within this chapter, customers also have the option of using RHN Proxy Server in conjunction with RHN Satellite Server. This works similarly to the vertically tiered Proxy configuration but increases capacity significantly, as Satellites can serve a much greater number of client systems. - Page 16 Chapter 3. Example Topologies...
-
Page 17: Installation
Chapter 4. Installation This chapter describes the initial installation of the RHN Proxy Server. It presumes the prerequisites listed in Chapter 2 Requirements have been met. If you are instead upgrading to a newer version of RHN Proxy Server, contact your Red Hat representative for assistance. 4.1. - Page 18 Chapter 4. Installation 4. Navigate to the System Details Packages Install subtab and search for . In the rhncfg ¡ ¡ resulting list, select all packages and install them. 5. If you will be enabling secure sockets layer (SSL) encryption on the Proxy and connecting to the central RHN Servers, install the package from the same Red Hat Network rhns-certs-tools...
- Page 19 Chapter 4. Installation Figure 4-2. Welcome 10. In the Welcome page, you will find notification of any requirements not met by the system. When the system is ready, a continue link appears. Click it to go to the Terms & Conditions page.
- Page 20 Chapter 4. Installation toring page appears next. Figure 4-4. Enable Monitoring 12. In the Enable Monitoring page, you must decide whether the Proxy will be used to monitor systems served by it. For this to take place, the RHN Proxy Server must meet the requirements identified in Chapter 2 Requirements and be connected to an RHN Satellite Server (or another Proxy connected to a Satellite).
- Page 21 Server. The RHN Parent Server is the domain name of the server serving the Proxy, either the central RHN Servers, another RHN Proxy Server or an RHN Satellite Server. To connect to the central RHN Servers, include the value xmlrpc.rhn.redhat.com. To connect to a Satellite or another Proxy, enter the parent system’s FQDN.
- Page 22 Chapter 4. Installation have SSL enabled by default) or to an RHN Satellite Server or RHN Proxy Server that has SSL enabled. Connection to the central RHN Servers requires upload of the certificate tar file mentioned earlier. Connection to a Satellite or another Proxy through SSL requires the CA certificate password used in enabling SSL on the parent system.
- Page 23 Chapter 4. Installation Figure 4-7. Upload SSL In the Upload SSL page applicable only to a Proxy connecting to the central RHN Servers, lo- cate the tar file created using the RHN SSL Maintenance Tool using the Browse button. It will be named with the machine rhn-org-httpd-ssl-archive-MACHINENAME-VERSION .tar...
- Page 24 Chapter 4. Installation Server or another Proxy which is in turn connected to a Satellite. You cannot achieve Monitoring through the central RHN Servers. When finished, click continue. The Install Progress page appears. Figure 4-9. Install Progress 16. In the Install Progress page, you may monitor the steps of the installation as they take place. Click the link to any step to go to its Action Details page.
-
Page 25: Rhn Package Manager
Before local packages can be provided through the RHN Proxy Server, a private channel is needed to store them. Perform the following steps to create a private channel: 1. Log in to the RHN Web interface at https://rhn.redhat.com. 2. Click Software on the top navigation bar. If the Manage Channels option is not present in the left navigation bar, ensure this user has channel editing permissions set. -
Page 26: Command Line Options
Chapter 5. RHN Package Manager is the list of packages to be uploaded. Alternatively, use the option to specify the local pkg-list directory that contains the packages to add to the channel. Ensure the directory contains only the packages to be included and no other files. RHN Package Manager can also read the list of packages from standard input (using --stdin To upload the package headers for the source RPMs:... - Page 27 Chapter 5. RHN Package Manager Option Description Push only the packages that are newer than packages --newest already pushed to the server for the specified channel. Read the package names from stdin. --stdin USERNAME Specify your RHN username. If you do not provide one --username with this option, you will be prompted for it.
- Page 28 Chapter 5. RHN Package Manager...
-
Page 29: Troubleshooting
This chapter provides tips for determining the cause of and resolving the most common errors as- sociated with RHN Proxy Server. If you need additional help, contact Red Hat Network support at https://rhn.redhat.com/help/contact.pxt. Log in using your Satellite-entitled account to see your full list of options. -
Page 30: General Problems
RHN Proxy Server. The latest version can be obtained through the Red Hat Network or from http://www.redhat.com/support/errata/. Also, be advised that since the RHN Proxy Server acts as a caching mechanism for RHN, the... -
Page 31: Connection Errors
Chapter 6. Troubleshooting 6.5. Host Not Found/Could Not Determine FQDN Because RHN configuration files rely exclusively on fully qualified domain names (FQDN), it is imperative key applications are able to resolve the name of the RHN Proxy Server into an IP address. Red Hat Update Agent, Red Hat Network Registration Client, and the Apache HTTP Server are particularly prone to this problem with the RHN applications issuing errors of "host not found"... -
Page 32: Caching Issues
Chapter 6. Troubleshooting 6.7. Caching Issues If package delivery fails or an object appears to be corrupt, and it isn’t related to connection errors, you should consider clearing the caches. The RHN Proxy Server has two caches you should be concerned with: one for Squid and the other for authentication. - Page 33 Chapter 6. Troubleshooting * copying configuration information * copying logs * querying RPM database (versioning of RHN Proxy, etc.) * get diskspace available * timestamping * creating tarball (may take some time): /tmp/rhn-proxy-debug.tar.bz2 * removing temporary debug tree Debug dump created, stored in /tmp/rhn-proxy-debug.tar.bz2 Deliver the generated tarball to your RHN contact or support channel.
- Page 34 Chapter 6. Troubleshooting...
-
Page 35: Sample Rhn Proxy Server Configuration File
# Username for that corporate HTTP proxy proxy.http_proxy_username = # Location of locally built, custom packages proxy.pkg_dir = /var/spool/rhn-proxy # Hostname of RHN Server or RHN Satellite proxy.rhn_parent = rhn.redhat.com # Destination of all tracebacks, etc. traceback_mail = user0@example.com, user1@example.com... - Page 36 Appendix A. Sample RHN Proxy Server Configuration File...
-
Page 37: Index
Index private channel, 21 additional requirements, 6 advantages, 2 questions and answers, 25 authentication, 3 authentication caching clearing, 28 Red Hat Network introduction, 1 Red Hat Update Agent, 2, 3 caching issues, 28 requirements, 5 channel, 2 additional, 6 creating a private channel, 21 disk space, 6 channel administrator, 2 hardware, 6...