[cisco-voip] Something SRST-like for large installations

[Erik Goppel]

Simon,

In case of upgrading your cluster, you could rehome your ipphones/GW`s to
one or more of your subscribers, make sure the ip phones/endpoints and
subscribers cannot reach your publisher or other call-processing nodes that
are included in the upgrade process(ACL`s)
then upgrade your cluster, and check if everything is fine, if you decide
your upgraded cluster is ok, start rehoming your devices to the upgraded
publisher and/or subscribers, now you can upgrade your other subcriber
nodes.

Be aware that a lot of cpu/io/SQL will be utilized when you start synching
the subscribers, and also for 11K devices you will have quit the TFTP and
registration load on the Pub/tftp

I`ve upgraded a cluster with 6500 endpoints, and worked perfectly with minor
disturbances (only the homing and rehoming from temp call processing node to
primary processing node)
The cluster had 1 pub and 5 subs, i configured 3 subs to each take approx
2500 endpoints, and started upgrading the pub, then i did the sub (wait for
complete synch), and rehomed 2500 devices to the upgraded sub, then started
the next sub, rehomed 2500 devices to the upgraded sub, and finally the last
one.
After the entire cluster was done, i configured the callmanager groups, the
way they should be, and rehomed the devices again.

I don`t know the nr of servers you are using, but this is a way of doing it,
without major disturbances. (however do it in a service window at all times)


If you really want something SRST like, you probably have to invest in a
bunch of SRST-capable routers and configure the underlying h323 to make sure
all the devices can utilize your e1`s /t1`s

Grtz


Erik Goppel



2006/12/19, Simon, Bill <bills at tns.its.psu.edu>:
>
> The idea is more that we are interested in a solid-state, non-Windows
> redundant solution.  For when we are upgrading CallManager or bailing
> out after screwing something up on the cluster.
>
>
> Ortiz, Carlos wrote:
> > I assume that means you don't have the bandwidth to have a local
> > subscriber?  That would be the easiest solution if the bandwidth is
> there.
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > *From:* cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Lelio
> Fulgenzi
> > *Sent:* Monday, December 18, 2006 3:47 PM
> > *To:* Simon, Bill; Cisco Voip
> > *Subject:* Re: [cisco-voip] Something SRST-like for large installations
> >
> >
> >
> > If you need all phones to have dialtone then two SRST routers seems like
> > the only alternative.
> >
> >
> >
> > However, do ALL phones really need to have dialtone? I mean, are there
> > some phones you can identify as phones that don't require redundant
> > dialtone? Some meeting rooms? Some hallways?
> >
> >
> >
> >
> --------------------------------------------------------------------------------
> > Lelio Fulgenzi, B.A.
> > Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> > (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > "I can eat fifty eggs." "Nobody can eat fifty eggs."
> >
> >     ----- Original Message -----
> >
> >     *From:* Simon, Bill <mailto:bills at tns.its.psu.edu>
> >
> >     *To:* Cisco Voip <mailto:cisco-voip at puck.nether.net>
> >
> >     *Sent:* Monday, December 18, 2006 3:43 PM
> >
> >     *Subject:* [cisco-voip] Something SRST-like for large installations
> >
> >
> >
> >     Need some suggestions for something SRST-like but for large
> >     installations.
> >
> >     Basically we would like to have dial-tone service in the event that
> the
> >     CallManager cluster, for some reason, bites the dust.
> >
> >     The largest SRST option seems to be 780 phones, but we often deploy
> >     large subnets of 800-1000 phones.  The campus overall has 11k phones
> at
> >     this time on one CM cluster.
> >
> >     Don't yell at me for putting 11k phones on one cluster; Cisco said
> we
> >     could do it ;-)  besides I am not at liberty to redo the whole
> >     infrastructure.  I just need to make a suggestion for redundant
> >     dial-tone service.
> >
> >     Any thoughts?
> >
> >     Bill
> >
> >
> >     _______________________________________________
> >     cisco-voip mailing list
> >     cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> >     https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
> --
> Bill Simon - bills at tns.its.psu.edu - (814) 865-2270
> http://tns.its.psu.edu/
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061219/cea7d16b/attachment.html