The Cyara SNMP Notifications are documented in a collection of Management Information Bases (MIBs) that describe the traps that should be sent in given situations, and also what attributes and information those traps will contain. The MIBs are written in Abstract Notation 1 (ASN.1). These are not readily readable, but they are necessary because the MIBs should be loaded into Network Management Systems (NMS) for the easy presentation of the traps in displays.
|cyaraNotification||Critical||126.96.36.199.4.1.404188.8.131.52.0||This event is intended only to be used when a trap must be raised, but there is not yet a specific definition in the Cyara MIBs. Used for temporary extension to the notifications that the Platform can support.|
|cyaraPulseFailure||Major||184.108.40.206.4.1.404220.127.116.11.0||This alarm is raised when a test from a Cyara Pulse Campaign fails. The alarm is cleared when the next successful test for the same Pulse Campaign occurs.|
|cyaraPulseAbort||Warning||18.104.22.168.4.1.40422.214.171.124.1||This event is raised when a Pulse Campaign is aborted by the operator. Because this trap is not for an alarm, it will be raised each time an abort occurs for a Pulse Campaign, and there will be no clear trap sent.|
|cyaraPulseSatisfactory||Minor||126.96.36.199.4.1.404188.8.131.52.2||This alarm is raised when a test from a Pulse Campaign achieves a satisfactory result, instead of success. Another trap is sent with a cleared severity when the next test succeeds for the same Pulse Campaign.|
|cyaraPulseOutboundNoCalls||Critical||184.108.40.206.4.1.404220.127.116.11.3||This is a Pulse Campaign alarm raised when no calls are received before a specified timeout. The same trap, with a cleared severity, will be sent when this condition changes and a call is received within the timeout|
|cyaraPulseInternalFailure||Critical||18.104.22.168.4.1.40422.214.171.124.4||This alarm is raised when a Pulse Campaign fails to run due to a Platform internal error. Another trap is sent with a cleared severity when the next test succeeds for the same Pulse Campaign.|
|cyaraSchedulerNoCallEngines||Critical||126.96.36.199.4.1.404188.8.131.52.0||This event is raised when a scheduled Campaign fails due to no available Call Engines.|
|cyaraSchedulerDatabaseConnection||Critical||184.108.40.206.4.1.404220.127.116.11.1||This alarm is raised when the connection to the database has failed. A corresponding clear trap will be sent once the database connection is restored.|
Cyara SNMP MIBs
The structure of the Cyara MIBs is as shown below:
CYARA-NOTIFICATION-MIB defines the general format and
content of the SNMP traps. Traps sent from any other module must, at least,
support the trap definition in the
Cyara Notification Structure and Content
All Cyara SNMP traps share some common attributes to describe some commonly needed information. This information includes an identifier, a description of why the trap has been sent, where it comes from, and what component it affects.
More specific attributes that describe the trap for the particular situation can also be attached.
The following attributes are shared among all Cyara SNMP traps and the content includes the following fields:
The cyaraNotifIndex Field: This field provides an index for the notification. This index is only unique over the set of notifications that are raised for the current instance of the notification service. It would not be unique across multiple notification services, or between one invocation of the service and the next.
The cyaraNotifIdentifier Field: This field provides a unique identifier for the notification over all instances of all notification services. It can be used to correlate state changes for an alarm notification. The field is actually a GUID represented as a Display string.
The cyaraNotifSummary Field: This field provides a brief description of the event that the trap has been raised for.
The cyaraNotifDateTime Field: A date and time when the notification was raised.
- cleared(1): The event indicates the condition is now normal.
- indeterminate(2): The event indicates a condition whose effect on the service is indeterminate.
- critical(3): The event indicates that service is heavily affected or completely disabled.
- major(4): The event indicates that service is affected and major/important function is affected.
- minor(5): The event indicates a condition where service is affected but only partial/non-critical function is affected.
- warning(6): The event indicates the condition deserves attention but operation is unaffected.
- informational(7): The event is purely informational and has no alarm state.
When a trap is received that has a status of indeterminate, critical, major, minor, or warning, it is the start of an alarmed state. The trap will have an identifier that does not match any other event.
When a trap is received that has a severity of cleared with an identifier that matches a previously raised alarm identifier, then that alarm is now cleared.
When a trap is received with a severity of informational, that trap represents an event and has no alarm state (do not expect a clear).
The cyaraNotifComponent Field: This field provides a reference
to the Cyara managed object that raised the event. The value expected for this
object identifier comes from the
The cyaraNotifSourceUri Field: A Uniform Resource Identifier
(URI) represented as a
DisplayString. The value of this field identifies
which Cyara Platform component raised the event. Combined with the
cyaraNotifComponent, it should allow the source of
the event (and also the component that is currently alarmed) to be identified.