Re: : Target Diameter server poorly specified

Glen Zorn (gwz) wrote:

> Miguel Garcia <mailto:[email protected]> supposedly scribbled:
> 
> ...
> 
> 
>>It is correct to think that there is a single Diameter server (for a
>>given user). 
> 
> 
> No, that can't be so: there must be only one Diameter server _period_ for this to work, unless the entire farm is preconfigured to know which Diameter handles requests for any given user.  If the Diameter clients can send requests to more than one server, how do they know which one handled the previous request (and thus holds the necessary state)?  What am I missing here?

So... let me clarify the situation:

On one side, we say that ***for a given user*** his data is stored in a 
single Diameter server. We say that such Diameter server can be 
configured as a farm of redundant servers, something that is outside the 
scope of this specification. In this case it is required that all the 
servers in the farm keep the data synchronized, again, something that is 
not within the scope of this specification.

On the other side, due to scalability in large networks with many users, 
it is feasible that the user space is split across several Diameter 
servers, so that, say Diameter server 1 takes care of users 1-100, 
Diameter server 2 takes care of users 101-200, etc. In this case we need 
a Diameter subscriber location, that acts similar to a Diameter redirect 
agent. Section 5.10 provides much information about that.

Regards,

     Miguel
> 
> ...
> 
> Hope this helps,
> 
> ~gwz
> 
> Why is it that most of the world's problems can't be solved by simply
>   listening to John Coltrane? -- Henry Gabriel

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:[email protected]
Nokia Research Center      Helsinki, Finland