Hi Jan,
Jan Setje-Eilers wrote: > Jan Damborsky wrote: >> Hi Mary, >> >> mary ding wrote: >>> Jan D. and Jan S: >>> >>> I realized that I had to specify the ipkg.sfbay IP to work around >>> the dns issues. >> >> DNS servers are provided by DHCP server - since we don't use >> DHCP in this scenario, DNS is not set up - we need to work out >> different mechanism how to provide AI client with list of DNS >> servers. One possibility is to pass this information in >> wanboot.conf file. > > The AI image could also simply re-dhcp itself as it's coming up. That > would seem to result in the _least_ divergence in code and practice. I am thinking there seems to be two scenarios as far as network configuration is concerned. [1] manual net-config strategy (no DHCP server available) ---------------------------------------------------------- In this case, user manually configures network in OBP or in wanboot prompt and AI has to manually bring up network as well - this is what is currently captured in http://defect.opensolaris.org/bz/show_bug.cgi?id=9549#c4 It currently seems to work on machines with wanboot support in OBP (network-boot-arguments variable is populated with network configuration and boot from net is initiated): {ok} setenv network-boot-arguments host-ip=... {ok} boot net as well as on machines without wanboot support in OBP (wanboot is loaded from media and network is configured from wanboot prompt): {ok} boot disk -F wanboot -o prompt ... boot> host-ip=... ... boot> go ... [2a] DHCP net-config strategy - OBP with wanboot support -------------------------------------------------------- This is currently the most common scenario supported in AI and works fine, user just initiates the whole process by {ok} boot net:dhcp [2b] DHCP net-config strategy - OBP without wanboot support ----------------------------------------------------------- wanboot is loaded from media and dhcp is used for network configuration in this scenario. It doesn't seem to work correctly at this point - Solaris doesn't bring up network interface. {ok} boot disk -F wanboot -o dhcp ... Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard OpenBoot 4.0, 2048 MB memory installed, Serial #52914889. Ethernet address 0:3:ba:27:6a:c9, Host ID: 83276ac9. Executing last command: boot disk -F wanboot -o dhcp Boot device: /pci at 1f,0/pci at 1/scsi at 8/disk at 0,0 File and args: -F wanboot -o dhcp <time unavailable> wanboot info: WAN boot messages->console <time unavailable> wanboot info: configuring /pci at 1f,0/pci at 1,1/network at c,1 <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot info: Default net-config-strategy: dhcp <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete ... SunOS Release 5.11 Version snv_117 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. strplumb: open /devices/pseudo/clone at 0:sd failed: 19 ... Preparing automated install image for use The AI image will be retrieved from /export/home/ai/images/ai-sparc-9026-117/ directory Downloading solaris.zlib archive --02:13:07-- http://192.168.100.2:5555/export/home/ai/images/ai-sparc-9026-117//solaris.zlib => `/tmp/solaris.zlib' Connecting to 192.168.100.2:5555... failed: Network is unreachable. FAILED Requesting System Maintenance Mode ... wanboot itself correctly deals with this situation (network is configured and boot archive is obtained from AI server), however Solaris itself doesn't bring up the network, as it assumes bootpath contains network device and fails to plumb the network interface, since bootpath refers to hard drive as wanboot was loaded from disk. This seems like an inconsistent behavior - do you think it might be considered as bug ? I am not very familiar with that part of code, but in general I assume that the result of network configuration should be the same as in [2a], since Solaris itself is booted from net via network interface configured by means of DHCP. In that case no special treatment from AI would be needed. Might this assumption be correct ? Thank you, Jan > > -jan > >> >>> >>> I had success installing the following system: >>> >>> line2-420r - this is the same as an ultra 80 >>> line2-sb2k - this is the Sun Blade 2000 >>> line2-280r >>> >>> >>> I had problem installing default for the following machine: >>> >>> linei-u5 - the system only had one 8 GB disk, I need to retry with >>> a custom manifest to work around bugid 7544 >>> >>> I will try more systems tomorrow and get more updates. >> >> Thank you very much ! >> Jan >
