Sun Fire V210 stalling on Jump Start install at NFS

Hi,

I recently purchased two brand new (open boxed) Sun Fire V210's. One is 
a dual CPU @1GHz with 8GB RAM and the other is single CPU @1.36GHz with 
8GB RAM for lab use at home.

I have setup a jump start server on an old laptop running Fedora 17 
following this guide:

http://hintshop.ludvig.co.nz/show/solaris-jumpstart-linux-server/


I intend for one of the servers to be a Debian Linux Application server 
while the other should be a Solaris 10 system running Oracle VDI and 
connected to my Sun Ray 1.


Since I previously didn't have any experience with Jump Start servers I 
followed the steps in the guides closely and decided to start with a 
Solaris 10 u10 SPARC install initially.

Currently my ethers file reads:

# cat /etc/ethers
0:3:ba:9c:53:55 Sol10

0:14:4f:5d:1e:7e Debian

The hosts file is as such:

192.168.140.2 boot

192.168.140.220 Sol10

192.168.140.230 Debian

...with 192.168.140.2 system being the Jump Start server.



I have tried to get Solaris 10 installed on either of the machines and 
they go as far as downloaded the HEX boot file from the TFTP portion of 
the Jump Start box.

This is the output from the Sun Fire with: 'boot net -v -- nowin' 
command issued:

100 Mbps full duplex  Link up
Using RARP/BOOTPARAMS...

Requesting Internet address for 0:14:4f:5d:1e:7e
Internet address is: 192.168.140.230


Here is the log from the server:


Sep 14 07:44:30 boot rarpd[1798]: link lo
Sep 14 07:44:30 boot rarpd[1798]:   addr 127.0.0.1/8 on lo
Sep 14 07:44:30 boot rarpd[1798]: link em1
Sep 14 07:44:30 boot rarpd[1798]:   addr 192.168.140.2/24 on em1
Sep 14 08:08:17 boot rarpd[1798]: RARP request from 0 on em1
Sep 14 08:08:17 boot rarpd[1798]: RARP response to 0 192.168.140.230 on em1
Sep 14 08:08:17 boot in.tftpd[2274]: RRQ from 192.168.140.230 filename 
C0A88CE6
Sep 14 08:09:23 boot rarpd[1798]: RARP request from 0 on em1
Sep 14 08:09:23 boot rarpd[1798]: RARP response to 0 192.168.140.230 on em1



It looks like everything goes well up until the NFS part, after that the 
system hangs. Here is the export:

/data/jumpstart
<world>(ro,wdelay,crossmnt,no_root_squash,no_subtree_check,fsid=0)

I can remotely mount the NFS portion on a Linux box, and it shows me:

boot       installer                         platform
Copyright  Offer_to_Provide_Source_Code.txt  Solaris_10

Under the mount directory eg. /mnt


Using Jnettop to track from the server side, the Sun Fire V210 is 
broadcasting a request to port 111:

Debian <-> 255.255.255.255
   192.168.140.230      569    UDP   2555.255.255.255    111 <transfer 
rates omitted>


Checking the netstat -uap of my Fedora box (jump start server) port 111 
is being used by NFS on IPv6 while IPv4 is using a different port.... 2049




Has anybody managed to get Solaris 10 installed while using a Linux jump 
start server?


I have seen that various people have struggled with Fedora in this 
instance so I'm wondering if it's the OS - that NFSv4 might be catching 
things out or could it be something else?


Unfortunately there isn't much information on the net regarding building 
jump start boxes and I've searched high and low and found max 7 sights 
with good illustrations on configuration on server and client side 
however, all are quite old and out of date.

Should I perhaps install Sol10u10 on my old Netra T105 with CDROM and 
attempt to set it up as a jump start box??


It seems easier due to various scripts that can be run to check that 
things are setup appropriately?


Could anybody give me a hand?


Regards,


Kaya