×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

2 clustered MCUs having Redundancy

Answered Question
Oct 7th, 2013
User Badges:

Hi,


I went thorugh some posts on this discussion forum,


and it turns out there is no such way to have Redundancy when two MCUs clustered eventhough we have Conductor.


But just in case, I want to discuss one more time.


To make duplex-MCUs(when master failed during the calls, slave gets calls),


what can we do?


Suppose you have two MCU 5320, one Conductor.





Ta,


best wishes


Paul.

Correct Answer by Patrick Sparkman about 3 years 10 months ago

When clustering MCUs and a failure occurs:

  • if the master fails, so will the slave, since the slave is tied to the master.
  • if the slave fails, the master will still be online and running, but without the added capacity of the slave.

If you would like total redundancy, you'd have to run both MCUs independently of each other, and use Conductor.  You won't get the feature of added capacity for each MCU because they aren't clustered, but you get resiliency.


As you mentioned there are several other discussions covering this exact topic.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
kntieche Tue, 10/08/2013 - 01:11
User Badges:

Hi Paul,


if your goal is to have call routed to the second MCU when the first one becomes unavailable that's achievable with the conductor. You will have to configure both MCU inthe same bridge pool on conductor

You might go through this guide for details: http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_with_Cisco_VCS_Policy_Service_Deployment_Guide_XC2-2.pdf


However if you are loking for a live failover where the call will be routed to the second MCU if the master currently hosting the conference "fails", that will not be possible as far as i know.

Cheers

Karim

Correct Answer
Patrick Sparkman Tue, 10/08/2013 - 06:33
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 TelePresence

When clustering MCUs and a failure occurs:

  • if the master fails, so will the slave, since the slave is tied to the master.
  • if the slave fails, the master will still be online and running, but without the added capacity of the slave.

If you would like total redundancy, you'd have to run both MCUs independently of each other, and use Conductor.  You won't get the feature of added capacity for each MCU because they aren't clustered, but you get resiliency.


As you mentioned there are several other discussions covering this exact topic.

Actions

This Discussion