no default route on NIM client after installationm

[bjmurdau]

I have a working NIM environment, but I have had one small issue from the beginning. After the installation completes on the client, a static default route gets added, but there is no dynamic default route. In order for the client to see its gateway, I must either run a route add command or I must reboot the machine. I tried using a post-install script to do this, but this does not even work. Any help would be greatly appreciated.

Thanks,
Bryan

 

[Yegolev]

We have been through this and have a script that works most of the time. Occasionally, maybe 9 out of 10 times, the route table gets blasted clean. That, of course, requires physical presence at the console. Otherwise we make and use a post-install script. I didn't get the NIM project but from what I can read in the nim script (which is way, way too large to post) it looks like a script is defined thusly:

nim -o define -t script -a server='master' -a location="$SCRIPT" post_install_script_$HNAME

Pretty much we build a client script and stick a line in the client's inittab to run it on reboot, then we remove the line later. The client script changes the hostname, sets up routes, sets the adapters to 100_Full_Duplex, and so on.