Moving to a new network/domain

[Admin.SIF]

Hi,
We are Planning to move a machine HP9000/N-Class/HP-UX 11.0 to another network and domain.
Any suggestion concerning the following points would be appreciated :
1 - Is there others elements that I have to consider besides modifying files netconf, hosts and resolv.conf before stopping the machine and moving it ?
2 - About software installed on this machine, there are files in which we make reference only to the name of the server (example tnsnames.ora for oracle), thus will not be affected by the change.
But there are other software for which we use the name of the machine follow-up by the name of domain : servername.abc.com (Case of messaging server).
If somebody has already done a similar exercise, just to know if it takes a lot of time to change these settings.
Thanks.

[Admin.SIF]

toc toc !
My message did not inspire anybody? Any information please. Thanks.

[James R. Ferguson]

Hi:

Probably the easist, most reliable method is to use '/sbin/set_parms' to change the IPAddress and other network configurations.

# /sbin/set_parms ip_address
# /sbin/set_parms addl_network

When done, you can verify the domain name changes in 'etc/hosts', '/etc/resolv.conf' and '/etc/sendmail.cf'.

Regards!

...JRF...

[S.K. Chan · Accepted solution]

I've been using "set_parms" most of the time but occasionally if I stumble onto some roadblocks along the way I prefer to manually edit the files involved. As far as OS is concern these are the files I would modified ..
/etc/rc.config.d/netconf
/etc/issue
/etc/warning
/etc/hosts
/var/adm/sw/products/ifiles/_ACL
/var/adm/sw/products/ifiles/_OWNER
/var/adm/inetd.sec
/var/adm/sw/security/_ACL
/var/adm/sw/security/_OWNER
/var/adm/sw/security/_PROD_DFLT_ACL
/var/adm/sw/security/_SOC_DFLT_ACL
Those ACL files has a comment string and I just want to update them. As for application that reference the static full domain name, you would just have to handle them seperately.

[Paul Sperry]

I recently moved over 100 system to a new network/domain

I edited the following files

/ect/rc.config.d/netconf
/etc/hosts
/etc/fstab
/var/adm/inted.sec
/etc/resolv.conf
/etc/nsswitch.conf
/etc/mail/sendmail.cf

Fortunately I knew the new network and domain specs and
I made the files in advance calling them .new (ie hosts.new)

The night before the big move
I ran a script that renamed the original files to .old and renamed the .new files to the original, then it did a shutdown -h now. Very easy script to write and push out to every box.

When we got to our new site all we had to do was plug them in and turn them on.

I might note that we changed our naming convention for the boxes as well. which is why I had to edit the /etc/fstab

The sendmail.cf around line 95
the is a spot to put in your domain.

[Steven E. Protter]

setparms will work.

You can handle most of it in /etc/rc.config.d/netconf

You can add the domain name to your hostname.

steve becomes steve.mynet.com

IP addresses can be done here as well, then either restart the box or bring the network down and up.

You will still have to look at resolv.conf and some of the other files mentioned above depending on the extent of the changes.

SEP

[Admin.SIF]

Thanks to all for your answers.
Paul, I would like to know if you had had to modify files others than the one we listed (I mean configuration files of software installed on the servers ) and if that caused problem for your applications.
Thanks in advance.

[Paul Sperry]

Fortunately most on the systems were production workstations and had no apps installed on them. All of our apps reside on the servers. Since the hostnames of the servers also changed, I did have to edit other files that were app related.
I used this script in the app directories to do this quickly.

#!/usr/bin/ksh
find /DIR -type f | while read FNAME
do
sed "s/OLDHOST/NEWHOST/g" < ${FNAME} > ${FNAME}.tmp
mv ${FNAME}.tmp $FNAME
done

[John Bolene]

If your boxes are managed by ITO/OVO, unmanage them before changing IP's and DNS, and repush/manage the agents after changing IP's and DNS.