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 Cisco Broadband Access Center (Cisco BAC) Device Provisioning Engine (DPE), and monitor and manage the Cisco BAC 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:
•DPE logs
•Hardware
•Syslog
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.
No keywords or arguments.
No default behavior or values.
bac_dpe# clear logs
Clearing historic log files...
+ Removing 1 DPE log files...
+ No more historic logs.
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.
No keywords or arguments.
Debugging is by default disabled.
bac_dpe# debug on
% OK
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.
debug service tftp 1 ipv4 | ipv6
•1—Identifies the instance of the TFTP service on the DPE.
•ipv4—Specifies debugging of the TFTP service for IPv4.
•ipv6—Specifies debugging of the TFTP service for IPv6.
Debugging of the TFTP service is by default disabled.
This result occurs when you enable debugging of the TFTP service for IPv4.
bac_dpe# debug service tftp 1 ipv4
% OK
This result occurs when you enable debugging of the TFTP service for IPv6.
bac_dpe# debug service tftp 1 ipv6
% OK
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.
no debug service tftp 1 ipv4 | ipv6
•1—Identifies the instance of the TFTP service on the DPE.
•ipv4—Specifies debugging of the TFTP service for IPv4.
•ipv6—Specifies debugging of the TFTP service for IPv6.
Debugging of the TFTP service is by default disabled.
This result occurs when you disable debugging of the TFTP service for IPv4.
bac_dpe# no debug service tftp 1 ipv4
% OK
This result occurs when you disable debugging of the TFTP service for IPv6.
bac_dpe# no debug service tftp 1 ipv6
% OK
Use the no debug all command to disable all the categories of debug logging.
For details about enabling debug logging, see debug on.
No keywords or arguments.
Debug logging is by default disabled.
bac_dpe# no debug all
% OK
Use the log level command to set the level of minimum DPE log messages that are saved, as described in the Cisco Broadband Access Center Administrator Guide, 4.2.
log level number
number—Identifies the logging level, by number, to be saved. Table 6-2 describes the log levels that Cisco BAC 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.
The default log level is 5-notification.
bac_dpe# log level 6
% OK
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]
•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 keyword 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 keyword is optional.
No default behavior or values.
This result occurs when you use the show log command.
bac_dpe# show log
dpe.example.com: 2007 06 04 08:01:42 EDT: %BPR-DPE-5-0236: [Device Provisioning Engine] starting up.
dpe.example.com: 2007 06 04 08:01:42 EDT: %BPR-DPE-6-0822: Server version [BAC 4.2.0 (SOL_BAC4_0_0_00000000_0505)].
dpe.example.com: 2007 06 04 08:01:42 EDT: %BPR-DPE-6-0689: Maximum Java heap size [307 MiB].
dpe.example.com: 2007 06 04 08:01:42 EDT: %BPR-DPE-6-0690: Maximum database cache size [102 MiB].
dpe.example.com: 2007 06 04 08:01:42 EDT: %BPR-DPE-5-1360: Connecting to RDU [dpe.example.com:49187]. Rate [1/d].
dpe.example.com: 2007 06 04 08:05:31 EDT: %BPR-DPE-5-0195: Connected to RDU [dpe.example.com:49187]. Time to connect [3.8 min]. Rate [1/d].
dpe.example.com: 2007 06 04 08:05:31 EDT: %BPR-DPE-5-0982: Configured provisioning interfaces: [localhost[10.10.0.1]].
dpe.example.com: 2007 06 04 08:05:31 EDT: %BPR-DPE-5-1359: Batch [DPE:dpe.example.com/10.86.149.133:bf7190:112f6a01cf7:80000002]. Registering with RDU. Rate [1/d].
dpe.example.com: 2007 06 04 08:05:32 EDT: %BPR-LICENSING-3-0998: Server registration failed. Lack of DPE licenses.
dpe.example.com: 2007 06 04 08:05:33 EDT: %BPR-DPE-5-1374: Opening database [default.db].
dpe.example.com: 2007 06 04 08:05:34 EDT: %BPR-DPE-5-1375: Opened database [default.db]. Time to open [1.2 s].
dpe.example.com: 2007 06 04 08:05:34 EDT: %BPR-TFTP-5-0462: Service is disabled.
dpe.example.com: 2007 06 04 08:05:34 EDT: %BPR-TOD-5-5501: TOD Server disabled.
dpe.example.com: 2007 06 04 08:19:21 EDT: %BPR-LICENSING-5-1002: DPE received a license event from the RDU.
dpe.example.com: 2006 12 21 11:22:20 GMT: %BPR-DPE-5: DPE-0: Device Provisioning Engine starting up
...
Note The output presented in this example is trimmed for demonstration purposes.
This result occurs when you use the show log last command.
bac_dpe# show log last 2
dpe.example.com: 2007 06 04 08:19:23 EDT: %BPR-DPE-5-0147: Batch dpe.example.com: 2007 06 04 08:19:23 EDT: %BPR-DPE-5-1371: Synchronized [0] cached device configurations with RDU. Time to synchronize [52 ms] ([0/s]).
dpe.example.com: 2006 12 21 11:28:17 GMT: %BPR-DPE-5: DPE-0: Device Provisioning Engine starting up
This result occurs when you use the show log run command.
dpe# show log run
Press <enter> to stop.
dpe.example.com: 2006 12 21 11:43:43 GMT: %BPR-DPE-5: DPE-0: Device Provisioning Engine starting up
dpe.example.com: 2006 12 21 11:43:44 GMT: %BPR-DPE-5: Info DPE: Attempt to connect to RDU BPR_host.example.com:49187 failed;
dpe.example.com: 2006 12 21 11:43:44 GMT: %BPR-DPE-5: Info TFTP: Ready to service requests
% Stopped.