lcsw2013 ✭✭✭✭✭

Hmmm. I've noticed a few other posts in the community indicating this same behavior. adatole​ Do you know if this is a known issue by chance?

As expected a few new questions came up as meetings have taken place and the initial deployment design is maturing into something that's more ready for a POC. We have 3 DC's. DC 1, DC 2, DC 3 (Cloud). We have the primary on DC 2. APE's across all three DC's. Wed servers on 2 DC's, etc. Here is a question that came. We plan…

This is amazing. Having fallen behind just a tad bit due to other things and solarwinds aggressively releasing new features means I was unaware about several of these features. And apparently need to do some homework on to catch back up. This answers plenty and gives me a general idea of where I should take our design and…

aLTeReGo​ adatole​ Guys can you possibly provide some insight and help please? If not direct me to the right product manager whom we could get some solid answers from? We are kind of bumping up against some dead lines and need solid answers we haven't been able to find. Any help is greatly appreciated. Thanks!

I found the issue. we have 97 groups set. Some dynamic. And they are all refreshing together. This is killing swis v3 with trying to query the database. This is what has been killing the site. Working on the groups refresh has resolved the issue

I think I have figured it out. I noticed that every time swis v3 became unstable there was what appear to be a dynamic query built way before I took over this environment. This query was built to get the devices for a specific group. When the query ran it ran multiple times and the execution time got longer and longer…

Opsgenie didn't fit our work model. We have a work flow of all alerts getting funneled through a triage team that does initial analyses and troubleshooting before dispatching to correct teams.

Just basing on the limited information it sounds like your job engine might not be running and or it might be having problems. When you notice the dots go grey, are any other data points obsolete? Any other devices showing grey in normal monitoring? Anything else outside of netpath that could be popping out as a potential…

This is something I believe adatole​ Might be able to give some insight on. Seems a bit weird to me that it would work on email but not on the display.

Not sure what versions this applies to. But I upgraded from 12.1 to 12.2 and have been having many similar issues mentioned on this thread. So thought I would post as well. Have had many cases opened due to a large number of issues going on. Seems like never ending as per every one issue fixed there is another 10 to…

No response? Any help? Please?

What kind of device is it? I ask because as far as I'm aware I don't believe this is possible, but yet I'm not entirely sure. There might possibly be a way to do something through SDK I believe for the API side. But I myself have not worked with the SDK long enough to say how. If you could share the type and make and model…

I agree with the other responses. In your case setting it to unplugged seems to be the best option. This way you don't have to remove re-add constantly. No need to have to keep rechecking things, etc. You monitor them. Chose the ones that aren't critical set unplugged to try and only get alerted when critical interfaces…

From my experience there shouldn't be anything to worry about if you make sure to have your settings set to not import duplicates. Network discovery can automatically ignore duplicates.

Windows 2003 are our biggest pain points. Suggested we move them to snmp and rpc combo, but idea was denied and was told Agents is the only option they want to go with. Thankfully though management has said that we are dwindling and reducing the number of 2003 servers. But it'll take time and the ones currently active need…

So we are slowly backing away from agent polling. And only using it on servers that actually need it. DMZ server I believe in our case will just have to wait. We have a palo alto that's directing traffic to and from and that palo alto is just a nightmare when it comes to solarwinds traffic as it allows some but not all to…

In our environment we have a mix of servers and network devices around 5000 devices monitored with around 70,000 elements monitored if not more. We have this across 7 pollers, 1 primary and 6 additional. And haven't had any problems since deployment. We forecast for future growth and over provisioned our vm's. This way we…

This sounds to me like it could potentially be related to IIS. Have you ran configuration wizard and attempted to rebuild the website? Have you attempted to restart the IIS services? Have you checked the web log files in the solarwinds folder for possible clues? I would say that a configuration wizard run should be able to…

I found the issue. we have 97 groups set. Some dynamic. And they are all refreshing together. This is killing swis v3 with trying to query the database. This is what has been killing the site. Working on the groups refresh has resolved the issue

Any ideas from the community? Anyone who might know?

Can you post up a snapshot of your conditions for the alert? This will help visualize things a little bit better.

Exactly! I share your pain in many similar ways. I love thwack for this very reason. Usually when I have issues I can’t resolve or find a reason too I come on here. I look at Solarwinds support team for more basic common problems and go through complex problems on my own. I took experience the instabilities you mentioned…

Port 161 is for snmp communication while 162 is for snmp traps. Two different functions. Have you tried doing a packet capture from the solarwinds server to the device to see if it's properly replying? Have you checked to see if the access lists are correct? Are there any firewalls blocking access? Have you checked your…

We tried to reach out to a consulting company but got voice mail. Left messages and no one returned for a long time. By the time they returned, through calls to solarwinds we ended up solving alot ourselves. I appreciate the help. When we were considering weather to upgrade in-place or build a new environment and move…

So it looks like our issue has to do with extremely huge tables. over 1 million rows of data over 2 gigs in space. Simple query (Select statements) to these tables spins and spins until it errors out. Trying to decrease size to see if it reduces the problem to manageable size or truncating table and starting fresh.

Most of ours are custom. Out of the box are basic and work great. However, it is only might to give a real high level view. I'll give you an example, Reboot alerts, If you received an alert that just says "Server has rebooted" how helpful would that be to you? It has no substance. But now if you had an alert that give you…

This all sounds perfect. I don't know if it's me or what but I try it I still end up with errors. Here is where I hit I snag. I go into custom property. I set a property for node. I use text format. And I use something similar to Windows server = wintel dl. So in other words anything in windows group has the wintel dl…

I believe all discovery related logs should be in this directory (Or similar) : C:\ProgramData\Solarwinds\Discovery Engine. The discovery engine logs should give you an idea of what failed. I would say try OrionDiscoveryJob.log, It should give you what you are looking for.

Have you tried looking into opsgenie? It integrates with solarwinds. And might possibly provide you with the interface you maybe looking for. They are somewhat similar to alert central that solarwinds used to have before they killed that off and decided to go with opsgenie instead. Might be worth looking into it. Alerts is…

Have you tried using netpath in NPM? It may not be the cleanest way to do what your attempting to do. But it might just work for what your attempting to complete. May be worth a shot!