Customize Session Delivery Manager Event Traps

The trap event setting allows you to override the core OCSDM default event trap severities and customize them.

1. Expand the Fault Manager slider and select Trap event setting.
2. In the Select dialog box, select the SDM trap group row from the Trap groups table and click OK.
3. The following table describes the OCSDM product event types and a description that references its respective trap. If you need to customize the severity level of this trap, see the Customize Alarm Trap Severity Levels section for more information.

   Trap	Description
   apEMPluginDuplicatedRestPrefixName	The trap is generated when there is a plugin installation attempt that has the same name as an existing REST API prefix name in the system.
   apEMPluginFailedInstall	The trap is generated whenever an element manager (EM) product plugin failed to install.
   apEMPluginFailedInstallClear	The trap is generated whenever an EM product plugin failed installation status is recovered.
   apEMPluginFailedUninstall	The trap is generated whenever an EM product plugin failed to uninstall.
   apEMPluginFailedUninstallClear	The trap is generated whenever an EM product plugin failed to uninstall status is recovered.
   apEMSActivateFailure	The trap is generated when OCSDM fails to activate a configuration, whether initiated from the SOAP XML API or the OCSDM GUI for the save/activate or activate operations.
   apEMSNodeUnreachable	The trap is generated when the status of a node changes from reachable to unreachable. The trap contains the node ID of the device and the time of the event.
   apEMSNodeUnreachableClear	The trap is generated when the status of a node changes from unreachable to reachable. The trap contains the node ID of the device and the time of the event.
   apEMSSaveFailure	The trap is generated when OCSDM fails to save a configuration. The trap is generated by a save failure whether initiated by the SOAP XML API or OCSDM GUI for the save/activate, save, or offline save operations. The trap contains the node ID of the device, the start and stop time of the save configuration attempt, and the user initiating the save operation.
   apEMSDiscoveryFailure	The trap is generated whenever an error is detected during server node discovery.
   apEMSInvalidConfigDiscovered	The trap is generated whenever an invalid configuration is retrieved from a node. Additional information about the validity failure is available in the discovery log.
   apEMSInvalidConfigInventory	The trap is generated whenever an inventory check was performed and failed.
   apNNCReportingHdrAggregationFailure	This trap is depricated. Use the apNNCReportingHdrAggregationLagFailure trap. This trap is generated when an OCSDM reporting HDR aggregation task fails to keep up with incoming HDR data.
   apNNCReportingHdrAggregationLagFailure	The trap is generated when an OCSDM reporting HDR aggregation task fails to keep up with incoming HDR data.
   apNNCReportingHdrAggregationLagFailureClear	The trap is generated when a previously failed OCSDM reporting HDR aggregation task is now able to stay current with incoming HDR data.
   apNNCReportingHdrDetectionFailure	The trap is generated whenever an OCSDM reporting HDR detection task failed.
   apNNCServerUnreachable	The trap is generated whenever an OCSDM server is determined to be unreachable by another an OCSDM server configured in the same cluster.
   apNNCServerUnreachableClear	The trap is generated whenever a previously unreachable OCSDM server is determined to be reachable by another OCSDM server configured in the same cluster.