Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Troubleshooting the Cisco TMS components
Cisco TMS Administration Guide
Page 30 of 37
4. supports SNMP
5. do not have status “No Response”, “No SNMP Response” or similar
To enable this feature:
1. Go to Administrative Tools > Network Settings.
2. Turn on the function Scan SNMP capable systems to allow quick discovery of
inaccessibility.
Furthermore, you can specify the interval, and the maximum number of missed SNMP responses
before the system will get the status No SNMP Response. If there is no response to SNMP queries,
Cisco TMS will use an HTTP connection to verify the status of the system. This feature was added in
Cisco TMS12.1.
before the system will get the status No SNMP Response. If there is no response to SNMP queries,
Cisco TMS will use an HTTP connection to verify the status of the system. This feature was added in
Cisco TMS12.1.
Symptoms
•
The statistics are empty.
•
Cisco TMS does not receive system events.
•
New systems are not automatically discovered.
How to fix
1. Make sure no other SNMP tool is running on the server, like HP Openview or other server/network
monitoring tools using Microsoft Windows’ SNMP Component.
2. Check the logs for symptoms or error messages at c:\Program
Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-watchdog.txt on the server.
3. Restarting the service or the Cisco TMS server will normally fix any problem with this service.
TMSServerDiagnosticsService
This service is responsible for checking:
•
the server disk space,
•
the database size
•
that the other services are running
A Cisco TMS ticket is opened if:
•
a service is not running
•
free disk space is less than 10%
•
the database is 90% of max size
Symptoms
Tickets are not opened if:
•
the service is not running
•
there is less than 10% free disk space
•
the database is larger than 90% of its max size
How to fix
1. Check the logs for symptoms or error messages at c:\Program
Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-TMSServerDiagnosticsService.txt on
the server.
the server.
2. Restarting the service or the Cisco TMS server will normally fix any problem with this service.