Jon Aimone wrote: > Hi, > > I think we solved it. I'm not certain when things changed. I know some > bugs concerning subnets in the installadm tools were addressed not > long ago. > > We had not upgraded our AI server since 09.06 until build 124, but I > did not try any services based on older AI images at that time, not > until today. > > The /etc/netboot directory was a mess with no "real" subnet > directories. Based on the logs from the webserver, my client was > requesting boot information specific to its subnet, but there was no > subnet directory... so it got the default which happened to be for > build 125... > > We added directories for the subnets with appropriate directories for > my client system and things are working much better now. The > /etc/netboot directory more closely resembles what's described in the > manual for how to set up wan boot. There may be some bus in that area (6182, 7115 and 7149). The installadm create-service command creates the network directory under /etc/netboot. If there are multiple interfaces or subnets, it may not add all the networks. If your case is not covered by these bugs, please add your problem and how you fixed with a workaround.
Thanks, Sundar > > Jon Aimone wrote: >> Hi, >> >> Ah. That directory is a collection of symlinks and conf files. From >> the behavior I'm seeing, wanboot is not finding the client specific >> files. >> >> Is there a way to get more information form the wanboot-cgi about >> which files it chose? A log file somewhere? >> >> Sundar Yamunachari wrote: >>> Jon Aimone wrote: >>>> Hi, >>>> >>>> We use static IP addresses, and I checked the DHCP macros. I have >>>> not changed them. They look the same as they did for build 124 and >>>> build 111. >>>> >>>> [ja123687] (18506)> dhtadm -P | grep 0100144F21ADA8 >>>> 0100144F21ADA8 Macro >>>> :Include=mpkpen-ai-1:BootSrvA=172.21.4.10:BootFile="http://172.21.4.10:5555/cgi-bin/wanboot-cgi": >>>> >>>> >>>> >>>> I'm not the one who created the services, so I don't have the text >>>> of the command executed. >>>> >>>> Before the service for 125 was created, I could select between >>>> build 111 and build 124. >>>> >>>> I don't know enough about wan boot configuration to know what to >>>> look at on the server. What configuration files would get changed >>>> by installing a new service? >>> WAN Boot files are created under /etc/netboot of the install server. >>> The default service configuration is available under >>> /etc/netboot/wanboot.conf. The service specific configuration will >>> be under /etc/netboot/<service_name> and the client specific >>> configuration under /etc/netboot/<network number>. >>> >>> - Sundar >>> >>>> >>>> Sundar Yamunachari wrote: >>>>> Jon Aimone wrote: >>>>>> Hi, >>>>>> >>>>>> If I have an AI server with multiple services, how do I choose >>>>>> which service will be used for my target system? >>>>>> >>>>>> I'd thought all I had to do was "create-client" specifying the >>>>>> service I desired. Is this not the case? >>>>> If you customized your client with a service, that client will be >>>>> using the image associated with that service. It shouldn't change >>>>> when you add a new service. >>>>>> >>>>>> I ask because when we added the 125 AI image to our server and >>>>>> created a service for it. Now my systems that had custom >>>>>> manifests using a service based on the 124 image all get the 125 >>>>>> miniroot. Is this the expected behavior? >>>>> It should not get 125 image. How your IP addresses are configured? >>>>> Are they static or dynamic? Check your DHCP server to see the DHCP >>>>> macros assigned to the IP addresses and what image/service >>>>> associated with the macro? Can you provide the commands you issued >>>>> to create the 124 and 125 services? >>>>> >>>>> Thanks, >>>>> Sundar >>>>>> >>>>>> _______________________________________________ >>>>>> caiman-discuss mailing list >>>>>> caiman-discuss at opensolaris.org >>>>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> caiman-discuss mailing list >>>> caiman-discuss at opensolaris.org >>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>> >>> >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
