Comments
-
Thank you for this, it's a good thing to have until the Devs add this directly to the NTA settings page, hopefully.
-
Great tool and already used it to find the root cause of an issue that was otherwise hard to detect.
-
If you have multiple polling engines this table will get a little messy. Here's a way to alter the table so it's a little cleaner: SELECT * FROM ( SELECT T1.EngineID, J1.ServerName, J1.IP, T1.StatisticsName AS [Statistics Name], T1.StatisticsValue AS [Value] FROM NetFlowEnginesStatistics AS T1 INNER JOIN Engines AS J1 ON…
-
This would be a great feature to have! I could also use it for the connections between my switch and firewall that doesn't have MIBs for interface stats. It would be a huge benefit for my WAN and ISP links, all of which I have on maps but am unable to show link utilization on the map for.
-
Yes, this is needed badly. In fact some way to do a report on all inventory (i.e. Node and chassis serial number regardless of vendor) is needed badly.
-
I am also pushing down all my policies from Panorama and NCM 8.0 doesn't see any of the policies pushed from Panorama. This is even after I have configured custom device templates that download all of the "shared" policies. Is this just a gap in the feature that you're still working on or am I doing something wrong?
-
I have this same issue on all of my Cisco ASR routers. SFP plugged into port but is admin down and I get all these alerts, very annoying to the point of making hardware health monitor almost useless because of all the false alerts.
-
Thank you for this info. I've been looking for how to do this and your explanations led me straight to it.
-
Do you need any stickiness on the F5 so that all flows from a particular router/switch always go to the same APE?
-
Figured out how to combine both into one query: ${SQL:SELECT Caption FROM NodesData left join NodeIPAddresses on NodesData.NodeID=NodeIPAddresses.NodeID where (NodeIPAddresses.IPAddress='${N=SwisEntity;M=NeighborIP}' OR NodesData.IP_Address='${N=SwisEntity;M=NeighborIP}')}
-
Thank you Richard, the information you pointed me to in (Look at using the Dynamic alert thresholds in 10.7) was what I was looking for and works for what I’m trying to do. I also figured out another way to do it (with a little more customization) by creating a custom SWQL alert with the following parameters: SELECT…
-
I finally got this to work! I'm using NPM 11.5.2 and this is the syntax I got to work: ${SQL: SELECT Caption FROM NodesData Where IP_Address='${N=SwisEntity;M=NeighborIP}'} The placement of the ' ' around the SWQL variable within the Custom SQL variable was critical. Note that if the NeighborIP doesn't match to any Node IP…
-
Simply adding radius authentication would be sufficient for me to enable two-factor auth in my environment and add an industry standard authentication protocol to the tool. I'd like to add a vote for this.
-
I also started having this issue a few weeks ago and just last Friday updated all my polling nodes to 4.7.2 and initially the issue went away. Now today it's back again! Guess I'll try the KB4457920 fix and see if that resolves it. Thank you all for your updates!
-
This is a feature that needs to be added. In addition the search bar on the Load Balancing page needs to be improved to jump to what was found. We have hundreds of VIPs in our load balanced environment which means the simple highlighting that happens now is just not good enough. It takes too long to scroll through the…
-
I also have this issue and have tried many things but can't get anything to work. Does anyone out there have some insights?