Cisco Headend System Release 2.7 Release Notes
SR 2.7 at a Glance
4012155 Rev B
9
Dynamic Logging
SR 4.0 first introduced a new Logging utility to make it easier than ever to capture
key troubleshooting information.
key troubleshooting information.
The new Logging utility allows an operator to manipulate those logs that Cisco
historically considered "Developer-Only" debug logging. Specifically, these are the
EMCDEBUG logs that reside in the /dvs/dncs/tmp directory that, in the past,
required process restarts for activation. These process restarts were quite
inconvenient and could, at times, result in disruption of some services. These
disruptions occurred usually at the least opportune time, for example, when an issue
required troubleshooting.
historically considered "Developer-Only" debug logging. Specifically, these are the
EMCDEBUG logs that reside in the /dvs/dncs/tmp directory that, in the past,
required process restarts for activation. These process restarts were quite
inconvenient and could, at times, result in disruption of some services. These
disruptions occurred usually at the least opportune time, for example, when an issue
required troubleshooting.
In order to streamline this problem-solving process and to remove any adverse
impact on functionality, Cisco developed the new logging utility. This new utility
allows you to fine-tune log levels for DNCS processes and their associated libraries
in much the same manner as the legacy DNCS Tracing utility (which is unaffected
by this new tool).
impact on functionality, Cisco developed the new logging utility. This new utility
allows you to fine-tune log levels for DNCS processes and their associated libraries
in much the same manner as the legacy DNCS Tracing utility (which is unaffected
by this new tool).
As a reminder, the legacy DNCS Tracing Utility allows dynamic activation, provides
fine-grained control over DNCS processes and their respective libraries, and saves its
output into the /var/log/dncsLog file. This logfile continues to contain information
that DNCS software developers considered appropriate to assist customers in their
day-to-day operation of the DNCS Application. Additionally, this content included
information about all DNCS processes.
fine-grained control over DNCS processes and their respective libraries, and saves its
output into the /var/log/dncsLog file. This logfile continues to contain information
that DNCS software developers considered appropriate to assist customers in their
day-to-day operation of the DNCS Application. Additionally, this content included
information about all DNCS processes.
In contrast, the SR 4.0 Logging Utility was focused on the more detailed debug
logging. The following list includes some of the highlights of this feature:
logging. The following list includes some of the highlights of this feature:
Dynamic Activation
Integrated DNCS User Interface using a Web browser user interface
Seven levels of logging detail, all while retaining the operation of the detail
output, which are deposited into a per-process set of Generation Log Files that
use the naming convention /dvs/dncs/tmp/[name of process.*]
output, which are deposited into a per-process set of Generation Log Files that
use the naming convention /dvs/dncs/tmp/[name of process.*]
Important! If you are using Cisco's RCS solution, you can use this utility to capture
DEBUG logging information about the processes and libraries for each site in your
system.
DEBUG logging information about the processes and libraries for each site in your
system.
Another key benefit of the logging utility is that logging level changes are now
allowed without the need to restart processes.
allowed without the need to restart processes.
Note: For more information on how to use log files to maintain a healthy system, see
the DNCS Online Help or the Maintenance Recommendations for the DBDS System
Guide.
the DNCS Online Help or the Maintenance Recommendations for the DBDS System
Guide.