Cluster TMS

Similar Questions

• TMS - XE Cluster Network Share size

  Hello

  Can't seem to find any guidance of sizing for Cluster TMS network sharing - XE. Will a hybrid deployment of CMR size medium with up to 25 endpoints re...

  TIA

  Hello

  Our documentation does not list a specific size for network sharing, as it varies according to the size of your deployment and the amount of data being synchronized.  However, you can provide about 200 MB of storage by managed endpoint. If you want you can hire TAC or your local Cisco team for details or confirmation.

  Manish

• TMS with a cluster of conductor?

  Hi, would appreciate any guidance.

  I built a group of conductor that I added to TMS for the purpose of planning appeals.

  I'm afraid that TMS does not seem very "cluster aware". All 3 devices (2 drivers + driver managed MCU) appear in the tab MCU, which does ' t seems correct.

  How a failure of conductor is managed by TMS? It is based on the standard MCU failover?

  How managed MCU port count works in a cluster?

  Thank you!

  Clusters of TMS and conductor is not currently supported.

  Sent by Cisco Support technique iPad App

• TMSXE connection to the Cluster of TMS

  When you run the TMSXE Setup Wizard can't connect to TMS by using its FULL VIP domain name. If I use each tms server name individually this works, but not when you use the cluster name or address VIP (behind F5 NLB)

  I can connect to the site of TMS using the FULL name of the VIP

  Don't know what else to check. Any help would be appreciated.

  Note: All applications run on different Windows servers, even VLAN.

  Thank you

  Hi Frank,.

  Please let me know is does not connect or there is a problem with authentication.

  Have you tried to access the MSDS on the web interface of the server tmsxe, it worked?

  Kind regards

  Vivek

• Extend the current TMS Cluster with two new server

  Hello

  We currently have a cluster of two TMS-Server (13.2.1) installed on a W2K3 Server with a database on a SQL-Server separat

  To have a smooth migration, we thought the following procedure.

  Addition of two new server with W2K8 R2 by installing a TMS 13.2.1 to the cluster with access to the same database.

  After a while remove the two old server and upgrade to TMS14 (updated TMSPE in advance).

  Unfortunately, we get the message, as seen in the PNG-attachment during the installation of the first server in new.

  Anyone know if we could proceed as described above?

  Is the message because of the different operating system. If I click on 'Yes' former TMS-server still works?

  Thank you

  Concerning

  Ingo

  Hello

  The error message is misleading and can be safely ignored, and you can continue with the installation of the new TMS nodes. It was deleted in 14.0 TMS, see bug CSCui34702.

  Kind regards

  Kjetil

• TMS and TCS Cluster

  We had two boxes of telepresence Content Server, as separate in TMS for a while now (TCS01 and TCS02)

  Recently, we grouped matches of two.  A day or two after having done this, the TCS02 device appears in TMS with an error "incorrect authentication information.  TCS01 is fine.

  Would we still followed the two devices separately in the TMS, or should we now be treated as a single device (via the pole DNS entry)?  Or is there a problem with TCS02 do we do?

  Hi Wayne,

  Try the steps below and let me know your comments.

  Here we must activate and change the API password in CHT management settings

  set a new password TCS (which is used for adding the TCS to the TMS
  Server)
  Connect to the web interface of TCS¹s go to

  Management > Configuration > Site Settings > API

  Ensure that the API is enabled. Choose a new password, and then save it.

  The user and the password in the settings of the API is the same user name and password
  who to be used when adding the TCS to the TMS

  Regrads

  Shyam

• After adding a subscriber to the CUCM, Sx20 Sip URI field empty cluster

  Hello

  After adding a subscriber to CUCM Cluster, all the restarted cluster devices, then sip uri field sx20 features seemed to "Null", simply enter the SIP registrar one by one for all devices sx20 IP.  Anyone else facing this problem? In my view, is not normal behavior.  What are the causes of this problem? Waiting for your opinions.

  CUCM system version: 9.1.2.13057 - 1

  The SX20 software version: TC7.2.0.aea6651

  //

  Thanks in advance

  Hi Dani

  Greetings of the day!

  Ideally this should not take place. I suspect this is something at the end of Manager at the origin of the problem.

  You make changes to the device pool after adding Subscriber to CUCM Cluster?

  Modifications were made to the Group Manager call?

  Replication between the call manager Publisher and Subscriber is any good?

  The SX20 is supplied by TMS devices?

  You should check the logs of provisioning of the endpoint to enter the cause for it.

  Concerning

  Radhika Sajan

• Clustered servers listed in TMS

  How managing licenses for control of VCS MSE 8510, TCS, cluster, VCS Expressway TMS.  Each slave/peers must be added in the TMS or that the master should be added?  I know for the MSE 8510 it says not to add the slave to MSDS, only add that the master, you can access the slave by the master in TMS via a tab group.  Is it the same way for other devices, and the slave/peers take device licenses in MSDS?

  Thanks, Patrick

  Hi Patrick,

  I can tell you that VCS and it is each VCS must be added to the MSDS. When there are cluster and you click the Cluster tab and that VCS you have selected, you will see the cluster information to include peer global cluster name under 'Settings of Cluster' and then all VCS cluster under "Cluster." According to which VCS you have selected, you will see which is the 'master' and who is a 'slave' in the pane "Peer Cluster.

  As far as TCS is going, and I assume you mean TANDBERG Content Server, I need for work research since I'll admit that I don't have a TCS cluster in my lab. However, I would remind each TCS must be added to the TMS as well and it will appear as does the VCS in TMS. And this should be covered in their documentation, i.e. Add TCSs and/or TCS clusters to MSDS.

  see you soon,

  Dale

• Removing VCS of TMS and TMSPE migration problem

  We prepare to start using TMSPE, however it must first disable replication on all VCS via MSD MSD Agent.  There is a VCS that have failed has been deleted afterwards, but we cannot delete TMS because TMS Agent replication is enabled.  We cannot have the Agent MSDS tab to disable the replication because the VCS is offline (i.e. it was removed) - it just goes to the 'Connection' tab whenever I try.

  So, how can we migrate to TMSPE if TMS don't delete us the VCS in offline mode or at least turn Replication Agent MSDS for it?

  Hey Nick

  Try to run this SQL query:

  USE TMSNG

  UPDATE field_SystemField SET BolValue = 0 WHERE field_Field_Id = 1072

  UPDATE Cluster SET EnforceTMSAgentDataReplication = 0

  This should clear the replication on all VCs added to the TMS (even the zombie ones like the one you have), once it is executed, you can try to purge the VCS.

  / Magnus

• EX90 using TMS disorders directory

  Hello

  I use an EX90 (TC5.1.4.295090) registered in the VCS - Cluster (X7.1) and using the TMS-Server ServerPhonebook (13.2%).

  I have also several C20 (TC5.1.3.292001) registert on VCS Cluster.

  For all settings, I did on TMS Server-directory entries.

  EX90 using some of the C20 can be composed, they appear with H323, some C20 may be composed, they are shonw with SIP, numbers on the EX90.

  Why is there a different behaivor between these systems? Each of them are configured the same way!

  Can someone help me out here?

  Kind regards

  Martin

  Hello

  Is the manual list the only directory located on the EX90

  The c20 are in the same area of intellectual property in MSDS?

  If you can see the intellectual property entry in the phone book and when you dial the number, you can not... Try to set the call for directly just installation mode to see if it works then change back. If it works with the installation of the direct call I look at the events on the vcs log and see what happens.

  You have an installation of the fact of all your entries in the directory as H323, but again, they appear as definition SIP on the ex90. How does this look on the c20, it's when you do the same search?

  I'm imagining how set you up, but what you see compared to how say you that you have configured it makes no sense

  I wish I could see it at this point. The screenshots you want to share? Otherwise, I think that a case of rapid tac should do the trick...

  / Magnus

  Sent by Cisco Support technique iPhone App

• Questions of FindMe Provisioning/user between TMS & VCS

  Hello

  I have what seems to be a problem in service between TMS and VCS.

  Using TMS to import users from AD (from 2 domains of x), everything seems to work, and can see the users in the provisioning of TMS directory. MOVI users use AD authentication which connect properly.

  User login also works very well on the VCS (with connection LDAP AD). However when to call the findme users address VCS does not recognize the configured users? If you navigate in user accounts, the user is not displayed, if you run a search on VCS (users account address name or findme) findme VCS find the user. Once the user has been found and open if you click on save button (without changing details), the user will then appear in the VCS user accounts section and findme works correctly.

  We use the TMS 13.1.1 and VCS x7.0.2 (Cluster).

  I would like to know if you have solved your problems or you are still having problems? Any suggestions for help would be appreciated.

  Thank you

  Matt

  Hi Matthew.

  Findme users must fill in the "user accounts".

  But you must make sure that the VCS 'Cluster name' matches the 'SIP server address' in TMS.

  TMS:

  VCS:

  I hope this helps.

  / Magnus

• VCS - C cluster and Cluster VCS-E with Movi 4.6 register and call interruption

  Hi all

  We have VCS - C cluster and Cluster VCS-E with Movi 4.6 register and call interruptions. The point is, if the appeal or record comes from the Internet. We have the sip proxy model vcse--> vcs - c record. The strange point is, if run us in mode not cluster with only 1 vcs - c, then the call works very well or so over 1 minute. We also have findme. The call internal registered locally (VCSC) works as well) the case appears if the active VCS - c cluster and the movi has been listed in the subzone of the crossing of VCS - c
  VCS versions are x.7.2.2 and tms 14.2.2
  Thx for your comments

  Sent by Cisco Support technique iPhone App

  Hi friend

  The issue you are experiencing is a known limit of Jabber of telepresence. This happens when registration of the device is transmitted by proxy to the VCS control, where VCS are clusters. Probably what is happening:

  -Jabber client records through the fast track to a control in the area of the highway crossing.

  -L' check requires authentication

  -When the customer registers again every minute (registration of SIP (re) process normal), the registration request is sent to one of the other controls in the cluster.

  -The customer then completes the current record and authenticates back to the other control

  -The client (Jabber) will tear down the ongoing call when there is re - authenticate registration

  This problem is resolved in the current version for Jabber for iPad. The current version of Jabber for TelePresence still has this problem. Default: CSCud17952

  Another user has reported the same issue. See the following:

  https://supportforums.Cisco.com/message/3967325#3967325

  Zachary Colton gave the answer. I simply copied his explanation and pasted here.

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

• Resilliency planning TMS with driver

  Hi all

  We plan to put our cluster 8710 2 blades behind the conductor, now programmed with WebEx conferences are supported. We also add an additional 8710.

  Here is what I intended with respect to the design of driver:

  Service preference

  Hen Bridge 1-8710 cluster

  Marked for planning

  Used for the CMR / appointment conferences only failing 8710 in pool 2

  Blade 2-8710 pool deck

  Unmarked for planning

  Used for only scheduled conferences if 8710 cluster in pool 1 fails

  If an existing scheduled conference is set to start at, say 10:00 and 09:00 8710 at the Bridge Pool 1 cluster fails, conductor forward this conference automatically to the Bridge Pool 2?

  We all want CMR / appointment conferences to automatically use the default Bridge Pool 2 and don't use Bridge Pool 1 if the 8710 in Bridge Pool 2 fails.

  The above version works for my scenario?

  What you have above, is correct for the planning, see example 2 of the planning section of the examples of the conductor with the TMS Deployment Guide.  However, in the case of a failover bridge, TMS does not guarantee that there are enough resources as the secondary bridge is shared with the announcement of conferences ad hoc it is not enabled for the planning, so TMS will monitor not his ability to do that there are enough resources for scheduled conferences.

  Regarding your failover scenario, if a bridge fails, conductor detects this and start to use either the next bridge in the pool or service preferences.  I'm not sure of the time, but it will happen in a minute or two.

  However, you will need an additional service for RMC preference / conferences appointment containing the pools two bridge in order reverse just like what you listed, but in this case, none of the bridges will be marked for planning.

• Question to the Cluster of conductor

  Hi all

  Just need some ideas:

  We have a Cluster of conductor, some behind MCU and TMS. Booking is running on MSDS / conductor. All have SW-latest Versions.
  TMS can handle only a single conductor of the Cluster. Okay, all right.
  But what happened if this driver is down with scheduled conferences? Is it possible to send the reservation as soon as possible to the cluster of conductor a store there? Solutions or workarounds?

  Thank you very much!

  Sent by Cisco Support technique iPad App

  Hi Dirk,

  Welcome to Cisco Support Community!

  As you said correctly, when you have a cluster of conductor, TMS is not able to recognize all members of the cluster, as well as a conductor (usually the main one) will be managed and demand by TMS. If the driver fails, when a scheduled conference reached the moment to start, TMS will be able to push the Conference to the driver, so that the conference will fail.

  Unfortunately, right now, you don't have any what automatic method to push the Conference to an another counterpart of conductor in the cluster, however, as a workaround, you can manually push the Conference to another position of conductor in this method:

  • Raise your driver cluster normally according to the Cisco documentation
  • Add only the counterpart of principal conductor to TMS
  • Configure TMS to follow the system using the IP address instead of the MAC address. You can find this configuration in "system > Navigator ', tab 'connection '.
  • Configure your TMS or any server monitoring for you advice (by e-mail or by using any other method) when the conductor comes down
  • When you are told that the conductor is down, go to TMS in ' system > Navigator ', select the conductor, go to the "Connection" tab and change the IP address of you're the conductor, put the IP of another position of conductor in the cluster. So TMS will push the forthcoming conferences of the annex to this peer of conductor
  • When the principal driver is back, go to TMS and set the IP address of the back of a main conductor. So the next regular conferences will be pushed to the main driver.

  It is important to point out that, obviously, if one starts regular Conference right in time when the driver is down, before you change the IP in TMS, then this conference will fail. You will probably have to reschedule the Conference manually.

  Although this good method works very well for our customer, it is important to inform you that it is not an official Cisco solution (as I know). So I personally suggest you to test and certify yourself before appling to your environment. Personally, I don't like to suggest informal recommendations of Cisco, but I think it's something interesting to consider.

  Sorry for the delay in answering your question.  =)

  I hope this helps.

  Paulo Souza

  Please note the useful answers and do not forget to mark questions resolved as "responded."

• Where TMS put my back?

  Hello

  I used to perform a backup on our infrastructure (cluster VCS - C and E) devices that are added in TMS, TMS devices...

  TMS said that the backup was made, but where he put on the back of the files? I'm assuming that I could run a backup every week / every time I make a change and the store then those files on a file share somewhere in case I ever needed to do a restore...

  Thanks for the help!

  This has been requested before :) - see https://supportforums.cisco.com/discussion/11510741/tms-backup-question

  To my pile of VCS, I much prefer to create backups system on individual VCS itself instead of TMS before doing any update, changes etc.

  /Jens

  Please note the answers and score the questions as "answered" as appropriate.