Steffen and Clay:
If you use osol_111b as your AI server, the sparc 111b AI client no
longer need to have the BootFile any more.
installadm create-client -e 0:14:4f:47:c5:84 -t
/export/home/images/osol-0906-111b-ai-sparc -n
osol-0906-111b-ai-sparc-osol-inst
Setting up SPARC client...
Creating SPARC configuration file
Detected that DHCP is not set up on this server.
If not already configured, please create a DHCP macro
named 0100144F47C584 with:
Boot server IP (BootSrvA) : 10.6.68.21
Boot file (BootFile) : http://10.6.68.21:5555/cgi-bin/wanboot-cgi
If you are running Sun's DHCP server, use the following
command to add the DHCP macro, 0100144F47C584:
/usr/sbin/dhtadm -g -A -m 0100144F47C584 -d
:BootSrvA=10.6.68.21:BootFile=\"http://10.6.68.21:5555/cgi-bin/wanboot-cgi\":
Note: Be sure to assign client IP address(es) if needed
(e.g., if running Sun's DHCP server, run pntadm(1M)).
Steffen Weiberle wrote:
> On 05/12/09 17:15, Clay Baenziger wrote:
>> Hi Steffen,
>> I would add it to a network macro if you want every system to get
>> it. Otherwise, just a generic macro which you assign to IP addresses
>> should be okay too. Lastly, a platform specific macro would work well
>> to ensure SPARC's get SPARC boot files and X86's get X86 specific boot
>> files.
>>
>> Thank you,
>> Clay
>
> Thanks, Clay. This helped point me in the right direction.
>
> This is to update on the steps I had to take to get Solaris 10 DHCP
> server to deliver the necessary options to allow a SPARC system to
> AutoInstall.
>
> The 'dhcp_macro_0906sparc' had been created. [1]
>
> I chose to use the 'ventnor' macro since that looked the easiest, and I
> did not need one for a specific client.
>
> The "Administering DHCP" in the "System Administration: IP Services"
> guide at
> http://docs.sun.com/app/docs/doc/816-4554/dhcp-admin-9?l=en&a=view has a
> section "How to Add Options to a DHCP Macro" which included the
> explanation on the "Include" value at an Option Name. That allows the
> inclusion of another macro, similar to the way the 'ventnor' macro
> already included the 'Locale' macro. Once I did that (I used the GUI,
> although there is a dhtadm(1M) way as well), everything worked. Only
> restriction is that the macro can only be 255 bytes long, so it limits
> the number of options or includes.
>
> Steffen
>
> [1]. Separately, I don't understand yet why the installadm on the IA
> server running 111a instructions did not work. Maybe there are
> differences between the server on S10 and OpenSolaris. Also, based on
> the results above, creating the macro is not sufficient. I hope to get a
> chance to try it again.
>
>
> $ pfexec installadm create-service -n 0906sparc -s
> /export/iso/opensolaris/2009.06/111a/osol-0906-111a-ai-sparc.iso
> /export/aiserver/osol-0906-ai-sparc
> Setting up the target image at /export/aiserver/osol-0906-ai-sparc ...
> Registering the service 0906sparc._OSInstall._tcp.local
>
> Detected that DHCP is not set up on this server.
> If not already configured, please create a DHCP macro
> named dhcp_macro_0906sparc with:
> Boot server IP (BootSrvA) : 129.154.53.138
> Boot file (BootFile) :
> http://129.154.53.138:5555/cgi-bin/wanboot-cgi
> Root path (Rootpath) :
> http://129.154.53.138:5555/export/aiserver/osol-0906-ai-sparc
> If you are running Sun's DHCP server, use the following
> command to add the DHCP macro, dhcp_macro_0906sparc:
> /usr/sbin/dhtadm -g -A -m dhcp_macro_0906sparc -d
> :BootSrvA=129.154.53.138:BootFile=\"http://129.154.53.138:5555/cgi-bin/wanboot-cgi\":Rootpath=\"http://129.154.53.138:5555/export/aiserver/osol-0906-ai-sparc\":
>
>
>
> Note: Be sure to assign client IP address(es) if needed
> (e.g., if running Sun's DHCP server, run pntadm(1M)).
> Service discovery fallback mechanism set up
> Creating SPARC configuration file
>
>
>>
>> On Tue, 12 May 2009, Steffen Weiberle wrote:
>>
>>> On 05/12/09 16:31, Clay Baenziger wrote:
>>>> Hi Steffen,
>>>> [Sensitive data cut out] I don't see a BootFile response in the
>>>> offer at all, which will cause the SPARC to try TFTP. For an
>>>> example, my macro contains the following entries. You should see
>>>> something similar in your offer for AI to work:
>>>> BootSrvA=172.20.24.78
>>>> Rootpath="http://172.20.24.78:5555/var/ai/clay_ai_sparc";
>>>> BootFile="http://172.20.24.78:5555/cgi-bin/wanboot-cgi";
>>>>
>>>> If you're running the Solaris DHCP server, looking at which macros
>>>> are assigned to IP addresses via "pntadm -P <network IP>", and what
>>>> macro definitions look like via "dhtadm -P" may provide some insight.
>>>>
>>>> Thank you,
>>>> Clay
>>>
>>> I did all that stuff, correclty, I think. Had to do it by hand as the
>>> generated output had a syntax error.
>>>
>>> # dhtadm -P
>>> Name Type Value
>>> ==================================================
>>> dhcp_macro_0906sparc Macro
>>> :BootSrvA=129.154.53.138:BootFile="http://192.164.53.138:5555/cgi-bin/wanboot-cgi":Rootpath="http://192.164.53.138:5555/export/aiserver/osol-0906-ai-sparc":
>>>
>>>
>>> 10.1.14.128 Macro
>>> :Subnet=255.255.255.192:Router=10.1.14.130:Broadcst=10.1.14.191:
>>> ventnor Macro
>>> :Include=Locale:Timeserv=10.1.14.171:LeaseTim=7200:LeaseNeg:DNSdmain="stw.east.sun.com":DNSserv=10.1.14.130:
>>>
>>>
>>> Locale Macro :UTCoffst=-18000:
>>>
>>> Oh, I see the problem. I did not match the macro.
>>>
>>> Should I have added this to the main macro (in my case ventnor, which
>>> is the system name) or to the 10.1.14.128 macro? I created a new macro.
>>>
>>> Steffen
>>>
>>>>
>>>> On Tue, 12 May 2009, Steffen Weiberle wrote:
>>>>
>>>>> On 05/12/09 15:40, Clay Baenziger wrote:
>>>>>> Hi Steffen,
>>>>>> The snoop output of the DHCPRESPONSE would be useful. In
>>>>>> particular I suspect you are receiving a bootfile record which is
>>>>>> not of the form "http://<blah>" in which case the OBP will try
>>>>>> TFTP instead of HTTP.
>>>>>> Thank you,
>>>>>> Clay
>>>
>>>
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
