jason.carrier · Product Manager · ✭✭✭✭✭

I'd be the guy to look at it. Feature Request makes sense. I'm not sure where it would rank in terms of priority though. Developer capacity challenges are ever-present. Care to throw me some SNMP walks of the devices you're looking to have supported?

I understand your frustration. I just came on-board recently at SolarWinds, and share your perspective that we could do a better job of managing feature requests by flagging or expiring them after a period of time. That's something I'm going to be internally pushing for in the near future. Thanks for your feedback there!…

It's not going to be in our next release, but I've got it included on NPMs roadmap. Look forward to sharing greater detail as soon as I'm able!

Speaking to item 3 - I agree! Incorporating status and threshold improvements to interface metrics is something I'm hoping to address in the near future. Important to also note it's not something we're currently working on.

@"sja" Agree. Definitely tracking this need. In the meantime, our best method of address gaps in native SNMP polling is NPM's Universal Device Poller; and for API integrations it's SAM's API Poller.

Nick - Thanks for engaging with a passionate reply! I understand where you're coming from and agree that this feature doesn't appear to be a particularly heavy lift. I definitely wouldn't describe it as an "insurmountable task" by any stretch. Also, totally agree it's a good idea. Let me know if you want to jump on a call…

Sure thing. I agree this one would be a big win, and I'd love to get it built. When we talked internally about how much developer capacity it would consume, it was much more than I expected. There are some hindrances related to scheduling in our core architecture that need to be resolved first. It's still on my radar, but…

Likewise, and you're very welcome!

Have you guys seen what osborne_graham​​ put together here? Be interested to hear your thoughts.

Implemented in NPM 2020.2. https://documentation.solarwinds.com/en/Success_Center/NPM/Content/npm-cloud-monitor-azure-gateways-and-site2site.htm

Message received! I'm definitely interested in implementing this one, but it's not something we're currently working on. Our next release will be focused on performance improvements, better localization, and device support. More to follow soon... That said, I've got some calls scheduled next week to explore this idea, and…

We've got a good amount of documentation for our Cisco ACI monitoring capabilities here. Did anything change in your environment in regards to firmware versions, or did the change happen after upgrading NPM? Have you opened a support case? If not, suggest you do that first. Also, if you let me know the case number and I'll…

Great question! SolarWinds does not provide a comprehensive list of all supported devices, but that is something I'm working on as cycles permit. If your device supports standard SNMP MIB2, it can be monitored with the Orion Platform. However, if your device model is not identified accurately, see the Tell Us Your Unknown…

It looks like we're having some issues with centralized upgrades at the moment for customers on 2020.2. Recommend using the offline installer to get up to 2020.2.1 HF1.

Thanks for bringing to my attention, Kevin. A case number would be helpful.

Do you have active maintenance? If so, you should see the available update. If it's not working correctly, recommend opening a support case and sharing the case number.

The investigation is still active/ongoing and we'll share more details as we have them.

Thanks for pointing out the confusion. We're working on getting the security advisory updated to be clearer on this point.

2020.2.1 is available in the customer portal and you can follow these upgrade instructions - https://documentation.solarwinds.com/en/Success_Center/orionplatform/content/install-centralized-upgrade-primary-server.htm

Thanks for the heads up. I'll keep an eye on it.

Make sure you check out the details in our Security Advisory. It outlines the impacted versions and is being kept up to date with the latest information we have available. It also has links to additional resources. Your antivirus vendor can probably provide details around how they're coming up with that detection result.

Assuming you're talking about WMI credentials, you can get this information by: 1. Go to the credential table and get the credential ID for the one you're concerned with 2. Add the credential ID and run this query to get the impacted node IDs: select * from NodeSettings Where SettingName = 'WMICredential' and SettingValue…

We're in the process of working with DHS and SANS to get their pages updated. This article provides steps to address the vulnerability and the SolarWinds Security Advisory describes it in more detail.

I haven't seen anyone else reporting this one, but will keep an eye out. Have you opened a support case?

Keep an eye on the security advisory page, which is being continually updated: https://www.solarwinds.com/securityadvisory

Keep an eye on our security advisory page, which is being continually updated: https://www.solarwinds.com/securityadvisory We're also hard at work getting a hotfix released.

The security advisory page is being actively updated as we handle this situation: https://www.solarwinds.com/securityadvisory

Have you opened a support case for this issue? If not, I'd recommend doing that first. This is a curious case, so if you wouldn't mind, please also send me the case number. Support should collect details/diagnostics so we can assist in getting to the bottom of it.

@"nks7892" I'll look into it and get NPM's documentation updated. Thanks for the heads up.

Hey Michael - Thanks for your feedback on wireless heatmaps. If you've got some time, I'd love to jump on a call to discuss. Tracking where users and devices are connected to wireless networks is something I'm researching at the moment.