Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CCX Far Away Redundancy

Hello all,

I have read in documentation that, more than 2 ms away redundancy has to be provided wih cold standby servers. Do you know any way two have warm stand by, do not mind if the configs have to be manually replicated?

Many thanks

1 ACCEPTED SOLUTION

Accepted Solutions
VIP Super Bronze

Re: CCX Far Away Redundancy

All current versions of CCX (5.x and 7.x) only support warm standby in a local LAN deployment.

UCM does support multiple CCX clusters if you configure everything properly. These are entirely separate from every perspective however and in reality is not viable for a fail over solution:

-Requires purchase of a second copy of all licenses (node, agent, etc)

-No replication between clusters: configuration, reporting, scripts, etc all must be configured twice.

-No automatic fail over from one cluster to another. The closest option would be CFB on the CTI Route Points on the first cluster. This does not guarantee a fail over though. Only certain call scenarios would catch the CFB.

-Agents would need to modify postinstall.exe on their PCs manually to log in to the second cluster.

Either do cold standby for now; or, wait until 8.0 for HAoWAN.

Please remember to rate helpful responses and identify helpful or
4 REPLIES
VIP Super Bronze

Re: CCX Far Away Redundancy

You misread the documentation. The 2ms latency requirement is for warm standby deployment scenarios and there is no way around this. Cold standby does not have this requirement and does involve manual data restoration.

Be advised that cold standby will no longer be supported beginning in 8.0. Starting next year, warm standby will be the only supported scenario and will have LAN- and WAN-based deployment scenarios. Additional information will be available when the product reaches FCS in Q1CY10.

Please remember to rate helpful responses and identify helpful or
New Member

Re: CCX Far Away Redundancy

hello,

thanks for the answer. I didn't explained myself properly. You have understanded what I need, but, how to have warm standby in CCX 5/6/7, in a remote site? I have heard about having two CCX clusters, one in each site, and CCX clients register with one or other. Is this posible?

VIP Super Bronze

Re: CCX Far Away Redundancy

All current versions of CCX (5.x and 7.x) only support warm standby in a local LAN deployment.

UCM does support multiple CCX clusters if you configure everything properly. These are entirely separate from every perspective however and in reality is not viable for a fail over solution:

-Requires purchase of a second copy of all licenses (node, agent, etc)

-No replication between clusters: configuration, reporting, scripts, etc all must be configured twice.

-No automatic fail over from one cluster to another. The closest option would be CFB on the CTI Route Points on the first cluster. This does not guarantee a fail over though. Only certain call scenarios would catch the CFB.

-Agents would need to modify postinstall.exe on their PCs manually to log in to the second cluster.

Either do cold standby for now; or, wait until 8.0 for HAoWAN.

Please remember to rate helpful responses and identify helpful or
New Member

Re: CCX Far Away Redundancy

Thanks a lot

149
Views
5
Helpful
4
Replies