Hi Kyle, looking at the documentation "Solaris Express Installation Guide: Network-Based Installations" available at http://docs.sun.com/app/docs/doc/819-2394
it seems that installer should support setting NIS domain name and IP address of NIS server from DHCP parameters. According to the table 3-3 - "Values for Standard DHCP Options" NISdmain and NISservs should do the job. But when searching in the Nevada code, it seems that the only DHCP values relating to naming services which are being processed for now are DNSdmain, DNSserv for setting DNS. Since to tell the truth, I don't know if/when/why support for setting NIS parameters by DHCP was dropped, I am CCing Sarah and Sundar who might be able to provide you with more information with respect to this. Best regards, Jan Kyle McDonald wrote: > Kyle McDonald wrote: > >> I've done this in the past with RARP/BootParams. >> >> I have the locale map, and 'timehost' in NIS. >> >> But the boot process with DHCP doesn't seem to be able to find the NIS >> domain and server. What am I missing? >> >> I add the subnet to the DHCP server with: >> >> dhcpconfig -N 172.30.170.0 -y Engineering.NIS -a 172.30.170.21 -m >> 255.255.255.0 -t 172.30.170.254 >> >> The values show up in the Macros in dhcpmgr. >> >> Running snoop during boot, shows that the bootparams call is still being >> attempted, but failing. >> >> > I've attached the snoop runs, showing the network activity during the > install. > > The DHCP responses appear to contain the NIS Domain name, but don't > appear to contain the NIS Server IP. > (Either way, I would think getting the NIS Domain would cause it to > broadcast for the Server?) > > Is SysIDCfg, and BootParams the only supported way of specifying a > Nameservice in NV? > I know DHCP support for other JS parameters was dropped a while back, > but was the Nameservice one of these? > > Either way, from the Snoop output, it appears the BootParams is still > being attempted, so I guess my only options are configure NS info in > BootParams, or in SysIDCfg? > > I hat putting anymore than I have to in SysIDCfg. And if I'm going to > run BOotParams, I may as well put everything in it that I had hoped to > put in DHCP, but ended up having to stick in the GRUB menu.lst instead. > It certainly would be easier to not have a separate menu.lst for every > rev of NV I have available. > > On the otherhand haveing to configure every host in both DHCP and > BootParams seems like a pain. > > I know it's been heard before, but I'm *really* missing the Jumpstart > DHCP option support. > > -Kyle > > > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-discuss >
