AIX

Again, you shouldn't (and need not) export anything by hand when you use NIM. Your exports file shows that a lot of directories are exported already. Some of them are probably exported by allocating NIM resources to machines, but some may be exported by hand.

If you use the NIM server alone or get some downtime for it: deallocate all resources at the NIM-server, then remove everything "/nim/..." (which i presume to be the root for your NIM resources) from the exports file. Always deallocate with the "force" option (otherwise that fails most of the times).

You might want to use something like:

Code:

lsnim -t standalone | while read system junk ; do
     nim -o reset -a force=yes $system
     nim -Fo deallocate -a subclass=all $system
done

Only then allocate resources again. These (and ONLY these) should appear in the exports file.

Next thing is to check the client you test with if the NIM connection is working. Quite often this is the problem. If you use "nimsh" check if the nimsh service is running on the client, otherwise you need a running rsh:

Code:

root@client # lssrc -g nimclient
 nimsh            nimclient        5505154      active

Now test this by placing a simple script (just put a "date" command into it, is enough) in "/nimres/scripts" (or somewhere, this is how i call the directory), add a nim resource of the type "script" and let it point to the script. Then test the client by

Code:

nim -o cust -a script=<scriptname> <client>

I hope this helps.

bakunin

Hi Bakunin!

Thanks for the reply! But my problem happens before I can allocate ressources. Also, in the LPAR setup, before installing the OS with BOOTP, I set an interface to communicate with the NIM and it pings. And finally, I was able to install the OS with an already made mksysb.

My problem is I'm unable to create an lpp_source, even from the base AIX DVD...

(See prior post for info... my format gets all screwed up when I copy paste it again...)

This is why i have shown you how to reset NIM resources. They are probably "partly" allocated already. At least the exports file you have shown suggests this.

Actually this is not what you need. First you need to define a "NIM network" where the (prospective) client can reside in (if this is not already there). When creating the network NIM tests if the router there can act as a "bootp relay agent" (see RFC 1533 and RFC 1534). The bootp protocol relies on an initial broadcast issued without any source IP address at all (from the client to be configured) to be transmitted by the router (or whatever functions as a relay agent).


Sigh...

Copy all the lpp-files from "/cdrom-mount/installp/ppc" to a directory.

Next, rename the packages to their true name:

Code:

bffcreate -c -d <source_device/path>

They will now have one of two names:

Code:

some.name.V.R.M.F.I
some.name.V.R.M.F.U

V, R, M and F are the version, release, ... numbers, like "1.7.15.30", "I" is for "installable" (a base level package, installable on its own), "U" is for "update" (installable only if the respective "I"-package is already installed).

Then create a table of contents (the file ".toc"):

Code:

 cd /path/to/prospective/lpp
inutoc .

Finally create the LPP-source with the command i showed you in Post #6 already. Proceed from there.

This is because your CODE snippets are full of all kind of crazy markup with "FONT", "SIZE", "COLOR" and whatnot-tags. I tried to remove them, but had to give up for the sheer amount. You might want to edit your posts yourself and just remove them. Leave only the CODE-tags in place and remove everything else.

I hope this helps.

bakunin

Hi Bakunin!

Thanks for the replies!!! Unfortunately, I haven't had time to try what's written above (work has been getting crazy) I'll have to try next year probably!

I'll keep you posted!

Thank you very much for your time!