Wireless Access

Reply
Occasional Contributor I
Posts: 5
Registered: ‎09-16-2014

What are your best practices for testing the environment after a controller upgrade?

I've been looking around but haven't been able to find a good answer for this. Does anybody have a list of tests they do to verify they didn't introduce any new issues into their environment?

 

Something along the lines of this -  after pushing to a test controller, I connect a dell, a macbook, an iphone, and android and ensure they are all able to get online and monitor their speed rates.

Guru Elite
Posts: 21,493
Registered: ‎03-29-2007

Re: What are your best practices for testing the environment after a controller upgrade?

[ Edited ]

Seanholt,

 

Device testing after an upgrade is  typically specific to each environment

 

You should initially read the release notes to observe any announced change in behavior and test those.  You would then test all of your client-facing applications to make sure that they work in varying circumstances, in general.  You would then throw in tests for admin-facing features.  It could easily take more time than the upgrade, so focus on all client applications at minimum should be the base starting point.  If you have a lab, running many of those tests ahead of time on the build you want to upgrade to will help save time.

 

Maybe others have ideas of tests that they conduct, but again, it is only important to you if it corresponds to your environment.

 

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: