Bob Doolittle wrote:
Brian Knoblauch wrote:
I rather not rely on the Sunray Server's dhcpd for my normal boxes,
I need DDNS and I need all my "normal" boxes to work when I take my
Sunray
Server to demonstrations.
I run my SunRays on the same network as everything else, and just
let
the DHCP server in the router server up the addresses. I don't setup
the SunRay server DHCP server. The SunRays still auto-discover the
server just fine (since they're in the same broadcast domain).
This'll work just fine, as Brad suggested (use "utadm -L on"). But,
it won't
manage firmware automatically (you could do something like put
"utfwload -l"
into a cron job to do this),
utfwload -l won't work if one runs just utadm -L on. They atleast should
run utfwadm -A -a -V
after utadm -L on and then can use ufwload -l to upgrade the firmware.
Thanks
P.S.M.Swamiji
Note:These are my personal opinions,nothing to do with my employer
and it won't enable client syslogging (unfortunately,
the only way to do this is still to use DHCP, but client syslogging
rarely shows
anything helpful anyway so this isn't critical).
Slightly fancier is to either set your DNS IPs for
"sunray-config-server" to
resolve to your Sun Ray servers (especially helpful if you have your
Sun Rays
on subnets remote to your server), or to set DHCP Option 66 to point
to them.
Then, the .parms file will get TFTP'd and will control your firmware
updates.
-Bob
_______________________________________________
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
