Establishing An Ssh Trust Relationship - Juniper NETWORK AND SECURITY MANAGER 2010.4 - INSTALLATION GUIDE REV1 Installation Manual

Establishing an SSH Trust Relationship

Copyright © 2010, Juniper Networks, Inc.
You also need to ensure that you have established an SSH trust relationship between
the primary and secondary servers.
The instructions for Linux are as follows:
Run the following commands on the primary server:
1.
cd /home/nsm
su nsm
ssh-keygen -t rsa
chmod 0700 .ssh
NOTE: If prompted to enter a pass phrase, leave the value blank.
The result of the process is the creation of a hidden directory called
/home/nsm which contains two text files (public and private key).
Run the following commands on the secondary server:
2.
cd /home/nsm
su nsm
ssh-keygen -t rsa
chmod 0700 .ssh
NOTE: If prompted to enter a passphrase, leave the value blank.
From the primary server, you then need to copy the public key called
3.
to the secondary server manually and place it in
you would run the following command:
scp .ssh/id_rsa.pub root@<IP addr NSM2>:/root/.ssh/authorized_keys
From the secondary server, you then need to copy
4.
.ssh/authorized_keys of the primary machine. For example:
scp .ssh/id_rsa.pub root@<IP addr NSM1>:/root/.ssh/authorized_keys
NOTE: If the remote machine already has established trust relationships
with other computers, overwriting the
trust relationships. Instead, copy the contents of the
a new line at the end of the
You should test connectivity via SSH from the primary server to the secondary server
5.
and vice versa. For example, to test SSH connectivity from NSM Server1 to NSM
Server2, type the following command:
ssh root@<IP ADDRESS of Secondary Server>
Chapter 5: Installing NSM with High Availability
.ssh/authorized_keys
.ssh/id_rsa.pub
authorized_keys
id_rsa.pub
authorized_keys file on the remote machine.
under
.ssh
.ssh/id_rsa.pub
. For example,
to the
file will break those
file onto
85