This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Storage Manager - I give up

dereksn over 9 years ago

For the last couple of weeks I have been troubleshooting all sorts of issues with the Storage Manager product. One minute it collects just fine, then the next it fails. I have several tickets open with Solarwinds and still no resolution. I am curious can anyone provide an idea of specs for the agents. I see no contention with memory or anything according to the Storage Manager Health Status. They keep saying its a connectivity issue between my netapp - which I am really doubting because I have other alerts (Netapp Oncommand, etc.) and witness no failures.

I am at a loss as this product being a monitoring solution is really failing me. I feel like I am the only customer on this. I want to add another array to this but until I can get consistent data from it I will have to stick to the NetApp toolset as its the only thing that is reliable.

Do most shops have a full time Monitor Admin?

/end rant

0 rupdegraff over 9 years ago

I wish I had an answer for you, but unfortunately I'm in the same boat. It's almost refreshing to see that I'm not the only one.
I've been trying to get STM to collect from 2 NSeries (NetApp), 1 DS5020, 1 DS8000 and 1 SVC from an agent with 2 CPUs and 8 GB of RAM. The other agent has the same specs and only collects from an SVC and DS8000 (so far.) The busier agent is unreliable and frequently misses the collection interval and then tells me there is a problem. The other is fairly stable, but I have issues with it periodically as well. I've tweaked the SolarWinds.Storage.Agent.ini with the direction of support, but problems persist. I'm working with an escalation engineer now.
I'm ready to call Solarwinds and get a refund!
Cancel
Vote Up 0 Vote Down

Cancel
0 KMSigma.SWI over 9 years ago in reply to rupdegraff

rupdegraff & derekd, I'm escalating your cases internally.
I have the case numbers as 685309 (derekd) and 704094 (rupdegraph). Please confirm that these are correct.
We never want our customers to experience issues like these. I will get any resources that are necessary online to assist.
--KMSigma
Cancel
Vote Up 0 Vote Down

Cancel
0 rupdegraff over 9 years ago in reply to KMSigma.SWI

That is the correct ticket number for me. Thanks for your help
Cancel
Vote Up 0 Vote Down

Cancel
0 jthomas4000 over 9 years ago in reply to rupdegraff

We had to bump up the java heap sizes...
Cancel
Vote Up 0 Vote Down

Cancel
0 rupdegraff over 9 years ago in reply to jthomas4000

I’ve made changes to the Java memory size in the config file, but can you give details so we can all be on the same page?
Thanks
Bob Updegraff
Cancel
Vote Up 0 Vote Down

Cancel