One of our customers is to have a primary site and the recovery for the conferencing site. They are planning to implement redundant VC a componnents like VCS, conductor, MCU and TMS.

I need your expert opinion in the deployment of the TMS in the main Site and recovery Site scenario.

Primary site and recovery Site is in a totally different network. We cannot extend the primary IP address on the site of DR. Because of this redundant components will have the IP address to a different subnet.

TMS Server A:

TMS Server B DR Site:

DNS A record for TMS server is>

I checked the options for redundancy of TMS, as shown in the link.

Fully redundant use the concepts of the load balancer.

I have the following questions.

1 could you please let me know what load balancer can be used for redundancy of TMS solution considering the IP address of the MSDS are in different subnets.

2. in several servers, manual failover option, if the failure of the principal server will we use address IP Cisco TMS Server Local IPv4 address and update the DNS record to point to


Option a.

I would not recommend an A DNS record pointing at a time... since it is essentially a round robin... which means that if DC 1 is down, you will get a search on the second, it will just fail. Therefore, I would recommend you do is just enter a DNS record for the DC 1 TMS and if you get a failure on DC 1, then simply go to DNS and to update IP address for this record to the DC 2 TMS.

Option B

No, you don't want to do this, i.e. Add the EPs for the two TMS initially. You only want to add systems to the DC 1 TMS... which means a TMS db to "govern together." And that's why your "asynchronous mirroring ' the TMS of DC db SQL to CC 1 2 SQL." And specify "async mirrroring in SQL", when you set the "async mirroring" in SQL, a db is 'active', while the other is "passive". That's why on the DC 2 TMS all services of TMS needs for people with reduced mobility because it cannot connect to the TMS SQL db (tmsng), which is passive. And with "async mirrored" on and how often you 'mirror', the basics of data will actually be the same.

At the end of the day, the deployment is not that big (20 systems) so all this may seem "exaggerated", but it is the approach to 2 x installation DC... unless of course you virtualize everything and go Nick road, i.e. the Group OTV and strecthed.



Tags: Cisco Support

Similar Questions


    I am configuring TMS 15.1 redundancy VM server to a different location other then the main server... It's about 2 clicks on the road.

    The only document of redundancy I found was the redundancy of CISCO's MSDS for 13.2 Guide?  Is there a newer version?

    Thank you.

    From TMS 14.1, establishing a deployment redundanct was incorporated into the TMS Admin Guides, and then it was moved to the TMS install Guides starting by TMS 14.4

    It is mentioned in both TMS 14.1 Release Notes and TMS 14.4 Release Notes.

  • Redundancy of the TMS with TMSXE

    Hi team,

    Since there is no redundancy of each device as VCS, MCU. I want to ask about a redundancy of MSDS on a virtual server-based computer.

    How can we create a redundancy of MSDS on server VM.

    Currently, my client bought only Cisco's TMS software and is installed on the server of the virtual computer. They would create a redundancy of TMS in case of TMS first down.

    Also, tell me if the first TMS license can be put on the 2nd TMS?

    And how wud it work with TMSXE?

    Apprecite your answer.

    Thank you


    Hi karim and Martin.

    We have released a brand new redundancy TMS 13.2 deployment guide a few days ago. The old man is very old and obsolete; Please pretend that there is not. The document should answer questions of karim.

    TMSXE and redundancy: we come through a long series of tests TMSXE 3.0.1 with a load-balanced solution TMS (two TMS servers behind a Cisco ACE 4710 appliance). Some time in the near future, we will add to the official documentation of TMSXE that this installation has been tested and is supported by Cisco.

  • Telepresence redundancy-UCS BE6K, UCS TCS, TMS, MCU

    I know I can do BE6K redundancy.

    How about TCS and TMS MCU?

    Is it possible to make redundancy on TCS and TMS MCU?


    Grouping of TCS and redundancy

    Redundancy TMS (page 2 of the following link)

    Redundancy MCU



  • Redundancy TMS - synchronize files the

    What program and the suggested method (unidirectional, bidirectional) for synchronization of local file between two redundant servers of TMS Cisco recommend?

    BTW, if I see just what are 'customizable' files, so most are by default, either does not exist or as the

    Data\Software which are just downloads the software versions.

    They can become critical if you change and depend on them :-)

    Synchronization correctly their is the right way to go, but do not be disappointed if there is nothing to synchronize :-)

  • TMS 14.5 and redundancy with F5 load balancing


    I'm looking in the installation guide for TMS 14.5 to design redundancy TMS with the F5 for one of my clients. I wonder if there is any requirement of specific network for the TMS1, TMS2 and F5 must be in the same VLAN or not. My client have a TMS with TMSPE and deploy the TMS Server 2nd in different data center and will use existing F5 load balancing. They cannot have the same VLAN as a current TMS server in the new data where 2nd MSDS server will be Center. Existing F5 load balancing is also, in the VLAN different already.

    y at - there no specific review we need to take care of the redundancy?

    Thank you


    As the TMS 14.4, TMS no longer an active/active load-balanced mode and now works as active/passive.

    You can find the details in the "Configure a redundant deployment" section of the Installation of TMS and Upgrade Guide (latest version 14.6 related).

    As long as both devices are accessible (and your F5 can route traffic to each of them according to the needs), it does not matter what VLAN, subnet or a location that each MSDS server resides on.  Information of VLAN in the guide are just one example of how it can be configured in a simple load balancing scenario.

    Remember the frequency responses and mark your question as answered as appropriate.

  • Cluster TMS


    I have 2 servers TMS lab facility. I need to make the combination between these servers with the same SQL database. I checked in google, all documents are mentioned with infront network load balancing. Because I don't have a material I don't know how the grouping between the TMS servers.

    When I asked my manager said, there is another way to do grouping without using NLB and he won't tell. BCZ I need to know about mine... which i have no idea... Please someone tell me... Here are the details...

    Primary server for the TMS (15.1) -

    Secondary server of MSDS (15.1) -

    SQL 2014 -


    You can use the LB which is the recommended method and other could be DNS (not so great)

    Please see the link below.

    Please see page 30 for the detailed explanation.

    Kind regards


  • Driver TP does redundancy MCU?


    It is claimed that TP driver can support several microcontrollers for the main use of the call for balance in the creation of a pool (if I understood). But there's just a couple of microcontrollers (any: either 2 separate 4505 x, or 2 x 5310 grouped) with calls on each, is there a way to pass calls from failure (just in case) MCU for work one?

    And another point of cleaning. As I undarstood in the documentation of a cluster of MCU 5300 provides no redundancy, because one is the master and the second is slave. Master/slave failure leads to the failure of the cluster.

    Please correct if I am wrong.

    Thank you

    Alexander Tratsevsky wrote:

    I've just found out that TMS has a so called "Automatic MCU Failover" option which could be "If conference start or MCU polling fails" [...]


    "If the start of the Conference or MCU offices fails" is a very dangerous option, since it can make TMS down permanent calls that actually are connected correctly. This happens if the TMS loses the connection to the MCU for a minute, but this does not necessarily mean that endpoints cannot connect to the MCU.

    We strongly recommend to not use "If the start of the Conference or MCU offices fails.

    Kind regards


  • Cisco TMS device virtualization

    We will virtualize the TMS device to a virtual machine, but had a few questions regarding the parameters:

    1. are there things that I have to watch what is using the same IP address?

    Let's change the name of TMS

    2. do I need generate a CSR that is new for a certificate, once I have install TMS on the new VM?

    I guess that Yes

    3. should I stop replication on our control VCS and highway regarding MSDS?

    4. any other telepresence infrastructure changes I have to make before you migrate the virtual server?

    1. Are there any things I need to watch out for in regards to using the same IP address?

    We will be changing the name of TMS

    You change the domain name FULL of server TMS, or do you mean that the actual name of the server is changing?  As long as you do not change the IP/domain name FULL you'll be fine with respect to systems added to the MSDS.  If you change the name of the server, you'll want to change it in the TMS using TMS tools.  See the most recent Administrator's guide, that I don't remember the name of the option.

    2. Do I need to generate a new CSR for a certificate once I install TMS on the new VM?

    I assume yes

    We use a wildcard certificate, so we are able to download the same certificate on all our servers no matter what they are as long as they use our domain.  Depends on your configuration.  Unless I understand this question, that I can't have the certificates for our group, just know enough to get.

    3. Should I stop replication on our VCS control and expressway in regards to TMS?

    Probably the best.

    4. Any other TelePresence infrastructure changes I need to perform prior to migrating to the virtual server?

    We have migrated our MSDS from a virtual machine to another, at the same time, adding a second server for redundancy.  As long as you don't change the IP or the FULL domain name depending on how you have your systems point to TMS, you should be fine.

  • GUID value for 14.4 TMS must be configured on F5.

    How get the 14.4 TMS GUID value must be configured on F5. 14.4 TMS upgrade guide, the value of the GUID of the TMS must be entered in the string to send to probe.

    #CREATE MONITOR for TMS KEEPALIVE THE GUID IS FOUND in TMS GUI tmsh create ltm monitor https mn-TMS-HTTPS {DEFAULT cipherlist: + SHA: + 3DES: + kEDH compatibility enabled by default - https destination *: 443 interval 5 past drifting recv 200 recv - disable 503 send "HEAD /tms/public/IsAlive.aspx/? '} {"Guid =\\r\\n" time - until line-up 0 timeout 16 username 'DOMAIN\rname'}

    Are you referring to a redundant deployment of TMS?

    If so, take a look at page 31 under the section "Configuring network load balancing."

    You will find the URL Probe in TMS with a specific GUID to this knot here:
    Administrative Tools > TMS Server Maintenance > TMS redundancy > probe URL

  • The upgrade to the will of the Sierra that software redundent

    Upgrade to Sierra will make it redundant software?

    Hello Robert,

    Thank you for using communities Support from Apple!

    I see Your ' e concerned about the software that you have installed on your Mac and its compatibility with macOS Sierra. You will need to check with the developers of the software that is installed to see if the version you have is compatible with macOS Sierra, or if there is an update available for her.  As a precaution, you can back up your Mac with Time Machine and then, if your software is not supported under macOS Sierra, just go back to your previous backup:

    Use Time Machine to back up or restore your Mac

    Take care.

  • Redundant notifications watch OS 3 Countdown Timer

    Watch 3 OS, the countdown now redundant notifications. When the timer counts down to 0, you get the normal "meter made" alert and then 15 seconds later, you also get a notification of alarm named 'COUNT_DOWN_TIME_REACHED '. It doesn't seem to be a sign of timer settings in the application settings of the watch, so I can't understand how to disable this alert redundant and boring.


    This seems to be a bug. You can report (as others have fact) to Apple here:

  • Store steel 640GO - message data error (cyclic redundancy check)


    I had the car store for a few months, so a lot of data on it.

    Today, windows detects it as a local disk and when I try to access it I get a message telling me that the disk must be formatted when I select number, I get a message saying * error (cyclic redundancy check *) data.


    I tried two other laptops, both give the same answer.

    Thank you



    It seems that something go wrong with the HARD disk partition.
    Did you try running chkdsk and to check the external HARD disc ability?
    Do this!

    Startup command box (cmd)
    You can use the command: chkdsk c: /f r + +.
    But c: means that the HARD drive or partition, you need to change this with the same letter that is assigned to the external HARD drive

  • Adding redundancy backup with time Capsules

    Are there problems associated with adding a second time Capsule to my system in order to add additional redundancy and safety of my backup options? I have a MacBook Pro and a single Capsule of 3 TB. I am looking for a non-Cloud option add extra security while maintaining the automation of the OSX TimeMachine.

    Adding a second Time Capsule works perfectly.  After that Time Machine performs a full backup of your Mac (s) on the new Time Capsule, it automatically alternates between two time Capsules backups.

    If you have the possibility of adding a USB or FireWire drive directly to your Mac, which would be a bit better set up in terms of reliability of time Machine, but probably not very convenient if you have a laptop that is moving all the time.

  • redundant names of pxi resources

    Whenever I run a VI that accesses my digitizer PXI using the VI OR-SCOPE module I find myself with many redundant instances of the resource in PXI drop down menu resource. See the image attached to the binary "niScope EX" cover for an example of what I'm describing. Why does this happen?

    Thank you


    It looks like niScope is incorrectly called.  This is where the sessions are cleaned.


Maybe you are looking for