The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the command line interface (CLI) commands that you can use to debug the Broadband Access Center (BAC) Device Provisioning Engine (DPE), and monitor and manage the BAC log system.
Note Before using any debug command, ensure that DPE debugging is enabled. Run the debug on command to enable this function. See debug on, for more information.
The commands described in this section are:
Use this command to remove historic (out-of-date) log files that exist on the system. These files include:
•DPE logs
•Syslog
Over time, historic log files accumulate in the DPE. The support bundle state command is used to bundle these logs. Cisco recommends that you create a bundle before clearing logs to ensure that no necessary files are accidently lost.
After this command is used, prompts appear to indicate that logs are being cleared. The number of log files that are cleared is also identified.
dpe# clear logs
Clearing historic log files...
+ Removing 1 DPE log files...
+ No more historic logs.
The debug dpe is the global syntax of the commands that you use to debug the various services on the DPE.
Note If you run the following commands on an unlicensed DPE, a message similar to this one appears:This DPE is not licensed. Your request cannot be serviced.
Please check with your system administrator for DPE licenses.
Table 6-1 describes the various commands you can use to debug the DPE.
Use this command to enable debug logging, which can be helpful when troubleshooting possible system problems. Additionally, specific debugging categories must be enabled separately with commands such as debug dpe cache.
To disable debug logging, run the no debug command. See no debug, for more information.
If you run this command on an unlicensed DPE, a message similar to this one appears:
This DPE is not licensed. Your request cannot be serviced. Please check with your system administrator for DPE licenses.
Debug logging is, by default, enabled.
dpe# debug on
% OK
Use this command to disable all debug logging.
If you run this command on an unlicensed DPE, a message similar to this one appears:
This DPE is not licensed. Your request cannot be serviced. Please check with your system administrator for DPE licenses.
To enable debugging, use the debug on command. For more information, see debug on.
dpe# no debug
% OK
Use this command to set the level of minimum DPE log messages that will be saved, as described in the Cisco Broadband Access Center Administrator's Guide, Release 3.5.
If you run this command on an unlicensed DPE, a message similar to this one appears:
This DPE is not licensed. Your request cannot be serviced. Please check with your system administrator for DPE licenses.
log level number
number—Identifies the logging level, by number, to be saved. The log levels that BAC supports are described in Table 6-2.
Note Setting a specific log level saves messages less than or equal to the configured level. For example, when you set the log level at 5-notification, all events generating messages with a log level of 4 or less are written into the log file.
The logging system's log levels are used to identify the urgency with which you might want to address log issues. The 0-emergency setting is the most severe level of logging while 6-info is the least severe, saving mostly informational log messages.
The level of minimum DPE log messages that will be saved is, by default, set at 5-notification.
dpe# log level 6
% OK
Use this command to show all recent log entries for the DPE. These logs contain general DPE process information, including logging all system errors or severe problems. Check this log when the system is experiencing difficulties. If the log contains insufficient information, enable the debug logging function and experiment with the different categories related to the problem.
show log [last 1..999 | run]
•last 1..999—Shows the specified number of recent log entries for the DPE, with 1..999 specifying the number of log entries that you want to display. This element is optional.
•run—Displays the running DPE log, which starts showing all messages logged to the DPE log. The command continues to run until you press Enter. This element is optional.
Example 1
dpe# show log
2006 02 14 07:50:26 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: ThreadMonitor:
BACThread[Connector,5,BAC,alive]
Note The output of this command has been shortened for demonstration purposes.
Example 2
dpe# show log last 3
2006 02 14 07:51:26 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: ThreadMonitor: Cwmp1Thread-1
2006 02 14 07:51:26 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: ThreadMonitor: Http1Thread-0
2006 02 14 07:51:26 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: ThreadMonitor: Http1Thread-1
Example 3
dpe# show log run
% Press <enter> to stop.
2006 02 14 07:53:22 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: OSStatusService: current CPU load percentage 1%
2006 02 14 07:53:25 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: MemoryMonitor: Memory:
2006 02 14 07:53:25 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: MemoryMonitor: Total memory 29777920
2006 02 14 07:53:25 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: MemoryMonitor: Free memory 4058120
2006 02 14 07:53:26 EST: %BAC-DPE-7-DEBUG_FRAMEWORK: ThreadMonitor: Threads:
Stopped.