Event was skipped, it was an old event - Event Alerts

[M. Jay]

I seem to get this when, for example, a bunch of alerts are coming in because we're doing maintenance. All other times the various notifications tasks work. I noticed when we kept getting of the "unreachable" alerts without getting the cooresponding "reachable" alerts.

Any thoughts? I'm not sure about it being flooded with too much because we seem to be getting the "unreachable" alerts just fine BUT the reachables get this error...very strange.

Now, that I'm writing about it I am thinking that the alerts are from virtual servers and they reboot very quickly...I wonder if this might be the issue and wonder what to do to solve.

Thanks for listening.

MJ

[M. Jay]

Sorry, forgot to mention that we're running HP SIM 5.1 on Windows 2003 SP2 R2 on an ML370 G4.

Also, in look closing and comparing recent alerts I noticed that it IS NOT, this time, virtual servers. But in looking at the SIM event logs on a server that we got both alerts and the event logs on a server that WE DID NOT get the "reachable" alert on here is what I see:

All the CORRECTLY rec'd alerts (both "unreachable" and "reachable") were rec'd at 6:17 AM (Unreachable) and 6:19 AM (Reachable) - just two minutes apart.

This must be some kind of timing issue on my polling tasks. Total devices we have in SIM is just over 900. This is the first time I've noticed this problem. Nothing has changed on our SIM server.

Here is the HW polling task we've been using forever:

Hardware Status Polling for Servers - runs every 12 minutes and it says it completes in approx. 4 minutes. We've got approx. 680 "Servers" in the list and the status on this polling tasks says completed with "Some Failures".

TIA.

MJ

[M. Jay]

I think I might be closer. Looking at the various HW polling status' I found:

HW Status Polling for Servers - 12 minutes
HW Status Polling for non Servers - 1 hour
HW Status Polling for Critical Systems 15 minutes

Anyway, when SIM was originally installed we were an almost 100% HP shop...but now we're very far from that. Back then the list of non Servers was small but now we have a lot of VM guest servers that show up as unknown so are on this non Server list. Anyway, I just changed the polling time from 1 hour down to 12 minutes so we'll see how it goes.

Also, just FYI - the HW Status Polling for Critical Systems was created/configured and set to catch those original few "unknown" devices and help keep them from showing unreachable for too long. I have also disabled this for now.

MJ