Cisco Cisco TelePresence Management Suite (TMS) Version 15
Deploying a hot standby
Cisco TMS Redundancy Deployment Guide
Page 15 of 27
Deploying a hot standby
Keeping an additional Cisco TMS server as a warm spare in case of failure is known as the "Hot Standby"
redundancy model.This requires manual intervention if there is a failure on the primary Cisco TMS server,
and is therefore a switchover solution rather than a failover solution.
redundancy model.This requires manual intervention if there is a failure on the primary Cisco TMS server,
and is therefore a switchover solution rather than a failover solution.
One Cisco TMS server is active at any given time with this redundancy model. The hot standby server must
be kept up to date with security patches and other upgrades so that it is ready for activation within a few
minutes if the primary server fails.
be kept up to date with security patches and other upgrades so that it is ready for activation within a few
minutes if the primary server fails.
Note that the hot standby redundancy model requires the tmsng database to be located on an external SQL
server, and that the two Cisco TMS servers must be in the same Windows domain.
server, and that the two Cisco TMS servers must be in the same Windows domain.
In the instructions below the following examples are used:
Server
DNS Name
IP Address
Primary Cisco TMS Server (tms01)
tms01.example.com
10.0.0.10
Secondary Cisco TMS Server (tms02)
tms02.example.com
10.0.0.11
The examples assume that you use IPv4. If you also use IPv6, change the IPv6 addresses accordingly.
Setting up the primary Cisco TMS server
Prior to installing Cisco TMS:
1. Set up an SQL server instance on an external server.
2. Set up a DNS entry: tms.example.com pointing to the IP address of the primary server tms01 (10.0.0.10).
, but:
a. Use the "Custom" installation mode.
b. Point Cisco TMS to the external database server you used in step 1.
b. Point Cisco TMS to the external database server you used in step 1.
4. If enabling HTTPS during installation, use a certificate issued to tms.example.com.
5. After the server has rebooted, log in to the Cisco TMS web application to verify that it works correctly.
All users and managed systems must use tms.example.com when connecting to Cisco TMS. The server's
own hostname (tms01.example.com) must not be used.
own hostname (tms01.example.com) must not be used.
After verifying that the installation of Cisco TMS was successful:
1. In Cisco TMS go to
Administrative Tools > Configuration > Network Settings
.
2. Enter tms.example.com in the TMS Server Fully Qualified Host Name and TMS Server Address
(Fully Qualified Host Name or IPv4 Address) fields.
Do not use local user accounts when logging in to Cisco TMS. All user accounts must be domain accounts,
so that they are available if you have to swap to the secondary server, tms02.
so that they are available if you have to swap to the secondary server, tms02.