Higher Education

last person joined: 16 days ago 

Got questions on how to enable mobility in education? Submit them here!
Expand all | Collapse all

controller load

This thread has been viewed 0 times
  • 1.  controller load

    Posted Sep 17, 2013 02:37 PM

    Hi,

     

    We have a  sudden increase in the number WLAN users after we embrace BYOD, now WLAn is slow, how would I measure the controller load and traffic to make sure that our controller is resource capable of handling the current traffic/no bottleneck in terms of controller hardware.

     

    Thank you



  • 2.  RE: controller load

    Posted Sep 17, 2013 02:47 PM

    Take a look at:

     

    show datapath utilization

    show cpuload

     

    Also, it also wouldn't hurt to make sure that you are saturating your uplinks into the controllers.



  • 3.  RE: controller load

    EMPLOYEE
    Posted Sep 17, 2013 03:15 PM

    @nointerference wrote:

    Hi,

     

    We have a  sudden increase in the number WLAN users after we embrace BYOD, now WLAn is slow, how would I measure the controller load and traffic to make sure that our controller is resource capable of handling the current traffic/no bottleneck in terms of controller hardware.

     

    Thank you


    noninterference,

     

    Wifi contention is typically the problem before controller network utlization/resources.   A good rule of thumb is to have a gigabit port for  each 100 access points you have connected to the controller.  Check to see what else could be your bottleneck here:  http://community.arubanetworks.com/t5/Technology-Blog/Removing-the-Bottleneck-in-Wireless/ba-p/77978



  • 4.  RE: controller load

    Posted Sep 17, 2013 04:08 PM

    More data is needed here, what controller, how many ap's, how many users.  How is your network designed, could this be a broadcast issue, possibly turning on the  BCMC (Broadcast-Multicast) Optimization feature may take care of it?



  • 5.  RE: controller load

    Posted Sep 17, 2013 08:28 PM

    A 5 minute wireshark while 'parked' on an SSID would be a good idea.  Then evaluate the 'pie chart' for proportions of BC, MC, Protocol A, B, C.      "Before" info is valuable to have as we manipulate the Nerd-Knobs to tweak performance and gain "After" performance data.