Jumpstart on Solaris 10 - things to start
bertieb...@gmail.com
successfully on Solaris 9 but never on Solaris 10.
I understand that system processes are a little different on 10 with
the introduction of services.
I've created /tftpboot directory, edited inetd.conf to allow tftp (and
then run inetconv). If I do inetadm now it does appear to have added
tftp to the bottom. Rebooted.
Should I be able to see the tftp and in.rarpd services using ps-aef
now. Or not?
Casper H.S. Dik
Not tftp, it is started by inetd when there's a call to tftp. You
can test whether it is enabled by using svcs:
% svcs '*tftp*'
STATE STIME FMRI
online Sep_23 svc:/network/tftp/udp6:default
Rarp should be run, but by enabling "rarpd":
svcadm enable rarp
en possibly also bootparams:
svcadm enable bootparams
Note that you can also use DHCP which I personally find easier and which
is required, IIRC, for x86 clients.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
bertieb...@gmail.com
Casper,
Thanks. It appears to be as easy as that.
Its actually a Sol9 sparc (single card machine) install that the
jumpstart server, a laptop, is going to be used for. We used to have
an old laptop running sol9 as the jumpstart but this is being replaced
with a newer model.
Though it would be an ideal time to upgrade the server to Sol10.
Getting the network card working wasnt easy though. What I did then
was tar copy the /jumpstart directory from my old Sol9 jumpstart
laptop to me new one,
Unfortunately, our application cards still need to be Sol 9.
bertieb...@gmail.com
new sol 10 one. Not sure if that was correct.
hume.sp...@bofh.ca
> then run inetconv). If I do inetadm now it does appear to have added
> tftp to the bottom. Rebooted.
Rebooting isn't really necessary.
> Should I be able to see the tftp and in.rarpd services using ps-aef
> now. Or not?
Not in.tftpd; you wouldn't see it under inetd, either. inetd handles the
port, and just fires off the services it manages as needed. inetadm (startd)
on Solaris works the same way. (As does inetd on any other Unix...)
To get in.rarpd running, you'll need to 'svcadm enable' network/rarp. Then
you should be able to see it running.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
YTC#1
> "BertieB...@gmail.com" <bertieb...@gmail.com> writes:
>
>> Trying to get Solaris 10 set up as a jumpstart server. Done it before
>> successfully on Solaris 9 but never on Solaris 10.
>
>> I understand that system processes are a little different on 10 with
>> the introduction of services.
>
>> I've created /tftpboot directory, edited inetd.conf to allow tftp (and
>> then run inetconv). If I do inetadm now it does appear to have added
>> tftp to the bottom. Rebooted.
>
>> Should I be able to see the tftp and in.rarpd services using ps-aef
>> now. Or not?
>
>
> Not tftp, it is started by inetd when there's a call to tftp. You
> can test whether it is enabled by using svcs:
>
> % svcs '*tftp*'
> STATE STIME FMRI
> online Sep_23 svc:/network/tftp/udp6:default
>
>
> Rarp should be run, but by enabling "rarpd":
>
> svcadm enable rarp
>
> en possibly also bootparams:
>
> svcadm enable bootparams
>
>
> Note that you can also use DHCP which I personally find easier and which
> is required, IIRC, for x86 clients.
>
Am I the only one who remembers to mention a Sun product that is part of
N1 (or xVMOC as it ios now) that is free to use ?
oh, yes, I am :-)
JET (JumpStart Enterprise Toolkit)
http://wikis.sun.com/display/JET
--
Bruce Porter
"The internet is a huge and diverse community and not every one is friendly"
http://www.ytc1.co.uk
There *is* an alternative! http://www.openoffice.org/
bertieb...@gmail.com
> Casper H.S. Dik wrote:
> > "BertieBigBol...@gmail.com" <bertiebigbol...@gmail.com> writes:
>
> >> Trying to get Solaris 10 set up as a jumpstart server. Done it before
> >> successfully on Solaris 9 but never on Solaris 10.
>
> >> I understand that system processes are a little different on 10 with
> >> the introduction of services.
>
> >> I've created /tftpboot directory, edited inetd.conf to allow tftp (and
> >> then run inetconv). If I do inetadm now it does appear to have added
> >> tftp to the bottom. Rebooted.
>
> >> Should I be able to see the tftp and in.rarpd services using ps-aef
> >> now. Or not?
>
> > Not tftp, it is started by inetd when there's a call to tftp. You
> > can test whether it is enabled by using svcs:
>
> > % svcs '*tftp*'
> > STATE STIME FMRI
> > online Sep_23 svc:/network/tftp/udp6:default
>
> > Rarp should be run, but by enabling "rarpd":
>
> > svcadm enable rarp
>
> > en possibly also bootparams:
>
> > svcadm enable bootparams
>
> > Note that you can also use DHCP which I personally find easier and which
> > is required, IIRC, for x86 clients.
>
> Am I the only one who remembers to mention a Sun product that is part of
> N1 (or xVMOC as it ios now) that is free to use ?
>
> oh, yes, I am :-)
>
>
> --
> Bruce Porter
>
> "The internet is a huge and diverse community and not every one is friendly"http://www.ytc1.co.uk
>
> - Show quoted text -
Hmmm. OK, Got bootparams, rarp and tftp/udp6 running but client is
timing out with waiting for rarp.... ?
Casper H.S. Dik
>Hmmm. OK, Got bootparams, rarp and tftp/udp6 running but client is
>timing out with waiting for rarp.... ?
Not using DHCP? Then you will need to put the systems name & ethernet
address in /etc/ethers (or whatever namneservice you use)
bertieb...@gmail.com
Yes. /etc/ethers entry has been added.
When I "boot - net install" from the client machine I get message
'link is not up' and then boot device not found.
Strangely I dont get an interface up/down message when I connect/
disconnect the lan cable?
bertieb...@gmail.com
Would DHCP be better? These are sparc based machines I'm
jumpstarting...
bertieb...@gmail.com
server. And it looks like the interface isnt even coming up.
Is it possible the interface works normally but wont support network
boot?
Richard B. Gilbert
Something is broken!! You may have a bad cable or a defective Ethernet
interface. Do you get "link lights" at both ends? It's customary to
have a little LED turn on when both ends of the cable are connected to
working interfaces.
bertieb...@gmail.com
wrote:
>
> - Show quoted text -
OK. New cable.
Now timing out with 'waiting for arp/rarp packet'. getting somewhere.
Doing a snoop on server I get:-
broadcast rarp c who is 0:3:ba:4:6:c ?
(0:3:ba:4:6:c being ethernet of client)
So its doing something. yes. entry in /etc/ethers for this....
YTC#1
Only if the network is active :-)
These days a lot more people are using DHCP for installation, especially
if their JumpStart server is doing both sparc and x86 (as PXE uses DHCP)
--
Bruce Porter
XJR1300SP, XJ900F, GSX750W, GSX250, Pegaso 650 Trail
POTM#1(KoTL), WUSS#1 , YTC#1(bar), OSOS#2(KoTL) , DS#3 , IbW#18 ,Apostle#8
YTC#1
> It looks like the client isnt even seeing the server as a network boot
> server. And it looks like the interface isnt even coming up.
>
If it won't come up, you will not get far.
What (HW) is the client ?
What is the server ?
What is the network setup ?
ie:- are you back to back or through a switch ?
> Is it possible the interface works normally but wont support network
> boot?
--
Bruce Porter
XJR1300SP, XJ900F, GSX750W, GSX250, Pegaso 650 Trail
POTM#1(KoTL), WUSS#1 , YTC#1(bar), OSOS#2(KoTL) , DS#3 , IbW#18 ,Apostle#8
bertieb...@gmail.com
Interface is up. The RARP broadcast message seems to indicate that no
boot server is responding to the RARP request for IP address....
Connected via crossover BTW.
YTC#1
> On Oct 6, 2:16 pm, YTC#1 <b...@ytc1-spambin.co.uk> wrote:
>> BertieBigBol...@gmail.com wrote:
>>> It looks like the client isnt even seeing the server as a network boot
>>> server. And it looks like the interface isnt even coming up.
>> If it won't come up, you will not get far.
>>
>> What (HW) is the client ?
>> What is the server ?
>> What is the network setup ?
>> ie:- are you back to back or through a switch ?
>>
>>> Is it possible the interface works normally but wont support network
>>> boot?
>
> Interface is up. The RARP broadcast message seems to indicate that no
> boot server is responding to the RARP request for IP address....
>
> Connected via crossover BTW.
Have a look at this troubleshooting guide
http://jet.maui.co.uk/wiki/index.php/Faq#Troubleshooting , it should
give some good tips.
If you plug the JumpStart serevr into a switch, can you get the network ok ?
I ask, as you seem to have a lot of issues with the network driver.
I think it would be easier if you used a different server with a
recognised driver/hardware.
Or, use another OS, add VirtualBox and build your JumpStart server
inside that.