Juniper NETWORK AND SECURITY MANAGER 2010.4 - REV1, Руководство по установке

Страница: 107 / 244

Establishing an SSH Trust Relationship
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:
1.
Run the following commands on the primary server:
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 .ssh under
/home/nsm which contains two text files (public and private key).
2.
Run the following commands on the secondary server:
cd /home/nsm
su nsm
ssh-keygen -t rsa
chmod 0700 .ssh
NOTE: If prompted to enter a passphrase, leave the value blank.
3.
From the primary server, you then need to copy the public key called .ssh/id_rsa.pub
to the secondary server manually and place it in .ssh/authorized_keys . For example,
you would run the following command:
scp .ssh/id_rsa.pub root@<IP addr NSM2>:/root/.ssh/authorized_keys
4.
From the secondary server, you then need to copy
.ssh/id_rsa.pub
to the
.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
authorized_keys
file will break those
trust relationships. Instead, copy the contents of the
id_rsa.pub
file onto
a new line at the end of the authorized_keys file on the remote machine.
5.
You should test connectivity via SSH from the primary server to the secondary server
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>
85 Copyright © 2010, Juniper Networks, Inc.
Chapter 5: Installing NSM with High Availability