5-54
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 5 Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
BuildUnitCount
This counter represents the number of gateways that were processed in the last
build of all the configuration files. This counter also updates while processing unit
change notifications. The counter increases when a new gateway is added and
decreases when an existing gateway is deleted.
ChangeNotifications
This counter represents the total number of all the Cisco Unified Communications
Manager database change notifications that the TFTP server received. Each time
that a device configuration is updated in Cisco Unified Communications Manager
Administration, the TFTP server gets sent a database change notification to
rebuild the XML file for the updated device.
DeviceChangeNotifications
This counter represents the number of times that the TFTP server received
database change notification to create, update, or delete configuration files for
devices.
DialruleChangeNotifications
This counter represents the number of times that the TFTP server received
database change notification to create, update, or delete configuration files for
dial rules.
EncryptCount
This counter represents the number of configuration files that were encrypted.
This counter gets updated each time a configuration file is successfully encrypted
GKFoundCount
This counter represents the number of GK files that were found in the cache. This
counter gets updated each time a GK file is found in the cache
GKNotFoundCount
This counter represents the number of GK files that were not found in the cache.
This counter gets updated each time a request to get a GK file results in the cache
not finding it
HeartBeat
This counter represents the heartbeat of the TFTP server. This incremental count
indicates that the TFTP server is up and running. If the count does not increase,
this means that the TFTP server is down.
HttpConnectRequests
This counter represents the number of clients that are currently requesting the
HTTP GET file request.
HttpRequests
This counter represents the total number of file requests (such as requests for
XML configuration files, phone firmware files, audio files, and so on.) that the
HTTP server handled. This counter represents the sum total of the following
counters since the HTTP service started: RequestsProcessed, RequestsNotFound,
RequestsOverflow, RequestsAborted, and RequestsInProgress.
HttpRequestsAborted
This counter represents the total number of HTTP requests that the HTTP server.
canceled (aborted) unexpectedly. Requests could get aborted if the requesting
device cannot be reached (for instance, the device lost power) or if the file transfer
was interrupted due to network connectivity problems.
HttpRequestsNotFound
This counter represents the total number of HTTP requests where the requested
file was not found. When the HTTP server does not find the requested file, a
message gets sent to the requesting device.
HttpRequestsOverflow
This counter represents the total number of HTTP requests that were rejected
when the maximum number of allowable client connections was reached. The
requests may have arrived while the TFTP server was building the configuration
files or because of some other resource limitation. The Cisco TFTP advanced
service parameter, Maximum Serving Count, sets the maximum number of
allowable connections.
Table 5-38
Cisco TFTP Server (continued)
Counters
Counter Description
