Let me quote of the TMS Install and getting started guide:
Note:Cisco TMS cannot use multiple network cards on a server: and will only bind to the first available network interface. Cisco TMS can manage a public and private network so long as the public network’s connection is further upstream from Cisco TMS, rather than being directly connected to Cisco TMS (using multiple network interface cards).
So if you talk about two different ip interfaces I say: no.
If you talk about a network adapter which can have multiple connections to two switches and which
is transparent as one ip interface to windows, why not. I assume this is what you are talking about.
Wouldnt it make more sense to add the additional interface on the sql server and connect that one to switch B?
I have seen more servers die then switches, so what do you think of forching to have a redundant SQL setup as well?
If you have high demands on redundancy I would look into a virtualized platform with failover capabilities + nice redundant server hardware + redundant network infrastructure.
If you havent read it, take a look at the TMS Server Redundancy Config Guide.
I am not 100% sure which deployment model you try follow here, but in general for two TMS
which should be up at the same time you would need a load balancer upfront, or you have
some switch over time (like changing DNS records) anyhow, then you could also replug the
TMS in the other switch, ...
What is your critical application? Conference booking, Phonebooks, statistics?
Always consider as well how deep in detail you want to get and don't forget to secure
other parts as well (like the call control (vcs), MCUs, network access itself / router / ...)
Especially advanced setups should be tested, so you definitly should look into a lab setup, as well
as use a maintenance window one day to test if your failover really properly works.
Thanks for your reply. I understand that we cannot have more than one Network Card in a server based on the documentation. I come from a network background so I am not as server saavy as I would like to be. Getting there slowly but surely. Is each physical interface (4 of them) on the one NIC considered a seperate NIC?
Our TMS servers are using a load balancer as a front end so there is a level of redundancy there.
I guess I could have explained myself better, or more specifically. I am more looking to get some redundancy for the SQL Server setup. We are currently working on getting a redudant SQL server as well, but that is a future endeavor so I am trying to work out solutions to provide a level of redundancy most specifically for that single point of failure we have in our SQL server.
Trying to investigate the ability to add teaming/bonding to the servers. This may be possible with the SQL Server but not the TMS Servers? I have read about teaming/bonding, but not extensively, so I am looking to find out if folks are doing it and if so if they have some quick guides on setting it up.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4