Load server and osprovisioning

Question

All,
I'm attempting to do an osprovision of Solaris to a T2000. The equivelant command that get's issued is as follows.
load server <discovered server name> osprofile Sol10R4_T2000 networktype static ip xx.xx.xx.xx hostname <hostname after install>
I've tried a number of different iterations and get the same results everytime.
The managed system starts to boot the "jusmpstart" process ( after all, that's what's really going on ) and reads the sysidcfg file correctly. When it attempts to find a matching rule in the rules.ok file, I get....
Warning: Could not find matching rule in rules.ok
and it kicks out into a manual install process.
The load server command is what sets up the sysidcfg, rules, rules.ok and the assocaited files to achieve the install, but based on what I had gotten use to with the old jumpstart mechanism, I would expect an entry in /etc/bootparams and /etc/ethers but these files never get created.
In the "old days", these were created by running the add_install_client script, but I'm not sure if the load server command from the n1sh shell is suppose to run this script itself, or if these 2 files are even required using the N1 System Manager mechanism for provisioning a system
Any help would be appreciated,
Dan
Message was edited by:
cgitunix

Answer 1

ok - I love answering my own questions ( lol ) but here it goes.
#1 Unless the managed server you are trying to provision has the ability ( and you set it right ) to resolve it's own hostname, you still have to put the entry in the local /etc/hosts file on the N1 System Manager Server.
After all - this is merely an updated variant of jumpstart. You can either call it SUNWjet or AllStart - take your pick......
Also, even though the load server command takes the hostname parameter and uses that entry to populate the rules file and the sysidcfg file, it is not suppose to be used in this command....
The true "bootable" entry would be the actual server name.. ie
load server <servername> hostname <Rservername> will populate the 2 files with Rservername but try to match servername.
I've placed a call with support on it and they have generated a RFE/BUG report on the item.
When you attempt to provision from the webconsole wizard, the hostname entry is disabled for a Solaris install....
So - rename the server entry to a valid <servername> which is the same as the <hostname> and don't use the <hostname> parameter in the load command. This will cleanly boot and match the rule correctly
Dan