Kita · Senior Director · ✭✭✭✭

@WindsOfNishat Juniper Mist Wireless was added in 2024.4 and later: https://documentation.solarwinds.com/en/success_center/npm/content/release_notes/npm_2024-4_release_notes.htm There were several bug fixes in 2024.4 to 2025.1 for Mist. The majority of those issues have been resolved.…

We have posted this information in the following article, but would love to hear more feedback if there are other challenges: https://support.solarwinds.com/SuccessCenter/s/article/Symptom-Audit-Events-for-Muting-Maintenance-Actions-Show-system-Instead-of-the-Actual-User-After-SolarWinds-Platform-2025-4-Upgrade

There are changes in Kiwi Syslog NG 1.5 to improve timezone support for LogToFile: Improved timezone support for LogToFile action You can now configure whether time-related AutoSplit variables use UTC or local time for LogToFile action file naming (Settings > Formatting > Log to file settings > Use local time instead of…

@mharvey It may be related to the following article: https://support.solarwinds.com/SuccessCenter/s/article/SolarWinds-Platform-service-fails-to-start-with-Plugin-Core-Business-Layer-failed-to-start-on-Poller-Name-Please-restart-the-Module-Engine-service-on-Poller-Name-message?language=en_US

@j1mat This is odd behavior. The assumption would be that when the SSH connection is dropped, it should disconnect immediately. If this did not happen, the assumption is that the application believes it was still connected. We can try and see if we can replicate similar behavior by dropping the SSH connection using third…

Depending on the data, the assumption would be that the focus is on specific metrics related to what SolarWinds is polling. There is no streamlined process for pulling the data and sending it to Microsoft Sentinel. In theory, you can use the Orion SDK to make a SWIS API call to pull the data, but time would need to be…

@rjrothwell UnDP would be the way to go for now. As long as you can pull the data, then you can build the necessary reporting. I did a bit of digging into the issue, as we are using the classic LLDP MIB. There are some vendors that are using the LLDP-V2-MIB, which may be the reason why some vendors don't work. We are…

@Servicecentre Thank you for the feedback. We've attached this ask to the existing item in our system. This item is still being discussed.

@syed_tahir Appreciate the feedback. I believe these are recommendations for product improvement, correct?

@narensw You are on the right track. It should work as long as the APPROVED column in the Actions table is set to True for the corresponding ActionID. It should match the logs: * Grab the ActionID from your Alert History / AlertHistory or ActionExecution.log. * Compare against those patterns (and ensure…

@NetDev_sol Believe I found your case, and we have already reviewed the data provided. We will reach out with more specific information, but there appears to be an interesting scenario in which the job engine and collector stopped working (or at least stopped recording data in the logs). There was an attempt to stop/start…

@joe.young Thank you for the feedback. If you have a support case, please let us know. We will provide a workaround or solution as soon as possible.

We did have some maintenance and changes to the portal a few months back. Everything should be working now. If there are more problems, please let us know.

@augiechimpo Changing the scanning intervals would be the first step. A SQL query to change them in bulk is discussed here. Agree that it would be hard to figure out without spending time to determine which subnet(s) are causing the problem, so having a UI option that flags or warns certain subnets that are taking longer…

Reason field was added in SolarWinds Platform 2025.4: https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-4_release_notes.htm

Implemented in NTM 2.4.4: https://thwack.solarwinds.com/discussion/151719/announcing-network-topology-mapper-2-4-4-is-now-generally-available

This is an existing feature request: There is the backup and restore process documented here, but requires several steps: https://support.solarwinds.com/SuccessCenter/s/article/Configure-Backups-on-your-LEM-Appliance

On the same server, open C:\ProgramData\SolarWinds\JobEngine.v2\Logs_Agent and look for clear JobEngine errors. Looking at the agent logs first would be the first step to see if there is any signs of problems.

This should be resolved in 2024.1 and above. The following documentation was updated via https://support.solarwinds.com/SuccessCenter/s/article/Supported-algorithms-and-cipher-for-NPM-and-NCM?language=en_US

Agreed +1

UPDATE: Went back to check all the recent changes and looks to be addressed in 2024.1 and document in the release notes. We may need to reword the release note as this is likely a problem in prior releases. PerfStack projects display data correctly after an upgrade. In early 2024.1 RC builds, the start and end times…

@"nedfields" Agreed. I went to the lab device and changing the settings using the quick pick options. Once the setting is changed, I went and click Save. I've logged out and login and I see the time setting is saved. I went and logged using a different browser to see if it is cached, but I am still seeing the saved time…

RHEL 9.5 is supported. If there is an issue with RHEL 9.5, please file a support case

Agreed! +1

@"nedfields" The expected behavior should be the time setting should be persistent and it should not reset. If I am setting the perfstack widget to 2 days, then it should remain as 2 days until the user changes the setting. If I am understanding your expectation, you are asking for the time period to reset to what it is…

agreed +1

This is supported in 2024.1 and above. Documentation has been updated via https://support.solarwinds.com/SuccessCenter/s/article/Supported-algorithms-and-cipher-for-NPM-and-NCM?language=en_US

Agreed! +1

We have documented that some maps have an underscore. If this occurs, then this will cause the HTTP 404: https://support.solarwinds.com/SuccessCenter/s/article/Orion-Maps-are-not-being-loaded-after-upgrading-to-HCO-2025-1-1

This issue was fixed in 2025.1. The recommendation is to upgrade to 2025.1.1. The issue was specific to the API response, which was sending information to SolarWinds, where the AP does not include an IP address. After 2025.1 release, if the API response does not include the IP address, we will continue to process properly.