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? I did: installadm create-service -n 123 -i 10.6.71.224 -c 1 -s /export/netimage/opensolaris/123/osol-1002-123-ai-x86.iso /export/ai/123/ 2) I created a client: installadm create-client -e 00:16:3e:1b:e8:18 -n 123 -t /export/ai/123/ which put in SUNWfiles1_10_6_70_0: 10.6.71.224|00|00|10.6.70.64|4294967295|993325192811905030|dhcp_macro_123| This doesn't work properly either: it will happily hand out this address to any client. So I got this after a while: 10.6.71.224|01001B245BD344|00|10.6.70.64|1254015807|8460574849968898050|dhcp_macro_123| It needs to write this: 10.6.71.224|0100163E1BE818|03|10.6.70.64|4294967295|993325192811905030|dhcp_macro_123| Note the MAC address, and the flags field (PERMANENT+MANUAL). The manual flag is necessary - the Solaris DHCP server is broken in this respect. 3) After all this, I get DHCP working, but the guest still can't access the server HTTP address (it can't resolve heaped.sfbay, heaped.sfbay.sun.com etc.). I had to use an IP address (I'm AI installing a domU). 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? 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 How come? regards john
