I have to comment on this to say that multi-domain servers don't deal well with the source of the default address provided for root_server. As an example, if I tried to use the following even though one of the interfaces for the root_server/install server/dhcp server is 10.6.68.21 but the system is on another domain entirely, the install will choke.
wanboot.conf root_server=http://10.6.68.21:5555/cgi-bin/wanboot-cgi root_file=/export/home/images/ws_sparc_test/boot/boot_archive boot_file=/export/home/images/ws_sparc_test/platform/sun4v/wanboot ... 100 Mbps half duplex Link up <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete Wed Apr 29 17:41:07 wanboot info: root_server URL not on local subnet Wed Apr 29 17:41:07 wanboot crit: incomplete boot configuration Type 'go' to resume {0} ok I would have to go in and modify the 10.6.68.21 to the address/interface on the server on which the client system is on. Is there a way to clobber this value somewhere without requiring root access to modify the wanboot.conf file? I understand that root_server may be removed but either way the fix should help support the fix for 6182. On 04/15/09 14:42, Alok Aggarwal wrote: > > On Wed, 15 Apr 2009, Sarah Jelinek wrote: > >> >>>> >>> No, doesn't it mean only one default sparc service? Seems to me we >>> wouldn't override /etc/inetboot/wanboot.conf if users added a new >>> service, unless they specified it as the default. Don't we have a >>> provision for default in installadm now? >>> >>> So, if the user adds a service that is not default, they must do a >>> create-client to use that service. >>> >>> Is this doable? >> I guess my question is.. can we create a sparc service without having >> to edit /etc/netboot/wanboot.conf and then later get the data we need >> when a client is created to so we can create the client specific >> wanboot.conf. > > The three important attributes /etc/netboot/wanboot.conf > allows specification for are root_server, root_file and > boot_file. For example - > > root_server=http://10.6.68.21:5555/cgi-bin/wanboot-cgi > root_file=/export/home/images/ws_sparc_test/boot/boot_archive > boot_file=/export/home/images/ws_sparc_test/platform/sun4v/wanboot > > With the required arguments to create-client (service name > and imagepath), I think all of these can be ascertained. > > Alok > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss -- -Manuel ________________________________________________________________________ Manuel Nunes (ext. 84197) Manuel.Nunes at Sun.COM Quality Engineering Group Phone: +1 650 786 4197 Sun Microsystems, Inc. Fax: +1 650 786 7816 www.sun.com ________________________________________________________________________
