Comments
-
Works perfect! Thank you very much.
-
Is it possible to restrict this to only the previous 24 hour period?
-
We are also seeing the exact same error, four times in the log.
-
Another vote for Trapeze. Dual MX2800 controllers with 400 APs.
-
Another request for support for Trapeze wireless monitoring.
-
Thanks...signing up.
-
Definitely appears to be the issue. Was not aware of the problem with the counter rollover. Monitoring around 70 or 80 of these things and it has been a pain recently. Thanks for the feedback.
-
Ditto...8600's and 5530/5520's.
-
Any movement on supporting Trapeze products?
-
Any update on adding IPFIX support?
-
Major duh. I never saw that they were clickable links and I assumed that there was numerical data that would display next to the individual items. Thanks.
-
Our company is also using Trapeze and would like to see it supported.
-
The database issue would not be one if the scheduled compact and repair would work. I have it scheduled to run twice a week on my system and it does not work. I still have to manually run it each week...so each Monday morning I shutdown NPM, compact and restart. I don't understand why they cannot get the scheduled compact…
-
Works as advertised for our shop. Do have one request if someone knows how to do it...there is a TimeStamp in the .SnapShot file and it would be nice if that was displayed at the top of the page so that you would know how current the displayed data is. Any suggestions? I have played with is some but I am very new to XML.…
-
Ditto
-
Thanks...glad to see the Solarwinds folks looking at the questions and suggestions!
-
Here are the configuration details that I use on our 5520 switches. I monitor our uplink ports out of the stack. Note: This is from a three switch stack where we are monitoring 1/48 and 2/48. We also use the default aging and export options. I also put comments in brackets. ip ipfix slot 1 aging-interval 86400…
