Bugzilla – Bug 7850
RFE would like support for static network instead of nwam config
Last modified: 2009-11-18 10:54:49 UTC
You need to log in before you can comment on or make changes to this bug.
Right now nwam is used for network config after install via AI. It would be useful if one could define the network config. Setting IP, netmask, hosts etc. eg, some environments may not want to have machines running nwam, in our benchmarking lab we don't use dhcp or any network nameservices to help minimise traffic to/from a SUT. That and we have our x86 machines boot order to be network then disk to automate installs. After install we remove the machine's entries from the dhcp server. In jumpstart the machine rshs back to the server via a finish script to do this.
As AI gets adopted throughout the enterprise environments, I suspect this request will be pretty high on the wish list.
The inability to set up nameservice information (NIS specifically) with automated installs is a major shortcoming in using automated installer within our labs. Pretty much every install right now of solaris ends up using NIS as nameservice, and that functionality is currently available in solaris jumpstart. Requiring users to manually set up nameservice isn't very automated. For wide spread installation, it would be a requirement to have automated installer set up nameservice.
I've discussed this topic a little in bug 10543. I was directed to comment here on it. Ideally, the "create-client" sub-command for installadm should take a flag to indicate static or nwam client configuration. Something like the following would probably be easiest on SA's and reduce any manual tinkering: $ pfexec installadm create-client -e 0:10:18:0f:28:26 -S myclient -I 192.168.1.3 -N 255.255.255.0 -D 192.168.1.1 -n 0906x86 -t /export/aiserver/osol-0906-ai-x86 The thinking here is that the clients end-state static IP configuration is passed to a client specific manifest that will get imported by the client upon bootup as a one-time process. Taking, -S <hostname> ,-I <IP> , -N <netmask> , -D <default route> as inputs. This could be made even more intelligent by doing an nslookup against the hostname provided by the -S option and auto-populating the IP, netmask, and default route based on nslookup output and /etc file entries. I will file a separate bug about the lack of name service details for AI clients.