Re: load balancing metrics

In the begining, without the thash of a filter, Alteon makes client
persistence by minmisses or hash metric in a group. Without other
factors, clients going to the same destination IP will be redirected to
the same real server. Once you setup the thash in a filter, the thash
will change the behavior (algorithm) of hash or minmisses in a group
because it becomes a factor for hash or minmisses algorithm in a group.


By default, thash of a filter, minmisses, and hash only use 24bit IP
address to make redircetion or SLB decisions. If the number of real
servers or the IP address range of clients never changes when you are
testing the redirection. You probably get the same result if you only
use sip as the parameter of thash. In other words, clients in the same
class C subnet probably are redirected to the same real server.

In the previous reply, I suggest "sip+sport" parameter for your
testing because this lets the factor become more variable than "sip".
Or you can use "mhash" command in a group; this command changes 24bit
to 32bit IP address hash for minmisses. Therefore, you might get a
different result for applicaiton redirection.

Anyway, it doesn't mean that clients going to different website will
be exactlly redirected to different real servers.

cconnell_1@xxxxxxxxx wrote:
Ok thats interesting, which part is used so that the client sip sticks
on the same real server, is it the hash metric in the sip filter, or
the hash metric in the group. We have thash on filter as sip and in the
group hash, it seems to load balance by sip of the client i.e. we only
get the same sips sticking to the same proxy server.(dont see any sips
on the other proxies)

I read the sip is passed to the slb group from the filter (which as you
said if you specify thash as sip in the filter it has an effect on
redirection) So as the hash and minmisses used in application
redirection is based on dest ip. So this should mean each time a
client goes to a different web site (dest ip), it will be a different
hash so the request should go to a different real server?

.

Relevant Pages

  • Re: Welcher Algorithmus steckt hinter PASSWORD?
    ... > vorhandene neue PW's weiterhin von neuen Clients zur Anmeldung benutzt ... Ausgerechnet dieses Password wird ... AND benutzername!= '' ... jetzt ein langer Hash, durch "--old-passwords" wird in eurer Anwendung jetzt ...
    (de.comp.datenbanken.mysql)
  • Re: Workaround with Remoting in CF
    ... > else you can store it in the Application Cache. ... >> I need a hash table in memory and clients accesing to it. ...
    (microsoft.public.dotnet.framework.compactframework)
  • RE: Password Management
    ... still the reasoning behind the legacy thoughts of 7 being an optimal ... Hash: SHA1 ... two hashes, one that is 7 characters full, one that only has 2 ... used in the early days of NT and Win95/98 clients. ...
    (Security-Basics)
  • Re: [opensuse] Tool to extract/save mail attachments?
    ... Hash: SHA1 ... but you need a filter to do this separation; ... But perhaps there is a procmail recipe for this. ...
    (SuSE)
  • Array object but to_a is needed to access data
    ... attr_reader:hash,:action ... endclass Filter ... puts "urgent: #" ...
    (comp.lang.ruby)