AMidnightSoul

Comments

  • Forgot to add one thing. The Node details page for the AP occasionally throws an Orion error of "Request Timed Out".
  • Yes. The grouping was actually on No Grouping, so it should've shown everything. I set it to AP and there's nothing there. Where I go to node details on an access point, there is no AP info displayed. It reads the info from the router, such as type of device, System Name, Location, etc, and you can see the interfaces, the…
  • We're actually having this problem also. Running 9.5 SP 5. SNMP is working, as the device shows up as an SNMP device and Node details, type of device, hardware type, telnet address, etc, show up, but there's nothing on the wireless tab. We've only added one wireless device, to test. The device we're using is a 3COM 7760.…
  • It our case, it turned out to be a registry key that somehow got stuck during the upgrade to 10.2. The registry value did not change even though the 'disable all alert actions' was not checked. We had to manually alter the registry keys. After we manually changed the registry key, the disable button in the alert manager…
  • Thanks. I have previously checked those items. Alerts are enabled and I am seeing all the active alerts under the Alerts tab on the web console and in the advanced alert manager. For instance, there are several new alerts that popped up today under the alert manager, but we didn't receive an email for those alerts. I have…
  • You're right, it would've been much easier to go this route if it fixed the problem. Unfortunately, the disable all alert actions was not checked in our case. We even checked and unchecked the box (countless times) to try and kick it in and change the registry setting automatically, but the registry setting was stuck and…
  • These are registry settings found on in the Windows Registry, which you can get to by running regedit from the search or run box, on the Start Button menu. However, if you are not familiar with editing the registry, it might be best to contact tech support and have them walk you through it. You can hose your system by…
  • It our case, it turned out to be a registry key that somehow got set incorrectly by Orion during the upgrade to 10.2. The correct setting should be HKEY_LOCAL_MACHINE\SOFTWARE\SolarWinds.net\Alert Manager\settings\ Disable Alert Actions (set it to False) (32-bit server) Or…
  • That explains it. I just upgraded to NPM 9.5 last night, so I haven't upgraded NTA from 3.1 to 3.5 yet. That answers my question. Thanks! Is there another option to tell how long a device has been un-managed without creating a query in the database?
  • Yes, that’s what we did the day we found out about the vulnerability.
  • One other thing I didn't mention......if I delete the node from system manager & re-add it, the node details webpage works fine for awhile again. But over time, it will eventually cause the webpage to time out when trying to view the node details page.
  • Hi. I was just wondering where Solarwinds is at in terms of getting a fix for this bug. Everytime I have to bring down the solarwinds services, I have to re-manage all our routers that are un-managed (other devices don't seem to affect Netflow), bring Netflow back up, then un-manage everything again. We can have as many as…
  • Thanks for the response! I'm pulling the specs together this week to turn in next week.
  • I agree that would be a whole new version and not a "patch", but I believe the reason it's frustrating to many customers is because the new version that fixes this vulnerability requires Server 2016 or newer, while the version affected by the vulnerability runs on Server 2012. Server 2012 doesn't reach end of life until…
  • It's a router with 4 interfaces. I'll contact support after I return from a trip in a few weeks. I was hoping someone had went thru this before & it's a quick fix...lol.
  • Thanks for the quick response! I will read the work around thread.
  • I had to contact Solarwinds support for something unrelated and asked them about this. "s for the vulnerability, since you cannot upgrade to 12.4 to resolve the vulnerability, you can limit port 17777 to communication with other related Orion NPM servers. Port 17777 is required for all API users, Additional Polling…
  • Thanks qle. I am looking into these solutions this week.
  • Thanks sotherls. I will check it out this week. Sorry for the late response, I'm a little behind on catching up with this thread.
  • Thanks for the reply. Do you know an approx. time frame that we can expect it in a future release?
  • Thanks for the reply. That's a setting that I know won't work, because it changed after the upgrade to 9.1 & we had to change it back to Mixed Status, since we don't want the status color to be red if only one site is down, when there are several sites in a map. Before the upgrade to 9.1, we were using Show Mixed Status, &…
  • Thanks for the response. We were looking at 8 total disks, so the RAID5 might be the way to go. I hadn't realized the read speed issue would decrease with a RAID10 with only 4 disks.
  • Very curious about this also. My security team is pinging me about it and we can't upgrade to 12.4 until we get the new server purchased & everything migrated, which will be around June/July, since 12.4 requires Server 2016 SP1. We weren't expecting to need to move to 2016 so early.
  • We are having the same issue. Alerts worked fine for years, through all of our upgrades. All of sudden, we stopped getting email alerts. We are getting alerts to cell phones though. When I go in and test the alert, the alert gets sent and is received. The alerts are not disabled and the email settings are correct, since I…
  • I attended the NPM training this fall in Dallas. I was really happy I did. I was very pleased with the course. The instructor not only knew the product, but he was very adept at teaching it. Pre-class, I was self taught & it could get frustrating muddling around in Solarwinds trying to figure out how to do stuff. Now I…