Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Troubleshooting the Cisco TMS components
Cisco TMS Administrator Guide
Page 29 of 37
The scanner process is a moderately CPU-intensive process for the server, and should be tuned
according to the need for updated system information in Cisco TMS. To scan one system takes from
two seconds up to approximately 20 seconds (worst case). This means that scanning 100 systems
might take from three minutes up to 30 minutes.
according to the need for updated system information in Cisco TMS. To scan one system takes from
two seconds up to approximately 20 seconds (worst case). This means that scanning 100 systems
might take from three minutes up to 30 minutes.
The scanner will read the system connection status and call status on every scan, but will only read
the full system configuration in intervals defined in the field System Force Refresh Interval (in
hours). The scanner will update 20 connection statuses in parallel and read five full system
configurations in parallel.
the full system configuration in intervals defined in the field System Force Refresh Interval (in
hours). The scanner will update 20 connection statuses in parallel and read five full system
configurations in parallel.
To improve response time, Cisco TMS runs an extra connection status check every 30 seconds for
systems in these categories:
systems in these categories:
Cisco TelePresence MCU
gateways
gatekeepers
border controllers
recording devices
supervisors
System types included (in addition to the categories mentioned above):
Cisco TelePresence Server (TS 7010)
Cisco TelePresence System (CTS)
Symptoms
The symptoms are that the system information and system status in Cisco TMS is outdated. Systems
not responding still have the status InCall or Idle.
not responding still have the status InCall or Idle.
How to fix
1. Check the logs for symptoms or error messages at c:\Program
Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-TMSDatabaseScanner.txt on the
server.
server.
2. Restarting the service or the Cisco TMS server will normally fix any problem with this service.
TMSLiveService
This service:
allocates conferences on the Cisco TelePresence MCU
issues the dial commands to the endpoints and the Cisco TelePresence MCU
monitors the activity of the participants during a conference
Symptoms
The call does not start, and the log in the Conference Control Center is almost empty.
You could have only one line that says “Created” in the log. You might have more lines there if the
conference has been changed – but none of them is related to launching the conference.
conference has been changed – but none of them is related to launching the conference.
How to fix
1. Check the logs for symptoms or error messages at c:\Program
Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-liveservice.txt on the server.
2. Restarting the service or the Cisco TMS server will normally fix any problem with this service.