Thanks Craig, Works like a charm, of course. I was missing the 'V' part of the magic incantation for utfwadm -AaV, step one. Was not generating the expanded files in tftp directory without it. Soon as I did that, powercycling causes the DTUs to go get the new firmware load since most are configured with server address already.
The utfwload -HaL command did not pick up all DTUs immediately however; not sure why. Some were not set up already with the firmware server address, but from your description, sounds like they should not have needed it anyway. At any rate, all is good. Comment: I think the documentation around this could be better though -- only contains instructions on dealing with the private interconnect case. And I also did not catch the 'V' trick from the man pages either, despite several reads -- still don't even now really. Your description would be a good add to the wiki btw. Thanks again, Peter Craig Bender <[email protected]> Sent by: [email protected] 20/11/2009 14:16 Please respond to SunRay-Users mailing list To: SunRay-Users mailing list <[email protected]> cc: Subject: Re: [SunRay-Users] Pushing GUI firmware updates across LAN / WAN / VPN ? In the case that you are upgrading (downgrading is different) Most people are configured without a private interconnect. Generally this is a good thing Did you just do utadm -L on? If that's the case and you wanted to upgrade to new FW after applying the patch you'd first run # ./utfwadm -AaV -f /opt/SUNWut/lib/firmware_gui And you'd see this output CoronaP1 GUI4.2_49_2009.08.27.18.08 CoronaP2 GUI4.2_49_2009.08.27.18.08 CoronaP3 GUI4.2_49_2009.08.27.18.08 CoronaP4 GUI4.2_49_2009.08.27.18.08 CoronaP5 GUI4.2_49_2009.08.27.18.08 CoronaP6 GUI4.2_49_2009.08.27.18.08 CoronaP7 GUI4.2_49_2009.08.27.18.08 SunRayP8 GUI4.2_49_2009.08.27.18.08 Now your /tftpboot directory is filled with the right firmware and parms files. Do you have the FW server configured in the FW GUI? It should point to the server with the updated firmware and parms. If not, you can force all connected Sun Rays to load via utfwload. First let's look at a unit: # ./utquery -d 255.255.255.255 terminalID=00144f79818b terminalIPA=192.168.7.134 model=SunRayP8 currentAuth=192.168.7.10 currentFW=4.1_50_2008.09.25.12.37 currentBarrier=325 currentBarrierLevel=325 currentMTU=1500 Subnet=255.255.255.0 Router=192.168.7.1 Broadcst=192.168.7.255 LeaseTim=120 DHCPServer=192.168.7.1 INFORMServer=192.168.7.1 FWservType=none configMTU=1500 dnsList=192.168.7.1 dname=lan stopqon=0 bandwidth=100000000 We see here it's running 4.1 FW. So let's run utfwload for all connected DTU's # ./utfwload -HaL Upgrading units to version GUI4.2_49_2009.08.27.18.08: DISP User IP Address Model.Mac Firmware Version 2.0 ???? 192.168.7.134 P8.00144f79818b 4.1_50_2008.09.25.12.37 <Sun Ray DL's FW and screen gets a little funky then resets> # ./utquery -d 255.255.255.255 terminalID=00144f79818b terminalIPA=192.168.7.134 model=SunRayP8 currentAuth=192.168.7.10 currentFW=GUI4.2_49_2009.08.27.18.08 currentBarrier=420 currentBarrierLevel=420 currentMTU=1500 Subnet=255.255.255.0 Router=192.168.7.1 Broadcst=192.168.7.255 LeaseTim=120 DHCPServer=192.168.7.1 INFORMServer=192.168.7.1 FWservType=none speed=100F configMTU=1500 dnsList=192.u168.7.1 dname=lan confNetType=DHCP stopqon=0 bandwidth=100000000 Presto. Upgraded FW without option 66 or vendor class options. Now if you are already running GUI FW, as noted before you can fill out that entry for the server configured with your new FW. I understand you might not want users doing that. [email protected] wrote: > > Hi, > This is probably a dumb question, but here goes... (I am used to it ;-) > > For various reasons, we are configured without private interconnect, ie. > on shared LAN. Also do not have DHCP setup across the whole network for > Sun Ray configuration. We have been using the GUI firmware to aim the > DTUs at appropriate Sun Ray Servers / FoGs -- we have multiple of them, > so need to be able to aim individual DTUs at specific servers. > > We would like to be able to push the GUI firmware out to the DTUs, in > order to update all for SRS 5 in this case, rather than drag each unit > back to lab and direct connect them to a particular server. I have not > been able to figure out how to do this from the Sun Ray documentation, > and have not managed to find it on wiki either. Perhaps I am blind. > > Have tried various combinations of utfwsync, utfwadm, utfwload, and all > are complaining that there is no direct interconnect -- "no action > taken". I have also manually copied the gui firmware files from > /opt/SUNWut/lib/firmware_gui to /tftboot/ directory, and set the DTUs > firmware server to the address of our server (using the ctl-break-M > trick). Powercycled the DTUs, reboot the server, etc. No joy so far. > I have also considered un-configuring the server for LAN access, and > trying to trick it into thinking it has a direct connect (utadm -a), > then set it back to LAN. But this seems risky. I have a feeling I am > missing something obvious here, or just don't know the right magic > incantation. > > So, the question is: Is there a reliable method to force firmware > updates out to DTUs across LAN? Same question will inevitably also come > up for teleworker case too, across the DTU-embedded VLAN. > > Any help on this would be great. > > -- Peter > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
