|
|
|
| Propagating the Kerberos Server |
|
|
|
| Setting Up Propagation |
|
|
|
| |
NOTE |
|
| The <admin/principal> is the same as the one added on the primary | |
|
|
| security server in step 2. | |
|
|
| ||
Step | 5. Start the admin daemon on the secondary security server by using the | |||
|
|
| following command: | |
|
|
| # /opt/krb5/sbin/kadmind | |
Step | 6. Start the propagation daemon on the primary security server, and verify | |||
|
|
| whether the daemons have started or not, by using the following | |
|
|
| command: |
|
|
|
| # /opt/krb5/sbin/kpropd | |
|
|
| Propagation System Started. | |
|
|
| [fqdn] subscriber_ip_addrs: <nnn.nnn.nnn.nnn> | |
|
|
| [fqdn] Established secure connection for | |
|
|
| propagation |
|
|
|
| [fqdn] no cache file or OK file found; will do | |
|
|
| full dump |
|
|
|
| [fqdn] starting full dump | |
|
|
| [fqdn] full_dump successful. | |
|
|
| where: |
|
|
|
| fqdn | Specifies the FQDN of the secondary security server. |
nnn.nnn.nnn.nnn Specifies the IP address of the secondary security server.
If the primary security server propagates to multiple secondary security servers, the message sequence is displayed for each secondary security server.
Step 7. Start the kdcd and the propagation daemon on the secondary security server, and verify whether the daemons have started, by using the following commands:
#/opt/krb5/sbin/kdcd
#/opt/krb5/sbin/kpropd
Chapter 9 | 261 |