[cisco-voip] 3 server cluster - Server roles

[Nate VanMaren]

One of those servers can do 7500 phones, so it would be hard to push them too hard.

If it were me, I would
Dedicated Pub
SUB1:  Subscriber + TFTP + IP Voice Media Streaming with ALL phones registered, secondary tftp
SUB2:  Subscriber + TFTP + IP Voice Media Streaming Primary TFTP, and secondary call processing.

I don't like load balancing between failover pairs during normal operation because if one fails and you aren't used to seeing the full load, then you've got trouble.

-Nate


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ovidiu Popa
Sent: Tuesday, August 31, 2010 2:27 AM
To: cisco-voip
Subject: [cisco-voip] 3 server cluster - Server roles

Hi everyone

I have a 3 server cluster (around 1500 users) with 7845 HPs and need to define how to activate the services between them.

Cisco recommends 4 servers for clusters > 1250 users :
1 dedicated PUB
1 dedicated TFTP
2 Subscribers

Since I have 1500 users and 3 servers I don't exactly fit the SRND specs and I was wondering what you think is the best way to handle this ?

For now I'm leaning towards 50-50 load on Subscribers with the following services:
PUB : Administration only
SUB1 : Subscriber + TFTP + IP Voice Media Streaming
SUB2 : Subscriber + TFTP + IP Voice Media Streaming

One other option that I like but involves overhead is this:
PUB: Administration + TFTP (primary)
SUB1: Subscriber + IP Voice Media Streaming (Primary)
SUB2: Subscriber + TFTP (Secondary) + IP Voice Media Streaming (Secondary)

What do you think?


Thanks,
Ovidiu








 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100831/df2c47ad/attachment.html>