Chapter 1.
Introduction
1.1. Red Hat Network
Red Hat Network (RHN) is the environment for system-level support and management of Red Hat
systems and networks of systems. Red Hat Network brings together the tools, services, and informa-
tion repositories needed to maximize the reliability, security, and performance of their systems. To use
RHN, system administrators register the software and hardware profiles, known as System Profiles,
of their client systems with Red Hat Network. When a client system requests package updates, only
the applicable packages for the client are returned (based upon the software profile stored on the RHN
Servers).
Advantages of using Red Hat Network include:
•
Scalability — with Red Hat Network, a single system administrator can set up and maintain hun-
dreds or thousands of Red Hat systems more easily, accurately, and quickly than that same admin-
istrator could maintain a single system without Red Hat Network.
•
Standard Protocols — standard protocols are used to maintain security and increase capability. For
example, XML-RPC gives Red Hat Network the ability to do much more than merely download
files.
•
Security — all communication between registered systems and Red Hat Network takes place over
secure Internet connections.
•
View Errata Alerts — easily view Errata Alerts for all your client systems through one website.
•
Scheduled Actions — use the website to schedule actions, including Errata Updates, package in-
stalls, and software profile updates.
•
Simplification — maintaining Red Hat systems becomes a simple, automated process.
1.2. RHN Proxy Server
An RHN Proxy Server is a service deployed within a corporate network with advanced Red Hat
Network functionality, such as a package-caching mechanism for reduced bandwidth usage and cus-
tomizable channels enabling custom package deployment.
This service allows a business or corporation to cache RPM Updates on an internal, centrally located
RHN Proxy Server and have the client systems download the updates from that server instead of
from one of the RHN Servers
1
over the 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. Only the RPM files are stored on the RHN Proxy Server. Every transaction is authenticated,
and the
Red Hat Update Agent
checks the GPG signature of each package retrieved from the local
RHN Proxy Server.
In addition to storing official Red Hat packages, the RHN Proxy Server can be configured to deliver
an organization’s own custom RPM packages from private RHN
channels
, using the RHN Package
Manager. For instance, an organization could develop its own software, package it in an RPM, sign it
1. Throughout this document, replace RHN Server with RHN Satellite Server if the RHN Proxy Server connects
to a RHN Satellite Server instead.
Summary of Contents for NETWORK PROXY SERVER 3.6 -
Page 1: ...RHN Proxy Server 3 6 Installation Guide ...
Page 4: ......
Page 12: ...8 Chapter 2 Requirements ...
Page 16: ...12 Chapter 3 Example Topologies ...
Page 28: ...24 Chapter 5 RHN Package Manager ...
Page 34: ...30 Chapter 6 Troubleshooting ...
Page 36: ...32 Appendix A Sample RHN Proxy Server Configuration File ...
Page 38: ......