This appendix describes the Broadband Provisioning Registrar (BPR) log files that you can use to identify the status of your BPR implementation to troubleshoot problems.
Log Directories
BPR creates log directories based on which server is running; either the DPE or RDU server.
The RDU server uses a log file called rdu.log. This log file is located in BPR_HOME/rdu directory.
The DPE server uses a log file called the dpe.log. This log file is located in the BPR_HOME/dpe directory.
Log Structure
The log file structure, is describe here and illustrated in Example A-1. The log file includes this information:
Domain Name—This is the name of the computer generating the log files.
Date and Time—This is the date on which a message is logged. This information also identifies the applicable time zone.
Facility—This identifies the system which, in this case is the BPR.
SubFacility—This identifies the BPR subsystem or component.
Severity Number—The logging system defines seven levels of severity (log levels) that are used to identify the urgency with which you might want to address log issues. The process of configuring log levels is described in the "Configuring Log Levels" section:
0—Emergency; System unstable.
1—Alert; Immediate action is needed.
2—Critical; A critical condition exists.
3—Error; Error conditions exist.
4—Warning; Warning condition exists.
5—Notification; A normal, but significant, condition exists.
6—Information; Informational messages only.
Note Another level known as DEBUG is used exclusively by Cisco Systems Inc. for debugging
purposes. Do not use this level except at the direction of the Cisco Technical Assistance
Center.
Message ID—This is a unique identifier for the message text.
Message—This is the actual log message.
Example A-1
Domain Name
Data and Time
Facility
Sub- facility
Security Level
Message ID
Message
BPR_1:
2001 11 21 09:06:11 EST:
BPR-
RDU-
236:
BPR Regional Distribution Unit starting up
BPR_1:
2001 11 21 09:06:15 EST:
BPR-
RDU-
5
0566:
Initialized API defaults
BPR_1:
2001 11 21 09:06:15 EST:
BPR-
RDU-
5
0567:
Initialized CNR defaults
BPR_1:
2001 11 21 09:06:15 EST:
BPR-
RDU-
5
0568:
Initialized server defaults
BPR_1:
2001 11 21 09:06:18 EST:
BPR-
RDU-
5
0570:
Initialized DOCSIS defaults
BPR_1:
2001 11 21 09:06:18 EST:
BPR-
RDU-
5
0571:
Initialized computer defaults
BPR_1:
2001 11 21 09:06:19 EST:
BPR-
RDU-
5
0573:
Initialized DVB defaults
BPR_1:
2001 11 21 09:06:19 EST:
BPR-
RDU-
5
0572:
Initialized DSTB defaults
BPR_1:
2001 11 21 09:06:19 EST:
BPR-
RDU-
5
0569:
Created default admin user
BPR_1:
2001 11 21 09:06:19 EST:
BPR-
RDU-
5
0574:
Loaded 6 license keys
BPR_1:
2001 11 21 09:06:20 EST:
BPR-
RDU-
5
0575:
Database initialization completed in 1211 msec
BPR_1:
2001 11 21 09:06:25 EST:
BPR-
RDU-
3
0015:
Unable to locate manifest file
BPR_1:
2001 11 21 09:06:28 EST:
BPR-
RDU-
3
0280:
Command error
Sample Log File
Configuring Log Levels
You can configure logging levels for both the RDU and the DPE to suit your specific requirements. For example, the logging level for the RDU could be set to Warning and the level for the DPE could be set to Alert.
Log messages are written based on certain events taking place. Whenever an event takes place, the appropriate log message and level are assigned and, if that level is less than or equal to the configured level the message is written to the log. The message is not written to the log if the level is higher than the configured value.
For example, assume that the log level is set to 4-Warning. All events generating messages with a log level of 4 or less are written into the log file. If the log level is set to 6-Information, the log file will receive all messages. Consequently, configuring a higher log level results in a larger log file size.
