Preview Tool

Cisco Bug: CSCvv35528 - CUCM and IM and Presence Trace Level inconsistent between GUI and CLI

Last Modified

Sep 28, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

11.5(1.18000.177) 11.5(1.21000.1) 11.5(1.88200.47) 12.5(1.11001.142) 12.5(1.13034.1) 12.5(1.13900.149) 12.5(1.13900.151) 12.5(1.22900.19)

Description (partial)

When the Trace Levels are seen in the Database, it shows up differently. For instance when the following CLI command is executed:

run sql select one.nameforcontrol as service, as trace_level, three.enable, three.servername from typeservice as one, typetracelevelgrouping as two, processnodeservice as three where one.enum=three.tkservice AND two.tktracelevelgroups=one.tktracelevelgroups AND three.tracelevel=two.value

The Output shows Cisco DRF Master Trace Level at "Detailed" whereas if you actually navigate to the Unified Serviceability > Trace > Configuration > Select the Server > Service Group of Backup and restore Services > Service of Cisco DRF Master it shows up as "DEBUG"

This cosmetic defect is to correct the behavior and make it consistent so that the customer can use these CLI commands to have a quick survey of what are the trace level and then do not get confused when trying to fix the trace level from the GUI.

This applies to all versions of CUCM and IM and Presence clusters
Bug details contain sensitive information and therefore require a 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.