Hi Sundar,
Sundar Yamunachari wrote:
> Jan Damborsky wrote:
>> Hi Mike,
>>
>>
>> Mike Gerdts wrote:
>>> On Mon, Jun 15, 2009 at 7:56 AM, Peter
>>> Tribble<peter.tribble at gmail.com> wrote:
>>>> I've been trying to test AI, without much success.
>>>>
>>>> I have a sparc client - a SunBlade 1500. I've set up a spare x86
>>>> desktop with
>>>> 2009.06 as the AI server.
>>>>
>>>> So I boot the client with net:dhcp, and discover that it's time to get
>>>> a cup of coffee.
>>>
>>> Seems kinda odd (and a show-stopper) that wanboot now requires dhcp.
>>> I've been meaning to ask about this for a while.
>>
>> Looking at the documentation, it seems that in case of wanboot,
>> client can boot
>> in following ways:
>> http://docs.sun.com/app/docs/doc/817-5504/6mkv4nh5m?a=view
>>
>> [1] Boot from the network by setting network interface variables in
>> the Open Boot PROM (OBP).
>> [2] Boot from the network with the DHCP option
>> [3] Boot from a local CD-ROM
>>
>> In 2009.06 version of AI, only [2] is supported. That said, as far as
>> I am aware of,
>> support for [3] is currently being looked at.
>> (Sundar, please feel free to correct me if I am not correct in this
>> point).
> The wanboot program doesn't export wanboot parameters (either from
> wanboot.conf or entered in the OBP prompt) and AI doesn't have access
> to the network variables to set the network during the boot. There is
> a bug filed against wanboot to export the wanboot configuration so
> that AI can work with booting from cdrom and disk.
It seems there might be two separate issues related to this problem.
[A] Making wanboot.conf file available to the client
----------------------------------------------------
I think this problem was resolved by fix for bug 8130. For now the only
information specific to AI which AI client obtains from DHCP server is
'BootFile' which is URL to wanboot-cgi script. Everything else is determined
from wanboot.conf file which is made available to the AI client
as /etc/netboot/wanboot.conf during boot process - from bug report:
...
During wanboot process, wanboot.conf along with other files is bundled
as HSFS filesystem and provided by kernel as /devices/ramdisk-bootfs:a block
device which we can mount:
...
BOOTFS_DISK="/devices/ramdisk-bootfs:a"
if [ -b "$BOOTFS_DISK" ] ; then
mount -r -F hsfs "$BOOTFS_DISK" /etc/netboot > /dev/null 2>&1
...
Then we have wanboot.conf available in /etc/netboot/ directory in microroot
and we could determine location of solaris*.zlib archives by inspecting
'root_file' and 'root_server' options - those are created by installadm(1M)
in following format:
...
[B] Configuring network interface
---------------------------------
I have investigated that for scenario [1] all necessary network parameters
are being passed to kernel:
# prtconv -vp
...
client-id: 010003ba.fb20c1
subnet-mask: '255.255.255.0'
router-ip: '192.168.100.1'
host-ip: '192.168.100.143'
hostname: 'cynura'
network-boot-file: 'http://192.168.100.2:5555/cgi-bin/wanboot-cgi'
net-config-strategy: 'manual'
bootargs: 00
bootpath: '/pci at 1f,700000/network at 2'
...
And legacy installer can extract them using 'netbootinfo' CLI, e.g.
# /usr/lib/inet/wanboot/netbootinfo net-config-strategy
manual
# /usr/lib/inet/wanboot/netbootinfo host-ip
192.168.100.143
I have verified that the same approach works for AI client in scenario [1] -
filed bug 9549 for this issue and captured the procedure there.
I am wondering if the same approach might address also scenario [3] - booting
wanboot from media (CDROM, disk).
Thank you,
Jan
