Guest

Preview Tool

Cisco Bug: CSCuo04528 - Way to save MSGLOGS/TRAPLOGs in a buffer on the WLC flash when rebooted

Last Modified

Aug 31, 2016

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases

7.3(101.0) 7.6(110.0) 7.6(111.0)

Description (partial)

Symptom:
Currently WLC will lose msglogs and traplogs info after reboot.. and not many mid-size or small customers deploy syslog..
 
Getting this from the device for any reload or crash may be of little help.. 

So the idea is - when ever we see a reboot on the WLC (Planned / Unplanned / Crash / Silent Crash), we should have a mechanism to save the latest msglogs and the trap logs on the flash.. may be in a buffer where in the next reload may overwrite the last logs what was collected..

Implementation Idea

•	allocate two circular buffer files out of flash, one for msglog, one for traplog, maybe 1MB each or something
•	if the tracing feature is enabled, then every 10 minutes or so, flush the last 10 minutes' worth of msgs and traps into the files
•	as part of the WLC's crash handler, flush out the latest msgs and traps to the file

We already have this feature on the AP - eventlog gets saved after a reboot

Conditions:
when ever we see a reboot on the WLC (Planned / Unplanned / Crash / Silent Crash)
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.