The aim of Cyara SNMP Support is to send notifications of issues that it can detect itself. This includes the failure of a Pulse Campaign, or the inability to make a database connection. However, these notifications may not reach an NMS if critical parts of the Platform cannot perform.
This section describes how to use MIBs supported by the Windows SNMP agent to notify the NMS of a problem when the Cyara SNMP is not able to.
A scenario where this may occur is when hosts, networks, resources, or Cyara services fail and break the Platform to the extent that it is not fully operational or cannot detect the problem or pass on the notification.
Monitoring Cyara Platform Hosts
Cyara Platform hosts need to be monitored to ensure they are all up and running. The NMS can be set to regularly poll the standard MIB-II system group attributes. This should determine when any host is unavailable and raise an alarm.
- Host that the Voice Scheduler is running on
- Host that the Omni Scheduler is running on
- Host for the Platform database
- Hosts for each Call Engine
- Host for Notification Service
- Hosts for Portal
- Host for any shared folders used for CE/SE operations
The Cyara Platform functions may be fewer than this, as multiple
services may run on a single host. Vital host statistics such as available
memory, CPU utilization, and so on can be monitored by periodically sampling
HOST-RESOURCES-MIB supported by the Windows SNMP
Monitoring Cyara Platform Services
Each Cyara Platform host can support several Cyara services. Although
the host may be active and healthy according to the
HOST-RESOURCES-MIB, the specific Cyara service may be
down. To monitor the health of the Platform, the services must also be
periodically checked to ensure they are running.
Information about the services being run by a host is available
through the Windows SNMP agent. The
LANMGR-MIB is supported and provides services
information in the svSvcTable.
Each service should be monitored through the
LANMGR-MIB svSvcTable on the host it is running on.