Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
This tool should only be used if, after upgrading to 14.4.2 or later, this critical ticket appears in Cisco TMS:
"Conferences with duplicate external primary keys found".
"Conferences with duplicate external primary keys found".
When the tool is accessed, all affected conferences are loaded into the page. Conferences with the same external
primary key are grouped together, and the title, owner, recurrence pattern, and a link to open the conference or
series in Cisco TMS > Booking > List Conferences are displayed.
primary key are grouped together, and the title, owner, recurrence pattern, and a link to open the conference or
series in Cisco TMS > Booking > List Conferences are displayed.
Select the correct conference from each group of conferences as only one conference in the group should exist in
Cisco TMS. Once you click SELECT, the remaining conferences in the group are deleted.
Cisco TMS. Once you click SELECT, the remaining conferences in the group are deleted.
If it is not clear which conference is the correct one, review the Exchange resource calendars for the systems
involved in the conference. If most or all of the resource calendars are in agreement with one of the duplicate
conferences, that is probably the correct one to select.
involved in the conference. If most or all of the resource calendars are in agreement with one of the duplicate
conferences, that is probably the correct one to select.
If it is still not possible to identify the correct conference, contact the conference owner.
Click VIEW LOG for a list of the conferences that have been selected/deleted. This log (log-tmstools-duplication-
resolution.txt) is located in the tmsdebug logs folder and contained in the Download Diagnostic Files download
bundle.
resolution.txt) is located in the tmsdebug logs folder and contained in the Download Diagnostic Files download
bundle.
Diagnostic Tools
SNMP Connectivity Checking Tool
When certain legacy systems are added into Cisco TMS, SNMP is used. If you are unable to add a system into Cisco
TMS you can use this tool to check whether Cisco TMS can contact the system using SNMP.
TMS you can use this tool to check whether Cisco TMS can contact the system using SNMP.
■
IP Address: IP address of the system you want to check
■
SNMP Read Community Name: The community name set in Cisco TMS > Administrative Tools >
Configuration > Network Settings > General Network Settings > SNMP Community Name which
corresponds with the community name set on the system itself.
Configuration > Network Settings > General Network Settings > SNMP Community Name which
corresponds with the community name set on the system itself.
■
SNMP Timeout (ms): Number of seconds before Cisco TMS will give up trying to contact the system via
SNMP.
SNMP.
Scan Db for Encryption Key Mismatch
■
Scan: Scan the SQL database to get a list of all the credentials which have been encrypted and are affected
by the encryption key having been changed (see ).
by the encryption key having been changed (see ).
■
Cleanup: Set all data found in the scan to default credentials for that system, or remove the values
completely.
completely.
■
Cancel: Stop the scan while it is running.
A Cisco TMS ticket is generated if the encryption key has been changed; the ticket is removed on cleanup.
Note that phone book source and WebEx credentials are not reset during cleanup.
267
Cisco TelePresence Management Suite Administrator Guide
Cisco TMS Tools