Data Protector 6.2 Remote Installation Linux Client problem - Unable to use ssh

[nurbi]

Hi,

     we have a problem to deploy Data Protector 6.2 agent on linux servers.

My customer configuration is:

Data Protector CM and Is on Red Hat Linux 6.1 64bit

Red Hat 6.1 and CentOS 5.6 as Data Protector clients.

I tried to install agents via "Add Clients" link on Data Protector GUI, but I have a problen witth ssh proto.

I tried also with a different Data  Protector server, installed on CentOS 5.6 in a different environment (demo area), but the problem is the same.

I generated public key to get DP server enter directly on clients without authenticate. I tried also to create in xinetd.d exec and rsh files like a post that I found in itrc forum, http://h30499.www3.hp.com/t5/ITRC-Data-Protector-Forum/Remote-Installation-Issue-Unix/m-p/4713714/hi... , even if I don't want to use rexec or rsh services. I'm sure ssh is working, both using Protocol 2, and all firewall and selinux are off.

Maybe I wrong something in configuration; any suggest ?

Thank you, bye

             nick

[Zigoze]

Run the following command on the Instalation Server:
ssh-keygen -t DSA
ssh-keygen -t RSA

The previous commands generates four files:

id_dsa
id_dsa.pub
id_rsa
id_rsa.pub


Create file "authorized_keys" by joining the two .pub files:

cat id_rsa.pub >> authorized_keys
cat id_dsa.pub >> authorized_keys

Copy file "authorized_keys" to the clients:

scp -rp authorized_keys client.localdomain:/root/.ssh/

Restart service sshd on the client and installation server:

service sshd restart

From the Installation Server open an ssh session to the client(s) (this is necessary to do only one time, for the certificate to be recorded on the installation server, and so it does not ask again if the connection is secure or not):

ssh client.localdomain

Edit file ".omnirc" on the installation server, adding the variable:

OB2_SSH_ENABLED = 1

Restart (if necessary) Data Protector services.

Try again to deploy the agents... it should use ssh without any problem.

[nurbi · Accepted solution]

Thank you.

      I didn't realized that I needed dsa key also. I created only the rsa key.

Thank you again.

         bye

nick

[William_Dishman]

I had some problems upgrading some Linux clients from 6.11 to 6.20 remotely.

I kept getting a "port 5555 busy" error.

Our CM is a HPUX 11.23 server, but I'm not sure if that had anything to do with it.

Here are the steps that I took.

1. Import Linux client using IP .

2. Delete client  along with software (6.11) using IP.

3. Add client using IP. This will install the 6.20 client software.

4. Import client using Fully Qualified Name.

5. Delete the IP from client list, but DO NOT remove software.

[Zigoze]

most recent linux filesystems have a service that occupies port 5555.

either you disable it on the /etc/services file (search for 5555 and you'll find two lines with it), or you change data protector inet port for your backup environment

[Damien_19]

This is what I have in a kickstart script, no need for ssh access from DP Servers:

First extract the OB2-CORE-A.06.11-1.x86_64.rpm:

cd /opt/omni/databases/vendor/omnicf/gpl/x86_64/linux-x86-64/A.06.11/

zcat packet.Z > /tmp/OB2-CORE-A.06.11-1.x86_64.rpm

Kickstart:

#--------------------------------------------
# Install HP Data Protector
#--------------------------------------------

<?
if (isset($HP_DP)) {
?>

cat >>/etc/hosts.allow <<EOF
inet: dp-cm.site.com, dp-ma.site.com
EOF

cp /etc/services /etc/services.orig
sed -e "s/personal-agent  5555/#personal-agent  5555/g" /etc/services.orig > /etc/services

rpm -ivh http://site.com/files/hp-datapro/OB2-CORE-A.06.11-1.<?echo $ARCH?>.rpm

<?
}
?>

Disk agents, and other agent are deployed via port 5555, Insert smoke and mirrors.