|
Home > Archive > Voice over IP Cisco > November 2005 > Split CM Cluster
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Andrew Dignan 2005-11-28, 5:54 pm |
| The old SRND guide said that 900k was needed "per" callmanager in a
cluster to split it. The new SRND guide says 900k per 10,000 BHCA (I
think this is slightly higher, if you use Cacti to monitor the bandwidth
its about 1200k from what I have seen). Anyway, is this to say that if
you have 5 CallManagers in a cluster. 3 in one site and 2 in another site
but less than 10,000 BHCA you only need about a T1? That just doesn't
seem right to me.
| |
| Philip Walenta 2005-11-28, 5:54 pm |
| Actually, the 900k number has always been for 10,000 BHCA. The 900k is raw,
unencapsulated data.
The way it works is - if a subscriber is doing 10,000 BHCA, it needs a
minimum of 900k. The numbers go up from there. If the whole cluster is
doing 10,000 BHCA, and it's across 5 sites, you still need no less than 900k
per server just to be safe, because some of the background processes (CTI,
TCD etc) can sometimes get a bit chatty.
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Andrew Dignan
Sent: Monday, November 28, 2005 10:36 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Split CM Cluster
The old SRND guide said that 900k was needed "per" callmanager in a cluster
to split it. The new SRND guide says 900k per 10,000 BHCA (I think this is
slightly higher, if you use Cacti to monitor the bandwidth its about 1200k
from what I have seen). Anyway, is this to say that if you have 5
CallManagers in a cluster. 3 in one site and 2 in another site but less
than 10,000 BHCA you only need about a T1? That just doesn't seem right to
me.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|