Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Wireless Environment / NPM

A lot of promises were made since the wireless module for thick clients went the way of the dodo bird.

Since then, NPM and the suite in general has grown by leaps and bounds with several releases that have included limited thin client support. I suspect there are development reasons for the delay in this element of NPM growing up, conidering how obviously critical this kind of visibility is in the enterprise. It has also strangely absent from upcoming feature discussions I have read.. if that has changed feel free to correct me... i stopped looking.

Any word on this front?

Find more posts tagged with

wireless

Accepted answers

fcaron

Hi SLXer,

Good input, tks for taking the time. I'll contact you off line to discuss about this lack of wireless historical info and impact on ability to troubleshoot issues.

All comments

bshopp

Can you elaborate on what you would like to see more? Is this a vendor support question or what other features are you wanting in this arena?

FormerMember

Ive posted all this before but if you are familiar with the original wireless module there isnt much of a comparison and it shouldnt really require a customer to outline the differences for Solarwinds. But i will humor you.

What makes NPM... NCM... APM.. Netflow... etc all valuable is historical visibility that provides a perspective valuable for trouble shooting, behavior characterization, capacity planning and so on.. The wireless module also provided this.. The NPM wireless component has no historical capability.. Not for AP's Not for SSID's, Not for users, Not for Signal, Not for client association.. (AP or user) not by mac address, not by IP address.

Illustration #1.

Hmm what to do with this view? Search?... Client names?.. right.. how about ip? how about a mac address? how about a time frame? How about clicking on any of the elements in this view for the associated historical information. Why arent the AP's names visible? Im thinking you can appreciate the absense of value in being able to see a client associated but not know where. Showing signal strength in relation to an uknown IP is also of.. questionable value.. and without a historical reference for the normal client behavior.. i think your getting the idea.. again all this functionality was part of the original wireless module and it was a very useful tool.

This view at least shows you a host name associated with an AP.. and there is some value in being able to search AP's by wild card but other than that really its the same story.. The real value comes having a historical perspective..

I hope this helps.. If there is anything i can do to help please dont hesitate to give me a call

fcaron

Hi SLXer,

Good input, tks for taking the time. I'll contact you off line to discuss about this lack of wireless historical info and impact on ability to troubleshoot issues.

fcaron

Tks for input (66271).

Any other user of the wireless module interested in improving (restoring) this history tracking capability, in order to facilitate Wireless troubleshooting scenarios (e.g. this user calls me and complains that he can't connect).