Cisco Cisco TelePresence Management Suite (TMS) Version 15
Deploying a hot standby
Cisco TMS Redundancy Deployment Guide
Page 17 of 27
1. Upgrade the primary server.
2. Upgrade the secondary server.
3. After the server has rebooted, log in to the Cisco TMS web application to verify that it works correctly.
4. In the Cisco TMS application go to
Administrative Tools > Configuration > Network Settings
.
5. Check that the following IP address(es) and host names are set to IP address: 10.0.0.10 and hostname:
tms.example.com:
l
Event Notification >
SNMP Traphost IP Address
l
Advanced Network Settings for Systems on Internal LAN: all fields
l
Advanced Network Settings for Systems on Public Internet/Behind Firewall
6. Stop the TMS services and set them to Manual again.
Recovery if the primary server fails
If the primary server: tms01 fails and becomes unusable, changing the secondary server: tms02 into an
operational state will take no more than a few minutes.
operational state will take no more than a few minutes.
1. Unplug tms01 from the network.
2. Change the IP address of tms02 to the old IP address of tms01, for example 10.0.0.10.
3. Verify that tms02 is reachable on its new IP address.
4. Open the TMS Tools application and go to
Configuration > Change DB Connect Settings
.
5. Click OK to verify that tms02 still has the correct password, as the password to the database might have
changed since you initially set up tms02.
6. In the Services Management Console:
a. Change the Startup Type of all the TMS services and the World Wide Web Publishing Service to
Automatic.
b. Start the services.
Tms02 is now the active Cisco TMS server. As you have instructed managed systems to use
tms.example.com when communicating with Cisco TMS, no reconfiguration is needed on the managed
systems themselves.
tms.example.com when communicating with Cisco TMS, no reconfiguration is needed on the managed
systems themselves.
To verify that tms02 operates correctly:
1. Schedule a short conference two minutes into the future.
2. See that it launches and is torn down as expected.
3. Check that you can monitor it using the
Conference Control Center
.
4. Check that Cisco TMS generates a call detail record (CDR) for the conference.
To verify that Cisco TMS is communicating with systems:
1. Wait approximately 20 minutes for the TMS Database Scanner Service to complete a full run.
2. Go to
Systems > System Overview
in Cisco TMS.
3. Select all the systems in the tree to the left, and select Network Settings > TMS To System
Connectivity in the tree to the right.
4. Click View and then check that no systems have their Status set to NoResponse.
Note that in
Administrative Tools > Server Maintenance > TMS Service Status
you will see the services
for both servers. Click on Clear List to remove the stopped services on tms01 from the list.