[SunRay-Users] Sessions clustering on one server in failover group

P.S.M. Swamiji Psm.Swamiji at Sun.COM
Wed Jan 31 16:41:19 EET 2007


If the  servers are offline then it won't be consider for load balancing.

Thanks
P.S.M.Swamiji

Note:These are my personal opinions, nothing to do with my employer

Marcus Young wrote:
> Thank you Brad,
>
> yes, the output utgstatus  was normal - utadm -n did the trick 
> (although utadm -l showed lan connections on).  So it looks like the 
> servers were configured not to 'accept' connections.  Although the 
> strange thing was that servers 1 & 3 were running a number of sessions 
> - just not load balanced.
>
> thank you for the advice...
>
> Marcus
>
>
>
> ----- Original Message -----
> *From: *sunray-users-bounces at filibeto.org on behalf of Brad Lackey - 
> US-SW Desktop Product Lead
> *Sent: *Wed, 1/31/2007 12:54am
> *To: *SunRay-Users mailing list
> *Subject: *Re: [SunRay-Users] Sessions clustering on one server in 
> failover group
>
> Let's start with the output of /opt/SUNWut/sbin/utgstatus
>
> The results of this command from each FOG server is an important first 
> step.
>
> This should tell us if SRSS thinks it's properly communicating to the 
> other members of the fail over group.
>
> On Tue, 2007-01-30 at 22:20 +1100, Marcus Young wrote:
>>  A question about unexpected behaviour with a failover group...    
>>      
>>  We have been running a Sol10/Sparc 3.1 LDAP auth failover group of 3 servers since mid 2006.  Several weeks ago we replaced the three servers with a similarly configured cluster upgraded to the current patch level.  The data store was migrated from the original cluster to the new cluster.  The group has now been running some time and we are seeing the majority of sessions (active and pseudo) landing on one of the servers (master).  The ratio of sessions is approximately (100:2:20).  In fact the middle server now has no sessions (after a restart).  This is quite different from the behaviour we have seen previously where the sessions balance reasonably well.  Nothing obvious in the SunRay or systems logs.  Would anybody be able to suggest a possible cause and consequent solution?    
>>      
>>      
>>  Marcus    
>>      
>>  
>>  _______________________________________________  
>>  SunRay-Users mailing list  
>>  SunRay-Users at filibeto.org <mailto:SunRay-Users at filibeto.org>  
>>  http://www.filibeto.org/mailman/listinfo/sunray-users 
>>     
>
> 	*Brad Lackey*
> Desktop Product Lead
> US Software Practice
> (720) 548-3339
> Brad.Lackey at sun.com <mailto:brad.lackey at sun.com>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> SunRay-Users mailing list
> SunRay-Users at filibeto.org
> http://www.filibeto.org/mailman/listinfo/sunray-users
>   



More information about the SunRay-Users mailing list