User manual TANDBERG TMS SERVER REDUNDANCY CONFIGURATION GUIDE 13.0

[. . . ] Cisco TMS Server Redundancy Configuration Guide D14570. 02 December 2010 Cisco Revision Notes Contents Cisco TMS Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Communication with Cisco TMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Users Communicating with Cisco TMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Cisco TMS and Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] This is achieved by specifying the machine key to be used by IIS rather then letting IIS generate its own which is the default behavior. The machinekey behavior can be controlled using the web. config file used by the Cisco TMS web application. This file is located in the wwwCisco TMS directory (default c:\program files\tandberg\tms\wwwCisco TMS) The behavior of this element is described in the following Microsoft articles http://msdn2. microsoft. com/en-us/library/w8h3skw9(VS. 71). aspx http://msdn. microsoft. com/library/default. asp?url=/library/en-us/dnpag2/html/paght000007. asp Microsoft provides sample code to generate these keys, but there are several public websites that simplify the creation of these keys for you. Some example sites are http://www. orcsweb. com/articles/aspnetmachinekey. aspx http://www. aspnetresources. com/tools/keycreator. aspx Example machinekey string: <configuration> <system. web> <machineKey validationKey='50C6CA92F369A87AB487E3678C7D229119A47F921C8266D9FB0DE2B28829 CDECDD5FEEE7CC534497A90D0AB3B8FB9F81021A7DC00ACC6F39D67EA9036C1F8733' decryptionKey='52480E9648080C4A87BB434CF281064243E3C09B003C49D0' validation='SHA1'/> </system. web> </configuration> Create a machinekey element using Microsoft's supplied methods or from the sample websites listed above. Open the web. config file under the wwwCisco TMS directory and insert the new machinekey element text under the existing <system. web> element in the document. Be sure to use the same machinekey string on all servers. Maintenance Users should regularly backup the SQL database. The interval between backups defines the maximum time window over which data would be lost. Typical installations would perform full nightly backups of the database. Please see Section 0 Backup and Recovery of the TMS database of this document for additional details on how to perform backups and restores of the Cisco TMS database. As multiple Cisco TMS servers are being used, administrators should periodically check that their file synchronization process is still functioning to ensure smooth cut-over in the case of having to use a warm spare. Cisco TMS redundancy configuration and overview Page 18 of 32 Cisco Redundancy Models for Cisco TMS Upgrading TMS All Cisco TMS servers accessing the same database must be running the same Cisco TMS version. When upgrading between Cisco TMS versions, there will be inconsistencies between different servers as each is upgraded so extra steps are required when performing Cisco TMS upgrades or patches. When performing a Cisco TMS upgrade, the following steps must be followed Plan an upgrade during a time window when Cisco TMS can be made unavailable to users as Cisco TMS will be unavailable during the duration of your upgrade. On your primary Cisco TMS server, start the installer for the Cisco TMS upgrade as normal. During this process, any updates to the SQL database will be performed. After the reboot, go into Services component of Computer Management on the server, manually stop all services whose name starts with Cisco TMS and the WWWPublishingService service. Proceed to the next server, and start the installer for the Cisco TMS upgrade the same as you did on the primary Cisco TMS server. The installer will likely restart the Cisco TMS services and WWWPublishingService and may require a reboot of the server. After the reboot, go into Services component of Computer Management on the server, manually stop all services whose name starts with Cisco TMS and the WWWPublishingSevice. On the General tab of each of the services you stopped, set startup type to Manual. After upgrading all Cisco TMS servers, log into the primary Cisco TMS's Windows console and restart all Cisco TMS services and WWWPublishingService. Secondary servers should all still have their Cisco TMS and WWWPublishingService stopped and set to manual startup. Log into the Cisco TMS website, go to Administrative Tools>Configuration>Network and change the Cisco TMS Server IPv4 Address (Local): address to the IP address of the primary Cisco TMS server. [. . . ] Active Monitoring will be handled by the Cisco TMS Server who handled the call initialization. By default, the same Cisco TMS server that was used to book a call will be the default to execute the call and all phases of the call. If a server fails, there are limitations to how active calls being handled by that server will be handled. Calls that have not begun the initialization phase or are executing on other servers will not be affected. [. . . ]