We have a similar config, i.e. Sunrays using GUI firmware pointing to version 4.1 Sunray servers and connecting via a shared LAN. For us, the firmware update just seems to work.
We do the following: ON THE SERVER: -------------- /opt/SUNWut/sbin/utfwadm -A -a -V -f /opt/SUNWut/lib/firmware_gui/CoronaP8 I think that the "-V" option avoids any attempt to update DHCP ON THE CLIENT: -------------- In the client GUI setup we setup the client IP details, then go into the "Servers" section and set both the SR server IP at the "Enter servers" prompt and the same IP at the "Enter firmware server" prompt. If we patch the Sunray server software and a new firmware is installed, the Sunrays seem to download it automatically the next time they connect. We *DID* have a problem once with firmware not loading into a new Sunray unit, but in that case the issue was that the existing firmware wasn't compatible with the newer Sunray hardware. Once we updated our firmware, it downloaded to the new unit properly. INTERESTING ASIDE: If you use the GUI firmware and enter only the server/firmware server information and *NOT* the client IP address, it will pick up a client address from your LAN DHCP infrastructure while still honouring the server addresses. In other words, you can assign the IP dynamically without having to have access to the DHCP infrastructure to setup the special Sunray specific keys. >To: " SunRay-Users List" <[email protected]> >From: [email protected] >Date: Fri, 20 Nov 2009 13:56:08 -0500 >Subject: [SunRay-Users] Pushing GUI firmware updates across LAN / WAN / VPN ? > >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 ================================================================= Sean Walmsley sean at fpp . nuclearsafetysolutions dot com Nuclear Safety Solutions Ltd. 416-592-4608 (V) 416-592-5528 (F) 700 University Ave M/S H04 J19, Toronto, Ontario, M5G 1X6, CANADA _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
