[mattanglin]

I have a NIM master with a few NIM clients. Pretty much the only thing I do with this setup is create mksysb images for the clients and store them on the master. To this end, I wrote a little script, and it was working fine a few months ago, but today I am getting errors I can't seem to get past.

I have a nim master

[zapp:root:/var/log] lsnim -l master
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.64.ent
if_defined = chrp.mp.ent
comments = machine which controls the NIM environment
platform = chrp
netboot_kernel = mp
if1 = master_net zapp.xxx.xxx.com 000nnnnnnnnA
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = not running
Mstate = not running
master_port = 1058
registration_port = 1059
Cstate_result = reset
reserved = yes

And, I have a nim client:

[zapp:root:/var/log] lsnim -l flicka
flicka:
class = machines
type = standalone
connect = nimsh
platform = chrp
netboot_kernel = 64
if1 = master_net flicka 0
net_settings1 = auto auto
cable_type1 = bnc
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
cpuid = 000nnnnnnnnn

So, I try to do a mksysb operation:

/usr/sbin/nim -o define -t mksysb -a server=master -a source=flicka -a location=/export/eznim/mksysb/flicka_sysb -a mk_image=yes flicka_sysb
0042-001 nim: processing error encountered on "master":
0042-302 m_mkbosi: the state of "master" prevents this operation
from succeeding. Use the "reset" operation to correct
its state then retry the intended operation.

Fine, so I do the reset

[zapp:root:/var/log] nim -F -o reset master

[zapp:root:/var/log]

But I still get the same error. I can't seem to figure out why it is failing. Anybody got any ideas? Should the MState on the master be running? If so, how do I get it into this state? What log file would have more info on this error? I added -a verbose=yes to the mksysb operation, but no additional messages were issued. The two ports mentioned seem to be active:

[zapp:root:/var/log] netstat -an | grep 105
tcp4 0 0 *.1058 *.* LISTEN
tcp4 0 0 *.1059 *.* LISTEN

And the nim group is active from src

[zapp:root:/var/log] lssrc -g nim
Subsystem Group PID Status
nimesis nim 196718 active

Thanks for your help.

[bagtache]

Hi,

I see two errors on your master:
-Its state indicates that it is not running
-The network interfaces show chrp.64.ent & chrp.mp.ent which completly wrong.

Since the nimesis daemon runs and its two ports (registration & communication) are open and that the reset doesn't fix the problem, i think that you can try to restore the NIM db (if you have a backup). It is probable that a corruption occured: did you change anything it the master configuration ? like the hostname, its interfaces, etc... because i have already seen such problems after an incorrect update of an attribut of the master.

Hope this can help u.
Please let me know if there any progress.
Good luck.

[jmcphee]

Machine State can be reset with a "check" if everything is configured right.
$ nim -o check master

Whether that's your problem is a good question

[mattanglin]

Thanks for all your suggestions. I suspect the change of the IP address messed everything up. I unconfigured everything and started over, and the mksysb creations are working again.

Thanks for all of your help.

Matt.