Wireless Access Point Keeps Crashing Collect Crash Log

An access-point is crashing or resetting and you need to  collect the crash logs:

An example error in your Wireless LAN Controller Events :


 Now we can check the AP and log into it directly to to check the log files by doing a 
                 "show log"

                  "show stacks"

These commands will display a couple items that you a generally looking for in regards to the AP continuously resetting or disconnecting. Reasoning codes, errors, crash log information upload.

The Crashlog file of the AP is uploaded to the WLC with the reasons after the AP has come back online and reassociated itself. So to collect this complete log we can get it from the WLC because it should then be removed from the AP.

After obtaining the information you can log into the WLC and do a show ap crash-file  this will show the file inside the flash of the WLC.  
 
In order to obtain the crash file you can do a couple items:

Get information from WLC GUI:
1. Log into the WLC 
2. Click Management Tab
3. Go to Tech Support Under Management
4. Click AP Crash Log 


Get information from WLC CLI:

 show ap crash-file
 show ap crash-file APNAME

Comments

Post a Comment

Popular posts from this blog

HULC LED PROCESS - 3750 High CPU

Image
If you're looking at a switch and you see the HULC LED Process running high. The HULC LED process does some of the following tasks: 1. Check link status on every port 2. If the switch supports POE, it checks to see if there is a power device 3. Transceiver checks 4. Fan status updates 5. Set LED ports 6. Check on temperature status Overall the HULC LED Process is a monitoring process running. During looking into this I turned off all non-used ports since it checks the link status. Then I made sure the environment was good. Two Cisco Bugs: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsi78581 http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn42790
Read more

Cisco Tomcat High CPU Utilization 99 percent

Image
So a client was experience slow web interface usage to their calling node. As well RTMT was shooting off the alert. The alert is for Call Process CPU Node Pegging.  The culprit tomcat! Cisco Tomcat Service -  In enterprise edition this is a web server service. In the business edition (BE Servers) this uses the web server and unity utilizes the service as well. Log in to each call manager node and issue the following command: show process load cpu **OUTPUT** top - 08:55:48 up 340 days, 4:03, 1 user, load average: 4.64, 3.25, 2.98  Tasks: 142 total, 2 running, 140 sleeping, 0 stopped, 0 zombie  Cpu(s): 16.3%us, 3.4%sy, 0.0%ni, 80.1%id, 0.1%wa, 0.0%hi, 0.2%si, 0.0%st  Mem: 4016964k total, 3856400k used, 160564k free, 29904k buffers  Swap: 2064280k total, 1664k used, 2062616k free, 598124k cached  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND  8065 tomcat 25 0 2317m 1.9g 22m S 99.4 50.4 358084:37 tomcat  1 root 15 ...
Read more