Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
n
Green: Status is OK.
n
Orange: The diagnostics task has not started yet.
n
Red: The system has a warning or a critical error.
n
Gray: The diagnostics task is idle or disabled.
n
Blue: The diagnostics task is in-progress.
Diagnostics are run on these systems:
n
User Repository
n
Device Repository
n
User Preference, imported from the user repository
n
Phone Book
n
FindMe, if in use
n
Diagnostics
n
CMR (Collaboration Meeting Room)
VCS Communication
This section displays information for each Cisco VCS and cluster names.
Last Call Time is the date and time of the last communication between the Cisco VCS and the Cisco TMS.
Conference Diagnostics
In Cisco TMS:
Administrative Tools > Diagnostics > Conference Diagnostics
This page allows administrators to identify and fix problems with existing conferences.
When to run diagnostics
As the task is resource intensive we recommend running it outside of normal business hours. The task can
take a long time to run, depending on the number of future conferences.
take a long time to run, depending on the number of future conferences.
While diagnostics can be used at any time, it is particularly useful after you have made changes to your
deployment such as:
deployment such as:
n
Dial plan:
l
Endpoints that were H.323 are moved to SIP.
l
The number range is changed on a bridge.
n
Infrastructure:
l
Conference bridges are moved behind TelePresence Conductor.
l
MCUs are swapped for TelePresence Server.
l
Migrating from a Cisco VCS to a Unified CM-based deployment.
How the diagnostics work
When Run Diagnostics is clicked, Cisco TMS checks the following for all future scheduled conferences:
n
All participants exist in the database and are bookable.
n
).
When an issue is found, the diagnostics status of the conference is set to Reported.
Cisco TelePresence Management Suite Administrator Guide (14.6)
Page 298 of 344
Administrative Tools
Diagnostics