Comments
-
Ah, that makes sense now. Thanks!
-
I think I am going to have to do as you suggested with using Syslog Viewer, as my offsites have redundant connections, so if one connection goes down, everything would still look good from one end. I could still get to all devices, i could still ping the default gateway. Can you describe how to setup Syslog to alert on…
-
Ok, I can see how that makes sense for as the alert is built at the moment, but eventually I want it monitoring 20 additional routers. Won't changing it to ALL then require all of the routers to be having issues for it to alert me?
-
I'm sorry, I didn't quite fully explain my situation. We have some nodes that will be monitored during business hours, and some that will be monitored 24/7. I figured the best way to achieve this was to make two different triggers and change the active time on them to what I need. I just wasn't sure the above configuration…
-
I spoke with our MS Server group who controls this, and reverse DNS is configured for some of our network ranges, but not all. In the small range I'm looking, and where my above screen shot was taken, one device populates the DNS field, while two others do not. Yet they all exist in the network range that is not configured…
-
I had my MS Server team add entries for two specific IPs for reverse DNS, and they populated the required field. While not ideal, it looks like I will have to have them continue doing this with all my existing and new nodes. I still wonder how it is several devices were able to get this information when specific reverse…
