Wireless Access

last person joined: 15 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

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

This thread has been viewed 0 times

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

    Posted Oct 23, 2014 03:42 PM

    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.



  • 2.  RE: What are your best practices for testing the environment after a controller upgrade?
    Best Answer

    EMPLOYEE
    Posted Oct 24, 2014 05:48 AM

    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.