cobrien1

We'd like to support these devices. If you could send me some SNMP Walks, that would definitely speed things up. I'll shoot you a PM.

Great post. I'm sure this will help out the Meraki guys. Thanks!

Have you tried scanning your F5s with NTM? What does your map end up looking like? Also, I'm curious how you would use the map after you created it.

In the future, it looks like automated dependencies may be very helpful for you: Re: What we're working on post-NPM 11.0

This is possible in NPM v12: NPM 12.0 feature: SwitchStack monitoring - SolarWinds Worldwide, LLC. Help and Support

Indeed text is not currently resizable. Definitely something we're thinking about now that icons are scalable.

The only way to remove is delete the agent and readd it without adding a NetPath destination to the agent. Why would you like to remove it? It's not doing anything unless a path is configured involving it.

NPM doesn't currently poll tunnels out of the box unless the device presents them as a logical interface. Do those models present tunnels as logical interfaces? In most cases, you can create a quick UNDP to get the bandwidth graphed and available for reporting and alerting.

Did you use the "Connect Now" function in Network Atlas to connect your nodes or did you manually connect them? Also, what do you see when you click the line and click "Line Properties..." in the "Lines" section of the ribbon bar at the top?

This is not an area I know about. Any ideas lanli.fsm​?

We're still looking for a few more volunteers!

Still looking for some more SNMP Walks!

I see what you're saying. Indeed there is a big gap between NPM's use of ping and the ideal. Detecting jitter, accurately detecting % of packet loss, determining a node is experiencing severe packet loss instead of just being down, and so on are hard to do with NPM's ping monitoring. But IPSLA does *fantastic* at those…

What version of Orion Core and NPM are you running? The original feature request (11015) is marked as completed/implemented. If you're running up to date versions of Orion Core and NPM, I'd suggest calling into support as this device should now be supported. Let me know what the results are.

Are you saying if you use an account limitation of a "Single Interface" the problem remains, but it is solved when you add the "Network Node" limitation (or permission would probably be more accurate)?

Your input on how you would like to see this working would be especially valuable right now. tulsi​, could you assist in setting up a discussion time?

For that one it would probably be best to contact Support: SolarWinds Customer Support - We're Here to Help

The icon is based on the device type, and it sounds like the device type is not being discovered. To discover Windows PCs, you need to add WMI credentials in the discovery wizard.

We're looking for more replies here. We will also be reaching out to the folks that complete the survey to see if they're interested in chatting about some of the stuff we're working on. We've got some really exciting stuff being iterated on that we'd like feedback on.

Many good points. I have a few thoughts: * In many cases 10 gbps interfaces have less than 1 gbps of traffic being sent. Depends on the density of your environment. Of the 20 gbps (bidirectional) available on the trunk you mentioned, how much is actually being used? * As you noted, Gigamon is one of the primary solutions…

The Cisco switch stack monitoring feature only works for Cisco switch stacks.

Additional walks would be appreciated. I know you guys have more F5s running 11.2 or earlier!

Support can help with this if you haven't already resolved it. You should not have to reinstall everything.

* Is 192.168.100.254 the correct first hop? * Do you have a device that is spoofing the destination? For example, a proxy that pretends to be the destination web server even though it is not?

NTM is a more direct solution to this than NPM: http://www.solarwinds.com/network-topology-mapper.aspx

QoE only displays QOE eligible nodes. To determine that a node is QoE eligible, it must be monitored in Orion and Orion must have been able to discover that it is a Windows device, etc. Can you confirm you have nodes in Orion that Orion sees as Windows?

FOE is Active/Standby as you mentioned. Active/Active is essentially doing everything twice, all the time. Obviously you could set that up by just setting up two different instance so I assume you're specifically looking for syncing of the configuration between the two Active NPM installations. Is that right?

This is not currently possible. Question so that I may understand better: would you rather the historical data to be updated promptly or not updated at all?

Could you send me an SNMP walk of both devices? chris.obrien (at) solarwinds.com The SolarWinds SNMP Walk tool can be found on your server: SolarWinds Knowledge Base :: SolarWinds SNMP Walk: A new tool for collecting SNMP MIB walks

There are a number of ways to generate an alert on that error condition (alert on routing adjacency change for certain protocols or alert on low interface traffic), but it sounds like you'd specifically like the information to display on the map. Is that right?