Table of Contents
Advertisement
Changes from previous versions
Cisco TMS version 11.0 and 11.5 included enhancements to Cisco TMS's redundancy capabilities.
For readers who were familiar with the previous Cisco TMS version 10.0 capabilities, the new
improvements are outlined below.
Snapshots now stored in database.
Websnapshots will now be available from any Cisco TMS Server, without having to create a
fileshare to share between servers to share the snapshot jpegs
Fail-over support for ongoing conferences.
Previously if a Cisco TMS Server failed, any ongoing conferences initiated by that individual Cisco
TMS Server would lose real-time monitoring updates in Conference Control Center on other Cisco
TMS servers. Now, if a Cisco TMS Server fails, the monitoring features of any ongoing
conferences that were initiated by the failed server will fail over to a running Cisco TMS server
within 2 minutes.
DNS Hostname support for Cisco TMS addresses.
Cisco TMS server addresses now support DNS hostname for system types that support DNS
resolution. This eliminates the need to manually update management settings on managed
devices if a Cisco TMS server IP changes when doing manual fail-over as required in some
deployment scenarios.
Enforce Now management settings command.
Administrative Tools in Cisco TMS now includes an 'Enforce Now' for management settings which
will initiate an immediate update to all systems in Cisco TMS. This eases configuration updates
when doing manual fail-over as required in some deployment scenarios.
Cisco TMS Service Reporting in Administrative Tools.
The Administrative Tools page in Cisco TMS now includes status reports of services from all
Cisco TMS servers connecting to the Cisco TMS database. This allows an administrator to
monitor the health of all Cisco TMS services across multiple servers directly from Cisco TMS.
Improved database connection resiliency for services.
The service components of Cisco TMS now include greater resiliency to the database server
failing by including the ability to startup with no database online, and then implementing retries to
wait for the database server to become available.
Cisco TMS Pages are now stateless bullet removed as some elements will require consistent web
validation keys for pages to operate properly and we will recommend HTTP 'sticky sessions'.
Cisco TMS redundancy configuration and overview
Cisco Changes from previous versions
Page 11 of 32
Advertisement
Table of Contents
