Veritas-bu

[Veritas-bu] Remote netbackup client install over ssh help

2004-12-06 05:45:30
Subject: [Veritas-bu] Remote netbackup client install over ssh help
From: Philip.Weber AT egg DOT com (Weber, Philip)
Date: Mon, 6 Dec 2004 10:45:30 -0000
I have similar problems with restrictions on where we can use ftp & rsh, and
firewalls creeping in between clients and servers.
I have an admin server which can ssh to master/media and clients as root, so
initially wrote a script to :

o  use sudo to ssh to master to check for sftp_to_client script.
o  if not found, hack ftp_to_client script into sftp_to_client (on master).
o  ssh to master to run sftp_to_client on master to push out install to
client.
o  ssh to client to run the client_config script.

This all worked nicely, but then they restricted ssh access to the master
couldn't ssh/scp/sftp to the client, traffic was only allowed from the admin
server :-(.

So the script now :
o  checks client's OS version
o  checks master for inst_client script for that OS version
o  if not found, hack ftp_to_client script into inst_client script which
copies locally instead of ftp
o  ssh to master to run inst_client script to build client install on the
master
o  scp the install dir back to the admin server
o  scp the install dir from the admin server to the client
o  ssh to the client to run the client config script

It's now a bit slow (!) but at least it runs unattended.

I can post either script if it would be helpful.

cheers, Phil


-----Original Message-----
From: Dave Markham [mailto:dave.markham AT fjserv DOT net] 
Sent: 03 December 2004 15:52
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Remote netbackup client install over ssh help


Has anyone here installed client software using ssh instead of rsh for 
remote installs?

Im running Solaris 9 and using netbackup 5.

I have keys set up from root so no password auth is needed. This works fine

I first tried linking rsh and rcp to ssh but that didnt seem to work 
ending with server/hostname not found. The same command with ssh worked 
fine.

So i edited /usr/openv/netbackup/client/Solaris/Solaris9/install_client 
and replaced the RSH and RCP sections with RSH=/usr/bin/ssh and 
RCP=/usr/bin/scp

Something started happening as the directories were created on the 
remote client, but things just hung and stuck there.

 From this i decided to run the install_client_files script manually 
from command line like this :-

cd /usr/openv/netbackup/bin
./install_client_files rsh <client name>

As id edited the install_client script to have a 'set -x' line at the 
top i can see all the output scrolling and the scp calls working and 
everything. Then things just stop...and wait.

Going on to the client i see loads and loads of ssh processes and when i 
tried killing 1 off the job moved a step along. I tried killing another 
ssh process on the client and then the server script had a connection 
lost, and still hung. Obviously killing processes isnt the way forward.

Has anyone had this type of things before? Im assuming there are too 
many ssh processes and so why are they not exiting when the scp or ssh 
command from install_clients as finished?

Help please. I have lots of clients to install and rsh is not allowed 
through the firewall correctly so, so i need to get this remote setup 
working over ssh.

Thanks
Dave
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-----------------------------------------
This private and confidential e-mail has been sent to you by Egg.  The Egg
group of companies includes Egg Banking plc registered no. 2999842), Egg
Financial Products Ltd (registered no. 3319027) and Egg Investments Ltd
(registered no. 3403963) which is authorised and regulated by the Financial
Services Authority. Egg Investments Ltd. is entered in the FSA register
under number 190518.     Registered in England and Wales. Registered
offices: 1 Waterhouse Square, 138-142 Holborn, London EC1N 2NA.    If you
are not the intended recipient of this e-mail and have received it in
error, please notify the sender by replying with 'received in error' as the
subject and then delete it from your mailbox.