Comments
-
Difference between the time of the event (when node went down) and the current time should give you the downtime. The custom SQL var below should give you just that - downtime in hours. So, just add the flavor text around it to achieve the required result. ${SQL:SELECT datediff(hh, (SELECT TOP 1 EventTime FROM Events WHERE…
-
Couple of ways depending on what exactly you need to achieve. If I got what you need correctly you can just open the report in report writer, on Filter Results tab add a condition to specify the interface (eg. using the Interface ID) and save the report (as a new one, so you don't overwrite the general one). You can run it…
-
I'd probably try to use the Alert/Filter Rules (in Trap Viewer: View > Alert/Filter Rules ...) to accomplish this. You can setup rules to filter the incoming traps (based on contents, source etc.) and so can e.g. dump the ones you don't care about or have an email send to you if some specific trap arrives etc.
-
AFAIK the UnDP will not poll the whole table as you'd like but still this is totally doable using multiple UnDPs (to get the data) and a custom report (to form the desired table using the data from the UnDPs) that you place on the Node page. The complexity of the report depends whether this would need to work for…
-
Previously there were the two (the [Unknown] and Unknown) groups, however this should be fixed in NPM 10.1 and later. From there on only the 'Unknown' group should be used (and contain all nodes that were previously split into the two groups). It's weird that you are reporting to be encountering this with 'Orion NPM v.10.1…
-
The most common reason for this would be that the SNMP agent you've deployed on your GNU/Linux system is running the default/maximum security config. So it is running but provides only the very basic data (i.e. responds only to requests to system part of the tree, like sysObjectID, sysDescr, sysUpTime etc.). Aren't you…