That's why the command is failing, there are no Sun Ray macros defined.
You can do utadm -A 192.168.129.0
This will create the Sun Ray macros.
From that point you can use the -N to declare a subnet, or you can even
use the term all to update all of them. Note that each time you apply a
SRSS patch you'll want to run the utfwadm to populate the /tfptboot
directory along with updating the DHCP Tables with the correct version
of FW. If you do use utadm -A <subnet> then you can use the command
/opt/SUNWut/sbin/utfwadm -AaN all -f /opt/SUNWut/lib/firmware_gui
To your dhtadm question, FWSrvr is a vendor class option under
SUNW.NewT.SUNW using code 31. Unless you let the utadm scripts do this
for you, I'd say stay away from that. That's why we now use and
recommend using standard option 66 which is TFTPSrvN. Which is TFTP
Server name. It's important to really understand that it's a name, not
an IP, which means that it has to be resolvable by DNS. This host will
contain the firmware files and the parms file for each host.
Or you could add an entry in DNS for sunray-config-servers.your.domain
that points to the firmware server. In the latter to cases, you'd then
use /opt/SUNWut/sbin/utfwadm -AaV -f /opt/SUNWut/lib/firmware_gui to
update the /tftpboot directory with both the firmware files and the
parms files to tell the Sun Ray which version of FW it should be running.
It's really not that complicated, but having a good understand of how
dhcp options work is required. The blog I pointed you to hoped to shed
some light on how that worked. Guess it kind of failed in that regard,
sorry.
CJ Keist wrote:
I just did utadm -L on and manually configured the DHCP server.
# /opt/SUNWut/sbin/utadm -l
LAN connections: On
Sun Ray interconnect framework is not configured
# dhtadm -P
Name Type Value
==================================================
192.168.129.0 Macro
:Subnet=255.255.255.0:Router=192.168.129.1:Broadcst=192.168.129.255:
suntest1 Macro
:Include=Locale:Timeserv=129.82.225.54:LeaseTim=86400:LeaseNeg:
Locale Macro :UTCoffst=-25200:
I tried adding FWSrvr using dhtadm but it gives that is an invalid DHCP
option. How when you configure an interconnect it can get that value in
there without any complaints?
Craig Bender wrote:
OK, let's back up.
How did you configure the interconnects? -A or just -L on? Provide
the output of /opt/SUNWut/sbin/utadm -l
CJ Keist wrote:
Thanks,
But it's jumping into something I don't fully understand. What do
they mean by DHCP option 66 or 49?
Craig Bender wrote:
A bunch of different ways. Pick the one that works the best for you.
http://blogs.sun.com/ThinkThin/entry/sun_ray_provisioning
CJ Keist wrote:
How do you get thin clients to get firmware updates if your SRSS
servers do not have dedicated interconnects configured? I have
tried the following:
./utfwadm -A -N 192.168.129.0 -a -f /opt/SUNWut/lib/firmware_gui
Error: cannot set firmware version to network macro "192.168.129.0":
Configuration for DHCP subnet 192.168.129.0 does not exist.
I do have DHCP configured to give IP address on the 192.168.129.0
network for the thin clients.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
