Some additional information...
Option 66 is a single item field. It can be an ip address or a dns name.
I like to put all of the servers in my FOG under an aliased name
sunrayfog.mydomain.com then add that name to Option 66... This way
there is some redundancy with the TFTP cycle of DTU configuration.
Then in the .parms files I put
servers=server1,server2,server3
select=random
Which balances the initial connection.
Then the FOG processes do the rest of the load balancing/re-conenction
logic.
Brad
Bob Doolittle wrote:
Andy Malato
wrote:
Hello --
We are currently running SRS 3.1 on Solaris 9 using a shared LAN, i.e.,
public addresses are assigned to the DTUs and no private SunRay
interconnect exists. The DTUs get their public addresses from a
separate
DHCP server, which handles addresses for our entire network.
The SunRay server is in a separate subnet from the DHCP addresses; the
DTUs
find the SunRay server via DHCP options 49 and 66.
We are interested in setting up an additional SunRay server to act as a
secondary server (failover) in case the primary server fails.
Are there any specific networking requirements that are needed in order
for the FOG to work correctly? From my understanding and
interpretation
of Sun Ray Server Software 3.1 Administrator's Guide, it appears that
the
only requirement is that the primary and secondary servers be on the
same subnet? I assume then we would then add both IP addresses,
Primary and
Secondary to our DHCP server options?
The Sun Ray servers should have static IP addresses. Options 49
and 66 are mutually exclusive - 66 is preferred since it provides finer
management control (e.g. firmware). You can specify your
SRSS servers in the .parms file itself (so 49 is not needed). It is
best to provide multiple IP addresses for option 66 for HA purposes,
so specifying both Sun Ray servers is a good approach.
If you multi-home the Sun Ray servers, they need only share
one subnet (you don't have to even share a subnet if you utilize
IP multicast but this configuration is error-prone due to difficulty
in implementing IP multicast properly in routers/switches).
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
--
 |
Brad Lackey
Desktop Product Lead
US Software Practice
(720) 548-3339
[EMAIL PROTECTED]
|
|
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
