Skip navigation
1369 Views 8 Replies Latest reply: Jul 9, 2012 4:55 PM by Shane Scott RSS
begbert Newbie 8 posts since
Jul 9, 2012
Currently Being Moderated

Jul 9, 2012 11:18 AM

Events stop generating for a downed device?

It's currently 10:34 AM and the last generated down event for this device was at 7:05 today.  It has since come back up.  Any idea why it seems like Zenoss just stopped checking?  Any help would be appreciated.

 

 

ip x.x.x.x is down

 

 

Device:DeviceName
Component:
Event Class:/Status/Ping
Status:0
Start Time:2012/07/07 01:22:47.000
Stop Time:2012/07/09 07:05:46.000
Count:1458
Message:ip x.x.x.x is down
Systems:
Groups: | /Routers
Location:/DeviceName
Device Class:/Server/Linux
Production State:Production
Device Priority:Normal

 

 

Hide details

 

 

agentzenping
clearid
component
count1458
dedupidx.x.x.x||/Status/Ping||5|ip x.x.x.x is down
devicex.x.x.x
DeviceClass/Server/Linux
DeviceGroups|/Routers
DevicePriority3
eventClass/Status/Ping
eventClassKey
eventClassMapping
eventGroupPing
eventKey
eventState0
evidcf6fe5de-15f1-432e-9826-af7e76b859fa
facilityunknown
firstTime2012/07/07 01:22:47.000
ipAddressx.x.x.x
lastTime2012/07/09 07:05:46.000
Location/DeviceName
managerzenoss.prismone.net
messageip x.x.x.x is down
monitorlocalhost
ntevid0
ownerid
priority-1
prodState1000
severity5
stateChange2012/07/09 07:05:46.000
summaryip x.x.x.x is down
suppid
Systems|

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points