On Sat, Sep 26, 2009 at 11:01:27PM -0700, sundar Yamunachari wrote: > John Levon wrote: > >I'm having much trouble setting up installadm to serve static DHCP from > >the same machine. I'm using 122 on the server, with the 123 AI ISO. > > > >1) when you use create-service with -i / -c, then dynamic allocation is > >immediately enabled. This is a major problem as a bunch of clients then > >grab the leases from the DHCP server. How am I supposed to get > >installadm to set up the DHCP server without it doing this? > > > If you setup DHCP server (using -i and -c) with installadm, it will > setup only dynamic addressing. If you want permanent IP addressing, > you have to manage the DHCP server on your own and should not > use -i and -c with installadm
This is a great shame (and not at all clear in the docs). The Sun DHCP server is incredibly painful to set up correctly by hand. Is there a plan to allow static DHCP configurations? > >There's no /etc/resolv.conf in the domU, and NIS isn't configured. > >SUNWfiles1_dhcptab has DNS info under the 'heaped' macro, but only NIS > >under > >the 10.6.70.0 network. But surely NIS should still work? > > > If the DNS is setup on the install server, the installadm will pick up > the information > and setup the DHCP macro with the name of the install server. For > example, the > install server 'install-test' will have the following macro: > > install-test Macro > :Timeserv=10.6.68.47:LeaseTim=604800:LeaseNeg:DNSdmain="sfbay.sun.com": > DNSserv=129.145.155.220 129.145.154.118 129.147.9.5:Include=Locale: I have something like this set up. It doesn't work. I get the dhcpinfo correctly in the domU, but no /etc/resolv.conf (until /usr is mounted). This is a little difficult to debug without /usr, so I'd appreciate some tips! Downloading solaris.zlib archive --2009-09-26 22:28:40-- http://heaped:5555//export/ai/123//solaris.zlib Resolving heaped... failed: node name or service name not known. wget: unable to resolve host address `heaped' FAILED ... root@:~# dhcpinfo DNSserv 129.145.155.220 129.145.154.118 129.147.9.5 -bash: /usr/bin/hostname: No such file or directory root@:~# cat /etc/resolv.conf cat: cannot open /etc/resolv.conf: No such file or directory -bash: /usr/bin/hostname: No such file or directory > >4) I've edited /export/ai/213/auto_install/*.xml to set auto-reboot to > >true (bad I know), but it's ignored: > > > >root at domu-224:~# grep reboot /tmp/install_log > ><AI Sep 25 18:30:21> Auto reboot disabled > > > Check whether the auto-boot is enabled on the > /tmp/ai_combined_manifest.xml on the > machine before rebooting the installed system. The manifest you edited > may not the > manifest the client is using to install the system. Where else are manifests stored? root at heaped:/export/ai/123/auto_install# ggrep -C1 reboot *.xml ai_manifest.xml- </ai_uninstall_packages> ai_manifest.xml: <ai_auto_reboot> ai_manifest.xml- true ai_manifest.xml: </ai_auto_reboot> ai_manifest.xml- </ai_manifest> ... default.xml- </ai_uninstall_packages> default.xml: <ai_auto_reboot> default.xml- true default.xml: </ai_auto_reboot> default.xml- </ai_manifest> And in the domU /tmp/ai_combined_manifest.xml: <ai_auto_reboot> false </ai_auto_reboot> thanks john
