0 Replies Latest reply on Aug 6, 2008 7:38 AM by sotherls

    Node reports down but can't find in the event table

    sotherls

      This is a perplexing problem...


      For some reason Orion (8.5.1) just started reporting that a node has been down for over 40+ days yet I can't find where or when the device went down. I know it is down because I can't ping it but I don't know why it just started showing up.


      I thought it might have been because of I might have unmanaged it previously (hence the posts on unmanaged reports) but the reports do not show that it was unmanged. I ran a query against the Events table and it shows that the device was last up on 2008-06-24 but there is no "stopped responding" after that. I also check my email where I get alerts and do not have one from the device during that time frame. Here are the query results:


      2008-06-06 10:11:21.000 Node123 has stopped responding (Request Timed Out)
      2008-06-06 10:16:05.000 Node123 is responding again.  Response time is 1 milliseconds
      2008-06-06 10:26:26.000 Node123 has stopped responding (Request Timed Out)
      2008-06-06 10:56:15.000 Node123 is responding again.  Response time is 1 milliseconds
      2008-06-10 14:13:27.000 Node123 has stopped responding (Request Timed Out)
      2008-06-10 14:18:12.000 Node123 is responding again.  Response time is 1 milliseconds
      2008-06-10 14:18:12.000 Node123 rebooted at 6/10/2008 14:15
      2008-06-24 07:03:52.000 Node123 has stopped responding (Request Timed Out)
      2008-06-24 07:33:28.000 Node123 is responding again.  Response time is 1 milliseconds


      So now I am trying to answer management's question: Why did this just show up now and not before?