On 2012-11-05 17:29, John Doe wrote:
Thank you Jim. I appreciate the fast reply.
According to http://docs.oracle.com/html/E22661_15/Clients-Boot-Process.html
(section 4a) the DNS entries simply provide a list of servers to get
the .parm files from.
Right, I was too eager in copy-pasting. Since you rely on DNS anyway,
you can also define the "sunray-servers" name in the default search
domains that your DTUs know from DHCP, which can be a list of "A" type
entries for each server in the FOG on this subnet. This way you don't
need the parms-files to provide the list of servers (though you can
pass other configuration this way).
Also note that you can have some programs (utswitch/utselect, maybe
hotseating, etc.) that might try to redirect your DTU to a different
server than the one it initially connected to. If you have some scripts
doing such utswitch'es, you might need to take care that they redirect
by name or to proper IP numbers. I am not experienced in this part,
so I hope that the more knowledgeable list members could chime in
if needed.
> The parm files then contain a list of servers
to connect to. What I am not following about your solution is that
even if the 10.0.2.0 sunrays get their parm files from 10.0.2.45-47
and the 10.0.1.0 sunrays get their parm files from 10.0.1.45-47 due to
the differing DNS entries, they would still be the same parm files
(since they are the same server). The parm files would contain:
servers=10.0.1.45, 10.0.1.46, 10.0.1.47, 10.0.20.48
Therefore the sunray thin client would still connect to one of those
IPs. I could modify the parm file to contain:
servers=10.0.1.45, 10.0.1.46, 10.0.1.47, 10.0.20.48,10.0.2.45,
10.0.2.46, 10.0.2.47
The issue with that however is 10.0.1.0 sunrays could happen to choose
a 10.0.2.0 interface to connect to and vice-versa.
--------------------------------------
Original Message:
You can still provide proper config with the DNS, just make two
naming zones (i.e. sunraynet0.domain.com and sunraynet1.domain.com)
where the "sunray-config-servers" entry points to correct IPs,
and announce the proper default domain with DHCP on these subnets.
Alternately, you can configure the (ISC BIND) DNS server with "views"
so that the server reports different naming info to the same queries
depending on client IP addresses. But this is mostly useful when you
split the naming info for intranets and internet and use the same
instance of the (multihomed or not) DNS server. This way names like
"www.domain.com" can resolve to different IP numbers reachable for
the particular client. I am not sure your situation requires that,
but keep the option in mind.
HTH,
//Jim
On 2012-11-05 16:37, John Doe wrote:
I currently have four Sunray server's in a FOG as follows:
10.0.1.45 - Server1
10.0.1.46 - Server2
10.0.1.47 - Server3
10.0.20.48 -Server4
The sunray clients are located in the 10.0.1.0/24 subnet. They obtain
the parm files using a DNS lookup of "sunray-config-servers" which
provides server 1, server 2, and server 3. The parm files on each
server are identical and contain a listing of all servers for the
sunray client to choose from. I want to modify the configuration as
follows:
10.0.1.45 - Server1 - net0
10.0.2.45 - Server1 - net1
10.0.1.46 - Server2 - net0
10.0.2.46 - Server2 - net1
10.0.1.47 - Server3 - net0
10.0.2.47 - Server3 - net1
10.0.20.48 -Server4
Some of the Sunray thin clients will be put into 10.0.2.0/24 and some
will be put into 10.0.1.0/24. I want the Sunray clients on
10.0.2.0/24 to connect to the .2 interfaces and 10.0.1.0/24 clients to
connect to the net0 interfaces. The only solution I could think of is
to use the DHCP option to specify a custom TFTP server to 10.0.2.0/24
clients. This TFTP server will serve custom parm files that only
contain .2.45, .2.46, and .2.47 in their servers list. This solution
seems like it will work but is hackish. Is there a better solution to
this issue?
_______________________________________________
SunRay-Users mailing list
SunRay-Users at filibeto.org
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
