Filter
Top Products
21-8
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 21 Troubleshooting Broadband Access Center
Logging
DPE Logs
The DPE maintains its logs at the BPR_DATA/dpe/logs directory.
• dpe.log—Records all events having the configured default level. In situations where the DPE
undergoes catastrophic failure, such as engaging in a series of system crashes, the catastrophic errors
are also logged into the rdu.log file.
• perfstats.log—Records device performance statistics to help troubleshoot issues related to system
performance. For more information, see Monitoring Cisco Broadband Access Center, page 11-1.
Viewing the dpe.log File
You can use any text viewer to view the dpe.log file. In addition you can use the show log command,
from the DPE CLI, to view the log file. See the Cisco Broadband Access Center 3.8 DPE CLI Reference,
for additional information.
You can also view the DPE log file using the Cisco BAC administrator user interface. To do this:
Step 1 Choose Servers > DPEs.
Step 2 Click the link corresponding to the DPE whose log file you want to view.
The View Device Provisioning Engines Details page appears.
Step 3 To view the contents of the dpe.log file, click the View Details icon against DPE Log File in the Log
Files area.
Access Registrar Logs
Cisco BAC generates trace messages from Cisco Access Registrar RADIUS server extensions. The
RADIUS server trace resides in the car-install-path/name_radius_1_trace directory; car-install-path
is a variable and is specific to the value that you enter. The default location for the RADIUS server log
file is /opt/CSCOar/logs/name_radius_1_trace.
The trace messages emitted using the RADIUS server extensions are based on the extension trace level
setting. You can set values (described in Table below) at the trace level; the number you set makes that
number the current setting of the extension-trace-level attribute for all extensions.
Use the aregcmd command trace to set the trace level in the specified server to a new value. The trace
level governs how much information is displayed about the contents of a packet. When the trace level is
zero, no tracing is performed. The higher the trace level, the more information displayed. The highest
trace level currently used by the CAR server is trace level 5.
Note Although the highest trace level supported by the CAR server is trace level 5, an extension point script
might use a higher level. There is no harm in setting the trace to a level higher than 5.
The trace levels are inclusive, meaning that if you set trace to level 3, you will also get the information
reported for trace levels 1 and 2. If you set trace level 4, you also get information reported for trace levels
1, 2, and 3. When you do not specify a server, CAR sets the trace level for all of the servers in the current
cluster. When you do not specify a value for the trace level, CAR displays the current value of the trace
level. The default is 0.