Cisco Cisco Broadband Access Center for Cable 4.0 Maintenance Manual
6
Supported Syslogs and Traps in Cisco Broadband Access Center 4.0 and 4.0.1
OL-22203-01
Syslog Alerts and Messages
DPE Alerts
Whenever a DPE syslog alert is sent, you can find additional details in the DPE logs.
You can use the
show log
command to access the DPE logs. For additional information, see
Some DPE errors are also propagated to the RDU server log files. You can find these in the
BPR_DATA/rdu/logs/rdu.log file.
BPR_DATA/rdu/logs/rdu.log file.
lists the DPE syslog alerts.
Table 3
Cisco BAC DPE Syslog Alerts
Syslog Name
Description
DPE-1-102: DPE ran out of disk
space
space
The storage partition that the DPE server uses ran out of space. You have three
options:
options:
a.
Clear out any excess support bundles from the disk. You can do this by
moving those support bundles to another machine and then running the
moving those support bundles to another machine and then running the
clear
bundles
command from the DPE CLI.
b.
Run the
clear logs
command from the DPE CLI to clear more disk space.
c.
As a last resort, run the
clear cache
command from the DPE CLI to remove
any cache files and force the DPE to resynchronize with the RDU server.
DPE-1-104: DPE ran out of memory The DPE process ran out of memory. After encountering this error condition, the DPE
restarts automatically.
Determine how many device configurations are on the DPE; the larger the number of
device configurations, the more memory is used. To reduce device configurations,
limit the number of devices in the provisioning groups that the DPE serves.
device configurations, the more memory is used. To reduce device configurations,
limit the number of devices in the provisioning groups that the DPE serves.
DPE-1-109: Failed to connect to
RDU
RDU
The RDU cannot be contacted. You must:
a.
Verify if the DPE network is configured and connected correctly.
b.
Check if the DPE is configured to connect to the proper RDU, and that the
connecting port is configured properly by using the
connecting port is configured properly by using the
dpe rdu-server
command.
c.
Check if 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.
the correct port. The DPE attempts to reconnect to the RDU process every
few seconds until a connection is established.
DPE-1-117: DPE license nodes have
been exceeded or there is no valid
DPE license
been exceeded or there is no valid
DPE license
Indicates that the DPE license nodes have been exceeded or there is no valid DPE
license.
license.
DPE-1-116: DPE evaluation license
has expired. Dropping DPE
connections and deleting DPEs from
database
has expired. Dropping DPE
connections and deleting DPEs from
database
Indicates that an evaluation license key for the DPE expired. You must contact Cisco
sales or TAC for a new license key.
sales or TAC for a new license key.
DPE-2-118: Directory [] that
contains the DPE’s cache has a
filesystem block size of [] bytes that
does not match the required size of []
bytes. Corruption may occur.
contains the DPE’s cache has a
filesystem block size of [] bytes that
does not match the required size of []
bytes. Corruption may occur.
Indicates that the DPE cache may not be reliable because the file system is not
configured to support an 8-KB or greater block size.
configured to support an 8-KB or greater block size.
For details on configuring the file system block size, refer to the
Installation and
Setup Guide for the Cisco Broadband Access Center 4.0
.