Had that today with a nim_bosinst operation: Dunno why this error pops in, this file exists (I checked), but I know that it is caused by the following option in the smit nim_bosinst menu: Just change this to « No »
Small NIM cheatsheet
Bundle creation A NIM installp bundle is a file that contains the names of filesets that should be installed or removed by a NIM operation. 1. installp bundle file creation, I for filesets, R for RPM : 2. installp bundle
NIM : get the latest TL on fix central and make it available on your nim server
1. Simplest method : create a lpp_source from a previous one (create the target FS before this): –> so you can avoid errors regarding the « simages » attribute 1.1 eliminate any unnecessary packages 1.2 update it with the latest TL don’t
NIM : enabling debug mode for a bos install without using a bosinst_data resource
Call 911 Just type » 911 » on the Installation menu : It should display « BOSINST_DEBUG enabled » : Let’s debug Now we can launch migration again and check why it crashes (in my example , my AIX 5.3 to
NIM operations don’t work after a Live Partition Mobility? Update your NIM client’s CPU_ID !
Using Live partition mobilty is a real pain reliever when you need to get some downtime, in order to upgrade your pseries’ firmware , for example . (if you’re not familiar with LPM migration , here is a visual example,
NIM : update your system easily with nimclient
I want to update my client to the latest AIX 7.1 service pack (service pack 5 for AIX 7.1) and I wanna get rid of the old « exportfs – mount – smit update_all – umount » sequence, and use the