From: sunmanager@gmxtechnologies.com
Date: Sun Jan 22 2006 - 03:39:19 EST
First of all, many thanks to those who responded so rapidly to my
problem getting the correct device string to boot off of the qfe0 device.
I'll work up a summary and shoot it out as soon as I can.
I've managed to get *that* box up and upgraded to Solaris 9 via
Jumpstart (yay!), so, now I'm stuck on the next 2.
This problem is something I've not seen before. Normally, when I see
the "Timeout waiting for ARP/RARP packet" messages, there's some
disconnect between the client and the world, but in this case, I *see*
the ARP request on the jumpstart server, but the jumpstart server just
ignores it!
I've tried adding a static ARP entry on the jumpstart server, no luck.
I've double checked the /etc/ethers and /etc/bootparams files, and
removed and add_install_client several times.
I can snoop the interface and see the ARP request come broadcast by, but
the jumpstart server does not respond at all. I also made sure that the
ethernet address being ARPd is the one in /etc/ethers.
The only thing that I can think of is that when the jumpstart server was
built, the 2nd interface (dmfe1) was not plumbed, and that interface is
on the network with these other 2 clients. I've looked through
everything I can think of to see if the services that should respond to
the ARPs and perform the jumpstart duties are somehow only active/tied
to dmfe0, but I can't find it.
I'm at a loss for ideas at this point.
Thanks!
Sam
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:38:39 EDT