160 Chapter 7. Monitoringrequired between the systems and RHN. This may be especially desirable if you alreadyhave sshd running. To configure the daemon for monitoring use:1. Ensure the SSH package is installed on the systems to be monitored:rpm -qi ssh2. Identify the user to be associated with the daemon. This can be any useravailable on the system, as long as the required SSH key can be put in the user’s~/.ssh/authorized_keys file.3.Identify the port used by the daemon, as identified in its /etc/ssh/sshd_configconfiguration file. The default is port 22.4. Install the SSH public key on all client systems to be monitored, as described inSection 7.2.4 Installing the SSH key.5. Start the sshd on all client systems using the command:service sshd start6. When adding probes requiring the daemon, insert the values derived from steps 2and 3 in the RHNMD User and RHNMD Port fields.7.2.4. Installing the SSH keyWhether you use rhnmd or sshd, you must install the Red Hat Network Monitoring Dae-mon public SSH key on the systems to be monitored to complete the secure connection.To install it:1. Navigate to the Monitoring ⇒ Scout Config Push page of the RHN website andclick the name of the RHN Server that will monitor the client system. The SSHid_dsa.pub key is visible on the resulting page.2. Copy the character string (beginning with ssh-dss and ending with the hostnameof the RHN Server).3. On the command line of the system to be monitored, switch to the user aligned withthe daemon. This is accomplished for rhnmd with the command:su - nocpulse4. Paste the key character string into the ~/.ssh/authorized_keys file for the dae-mon’s user. For rhnmd, this is /opt/nocpulse/.ssh/authorized_keys.If config management is enabled on the systems to be monitored, youmay deploy this file across systems using a config channel. Refer toSection 6.6.6.1 Preparing Systems for Config Management for details.
