Pushing a file from one to many AIX LPARS 1

[macrun95]

I was wondering if anyone could help me with a scripting problem. I'm not very good at scripting but know the basics of Korn. I wrote a Korn script that I need to push to about 40 LPARS. I obviously don't want to ftp it to each LPAR by hand as that is very time consuming and I am sure there is a way to automate it.

What would be the best way to do it? Like I said, I don't know any scripting languages really but if someone would be so kind as to give me a short script or point me in the right direction it would be greatly appreciated.

Eric

 

[khalidaaa]

The best way is to use dsh command after configuring ssh on your LPARs.

If you don't want to configure ssh (which i think you should to make your life easier administring 40 LPARS!)

You can script this using rcp command.

(you will need to configure .rhosts for all LPARs with this as well!)

Regards,
Khalid

 

[khalidaaa]

Just to clear something on my post above (you need to configure ssh to avoid using passwords when logging between LPARs) That's what i mean by configuring ssh!

Here is a link that will help you configure ssh:

http://www.tek-tips.com/viewthread.cfm?qid=1207338&page=1

Regars,
Khalid

 

[khalidaaa]

And this is another link for using the dsh:

http://www.tek-tips.com/viewthread.cfm?qid=1353921

I hope this is helpful enough.

Regards,
Khalid

 

[MoreFeo]

If you don't want (or if you can't) configure ssh, you can use the .netrc file to ftp without having to put user and passwd. For example, you can script an ftp from serverA to serverB and serverC, by addind a .netrc in serverA:

This is an example of a .netrc file:

machine serverB login username password passwd
machine serverC login username password passwd

macdef sendascii
    ascii
    put $1 $2
    quit

macdef sendbin
    bin
    put $1 $2
    quit

macdef cd_sendascii
    ascii
    cd $3
    put $1 $2
    quit

macdef cd_sendbin
    bin
    cd $3
    put $1 $2
    quit

This file has to be in serverA in the HOME of the user that's going to make the ftp, and it should be chmod 600.

So in your script you can call use the macros defined in this file like this:

cd /path/to/file
echo "\$ cd_sendascii filename filename /path/to/file/innewserver | ftp serverB"
echo "\$ cd_sendascii filename filename /path/to/file/innewserver | ftp serverC"

You can put this in a while or for loop to ftp the file to the 40 LPARs.

 

[MoreFeo]

Of course, having usernames and passwords in a plain file is a security issue, so it's not always a good idea, but if it's just for this time then you can delete it afterwards.

Also, if you only need one of the macros you don't need to add the four macdefs in your file.

 

[mrn]

Try rsync

He's a How-to

Using Secure Rsync to Synchronize Files Between Servers


This tutorial will help you set up synchronization of files and/or directories between AIX servers. OpenSSH will be used to provide an additional element of security.

OpenSSH is a free software tool that supports SSH1 and SSH2 protocols. It's reliable and secure and is widely accepted in the IT industry to replace the r-commands, telnet, and ftp services, providing secure encrypted sessions between two hosts over the network.

OpenSSH source code is compiled on AIX 5L and shipped on the AIX 5L Expansion Pack and Web Download Pack. You can also get the installation images from OpenSSH on AIX. When you install the AIX OpenSSH image from the Bonus Pack CD or from the website, you can get support from IBM Program Services.

OpenSSH is dynamically linked with OpenSSL for use of the encryption library libcrypto.a. You can get the OpenSSL library from the AIX Toolbox for Linux Applications CD or from this website. OpenSSL is delivered in RPM format (instead of installp format). To install OpenSSL, use the command:

# rpm -i

Lets walk through the process of downloading and installing OpenSSL, OpenSSH and rsync.

1. Download the package manager: ftp://ftp.software.ibm.com/aix/freeS...LP/ppc/rpm.rte
2. Install the package manager

# installp -qacXgd rpm.rte rpm.rte

3. Download the OpenSSL library: [URL unfurl="true"]http://www6.software.ibm.com/dl/aixtbx/aixtbx-p[/URL]
a. OpenSSL is cryptographic content so you will need to sign in with your IBM ID and password. Create one if you don’t have one. 
b. The next screen is a license agreement. Agree and confirm.
c. Search the page for “openssl-0.9.7g-1.aix5.1.ppc.rpm” and click on the download button next to it. 

4. Install the RPM: 

# rpm –i openssl-0.9.7g-1.aix5.1.ppc.rpm

5. Download OpenSSH: [URL unfurl="true"]https://sourceforge.net/project/show...roup_id=127997[/URL]
6. Installation: The resulting file is compressed tar file. Uncompress and untar it and follow the directions in the Customer_README file exactly as given.
7. Download the latest version of rsync: ftp://ftp.software.ibm.com/aix/freeS...RPMS/ppc/rsync
8.Install rsync:

# rpm –i rsync-2.6.2-1.aix5.1.ppc.rpm

You must complete these steps on all servers/LPARs that will be using rsync, either as a file server or a sync client. You must also set up the necessary SSH keys between servers.

For the remainder of this exercise, we are going to limit ourselves to two servers. FileServe will be the server with the master files and FileClient will be the server/LPAR obtaining the master files for local use.

A common usage in this scenario is user information, so we will address that particular example, but rsync can be used for any types of files or directory trees. Indeed, it can be used to keep HTML source in sync, as just one more example use.

This is an example of a script that does a “pull” from FileServe. FileClient transfers the latest passwd, group and security files overwriting its own files. Additionally, FileClient copies any new user directories in /home but does not update, modify or delete any existing directories. 

#!/usr/bin/ksh
# Get new /etc/passwd & /etc/group files
# Overwrite existing files
rsync –goptvz -e ssh FileServe:/etc/passwd /etc/passwd
rsync –goptvz -e ssh FileServe:/etc/group /etc/group
# Get new files from /etc/security
# Overwrite existing files
for FILE in group limits passwd .ids environ .profile
do
rsync –goptvz -e ssh FileServer:/etc/security/$FILE /etc/security/$FILE
done
# Grab new directories in /home 
# Do not change anything that already exists
rsync -gloprtuvz -e ssh --ignore-existing FileServer:/home /home

This solution is fine for two or three servers, but what about more than that? Besides which, if the centralized user management is being done on FileServe, doesn’t it make more sense to pull rather than push?

This script does a push from FileServe to multiple clients:

#!/usr/bin/ksh
for CLIENTS in `cat /etc/useradm_clients.rsync`
do 
echo Updating ${CLIENTS}…
# Get new /etc/passwd & /etc/group files
# Overwrite existing files
rsync –goptvz -e ssh /etc/passwd ${CLIENTS}/etc/passwd
rsync –goptvz -e ssh /etc/group ${CLIENTS}/etc/group
# Get new files from /etc/security
# Overwrite existing files
for FILE in group limits passwd .ids environ .profile
do
rsync –goptvz -e ssh /etc/security/$FILE ${CLIENTS}/etc/security/$FILE
done
# Grab new directories in /home 
# Do not change anything that already exists
rsync -gloprtuvz -e ssh --ignore-existing /home ${CLIENTS}/home
echo ${CLIENTS} Complete.
done

Personally, I would not automate this unless you put the proper safeguards in place to make sure you’re notified immediately of a failure.

As always, the code I provide is meant to show concepts. Notice none of these commands check error codes, or emails/pages admins. It meant to run interactively so that you see the results.

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."