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 Prime Cable Provisioning Device Provisioning Engine (DPE), and monitor and manage the Prime Cable Provisioning log system.
Before using a debug command, you must enable DPE debugging by running the debug on command. 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 a DPE license.
The commands described in this chapter are:
Use the clear logs command to remove historic (out-of-date) log files that exist on the system. These files include:
Over time, historic log files accumulate within the DPE. You can use the support bundle state command to bundle these logs. We recommend that you create a bundle before clearing logs, so that no necessary files are lost accidently.
Use the debug dpe command to configure debug settings on the DPE. Table 6-1 describes the keywords that you can use with this command.
Note Enter the commands described in Table 6-1 as indicated.
Use the debug on command to enable debug logging, which can be helpful when troubleshooting possible system problems. Additionally, you must separately enable specific debugging categories with commands such as debug dpe cache.
To disable all the categories of debug logging, run the no debug all command. See no debug all.
Use the debug service tftp ipv4 | ipv6 command to enable debugging of TFTP transfers for IPv4 or IPv6.
To disable debugging of the TFTP service, use the no form of this command. See no debug service tftp ipv4 | ipv6.
This result occurs when you enable debugging of the TFTP service for IPv4.
This result occurs when you enable debugging of the TFTP service for IPv6.
Use the no debug service tftp ipv4 | ipv6 command to disable debugging of TFTP transfers for IPv4
or IPv6.
To enable debugging of the TFTP service, see debug service tftp ipv4 | ipv6.
This result occurs when you disable debugging of the TFTP service for IPv4.
This result occurs when you disable debugging of the TFTP service for IPv6.
Use the no debug all command to disable all the categories of debug logging.
For details about enabling debug logging, see debug on.
Use the log level command to set the level of minimum DPE log messages that are saved, as described in the Cisco Prime Cable Provisioning 6.1.1 User Guide.
number —Identifies the logging level, by number, to be saved. Table 6-2 describes the log levels that Prime Cable Provisioning supports.
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.
Use the show log command to show all recent log entries for the DPE. These logs contain general DPE process information, including 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. See debug dpe, for detailed information.
show log [ last 1..999 | run ]
This result occurs when you use the show log command.
Note The output presented in this example is trimmed for demonstration purposes.
This result occurs when you use the show log last command.
This result occurs when you use the show log run command.