Go Back   The UNIX and Linux Forums > Operating Systems > AIX
NIM client boot problem NIM client boot problem
Forums Search Forums Register Forum RulesMan PagesAlbums FAQ Members Calendar Search Today's Posts Mark Forums Read


AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace.

Closed Thread    
 
Thread Tools Search this Thread Display Modes
    #1  
Old 10-25-2011
Registered User
  
Join Date: Sep 2009
Posts: 79
Thanks: 2
Thanked 1 Time in 1 Post
NIM client boot problem
Hi all,

I have created VIO Server which serves 3 lpars. All of them are on VLAN ID 50.

From one lpar I installed and set up NIM master server called testAIX1.

Quote:
testAIX1:/ > lsnim -l master
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.64.ent
if_defined = chrp.mp.ent
if_defined = chrp.up.ent
comments = machine which controls the NIM environment
if_defined = rc=0.64.ent
if_defined = rc=0.mp.ent
platform = chrp
netboot_kernel = 64
if1 = network1 testAIX1 66F1F0004015
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
serves = AIX71_TL00_SP01_mksysb
serves = AIX71_TL00_SP01_spot
serves = boot
serves = nim_script
master_port = 1058
registration_port = 1059
reserved = yes
I have created client and allocated resources to it:


Code:
testAIX1:/ > lsnim -l test_lpar
test_lpar:
   class          = machines
   type           = standalone
   connect        = shell
   platform       = chrp
   netboot_kernel = 64
   if1            = network1 test_lpar 0
   cable_type1    = N/A
   Cstate         = BOS installation has been enabled
   prev_state     = not running
   Mstate         = not running
   boot           = boot
   mksysb         = AIX71_TL00_SP01_mksysb
   nim_script     = nim_script
   spot           = AIX71_TL00_SP01_spot
   control        = master


Code:
testAIX1:/ > exportfs
/export/spot/AIX71_TL00_SP01_spot/usr -ro,root=test_lpar,access=test_lpar
/export/mksysb/AIX71_TL00_SP01_mksysb -ro,root=test_lpar,access=test_lpar
/export/nim/scripts/test_lpar.script  -ro,root=test_lpar,access=test_lpar

I have set up IPL on test_lpar with correct NIM master server IP and GW.

And /etc/hosts file contains entry for NIM server and NIM client.

But I can not boot from it. From NIM master server from log file I got:


Code:
<Tue Oct 25 16:43:54 CDT 2011> <master> <7208992> <warning: warning: 0042-226 m_bos_inst:  A time-out occurred while attempting to initiate
        the bos_inst operation on the client.  The operation may not
        have started successfully.>

And time out from SMS of test_lpar client of NIM master server.

Could you tell me what am I doing wrong? Please.

Thank you.
Last edited by phobus; 10-25-2011 at 12:18 PM..
Sponsored Links
    #2  
Old 10-26-2011
Registered User
  
Join Date: May 2006
Location: England
Posts: 404
Thanks: 7
Thanked 7 Times in 7 Posts
Can you run the following and paste the results here:


Code:
ls -l /tftpboot


Code:
lsnim -c machines

Then I will have a further look at it.
Sponsored Links
    #3  
Old 10-26-2011
Registered User
  
Join Date: Sep 2009
Posts: 79
Thanks: 2
Thanked 1 Time in 1 Post
Here is what I did:

1.Commented out line in inetd.conf "bootps"
2. run
Code:
/usr/sbin/bootpd -s -d -d -d

3. Created another partition in another managed system (no VIOS there) and used HEA logical port

And I was able to boot up. So I think I have something wrong with VIOS if I can not boot via virtual ethernet adapter but I can ping NIM master.
Here's config of VIOS:


Code:
$ lsdev -virtual
name             status      description
ent2             Available   Virtual I/O Ethernet Adapter (l-lan)
vhost0           Available   Virtual SCSI Server Adapter
vhost1           Available   Virtual SCSI Server Adapter
vhost2           Available   Virtual SCSI Server Adapter
vsa0             Available   LPAR Virtual Serial Adapter
testAIX1_dvg1    Available   Virtual Target Device - Logical Volume
testAIX1_nvg1    Available   Virtual Target Device - Logical Volume
testAIX1_rvg1    Available   Virtual Target Device - Logical Volume
testAIX2_rvg1    Available   Virtual Target Device - Logical Volume
testlpar_rvg1    Available   Virtual Target Device - Logical Volume
testlpar_rvg2    Available   Virtual Target Device - Logical Volume
vtopt0           Available   Virtual Target Device - File-backed Optical
vtopt1           Available   Virtual Target Device - File-backed Optical
ent3             Available   Shared Ethernet Adapter
ent4             Available   VLAN


Code:
$ lsdev -dev ent2 -attr
attribute      value          description                                user_settable

alt_addr       0x000000000000 Alternate Ethernet Address                 True
chksum_offload yes            Checksum Offload Enable                    True
copy_buffs     32             Transmit Copy Buffers                      True
copy_bytes     65536          Transmit Copy Buffer Size                  True
desired_mapmem 0              I/O memory entitlement reserved for device False
max_buf_huge   64             Maximum Huge Buffers                       True
max_buf_large  64             Maximum Large Buffers                      True
max_buf_medium 256            Maximum Medium Buffers                     True
max_buf_small  2048           Maximum Small Buffers                      True
max_buf_tiny   2048           Maximum Tiny Buffers                       True
min_buf_huge   24             Minimum Huge Buffers                       True
min_buf_large  24             Minimum Large Buffers                      True
min_buf_medium 128            Minimum Medium Buffers                     True
min_buf_small  512            Minimum Small Buffers                      True
min_buf_tiny   512            Minimum Tiny Buffers                       True
trace_debug    no             Trace Debug Enable                         True
use_alt_addr   no             Enable Alternate Ethernet Address          True


Code:
$ lsdev -dev ent3 -attr
attribute     value    description                                                        user_settable

accounting    disabled Enable per-client accounting of network statistics                 True
ctl_chan               Control Channel adapter for SEA failover                           True
gvrp          no       Enable GARP VLAN Registration Protocol (GVRP)                      True
ha_mode       disabled High Availability Mode                                             True
jumbo_frames  no       Enable Gigabit Ethernet Jumbo Frames                               True
large_receive no       Enable receive TCP segment aggregation                             True
largesend     0        Enable Hardware Transmit TCP Resegmentation                        True
netaddr       0        Address to ping                                                    True
pvid          50       PVID to use for the SEA device                                     True
pvid_adapter  ent2     Default virtual adapter to use for non-VLAN-tagged packets         True
qos_mode      disabled N/A                                                                True
real_adapter  ent0     Physical adapter associated with the SEA                           True
thread        1        Thread mode enabled (1) or disabled (0)                            True
virt_adapters ent2     List of virtual adapters associated with the SEA (comma separated) True


Code:
$ lsdev -dev ent4 -attr
attribute     value description       user_settable

base_adapter  ent3  VLAN Base Adapter True
vlan_priority 0     VLAN Priority     True
vlan_tag_id   50    VLAN Tag ID       True

All of them are on vlan ID 50.

Any idea?

---------- Post updated at 11:17 AM ---------- Previous update was at 11:05 AM ----------

Quote:
Originally Posted by johnf View Post
Can you run the following and paste the results here:


Code:
ls -l /tftpboot


Code:
lsnim -c machines

Then I will have a further look at it.
Sure, there you go:


Code:
testAIX1:/ > ls -l /tftpboot
total 34688
lrwxrwxrwx    1 root     system           19 Oct 26 09:57 xxx.xxx.xxx.98 -> /tftpboot/test_lpar
lrwxrwxrwx    1 root     system           19 Oct 26 09:57 xxx.xxx.xxx.98.boot -> /tftpboot/test_lpar
lrwxrwxrwx    1 root     system           24 Oct 26 09:57 xxx.xxx.xxx.98.info -> /tftpboot/test_lpar.info
lrwxrwxrwx    1 root     system           29 Oct 26 09:57 xxx.xxx.xxx.98.iplrecord -> /tftpboot/test_lpar.iplrecord
-rw-r--r--    1 root     system     17751040 Oct 25 16:37 AIX71_TL00_SP01_spot.chrp.64.ent
-rw-r--r--    1 root     system          512 Oct 25 16:37 AIX71_TL00_SP01_spot.iplrecord.ent
lrwxrwxrwx    1 root     system           42 Oct 26 09:57 test_lpar -> /tftpboot/AIX71_TL00_SP01_spot.chrp.64.ent
-rw-r--r--    1 root     system         1100 Oct 26 09:57 test_lpar.info
lrwxrwxrwx    1 root     system           44 Oct 26 09:57 test_lpar.iplrecord -> /tftpboot/AIX71_TL00_SP01_spot.iplrecord.ent


Code:
testAIX1:/ > lsnim -c machines
master        machines       master
testAIX2      machines       standalone
test_lpar     machines       standalone

Thank you.
Last edited by phobus; 10-26-2011 at 06:32 AM..
    #4  
Old 10-26-2011
Registered User
  
Join Date: May 2006
Location: England
Posts: 404
Thanks: 7
Thanked 7 Times in 7 Posts
Right the good news is the NIM server knows that the LPAR is there and ready to be installed. It also knows that certain resources are allocated to it.

Please excuse me if I am "Teaching my Granny how to suck eggs".

How did you try to boot the LPAR, from the NIM server? Or have you started the LPAR to SMS and setup the network boot configuration. This as you well know includes the IP address of the server, its subnet mask, and the IP address of the gateway. You can then PING the NIM master to make sure the network between the NIM master and client is open with no firewall in the way, which often happens.

Again if I am telling you things you already know please excuse me. The things I have outlined above are the usual reasons a NIM client will not boot from the NIM master.
Sponsored Links
    #5  
Old 10-26-2011
Registered User
  
Join Date: Sep 2009
Posts: 79
Thanks: 2
Thanked 1 Time in 1 Post
Quote:
Originally Posted by johnf View Post
Right the good news is the NIM server knows that the LPAR is there and ready to be installed. It also knows that certain resources are allocated to it.

Please excuse me if I am "Teaching my Granny how to suck eggs".

How did you try to boot the LPAR, from the NIM server? Or have you started the LPAR to SMS and setup the network boot configuration. This as you well know includes the IP address of the server, its subnet mask, and the IP address of the gateway. You can then PING the NIM master to make sure the network between the NIM master and client is open with no firewall in the way, which often happens.

Again if I am telling you things you already know please excuse me. The things I have outlined above are the usual reasons a NIM client will not boot from the NIM master.
Johnf, don't worry I do not get offended if you will tell me something I know already I'm happy if someone is trying to help me .

Every time I go to SMS and set up IPL and ping NIM server. But the thing is that I can ping NIM server but I can not use bootps for some reason.
I have contacted our network team to confirm, that ports 67 and 68 are not blocked to this particular managed system.
If they say that there are no ports blocked I will assign physical ethernet adapter to lpar to avoid VIOS and will see if it was caused by VIOS or not.

---------- Post updated at 12:31 PM ---------- Previous update was at 12:06 PM ----------

So I have tried to boot up via physical ethernet adapter from another NIM server and avoided VIO server and still I can not boot. I can ping the NIM server but not use bootps protocol.
Still waiting for network team to confirm if bootps ports are blocked or not.
Sponsored Links
Closed Thread

« AIX Booting problem | Aggregated Etherchannel »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Linux dhcp client boot process with packets traffic sudhirav Linux 2 08-12-2010 11:20 PM
One time network boot of Jumpstart x86 client chajo19 Solaris 7 10-08-2008 10:47 AM
NFS client Mount script after boot sv2xs Shell Programming and Scripting 0 06-27-2008 02:58 PM
NFS client subsystem hang up on boot Asheley Ryan UNIX for Dummies Questions & Answers 4 01-11-2008 07:09 PM
solaris boot problem boot error loading interpreter(misc/krtld) johncy_j Solaris 0 08-17-2005 08:15 AM



All times are GMT -4. The time now is 06:11 AM.

The UNIX and Linux Forums - Where There is a Shell There is a Way RSS Feeds - Contact Us - The UNIX and Linux Forums - Where There is a Shell There is a Way - Archive - Botnik - Top
SEO by vBSEO
The UNIX and Linux Forums Content Copyright ©1993-2013. All Rights Reserved.
Forum Operations by The UNIX and Linux Forums
Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited.