Solved

Starting a new LPAR from NIM

Posted on 2011-03-16
9
3,833 Views
Last Modified: 2013-11-17
Hi wmp, I need your help... again :-)

I have a NIM on AIX 7.1 with latest SP. Look at my resources:

[root@bibmnim:/] lsnim -l
master:
   class               = machines
   type                = master
   max_nimesis_threads = 20
   if_defined          = chrp.64.ent
   comments            = machine which controls the NIM environment
   platform            = chrp
   netboot_kernel      = 64
   if1                 = network1 bibmnim AA92EA38AA04
   cable_type1         = N/A
   Cstate              = ready for a NIM operation
   prev_state          = ready for a NIM operation
   Mstate              = currently running
   serves              = AIX53TL12
   serves              = AIX53TL12SPOT
   serves              = AIX61TL6LPP
   serves              = AIX61TL6SPOT
   serves              = AIX71TL0LPP
   serves              = AIX71TL0SPOT
   serves              = MKSYSB_BIBMDES
   serves              = MKSYSB_BIBMDES_CONT
   serves              = MKSYSB_MIDDLEDES
   serves              = bid_ow
   serves              = boot
   serves              = nim_script
   lpp_source          = AIX53TL12
   control             = master
   master_port         = 1058
   registration_port   = 1059
   reserved            = yes
boot:
   class       = resources
   type        = boot
   comments    = represents the network boot resource
   Rstate      = ready for use
   location    = /tftpboot
   alloc_count = 1
   server      = master
   reserved    = yes
nim_script:
   class       = resources
   type        = nim_script
   comments    = directory containing customization scripts created by NIM
   Rstate      = ready for use
   location    = /export/nim/scripts
   alloc_count = 1
   server      = master
   reserved    = yes
network1:
   class      = networks
   type       = ent
   Nstate     = ready for use
   prev_state = ready for use
   net_addr   = 172.16.32.96
   snm        = 255.255.255.240
   routing1   = default 172.16.32.110
AIX71TL0LPP:
   class       = resources
   type        = lpp_source
   arch        = power
   Rstate      = ready for use
   prev_state  = unavailable for use
   location    = /nim/lpp_source/AIX71TL0LPP
   simages     = yes
   alloc_count = 0
   server      = master
AIX71TL0SPOT:
   class         = resources
   type          = spot
   plat_defined  = chrp
   arch          = power
   bos_license   = yes
   Rstate        = ready for use
   prev_state    = customization is being performed
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /nim/spot/AIX71TL0SPOT/usr
   version       = 7
   release       = 1
   mod           = 0
   oslevel_r     = 7100-00
   alloc_count   = 0
   server        = master
   if_supported  = chrp.64 ent
   Rstate_result = success
bid_ow:
   class       = resources
   type        = bosinst_data
   Rstate      = ready for use
   prev_state  = unavailable for use
   location    = /export/bosinst_data/bid_ow
   alloc_count = 0
   server      = master
AIX61TL6LPP:
   class       = resources
   type        = lpp_source
   arch        = power
   Rstate      = ready for use
   prev_state  = unavailable for use
   location    = /nim/lpp_source1/AIX61TL6LPP
   simages     = yes
   alloc_count = 1
   server      = master
AIX61TL6SPOT:
   class         = resources
   type          = spot
   plat_defined  = chrp
   arch          = power
   bos_license   = yes
   Rstate        = ready for use
   prev_state    = lppchk operation is being performed
   location      = /nim/spot1/AIX61TL6SPOT/usr
   version       = 6
   release       = 1
   mod           = 5
   oslevel_r     = 6100-05
   alloc_count   = 1
   server        = master
   if_supported  = chrp.64 ent
   Rstate_result = success
AIX53TL12:
   class       = resources
   type        = lpp_source
   arch        = power
   Rstate      = ready for use
   prev_state  = unavailable for use
   location    = /nim/lpp_source2/AIX53TL12
   simages     = yes
   alloc_count = 1
   server      = master
AIX53TL12SPOT:
   class         = resources
   type          = spot
   plat_defined  = chrp
   arch          = power
   bos_license   = yes
   Rstate        = ready for use
   prev_state    = lppchk operation is being performed
   location      = /nim/spot2/AIX53TL12SPOT/usr
   version       = 5
   release       = 3
   mod           = 12
   oslevel_r     = 5300-12
   alloc_count   = 0
   server        = master
   if_supported  = chrp.64 ent
   if_supported  = chrp.mp ent
   Rstate_result = success
MKSYSB_BIBMDES:
   class         = resources
   type          = mksysb
   Rstate        = ready for use
   prev_state    = unavailable for use
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /LPAR_MKSYSB/bibmdes/bibmdes_mksysb.img
   version       = 5
   release       = 3
   mod           = 12
   oslevel_r     = 5300-12
   alloc_count   = 0
   server        = master
   creation_date = Wed Mar 16 18:06:24 2011
bibmdes_prova:
   class          = machines
   type           = standalone
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = ent-Network1 bibmdes_prova 0
   cable_type1    = bnc
   Cstate         = BOS installation has been enabled
   prev_state     = ready for a NIM operation
   Mstate         = not running
   boot           = boot
   lpp_source     = AIX61TL6LPP
   mksysb         = MKSYSB_MIDDLEDES
   nim_script     = nim_script
   spot           = AIX61TL6SPOT
   control        = master
ent-Network1:
   class      = networks
   type       = ent
   comments   = Generated during definition of bibmdes_prova
   Nstate     = ready for use
   prev_state = information is missing from this object's definition
   net_addr   = 172.17.32.0
   snm        = 255.255.255.240
   routing1   = default 172.17.32.14
MKSYSB_MIDDLEDES:
   class         = resources
   type          = mksysb
   Rstate        = ready for use
   prev_state    = unavailable for use
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /LPAR_MKSYSB/middledes/middledes.img
   version       = 6
   release       = 1
   mod           = 6
   oslevel_r     = 6100-05
   alloc_count   = 1
   server        = master
   creation_date = Wed Mar 16 18:08:24 2011
MKSYSB_BIBMDES_CONT:
   class         = resources
   type          = mksysb
   Rstate        = ready for use
   prev_state    = unavailable for use
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /LPAR_MKSYSB/bibmdes_cont/contingencia.img
   version       = 5
   release       = 3
   mod           = 12
   oslevel_r     = 5300-12
   alloc_count   = 0
   server        = master
   creation_date = Wed Mar 16 18:09:52 2011

As you can see, I have created 3 resources from mysksb images using this command mksysb -e -i -p /mksysb_image.img

I ran this command after I created the resources:
nim -o bos_inst -a spot=AIX61TL6SPOT -a mksysb=MKSYSB_MIDDLEDES -a accept_licenses=yes -a no_client_boot=yes bibmdes_prova

So, I went to the BLADE server, create a new LPAR, setup tle IPL and boot from SMS. The LPAR starts loading the files from the tftpboot, bootps and I see it connects to the NFS on the NIM side, but it freezes.. see image attached

Am I missing something? For now I just want  NIM to keep mksysb resources to be used on new LPARs if dissaster recover.

Thanks.
nim-freeze.bmp
0
Comment
Question by:sminfo
  • 5
  • 4
9 Comments
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 35152181
Wow,

I fear that's going to be a hard one!

The only thing I can see at first sight is that you probably configured a wrong cable type "bnc" for your node, or do you actually still use Coax cables? I don't assume so!

I must admit, however, that I really (really!) don't have any idea whether this could actually do any harm.

Did you retry several times? If I remember well I once had such a situation where it worked at the third or even fourth try.

Is this your first Blade LPAR? Is the blade firmware at a recent level?

Let me analyze your issue a bit further tomorrow!

In the meantime you could try to verify and check the mksysb with "lsmksysb",
e.g.

lsmksysb -l -f /LPAR_MKSYSB/middledes/middledes.img
lsmksysb -L -f /LPAR_MKSYSB/middledes/middledes.img

(or use "smitty nim_verify_res")

Any clue?

Good luck an CU tomorrow!

wmp


0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 35152527
>> Is this your first Blade LPAR? <<

Sorry, that was a dumb question!

Since you configured the LPAR you must have an IVM running!
But I guess you used the Bladecenter's media tray to install it, and perhaps there is actually a difference between installing from DVD and installing via network.

Find the Blade microcode here (I guess you're familiar with that site however):

http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5085757&brandind=5000020

wmp
0
 

Author Comment

by:sminfo
ID: 35154756
Hi wmp,

One question, as you see I allocate one SPOT and a mksysb resource to the machine. This SPOT must be created from the mksysb? Because, I create the SPOT from the AIX 6.1 DVDs TL6, and the mksysb has AIX6.1 TL5.. ??

Now, I'll  try again with other mksysb resources, I have two made from AIX5.3 and one from AIX 6.1.. tell you later..:-)
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 35154784
No, the SPOT doesn't have to be created from the mksysb. Its level must (should) be equal to or higher than the mksysb level, that's all.

Did you change "bnc" to "N/A"?

Good luck anyway

wmp
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:sminfo
ID: 35158051
well.. I changed it from bnc to tp.. but I think the problem was not there... sometimes it starts to install.. so, the problem is on the SLOW fu.. speed between the NIM and tle BLADE/LPAR.. so, to finish this question, because I'll open other again...

I have this mksysb resource:
MKSYSB_MIDDLEPRE:
   class         = resources
   type          = mksysb
   Rstate        = ready for use
   prev_state    = ready for use
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /LPAR_MKSYSB/middlepre/middlepre.img
   version       = 6
   release       = 1
   mod           = 6
   oslevel_r     = 6100-06
   alloc_count   = 0
   server        = master
   creation_date = Thu Mar 17 14:59:30 2011

I want to create a SPOT called spotbibm  from this resource running:
nim -o define -t spot -a server=master -a location=/nim/spot1 -a source=MKSYSB_MIDDLEDES spotbibm, but it starts it aborts with this error:

[root@bibmnim:/var/adm/ras] nim -o define -t spot -a server=master -a location=/nim/spot1 -a source=MKSYSB_MIDDLEDES spotbi>

 Creating SPOT in "/nim/spot1" on machine "master" from "MKSYSB_MIDDLEDES" ...

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


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

0042-001 nim: processing error encountered on "master":
   warning: 0042-158 c_mkspot: unable to modify the "/etc/inetd.conf" file

rc=0
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 /LPAR_MKSYSB/middledes/middledes.img not found in /etc/exports


My exportfs
[root@bibmnim:/var/adm/ras] exportfs
exportfs: 1831-182 nothing exported


Any idea?
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 35158429
I think you should have "N/A" as cable type, not "tp"

The command you use to create the SPOT from mksysb is quite OK, the same thing works for me.

The errors during SPOT creation must have to do with the way you created the image (see your new Q!).
I fear there is a mismatch between the mksysb image and its representation in the NIM ODM.

But you should be able to install this image, which way ever you created it!
OK, the installation (mksysb restoration) should at least start and run a while and not hang at the very beginning!.


0
 

Author Comment

by:sminfo
ID: 35158639
But, I dont want to use PULL mode, I just wan to save all mksysb from all AIX's somewhere, and create a mksysb resource on the NIM. If some LPAR crash, I can get it soon this way. This is ONLY what I need, I dont think, for now, use NIM for anything else.. Remember we had a crashed last december and we spent 4 hous to get the server back.. that's why NIM is need it for us...:-)

What do you mean by "But you should be able to install this image, which way ever you created it! "
I think I MUST need the mksysb and the SPOT resource  (at the same level) to can install the LPAR (PUSH mode) from the SMS console.

Or is there any way to use ONLY the mksysb resource install a new LPAR?

Thanks ondce more wmp.

AHH, I changed to N/A :-)

0
 

Author Closing Comment

by:sminfo
ID: 35164095
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 35164098
>>  I just wan to save all mksysb from all AIX's somewhere, and create a mksysb resource on the NIM <<

Yes, that's exactly what I do, and it works perfectly with pull mode.
You can set it up on the master via cron. No scripts/crontab entries needed on the clients. All is managed centrally, you will never touch the clients again in order to create an mksysb image.
So, why shouldn't you use PULL mode?

And what do you mean with "somewhere"? The images must reside on the master, so the clients will be able to get them from there.

Restoring the mksysb is independent of how it has been created,  
You can request a restore from the client's SMS menu whichever way you created the mksysb resource,
the importatnt thing is that it exists!
And you need the SPOT, of course. That's part of the NIM paradigm.

mksysb alone is only sufficient if you have a bootable image.
Such an image must reside on tape or DVD. An image on disk is never bootable!
If there is a bootable image you don't need NIM at all.

With >> you should be able to install this image << I was trying to say that even if the image is inconsistent/faulty the installation process should at least start and not hang before anything has been attempted.

wmp
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Hello fellow BSD lovers, I've created a patch process for patching openjdk6 for BSD (FreeBSD specifically), although I tried to keep all BSD versions in mind when creating my patch. Welcome to OpenJDK6 on BSD First let me start with a little …
I promised to write further about my project, and here I am.  First, I needed to setup the Primary Server.  You can read how in this article: Setup FreeBSD Server with full HDD encryption (http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/A_3660-S…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now