Guest

Preview Tool

Cisco Bug: CSCvi11595 - 8.7:Restriction required for the interaction message log severity setting vs. buffer debug enable

Last Modified

Mar 13, 2018

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases

8.7(1.139)

Description (partial)

Symptom:
There is interaction between message log severity and buffer debug enable. In this particular case, event log could show show in message log even though message log is set to Error level.


CSCvi11595 is to document update to https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-6/config-guide/b_cg86.pdf .

Step 3 To set the severity level for filtering syslog messages to the syslog servers, choose one of the following options from the Syslog Level drop-down list: o Emergencies = Severity level 0 o Alerts = Severity level 1 (default value) o Critical = Severity level 2 o Errors = Severity level 3 o Warnings = Severity level 4 o Notifications = Severity level 5 o Informational = Severity level 6 o Debugging = Severity level 7 Cisco Wireless Controller Configuration Guide, Release 8.2 934 Configuring System and Message Logging If you set a syslog level, only those messages whose severity is equal to or less than that level are sent to the syslog servers. For example, if you set the syslog level to Warnings (severity level 4), only those messages whose severity is between 0 and 4 are sent to the syslog servers.

Expect update here something like:
Restriction: If "config logging debug buffered enable", some messages from the application debug could show in message log with severity more than the level set. For example, if "debug client <Mac>", client event log could show in message log even though message severity level is set to Error.


(tb30-khanda-70) >show logging         

Logging to Logger Queue : 
- Logging of system messages to Logger Queue : 
 - Effective Logging Queue filter level.......... errors
Logging to syslog : 
- Syslog facility................................ local2
- Logging of system messages to syslog : 
 - Logging filter level.......................... errors


But the following messages showing in message log incorrectly:

Issue 1,
*nim_t: Feb 20 20:49:41.397: %SIM-3-PORT_UP: [PA]Physical port 4 is up!.
*nim_t: Feb 20 20:49:41.397: %SIM-3-PORT_UP: [PA]Physical port 3 is up!.
*nim_t: Feb 20 20:49:41.397: %SIM-3-PORT_UP: [PA]Physical port 2 is up!.
*nim_t: Feb 20 20:49:41.396: %SIM-3-PORT_UP: [PA]Physical port 1 is up!.

Issue 2,
*osapiBsnTimer: Feb 20 20:50:13.083: %NIM-3-ADMIN_MODE_ENABLE_RETRY: [PA]Port 4 Admin Mode is Enabled (retry-1)!
*osapiBsnTimer: Feb 20 20:50:13.083: %NIM-3-ADMIN_MODE_ENABLE_RETRY: [PA]Port 3 Admin Mode is Enabled (retry-1)!
*osapiBsnTimer: Feb 20 20:50:13.083: %NIM-3-ADMIN_MODE_ENABLE_RETRY: [PA]Port 2 Admin Mode is Enabled (retry-1)!
*osapiBsnTimer: Feb 20 20:50:13.083: %NIM-3-ADMIN_MODE_ENABLE_RETRY: [PA]Port 1 Admin Mode is Enabled (retry-1)!

Conditions:
na
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.