Ignite server moved to new net/ip works fine until xfer tries to nfs mount from old IP

[Christian Tremblay]

Hello all,

I had to take an Ignite server off the network and modify it to use a xconnect cable with a 192.168.xxx.xxx address.

Everything works, client boots from server, Itool loads, images and recovery are selectable
mini kernel gets xfered, root disk created etc.
Until it gets to the point where it tries to nfs mount and xfer the image.

Retrying: "/sbin/fs/nfs/mount -oro 10.1.xxx.xxx:/var/opt/ignite/archives/Rel_B.11.23/Gold

I have replaced the old 10.14.xxx.xxx IP in all config files I could find with the new 192 IP and reconfigured instl_adm

instl_adm -d
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="192.168.100.2"
netmask[]="255.255.255.0"
route_gateway[0]="default"
route_destination[0]="default"
sd_server="192.168.100.2"
# end instl_adm defaults.

The problem is obviously that the NFS mount stills try to mount from the old IP.

Where does the NFS mount gets that IP from and how can I change it to use the new one ?

Thx

Chris

[Ivan Krastev]

Try to stop and restart rpc.mountd

Another option is to clear DCE cache.


regards,
ivan

[Christian Tremblay]

What I am trying to do is ultimately to clone a system from a recovery image that has been created on a different Ignite server.
Source system can only see ignite server A
Target system can only see ignite server B

1-create recovery archive from source system to ignite server A
2- move /var/opt/ignite/clients/0x0018714E55FB
directory from ignite server A to B
move /var/opt/ignite/recovery/archives/servername (archive file)from server A to server B

replace original MAC directory name with target system MAC as directory name

Boot target system from ignite server B, it sees it's own MAC as directory name of the archive, offers archive as recovery in Itool
menu, proceeds with loading mini kernel, configures boot disks etc, up to the point where it tries to NFS mount the recovery image for transfering ,at which point it will fail because it tries to nfs mount the archive using ignite server A IP address instead of ignite server B IP address.

I am trying to find where I can substitute ignite server B adress instead so it will nfs mount from it.

[Sameer_Nirmal]

I assume here you are using the network recovery archive to clone the systems.

Did you check the client's "archive_cfg" file for "nfs_source" for correct IP address?

The client archive config file is as defined in CINDEX.

[Mike Shilladay · Accepted solution]

Hi Chris,

I had a similar problem with Ignite/UX, old ignite images taken with the server at 172.19.144.21 then changed the server to 172.19.144.1. The Ignite would start the process but once the mini kernel was loaded would fail on the nfs retrying.

I got round this by adding the old IP address back into the config, but only after the ignite has loaded the mini kernel.

Example:

ifconfig lan0:1 172.19.144.21 netmask 255.255.240.0 up

Ignite then works fine. Don't forget to down the IP after you have loaded the server.

You may also want to take a new ignite with your new IP immediately, so as you don't have to mess around with IP address when it really matters!

Hope that helps,

Mike.

[Mike Shilladay]

Sorry Chris,

Forgot to give you the example of down-ing the IP after you had finished. So here it is now. (But i am sure you don't need me to tel you) ;o)

ifconfig lan0:1 0.0.0.0 down

Mike.

[Christian Tremblay]

Thanks guys for your help, but management decided on another course of action so I couldn't try your solutions.

( I miss the old days where you only had to do a make_tape_recovery of the source server on a DDS tape, walk to the target and boot from it... done ;-) )