Quick checks:
Are you running either a tftpd or have the tftp service available in inetd?
Ditto for dhcp or bootp?
/etc/ethers, /etc/hostname set up correctly with your client settings?
Have you run setup_install_server or something similar on the blade100?
If those are all ok, you can look further by doing the following:
Run a packet sniffer (tcpdump or snoop for examples) on your blade100 looking for ARP and RARP packets (you only need one but I keep forgetting which one's which
).
Try to boot the Ultra1 on the network and watch the dump output. You should see the Ultra1 sending (R)ARP requests onto the local network.
If you see these, check the MAC matches what you have in your dhcp/bootp ethernet config (generally this is /etc/ethers on solaris).
If you have the right MAC, try looking to see if your jumpsart server (the Blade100) is replying correctly (again via tcpdump or snoop).
If that's working right, move on to the tftp step (where it passes a kernel across to the Ultra1) and repeat the process (ie more packet sniffing but looking for the next stage in the boot process).
If that works, you then look for NFS traffic indicating where it's looking for the OS image.
Lastly the NFS traffic to find the install media.