1 Rookie
•
27 Posts
0
162
February 21st, 2024 07:22
OpenManage Email notification show wrong IP address
Hello,
I have such problem, that email notification sent from dell openmanage shows the wrong ip address of the affected server, i.e. it shows:
Severity Critical
Device Sent from <-- here is correct afected server name
Device IP <-- here is the IP address of the Openmanage server and not the affected server.
No Events found!
DELL-Young E
Moderator
•
5.3K Posts
0
March 9th, 2025 04:52
Please confirm if OME had iDRAC devices discovered with SNMP settings selected. In OME GUI you should have the device managed state as "Managed with Alerts".
Then check if Fan events generate SNMP traps and forward them to OME IP. Run a test event in iDRAC and OME should generate the syslog event with the source device iDRAC IP . I tested it in the lab and it works for me (iDRAC ip was 172.16.xxx.xxx).
I suspect all the events you getting are not from devices, but rather actual OME events. For example, CDEV6131 is not an iDRAC issue, it is OME losing connection to the device.
[…]Syslog message: LOCAL3.CRIT: 2025-03-07T06:24:44.942895+00:00 openmanage-enterprise EEMI System Health event from device with { IP } 172.16.xxx.xxx{ HostName } localhost.localdomain { Severity } Critical { MessageID } FAN0001 { Messa
DELL-Erman O
Moderator
•
2.9K Posts
0
February 21st, 2024 12:15
Hello, Could you check these troubleshooting steps:
Alert Policies Troubleshooting - Email Alerts:
Step 1: Receive SNMP Trap from device.
Check the alert log. If no alerts, check the iDRAC configuration.
Use the Test Event option in the iDRAC to simulate an error.
Step 2: Alert Policy Configuration
Under Category, select the All checkbox since often the user is filtering out the alerts they want.
Under Target, ensure all devices that you want email messages from are selected.
Under Date and Time, do not select anything at all. Often, users are setting times here and if any alerts fall outside of that time, they get nothing.
Under Severity, Warning and Critical should be fine.
Under Action, fill out user email details.
Step 3: Send Test trap from iDRAC again to verify functionality.
Check the Alert log again to verify it got to appliance.
Wait for email.
If no email is received, then this indicates an email server configuration issue.
Under Application Settings > Alerts > Email Configuration, check the email server configuration.
Ensure that IP is correct, port is correct, and credentials are correct. Switch Authentication and SSL for testing.
rodsavard
1 Rookie
•
55 Posts
0
July 5th, 2024 22:10
@DELL-Erman O that answer doesn't address the root problem. We are getting alerts, it's just that the "device IP" reported in the email is sometimes (not always) the IP address of the OME server itself.
I am experiencing it on OME 4.1. Not sure if it happened before this version.
DELL-Young E
Moderator
•
5.3K Posts
0
July 8th, 2024 01:11
Hello, thanks for getting back to us with this. We'll be looking into this.
Respectfully,
DELL-Young E
Moderator
•
5.3K Posts
0
July 12th, 2024 03:04
Follow up:
It is working as designed, for all internal device health alerts, like CDEV6130 and CDEV6131. The email alert policy sends a notification with the OME IP address instead of the device IP. You still have the device name and tag in the alert message to identify the device.
Respectfully,
DELL-Young E
Moderator
•
5.3K Posts
0
March 6th, 2025 05:56
Hello,
ccbnl,
I referred this to the team and this is working as designed.
If OME is generating syslog event on CDEV6131,it means OME has lost connection with the device, so the source will be OME.
"The operation cannot be performed on the device because connection with the device is lost."
Let us know if you have additional questions. Also we would like to ask you to visit https://www.dell.com/community/en/direct-messaging
ccbnl
1 Rookie
•
3 Posts
0
March 7th, 2025 02:49
I have this issue with ALL syslog events.
Syslog shows the OpenManage VM in the "IP" and HostName". That is useless, we don't know what device had the issue from this message:
154>Mar 5 14:45:36 om EEMI System Health event from device with { IP } 130.199.XXX.XXX { HostName } XXX.XXX.bnl.gov { Severity } Critical { MessageID } CDEV6174 { Message } Device health has deteriorated. { Recommended Action } Check the device subsystems for components that require immediate attention. For information about device health status, see the Online Help by clicking the help icon. Also see the User's Guide available on the support site.
The web UI shows the real device with the hardware issue (differing timezones on the two but it is the same event):