From: peter (elveros@gmail.com)
Date: Tue Oct 03 2006 - 19:53:59 EDT
i can now categorically confirm that it was DHCP lease expiry that was
causing the problem.
only the default expiry time (3600 sec) was being sent with the lease.
i included a macro
sepcifying a 172800 sec (2 day) expiry time and the jumpstart install
completed successfully.
so, for some reason, during the jumpstart, solaris 9 will not renew
it's lease, it just sits there with
fingers in ears and sulks.
solaris 10 obviously _does_ renew, since it was able to complete.
mystery solved, anyway.... something to file away for the future...
snoop showed nothing after failure. nothing at all. NFS traffic just
stopped. there were no packets at all being received at the NFS/DHCP
server
p
On 03/10/06, peter <elveros@gmail.com> wrote:
> hi folks,
>
> i have (open)solaris 11 build 44 (x86) acting as a jumpstart server
> for some sparc
> systems (v120, v240). i am jumpstarting solaris 9 (5/05)
>
> with the small jumpstart config i normally use (<1GB) the installation
> has worked fine.
>
> with larger package sets (eg SUNWCall & SUNWCprog) the NFS connection is failing
> part-way through installation.
>
> after installing about 800MB, the jumpstart process stops with
> "NFS server not responding, still trying"
>
> i have tried:
>
> - 2 different jumpstart servers (one IBM PC, one HP DL380 server)
> - 2 different client systems (v240, v120)
>
>
> jumpstarting solaris 10 *works* successfully
>
>
> any suggestiosn on what might be happening here? do i have some
> bizarre NFS versioning getting in the way?
>
> tia
_______________________________________________
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:40:55 EDT