Comments on: Debugging problems with Solaris in.dhcpd vendor options

By: Marcel

Marcel — Mon, 14 Mar 2011 15:26:23 +0000

Thank you for this very useful blog entry. So i find out a problem with the identifier of the new T3-1. The command uname -i says sun4v, but with snoop i see the real name ORCL.SPARC-T3-1.

By: Chris

Chris — Tue, 23 Mar 2010 16:10:09 +0000

Thanks, it took me the better part of the day to solve this issue on a T1000. Cheers

By: Mark

Mark — Tue, 31 Mar 2009 08:16:28 +0000

Thanks heaps for posting this! While I was well familiar with setting up non-DHCP jumpstarts, I’m now managing DHCP jumpstarts from a setup built by a contractor. So far, I’d only needed to jumpstart Ultra 45 workstations (without any problems), and was stumped why I couldn’t similarly jumpstart a SunBlade 2500 with Solaris 10 from the same jumpstart server. After all, Client Class Identifiers didn’t require specifying under non-DHCP jumpstart, and the need to do so under DHCP isn’t particularly obvious from a quick glance at the DHCP GUI’s tabbed pages.

This help turned an otherwise mediocre day at work into a good day! :-)

By: DarkPower

DarkPower — Thu, 05 Feb 2009 22:04:30 +0000

Thanks you for the tip !!!
Its solves my problem ^^ about the T5240 :D

By: Andy

Andy — Thu, 22 Jan 2009 14:36:34 +0000

Thanks a lot, I had the same problem with T5140, which SUN claims as SUNW.SPARC-Enterprise-T5140 but CCI is SUNW.T5140.
You just made my day man. MANY THANKS !!!

By: Serkan ÖKTER

Serkan ÖKTER — Thu, 18 Oct 2007 08:46:38 +0000

Thanks for your helpful information regarding Solaris 10 Net install on Sparc based Systems. However where can I find DHCP vendor Parameter Codes ? Because, T1000′ take the parameter codes, it can’t handle the name of parameters from DHCP macro.