Filter
Top Products
8-6
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 8 CPE History and Troubleshooting
Device Faults
Step 3 Click the radio buttons corresponding to the operation you want to enable or disable:
• To enable recording the history of immediate operations, click the Enabled radio button
corresponding to Immediate Operation History.
• To enable recording the history of on-connect operations, click the Enabled radio button
corresponding to On-Connect Operation History.
• To enable recording the history of configuration generation, click the Enabled radio button
corresponding to Instruction Generation History.
To disable these operations, click the corresponding Disabled radio button.
Step 4 Click Submit.
Device Faults
In large installations, devices with recurring faults can cause bottlenecks and affect performance.
Recurring faults can result from a device malfunction or misconfiguration of Cisco BAC. You can use
Cisco BAC to detect recurring faults occurring at the RDU and the DPE servers through the Recurring
Device Faults feature.
You can also configure Cisco BAC to ignore and not store the CWMP faults reported by the CPE. The
fault values must be specified in the dpe.properties file with comma separation, for example,
/dpe/cwmp/fault/ignore=9003, 9801.
The DPE will filter the CPE faults with fault codes 9003 and 9801 while reporting the faults. This feature
is helpful when faults from Customer Premises Equipment (CPE) to Cisco BAC are expected for certain
standard operations such as a reboot or recurrent faults.
A recurrent fault is one that occurs many times over a short period of time, or one with high chances of
occurring repeatedly. For instance, a fault may occur when an attempt is made to configure a device and
if the device is missing a parameter.
Such a fault qualifies as recurring even if it happens only once, because this operation is executed on
every device contact. However, if a one-time device operation is initiated from the API and results in a
fault, this fault is returned to the API client in the operation response and is not considered to be
recurring.
Also, consider the following scenarios:
• A configuration template at the RDU may refer to a property that was deleted from the system. Every
time the RDU tries to generate instructions for devices by using this template, an error occurs. This
error qualifies the device as the one causing a recurring fault and is reported to the user.
• A device sends an invalid or incomplete Inform message because of a bug in the device firmware.
The same Inform is generated on every device contact. This problem also qualifies as a recurring
fault.
This feature provides details about the last fault for given devices as well as aggregated fault statistics
for the system as a whole, the RDU server, and each DPE server.