Log and Debug Commands for DPE

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.

clear logs

Use this command to remove historic (out-of-date) log files that exist on the system. These files include:

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.

Examples

debug dpe

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 List of debug dpe Commands
Command Usage	Example
debug dpe cache no debug dpe cache
Enables DPE cache debug logging, which involves messages pertaining to the DPE cache including: •Logging requests for cache entries. •Updates to the cache. •Other interactions by DPE subsystems. To disable DPE cache debug logging, use the no form of this command.	`dpe# debug dpe cache` `% OK`
debug dpe connection no debug dpe connection
Enables debugging of the DPE connection, which logs communication subsystem status and error messages. Use this command for finding communication problems between the DPE and the RDU. To disable the debugging of the DPE connection, use the no form of this command.	`dpe# debug dpe connection` `% OK`
debug dpe dpe-server no debug dpe dpe-server
Enables debugging of the DPE server, which involves logging messages about the overall status and issues of the DPE server. To disable debugging of the DPE server, use the no form of this command.	`dpe# debug dpe dpe-server` `% OK`
debug dpe event-manager no debug dpe event-manager
Enables debugging of the DPE event manager, which involves logging messages and conditions showing the state of the event manager. To disable debugging of the DPE event manager, use the no form of this command. Debugging of the DPE event manager is, by default, enabled.	`dpe# debug dpe event-manager` `% OK`
debug dpe exceptions no debug dpe exceptions
Enables debugging of DPE exceptions, which involves logging full stack traces for exceptions occurring during system operation. When unusual situations occur, where the system is apparently corrupt or behaving abnormally, running this command can reveal valuable information for the Cisco TAC support. To disable the debugging of DPE exceptions, use the no form of this command. Debugging of DPE exceptions is, by default, enabled.	`dpe# debug dpe exceptions` `% OK`
debug dpe framework no debug dpe framework
Enables debugging of the DPE framework, which involves logging information about the DPE server's underlying framework. This underlying infrastructure provides support for all of the various servers in BAC. To disable the debugging of the DPE framework, use the no form of this command. Debugging of the DPE framework is, by default, enabled.	`dpe# debug dpe framework` `% OK`
debug dpe messaging no debug dpe messaging
Enables debugging of DPE messaging, which involves logging details about the DPE messaging subsystem. This subsystem is used primarily for communication between the DPE and the RDU. To disable the debugging of DPE messaging, use the no form of this command.	`dpe# debug dpe messaging` `% OK`
debug dpe statistics no debug dpe statistics
Enables the performance statistics collection. To disable debugging of the DPE performance statistics collection, use the no form of this command.	`dpe# debug dpe statistics` `% OK`

debug on

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:

Defaults

Examples

no debug

If you run this command on an unlicensed DPE, a message similar to this one appears:

To enable debugging, use the debug on command. For more information, see debug on.

Examples

log level

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.0.

If you run this command on an unlicensed DPE, a message similar to this one appears:

Syntax Description

number—Identifies the logging level, by number, to be saved. The log levels that BAC supports are described in Table 6-2.

Table 6-2 DPE Log Levels
Log Level No.	Description
0-emergency	Saves all emergency messages
1-alert	Saves all activities that need immediate action and those of a more severe nature
2-critical	Saves all critical conditions and those of a more severe nature
3-error	Saves all error messages and those of a more severe nature
4-warning	Saves all warning messages and those of a more severe nature
5-notification	Saves all notification messages and those of a more severe nature
6-info	Saves all logging messages available

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.

Defaults

The level of minimum DPE log messages that will be saved is, by default, set at 5-notification.

Examples

show log

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.

Syntax Description

•

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.

Examples

Note

The output of this command has been shortened for demonstration purposes.

Table Of Contents