Article: 61537 of comp.sys.sun.hardware
Sender: Thomas Nau <nau@frago.rz.uni-ulm.de>
Message-ID: <3a9e1be3@news.uni-ulm.de>
From: Thomas Nau <Thomas.Nau@rz.uni-ulm.de>
Subject: SunRay hints
Newsgroups: comp.unix.solaris,comp.sys.sun.hardware
Organization: University of Ulm, Germany
User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (SunOS/5.8 (sun4u))
NNTP-Posting-Host: frago.rz.uni-ulm.de
Date: 1 Mar 2001 10:52:36 +0100
X-Trace: 1 Mar 2001 10:52:36 +0100, frago.rz.uni-ulm.de
Lines: 74
Path: news.meer.net!sea-read.news.verio.net!dfw-artgen.news.verio.net!dfw-peer.news.verio.net!news.verio.net!newsfeed.mathworks.com!dispose.news.demon.net!demon!colt.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!feed.news.nacamar.de!rz.uni-karlsruhe.de!news.uni-ulm.de!not-for-mail
Xref: news.meer.net comp.unix.solaris:201494 comp.sys.sun.hardware:61537

Here's some information about some problems we ran into setting up SunRays
in a non standard fashion.

1) we are using the ISC DHCP server to serve a bunch of wireless
   clients. Adding Rays to the server required at least version 3*
   because of the vendor specific stuff. Beside that you may want to add 

	class "SunRayWorkstations" {
		match if option vendor-class-identifier = "SUNW.NewT.SUNW" ;
		default-lease-time 86400;
	}

	if option vendor-class-identifier = "SUNW.NewT.SUNW" {
		vendor-option-space SunRay;
	}

	option space SunRay;
	option SunRay.AuthSrvr code 21 = ip-address;
	option SunRay.AuthSrvr xxx.xxx.xxx.xxx;
	option SunRay.AuthPort code 22 = integer 16;
	option SunRay.AuthPort 7009;
	option SunRay.NewTVer  code 23 = text;
	option SunRay.NewTVer  "1.2_16.a,REV=2000.10.31.16.19";
	option SunRay.LogHost  code 24 = ip-address;
	option SunRay.LogHost  xxx.xxx.xxx.xxx;
	option SunRay.LogKern  code 25 = integer 8;
	option SunRay.LogKern  6;
	option SunRay.LogNet   code 26 = integer 8;
	option SunRay.LogNet   6;
	option SunRay.LogUSB   code 27 = integer 8;
	option SunRay.LogUSB   6;
	option SunRay.LogVid   code 28 = integer 8;
	option SunRay.LogVid   6;
	option SunRay.LogAppl  code 29 = integer 8;
	option SunRay.LogAppl  6;
	option SunRay.FWSrvr   code 31 = ip-address;
	option SunRay.FWSrvr   xxx.xxx.xxx.xxx;
	option SunRay.Intf     code 33 = text;
	option SunRay.Intf     "hme0";

	subnet xxx.xxx.xxx.xxx netmask 255.255.255.0 {
		pool {
			range xxx.xxx.xxx.1 xxx.xxx.xxx.10;
			allow members of "SunRayWorkstations";
		}
		range xxx.xxx.xxx.100 xxx.xxx.xxx.200;
		default-lease-time 3600;
		option routers xxx.xxx.xxx.254;
		option broadcast-address xxx.xxx.xxx.255;
	}

   or the like to the config file. Get the values from the DHCP template
   used by SUNs server.


2) VERY IMPORTANT
   The hardware does not necessarily ship with the latest firmware. This
   causes problems when USB support is required. Since most SysAdmins turn
   of tftp on their nodes there's no way for the appliance to load the
   new code from the server. The statement that the Rays use TFTP is hidden
   deep down in some manpage :-( Check your logfile for lines with
          software Version mismatch -- DHCP version
   The firmware management tools utfw* don't work with other DHCP servers
   than the one shipped by SUN because they simply change the value of the
   'NewTVer' tag (check config above) either for all or for single stations.

OK, hope that helps

Thomas

====== PGP fingerprint B1 EE D2 39 2C 82 26 DA  A5 4D E0 50 35 75 9E ED ======

	Thought you got rid of all year 2k bugs and problems?
	Here's a new one: Windows 2000