Guest

Preview Tool

Cisco Bug: CSCvt92243 - COS APs not updating syslog level post rejoining the WLC

Last Modified

Aug 21, 2020

Products (1)

  • Cisco Aironet 1850 Series Access Points

Known Affected Releases

8.10(118.77)

Description (partial)

Symptom:
Set up:
WLC : 3504 on 8.10.118.77(8.10MR3 build)
Aps : 1832 (1 No.), 3802 (1 No.), 9115 (1 No.)
 
Steps:
All Aps joined the WLC.
Change the syslog level to ?debug? via WLC (config ap logging syslog level debugging all)
All AP successfully updated its syslog level to debug
Now let’s change the syslog level to ?alert? via WLC (config ap logging syslog level alerts all)
Simultaneously we will do a capwap restart on one AP ( capwap ap restart). We will have the respective commands ready on WLC and AP. First we execute the capwap restart on AP and then immediately change the logging level from WLC.
 
Observations:
AP where capwap restart was not done successfully changes its log level to alert.
AP where capwap restart was done, continues to be in ?debug? level post its rejoin to the WLC.
If we again set loglevel from WLC either specifically for that AP or for all Aps, AP is setting the new loglevel.
 
Excerpts from Log:
 
WLC logs:
*spamApTask0: Apr 16 11:03:32.745: [PA] 08:ec:f5:9c:e0:60 Received syslog trap level info from AP AP3802_2. Level: 3, save flag: True
*spamApTask0: Apr 16 11:03:32.745: [PA] Received LOG_TRAPLEVEL_PAYLOAD
 
Since save flag is set to TRUE, WLC is not pushing the new log level (Alert in our case) to the AP. Hence AP is continuing with its previous set log level.

Conditions:
Set up:
WLC : 3504 on 8.10.118.77(8.10MR3 build)
Aps : 1832 (1 No.), 3802 (1 No.), 9115 (1 No.)
 
Steps:
All Aps joined the WLC.
Change the syslog level to ?debug? via WLC (config ap logging syslog level debugging all)
All AP successfully updated its syslog level to debug
Now let’s change the syslog level to ?alert? via WLC (config ap logging syslog level alerts all)
Simultaneously we will do a capwap restart on one AP ( capwap ap restart). We will have the respective commands ready on WLC and AP. First we execute the capwap restart on AP and then immediately change the logging level from WLC.
 
Observations:
AP where capwap restart was not done successfully changes its log level to alert.
AP where capwap restart was done, continues to be in ?debug? level post its rejoin to the WLC.
If we again set loglevel from WLC either specifically for that AP or for all Aps, AP is setting the new loglevel.
 
Excerpts from Log:
 
WLC logs:
*spamApTask0: Apr 16 11:03:32.745: [PA] 08:ec:f5:9c:e0:60 Received syslog trap level info from AP AP3802_2. Level: 3, save flag: True
*spamApTask0: Apr 16 11:03:32.745: [PA] Received LOG_TRAPLEVEL_PAYLOAD
 
Since save flag is set to TRUE, WLC is not pushing the new log level (Alert in our case) to the AP. Hence AP is continuing with its previous set log level.
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.