Hi, Thank Chris. :-) On Mon, 2005-03-21 at 16:50 +0400, Christopher Saul wrote: > Hi Kim > > Take a look at this section of the docs - > > http://docs.sun.com/source/817-6806/failover.html#84345 >
Thanks now I re-read that. > 'Ideally, each server would have an address for each DTU. ' > > In your case a Class B network would work best, with each server having > at least 1,000 addresses available for DTUs. > > In your example, if one server fell over, the remaining servers wouldn't > have spare addresses for the 100 DTUs that had lost their connections > and needed to reconnect. Oh, I see. how about that? Sunray Server 01 --> 172.16.0.1 --> Switch (for 1000 DTU 172.16.1.1 ~ 172.16.4.254) Sunray Server 02 --> 172.17.0.1 --> Switch (for 1000 DTU 172.17.1.1 ~ 172.17.4.254) Sunray Server 03 --> 172.18.0.1 --> Switch (for 1000 DTU 172.18.1.1 ~ 172.18.4.254) ..... Sunray Server 10 --> 172.25.0.1 --> Switch (for 1000 DTU 172.25.1.1 ~ 172.25.4.254) I think upper lay out is cover nine Server failure. that's correct? And in that design, If I use DTU 172.16.1.1 with a smart-card, and runing some application then without logout just remove smart-card, then I use different DTU 172.25.1.1 with that smart-card. that time I think I can see exist work space(used in DTU(172.16.1.1)) with my running application. is it correct? If that is, when I insert smart-card, SRSS check session info, and new DTU(172.25.1.1) direct contact to Sunray Server 01, is it correct? > > First, when I use Sunray failover group, that group share all session > >info? > > So Any one can access any DTU with same session? > > Yes. It's explained in detail in the docs, but... Assuming we are > using smartcards or non smartcard mobility, a user inserts a smartcard > or logs in and the servers pass tokens around, talk to eachother and > direct the DTU to the server running an existing user session, or create > a new one if no session exists. > > >Last, in order to share user account info( disk and password) within a > > fail over group, is there need some kind of LDAP and NFS solution? or > > SRSS cover all of them? > > Sun Ray Server Software just handles displaying a Solaris session on a > Sun Ray device. Managing user names and passwords, file sharing etc, is > normal Solaris stuff (I'm assuning you're using Solaris - same goes for > Linux though). > > In your case, assuming users are running Solaris sessions and using > Solaris applications, the ideal way would be to have a separate NFS > server, preferably clustered, given the large number of DTUs. For > managing usernames you could use LDAP or NIS. NIS could run on the file > server(s), as could LDAP. At first we test x86 SRSS 3 in JDS, I think JDS is too havey and too slow so I will try to change test system to Redahat EL4. I also think some kind of LDAP and NFS for sharing each account info, but some guy insisted there is no need that, so I asked. We(I am not project manager or main staff, but have to do some kind of main staff :-( ) try to design a network solution using Sun Ray System with some SBC solution, for using Microsoft OS or Application. For testing sunray system, now we just using rdesktop with MS 2003 server and terminal service. We try to find more fixable solution, we consider citrax's metafram, cnetia's thinmaster, and vmware's ESX server. > Which country are you based in? This sounds like a large and > potentially complex deployment - your local Sun team should be able to help. I am not Sun member but have some kind reelection ship with local Sun team, but honestly our local Sun team is helpless(They doesn't offer contact point for technical issue for sunray and doesn't well reply about some question). Now I am not sure that project will be continued or not, I also know there is another almost 1,000 DTU Sunray Project, and that project manager asking me some setting and some.(mostly about Linux, but some time about sunray :-( ). At beginning I join that project for temporally, I just know linux, observing that project I found there is no one well understand and can design Sun Ray system. > Chris > > > Kitae Kim wrote: > > Hi, > > > > Now we have some project for using almost 1,000 sunray DTU with SRSS 3. > > I am new about sunray system. There is some question about design Sunray > > network system. > > In Administrator guide show two type sunray fail over group. > > > > First, when I use Sunray failover group, that group share all session info? > > So Any one can access any DTU with same session? > > > > > > Second, My thought for 1,000 DTU is(each Sunray Server cover 100 DTU, > > and 10 Sunray Server with one failover group) > > > > Sunray Server 01 --> 192.168.1.1 --> Switch (for failover group) > > --> 192.168.2.1 --> Switch (for 100 DTU 192.168.2.10 ~ > > 192.168.2.110) > > Sunray Server 02 --> 192.168.1.2 --> Switch (for failover group) > > --> 192.168.2.2 --> Switch (for 100 DTU 192.168.2.111 ~ > > 192.168.2.210) > > Sunray Server 03 --> 192.168.1.3 --> Switch (for failover group) > > --> 192.168.3.1 --> Switch (for 100 DTU 192.168.3.10 ~ > > 192.168.3.110) > > ..... > > Sunray Server 10 --> 192.168.1.10 --> Switch (for failover group) > > --> 192.168.6.2 --> Switch (for 100 DTU 192.168.6.111 ~ > > 192.168.6.210) > > > > That is my simple thought. Do you have any suggestion? > > > > > > Last, in order to share user account info( disk and password) within a > > fail over group, is there need some kind of LDAP and NFS solution? or > > SRSS cover all of them? > > > > Thanks > > > > Kitae > > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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
