1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Server
  5. NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT
  6. Installation manual

Red Hat NETWORK SATELLITE 5.3.0 Installation Manual

Hide thumbs Also See for RED HAT NETWORK SATELLITE 5.3.0:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Configuration Manual
Red Hat Network
Satellite 5.3.0
Installation Guide
Red Hat Network Satellite

Advertisement

Table of Contents
loading

Related Manuals for Red Hat RED HAT NETWORK SATELLITE 5.3.0

Summary of Contents for Red Hat RED HAT NETWORK SATELLITE 5.3.0

  • Page 1 Red Hat Network Satellite 5.3.0 Installation Guide Red Hat Network Satellite...
  • Page 2 Installation Guide Red Hat Network Satellite 5.3.0 Installation Guide Red Hat Network Satellite Edition 2 Copyright © 2010 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/.

  • Page 3: Table Of Contents

    1. Introduction 1.1. Red Hat Network ......................1 1.2. RHN Satellite ....................... 1 1.3. Terms to Understand ....................2 1.4. How it Works ....................... 3 1.5. Summary of Steps ....................... 4 1.6. Upgrades ........................6 1.6.1. Satellite Certificate ..................... 6 1.6.2.
  • Page 4 Installation Guide 6.4.2. Configuring the Master RHN Satellite Server ............. 51 6.4.3. Configuring the Slave RHN Satellite Servers ............. 52 6.5. Using Inter-Satellite Sync .................... 52 6.5.1. Syncing between a Development Staging Server and a Production Satellite ..53 6.5.2. Bi-directional sync .................... 53 6.6.

  • Page 5: Introduction

    Chapter 1. Introduction RHN Satellite 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 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.

  • Page 6: Terms To Understand

    Chapter 1. Introduction • Security — an end-to-end secure connection is maintained from the client systems to the RHN Satellite without connecting to the public Internet. • Efficiency — packages are delivered significantly faster over a local area network. • Control — clients' System Profiles are stored on the local RHN Satellite, not on the central Red Hat Network Servers.

  • Page 7: How It Works

    How it Works For more detailed explanations of these terms and others, refer to the Red Hat Network Reference Guide. 1.4. How it Works RHN Satellite consists of the following components: • Database — for the Stand-Alone Database, this may be the organization's existing database or, preferably, a separate machine.

  • Page 8: Summary Of Steps

    Chapter 1. Introduction The organization can configure the website for the RHN Satellite to be accessible from the local area network only or from both the local area network and the Internet. The Satellite's version of the RHN website allows full control over client systems, system groups, and users. The RHN Satellite management tools are used to synchronize the RHN Satellite database and package repository with Red Hat Network.
  • Page 9 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 4 or Red Hat Enterprise Linux 5 and RHN Satellite. These can be found within the Downloads tab of the respective Channel Details pages.

  • Page 10: Upgrades

    • New Installation ISO 1.6.1. Satellite Certificate To obtain a Satellite certificate, visit Red Hat support at http://support.redhat.com. 1.6.2. Satellite Upgrade Documentation Package (rhn-upgrade) To install the rhn-upgrade package, ensure the satellite is registered to RHN and to the Red...

  • Page 11: New Installation Iso

    New Installation ISO 10. Click the Download Package link. 11. Copy the package to the Satellite server. 12. On the Satellite server run the following command: rpm -Uvh rhn-upgrade-version.rpm 1.6.3. New Installation ISO This ISO can be downloaded by performing the following steps: 1.

  • Page 13: Requirements

    /etc/selinux/config file to read SELINUX=permissive and reboot the 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 at http://kbase.redhat.com/faq/.

  • Page 14: Hardware Requirements

    Chapter 2. Requirements to download the files from RHN. If your system is not registered to RHN, you should have the Red Hat Enterprise Linux installation media available during the Satellite installation process to install these additional packages as needed. The files necessary for Satellite installation are listed in the rhelrpms file located in the updates directory on the Satellite installation ISO image.

  • Page 15: S/390 Hardware Requirements

    s/390 Hardware Requirements Stand-Alone Database Embedded Database Strongly recommended - a SCSI drive connected to a level 5 RAID Separate partition (or better, a separate set of physical disks) for storing backups. This can be any directory specifiable at backup time. Table 2.2.

  • Page 16: Additional Requirements

    Chapter 2. Requirements Stand-Alone Database Embedded Database Recommended - VSWITCH or Hipersocket LAN Recommended - VSWITCH or Hipersocket LAN for high speed connections to guests for high speed connections to guests z/VM required for kickstart/provisioning of guests. Table 2.3. Stand-Alone Database and Embedded Database Satellite Hardware Requirements for s/390 Platform 2.2.3.
  • Page 17 Database Requirements 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. If the database is shared, its hardware and spacing are entirely dependent on what else is using it. Additionally, block sizes must be a minimum of 8 KB for RHN Satellite to install properly.

  • Page 18: Additional Requirements

    Inbound Open this port to configure Satellite as a PXE server and allow installation and re- installation of PXE-boot enabled systems. Outbound Satellite uses this port to reach rhn.redhat.com xmlrpc.rhn.redhat.com satellite.rhn.redhat.com (unless running in a disconnected mode for Satellite) Inbound...
  • Page 19 If you do not have an Entitlement Certificate at installation time, contact Red Hat Global Support Services at: https://www.redhat.com/apps/support/ • A Red Hat Network Account Customers who connect to the central Red Hat Network Servers to receive incremental updates must have an external account with Red Hat Network.
  • Page 20 It is imperative that customers keep track of all primary login information. For RHN Satellite, this includes usernames and passwords for the Organization Administrator 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 21 Additional Requirements Finally, you should have the following technical documents in hand for use in roughly this order: 1. The RHN Satellite Installation Guide — This guide, which you are now reading, provides the essential steps necessary to get an RHN Satellite up and running. 2.

  • Page 23: Example Topologies

    Chapter 3. Example Topologies The RHN Satellite 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. • The maximum number of clients expected to connect concurrently to the RHN Satellite. •...

  • Page 24: Satellite-Proxy Vertically Tiered Topology

    Chapter 3. Example Topologies It is possible to synchronize content between RHN Satellites using the rhn-satellite-exporter Section 6.1.1, “rhn- and satellite-sync -m commands. This feature is discussed in detail in satellite-exporter”. Additional maintenance is the biggest disadvantage of this horizontal structure. Figure 3.2.
  • Page 25 Satellite-Proxy Vertically Tiered Topology Figure 3.3. Satellite-Proxy Vertically Tiered Topology...

  • Page 27: Installation

    Chapter 4. Installation This chapter describes the initial installation of the RHN Satellite. It presumes the prerequisites listed Chapter 2, Requirements have been met. If you are instead upgrading to a newer version of RHN Satellite, contact your Red Hat representative for assistance. 4.1.
  • Page 28 Chapter 4. Installation 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.
  • Page 29 RHN Satellite Installation Program * Setting up environment and users ** GPG: Initializing GPG and importing RHN key. ** GPG: Creating /root/.gnupg directory 10. The next step creates and populates the initial database, if you have opted for the RHN Satellite with Embedded Database.
  • Page 30 Chapter 4. Installation * Final configuration. * Restarting services. Installation complete. Visit https://your-satellite.example.com to create the satellite administrator account. 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 Organization Administrator - and click the Create Login button to move to the next screen, the Your RHN screen.
  • Page 31 RHN Satellite Installation Program 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.
  • Page 32 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 33 RHN Satellite Installation Program 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.
  • Page 34 Chapter 4. Installation 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.
  • Page 35 RHN Satellite Installation Program 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.

  • Page 36: Options To The Satellite Installation Program

    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 4.2.1. Options to the Satellite Installation Program The various options available for the Satellite Installation Program are included below for easy reference.

  • Page 37: Automated Rhn Satellite Server Installation

    Automated RHN Satellite Server Installation Option Usage For use only with --answer-file. If the --answer-file --non-interactive does not provide a required response, exit instead of prompting the user. Register the system with RHN, even if it is already registered. --re-register Install the satellite in disconnected mode.

  • Page 38: Sendmail Configuration

    Chapter 4. Installation 4. Once the answer file is ready, use the --answer-file option when starting the installation process from the command line: ./install.pl --answer-file=/tmp/answers.txt The RHN Satellite 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.

  • Page 39: Mysql Installation

    MySQL Installation yum update sendmail-cf Note, disconnected installs must obtain this package from the ISO. Restart sendmail: service sendmail restart 4.5. MySQL Installation This sections is applicable only if your RHN Satellite will serve Monitoring-entitled systems and you wish to run MySQL probes against them. Refer to the Probes appendix of the RHN Satellite Reference Guide for a list of available probes.

  • Page 41: Entitlements

    Chapter 5. Entitlements The RHN Satellite, 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, entitlements are contractually agreed-upon beforehand, and they are set at installation time.

  • Page 42: Uploading The Rhn Entitlement Certificate

    5.2. Uploading the RHN Entitlement Certificate If your RHN Satellite is connected to the Internet, you have the option of uploading your new RHN Entitlement Certificate through the RHN website. To do this: https://rhn.redhat.com 1. Log into with your organization's Satellite-entitled account.

  • Page 43: Activating The Satellite

    Activating the Satellite Option Description For testing only - Provides an alternative system ID --systemid=/PATH/TO/SYSTEMID by path and file. The system default is used if not specified. For testing only - Disable SSL. --no-ssl Table 5.1. RHN Entitlement Certificate Options To use these options, insert the option and the appropriate value, if needed, after the rhn- Section 5.3.2, “Activating the Satellite”.
  • Page 44 Chapter 5. Entitlements • The Satellite remains active. • Each user that logs into the Satellite sees a banner on their Your RHN page that explains that the Satellite certificate has expired. • Once a day, for all seven days, the Satellite Administrator's email receives notification that the certificate has expired.

  • Page 45: Importing And Synchronizing

    Chapter 6. Importing and Synchronizing After installing the RHN Satellite, 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.

  • Page 46: Exporting

    Chapter 6. Importing and Synchronizing The RHN Satellite Exporter offers several command line options. To use them, insert the option and appropriate value after the rhn-satellite-exporter command. Option Description Place the exported information into this directory. -d, --dir= Process data for this specific channel (specified -cCHANNEL_LABEL, -- by label) only.

  • Page 47: Importing With Rhn Satellite Synchronization Tool

    Importing with RHN Satellite Synchronization Tool • The RHN Satellite installation must have been performed successfully. • There must be sufficient disk space in the directory specified in the --dir option to contain the exported contents. Although it is not a requirement for the export to succeed, the export will be most useful when performed on a Satellite that has populated channels.
  • Page 48 Chapter 6. Importing and Synchronizing satellite-sync This tool can be used in a closed environment, such as the one created with a disconnected install, or it may obtain data directly over the Internet. Closed environment imports can get their data from downloaded ISOs or from the XML data generated by RHN Satellite Exporter.

  • Page 49: Preparing For Import From Local Media

    Preparing for Import from Local Media Option Description Perform the sync process only to the step --step=STEP_NAME specified. Typically used in testing. Do not retrieve actual RPMs. --no-rpms Do not process full package data. --no-packages Do not process Errata information. --no-errata Do not process kickstart data --no-kickstarts...
  • Page 50 Chapter 6. Importing and Synchronizing • The RHN Satellite installation must have been performed successfully. • The Red Hat Network Channel Content ISOs or RHN Satellite Exporter data must be available, or the Satellite must have access to the Internet and the RHN website. Although it is possible to conduct the import directly from the RHN website, this should be done only if Channel Content ISOs are not available.

  • Page 51: Running The Import

    Running the 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 52: Synchronizing

    Chapter 6. Importing and Synchronizing are necessary for registration, although updates cannot be retrieved from the Satellite until the channel is completely populated. You may repeat this step for each channel or include them all within a single command by passing each channel label preceded by an additional -c flag, like so: satellite-sync -c channel-label-1 \ -c channel-label-2 \...

  • Page 53: Synchronizing Errata And Packages Directly Via Rhn

    Synchronizing Errata and Packages Directly via RHN 2. Examines the export and identifies differences between the RHN Satellite data set and the exported RHN data set. For a particular channel, the following information is analyzed: • Channel metadata • Metadata of all packages in that channel •...

  • Page 54: Inter-Satellite Sync

    Chapter 6. Importing and Synchronizing This can be used to perform the sync process described above, using the dump files in /var/rhn- Section 6.2.3, “Running the sat-sync to perform the necessary comparisons and imports. See Import” for precise steps. 6.4. Inter-Satellite Sync RHN Satellite 5.3 or greater supports synchronization between two Satellites.

  • Page 55: Configuring The Master Rhn Satellite Server

    Configuring the Master RHN Satellite Server Figure 6.2. Master Server and Slave Peers that include their own custom content In this example, the master Satellite is the development channel, from which content is distributed to all production slave Satellites. Some slave Satellites have extra content not present in master Satellite channels.

  • Page 56: Configuring The Slave Rhn Satellite Servers

    Chapter 6. Importing and Synchronizing allowed_iss_slaves= By default, no slave Satellites are specified to sync from the master server, so you must enter the hostname of each slave Satellite server, separated by commas. For example: allowed_iss_slaves=slave1.satellite.example.org,slave2.satellite.example.org Once you finished configuring the rhn.conf file, restart the httpd service by issuing the following command: service httpd restart 6.4.3.

  • Page 57: Syncing Between A Development Staging Server And A Production Satellite

    Figure 6.4. Syncing from RHN Hosted and a Satellite Staging Server Normally, the administrator runs: satellite-sync -c your-channel This command downloads directly from data from rhn_parent (usually RHN Hosted, rhn.redhat.com). Then, to sync from the staging Satellite server address , the administrator runs: satellite-sync --iss-parent=staging-satellite.example.com -c custom-channel 6.5.2.
  • Page 58 Chapter 6. Importing and Synchronizing The aim is for Satellite sync to be able to import content with respect to org_id. This targets two sets of users. One is the disconnected Multi-Org case, where the main source of content for the user is either to get content from channel dumps or to export them from connected satellites and import it to the Satellite.

  • Page 59: Troubleshooting

    RHN Satellite. If you need additional help, contact Red Hat Network support at 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 Section 7.8, “Satellite Debugging by Red Hat”...

  • Page 60: Log Files

    Chapter 7. Troubleshooting Report Invoked as Description Errata details Lists all errata that affects systems registered to the errata-list Satellite Errata for systems Lists applicable errata and any registered systems errata- that are affected. systems Users in the system Lists all users registered to the Satellite. users Systems administered List of systems that individual users can administer.

  • Page 61: General Problems

    General Problems 7.3. 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 tail -f command for all log files and then run yum list on Red Hat Enterprise Linux 5 (or up2date --list on earlier Red Hat Enterprise Linux versions).

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

    If the administrator is not getting email from the RHN Satellite, 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.

  • Page 63: Connection Errors

    Connection Errors Then, save the file and attempt to re-run the RHN client applications or the Apache Web server. If they still fail, explicitly identify the IP address of the Satellite in the file, such as: 127.0.0.1 localhost.localdomain.com localhost 123.45.67.8 this_machine.example.com this_machine Replace the value here with the actual IP address of the Satellite.

  • Page 64: Selinux Issues

    Chapter 7. Troubleshooting 7 rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm is installed on the RHN Satellite and the corresponding rhn-org-trusted-ssl-cert- *.noarch.rpm or raw CA SSL public (client) certificate is installed on all client systems. • Verify the client systems are configured to use the appropriate certificate. •...
  • Page 65 Satellite Debugging by Red Hat Warning: this may take some time... * copying configuration information * copying logs * querying RPM database (versioning of RHN Satellite, etc.) * querying schema version and database character sets * get diskspace available * timestamping * 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...

  • Page 67: Maintenance

    For RHN Satellite 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 68: Backing Up The Satellite

    • /root/ssl-build/ If possible, back up /var/satellite/, as well. In case of failure, this will save lengthy download time. Since /var/satellite/ (specifically /var/satellite/redhat/NULL/) is 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.

  • Page 69: Using Rhn Db Control

    Using RHN DB Control The final and most comprehensive method would be to back up the entire machine. This would save time in downloading and reinstalling but would require additional disk space and back up time. Note Regardless of the back-up method used, when you restore the Satellite from a back-up, you must run the following command to schedule the recreation of search indexes the next time the rhn-search service is started: /etc/init.d/rhn-search cleanindex...

  • Page 70: Backing Up The Database

    Chapter 8. Maintenance Option Description Restores the database from backup kept in DIRNAME. restore DIRNAME Database must be stopped for this command to run successfully. Starts the database instance. This can also be start accomplished by issuing the service rhn- database start command as root.

  • Page 71: Verifying The Backup

    Verifying the Backup off-site. To conduct a backup, shut down the database and related services first by issuing the following command as root: /usr/sbin/rhn-satellite stop Then switch to the oracle user and issue this command to initiate the backup: db-control backup DIRNAME Backup files are stored in the directory specified.

  • Page 72: Cloning The Satellite With Embedded Db

    Chapter 8. Maintenance db-control restore DIRNAME This not only restores the Embedded Database but first verifies the contents of the backup directory using md5sums. Once the restoration is complete, return to root user mode and restart the database and related services with these commands in this order: /usr/sbin/rhn-satellite start 8.5.

  • Page 73: Conducting Satellite-Specific Tasks

    Conducting Satellite-Specific Tasks 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.

  • Page 74: Using The Tools Menu

    Chapter 8. Maintenance 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. Clicking this opens the RHN Internal Tools page. Figure 8.1.

  • Page 75: Deleting Users

    Deleting Users Other service commands can also be used, including start, stop, and status. 8.7.2. Deleting Users Because of the isolated environment in which RHN Satellites operate, Satellite customers have been granted the ability to delete users. To access this functionality, click Users in the top navigation bar of the RHN website.

  • Page 76: 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 repository with Red Hat Network can be a time-intensive task.

  • Page 77: Implementing Pam Authentication

    Implementing PAM Authentication 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 Table 6.2, “Satellite satellite-sync. Options other than --email can also be included. Refer to Import/Sync Options”...
  • Page 78 Chapter 8. Maintenance the typical delay between scheduling an action and the client system checking in with RHN to retrieve Important SSL must be employed between the Satellite and its clients systems for this feature to work. If the SSL certificates are not available, the daemon on the client system fails to connect.

  • Page 79: Sample Rhn Satellite 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 81: Revision History

    Appendix B. Revision History Revision 1.0 Fri Feb 27 2009...

  • Page 83: Index

    Index enabling push to clients, 73 entitlement certificate, 15, 23 uploading, 38 Symbols /etc/nsswitch.conf, 58 firewall rules /etc/rhn/rhn.conf, 58 requirements, 14 advantages, 1 general problems, 57 Apache, 63 GPG keys, 23 Apache HTTP, 3 automating Satellite synchronization, 72 host not found error backing up the RHN Satellite, 64 could not determine FQDN, 58 block sizes, 13...
  • Page 84 Index options, 44 RHN Task Engine, 70 operating system rhn-satellite, 63 supported, 9 rhn-satellite-activate, 38 Oracle 10g, 3 activating, 39 Organization Administrator options, 38 definition, 2 rhn-satellite-exporter, 41 osa-dispatcher, 74 export, 43 osad, 74 options, 42 rhn.conf sample file, 75 PAM authentication rhns-satellite-tools, 38, 47 implementation, 73...

Table of Contents