Login or Register to Ask a Question and Join Our Community


AIX

NIM server

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX NIM server
# 1  
Old 05-14-2010
[Solved] NIM server
Hi.
I would like to try installation via NIM server. I have set up :

Code:
[lpar_a06:root:/tftpboot:] lsnim
master              machines        master
boot                resources       boot
nim_script          resources       nim_script
NET_EN0             networks        ent
mksysb_AIX_6141     resources       mksysb
SPOT_AIX_6141       resources       spot
lpar_a07            machines        standalone

[lpar_a06:root:/tftpboot:] lsnim -l lpar_a07
lpar_a07:
   class          = machines
   type           = standalone
   connect        = shell
   platform       = chrp
   netboot_kernel = 64
   if1            = NET_EN0 lpar_a07 0
   cable_type1    = bnc
   Cstate         = ready for a NIM operation
   prev_state     = ready for a NIM operation
   Mstate         = not running

[lpar_a06:root:/tftpboot:] lsnim -l NET_EN0
NET_EN0:
   class      = networks
   type       = ent
   Nstate     = ready for use
   prev_state = information is missing from this object's definition
   net_addr   = 192.168.0.0
   snm        = 255.255.252.0
   routing1   = default 192.168.0.1

[lpar_a06:root:/tftpboot:] lsnim -l master
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                 = NET_EN0 lpar_a06 EA7068BB7064
   cable_type1         = N/A
   Cstate              = ready for a NIM operation
   prev_state          = ready for a NIM operation
   Mstate              = currently running
   serves              = SPOT_AIX_6141
   serves              = boot
   serves              = mksysb_AIX_6141
   serves              = nim_script
   master_port         = 1058
   registration_port   = 1059
   reserved            = yes

[lpar_a06:root:/tftpboot:] lsnim -l mksysb_AIX_6141
mksysb_AIX_6141:
   class          = resources
   type           = mksysb
   Rstate         = ready for use
   prev_state     = unavailable for use <----- IS THIS RIGHT ?
   location       = /nim/mksysb/aix61000_64_os_0401_us_2.gbl.mksysb_iplno
   version        = 6
   release        = 1
   mod            = 4
   oslevel_r      = 6100-04
   alloc_count    = 0
   server         = master
   extracted_spot = SPOT_AIX_6141
   creation_date  = Thu May 13 15:00:24 2010

[lpar_a06:root:/tftpboot:] lsnim -l SPOT_AIX_6141
SPOT_AIX_6141:
   class         = resources
   type          = spot
   plat_defined  = chrp
   arch          = power
   Rstate        = ready for use
   prev_state    = lppchk operation is being performed
   location      = /nim/mksysb/SPOT_AIX_6141/usr
   version       = 6
   release       = 1
   mod           = 4
   oslevel_r     = 6100-04
   alloc_count   = 0
   server        = master
   if_supported  = chrp.64 ent
   Rstate_result = failure <----- IS THIS OK ?
   mksysb_source = mksysb_AIX_6141

[lpar_a06:root:/home/root:] nim -o lppchk -a show_progress=yes SPOT_AIX_6141
+-----------------------------------------------------------------------------+
                      Performing "lppchk" Operation
+-----------------------------------------------------------------------------+
 Performing lppchk operation on machine 1 of 1: master ...

lppchk:  The following filesets need to be installed or corrected to bring
         the system to a consistent state:

  bos.64bit 0.0.0.0                       (COMMITTED)
  bos.diag 0.0.0.0                        (COMMITTED)
  bos.mp 0.0.0.0                          (COMMITTED)
  bos.net.nfs.client 0.0.0.0              (COMMITTED)
  bos.net.tcp.client 0.0.0.0              (COMMITTED)
  bos.net.tcp.smit 0.0.0.0                (COMMITTED)
  bos.sysmgt.nim.client 0.0.0.0           (COMMITTED)
  bos.sysmgt.nim.spot 0.0.0.0             (COMMITTED)
  bos.sysmgt.serv_aid 0.0.0.0             (COMMITTED)
  bos.sysmgt.smit 0.0.0.0                 (COMMITTED)
  bos.sysmgt.sysbr 0.0.0.0                (COMMITTED)
  bos.terminfo 0.0.0.0                    (COMMITTED)
  bos.up 0.0.0.0                          (COMMITTED)
  devices.all 0.0.0.0                     (COMMITTED)

+-----------------------------------------------------------------------------+
                      "lppchk" Operation Summary
+-----------------------------------------------------------------------------+
 Target                  Result
 ------                  ------
 master                  FAILURE
 Unexpected results ... (details will follow). Performing clean up ...


master
------
warning: warning: 0042-001 m_lppchk: processing error encountered on "master":
   0042-175 c_ckspot: An unexpected result was returned by the "/usr/bin/lppchk" command:

See the log file:
        /nim/mksysb/SPOT_AIX_6141/usr/lpp/bos/inst_root/var/adm/ras/nim.lppchk
for details or use the "showlog" operation.


[lpar_a06:root:/tftpboot:] lsnim -l boot
boot:
   class       = resources
   type        = boot
   comments    = represents the network boot resource
   Rstate      = ready for use
   location    = /tftpboot
   alloc_count = 0
   server      = master
   reserved    = yes

[lpar_a06:root:/home/root:] ls -l /tftpboot
total 32616
-rw-r--r--    1 root     system     16692224 May 13 15:42 SPOT_AIX_6141.chrp.64.ent
-rw-r--r--    1 root     system          512 May 13 15:42 SPOT_AIX_6141.iplrecord.ent

[lpar_a06:root:/home/root:] cat /etc/bootptab

# bootpd 2.1 #77: Tue Jul 16 11:29:48 CDT 1991

# /etc/bootptab: dump of bootp server database.
#
# Dump taken Fri May 14 08:10:13 2010
#
#
# Legend:
#       hd -- home directory
#       bf -- bootfile
#       bs -- bootfile size in 512-octet blocks
#       cs -- cookie servers
#       ds -- domain name servers
#       gw -- gateways
#       ha -- hardware address
#       hd -- home directory for bootfiles
#       ht -- hardware type
#       im -- impress servers
#       ip -- host IP address
#       lg -- log servers
#       lp -- LPR servers
#       ns -- IEN-116 name servers
#       rl -- resource location protocol servers
#       sa -- server IP address in bootp reply packet
#       sm -- subnet mask
#       to -- time offset (seconds)
#       ts -- time servers
lpar_a07:bf=/tftpboot/:ip=192.168.1.7:ht=ethernet:sa=192.168.1.6:sm=255.255.252.0:

[lpar_a06:root:/home/root:] grep -i boot /etc/inetd.conf ; grep -i tftp /etc/inetd.conf
bootps  dgram   udp     wait    root    /usr/sbin/bootpd       bootpd -d /etc/bootptab
tftp     dgram  udp6    SRC     nobody  /usr/sbin/tftpd         tftpd -nv

When I try to boot up lpar_a07 I will get just error message "NO OS INSTALLED"

On nim server :

Code:
 cat /var/adm/ras/syslog.log
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Received boot request.
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: request from IP addr 192.168.1.7
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: found 192.168.1.7 lpar_a07
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: bootfile = /tftpboot/
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: vendor magic field is 99.130.83.99
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: sending RFC1048-style reply
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: The following addresses are included in the bootp reply
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Client IP address (bp->bp_ciaddr) = 192.168.1.7
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Server IP address (bp->bp_siaddr) = 192.168.1.6
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Gateway IP address (bp->bp_giaddr) = 192.168.1.6 <---- MY GATEWAY IS 192.168.0.1 dont
now why is there 192.168.1.6 , i have set up in SMS for client gateway 182.168.0.1.
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Finished processing boot request.
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Received boot request.
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: request from IP addr 192.168.1.7
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: found 192.168.1.7 lpar_a07
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: bootfile = /tftpboot/
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: vendor magic field is 99.130.83.99
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: sending RFC1048-style reply
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: The following addresses are included in the bootp reply
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Client IP address (bp->bp_ciaddr) = 192.168.1.7
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Server IP address (bp->bp_siaddr) = 192.168.1.6
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Gateway IP address (bp->bp_giaddr) = 192.168.1.6
May 14 10:18:13 lpar_a06 daemon:info bootpd[368872]: Finished processing boot request.
May 14 10:18:13 lpar_a06 daemon:info tftpd[413724]: [00000204] EZZ7044I Retrieval failed for the message: TFTP_MSG_C_45: {1,44} : lpar_a07 RRQ     <file=Received   , mode=/tftpboot/, recognized options: octet>
May 14 10:18:13 lpar_a06 daemon:info tftpd[413724]: [00000204] EZZ7029I Retrieval failed for the message: TFTP_MSG_C_29: {1,29} : Status      Read request for lpar_a07: /tftpboot/

Code:
[lpar_a06:root:/home/root:] ls -l /tftpboot/
total 32616
-rw-r--r--    1 root     system     16692224 May 13 15:42 SPOT_AIX_6141.chrp.64.ent
-rw-r--r--    1 root     system          512 May 13 15:42 SPOT_AIX_6141.iplrecord.ent

Could you have a look at that? Please. Maybe you will see where I did mistake.
Thanks for help.

---------- Post updated at 11:00 AM ---------- Previous update was at 08:35 AM ----------



---------- Post updated at 11:01 AM ---------- Previous update was at 11:00 AM ----------

I got 1 step forward ... I changed in /etc/bootptab to
lpar_a07:bf=/tftpboot/SPOT_AIX_6141.chrp.64.ent:ip=192.168.1.7:ht=ethernet:sa=192.168.1.6:sm=255.255.252.0:

and now kernel is copied and it started booting up but it hangs on ref code 0608 which means "Attempting to retrieve the client.info file with tftp from the SPOT server" . I did try to look that file on NIM server but I didn't succeed. Do I have that file create manually ?

Thanks
Last edited by phobus; 05-14-2010 at 05:51 AM..
# 2  
Old 05-14-2010
First off, i wonder where your lpp_source is. Didn't you use it to create the SPOT?

Second, i don't see where you allocated the NIM resources for the system you want to install. NIM is pretty selective about who to install and every resource you want to use for a client installation has to be "allocated" first (meaning that the client gets the permission to use it - once!).

Third, the "previous state = unavailable for use" is ok. It just means that the resource was newly created, its state now is "ready for use", but the state before that was (naturally) different.

Finally i have to disencourage you: you didn't get a "step forward", because you should be able to use NIM without having to resort to such measures. Chances are that if you change these files you will effectively confuse NIM and once you get it running it still won't work because of your changes. (The same is true for manual changes on "/etc/exports", which is a common problem in malfunctioning NIM-setups.)

You might want to read the (very short) introduction to NIM concepts i wrote some time ago: NIM-Introduction. For a more elaborate description get IBMs Redbooks (see our list of AIX links) regarding NIM.

I hope this helps.

bakunin
# 3  
Old 05-15-2010
Thanks for answer bakunin. I gotta go all over and reconfigure it from scratch. And nice reading about NIM what you wrote.
# 4  
Old 05-17-2010
I found answer .... I forgot to configure client for bos installation. After I configured it the Cstate was changed to = "BOS installation has been enabled" and ClientName.info file + few links were created. And now it works.
Problem solved.
Thanks.
# 5  
Old 05-18-2010
You can use smitty to setup a BOS install like this, and you don't need an LPP_SOURCE:

Code:
smitty nim -->
Perform NIM Software Installation and Maintenance Tasks -->
Install and Update Software -->
Install the Base Operating System on Standalone Clients -->
lpar_a07 -->
mksysb - Install from a mksysb -->
mksysb_AIX_6141 -->
SPOT_AIX_6141 -->
Change "ACCEPT new license agreements?" to "yes"
Change "Initiate reboot and installation now?" to "no"
Press enter twice

At this point your NIM server is ready for the NIM client to connect and take the mksysb image. You can then boot up lpar_a07 to the SMS menu and setup your IPL menus to boot from your NIM server and the restore should take place. Later, you can get fancy and use the bosinst_data and image_data to do more advanced stuff but just the steps above are a good start.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

exported filesystems on a NIM server

I have a filesystem that was exported sometime in the past, probably by NIM processes, but cannot be unexported now. How can I get rid of this? Any ideas? I tried rebooting and it survived it. hostname:/:$ exportfs -v /usr/lpp/bos.sysmgt/nim/methods... (2 Replies)
Discussion started by: kah00na
2 Replies

2. AIX

NIM Master as Mgmt Server

Guys, I need your help I got a requirement from a cUstomer asking for a specific design He wants to use the NIM Master as one single mgmt server and access the nodes maintained by it there by the accounting is in one single server for all the nodes Note:- Direct login to the nodes will... (3 Replies)
Discussion started by: kkeng808
3 Replies

3. AIX

Troubleshooting NIM Server

hello folks, Can someone help me troubleshoot the NIM Server NIM MASTER: >> # hostname oldbcoedv # cat /etc/hostname 192.52.100.29 bcoeqa bcoeqa.bin.com.sa 192.52.100.66 oldbcoedv # cat /etc/bootptab ..... # T180 -- (xstation only) -- enable virtual screen #NO CLIENTS... (6 Replies)
Discussion started by: filosophizer
6 Replies

4. AIX

configuring NIM server

I have never used NIM. Please help with the steps for configuring NIM server and client. thanks Pchangba (3 Replies)
Discussion started by: pchangba
3 Replies

5. AIX

NIM Server Issue

Hi, I'm getting the above error while trying to take a MKSYSB image via NIM. I've only just started getting this and don't know why it is failing. Any one got any suggestions? Thanks Kees (3 Replies)
Discussion started by: KeesH
3 Replies

6. UNIX for Advanced & Expert Users

NIM - mksysb of remote server

Hi, I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network. I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows Resource Name : gmt_fail_mksysb Server of... (1 Reply)
Discussion started by: KeesH
1 Replies

7. AIX

migrate NIM server through NIM installation

I try to migrate a NIM server from one server to another. I try to do a mksysb on NIM server restore the NIM server's mksysb to a client through NIM installation shutdown NIM server start newly installed client as NIM server Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies

8. AIX

NIM Server

Is anybody using a NIM server for DR recovery purposes? If so, how are you handling Volume Groups outside of root? (0 Replies)
Discussion started by: kd30185
0 Replies

9. AIX

NIM Server - bos.rte5.3.*

Trying to build a server off the NIM server and its complaining that my bos.rte.5.3.0.0 is a missing prerequisite. I have bos.rte.5.3.0.30 which is for AIX 5.3.3, my question is where can I find the bos.rte.5.3.0.0 ? Ive looked on my base AIX 5.3 software and cant find it. Any assistance... (0 Replies)
Discussion started by: maurice-pacific
0 Replies

10. AIX

NIM server setup (AIX 5.3)

Hi, I'a a new member here. My company just bought p570 with 8 LPAR (previously we have p650 with 4 LPAR). Did anyone have procedure how to setup NIM server (NIM LPAR) and how to install other new LPAR to use the NIM server (as client). Appreciate your help and thank you very much. Rgds, David (0 Replies)
Discussion started by: dshg
0 Replies
Login or Register to Ask a Question