NIM mksysb installation 1

[jprabaker]

Probably a dumb question but I'm going to ask anyway!

why do I need to assign a spot to a client in order to do a NIM mksysb installation? I would have thought everything that was required to build the server was on the mksysb image.

Thanks in advance,
John

 

[AIX5L]

Hi

You need the lppsource and the spot to install the mksysb.
spot - Is required, ODM, ibraries...to create a bootable System ( bosboot ). The mksysb doesnt contain any rawlv. hd5 = rawlv !

lppsource - Is needed when a Device Driver is not in the mksysb Image

If you restore your mksysb on the same machine dont forget the recoverdevices=yes, beacuse you loos all device Configs, and aio0 Settings ! ( Everything in the dev ODM )

AIX5L
AIX Certified Advanced Technical Expert
Certified Specialist/p690 Technical Support
Linux Professional Institue LPIC1

 

[jprabaker]

Interestingly,

Both my (mksysb) client and my NIM resources claim to be at ML05. However, many of the filesets on the client are downlevel to whats in the nim resources, eg:

mksysb client:

lslpp -l bos.net.nfs.client
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
bos.net.nfs.client 5.1.0.55 APPLIED Network File System Client

Path: /etc/objrepos
bos.net.nfs.client 5.1.0.55 APPLIED Network File System Client


lpp_source:

rs026a# nim -o showres 5100_05_lpp |grep bos.net.nfs.client
bos.net.nfs.client 5.1.0.35 I b usr,root
bos.net.nfs.client 5.1.0.57 S b usr,root

When I did the mksysb restore (with the lpp_source) allocated, the new system came up with the more upto date filesets it had got from the lpp_source & not from the mksysb image.

When I restore the mksysb image without the lpp_source allocated the system comes up as a clone of the other with all the same fileset levels.

My questions are, how can the 2 systems both think they are at ML05 when they have differing fileset levels, and why does the mksysb install update the filesets installed with those from the lpp_source when doing a mksysb installation. Is this normal behavoir?

Of course I should have built my lpp_source & spot using the same update source as the client in question, but I didn't forsee this issue...


Thanks,
John