Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
n
Both servers use the same mechanism for certificate revokation.
Upgrading Cisco TMS
You must keep the Cisco TMS software versions on the primary and secondary servers consistent. After
upgrading the primary server, you must upgrade the secondary server as soon as possible. If the primary
server fails while the secondary server is on an older software version, you will not be able to swap the
servers until you have upgraded the secondary server to the newer Cisco TMS software version.
upgrading the primary server, you must upgrade the secondary server as soon as possible. If the primary
server fails while the secondary server is on an older software version, you will not be able to swap the
servers until you have upgraded the secondary server to the newer Cisco TMS software version.
1. Disable file replication to temporarily stop synchronizing local files.
2. Upgrade the primary server.
3. Upgrade the secondary server.
4. After the server has rebooted, log in to the Cisco TMS web application to verify that it works correctly.
5. In the Cisco TMS application go to
Administrative Tools > Configuration > Network Settings
.
6. Check that the following IP address(es) and hostnames 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
7. Stop the TMS services and set them to Manual again.
8. Enable file replication.
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.
Cisco TMS Administrator Guide (14.3)
Page 307 of 340
Redundant deployments
Deploying a hot standby