I would suggest to start with the manual to see if you have it properly configured

then take a look at the messages files and server_log

Thanks for the helpful hints.

I have been using the Configuring Celerra Events and Notifications manual. That is where I got the syntax to send the test event, Its just troublesome that the events that are created through the GUI aren't being sent but the manually created events are.

I'll now look though the following to get some insight.

nas_logviewer /nas/log/sys_log

cat /var/log/messages

nas_emailuser -info

Thanks,

Ayo

I ended up modifying /etc/init.d/snmptrapd so that it dumps its logs to an alertnate location. Now snmptrapd command line run options are as follows.

[nasadmin@TOWNAS2CS ~]$ ps -ef | grep snmp
nasadmin  4286  4134  0 11:46 pts/1    00:00:00 grep snmp
root     27614     1  0 Jan07 ?        00:00:00 /usr/sbin/snmptrapd -Lsd -Lf /nas/var/log/my_eventlog_messages -p /var/run/snmptrapd.pid

When I set an alert via Celerra Manager I enter the SNMP Trap destination as well as an email address for testing. The problem is that I recieve the email alert but the SNMP trap never gets sent.

[root@TOWNAS2CS init.d]# tail -f /nas/var/log/my_eventlog_messages
2010-01-07 17:08:26 NET-SNMP version 5.1.2 Started.

What else could cause the Celerra to not send SNMP traps? I'm at wits ends and I've searched through the "Configuring Celerra Events and Notifications" documentation and I don't see anything that can offer meaningful help.

TIA

I would suggest to open a service request

It turns out there is a bug with all DART less than 5.6.45 where the trap events are created with the wrong facility ID when they are created through the GUI. The issue is documented in emc217192, I don't think its available publicly but here is the work around.

Cause      DART 5.6 introduced new disposition IDs for some events. For instance, the old IDs 201, 202 and 203 are now replaced by IDs 210, 211 and 222, respectively.
When using Celerra Manager GUI to configure SNMP traps, Jserver still uses the old disposition IDs to create the traps. As these IDs are no longer used, the traps configured this way will never fire

Fix        Fix is in 5.6.45 and above

Fix        Workaround:

A workaround is to manually add a file based on the /nas/jserver/event_config/events.cfg file - please note that any changes to notifications in the Celerra Manager GUI will reproduce the events.cfg file again.
It is therefore recommended not to make changes to notification configurations in the GUI once the workaround is applied while the permanent fix is pending.
The example below assumes that an SNMP trap was only configured only a file system size threshold (old ID 201, new ID 210).
If other or additional SNMP traps were configured, they will need to be modified accordingly (see Note below for details on which ID has been replaced by which new ID).

Hope this helps other people.

thanks very much for letting us know

most people here never take the time to report back how their issue was solved.

regards

Rainer