New OME Server Not Showing Device Alert Logs

Hi,

Glad to know that you have setup new OME server. Welcome on-board.

For OME to receive alerts from the iDRAC, you need to setup the "alert destination" in the iDRAC UI to OME server IP address. That way iDRAC will send all the generated alerts to OME. Also, there is a way, where you can do these settings via OME itself in 1 to many fashion. Refer this http://en.community.dell.com/techcenter/extras/m/white_papers/20438657 

Also, once you receive alerts in OME, you can create alert action to send those notification via email to the concerned. See http://en.community.dell.com/techcenter/extras/m/white_papers/20437131 

Hi,

It seems the command did not executed successfully based on the above log. Try opening the iDRAC UI and go to the SNMP Traps and Email settings. Set the Destination Address as your OME server IP address and enable. Apply these settings.

Post that you can click the "Send" button under "Test SNMP Trap" and see whether some test trap is received in your OME server.

Let us know if this helps.

Thanks,
Vijay

OK, so I went through and read the PDF file and setup the alert using the process described. The command executed fine. However, I am still not seeing any of the alerts:

Results: Exit code:1.
Output from command (stdout):
C:\Windows\system32>racadmﾠ-r 10.100.157.158ﾠ-u (username)ﾠ-p (password) configﾠ-g cfgipmilanﾠ-o cfgipmilanalertenable 1

C:\Windows\system32>racadmﾠ-r 10.100.157.158ﾠ-u (username)ﾠ-p (password) eventfilters setﾠ-c idrac.alert.allﾠ-a noneﾠ-n snmp

C:\Windows\system32>racadmﾠ-r 10.100.157.158ﾠ-u (username)ﾠ-p (password) set idrac.snmp.alert.1.enable 1

C:\Windows\system32>racadmﾠ-r 10.100.157.158ﾠ-u (username)ﾠ-p (password) set idrac.snmp.alert.1.destaddr 10.157.0.20

Output from command (stderr): 'racadmﾠ-r' is not recognized as an internal or external command,
operable program or batch file.
'racadmﾠ-r' is not recognized as an internal or external command,
operable program or batch file.
'racadmﾠ-r' is not recognized as an internal or external command,
operable program or batch file.
'racadmﾠ-r' is not recognized as an internal or external command,
operable program or batch file.

Hi,

The problem with the whitepaper in question is that Microsoft Word will autocorrect the "-" to a different character which will not work from your command prompt. 

I've uploaded it to our whitepaper section.

Setup remote iDRAC SNMP task with OME
Setup remote iDRAC SNMP task with OME - script

That will give you the correct settings in the iDRAC's/CMC's

This is the new result after following the new steps:

Results: Could not write the following results to the designated task output file (make sure the file is not read-only and is not being accessed by another program): Exit code:0.
Output from command (stdout):
Incorrect number of command line arguments
Usage: SNMP.cmd RACIP RACUSER RACPW SNMPCOMMUNITY TRAPINDEX OMEIP

RACIP = The IP address of the iDRAC we are currently processing
RACUSER = The iDRAC username used to logon
RACPW = The iDRAC password uses to logon
SNMPCOMMUNITY = The Communtity string that is set in the iDRAC or CMC
TRAPINDEX = The SNMP trap destination index number
OMEIP = The SNMP trap destination IP address (normally the OME IP)

#############################################################################

THIS SOFTWARE IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT IS
PROVIDED ﾓAS ISﾔ WITHOUT ANY WARRANTY, EXPRESS, IMPLIED OR OTHERWISE,
INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTY OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE OR ANY WARRANTY REGARDING TITLE OR
AGAINST INFRINGEMENT.

#############################################################################

Waiting for 10 seconds, press a key to continue ...?? 9?? 8?? 7?? 6?? 5?? 4?? 3?? 2?? 1?? 0

Could you create a screenshot of the task with settings?

I think you may have created an output log with double qoutes in the task settings.

Remove the quotes from the output log and it will work. That is a weird quirk with OME.

You are also missing 2 parameters, the community string and the trap index

That fixed the output log file, but am still getting this:

Incorrect number of command line arguments
Usage: SNMP.cmd RACIP RACUSER RACPW SNMPCOMMUNITY TRAPINDEX OMEIP

RACIP = The IP address of the iDRAC we are currently processing
RACUSER = The iDRAC username used to logon
RACPW = The iDRAC password uses to logon
SNMPCOMMUNITY = The Communtity string that is set in the iDRAC or CMC
TRAPINDEX = The SNMP trap destination index number
OMEIP = The SNMP trap destination IP address (normally the OME IP)

#############################################################################

So I fixed that. Thanks for pointing that out. 

It is definitely taking a lot longer to run now and I am seeing some more alert logs, but I can't really tell if it is everything from my servers. 

Just open a iDRAC and take a look at the Alert page. There should now be the IP address of the OME server in one of the trap indexes. From there you can send a test trap.

I haven't done the test just yet, I hope to later. However, I am seeing a lot of these messages and not sure why:
SNMP agent shut down message.

SNMP agent cold start message. 

Very frequently. Almost to the point of pushing out the useful logs. 

The script will enable all SNMP messages in the iDRAC's which can result in a lot of alerts.

Just right click any Alert that you are not interested in and create an ignore rule for all devices.

Thanks that fixed the excessive logs. 

So I did a test just now to see if I'd get the alerts from a server that has a drive failure. Currently it did not pull in the Alert logs, only the Hardware logs. 

Here are the screenshots from the server itself:

And here are the screenshots from Server Admin:

And here are the screenshots from OME: