topic Re: copy ignite server in Operating System - HP-UX

copy ignite server

Toon Joye — Tue, 06 Feb 2007 08:58:45 GMT

hello,

I 've made made a copy of our Central Ingite Server. So now I've got a CIS3 and a CIS4.
The ipadres of CIS3 is xx.xxx.xxx.103, the ip of CIS4 ends with 104.
When installing from CIS4, I encounter a problem with NFS: when starting to install CIS4 sets up an NFS-connection with xx.xxx.xxx.103(=CIS3). So he gives an RPC Bind error .I've checked the /etc/export-file and everything is there.
So I think that there must be another file that specifies the ipadres of the igniteserver wich I haven't modified yet.

Does anaybody know which file I'm looking for?

Tnx
Toon
When

Re: copy ignite server

Steven E. Protter — Tue, 06 Feb 2007 09:33:03 GMT

Shalom,

/etc/exports probably has inconsisten entries in it.

SEP

Re: copy ignite server

Toon Joye — Tue, 06 Feb 2007 09:40:01 GMT

CIS3 and CIS4 are exactly the same(made by ignite). The only thing that differs is the hostname and the ipadres. So the /etc/exports-files on both servers are also the same.

That's why I think there must be a specific file that determines the ipadres of the ignite-server to setup nfs.
Because when installing from CIS4, ignite tries to setup NFS with the ipadres from CIS3.

Re: copy ignite server

Scot Bean — Tue, 06 Feb 2007 13:41:42 GMT

There are multiple config files on an Ignite server that can set this. By cloning the server, you have also cloned those files:

First place to look:
'instl_adm -d'
shows you the very first config file Ignite runs. I'd bet
'server=' is set to the previous IP

You can change this setting with the
'instl_adm -f '
command.

You may also have other custom config files called out in /var/opt/ignite/INDEX that have settings. For example I have
nfs_source = "xx.x.xxx.xxx...
IP setting in my custom config files.

Re: copy ignite server

John P. Kole — Tue, 06 Feb 2007 20:32:30 GMT

As Scot said, typically an Ignite-UX server has these
"server=" lines located in config files. My first
guess would be the *INSTALLFS files. Do this on your
server:

$ cd /opt/ignite/boot
$ ls -aon Rel_B.11.[123][13]/*INSTALLFS
-r--r--r-- 1 2 15728640 Feb 6 16:07 Rel_B.11.11/INSTALLFS
-r--r--r-- 1 2 44957696 Feb 6 16:07 Rel_B.11.23/IINSTALLFS
-r--r--r-- 1 2 33550336 Feb 6 16:07 Rel_B.11.23/WINSTALLFS
-r--r--r-- 1 2 61341696 Feb 6 16:07 Rel_B.11.31/IINSTALLFS
-r--r--r-- 1 2 32768000 Feb 6 16:07 Rel_B.11.31/WINSTALLFS

The config text (which is basically the first 8k of each of
those files above) is typically identical in all files. You
can examine this config text via:

$ instl_adm -d > /tmp/mycfgFS
$ cat -n /tmp/mycfgFS
1 # instl_adm defaults:
2 # NOTE: Manual additions between the lines containing "instl_adm defaults"
3 # and "end instl_adm defaults" will not be preserved.
4 server="99.9.98.48"
5 netmask[]="255.255.255.0"
6 route_gateway[0]="99.9.99.1"
7 route_destination[0]="default"
8 # end instl_adm defaults.

You can edit this file, changing line 4 to reflect the proper
server address. Once done, you would put this config text back
into all of your *INSTALLFS files on the server via:

$ instl_adm -f /tmp/mycfgFS

Validate your work via:

$ instl_adm -d | cat -n