Red Hat NETWORK PROXY 5.3.0 Installation Manual

Also see for NETWORK PROXY 5.3.0 -: Installation guide

Red Hat NETWORK PROXY 5.3.0 Installation Manual Manual pdf 13 page image

Chapter 3.9Example TopologiesThe RHN Proxy Server can be configured in multiple ways. Select one method depending on thefollowing factors:1. The total number of client systems to be served by the RHN Proxy Server2. The maximum number of clients expected to connect concurrently to the RHN Proxy Server.3. The number of custom packages and channels to be served by the RHN Proxy Server.4. The number of RHN Proxy Servers being used in the customer environment.The rest of this chapter describes possible configurations and explains their benefits.3.1. Single Proxy TopologyThe simplest configuration is to use a single RHN Proxy Server to serve your entire network. Thisconfiguration is adequate to service a small group of clients and a network that would benefit fromcaching Red Hat RPMs and storing custom packages on a local server.The disadvantage of using one RHN Proxy Server is that performance will be compromised as thenumber of clients requesting packages grows.Figure 3.1. Single Proxy Topology3.2. Multiple Proxy Horizontally Tiered TopologyFor larger networks, a more distributed method may be needed, such as having multiple RHN ProxyServers all connecting to Red Hat Network individually. This horizontally tiered configuration balancesthe load of client requests while enabling each Proxy to simultaneously synchronize with RHN.A disadvantage of this horizontal structure is that custom packages loaded to an individual Proxy mustbe distributed to its sibling servers. This situation can be addressed in one of two ways:• The rsync file transfer program can be used to synchronize packages between the Proxies