Summary: Jumpstart boot server issues on second network interface .

[Tim Moran]

Thanks for the immediate feedback, got me up a going already!

The issue is that in.rarpd -a runs at boot time (/etc/rc3.d/S15nfs.server).
When the boot server was booted, the interface didn't exist (I brought it up
later).

Running in.rarpd -a again made the world happy.

Thanks again.
Tim

>  -----Original Message-----
> From: 	Tim Moran  
> Sent:	Tuesday, May 07, 2002 2:07 PM
> To:	'sunmanagers at sunmanagers.org'
> Subject:	Jumpstart boot server issues on second network interface.
> 
> I have a functioning boot server (that is, I've successfully jumpstarted
> servers using hme0) that I am attempting to use the second interface, for
> a different network.
> 
> I have brought up the interface and it is functioning well, I've added an
> entry in /etc/hosts and /etc/hostname.hme1, etc. The add_install_client
> accepts the arguments, and /etc/bootparams,  /etc/ethers and /etc/hosts
> look good, etc.
> 
> Snooping the second interface (snoop -d hme1) you can see the RARP go by,
> but the boot server never responds. I've removed and re-added the client
> multiple times, no response on hme0 either (that is, the boot server does
> not attempt to respond to the hme1 RARP on hme0).
> 
> Any thoughts on why the second interface would not work for a boot server?
> 
> Tim Moran
> tmoran at shutterfly.com