Filter
Top Products
21-4
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 21 Troubleshooting Broadband Access Center
Logging
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.
To configure the log level on the DPE, using the log level command from the DPE command line. See
the Cisco Broadband Access Center 3.8 DPE CLI Reference, for detailed information.
To configure the log level on the RDU, see The RDU Log Level Tool, page 21-5.
Rotating Log Files
All log files, except perfstat.log, are numbered and rolled over based on a configured maximum file size.
The default maximum file size is 10 MB. (To configure the maximum file size from the API, use the
ServerDefaultsKeys.SERVER_LOG_MAXSIZE property.) After a log file touches the configured limit, the
data is rolled over to another file. This file is renamed in the XXX.N.log format, where:
• XXX—Specifies the name of the log file.
• N—Specifies any value between 1 and 100.
For example, once rdu.log reaches the 10 MB limit, it is renamed as rdu.1.log. With every 10-MB
increase in file size, the latest file is renamed as rdu.2.log, rdu.3.log, and so on. So, the rdu.7.log file will
contain data more recent than rdu.4.log. However, the latest log information is always stored in rdu.log.
In the case of the perfstat.log file, the file is renamed everyday. The file is rolled over in the perfstat.N.log
format, where N is any value between 1 and 100. For example, perfstat.100.log will be the oldest log
while perfstat.1.log will be the most recent renamed perfstat.log file.
Cisco BAC stores up to 10 log files at a given time. For a list of log files in the RDU and DPE servers,
see RDU Logs, page 21-5, and DPE Logs, page 21-8, respectively.
BAC1: 2006 04 21 07:28:00 EDT: BAC- RDU- 6 0569: Created default admin user
BAC1: 2006 04 21 07:28:00 EDT: BAC- RDU- 6 0574: Loaded 6 license keys
BAC1: 2006 04 21 07:28:00 EDT: BAC- RDU- 6 0575: Database initialization completed in 471 msec
BAC1: 2006 04 21 07:28:00 EDT: BAC- RDU- 6 0015: Unable to locate manifest file
BAC1: 2006 04 21 07:28:00 EDT: BAC- RDU- 6 0280: Command error
Domain
Name Data and Time Facility
Sub-
facility
Security
Level Msg ID Message