SSH Configuration

Home | Index/DBAmon Doc. | DBAmon Version/Change History | DBAmon Event/Error Doc. | What DBAmon Monitors | DBAmon Download | Free Oracle Tool: orastat | Request Support

SSH Configuration

This process assumes that the ssh1 daemon has been installed on the server, and the ssh1 client is being used on the client machine.

On The DB Client:

  1. Make sure that there is a .ssh directory in the /home/user directory for the user the DBAmon will be running under (the value that you will specify for the User: parm of the .dbc file).
     ls -al .ssh  
  2. If there is no .ssh directory, create it.
     mkdir .ssh 
  3. Change the rights of directory to 755.
     chmod 755 .ssh
  4. Change to the directory.
     cd .ssh
  5. Create the authorized_keys file.
     touch authorized_keys 
  6. Change the rights of the file to 644.
     chmod 644 authorized_keys 

On The DBAmon Master:

  1. Install SSH1.
  2. Generate the identity.pub file.
  3. When prompted, enter a passphrase of blank (just hit {Enter}).
  4. TELNET to the DB Client.
  5. Change to the .ssh directory.
     cd .ssh  
  6. FTP the identity.pub file from your machine to the .ssh directory in your home directory in the server.
         ftp [DBAmon Master] 
         cd /home/[DBAmon User]/.ssh 
         get identity.pub 
  7. Copy the identity.pub file to the authorized_keys file. Use the cat command to append the file, so that if you are trying to access the server from more than one client, you will have a keypair in the authorized_keys file from every client you are using to access the server.
     cat identity.pub >> authorized_keys 
  8. Erase the identity.pub file.
     rm identity.pub 
  9. Exit the telnet session and try logging in using ssh1.
     ssh1 -l [username on server] [server] 
  10. You should not have to enter a passcode, and you are now logged on.

This Document: http://dbamon.com/config/ssh.shtml