<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic TMS Cluster in TelePresence and Video Infrastructure</title>
    <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890034#M16645</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i have lab setup with 2 TMS servers . I need to do clustering between these servers with same SQL database. I have checked in google, all the documents are mentioned with Network Load Balancer infront. Since i dont have a hardware i dont know how to do the clustering in between TMS servers.&lt;/P&gt;
&lt;P&gt;when i asked my manager he said, there is one more way to do the clustering without using NLB and he wont tell. bcz i need to find out on my own .. which i have no idea.. Please anyone tell me ...Here is the details...&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Primary TMS server (15.1)-- 10.66.204.45&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Secondary TMS server (15.1)-- 10.66.204.46&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;SQL 2014-- 10.66.204.40&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 18 Mar 2019 12:46:57 GMT</pubDate>
    <dc:creator>Saravana Boobathy</dc:creator>
    <dc:date>2019-03-18T12:46:57Z</dc:date>
    <item>
      <title>TMS Cluster</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890034#M16645</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i have lab setup with 2 TMS servers . I need to do clustering between these servers with same SQL database. I have checked in google, all the documents are mentioned with Network Load Balancer infront. Since i dont have a hardware i dont know how to do the clustering in between TMS servers.&lt;/P&gt;
&lt;P&gt;when i asked my manager he said, there is one more way to do the clustering without using NLB and he wont tell. bcz i need to find out on my own .. which i have no idea.. Please anyone tell me ...Here is the details...&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Primary TMS server (15.1)-- 10.66.204.45&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Secondary TMS server (15.1)-- 10.66.204.46&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;SQL 2014-- 10.66.204.40&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 12:46:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890034#M16645</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2019-03-18T12:46:57Z</dc:date>
    </item>
    <item>
      <title>Hello,</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890035#M16646</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You can use the LB which is recommended method and other could be DNS( not so much great)&lt;/P&gt;
&lt;P&gt;Please refer the below link.&lt;/P&gt;
&lt;P&gt;https://supportforums.cisco.com/discussion/11921901/tms-redundancy&lt;/P&gt;
&lt;P&gt;Please see the page 30 for the detailed explanation.&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/install_guide/Cisco-TMS-install-guide-15-1.pdf&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Raaj&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 07:50:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890035#M16646</guid>
      <dc:creator>Rajkumar Yadav</dc:creator>
      <dc:date>2016-04-07T07:50:44Z</dc:date>
    </item>
    <item>
      <title>Hi Raaj,</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890036#M16647</link>
      <description>&lt;P&gt;Hi Raaj,&lt;/P&gt;
&lt;P&gt;Thanks for the reply. i&amp;nbsp;will try that method let you know.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 11:00:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890036#M16647</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2016-04-07T11:00:10Z</dc:date>
    </item>
    <item>
      <title>If you don't have access to</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890037#M16648</link>
      <description>&lt;P&gt;If you don't have access to an NLB or choose to not use one, you can configure TMS to use DNS, this it described&amp;nbsp;in the "Deploying a Hot Standby" section in the TMS install guide Raaj mentions on pgs 37-40.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 13:39:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890037#M16648</guid>
      <dc:creator>Patrick Sparkman</dc:creator>
      <dc:date>2016-04-07T13:39:18Z</dc:date>
    </item>
    <item>
      <title>Thanks Patrick for mentioning</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890038#M16649</link>
      <description>&lt;P&gt;Thanks Patrick for mentioning&amp;nbsp;&lt;SPAN&gt;"Deploying a Hot Standby" method.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Raaj&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 13:43:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890038#M16649</guid>
      <dc:creator>Rajkumar Yadav</dc:creator>
      <dc:date>2016-04-07T13:43:28Z</dc:date>
    </item>
    <item>
      <title>Hi All,</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890039#M16650</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;As you are discussing the TMS redundancy, I would to ask&amp;nbsp;a question about the automatic failover with NLB. &amp;nbsp; In the admin guide tms01, tms02 and NLB are in the same vlan. &amp;nbsp;Is this manadatory? &amp;nbsp;Or tms01 and tms02 can be in different vlan's and/or subnet? same question for SQL database?&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;Ahmed&lt;/P&gt;</description>
      <pubDate>Sat, 09 Apr 2016 20:00:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890039#M16650</guid>
      <dc:creator>nuinoahmed</dc:creator>
      <dc:date>2016-04-09T20:00:23Z</dc:date>
    </item>
    <item>
      <title>Thank you guys... I have done</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890040#M16651</link>
      <description>&lt;P&gt;Thank you guys... I have done the "&lt;SPAN&gt;Deploying a Hot Standby&lt;/SPAN&gt;" model and its working fine. In this model one server is up and running and another is on idle state.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;But, in my case both the TMS servers should be up and running. is there any possible way to do that ?.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2016 10:53:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890040#M16651</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2016-04-11T10:53:39Z</dc:date>
    </item>
    <item>
      <title>hi Ahmed, </title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890041#M16652</link>
      <description>&lt;P&gt;hi Ahmed,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As per the admin guide, Both TMS servers should be in same Windows Domain.&lt;/P&gt;
&lt;P&gt;i dont know about the Different VLAN/SUBNET. If you tried with that setup please let &amp;nbsp;us know what happened .. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2016 12:09:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890041#M16652</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2016-04-11T12:09:55Z</dc:date>
    </item>
    <item>
      <title>TMS redundancy use to be an</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890042#M16653</link>
      <description>&lt;P&gt;TMS redundancy use to be an active/active model, but was changed to active/passive starting with TMS 14.4. Even if the redundancy model was&amp;nbsp;active/active, without an NLB and using the hot standby method, you'd still be deploying TMS as active/passive because of the manual intervention to failover to the non active node in the case of a failure.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2016 15:29:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890042#M16653</guid>
      <dc:creator>Patrick Sparkman</dc:creator>
      <dc:date>2016-04-11T15:29:46Z</dc:date>
    </item>
    <item>
      <title>ohh ok... Thanks Patrick.. </title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890043#M16654</link>
      <description>&lt;P&gt;ohh ok... Thanks Patrick..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2016 04:42:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890043#M16654</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2016-04-12T04:42:10Z</dc:date>
    </item>
    <item>
      <title>hi guys.. i presented this</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890044#M16655</link>
      <description>&lt;P&gt;hi guys.. i presented this setup to manager..he said "the active/passive redundancy without a loabbalancer, and have "most" functionality." &amp;nbsp;... i dont know what is that...&lt;/P&gt;
&lt;P&gt;But its something to do with "cluster should have a Probe monitor to count IIS liveliness for failovers."&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Any idea ?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 12:18:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890044#M16655</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2016-04-13T12:18:59Z</dc:date>
    </item>
    <item>
      <title>TMS does have a Probe URL</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890045#M16656</link>
      <description>&lt;P&gt;&lt;/P&gt;
&lt;P&gt;TMS does have a Probe URL used for redundant deployments with the&amp;nbsp;NLB model, however the hot standby model does't have this feature.&lt;/P&gt;
&lt;P&gt;If you want, you could simply monitor TMS&amp;nbsp;to make sure it's up and running, if you have some sort of monitoring application that can login to the website and do a search for a particular string of text on the webpage.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 21:44:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890045#M16656</guid>
      <dc:creator>Patrick Sparkman</dc:creator>
      <dc:date>2016-04-13T21:44:49Z</dc:date>
    </item>
    <item>
      <title>i have done TMS Clustering</title>
      <link>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890046#M16657</link>
      <description>&lt;P&gt;i have done TMS Clustering using SQL mirror sync method... i think i got what i want...&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2016 06:58:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/telepresence-and-video-infrastructure/tms-cluster/m-p/2890046#M16657</guid>
      <dc:creator>Saravana Boobathy</dc:creator>
      <dc:date>2016-05-19T06:58:01Z</dc:date>
    </item>
  </channel>
</rss>

