Red Hat Network Satellite Installation Guide 5.1.0 5.
Red Hat Network Satellite
Red Hat Network Satellite: Installation Guide 5.1.0 Copyright © 2008 Red Hat, Inc. Copyright © 2008 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0 or later with the restrictions noted below (the latest version of the OPL is presently available at http://www.opencontent.org/openpub/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.
Red Hat Network Satellite
1. Introduction ........................................................................................................... 1 1. Red Hat Network ........................................................................................... 1 2. RHN Satellite Server ...................................................................................... 2 3. Terms to Understand ...................................................................................... 2 4. How it Works ................................
Red Hat Network Satellite 5. Updated Software Components .....................................................................55 6. Satellite Debugging by Red Hat .....................................................................56 8. Maintenance .........................................................................................................57 1. Managing the Satellite Service .......................................................................57 2. Updating the Satellite ...................
Chapter 1. Introduction RHN Satellite Server provides a solution to organizations requiring absolute control over and privacy of the maintenance and package deployment of their servers. It allows Red Hat Network customers the greatest flexibility and power in keeping servers secure and updated. Two types of RHN Satellite Server are available: One with a stand-alone database on a separate machine and one with an embedded database installed on the same machine as the Satellite.
Chapter 1. Introduction 2. RHN Satellite Server RHN Satellite Server allows organizations to utilize the benefits of Red Hat Network without having to provide public Internet access to their servers or other client systems. System Profiles are stored locally on the customer's RHN Satellite Server. The Red Hat Network website is served from a local Web server and is not accessible from the Internet. All package management tasks, including Errata Updates, are performed through the local area network.
How it Works • certificate authority — A Channel Administrator is a user role with full access to channel management capabilities. Users with this role are capable of creating channels, assigning packages to channels, cloning channels, and deleting channels. This role can be assigned by an Organization Administrator through the Users tab of the RHN website.
Chapter 1. Introduction • User management tools (Web-based) • Client system and system grouping tools (Web-based) • Red Hat Update Agent on the client systems The Red Hat Update Agent on the client systems must be reconfigured to retrieve updates from the organization's internal RHN Satellite Server instead of the central Red Hat Network Servers.
Summary of Steps Figure 1.1. Using RHN Satellite Server and RHN Proxy Server Together 5. Summary of Steps Implementing a fully functional RHN Satellite Server requires more than installing software and a database. Client systems must be configured to use the Satellite. Custom packages and channels should be created for optimal use. Since these tasks extend beyond the basic installation, they are covered in detail in other guides, as well as this RHN Satellite Server Installation Guide.
Chapter 1. Introduction 4. Log into the RHN website (rhn.redhat.com) and download the distribution ISOs for Red Hat Enterprise Linux AS 3 or 4 and RHN Satellite Server 5.0.0. These can be found within the Downloads tab of the respective Channel Details pages. Refer to the RHN Reference Guide for instructions. 5. While still logged into the RHN website, download the Channel Content ISOs to be served by your Satellite, also available through the Downloads tab of your Satellite's Channel Details page.
Upgrades website. Refer to the RHN Channel Management Guide for details. 6. Upgrades The process for upgrading a Satellite from one version to another is not covered within this Satellite Guide, but can be found within the Red Hat Knowledgebase ( http://kbase.redhat.com/faq/1) and can be found by performing a search for upgrade satellite or by following this link — http://kbase.redhat.com/faq/FAQ_49_8610.shtm. 1 http://kbase.redhat.
8
Chapter 2. Requirements These requirements must be met before installation. 1. Software Requirements To perform an installation, the following software components must be available: • Base operating system — RHN Satellite Server is supported with Red Hat Enterprise Linux AS 3 Update 5 or later, or Red Hat Enterprise Linux AS 4 or later.
Chapter 2. Requirements Satellite Synchronization Tool or obtained from your Red Hat representative if synchronization is not possible, such as in a disconnected environment. When installing Red Hat Enterprise Linux AS 3 or 4 from CD or ISO image, there is no need to select any package groups, only the base install is required. When installing either operating system via kickstart, select the @ Base package group. 2.
Database Requirements • 2 GB of memory See Section 3, “Database Requirements” for instructions on estimating the tablespace of the database and setting its environment variables. Keep in mind, the frequency with which client systems connect to the Satellite is directly related to load on the Apache Web server and the database.
Chapter 2. Requirements the following factors: • The number of public Red Hat packages imported (typical: 5000) • The number of private packages to be managed (typical: 500) • The number of systems to be managed (typical: 1000) • The number of packages installed on the average system (typical: 500) Although you should be generous in your database sizing estimates, you must consider that size affects the time to conduct backups and adds load to other system resources.
Additional Requirements • Auto Segment Space Management • UTF-8 character set Note Ensure that the NLS/charset setting is set to "UTF8"' when using an external database, not 'AL32UTF8' or other charsets. Using other charsets may lead to problems later. The disk layout on the database machine is independent of the RHN Satellite Server and entirely up to the customer. 4.
Chapter 2. Requirements Port Direction Reason xmlrpc.rhn.redhat.com5 and satellite.rhn.redhat.com6(unless running in a disconnected mode for Satellite) 4545 Outbound RHN Satellite Server Monitoring makes connections to rhnmd running on client systems, if Monitoring is enabled and probes are configured for registered systems. 5222 Inbound If you plan to push actions to client systems 5269 Inbound If you push actions to an RHN Proxy Server Table 2.2.
Additional Requirements be linked to a working DNS server in the customer environment. • An Entitlement Certificate The customer will receive, via email from the sales representative, a signed Entitlement Certificate explaining the services provided by Red Hat through RHN Satellite Server. This certificate will be required during the installation process.
Chapter 2. Requirements Satellite with the central Red Hat Network Servers. All other RHN Satellite Servers should be synchronized directly over the Internet. • All unnecessary ports should be firewalled off. Client systems connect to RHN Satellite Server over ports 80, 443, and 4545 (if Monitoring is enabled).
Chapter 3. Example Topologies The RHN Satellite Server can be configured in multiple ways. Select one method depending on the following factors: • The total number of client systems to be served by the RHN Satellite Server. • The maximum number of clients expected to connect concurrently to the RHN Satellite Server. • The number of custom packages and channels to be served by the RHN Satellite Server. • The number of RHN Satellite Servers being used in the customer environment.
Chapter 3. Example Topologies 2. Multiple Satellite Horizontally Tiered Topology For very large networks, a more distributed method may be needed, such as having multiple RHN Satellite Servers in a horizontally tiered configuration and balancing the load of client requests. It is possible to synchronize content between RHN Satellites using the rhn-satellite-exporter and satellite-sync -m commands. This feature is discussed in detail in Section 1.1, “rhn-satellite-exporter”.
Satellite-Proxy Vertically Tiered Topology Figure 3.3.
20
Chapter 4. Installation This chapter describes the initial installation of the RHN Satellite Server. It presumes the prerequisites listed in Chapter 2, Requirements have been met. If you are instead upgrading to a newer version of RHN Satellite Server, contact your Red Hat representative for assistance. 1. Base Install The RHN Satellite Server is designed to run on the Red Hat Enterprise Linux AS operating system.
Chapter 4. Installation mount /dev/cdrom /media/cdrom If you are installing from an ISO, mount the file from within the directory containing it using the command: mount -o loop iso_filename /media/cdrom The remaining instructions assume it is mounted in /media/cdrom/. 4. Ensure that the RHN Entitlement Certificate has been copied onto the Satellite's file system. It can be named anything and located in any directory. The installation program will ask you for its location.
RHN Satellite Server Installation Program 7. At the prompt, enter the email address to which you would like notifications from the Satellite to be sent. It may be a good idea to choose a general email address rather than the address of an individual, as there can be a large volume of emails. ? Admin email address? sat-admin@example.com 8. The Satellite is then registered with your RHN Hosted account, and all required packages are installed and updated. * RHN Registration * Installing updates.
Chapter 4. Installation * Activating Satellite. Where is your satellite certificate file? /root/example.cert 13.The next step is to create a CA cert for the Satellite. To do so, you must answer a few questions. CA cert Enter a password for the certificate. Organization Enter the name of your organization Email Address Enter an email address to be associated with this certificate, such as the admin email entered in the steps above. City Enter the city where the Satellite resides.
RHN Satellite Server Installation Program Figure 4.1. Admin Account Creation 16.A blue text box appears at the top of the screen indicating that you can now custom-configure the Satellite and its behavior. To do so, click the bold clicking here text at the end.
Chapter 4. Installation Figure 4.2. Final Configuration Prompt 17.The Satellite Configuration - General Configuration page allows you to alter the most basic Satellite settings, such as the admin email address and whether Monitoring is enabled.
RHN Satellite Server Installation Program Figure 4.3. General Configuration 18.The RHN Satellite Configuration - Monitoring page allows you to configure the monitoring aspects of this Satellite. The local mail exchanger and local main domain are used to mail monitoring notification messages to administration. This is required only if you intend to receive alert notifications from probes. If you do, provide the mail server (exchanger) and domain to be used.
Chapter 4. Installation Figure 4.4. Monitoring 19.The RHN Satellite Configuration - Certificate page allows you to upload a new Satellite certificate. To identify the certificate's path, click Browse, navigate to the file, and select it. To input its contents, open your certificate in a text editor, copy all lines, and paste them directly into the large text field at the bottom. Red Hat recommends using the file locator as it is less error prone. Click Validate Certificate to continue.
RHN Satellite Server Installation Program Figure 4.5. Certificate 20.The RHN Satellite Configuration - Bootstrap page allows you to generate a bootstrap script for redirecting client systems from the central RHN Servers to the Satellite. This script, to be placed in the /var/www/html/pub/bootstrap/ directory of the Satellite, significantly reduces the effort involved in reconfiguring all systems, which by default obtain packages from the central RHN Servers.
Chapter 4. Installation Figure 4.6. Bootstrap 21.The RHN Satellite Configuration - Restart page contains the final step in configuring the Satellite. Click the Restart button to restart the Satellite in order to incorporate all of the configuration options added on the previous screens. Note that it will take between four and five minutes for the restart to finish.
Options to the Satellite Installation Program Figure 4.7. Restart 22.Once the Satellite has restarted, the countdown notice disappears. You are now free to begin using your Satellite. Figure 4.8. Restart Complete 2.1. Options to the Satellite Installation Program The various options available for the Satellite Installation Program are included below for easy reference. Option Usage --help Print this help message.
Chapter 4. Installation Option Usage Satellite is not currently supported on selinux-enabled systems. --skip-fqdn-test Do not verify that the system has a valid hostname. RHN Satellite requires that the hostname be properly set during installation. Using this option may result in a Satellite server that is not fully functional. --skip-db-install Do not install the embedded database. This option may be useful if you are reinstalling the satellite, and do not want to clear the database.
Sendmail Configuration The RHN Satellite Server Installation Program then looks for answers in the file. For any option no filled out in the file, the Installer Program prompts the user for the missing information. 4. Sendmail Configuration If your RHN Satellite Server will serve Monitoring-entitled systems and you wish to acknowledge via email the alert notifications you receive, you must configure sendmail to properly handle incoming mail.
Chapter 4. Installation newaliases Finally, update the sendmail-cf package: up2date sendmail-cf Note, disconnected installs must obtain this package from the ISO. Restart sendmail: service sendmail restart 5. MySQL Installation This sections is applicable only if your RHN Satellite Server will serve Monitoring-entitled systems and you wish to run MySQL probes against them. Refer to the Probes appendix of the RHN Reference Guide for a list of available probes.
Chapter 5. Entitlements The RHN Satellite Server, like RHN itself, provides all services to customers through the setting of entitlements. For RHN, entitlements are purchased by customers as needed; however, for RHN Satellite Server, entitlements are contractually agreed-upon beforehand, and they are set at installation time. All public channels are automatically available; the private channels that should also be made available through the Satellite are determined by the RHN Entitlement Certificate.
Chapter 5. Entitlements -----END PGP SIGNATURE---- Note Do not try to use this RHN Entitlement Certificate; it is just an example. The initial RHN Entitlement Certificate is generated by a member of the RHN team and emailed to a consultant or customer prior to installation. This process helps guarantee that we do not inadvertently install any RHN Satellite Servers that the RHN team does not know about.
Command Line Entitlement Options the Satellite installation as part of the rhns-satellite-tools package. 3.1. Command Line Entitlement Options The rhn-satellite-activate tool offers a handful of command line options for activating a Satellite using its RHN Entitlement Certificate: Option Description -h, --help Display the help screen with a list of options. --sanity-only Confirm certificate sanity. Does not activate the Satellite locally or remotely.
Chapter 5. Entitlements To validate an RHN Entitlement Certificate and populate the local database: rhn-satellite-activate --disconnected --rhn-cert=/path/to/demo.cert To validate an RHN Entitlement Certificate and populate both the local and the RHN database: rhn-satellite-activate --rhn-cert=/path/to/demo.cert Once you run this final command, the Satellite is running and able to serve packages locally and synchronize with the central RHN Servers. Refer to Chapter 6, Importing and Synchronizing. 4.
Chapter 6. Importing and Synchronizing After installing the RHN Satellite Server, you must provide it with the packages and channels to be served to client systems. This chapter explains how to import that data and keep it up to date whether the content is from RHN's central servers, local media, or from one Satellite within your organization to another. Two tools, RHN Satellite Exporter and RHN Satellite Synchronization Tool, come installed as part of the rhns-sat-tools package. 1.
Chapter 6. Importing and Synchronizing When exporting an RHN base channel, you must also export the tools channel associated with that base channel in order to kickstart machines to the distribution in the base channel. For instance, if you export rhel-i386-as-4 you must also export the rhn-tools-rhel-4-as-i386 channel in order to kickstart machines to Red Hat Enterprise Linux 4 AS.
Exporting Option Description --make-isos=cd or dvd --email Email a report of what was exported and what errors may have occurred. --traceback-mail Alternative email address for --email. --db=DB Include alternate database connect string: username/password@SID. Table 6.1. RHN Satellite Exporter Options 1.2. Exporting To perform a RHN Satellite Exporter export, the following prerequisites must be met: • The RHN Satellite Server installation must have been performed successfully.
Chapter 6. Importing and Synchronizing Important To populate custom channels correctly, you must first populate at least one Red Hat base channel. The RHN Satellite Synchronization Tool creates the necessary directory structures and permissions; without these, the custom channel tools will not work properly. For this reason, you should use these instructions to set up your base channel(s) and then refer to the RHN Channel Management Guide for steps to establish custom channels. 2.1.
satellite-sync In addition to --step, the RHN Satellite Synchronization Tool offers many other command line options. To use them, insert the option and the appropriate value after the satellite-sync command when launching import/synchronization. Option Description -h, --help Display this list of options and exit. -d=, --db=DB Include alternate database connect string: username/password@SID. -m=, --mount-point=MOUNT_POINT Import/sync from local media mounted to the Satellite.
Chapter 6. Importing and Synchronizing Option Description -s=, --server=SERVER Include the hostname of an alternative server to connect to for synchronization. --http-proxy=HTTP_PROXY Add an alternative HTTP proxy server in the form hostname:port. --http-proxy-username=PROXY_USERNAME Include the username for the alternative HTTP proxy server. --http-proxy-password=PROXY_PASSWORD Include the password for the alternative HTTP proxy server.
Preparing for Import from Local Media only if Channel Content ISOs are not available. It takes a long time to populate a channel from scratch over the Internet. For this reason, Red Hat urges you to use ISOs, if they are available, for initial import. 2.2.1. Preparing Channel Content ISOs Channel Content ISOs are special collections that contain both packages and XML dumps of metadata.
Chapter 6. Importing and Synchronizing cp -ruv /mnt/import/* /var/rhn-sat-import/ 7. Then unmount /mnt/import in preparation for the next CD or ISO: umount /mnt/import 8. Repeat these steps for each Channel Content ISO of every channel to be imported. 2.2.2. Preparing RHN Satellite Exporter Data In order to perform the import from data previously exported using RHN Satellite Exporter, you must first copy that data onto the local system.
Running the Import satellite-sync --list-channels --mount-point /var/rhn-sat-import The next step is to initiate the import of a specific channel. Do this using a channel label presented in the previous list. The command will look like: satellite-sync -c rhel-i386-as-3 --mount-point /var/rhn-sat-import Note Importing package data can take up to two hours per channel. You may begin registering systems to channels as soon as they appear in the RHN Satellite Server's website.
Chapter 6. Importing and Synchronizing Individually, use the --step=errata option. After running the preceding sample command, the population of the channel should be complete. All of the packages should have been moved out of the repository; this can be verified with the command cd /var/rhn-sat-import/; ls -alR | grep rpm.
Synchronizing Errata and Packages Directly The satellite-sync command can be used in two modes: via RHN and via local media. 3.1. Synchronizing Errata and Packages Directly via RHN For customers who want to sync data as frequently as possible and who can initiate connections outside of their own environments, the satellite sync can be run over the Internet through SSL. This is the default setting for the satellite sync script.
50
Chapter 7. Troubleshooting This chapter provides tips for determining the cause of and resolving the most common errors associated with RHN Satellite 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. In addition, you may package configuration information and logs from the Satellite and send them to Red Hat for further diagnosis.
Chapter 7. Troubleshooting component exhibiting failures. A useful exercise is to issue the tail -f command for all log files and then run up2date --list. You should then examine all new log entries for potential clues. A common issue is full disk space. An almost sure sign of this is the appearance of halted writing in the log files. If logging stopped during a write, such as mid-word, you likely have filled disks.
Host Not Found/Could Not Determine FQDN To derive the character set types of your Satellite's database, run the command: rhn-charsets If the administrator is not getting email from the RHN Satellite Server, confirm the correct email addresses have been set for traceback_mail in /etc/rhn/rhn.conf. If the traceback mail is marked from dev-null@rhn.redhat.com and you would like the address to be valid for your organization, include the web.default_mail_from option and appropriate value in /etc/rhn/rhn.conf.
Chapter 7. Troubleshooting and the RHN client applications to work. To resolve this problem, identify the contents of the /etc/hosts file. It may look like this: 127.0.0.1 this_machine.example.com this_machine localhost.localdomain \ localhost First, in a text editor, remove the offending machine information, like so: 127.0.0.1 localhost.localdomain.com localhost Then, save the file and attempt to re-run the RHN client applications or the Apache Web server.
Updated Software Components By default, the server certificate has a one-year life while client certificates are good for 10 years. If you find the certificates are incorrect, you can either wait for the valid start time, if possible, or create new certificates, preferably with all system times set to GMT.
Chapter 7. Troubleshooting Subscribing to these channels and updating your Satellite (such as by running up2date), may install newer, incompatible versions of critical software components, causing the Satellite to fail. 6. Satellite Debugging by Red Hat If you've exhausted these troubleshooting steps or want to defer them to Red Hat Network professionals, Red Hat recommends you take advantage of the strong support that comes with RHN Satellite Server.
Chapter 8. Maintenance Because of the RHN Satellite Server's unique closed environment, its users are provided with abilities not available to any other Red Hat Network customers. In addition, the Satellite itself also requires maintenance. This chapter discusses the procedures that should be followed to carry out administrative functions outside of standard use, as well as to apply patches to the RHN Satellite Server. 1.
Chapter 8. Maintenance can be applied manually by the customer according to instructions in the Errata Advisory. Warning It is very important to read the Errata Advisory before applying any RHN Satellite Server Errata Updates. Additional configuration steps may be required to apply certain RHN Satellite Server updates, especially if they involve the database. In such cases, the advisory will contain specific and detailed information about necessary steps that may be required.
Using RHN DB Control primarily a duplicate of Red Hat's RPM repository, it can be regenerated with satellite-sync. Red Hat recommends the entire /var/satellite/ tree be backed up. In the case of disconnected satellites, /var/satellite/must be backed up. Backing up only these files and directories would require reinstalling the RHN Satellite Server ISO RPMs and reregistering the Satellite. In addition, Red Hat packages would need to be resynchronized using the satellite-sync tool.
Chapter 8. Maintenance Option Description report Reports on current usage of database space. restore DIRNAME Restores the database from backup kept in DIRNAME. Database must be stopped for this command to run successfully. start Starts the database instance. This can also be accomplished by issuing the service rhn-database start command as root. status Shows the current status of the database, either "running" or "offline". stop Stops the database instance.
Verifying the Backup service rhn-satellite start You should then copy that backup to another system using rsync or another file-transfer utility. Red Hat strongly recommends scheduling the backup process automatically using cron jobs. For instance, back up the system at 3 a.m. and then copy the backup to the separate repository (partition, disk, or system) at 6 a.m. 4.3. Verifying the Backup Backing up the Embedded Database is useful only if you can ensure the integrity of the resulting backup.
Chapter 8. Maintenance 5. Cloning the Satellite with Embedded DB You may limit outages caused by hardware or other failures by cloning the Satellite with Embedded Database in its entirety. The secondary Satellite machine can be prepared for use if the primary fails. To clone the Satellite, perform these tasks: 1. Install RHN Satellite Server with Embedded Database (and a base install of Red Hat Enterprise Linux AS) on a separate machine, skipping the SSL Certificate generation step. 2.
Conducting Satellite-Specific Tasks schema, SSL certificate, and bootstrap script generation steps. Include the same RHN account and database connection information provided during the initial Satellite install and register the new Satellite. If your original SSL certificate does not take your high-availability solution into account, you may create a new one with a more appropriate Common Name value now. In this case, you may also generate a new bootstrap script that captures this new value. 3.
Chapter 8. Maintenance Using a RHN Satellite Server is quite similar to using the hosted version of Red Hat Network. For this reason, you should consult the RHN Reference Guide to obtain detailed instructions to standard tasks, such as editing System Profiles and updating packages. Tasks directly related to managing custom channels and Errata are covered in the RHN Channel Management Guide. This section seeks to explain activities available only to Satellite customers. 7.1.
Deleting Users The default display shows the status of the RHN Task Engine. This tool is a daemon that runs on the Satellite server itself and performs routine operations, such as database cleanup, Errata mailings, etc., that must be performed in the background. The page displays the execution times for various activities carried out by the daemon. Administrators should ensure the RHN Task Engine stays up and running. If this daemon hangs for any reason, it can be restarted using it's filename, taskomatic.
Chapter 8. Maintenance Figure 8.2. User Deletion A confirmation page appears explaining that this removal is permanent. To continue, click Delete User at the bottom-right corner of the page. Note The Organization Administrator role must be removed from the user's profile before deleting the user from the RHN Satellite Server. Failing to do so causes the delete operation to fail.
Automating Synchronization Figure 8.3. User Delete Confirmation Many other options exist for managing users. You can find instructions for them in the RHN website chapter of the RHN Reference Guide. 8. Automating Synchronization Manually synchronizing the RHN Satellite Server repository with Red Hat Network can be a time-intensive task. United States business hours tend to be the peak usage time for Red Hat Network, so synchronization at that time may be slow.
Chapter 8. Maintenance synchronization. Remember, hours use military time. Edit the crontab to include random synchronization, like so: 0 1 * * * perl -le 'sleep rand 9000' && satellite-sync --email >/dev/null \ 2>/dev/null This particular job will run randomly between 1:00 a.m. and 3:30 a.m. system time each night and redirect stdout and stderr from cron to prevent duplicating the more easily read message from satellite-sync. Options other than --email can also be included. Refer to Table 6.
Enabling Push to Clients #%PAM-1.0 auth auth auth account required sufficient required required pam_env.so pam_krb5.so no_user_check pam_deny.so pam_krb5.so no_user_check Please note that changing the password on the RHN website changes only the local password on the RHN Satellite Server, which may not be used at all if PAM is enabled for that user. In the above example, for instance, the Kerberos password will not be changed. 10.
Chapter 8. Maintenance Keep in mind, this feature depends on the client system recognizing the fully qualified domain name (FQDN) of the Satellite. This name and not the IP address of the server must be used when configuring the Red Hat Update Agent. Refer to the RHN Client Configuration Guide for details. Now when you schedule actions from the Satellite on any of the push-enabled systems, the task will begin immediately rather than wait for the system to check in.
Appendix A. Sample RHN Satellite Server Configuration File The /etc/rhn/rhn.conf configuration file for the RHN Satellite Server provides a means for you to establish key settings. Be warned, however, that errors inserted into this file may cause Satellite failures. So make configuration changes with caution. You should be particularly concerned with the following parameters: traceback_mail, default_db, and server.satellite.http_proxy.
Appendix A. Sample RHN Satellite Server Configuration File RHN::Task::RHNProc, RHN::Task::PackageCleanup web.rhn_gpg_backend_module = RHN::GPG::OpenPGP web.
chkconfig, 16 Index Symbols /etc/nsswitch.conf, 53 /etc/rhn/rhn.
Index M maintenance, 57 mysql-server, 34 N Network Time Protocol, 14 ntp, 14 ntsysv, 16 O operating system supported, 9 Oracle 9i R2, 3 Organization Administrator definition, 2 osa-dispatcher, 69 osad, 69 P PAM authentication implementation, 68 port 443, 13 port 4545, 13 port 5222, 13 port 5269, 13 port 80, 13 R Red Hat Network introduction, 1 Red Hat Update Agent definition, 2 redundant satellite, 62 requirements, 9 additional, 13 database, 11 DNS, 14 entitlement certificate, 15 firewall rules, 13 FQD
T terms to understand, 2 tool use, 63 topologies, 17 multiple satellites horizontally tiered, 18 satellite and proxies vertically tiered, 18 single satellite, 17 traceback, 3 definition, 2 troubleshooting, 51 /etc/hosts, 52 Embedded Database, 52 full disk space, 52 SSL_CONNECT errors, 54 traceback email address, 53 U updating the RHN Satellite Server, 57 75
76
