Red Hat NETWORK SATELLITE 5.1.0 - CLIENT Configuration Manual

Also see for NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT: Release note Manual Reference guide

Red Hat NETWORK SATELLITE 5.1.0 - CLIENT Configuration Manual Manual pdf 9 page image

Client ApplicationsIn order to utilize most enterprise-class features of Red Hat Network, such as registering with aRHN Satellite, configuration of the latest client applications is required. Obtaining theseapplications before the client has registered with Red Hat Network can be difficult. This paradoxis especially problematic for customers migrating large numbers of older systems to Red HatNetwork. This chapter identifies techniques to resolve this dilemma.ImportantRed Hat strongly recommends that clients connected to a RHN Proxy Server orRHN Satellite Server be running the latest update of Red Hat Enterprise Linux toensure proper connectivity.Additionally, if client firewalls are configured, ports 80 and 443 should be openfor proper functionality with Red Hat Network.1. Deploying the Latest Red Hat Network Client RPMsRed Hat Update Agent (up2date) and Red Hat Network Registration Client (rhn_register)are prerequisites for using much of Red Hat Network's enterprise functionality. It is crucial toinstall them on client systems before attempting to use RHN Proxy Server or RHN SatelliteServer in your environment.There are several sensible approaches to accomplish this update of the RHN client software.One of which involves storing the RPMs in a location that is accessible by all client systems anddeploying the packages with the simplest command possible. In nearly all cases, a manualdeployment of up2date and rhn_register (if RHEL 2.1) do not need to be performed. Thoseclient tools should have no issues connecting to your RHN Satellite or Proxy environment.These discussion below assumes that the "out of box" up2date and rhn_register are not thelatest and do not work for your environment.Remember, only systems running Red Hat Enterprise Linux 2.1 must use the Red Hat NetworkRegistration Client to register with RHN. Systems running Red Hat Enterprise Linux 3 andlater can use the registration functionality built into the Red Hat Update Agent.This document presumes that the customer has installed at least one RHN Satellite Serverand/or RHN Proxy Server on their network. The example below demonstrates a simpleapproach of deploying up2date and rhn_register for the first time by an administratorassuming the machines don't already have a working RHN. The administrator has populated the/var/www/html/pub/ directory with a copy of the up2date and rhn_register (for RHEL 2.1systems) RPMs that his client systems need, and then has simply deployed those RPMs ontohis client systems with a simple rpm -Uvh command. Run from a client, this command installsthe RPMs to that client, assuming the domain name, paths, and RPM versions are correct:Chapter 2.3