> Hello, > > my dhcp Server has the following info > dhtadm -P |grep "SjumpsCF" > edvadm3 Macro > > SrootPTH=/dhcp/OS_sol-nv-b96-sparc/Solaris_11/Tools/Bo > ot:SinstPTH=/dhcp/OS_sol-nv-b96-sparc:SrootIP4=172.16. > 64.1:SrootNM=172.16.64.1:SinstIP4=172.16.64.1:SinstNM= > 172.16.64.1:SjumpsCF="172.16.64.1:/opt/SUNWjet":Ssysid > CF="172.16.64.1:/opt/SUNWjet/Clients/edvadm3":BootSrvA > =172.16.64.1:BootFile=0100144F486CAA: > > SjumpsCF Symbol > Vendor=SUNW.Ultra-5_10 SUNW.Ultra-30 > SUNW.Sun-Blade-1000 SUNW.Ultra-80 SUNW.Ultra-60 > SUNW.UltraSPARC-IIi-cEngine SUNW.UltraAX-i2 > SUNW.Sun-Fire-T1000 SUNW.i86pc,14,ASCII,1,0
It appears to be correct. And you included the "SUNW.`uname -i`" for the system as well, I take it? Personally, I still don't really get what that listing of "SUNW.`uname -`" really means to the DHCP server or the client. If someone could answer that, that'd be really appreciated. > I can jumpstart all Solaris 9 an Solaris 10 versions > and > also snv_79b. > Then I tried snv_90 and snv_95, snv_96 and all the > version had the problem. > > It is a SPARC platform. NO PXE! I realized that after I answered your previous post. Your posts are kind of structured "backwards", for lack of a better term to describe it. Anyways, I was successful in DHCP booting a 220R last week, unfortunately no OpenSolaris. Perhaps I'll give it a shot this week and see how I fare. If I do, I'll let you know what the results were. No promises though, I don't know if I'm going to have the time to do it. > I'm looking for information, documents for this new > boot architecture for debugging my problem. Start here: http://www.opensolaris.org/os/community/on/flag-days/ http://dlc.sun.com/osol/on/downloads/ Good luck. You'll need it. -- This message posted from opensolaris.org
