Hi Thorsten, Well then I may be confused or missing some subtle detail here. When it comes to SNMP alerts, OME doesn't contact the target, the target device sends an alert to OME.  So if OME is getting a rogue alert in the Alert/Event console, it is because the device is pointing at the OME ip address for sending traps. Did you review the SNMP settings of the target device itself? Thx Rob (sorry if I'm being dense and missing your point)
Hello, I'm really stuck here. We have more than 15000 "Authentication Failures" for a device which is not listed in the "Devices" section. Therefore I'm unable to remove that device. The alert is shown with the ip address which points to a live device (Equallogic member). Here is what I did so far: When I try to "ignore this device only" I get an error saying that there is no device for that alert. When looking in the database table the deviceID is shown as -1 The aim is to have the Equallogic reporting into OME and when I add both the group and the member (which is using that ip address) the device adds ok. But the alerts continue to occur (this time showing the correct DNS name). I then removed the devices from the discovery range but the alerts continue to come in (again with just the ip address). So to me it looks like that device got stuck somewhere in OME and is accessed although no device exists. But I'm failing to see where it is coming from. Those alerts are just a pain and I need to find a way to get rid of it. Please can anybody shed some light into this strange behaviour. We are on OME 1.2.0.3441 Thanks Thorsten  
Getting "authentication error" for a device which is not in OME