Using iDRAC, an out-of-band server management and
monitoring tool, the SNMP traps/alerts can be recorded in the log.
However, from a host OS systems management using in-band agent perspective,
the preference is more on the SNMP alert received from the host OS
than the traps received from iDRAC. When an SNMP alert is received
from iDRAC, it would be challenging to determine the source of the
alert as it is from an iDRAC IP and not the system IP.
Starting from 14th generation of servers, all events that have
the "SNMP Trap" option as the target (in the Alerts page or in the
equivalent RACADM or WSMAN interfaces) can be received as SNMP trap
through the OS using the iDRAC Service Module. Starting iSM 3.0.1
or later and iDRAC firmware 3.0.0 or later, this feature does not
require iSM LCL replication feature to be enabled. Only the events
logged in the LC log after the iDRAC Service Module was installed
are sent as SNMP traps.
Using iDRAC Service Module 2.3 or later, you can receive
SNMP alerts from the host OS which is similar to the alerts that are
generated by iDRAC.
NOTE: By default this
feature is disabled. Though the In-band SNMP alerting mechanism can
coexist along with iDRAC SNMP alerting mechanism, the recorded logs
may have redundant SNMP alerts from both the sources. It is recommended
to either use the in-band or out-of-band option, instead of using
both.
NOTE: You can use the
In-band SNMP feature on 12th generation of Dell’s PowerEdge Servers
or later with a minimum iDRAC firmware version 2.30.30.30.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\