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:
<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.
1.Commented out line in inetd.conf "bootps"
2. run
/usr/sbin/bootpd -s -d -d -d
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:
$ 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
$ 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
$ 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
$ 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 ----------
Sure, there you go:
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
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.