Wireless Access

Reply
Contributor II

Controller debug limits

Hi, 

 

I get asked this question a lot, but do not know the official answer to it so I thought I post it out there as I cannot find any community links about it. So here goes...

 

In the controller you can run debug for various things, the common debug I have used is the user-debug. Is there any limit on the amount of debug you can run on the controller when it starts impacting performance. For example, is there a limit on the amount of user debug you can run from the controller?

 

Also, is there a limit on the other debugs as well ?

 

 

Guru Elite

Re: Controller debug limits

I would run a "show cpuload" on the controller before your turn on debugging.  If at any time it stays at 80% or above, I would not turn on debugging.

 

After you turn on debugging, once again check to make sure it is not at 80% or above sustained.  If it is not, you are probably okay.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Contributor II

Re: Controller debug limits

Thank you for the answer. 

 

So what I get from your answer is the amount of debugs that could be run on a controller depends on the resources of the controller ? Is this correct ?

Guru Elite

Re: Controller debug limits

Correct.

 


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: