Red Hat NETWORK - USER 3.0 Guía de instalación descargar pdf (Pagina 73)

Changing the Satellite Hostname

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. After installation, copy the following files from the primary Satellite to the secondary Satellite:

• /etc/rhn/rhn.conf

• /etc/tnsnames.ora

• /var/www/rhns/server/secret/rhnSecret.py

4. Copy and install the server-side SSL certificate RPMs from the primary Satellite to the secondary.

Refer to the Sharing Certificates section of the RHN Client Configuration Guide for precise

instructions. Remember, the Common Name value must represent the combined Satellite solution,

not a single machine's hostname.

If you generated a new SSL certificate during Satellite installation that included a new Common

Name value, copy the SSL certificate RPMs from the secondary to the primary Satellite and

redistribute the client-side certificate. If you also created another bootstrap script, you may use this

to install the certificate on client systems.

5. If you did not create a new bootstrap script, copy the contents of /var/www/html/pub/

bootstrap/ from the primary Satellite to the secondary. If you did generate a new one, copy that

directory's contents to the primary Satellite.

6. Turn off the RHN Task Engine on the secondary Satellite with the following command:

/sbin/service taskomatic stop

You may use custom scripting or other means to establish automatic start-up/failover of the RHN

Task Engine on the secondary Satellite. Regardless, it will need to be started upon failover.

7. Share channel package data (by default located in /var/satellite) between the Satellites over

some type of networked storage device. This eliminates data replication and ensures a consistent

store of data for each Satellite.

8. Share cache data (by default located in /var/cache/rhn) between the Satellites over some type

of networked storage device. This eliminates data replication and ensures a consistent store of

cached data for each Satellite.

9. Make the various Satellites available on your network via Common Name and a method suiting

your infrastructure. Options include round-robin DNS, a network load balancer, and a reverse-

proxy setup.

8.7. Changing the Satellite Hostname

If you need to change the hostname or IP address of your Satellite server, the satellite-utils

package contains the satellite-hostname-rename script.

To use the satellite-hostname-rename script, you must first ensure that you know your SSL CA

passphrase by performing the following command:

1 2 ... 68 69 70 71 72 73 74 75 76 77 78 ... 85 86

Sin comentarios

Red Hat NETWORK - USER 3.0 Guía de instalación Pagina 73