Table Of Contents
Supported Syslogs and Traps in
Cisco Broadband Access Center 4.0 and 4.0.1
Revised: March 31, 2010, OL-22203-01
This document provides the detailed information about the traps and syslogs supported in
Cisco BAC 4.0 and 4.0.1 releases.
This document includes the following sections:
Cisco BAC provides basic SNMP v2-based monitoring of the RDU and DPE servers. The Cisco BAC SNMP agents support SNMP informs and traps, collectively called notifications.
You can configure an SNMP agent on the DPE by using snmp-server CLI commands. For additional information of the commands, see Cisco Broadband Access Center DPE CLI Reference 4.0
You can configure an SNMP agent on the RDU by using the snmpAgentCfgutil.sh tool. For information about configuring SNMP agent on the RDU using snmpAgentCfgutil.sh tool, see Cisco Broadband Access Center Administrator Guide 4.0
Table 1 lists the Cisco BAC RDU SNMP Traps
Table 1 Cisco BAC RDU SNMP Traps
Syslog Alerts and Messages
Cisco BAC generates alerts through the Solaris syslog service. Syslog is a client-server protocol that manages the logging of information on Solaris. Cisco BAC syslog alerts are not a logging service; they provide a notification if a problem exist, but do not necessarily define the specific cause of the problem. You might find this information in the appropriate Cisco BAC log files. For more information on Cisco BAC logging events see Cisco Broadband Access Center Administrator Guide 4.0
This section describes the alerts generated by the components of Cisco BAC. The alerts include:
When Cisco BAC generates an alert message, the format is:
•XXX—Identifies the facility code, which can include:
–RDU (Regional Distribution Unit)
–DPE (Device Provisioning Engine)
–AGENT (rduSnmpAgent or dpeSnmpAgent)
–NR_EP (Cisco Network Registrar extension points)
–KDC (Key Distribution Center)
•#—Identifies the severity level in use. The three levels of alert are:
–1—Identifies an alert
–2—Identifies and critical alert
–3—Identifies an error
–4—Identifies and informational message
•###—Identifies the numeric error code.
•Message—Provides the alert text or message.
Whenever an RDU syslog alert is sent, additional details (if any) can be found in the log file, BPR_DATA/rdu/logs/rdu.log.
Table 2 identifies the RDU Alerts.
Table 2 Cisco BAC RDU Syslog Alerts
Syslog Name Description
RDU-1-101:RDU ran out of disk space
Indicates that the storage partition of the RDU server ran out of space. After encountering this error, the RDU attempts to restart automatically, but will typically encounter the same error again until more storage space is available. You can remove or compress some of the log files.
RDU-1-103:RDU ran out of memory
Indicates that the RDU ran out of memory. After encountering this error, the RDU server restarts automatically.
RDU-1-111: Evaluation key for technology [technology_name] expired
Indicates that an evaluation key for the technology specified expired. You must contact Cisco sales or TAC for a new license key.
RDU-1-115:You have used  percent of available [technology_name] licenses.
Identifies, in percentage, the quantity of licenses used out of the total number of allowable licenses. Appears when you reach 80 percent of the license capacity.
Generated when the:
•DPE evaluation license expires.
•DPE drops connection with the database.
•DPE is deleted from the database.
BPR-RDU-1-122: DNS took  seconds for lookup of address [ip/hostname]. Check DNS configuration and health of servers
Indicates that BAC performance may be slow due to delayed response from the DNS. The alert is generated whenever IP address lookup takes more than 60 seconds.
RDU-2-119: Directory  that contains the RDU database has a filesystem block size of  bytes that does not match the required size of  bytes. Corruption may occur.
Indicates that the BAC database may not be reliable because the file system that contains the database files is not configured to support an 8-KB or greater block size.
For details on configuring the file-system block size, see the Installation and Setup Guide for the Cisco Broadband Access Center 4.0.
RDU-2-200: Directory  that contains the RDU database transaction logs has a filesystem block size of  bytes that does not match the required size of  bytes. Corruption may occur.
Indicates that the BAC database may not be reliable because the file system that contains the database log files is not 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.
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 Cisco Broadband Access Center DPE CLI Reference 4.0.
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.
Table 3 lists the DPE syslog alerts.
Table 3 Cisco BAC DPE Syslog Alerts
Whenever the process watchdog sends a syslog alert, 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.
Table 4 lists the process watchdog alerts:
Table 4 Process Watchdog Alerts
The [component] variable presented in the process watchdog alerts list shown in Table 4 represents any of these component values:
Network Registrar Extension Points Alerts
Whenever a BAC Network Registrar extension point syslog alert is sent, you can find additional details in the Network Registrar log file.
Table 5 lists the Network Registrar Extension Points alerts:
Table 5 Cisco BAC Network Registrar Extension Points Alerts
This release of the Cisco BAC product is supported by the following documents:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the section Related Documentation.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.