How to synchronize alarms with the DSC
In this section:
This section provides an overview of alarm synchronization using the REST API. For more information about alarm synchronization on the DSC, refer to the DSC Alarms Guide, Alarm Synchronization.
Alarm synchronization allows all active alarms stored in the Active Trap List on the DSC to be kept in sync with an Element Management System (EMS) or other external client manager, at all times. The synchronization is provided using the REpresentational State Transfer (REST) Application Program Interface (API).
This feature allows the DSC REST API clients to perform the following:
To receive an SNMP trap, a host needs to be entered in the Trap Host List. This can be accomplished through the Web UI (refer to SNMP Configuration) or SNMP if EMS Access is enabled (refer to Configuring Community Directives).
To enable the alarm synchronization on the DSC, refer to the .
Once the alarm synchronization is enabled, the DSC stores all active traps in the Web UI under SNMP > Active Trap List.
For more information about DSC alarms, refer to the . The Alarms guide describes all events including alarms, warnings, notifications, clearing events, and Intelligent Platform Management Interface (IPMI) hardware sensor alarms recorded by the DSC Platform as well as possible troubleshooting actions.
The following figure shows an example of the EMS sending requests through the REST API to the DSC, and the DSC sending SNMP messages to the EMS.
The REST API handlers will check that the Active Traps attribute and the Single Trap Stream attribute are set for each incoming HTTP request and will return an error in response to the HTTP request if the DSC is not properly configured for this feature.
The HTTP requests coming from EMS with the goal of alarm synchronization are processed by an addition to DSC REST API - Alarm Sync subsystem.
If you send an HTTP POST request from the EMS and the network is overloaded or there are connectivity issues, the EMS may not receive the corresponding DSC SNMP Trap response. To check if your request was successful, you can send another request to the DSC using HTTP GET to confirm changes.
If an alarm is manually cleared through the EMS, it will be removed from the Active Trap List and will not be returned in the HTTP GET response, but will still be visible under the cleared bucket list on the DSC Web UI.
If an alarm was manually cleared on the DSC before the Active Traps attribute was enabled, the corresponding clear notification will not be sent to the EMS after the Active Traps attribute is enabled.
If you require a previously cleared alarm to be sent to the EMS, you must manually restore the alarm from the Web UI (refer to Restoring an Alarm), so the DSC can send a new trap notification to the EMS.
The following table lists the REST API commands: