Cisco Redundancy Models for Cisco TMS
Cisco TMS redundancy configuration and overview
Page 17 of 32
Installation
Using multiple Cisco TMS Servers requires the use of a separate SQL server, either stand-alone or
clustered.
Stand-alone SQL Server
The separate SQL Server should be installed and operational prior to installing Cisco TMS. You do not
need to perform any special operations on the SQL server prior to Cisco TMS installation except
‘mixed mode authentication’ must be enabled.
Clustered SQL Server
Configuring a Microsoft SQL Cluster is outside the scope of this document. Please refer to Microsoft’s
documentation for additional details
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
Prior to installing Cisco TMS, the SQL Cluster should be active and must have the Virtual SQL Server
installed and active that you wish to use for Cisco TMS. The Virtual SQL Server will have an instance
name and IP Address to reach the SQL server and ‘mixed mode authentication’ must be enabled.
Installing the Cisco TMS servers
Domain Requirements.
Since you will be using multiple Cisco TMS servers, all Cisco TMS servers must be a member of a
domain, and all Cisco TMS users should be a member of that domain or a domain trusted by the
Cisco TMS server’s domain. Using Windows local user accounts is not supported when using multiple
Cisco TMS servers.
Installing primary TMS application.
Once the SQL Server is configured, begin by installing Cisco TMS on what is to be the primary Cisco
TMS server. By choosing custom during installation, the program allows you to select the existing
remote SQL server as part of the installation. Select or enter the instance name or IP address of the
SQL Server (Virtual SQL Server if using clustering). The installation program will fully handle the
configuration of the database on the existing SQL server. The database files will be created per the
database defaults of the SQL Server. The Cisco TMS Tools application installed with Cisco TMS
should be used to update SQL connection settings post-install if required.
Installing secondary TMS application.
Once the primary server is installed, you may install additional Cisco TMS servers to be your inactive
‘warm standby’ servers. Each of the warm stand-by servers will be a separate server, with its own IP
address and machine name. Perform the installation on the secondary servers following the same
steps as used on the primary Cisco TMS server. Each Cisco TMS install must be consistent with the
other servers, so you must use the same local file paths on each server installation (Example: Cisco
TMS installation path and Software Directory). After the Cisco TMS installation completes, you will be
prompted to reboot the server. Reboot the server. After the server restarts, you must make the Cisco
TMS portion of the server inactive by stopping all the Cisco TMS and Web services and setting them
to manual startup. Open the Services tool from Administrative Tools in the Windows smart menu, and
stop all services whose name starts with Cisco TMS and the WWWPublishingService service. Right-
click on each of these services and select Properties. On the General tab of each of the services you
stopped, set startup type to Manual. The server now has Cisco TMS installed, but is not actively
running. Repeat these steps for each additional ‘warm spare’ server you wish to have. When
promoting a server to be the primary Cisco TMS server, you should change these services back to
Automatic so they restart on server power-up. Only the active primary Cisco TMS server should have
it’s services set to Automatic.
Custom file synchronization.
Part of the Cisco TMS installation will consist of files added or customized by users and
administrators. These files must be synchronized to all Cisco TMS servers being used. The setup of
this synchronization should be configured as part of the installation process. Please see Section
0
Customer specific TMS Files
for more details on these files and methods to synchronize them
between servers.
Set primary TMS address
After all the warm spares have been installed, log into the primary Cisco TMS server’s website, go to
Administrative Tools>Configuration>Network and change the Cisco TMS Server IPv4 Address (Local):
