Unable to create a SPOT

Hi everyone!

Ok so I'm trying for the first time to install AIX on a LPAR with NIM.

The NIM:

root@oaexpnimp01(/home/root) # oslevel -s
6100-08-02-1316

I'm trying to install AIX 6.1 TL1. I successfully created a new lpp source

root@oaexpnimp01(/home/root) # lsnim -l AIX61_TL1_2
AIX61_TL1_2:
   class       = resources
   type        = lpp_source
   arch        = power
   Rstate      = ready for use
   prev_state  = unavailable for use
   location    = /nim/lppsource/AIX61_TL1_2
   simages     = yes
   alloc_count = 0
   server      = master

Now I'm trying to create the SPOT

root@oaexpnimp01(/home/root) # nim -o define -t spot -a server=master -a location=/nim/spot -a source=AIX61_TL1_2  spot-LPP_AIX61_TL1_2

 Creating SPOT in "/nim/spot" on machine "master" from "AIX61_TL1_2" ...

 Restoring files from BOS image.  This may take several minutes ...


 Checking filesets and network boot images for SPOT "spot-LPP_AIX61_TL1_2".
 This may take several minutes ...

warning: 0042-001 m_mkspot: processing error encountered on "master":
   0042-175 c_ch_nfsexp: An unexpected result was returned by the
        "/usr/sbin/exportfs" command:
        exportfs: 1831-186 /nim/lppsource/AIX61_TL1_2 not found in /etc/exports


rc=0
warning: 0042-001 m_instspot: processing error encountered on "master":
   0042-175 c_ch_nfsexp: An unexpected result was returned by the
        "/usr/sbin/exportfs" command:
        exportfs: 1831-186 /nim/lppsource/AIX61_TL1_2 not found in /etc/exports


rc=0
warning: 0042-001 m_instspot: processing error encountered on "master":
   0042-062 m_ckspot: "spot-LPP_AIX61_TL1_2" is missing something which is
        required

It said it failed but when i look it up, it exists with an error:

root@oaexpnimp01(/home/root) # lsnim -l spot-LPP_AIX61_TL1_2
spot-LPP_AIX61_TL1_2:
   class         = resources
   type          = spot
   arch          = power
   Rstate        = information is missing from this object's definition
   prev_state    = verification is being performed
   info          = warning: 0042-157 c_ckspot: unable to access the "/nim/spot/spot-LPP_AIX61_TL1_2/usr/./lpp/bosinst/image.template" file
   location      = /nim/spot/spot-LPP_AIX61_TL1_2/usr
   version       = 6
   release       = 1
   mod           = 1
   oslevel_r     = 6100-01
   alloc_count   = 0
   server        = master
   Rstate_result = success
   mk_netboot    = yes
   missing       = "network boot image"
   missing       = bos.64bit
   missing       = bos.diag
   missing       = bos.mp64
   missing       = bos.net.nfs.client
   missing       = bos.net.tcp.client
   missing       = bos.net.tcp.smit
   missing       = bos.sysmgt.nim.client
   missing       = bos.sysmgt.nim.spot
   missing       = bos.sysmgt.serv_aid
   missing       = bos.sysmgt.smit
   missing       = bos.sysmgt.sysbr
   missing       = bos.terminfo
   missing       = bos.wpars
   missing       = mcr.rte

I know the error message is quite explicit, but when I look at my exported file, everything is there:

root@oaexpnimp01(/home/root) # exportfs
/nim/VIOS        -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottvio1:oaexpviop01:oaexpviop02
/opera/scripts   -sec=sys:krb5p:krb5i:krb5:dh,rw
/nim/HMC         -vers=3,sec=sys:krb5p:krb5i:krb5:dh,access=otthmc1,root=otthmc1
/opera/nimfs     -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottwaspsp:ottland1:ottutil:ottwas1:ottfircoqa:oaexpswpp01:ottdb1:oadejlandt01:oaexpnimp01:oaexpaix06:ottapps:oaexpsaap01:oaexpfffp01:oablcsaap01:oadejsaap01:oadejmqmdt01:oablclanp01:oadejlanp01:oahedwasp01:oablcsaat1:oadejmqmp01:otticdqa:oamcbappp01:oldejwasdt01:oldejdb2dt01:oldejwasp01:oldejdb2p01:oaacpwasp01:olicdlanp01:olsncwasp01:olsncdb2p01
/nim/mksysb      -vers=2:3,sec=sys:krb5p:krb5i:krb5:dh,root=ottwaspsp:ottland1:ottutil:ottwas1:ottfircoqa:oaexpswpp01:ottvio1:oaexpviop01:oaexpviop02:ottdb1:oaexpfffp01:oadejlandt01:oaexpnimp01:oaexpaix06:ottapps:oaexpsaap01:oablcsaap01:oadejsaap01:oadejmqmdt01:oablclanp01:oadejlanp01:oahedwasp01:oablcsaat1:oadejmqmp01:oamcbappp01:oaacpwasp01
/opera/logiciels -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=olicdlanp01:olsncwasp01:olsncdb2p01:olexpwpsr01
/nim/lppsource   -vers=2:3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottland1:oaexpnimp01
root@oaexpnimp01(/home/root) # exportfs -ua
root@oaexpnimp01(/home/root) # exportfs
exportfs: 1831-182 nothing exported
root@oaexpnimp01(/home/root) # exportfs -a
root@oaexpnimp01(/home/root) # exportfs
/nim/VIOS        -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottvio1:oaexpviop01:oaexpviop02
/opera/scripts   -sec=sys:krb5p:krb5i:krb5:dh,rw
/nim/HMC         -vers=3,sec=sys:krb5p:krb5i:krb5:dh,access=otthmc1,root=otthmc1
/opera/nimfs     -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottwaspsp:ottland1:ottutil:ottwas1:ottfircoqa:oaexpswpp01:ottdb1:oadejlandt01:oaexpnimp01:oaexpaix06:ottapps:oaexpsaap01:oaexpfffp01:oablcsaap01:oadejsaap01:oadejmqmdt01:oablclanp01:oadejlanp01:oahedwasp01:oablcsaat1:oadejmqmp01:otticdqa:oamcbappp01:oldejwasdt01:oldejdb2dt01:oldejwasp01:oldejdb2p01:oaacpwasp01:olicdlanp01:olsncwasp01:olsncdb2p01
/nim/mksysb      -vers=2:3,sec=sys:krb5p:krb5i:krb5:dh,root=ottwaspsp:ottland1:ottutil:ottwas1:ottfircoqa:oaexpswpp01:ottvio1:oaexpviop01:oaexpviop02:ottdb1:oaexpfffp01:oadejlandt01:oaexpnimp01:oaexpaix06:ottapps:oaexpsaap01:oablcsaap01:oadejsaap01:oadejmqmdt01:oablclanp01:oadejlanp01:oahedwasp01:oablcsaat1:oadejmqmp01:oamcbappp01:oaacpwasp01
/opera/logiciels -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=olicdlanp01:olsncwasp01:olsncdb2p01:olexpwpsr01
/nim/lppsource   -vers=2:3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottland1:oaexpnimp01

When i try to recreate the SPOT after unexporting the FS and re-export them, the still occurs. Anyone has an idea for me?

I'm still new AIX installation

Regards,
Trivium012

You need to include the filesets reported as "missing". A SPOT (shared product object tree) is like a shared, NFS-mounted "/usr"-tree and therefore needs several core packages included otherwise it couldn't act in this function. If you do not have them in your LPP-source you should include them there either.

Further, this is only a suspicion but it seems you manipulated the exports file yourself. As a rule of thumb: don't do that! At least don't do that with anything in or below the directory with the NIM resources. It might solve one specific problems but usually introduces several dozens of new ones in the process.

Another frequent problem is the definition of the NIM networks. NIM works (in parts) on top of the bootp protocol and therefore has to specifically check clients on other networks if they can be booted with it (this means testing the switch/router for being able to act as a "bootp relay agent", originally called "bootp forwarding agents", see RFC951, RFC1532, RFC1542, etc.) which is why for each network a client could be on a "NIM network" has to be defined.

Finally, when you allocate a resource to a client and it doesn't work somehow in most cases - but not all! - the resources are deallocated. Alas, rather frequently they remain allocated and not even a deallocation with the "force" option will straighten them out. NIM is quite untrustworthy in this regard and i hate to say it but it didn't improve much over the ~20 years i work with it. It is sometimes a good idea to simply delete the respective machines object and recreate it from scratch.

Right now i am not at the office so i cannot look it up but tomorrow i can post you a simpler way to create SPOTs, so stay tuned.

I hope this helps.

bakunin

Good morning Bakunin!

Thanks for the reply!

This error happened on my first try. So as part of common sense troubleshooting:
-I unexported everything with exportfs -ua
-Backuped the /etc/exports
-modified the exportfs file to add directly the folder where the SPOT is.
-Exported everything with exportfs -a

Once I noticed the error was still occuring I figured the Folders added in /etc/exportfs are reccursive, therefore I rollbacked.

I'm looking foward to see your procedure

Trivium012

---------- Post updated at 10:59 AM ---------- Previous update was at 10:22 AM ----------

So I decided to try with a mksysb instead and I found a mksysb ressource that was made prior a prior sysadmin. So I made the SPOT with it, but the error messahe occured again... but this time, when I list the new SPOT, it says Ready for use

root@oaexpnimp01(/nim/mksysb) # nim -o define -t spot -a source=generic01_61TL6SP5 -a server=master -a location=/nim/spot spottest1

 Creating SPOT in "/nim/spot" on machine "master" from "generic01_61TL6SP5" ...

 Restoring files from BOS image.  This may take several minutes ...


 Checking filesets and network boot images for SPOT "spottest1".
 This may take several minutes ...

warning: 0042-001 m_mkspot: processing error encountered on "master":
   0042-175 c_ch_nfsexp: An unexpected result was returned by the
        "/usr/sbin/exportfs" command:
        exportfs: 1831-186 /nim/mksysb/AIXgeneric/generic01.61TL6SP5.mksysb not found in /etc/exports



root@oaexpnimp01(/nim/mksysb) # lsnim -l spottest1
spottest1:
   class         = resources
   type          = spot
   plat_defined  = chrp
   arch          = power
   Rstate        = ready for use
   prev_state    = verification is being performed
   location      = /nim/spot/spottest1/usr
   version       = 6
   release       = 1
   mod           = 6
   oslevel_r     = 6100-06
   alloc_count   = 0
   server        = master
   if_supported  = chrp.64 ent
   Rstate_result = success
   mksysb_source = generic01_61TL6SP5

I will try with this and keep you posted!

Also, if it works, I also want to know how to fix the problem above! For my own understanding (I wish I could simulate a PowerPC at home for my personal tests )

---------- Post updated at 11:33 AM ---------- Previous update was at 10:59 AM ----------

Ok so I allocated my SPOT and my MKSYSB to my new LPAR and started the software installation. But when the LPAR boots, I get stuck on error 0611 :Remote mount of the NFS file system failed.

But all my nfs daemons seems to be running fine (I think?)

root@oaexpnimp01(/nim/mksysb) # lssrc -g nfs
Subsystem         Group            PID          Status
 biod             nfs              19661004     active
 nfsd             nfs              18350294     active
 rpc.mountd       nfs              18219008     active
 rpc.lockd        nfs              16515326     active
 rpc.statd        nfs              15466566     active
 nfsrgyd          nfs                           inoperative
 gssd             nfs                           inoperative

First off, i want to apologize. Having a very busy day at the office made me forget to update this thread, i promise to make good for that first thing tomorrow morning. Sorry.

This is probably where your error is. You DO NOT EXPORT ANYTHING! Instead "allocate" a resource (SPOT, mksysb, ...) to a client. NIM will do the exporting, mounting, unmounting and unexporting all on its own. You "allocate" (NIMs wording) the resource using the "nim" command:

nim -o allocate -a spot=<spotname> -a lpp_source=<lpp_name> <clientname>

or you can do it using a SMIT panel (search in "NIM->NIM Administration Tasks->somewhere", i don't know it by heart).

You might want to read this little introduction i once wrote in the meanwhile to get acquainted to NIMs and AIXs terminology.

There are, of course, more in-depth sources too: i can wholeheartedly recommend the IBM Redbook on NIM. Despite the seemingly outdated version number it is still quite up-to-date. NIM is a very stable software and major changes haven't taken place since this book.

Yes, if you use NFS3 or lower.

If you use NFS4 you need nfsrgyd to be running. Further you need to have both machines (server and client) in the same NFS domain. Use the chnfsdom command to display and/or set the NFS domain. I use to set it to a value equal to the respective DNS domain, but this isn't required. Notice that for NFS4 you also need some FS as a "stable storage", preferably one without an external JFS log but using an "inline log" instead.

I hope this helps.

bakunin

My ressources are allocated...

root@oaexpnimp01(/nim/mksysb) # lsnim -c resources generic01
generic01_61TL6SP5     mksysb
spottest1              spot
AIX61_TL1_2            lpp_source
nim_script             nim_script       directory containing customization scrip
boot                   boot             represents the network boot resource

OK, sorry for the delay, here is my approach to managing NIM resources:

Start with an LPP_SOURCE. To avoid having update packages without the respective base-level filesets in my LPP_SOURCES i always copy the base-level LPP_SOURCE (which contains only install-packages and no update-packages) first. Then i create version X+1 using the resource of version X as a basis. Here is how i created the AIX 7.1 TL3 SP3 LPP_source from the 7.1 TL2.

First, copy the LPP_SOURCE of your base level fileset:

# mkdir /nimres/aix_71/lpp_71_03_03
# cd /nimres/aix_71/lpp_71_02
# pax -rwl * ../lpp_71_03_03

after this you update the newly created image(-copy) with your updates to the level you want. /nimres/aix_71/lpp_71_03_source holds the packages i downloaded from fix-central:

# bffcreate -d /nimres/aix_71/lpp_71_03_source \
            -t /nimres/aix_71/lpp_71_03_03/installp/ppc \
            -X all

Once this is through i create the NIM-resource to use that image:

# nim -o define \
      -t lpp_source \
      -a server=master \
      -a comments="AIX 7.1.3 SP3 (1415)" \
      -a location=/nimres/aix_71/lpp_71_03_03 lpp_71_03_03

To remove all the unnecessary languages you don't need (perhaps you need only "C", "en_US" and maybe your local locale):

nim -o lppmgr -a lppmgr_flags="-bux -r -e"  lpp_71_03_03

Now your LPP_source is ready to use. If you need a SPOT you create it from the LPP-SOURCE:

nim -o define -t spot -a server=master \
      -a location=/nimres/spots \
      -a comments="AIX 7.1.3 SP3 (1415)" \
      -a source=lpp_71_03_03 spot_71_03_03

Here is how you install packages through NIM:

a) from the NIM-Master:

root@nim-master # nim -o cust -a lpp_source=<lpp_source> -a filesets="<pkg1> [<pkg2> <pkg3> .. ]"  <client>

b) from the NIM-client (the /etc/niminfo file has to be configured already and the client needs to be configured on the NIM-master) :

root@lpar # nimclient -o cust -a lpp_source=<lpp_source> -a filesets="<pkg1> [<pkg2> <pkg3> .. ]"

I hope this helps.

bakunin

Hi Bakunin!

So while you answered me, I finally managed to install the OS by making a spot from a mksysb that was already there. So main problem fixed. But I still want to be able to create my own lpp_source and SPOT (for my own knowledge and to document properly)

So I downloaded the base image of AIX from the IBM website and created an lpp_source from it.

root@oaexpnimp01(/nim/OS_IMAG) # loopmount -i /nim/OS_IMAG/6.1_AIX_Operating_System_DVD_1_of_2_6100-09-04_112014.udf -o "-V cdrfs -o ro" -m /mnt/cdrom
root@oaexpnimp01(/nim/OS_IMAG) # cd /mnt/cdrom/
root@oaexpnimp01(/mnt/cdrom) # ls -l
total 84
-rw-rw-r--    1 4000     4000             42 Oct 15 12:43 .Version
drwxr-xr-x    2 4000     4000           2048 Oct 15 12:40 6100-09
-rw-r--r--    1 4000     4000             16 Oct 15 12:40 OSLEVEL
-rw-r--r--    1 4000     4000            981 Oct 15 12:40 README.aix
drwxrwxr-x    4 4000     4000           2048 Oct 15 12:41 RPMS
-rw-r--r--    1 4000     4000           6424 Oct 15 12:40 bosinst.data
-rw-r--r--    1 4000     4000          15081 Oct 15 12:40 image.data
drwxr-xr-x    4 4000     4000           2048 Oct 15 12:42 installp
drwxr-xr-x    3 4000     4000           2048 Oct 15 12:40 ppc
drwxr-xr-x    3 4000     4000           2048 Oct 15 12:40 root
drwxr-xr-x   11 4000     4000           2048 Oct 15 12:42 usr

root@oaexpnimp01(/mnt/cdrom) # nim -o define -t lpp_source -a server=master -a source=/mnt/cdrom/ -a location=/nim/lppsource/AIX61_00 AIX61_00
Preparing to copy install images (this will take several minutes)...

/nim/lppsource/AIX61_00/RPMS/ppc/cdrecord-1.9-9.aix5.3.ppc.rpm
/nim/lppsource/AIX61_00/RPMS/ppc/mkisofs-1.13-9.aix5.3.ppc.rpm
/nim/lppsource/AIX61_00/RPMS/ppc/expect-5.42.1-3.aix6.1.ppc.rpm
/nim/lppsource/AIX61_00/RPMS/ppc/tcl-8.4.7-3.aix6.1.ppc.rpm
/nim/lppsource/AIX61_00/RPMS/ppc/tk-8.4.7-3.aix6.1.ppc.rpm
/nim/lppsource/AIX61_00/installp/ppc/xlC.sup.aix50.rte.9.0.0.1.I
/nim/lppsource/AIX61_00/installp/ppc/xlC.rte.12.1.0.1.I
/nim/lppsource/AIX61_00/installp/ppc/xlC.msg.en_US.cpp.9.0.0.0.I
/nim/lppsource/AIX61_00/installp/ppc/xlC.cpp.9.0.0.0.I
/nim/lppsource/AIX61_00/installp/ppc/xlC.aix61.12.1.0.1.I
...

A crap load like the last lines...

Now checking for missing install images...
  
All required install images have been found. This lpp_source is now ready.
  
root@oaexpnimp01(/mnt/cdrom) # lsnim -c resources
boot                         resources       boot
nim_script                   resources       nim_script
spottest1                    resources       spot
AIX61_00                     resources       lpp_source
TSM_client_AIX_v55           resources       lpp_source
cas_client                   resources       installp_bundle
cas_server                   resources       installp_bundle
all_LPAR_MAG                 resources       script
all_LPAR_delete_user         resources       script
all_LPAR_create_user         resources       script
openssh_client               resources       installp_bundle
openssh_server               resources       installp_bundle
bid_ow                       resources       bosinst_data
VIOS_2_2_FP24_SP02           resources       mksysb
spot_VIOS_2_2_FP24_SP02      resources       spot
sc_listug                    resources       script
sc_rmuser                    resources       script
mksysb_exclude               resources       exclude_files
generic01_61TL6SP5           resources       mksysb
get_Audit_Files              resources       script
ottvio1_201208301727         resources       mksysb
sc_secgat                    resources       script
create_ug                    resources       script
sc_custom                    resources       script
oaexpviop01_201210140232     resources       mksysb
oaexpviop02_201210140239     resources       mksysb
  
root@oaexpnimp01(/mnt/cdrom) # nim -o define -t spot -a server=master -a location=/nim/spot/ -a source=AIX61_00 -a installp_flags=-aQg spot-AIX61_00
  
Creating SPOT in "/nim/spot/" on machine "master" from "AIX61_00" ...
  
Restoring files from BOS image.  This may take several minutes ...
  
  
Checking filesets and network boot images for SPOT "spot-AIX61_00".
This may take several minutes ...
  
warning: 0042-001 m_mkspot: processing error encountered on "master":
0042-175 c_ch_nfsexp: An unexpected result was returned by the
       "/usr/sbin/exportfs" command:
        exportfs: 1831-186 /nim/lppsource/AIX61_00 not found in /etc/exports
  
  
rc=0
warning: 0042-001 m_instspot: processing error encountered on "master":
   0042-175 c_ch_nfsexp: An unexpected result was returned by the
        "/usr/sbin/exportfs" command:
       exportfs: 1831-186 /nim/lppsource/AIX61_00 not found in /etc/exports
  
  
rc=0
warning: 0042-001 m_instspot: processing error encountered on "master":
   0042-062 m_ckspot: "spot-AIX61_00" is missing something which is
        required
  
  
root@oaexpnimp01(/mnt/cdrom) # lsnim -l spot-AIX61_00
 spot-AIX61_00:
   class         = resources
   type          = spot
   arch          = power
   Rstate        = information is missing from this object's definition
   prev_state    = verification is being performed
   info          = warning: 0042-157 c_ckspot: unable to access the "/nim/spot/spot-AIX61_00/usr/./lpp/bosinst/image.template" file
   location      = /nim/spot/spot-AIX61_00/usr
   version       = 6
   release       = 1
   mod           = 9
   oslevel_r     = 6100-09
   alloc_count   = 0
   server        = master
   Rstate_result = success
   mk_netboot    = yes
   missing       = "network boot image"
   missing       = bos.64bit
   missing       = bos.diag
     missing       = bos.mp64
     missing       = bos.net.nfs.client
     missing       = bos.net.tcp.client
     missing       = bos.net.tcp.smit
     missing       = bos.sysmgt.nim.client
     missing       = bos.sysmgt.nim.spot
     missing       = bos.sysmgt.serv_aid
     missing       = bos.sysmgt.smit
     missing       = bos.sysmgt.sysbr
     missing       = bos.terminfo
     missing       = bos.wpars
     missing       = mcr.rte
  

So I'm guessing I really do have an NFS problem, but I have no idea how to troubleshoot this problem...

Here's my exports file

 root@oaexpnimp01(/mnt/cdrom) # exportfs
  /nim/VIOS                            -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottvio1:oaexpviop01:oaexpviop02
  /opera/scripts                       -sec=sys:krb5p:krb5i:krb5:dh,rw
  /nim/HMC                             -vers=3,sec=sys:krb5p:krb5i:krb5:dh,access=otthmc1,root=otthmc1
  /opera/nimfs                         -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottwaspsp:ottland1:ottutil:ottwas1:ottfircoqa:oaexpswpp01:
ottdb1:oadejlandt01:oaexpnimp01:oaexpaix06:ottapps:oaexpsaap01:oaexpfffp01:oablcsaap01:oadejsaap01:oadejmqmdt01:oablclanp01
:oadejlanp01:oahedwasp01:oablcsaat1:oadejmqmp01:otticdqa:oamcbappp01:oldejwasdt01:oldejdb2dt01:oldejwasp01:oldejdb2p01:
oaacpwasp01:olicdlanp01:olsncwasp01:olsncdb2p01
  /opera/logiciels                     -vers=3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=olicdlanp01:olsncwasp01:olsncdb2p01:olexpwpsr01
  /nim/spot                            -sec=sys:krb5p:krb5i:krb5:dh,rw,root=generic01
  /nim/lppsource                       -vers=2:3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottland1:oaexpnimp01:generic01
  /nim/mksysb                          -vers=2:3,sec=sys:krb5p:krb5i:krb5:dh,rw,root=ottwaspsp:ottland1:ottutil:ottwas1:ottfircoqa:oaexpswpp01
:ottvio1:oaexpviop01:oaexpviop02:ottdb1:oaexpfffp01:oadejlandt01:oaexpnimp01:oaexpaix06:ottapps:oaexpsaap01:oablcsaap01:oadejsaap01
:oadejmqmdt01:oablclanp01:oadejlanp01:oahedwasp01:oablcsaat1:oadejmqmp01:oamcbappp01:oaacpwasp01:generic01
  /export/nim/scripts/generic01.script -ro,root=generic01,access=generic01
  

Thanks for the help!!

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:

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:

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

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:

bffcreate -c -d <source_device/path>

They will now have one of two names:

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"):

 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!