Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Using sticky connections ensures that new connections from a client IP address are assigned to the same
Cisco TMS node that received previous connections from that address.
Cisco TMS node that received previous connections from that address.
Traffic must be forwarded to one single server, not both servers.
Other protocols
Other protocols such as SSH and FTP are always initiated from the Cisco TMS side. No special
configuration of the NLB is required for these protocols.
configuration of the NLB is required for these protocols.
Probes
A probe is a request sent from the NLB to a node to check whether a particular service is still responding.
Whenever a probe fails, the load balancer, assuming that the node is at least partially inoperative, directs all
traffic to the other node and notifies the network administrator.
traffic to the other node and notifies the network administrator.
We recommend probing:
n
TMS Scheduler (/tms/booking)
n
Cisco TMS web application (/tms)
Create a new domain service account specifically for probing.
This service account does not need any specific rights in Cisco TMS itself and can be a member of the
“Users” group only. It must, however, be allowed by IIS to authenticate and log in to Cisco TMS.
“Users” group only. It must, however, be allowed by IIS to authenticate and log in to Cisco TMS.
for a sample configuration.
Scheduled tasks
Some tasks in Cisco TMS are scheduled.
Examples include:
n
Updating phone book sources from gatekeeper registration lists
n
Pushing configuration templates to managed systems
n
Mirroring user directories
Such tasks are assigned randomly to one of the two Cisco TMS nodes.
To see which node has been assigned a task, go to the PrimaryServerId column of the SchedulerEvent table
in the tmsng database:
in the tmsng database:
Cisco TMS Administrator Guide (14.1)
Page 287 of 320
Redundant deployments
Deploying with a load balancer