SUMMARY: Problems setting up solaris 10 server as jumpstart server

I didn't see this summary post, so I'm sending again.


Many thanks to the several people who replied and hit the answer on
the head.  Here is the answer......

running 'add_install_client' will put the line in inetd.conf, but it
will not run 'inetconv'.

With sun's new SMF stuff /etc/inetd.conf is no longer used in place of
xml files instead.  inetconv is the utility to convert these files.
to see what's enabled use svcs -a

Many thanks

Ryan

---------- Forwarded message ----------
From: Ryan Mcewan <mcmeister@gmail.com>
Date: May 10, 2005 3:05 PM
Subject: Problems setting up solaris 10 server as jumpstart server
To: sunmanagers@sunmanagers.org

I have a solaris 10 server that I am trying to setup as a jumpstart
server.  Initially I tried setting it up as a solaris 8 jumpstart
server.  When that didn't work, I also tried solaris 10.  I am very
familiar with setting these up on solaris 8 and 9, however there are
subtle differences that I cannot seem to be able to figure out in
Solaris 10.  I have ran setup_install_server and add_install_client
correctly I believe.  I have also enabled the following services via
svcadm

svcadm enable svc:/network/rpc/bootparams:default
svcadm enable svc:/network/rarp:default
svcadm enable svc:/network/nfs/cbd:default

Tftp also appears to be enabled in /etc/inetd.conf.

When I try to run boot net - install from the client it says the boot
device and args: - install

and then it just hangs forever.  I've tried rebooting the server after
doing all of this to no avail.  What am I missing in solaris 10 that
is different from the rest?

Help is appreciated.

Thanks

Ryan
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers