1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. NETWORK SATELLITE SERVER 4.1.0
  6. Installation manual

Red Hat NETWORK SATELLITE SERVER 4.1.0 Installation Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
RHN Satellite Server 4.1.0
Installation Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETWORK SATELLITE SERVER 4.1.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Red Hat NETWORK SATELLITE SERVER 4.1.0

Summary of Contents for Red Hat NETWORK SATELLITE SERVER 4.1.0

  • Page 1 RHN Satellite Server 4.1.0 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 Satellite Server..................2 1.3. Terms to Understand ..................2 1.4. How it Works ....................3 1.5. Summary of Steps .....................5 2. Requirements........................9 2.1. Software Requirements ..................9 2.2. Hardware Requirements..................10 2.3.
  • Page 4 7. Troubleshooting......................51 7.1. Log Files ......................51 7.2. General Problems....................52 7.3. Host Not Found/Could Not Determine FQDN ..........53 7.4. Connection Errors ...................54 7.5. Satellite Debugging by Red Hat ..............55 8. Maintenance .........................57 8.1. Managing the Satellite Service ...............57 8.2. Updating the Satellite ..................57 8.3.

  • Page 5: Introduction

    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.

  • Page 6: Rhn Satellite Server

    Chapter 1. Introduction Scheduled Actions — use the website to schedule actions, including Errata Updates, • package installs, and software profile updates. Simplification — maintaining Red Hat systems becomes a simple, automated process. • 1.2. RHN Satellite Server RHN Satellite Server allows organizations to utilize the benefits of Red Hat Network with- out having to provide public Internet access to their servers or other client systems.

  • Page 7: How It Works

    Chapter 1. Introduction a specific architecture and Red Hat release. A child channel is a channel associated with a base channel that contains extra packages. Organization Administrator — An Organization Administrator is a user role with the • highest level of control over an organization’s Red Hat Network account. Members of this role can add other users, systems, and system groups to the organization as well as remove them.
  • Page 8 Chapter 1. Introduction RPM importing tools • Channel maintenance tools (Web-based) • Errata management tools (Web-based) • 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 up- dates from the organization’s internal RHN Satellite Server instead of the central Red Hat Network Servers.

  • Page 9: Summary Of Steps

    Chapter 1. Introduction private network; an Internet connection is not required for any of the systems. Refer to the RHN Proxy Server Installation Guide for more information. Figure 1-1. Using RHN Satellite Server and RHN Proxy Server Together 1.5. Summary of Steps Implementing a fully functional RHN Satellite Server requires more than installing soft- ware and a database.
  • Page 10 3. Your Red Hat contact creates a Satellite-entitled account on the RHN website and sends you the login information. 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 4.1.0. These can be found within the Downloads tab of the respective Channel Details pages.
  • Page 11 Chapter 1. Introduction 15. Record all relevant usernames, passwords and other login information and store in multiple secure places. 16. Now that the Satellite is populated with standard Red Hat channels and packages and all clients are connected to it, you may begin creating and serving custom channels and packages.
  • Page 12 Chapter 1. Introduction...

  • Page 13: Requirements

    /etc/selinux/config SELINUX=permissive system. More in-depth coverage of SELinux is available at http://www.redhat.com/docs/. You may also refer to the Red Hat Knowledgebase article on SELinux and RHN Satellite Server at http://kbase.redhat.com/faq/. Satellite installation disc or ISO — this contains the RHN Satellite Server Installation •...

  • Page 14: Hardware Requirements

    Chapter 2. Requirements Note Installing packages other than the packages contained in the @ Base package group can lead to package conflicts. Channel content — All software packages and data exported for all entitled Red Hat • channels. This content may be loaded directly on the Satellite after installation using the RHN Satellite Synchronization Tool or obtained from your Red Hat representative if synchronization is not possible, such as in a disconnected environment.

  • Page 15: Database Requirements

    Chapter 2. Requirements Stand-Alone Database Embedded Database 12 GB storage for the database repository, in the partition (local storage /rhnsat only) Strongly recommended - a SCSI drive connected to a level 5 RAID Separate partition (or better, a separate set of physical disks) for storing backups.
  • Page 16 Chapter 2. Requirements requirements. Red Hat supports RHN Satellite Server 4.1.0 installations in conjunction with Oracle 9i R2. The Stand-Alone Database must not run on the same server as the RHN Satellite Server. A single 6 GB tablespace is recommended as more than sufficient for most installations. It is possible for many customers to function with a smaller tablespace.

  • Page 17: Additional Requirements

    Firewall Rules RHN strongly recommends firewalling the RHN Satellite Server solution from the In- ternet. However, it must be able to issue outbound connections to rhn.redhat.com, xml- rpc.rhn.redhat.com and satellite.rhn.redhat.com on ports 80 and 443. Also, if Monitoring is enabled on your RHN Satellite Server, inbound traffic must be allowed on port 4545.
  • Page 18 It is imperative that customers keep track of all primary login information. For RHN Satellite Server, this includes usernames and passwords for the Organization Admin- istrator account on rhn.redhat.com, the primary administrator account on the Satellite itself, SSL certificate generation, and database connection (which also requires a SID, or net service name).
  • Page 19 Chapter 2. Requirements • All unnecessary services should be disabled using ntsysv or chkconfig • service should be enabled. httpd • If the Satellite serves Monitoring-entitled systems and you wish to acknowledge via email the alert notifications you receive, you must configure sendmail to properly handle incoming mail as described in Section 4.4 Sendmail Configuration.
  • Page 20 Chapter 2. Requirements...

  • Page 21: Example Topologies

    Chapter 3. Example Topologies The RHN Satellite Server can be configured in multiple ways. Select one method depend- ing 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 •...

  • Page 22: Multiple Satellite Horizontally Tiered Topology

    Chapter 3. Example Topologies Figure 3-1. Single Satellite Topology 3.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.

  • Page 23: Satellite-Proxy Vertically Tiered Topology

    Chapter 3. Example Topologies Figure 3-2. Multiple Satellite Horizontally Tiered Topology 3.3. Satellite-Proxy Vertically Tiered Topology An alternative method to balance load is to install RHN Proxy Servers below a RHN Satel- lite Server. These Proxies connect to the Satellite for RPMs from Red Hat Network and custom packages created locally.
  • Page 24 Chapter 3. Example Topologies Figure 3-3. Satellite-Proxy Vertically Tiered Topology...

  • Page 25: Installation

    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 upgrad- ing to a newer version of RHN Satellite Server, contact your Red Hat representative for assistance.
  • Page 26 Chapter 4. Installation 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 loaded onto the Satellite. It can be named anything and located in any directory.
  • Page 27 Chapter 4. Installation 10. The next step creates and populates the initial database, if you have opted for the RHN Satellite Server with Embedded Database. If you are installing RHN Satellite Server with Stand-Alone Database, the installer connects with the database. This step can take quite a while.
  • Page 28 Chapter 4. Installation * Final configuration. * Restarting services. Installation complete. Visit https://your-satellite.example.com to create the satellite administrator 15. Follow the on-screen instructions and visit the FQDN of your Satellite via a web browser. Create the satellite administrator account - also referred to as the Organiza- tion Administrator - and click the Create Login button to move to the next screen, the Your RHN screen.
  • Page 29 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 Monitor- ing is enabled.
  • Page 30 Chapter 4. Installation 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.
  • Page 31 Chapter 4. Installation Figure 4-4. Monitoring 19. The RHN Satellite Configuration - Certificate page allows you to either 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.
  • Page 32 Chapter 4. Installation Figure 4-5. Certificate 20. The RHN Satellite Configuration - Bootstrap page allows you to generate a boot- strap script for redirecting client systems from the central RHN Servers to the Satel- lite. This script, to be placed in the directory /var/www/html/pub/bootstrap/ of the Satellite, significantly reduces the effort involved in reconfiguring all systems,...
  • Page 33 Chapter 4. Installation Figure 4-6. Bootstrap 21. The RHN Satellite Configuration - Restart page contains the final step in con- figuring the Satellite. Click the Restart button to restart the Satellite in order to incorporate all of the configuration options added on the previous screens.
  • Page 34 Chapter 4. Installation 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...

  • Page 35: Options To The Satellite Installation Program

    Chapter 4. Installation 4.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 Print this help message. --help Indicates the location of an answer file to be use for --answer-file= <...

  • Page 36: Automated Rhn Satellite Server Installation

    Chapter 4. Installation Table 4-1. Installation Options 4.3. Automated RHN Satellite Server Installation One option of the RHN Satellite Server Installation Program allows the user to reference an answer file. This file contains pre-determined responses to all, or some, of the questions asked by the installer program.

  • Page 37: Mysql Installation

    Chapter 4. Installation To configure sendmail correctly, run the following commands as root. First, create a sym- bolic link allowing sendmail to run the notification enqueuer with the following command: ln -s /opt/notification/scripts/ack_enqueuer.pl /etc/smrsh/. Next, edit the file on the mail server and add the following line: /etc/aliases rogerthat01: | /etc/smrsh/ack_enqueuer.pl Next, edit the...
  • Page 38 Chapter 4. Installation...

  • Page 39: Entitlements

    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; how- ever, for RHN Satellite Server, entitlements are contractually agreed-upon beforehand, and they are set at installation time.

  • Page 40: Uploading The Rhn Entitlement Certificate

    If your RHN Satellite Server is connected to the Internet, you have the option of uploading your new RHN Entitlement Certificate through the RHN website. To do this: 1. Log into https://rhn.redhat.com with your organization’s Satellite-entitled account. 2. Click Systems in the top navigation bar and then the name of the RHN Satellite Server.

  • Page 41: Command Line Entitlement Options

    Chapter 5. Entitlements 5.3. Managing the RHN Certificate with RHN Satellite Activate For disconnected Satellites or customers who prefer to work locally, Red Hat provides a command line tool for managing your RHN Entitlement Certificate and activating the Satellite using that certificate: RHN Satellite Activate ( rhn-satellite-activate This is included with the Satellite installation as part of the rhns-satellite-tools...
  • Page 42 Chapter 5. Entitlements 2. Activate the Satellite locally by inserting the RHN Entitlement Certificate into the local database. 3. Activate the Satellite remotely by inserting the RHN Entitlement Certificate into the central RHN (remote) database. This is typically accomplished during local activa- tion but may require a second step if you chose the option.

  • Page 43: Importing And Synchronizing

    Chapter 6. Importing and Synchronizing After installing the RHN Satellite Server, you must provide it with the packages and chan- nels 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.
  • Page 44 Chapter 6. Importing and Synchronizing example, if you use with you must --no-kickstarts rhn-satellite-exporter specify the option when importing the data. --no-kickstarts 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.

  • Page 45: Exporting

    Chapter 6. Importing and Synchronizing Option Description Alternative email address for --email. --traceback-mail Include alternate database connect string: --db=DB username/password@SID. Table 6-1. RHN Satellite Exporter Options 6.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.

  • Page 46: Satellite-Sync

    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 struc- tures 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.
  • Page 47 Chapter 6. Importing and Synchronizing , the RHN Satellite Synchronization Tool offers many other com- In addition to --step mand line options. To use them, insert the option and the appropriate value after the command when launching import/synchronization. satellite-sync Option Description Display this list of options and exit.
  • Page 48 Chapter 6. Importing and Synchronizing Option Description Email a report of what was --email imported/synchronized to the designated recipient of traceback email. Direct sync output (from --traceback-mail=TRACEBACK_MAIL --email to this email address. Include the hostname of an --server=SERVER alternative server to connect to for synchronization.

  • Page 49: Preparing For Import From Local Media

    Chapter 6. Importing and Synchronizing 6.2.2. Preparing for Import from Local Media To perform the RHN Satellite Server import, the following prerequisites must be met: The RHN Satellite Server installation must have been performed successfully. • The Red Hat Network Channel Content ISOs or RHN Satellite Exporter data must be •...

  • Page 50: Running The Import

    Chapter 6. Importing and Synchronizing 7. Then unmount in preparation for the next CD or ISO: /mnt/import umount /mnt/import 8. Repeat these steps for each Channel Content ISO of every channel to be imported. 6.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.

  • Page 51: Synchronizing

    Chapter 6. Importing and Synchronizing 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. No packages are necessary for registration, although updates cannot be retrieved from the Satellite until the channel is completely populated.

  • Page 52: Synchronizing Errata And Packages Directly Via Rhn

    Chapter 6. Importing and Synchronizing advisories published by RHN must be manually imported and synchronized by the admin- istrator of the RHN Satellite Server. During synchronization over the Internet, the RHN Satellite Synchronization Tool per- forms the following steps: 1. Connects over SSL to central RHN Servers, authenticates itself as an RHN Satel- lite Server, and triggers an export of RHN data —...

  • Page 53: Synchronizing Errata And Packages Via Local Media

    Chapter 6. Importing and Synchronizing 6.3.2. Synchronizing Errata and Packages via Local Media For customers who cannot connect their Satellite directly to RHN, Red recommends downloading Channel Content ISOs separate, Internet-connected system and then transferring them to the Satellite. Refer to Section 6.2.2.1 Preparing Channel Content ISOs for instructions on downloading the ISOs.
  • Page 54 Chapter 6. Importing and Synchronizing...

  • Page 55: 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.

  • Page 56: General Problems

    Chapter 7. Troubleshooting Component/Task Log File Location Red Hat Update Agent /var/log/up2date XML-RPC transactions /var/log/rhn/rhn_server_xmlrpc.log Table 7-1. Log Files 7.2. General Problems To begin troubleshooting general problems, examine the log file or files related to the component exhibiting failures. A useful exercise is to issue the command for all tail -f log files and then run...

  • Page 57: Host Not Found/Could Not Determine Fqdn

    If the administrator is not getting email from the RHN Satellite Server, confirm the correct email addresses have been set for traceback_mail /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 option web.default_mail_from and appropriate value in /etc/rhn/rhn.conf...

  • Page 58: Connection Errors

    Chapter 7. Troubleshooting To resolve this problem, identify the contents of the file. It may look like /etc/hosts 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 HTTP Server.

  • Page 59: Satellite Debugging By Red Hat

    Chapter 7. Troubleshooting The following measures can be used to troubleshoot general connection errors: Attempt to connect to the RHN Satellite Server’s database at the command line using • the correct connection string as found in /etc/rhn/rhn.conf sqlplus username/password@sid Ensure the RHN Satellite Server is using Network Time Protocol (NTP) and set to the •...
  • Page 60 Chapter 7. Troubleshooting * creating tarball (may take some time): /tmp/satellite-debug.tar.bz2 * removing temporary debug tree Debug dump created, stored in /tmp/satellite-debug.tar.bz2 Deliver the generated tarball to your RHN contact or support channel. Once finished, email the new file from the directory to your Red Hat representative /tmp/ for immediate diagnosis.

  • Page 61: Maintenance

    RHN Satellite Server or use the website up2date -u at https://rhn.redhat.com to apply the updates. Important Apache RPMs do not restart the httpd service upon installation. Therefore, after conduct- ing a full update of an RHN Satellite Server (such as with the command up2date -uf Apache may fail.

  • Page 62: Backing Up The Satellite

    For RHN Satellite Server systems that may not be connected to the Internet, the packages themselves may be retrieved using a customer account at https://rhn.redhat.com. Then, they can be applied manually by the customer according to instructions in the Errata Advisory.

  • Page 63: Using Rhn Db Control

    Chapter 8. Maintenance ) is primarily a duplicate of Red Hat’s RPM /var/satellite/redhat/NULL/ repository, it can be regenerated with . Red Hat recommends the satellite-sync entire tree be backed up. In the case of disconnected satellites, /var/satellite/ must be backed up.

  • Page 64: Backing Up The Database

    Chapter 8. Maintenance Option Description Examines the contents of a backup directory. examine DIRNAME Returns the timestamp of backup creation and reports on its contents. Increase the RHN Oracle tablespace extend Reports on current usage of database space. report Restores the database from backup kept in restore DIRNAME DIRNAME.

  • Page 65: Verifying The Backup

    Chapter 8. Maintenance utes. The first backup is a good indicator of how long subsequent backups will take. Once the backup is complete, return to root user mode and restart the database and related services with the following command: service rhn-satellite start You should then copy that backup to another system using rsync or another file-transfer utility.

  • Page 66: Cloning The Satellite With Embedded Db

    Chapter 8. Maintenance 8.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.

  • Page 67: Conducting Satellite-Specific Tasks

    Chapter 8. Maintenance 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.

  • Page 68: Using The Tools Menu

    Chapter 8. Maintenance directly related to managing custom channels and Errata are covered in the RHN Chan- nel Management Guide. This section seeks to explain activities available only to Satellite customers. 8.7.1. Using the Tools menu In addition to the standard categories available to all users through the top navigation bar, Satellite Organization Administrators also have access to a Tools menu.

  • Page 69: Deleting Users

    Chapter 8. Maintenance 8.7.1.1. Maintaining the RHN Task Engine 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.
  • Page 70 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 delet- ing the user from the RHN Satellite Server.

  • Page 71: Automating Synchronization

    Chapter 8. Maintenance 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.8. Automating Synchronization Manually synchronizing the RHN Satellite Server repository with Red Hat Network can be a time-intensive task.

  • Page 72: Implementing Pam Authentication

    Chapter 8. Maintenance This opens the crontab in a text editor, by default Vi. Another editor can be used by first changing the variable, like so: EDITOR export EDITOR=gedit Once opened, use the first five fields (minute, hour, day, month, and weekday) to sched- ule the synchronization.

  • Page 73: Enabling Push To Clients

    Chapter 8. Maintenance Please note that changing the password on the RHN website changes only the local pass- word 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. 8.10.
  • Page 74 Chapter 8. Maintenance...

  • Page 75: Sample Rhn Satellite Server Configuration File

    #/etc/rhn/rhn.conf example for an RHN Satellite #---------------------------------------------- # Destination of all tracebacks, such as crash information, etc. traceback_mail = test@pobox.com, test@redhat.com # Location of RPMs (Red Hat and custom) served by the RHN Satellite mount_point = /var/satellite # Corporate gateway (hostname:PORT): server.satellite.http_proxy = corporate_gateway.example.com:8080...
  • Page 76 Appendix A. Sample RHN Satellite Server Configuration File web.base_acls = RHN::Access web.default_taskmaster_tasks = RHN::Task::SessionCleanup, RHN::Task::ErrataQueue, RHN::Task::ErrataEngine, RHN::Task::DailySummary, RHN::Task::SummaryPopulation, RHN::Task::RHNProc, RHN::Task::PackageCleanup web.rhn_gpg_backend_module = RHN::GPG::OpenPGP web.restrict_mail_domains =...

  • Page 77: Index

    Index embedded database default location Symbols /rhnsat/, 21 enabling push to clients, 69 /etc/nsswitch.conf, 53 entitlement certificate, 14, 21 /etc/rhn/rhn.conf, 53 advantages, 2 firewall rules, 13 Apache, 57 Apache HTTP, 3 automating Satellite synchronization, 67 general problems, 52 GPG keys, 21 backing up the RHN Satellite Server, 58 host not found error could not determine FQDN, 53...
  • Page 78 of RHN Satellite Server, 21 sendmail, 32 Red Hat Network installation task list, 5 introduction, 1 Red Hat Update Agent definition, 2 redundant satellite, 62 log files, 51 requirements, 9 table, 51 additional, 13 database, 11 hardware, 10 software, 9 maintenance, 57 mysql-server, 33 components, 3...
  • Page 79 satellite redundancy, 62 satellite-debug, 55 satellite-sync, 46, 48 --step=channel-families, 47 --step=channels, 47 --step=rpms, 47 cron job, 67 sendmail, 15 summary of steps, 5 synchronizing keeping channel data in sync, 47 satellite data, 39 terms to understand, 2 tool use, 63 topologies, 17 multiple satellites horizontally tiered, 18 satellite and proxies vertically tiered, 19...

This manual is also suitable for:

Rhn satellite server 4.1.0

Table of Contents