cobrien1

This was delivered as part of NPM v12.1 which released 3/14/2017. Now, when you use the new Maintenance Mode "Mute Now" and "Unmanage Now" options, the nodes are muted or unmanaged indefinitely.

Development and I will jump in on this Edward! We'll schedule a call shortly.

This UI does indeed apply to both SAM and NPM.

It seems to me more granular page refresh timers are a kludge to fix a deeper problem. Would the following solution set obviate the need for this specific feature and bring other benefits?: * Stop doing full page refreshes. * Allow resources to intelligently pull in new data points. Examples of "intelligently":* Charts: if…

This is helpful. Thanks.

NPM v12.1 was released 3/14/2017 and has this functionality.

http://techfieldday.com/event/nfd13/

Yes - just include the device manufacturer and model number in the file name if possible.

All very good suggestions. Number 1, 2, and 4 are top of mind for me lately Will think about the third. If you can align and distribute icons, what do you feel the grid would help with?

Hi nickzourdos​! I'll put your name on the list of people to contact for this one.

>Does this mean that next year my support renewal will reflect that there's really nothing happening here? Not sure why I'd get billed for a maintenance agreement when it sounds like there's no maintenance. No, because that would not be accurate. We will continue to provide 24/7 support, hot fixes, and so on as we have…

kimberly.wooden@smithgroupjjr.com​, I believe the API is reporting APs that are attached to the WLC, not simply ping. However, this is something only Meraki can speak authoritatively about. The symptoms you describe sound like a bug. Have you had a chance to open a Support case yet to so we can investigate?

You may want to add these specifics (and perhaps your vote) to the related FR: I'd love to hear what specific data you'd like to see for your FEX.

designerfx​ - Probe deployment options tend to require some hands on troubleshooting to resolve, so a support case is likely the best bet for resolution. It should just work, and if it isn't, we need to fix it for you.

We released our brand new user interface some time ago: SolarWinds Orion 2016.1 feature: Brand new look and feel - SolarWinds Worldwide, LLC. Help and Support. More recently we added a new way to list resources that can be added to a page. We also added a drag and drop page editing. There are several pages (ex: NetPath)…

Good catch!

tero.kiminki​, if you're getting everything else then both SNMP and API/CLI polling are working. Sounds like it's time to call in Support! I'm glad the upgrade went well. We've put a lot of work into improving that.

Transitioned this idea to "What We're Working On" status as we're working on Network Insight for ASA now.

Everything will work except where I explicitly called out NCM: Access Lists.

jjmason​, here's explicit answers: >As the new Network Insight for F5 functionality requires the iControl API, what is required for setting up iControl on the appliances? By default, F5s have iControl enabled for the admin account. This is why it is not mentioned as a required configuration step in the guide. >Does it need…

There's a couple of challenges to solve. First challenge is increasing how many polling engines can talk to one database server. Currently that maxes out around 20 for very busy full polling engines. Smaller polling engines would go much higher, but spreading the same element count across a larger number of pollers produce…

Other than which nodes the alert applied to, what did you adjust precisely?

I couldn't agree more and have been thinking about this a lot lately. This thread has already discussed stack ports (and by extension stack ring) health and seeing member status and serial numbers. What else is needed beyond what we can currently display now to have the ideal dashboard for switch stacks?

I do not think this is new behavior as we did not touch this area of the code, but perhaps something unexpected happens. I will keep my ears open for other reports like this one to prompt deeper investigation. Apologies for the hassle. We'd like to take some big steps forward with mapping, which is why we're working on…

In the beta, a virtual site survey can be performed to make the map more accurate by considering real measurements that will take into account things like metal walls and cement.

We should totally do this. There's a lot of information in the Top errors and discards resource today though so I'm not sure we want to add more. Currently we have: Node Interface Receive Errors Receive Discards Transmit Errors Transmit Discards For the sake of simplicity, let's say we created a new resource to accomplish…

Are there locations in your network that you want to be the source of a path that do not have a Windows machine present?

What would you like to see in these new resources?

I'm afraid I do not have more to share on this right now.

It's contrary to initial intent because as soon as we use ICMP, the performance and even the path may be different than the application receives. In practice, path is not frequently different but performance is. It also encourages making paths destined to transit nodes like a router rather than to an endpoint like an app…