Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Conferences that are scheduled to start more than 15 minutes into the future are stored in the
SchedulerEvent table as described in the
SchedulerEvent table as described in the
node will control the conference by examining the PrimaryServerId value.
Conferences scheduled to start less than 15 minutes into the future are not written to the SchedulerEvent
table, but are directly assigned to the Live Service on the node the conference was scheduled on.
table, but are directly assigned to the Live Service on the node the conference was scheduled on.
Upgrading Cisco TMS
Upgrading Cisco TMS to a later software version must be done during a maintenance window, as upgrading
will make Cisco TMS unavailable to users for a short period of time.
will make Cisco TMS unavailable to users for a short period of time.
As the two Cisco TMS nodes share a common database, they must run the same software version at all
times. It is therefore not possible to upgrade one node at a time and keep the other node operational to serve
systems and users.
times. It is therefore not possible to upgrade one node at a time and keep the other node operational to serve
systems and users.
1. Log in to both Cisco TMS Windows servers.
2. Disable file replication to temporarily stop synchronizing local files.
3. Stop all the TMS services, as well as the IIS service on both nodes.
4. Upgrade one of the nodes to the new software version. This will upgrade the tmsng database.
5. Log in to the Cisco TMS web application on this server to verify that it works correctly.
The probes on the NLB will now report that only the first Cisco TMS server is operational so all traffic will
automatically be directed to this node. Users and managed systems can now use Cisco TMS again.
automatically be directed to this node. Users and managed systems can now use Cisco TMS again.
1. Upgrade the second Cisco TMS node.
2. The installer will detect that the database has already been upgraded, and offer to continue using the
updated database: select Yes. The installer will then update the binaries and leave the database alone.
3. Log in to the Cisco TMS web application on this server to verify that it works correctly.
4. Enable file replication.
Check that the network settings have not been changed during the install process:
Cisco TMS Administrator Guide (14.1)
Page 289 of 320
Redundant deployments
Deploying with a load balancer