cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
405
Views
0
Helpful
5
Replies

Multiple TMS with different version on a Single VCS platform

uddinabu1
Level 1
Level 1

Hi All,

Is it possible to use (configure) Multiple TMS with different version on a  Single VCS platform?

If yes, is there any interoperability issues among MCU5320, TMS, VCS and ISDN Gateway?

 

Thanks in advance

 

Uddin

1 Accepted Solution

Accepted Solutions

You can run several TMS instances and point them to a shared database for redundancy, creating a active/standby cluster.

The VCS C/E and endpoints, all can be configured with an external manager, which is used to monitor alerts, send CDR data, and alarms to.

Now as I type this out and think about it, you could possibly use multiple TMS servers, but you might get some unforeseen side affects, but only one TMS would receive the external manager data.  Both TMS servers would or could essentially be trying to control the same device and cause a conflict.  In this case, the VCS might be fine, because you're not actually controlling anything on it, just monitoring it unless you're also using it for provisioning which would cause a conflict.  I'd suggest you only run one TMS instance or cluster.

Why do you require multiple versions of TMS?

View solution in original post

5 Replies 5

Patrick Sparkman
VIP Alumni
VIP Alumni

You can only use a single TMS instance or cluster, because the VCS external manager address can point to one address.

Thanks Patrick for your quick Response.

Could you please provide more details?

TMS cluster means we can install multiple TMS and create a TMS cluster?

VCS external Manager- What do you mean here? is it VCS express or VCS Control

 

Thanks

You can run several TMS instances and point them to a shared database for redundancy, creating a active/standby cluster.

The VCS C/E and endpoints, all can be configured with an external manager, which is used to monitor alerts, send CDR data, and alarms to.

Now as I type this out and think about it, you could possibly use multiple TMS servers, but you might get some unforeseen side affects, but only one TMS would receive the external manager data.  Both TMS servers would or could essentially be trying to control the same device and cause a conflict.  In this case, the VCS might be fine, because you're not actually controlling anything on it, just monitoring it unless you're also using it for provisioning which would cause a conflict.  I'd suggest you only run one TMS instance or cluster.

Why do you require multiple versions of TMS?

Here is the more info regarding our existing VCS system:

-We have VCS 7.x, TMS 13.X, MCU, ISDN gateway at UK location

and also MPS 200, TMS11.8 in our Australian location and they are working fine so far...

Now our plan is:

Install TMS (may be latest 14.6), MCU 5320, Session Border Controller (Cisco or Avaya) instead of ISDN PRI on a test environment, once it is tested successfull, then replace MPS200 and TMS 11.8.

Is there any issue on our Plan or what is your expert advice to replace MPS 200, TMS11.8 in our Australian location?

Thanks

If you're already sharing the VCS between the UK and Australian locations without issues, than it probably would be fine.

Looking at the latest TMS documentation, MPS is still a supported MCU.  See the TMS 14.6 Admin Guide on pg 42.  The MPS is EOS, but it's replacement for per the End-of-Sale and End-of-Life Announcement, is to use either the MSE 8000 or Serial Gateway 3340.

I would suggest you upgrade both TMS instances to 14.x, take advantage of the latest features and bug fixes, just be sure to look over all the release notes from your current version up to version 14 so you're not caught off guard of any changes within TMS that might impact you.