Cisco Cisco Broadband Access Center for Cable 4.1

Whenever a syslog alert is sent by the watchdog agent process, you can find error details (if any) in the 
<BPR_DATA>/agent/logs/ agent_console.log file and the log files corresponding to the specific 
component mentioned in the alert (if any). For example, if you receive an alert similar to The [rdu] 
unexpectedly terminated, you would check the RDU server log file (<BPR_DATA>/rdu/logs/rdu.log) for 
additional information. 

 identifies the agent alerts.

DPE-1-104: DPE ran out of memory

This alarm indicates that the DPE process has run 
out of memory. 

Determine how many device configurations are on 
the DPE; the more device configurations that exist, 
the more memory is used. The way to reduce 
device configurations is to limit the number of 
provisioning groups, either primary or secondary, 
that the DPE serves.

DPE-1-109: Failed to connect to RDU

This alert indicates that the RDU cannot be 
contacted. You must:

Verify that the DPE network is configured and 
connected correctly.

Check that the DPE is configured to connect to 
the proper RDU, and that the connecting port 
is configured properly, using the dpe 
rdu-server command. 

Check that the RDU process is running on the 
correct server and listening on the correct port. 
The DPE attempts to reconnect to the RDU 
process every few seconds until a connection 
is established.

AGENT-3-9001: Failed to start the 
[<component>] 

This alert indicates that the process has failed to 
start the specified component.

AGENT-3-9002: The [<component>] 
unexpectedly terminated

This alert indicates that the specified component, 
monitored by the agent process, has unexpectedly 
failed.

AGENT-3-9003: Failed to stop the 
[<component>]

This alert indicates that a component did not stop 
when the agent attempted to stop it gracefully.