Unsolved
This post is more than 5 years old
2 Posts
0
36128
September 23rd, 2013 15:00
OME not registering SNMP traps from OMSA client
Hello, I'm doing some testing using a server with OME 1.2 installed and another server using OMSA 7.2, but having problems getting the right SNMP trap events to show up in OME as alerts. I've been testing by offline-ing a physical disk on the OMSA server, which generates the following traps, and I see them being logged on the OME server using the SNMP listener tool:
However, these specific traps do not show up in OME. Actually, nothing shows up in OME until I manually perform a status polling of the OMSA server. The SNMP trap that then shows up in OME is entirely different from what was received (I assume because I am polling against the OMSA server instead of operating on the 3 traps that were received initially):
The "omeAlertWarningStatus" is a very generic message, whereas the 3 SNMP traps that were received initially are far more relevant to the actual problem, i.e. 903 is "alertArrayDiskWarning". Any idea what's wrong?
0 events found
DELL-Pupul M
2 Intern
•
1K Posts
0
September 24th, 2013 01:00
Hi,
When you perform a status poll on the target server and of internal health alerts are enabled on the OME server (which is enabled by default), then OME generates internal health alerts if there is a change in the health of the target server. This is what you are seeing when you perform status poll.
Is there any other application other than OME installed on the same machine where OME is installed which is listening to alerts over the same port? If there is another application having trap listener, it might not share the ports with OME.
Also, in OME, there is an option to ignore duplicate alert if it is received within next 15 seconds. Make sure, that option is disabled so that the alerts make their way to the database.So, another thing to check would be there is no alert ignore action created for any alert which you are receiving.
DELL-Pupul M
2 Intern
•
1K Posts
0
September 24th, 2013 08:00
Hi,
Thanks for taking your time to post it here. It helps :)
QuicksilverO2
2 Posts
0
September 24th, 2013 08:00
Got it working. It seems that when I installed OME yesterday, the SNMP trap service was disabled. I ended up setting it to the manual startup type to use the Windows SNMP Trap Listener in the Dell Troubleshooting Tool. Upon running a "netstat -ab -p udp", I noticed there was only 1 snmptrap.exe service running on port 162. I stopped the SNMP listener tool, restarted the OME services, and now SNMP traps work correctly. So I think what happened is the SNMP trap service did not get started after the initial OME installation and startup...I did have the OME setup program install the SNMP services though, so maybe the setup program doesn't change the SNMP trap service to something other than disabled if it's not currently installed?
Thanks for your help Pupul.
YoungyLives
29 Posts
0
December 2nd, 2013 18:00
In addition to the help I got from this thread and some further testing I found I had to massage windows internal firewall as well to allow port 162.
In case that helps someone else.