16 May
2005
16 May
'05
9:48 p.m.
I'm hoping to clarify a couple questions on clustering SER in high-volume
environments as well. Assuming authentication is RADIUS, wouldn't
clustering something like what Darren is talking about be as simple as
installing multiple SER boxes and just doing some DNS round-robin? Would
that introduce any registration issues?
-Corey
Darren Nay wrote:
*********************************************
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
Senad, Thanks for your response.
There are several reasons.
The 2 biggest are..
1 - We offer our customers the option to forward calls when an IAD is
not registered .. In order to do that the registration interval needs
to be relatively low.
Fine... But still I am curious why u need to do in order to forward the
calls.
2 - We've had some issues with setting registration intervals higher
than 10 minutes. It seems to work about 99.5% of the time, but
occaisionally an endpoint won't reregister before the reg interval on
SER times out. I believe this is a bug in our endpoint and have been
working with them on that. Setting the reg interval below 10 minutes
has eliminated that problem for the time being .. However, even if
this problem was fixed by the IAD manufacturer we still have the
first reason (above) that would keep us from being able to increase
the interval.
Well. apart from fixing the issue with your IAD, you could use DNS SRV
record.
Each time, IAD wants to re-register it will use DNS SRV record, hence
"hitting" different server.
This way, u will need more than one SER server each getting its data from
central network database.
If you need cluster file system, then you could use GFS or similar.
Regards,
Senad
PSS!!!
Which IAD are you using ?