
Dell iDRAC Service Module 5.0.1.0 User’s Guide
Mapping iDRAC Lifecycle Logs to OMSA and OMSS SNMP alerts
The ability to map iDRAC Lifecycle logs to OMSA and OMSS SNMP alert is disabled by default and can be enabled only when the existing Host SNMP Alerts feature is enabled. Configure the feature using either the iDRAC RACADM interface or the iSM Installer Modify option. When enabled, the feature converts iDRAC Lifecycle logs records selected as SNMP alerts into corresponding OMSA and OMSS SNMP alerts. The resulting OMSA or OMSS alert Object Identifier (OID) corresponds to the OMSA or OMSS product, and the rest of the alert varbinds are those of the iDRAC.
The iSM SNMP subagent forwards the mapped alerts to the SNMP trap destination configured on the host operating system. iSM does not add or modify any trap destination that is configured by the administrator, and does not create any outbound firewall rules to open User Datagram Protocol (UDP) ports corresponding to SNMP traps.
When the Host SNMP OMSA Alerts feature is disabled, the existing feature of forwarding iDRAC LifeCycle Logs as SNMP traps is active. The following table indicates the various feature states:
| iDRAC.ServiceModule. HostSNMPAlert | iDRAC.ServiceModule. HostSNMPOMSAAlert | Remarks |
|---|---|---|
| Yes | Yes | iDRAC to OMSA SNMP map is trapped and sent to destination. |
| Yes | No | Only iDRAC alerts are sent to destination (default condition). |
| No | Yes | NA |
| No | No | No alert is mapped and sent to any destination. |
iSM auto disables this new feature when it detects the OMSA service running on the host operating system to avoid duplicate traps at the trap destination.
Based on the above feature configuration, iSM forwards the received iDRAC alert to the trap destination having any of the following Object Identifiers:
- iDRAC Enterprise Object Identifier (existing feature)
- OMSA/OMSS Enterprise Object Identifier (introduced from iSM 4.1.0.0 onwards)