This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

How to build an alarm for SNMP discovery/stat collection failing

Hello,

Someone removed a Cisco router (with a valid community string) and installed a Windows PC (without a community string) using the same address as the router.  They didn't updated DNS.

Orion continued ping the PC, but didn't update the Node Details, or generate any Event log that I could find about failing to rediscover or query the device.

How do you build an alert or event to trigger when SNMP rediscovery or stat collection fails?  Or maybe how to build one for X amount of time since last successful stat collection or rediscovery?

  • If you were monitoring any of the interfaces on that router, Orion would have displayed a node with a problem since the interfaces could no longer be polled. If you had any alerting for those particular interfaces, then that would have generated an alert. Were you only monitoring the router itself and not any of the interfaces?

  • Usually we monitor the ports that connect the router to other routers and swtiches.  Although I don't know for sure if this one had any interfaces being monitored.  But no alerts would have been setup for those interfaces.