MarieB replied on Thu, Oct 8 2009 1:52 PM

rated by 0 users

Hi Dave--

You will have to create a new Universal Device Poller (UnDP) for the specific RSSI you want to chart. Here's the online help for that:

http://www.solarwinds.com/NetPerfMon/SolarWinds/wwhelp/wwhimpl/js/html/wwhelp.htm#href=OrionAGMonitoringCustomMIBsCreate.htm

Then you will have to create the report for it. Here's the online help for that:

http://www.solarwinds.com/NetPerfMon/SolarWinds/wwhelp/wwhimpl/js/html/wwhelp.htm#href=OrionAGCreatingReports.htm

Unless someone in the community has already done this and can just share. Anyone?

Thanks,

M

dstj replied on Fri, Oct 9 2009 9:27 AM

rated by 0 users

Thanks for the reply Marie,

Any reason why we can't get that feature back ?

Seems a shame to lose features when upgrading NPM.

Especially when i paid for that feature when i purchased the Wireless Module less than half a year ago.

Dave

MarieB replied on Fri, Oct 9 2009 9:39 AM

rated by 0 users

Hi Dave--

Let me get your post over the NPM product manager just to maks sure the option's not available.

M

dstj replied on Fri, Oct 9 2009 9:58 AM

rated by 0 users

Good stuff, thanks.

rgward replied on Wed, Feb 3 2010 2:57 PM

rated by 0 users

Is RSSI fixed in 9.5.1?

MarieB replied on Thu, Feb 4 2010 11:46 AM

rated by 0 users

Hi rgward--

Here's what's fixed in 9.5.1. I'll also mark this for the product manager.

M

rgward replied on Mon, Feb 8 2010 5:31 PM

rated by 0 users

Thanks Marie but the thread doesn't mention any fixes in the wireless area.  Since the RSSI reporting was broken by the developers going from v9.1 to v9.5, I would expect this would have a high degree of priority to fix in the next stability release, i.e., v9.5.1 .   So, it would be helpful if the product manager would chime in here.

rgward replied on Fri, Feb 12 2010 8:15 AM

rated by 0 users

Well, never heard from the product manager.  Finally got around to doing a upgrade to 9.5.1 on our Dev system and found out... NOPE, still not fixed.

I don't get it!  I don't understand SolarWinds logic behind fixing bugs, expecially ones like this one.  They have acknowledged they broke RSSI reporting in 9.5 that worked in 9.1, yet they don't give it priority to fix the problem either with a hot fix or in the very next stability release.  Sometimes, the issues seem would be simple to fix with a minimal correction to the code but, for reasons beyond my compehension, they never get addressed in the very next code release.  Sometimes it takes many releases before they are fixed.  I've never experienced a company like this before that doesn't respond to breaks in existing functionality in a timely manner.  I've worked with IBM, Cisco, Unisys and a few other networking companies and they respond quickly to fixing problems they inadvertantly break in a new release.  They take serious fixing bugs and breaks in a very timely manner measured in days and weeks, not months.  I just don't get it!  I hope SW is listening and will revisit establishing their priorites in regard to breaks and bugs.  This isn't the only case I've seen handled in this way but I thought this was an opportunity to express my disappointment and dissatisfaction in how SW has dealt with this problem.  I've been considering opening a thread about this topic to give other customers an opportunity to express their views.   Strength is in numbers.

MarieB replied on Fri, Feb 12 2010 9:52 AM

rated by 0 users

Hi rgward--

I'm going to email the PMs directly so that they can address your issues. However, if you'll look earlier in the thread, Brandon does address the issue and offer a workaround.

Thanks for your feedback,

M

denny.lecompte replied on Fri, Feb 12 2010 10:53 AM

rated by 0 users

rgward:

They have acknowledged they broke RSSI reporting in 9.5 that worked in 9.1

rg,

Just to be clear, this is functionality we would like to add to NPM, but we didn't break it in the sense you're implying.  RSSI monitoring was part of the old Wireless Network Monitor.  That product was discontinued.  At the same time, we added native wireless functionality to NPM.  We tried to make the native wireless functionality close to the old module with the addition of lots of new functionality such as support for wireless controllers.  Despite those efforts, we did not add 100% of the same features to NPM. 

This distinction is important because we do not view the RSSI feature as something we broke.  When we accidentally break a feature, replacing it is a high priority.  Because you clearly think we should have 100% of the functionality of the module we EOL'd, I can see why our approach to this issue doesn't make sense to you.  We view it as a feature, and you see it as a bug.

I hope that clarifies our behavior, but I'm afraid we're going to stick by our interpretation.  We killed the old Wireless module and provided comparable and expanded functionality for no additional cost as part of NPM.  We did not commit to carrying forward every feature. 

I'm not saying we won't add this feature to NPM.  It's a good feature, but it will be treated as a feature request, not a bug. 

I appreciate that this answer is probably not going to make you happy, and I am happy to listen to you directly.  We can get on the phone (you, me, and Brandon, since he's the PM who owns NPM) and discuss.