Filter
Top Products
9-3
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 9 Managing Cisco Broadband Access Center
Cisco BAC Process Watchdog
When the operating system (Solaris and Linux) is rebooted, the Cisco BAC process watchdog is first
stopped, allowing Cisco BAC servers to shut down properly. To shut down or reboot the operating system
gracefully, use the init 6 command.
The reboot command does not execute application shut down hooks and kills Cisco BAC processes
rather than shutting them down. While this action is not harmful to Cisco BAC, it may delay server
start-up and skew certain statistics and performance counters.
The events that trigger an action in the Cisco BAC watchdog daemon, including process crashes and
restarts, are logged in a log file, <BPR_HOME>/agent/logs/agent.log. The watchdog daemon also logs
important events to syslog under standard
local6 facility.
Enabling SNMP Trap for Cisco BAC Process Watchdog
The Cisco BAC process watchdog can be configured to send SNMP traps to the trap receiver for all the
critical conditions of Cisco BAC components. The critical conditions include:
• BAC process fails to start, restart, or stop
• BAC process stops unexpectedly
• Cisco BAC process watchdog fails to start or stop
The Cisco BAC process watchdog runs on the following BAC components:
• RDU
• DPE
• CLI
• Tomcat
• SNMPAgent
• STUNServer
bprAgent status process-name Gets the status of one particular monitored process. The value
process-name identifies that process.
The process-name mentioned in Table 9-1 can be:
• rdu—Specifies the RDU server.
• dpe—Specifies the DPE server.
• stun—Specifies the STUN server.
• snmpAgent—Specifies the SNMP agent.
• tomcat—Specifies the administrator user interface.
• cli—Specifies the DPE command line interface.
Table 9-1 Cisco BAC Watchdog Agent CLI Commands (continued)
Command Description