Call server group thresholds are designed for your Cisco call server clusters and other logical groupings of call servers. Each call server in a cluster can play several different roles to provide failover safeguards and load balancing. The call server group thresholds apply to all call servers in a cluster.
Note: Call server group thresholds apply only to Cisco Unified Communications Manager environments.
Call server group thresholds trigger incidents when status changes exceed the Phone Status Changes metric. The Phone Status Changes incident helps you detect failover events and branch office outages. The incident also helps identify call server performance issues and costly branch office connectivity failures. Typically, the incident itself provides enough information to help you identify the affected devices and call server group. The Phone Status Changes incident helps you distinguish between endpoints that access call servers over a WAN link and endpoints that use a local cluster.
The Default call server group threshold triggers incidents when 50 percent of all devices had status changes during the reporting interval.
The following types of status changes contribute to a Phone Status Changes incident.
The percentage of endpoints that were once registered to a server in the group, but are not now registered to any server in the group, and were not observed to have been formally unregistered. The total does not include endpoints that had normal deregistration, which can occur during a restart.
The percentage of endpoints that were registered to a call server in this group, but are now registered to a different call server in the same group.
The percentage of endpoints that are registered to a call server in this group, but were not registered during the previous reporting interval.
When the threshold is exceeded, a Phone Status Changes incident appears in the Call Server Incident Details. Separate data views provide more information when you drill down into the detailed incident report.
The incident is not dependent on the similar information reported in the Phones Report. For example, when a Currently Missing Phones status change occurs, multiple devices in the Phones List can show a status of Unavailable or Lost Contact. The status of an endpoint is actually the device status at the end of the reporting interval. When a change in status occurs, the incident is created before another status change occurs. The later status is reflected in the Phones Report and is slightly out of sync with the incident. Review the Phone Details Report, which includes the Previous Status for each endpoint.
|
Copyright © 2013 CA.
All rights reserved.
|
|