Trevor Dell wrote:
Do you mean you connect to the failover group by a utswitch
<HOSTNAME>? Or are you meaning the SunRays find the servers via DHCP
(not DNS)?
The sunrays find the sunray server from dns. They are registered as
dtu.domain.stuff and there is a cname for the sunray server at
sunray-config-servers.domain.stuff. That has worked well thus far, until
the new server came along. According to
http://blogs.sun.com/ThinkThin/entry/sun_ray_provisioning, the dns query
is the second option tried, while the broadcast is the last. From that,
I would think that the dns way should have priority over broadcasting,
but this does not appear to be the case.
If the answer is the latter (which I think you mean) They have 3
methods of finding the server they do in this order:
1) Use the Sun DHCP vendor macros
2) Send a broadcast out to the local subnet on the SunRay server port
3) Use the standard DHCP option 55 (X-Display-Manager)
If have your test server on the same subnet as your production FOG,
the only way you can prevent the SunRays connecting to your test
server is by using the 1st method. The 3rd option is useless if the
SunRays are on the same subnet.. (unless things have changed)
Does this mean that the DNS method does not supersede broadcast?
We would put the test server and certain SunRays on a different VLAN
here if we did something like that, though I know that isn't an option
for some environments.
I'd rather not have to go through such lengths for a system that should
be working now.
Thanks,
Christian McHugh
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
