This article has ben archived and is no longer maintained by F5. WorldTech IT will continue to host this source.
This article applies to BIG-IP 9.x through 10.x. For information about other versions, refer to the following article:
The BIG-IP system daemons perform a variety of functions, such as managing load-balanced traffic, configuring and controlling the switch chips, monitoring the health and performance of pool members, and performing high-availability failover actions.
BIG-IP daemons belong to one of two categories: core daemons, which start up when you boot the BIG-IP system and run continually, and secondary daemons, which may not be critical for basic operation. The tasks required to manage these processes are different, depending on whether the daemon is core or optional.
Core BIG-IP daemons
Core BIG-IP daemons are those that are essential to system operation. The following table lists the core BIG-IP daemons, and indicates the impact to BIG-IP system operation if the daemon is not running:
|Daemon||Description||Impact if not running||Relevant log files|
|alertd||The alert process monitors system error messages and triggers proper actions, such as sending snmptrap and displaying messages on the panel.||No Alerts||/var/log/ltm|
|bcm56xxd||The switch process configures and controls the Broadcom 56xx switch chips.||No switch traffic, LEDs not functional, STP and LACP not functional||/var/log/ltm
|bigd||The bigd monitor process provides system health checks.||Monitors not available||/var/log/ltm|
|bigdbd*||The bigdb process loads the mcpd process with the initial values from the BigDB.dat database, and adds any changes to these values to the BigDB.dat database.
*The bigdbd process was removed from the BIG-IP software in version 10.1.0.
|Cannot initialize mcpd, cannot load or save BigDB.dat values||/var/log/ltm|
|cbrd*||The XML content based routing process provides document parsing functionality for the XML profile.
*The cbrd process was introduced in BIG-IP 10.2.0.
|Virtual servers are unable to parse XML documents||/var/log/cbr/cbrd.log
|cand||The cand process manages the CAN buses for multiple clients (over UDP/SLIP/PPP). It manages utility communication between all cards in the VIPRION chassis, fan trays, and the Annunciator panel.||Loss of function and communication between devices in the CAN bus||/var/log/ltm|
|chmand||The chassis manager process is responsible for implementing the following HAL capabilities: platform identification, synchronization with SCCP (on platforms containing SCCP), device discovery, chassis sensor monitoring, and chassis configuration (management & serial interfaces).||Cannot perform platform ID, enumerate interfaces and push/publish platform info to MCPD, nor start SCCP software processes||/var/log/ltm|
|clusterd||The clusterd process manages blade clustering for VIPRION systems.||Blade clustering does not function||/var/log/ltm|
|crond||The cron process executes scheduled commands and scripts.||Cannot execute scheduled commands||/var/log/cron|
|cssd||The config sync status process monitors configuration changes and establishes when the configuration needs to be synchronized between systems.||No ConfigSync status||/var/log/ltm|
|csyncd||For all platforms, the csyncd process populates the software image table. In addition, on VIPRION systems, the csyncd process replicates portions of the filesystem between cluster members.||For all platforms, the software image table does not get updated and you are unable to view or manage the latest software image list using the Configuration utility. In addition, on VIPRION systems, there is no synchronization amongst cluster members.||/var/log/ltm|
|eventd||The event process provides asynchronous event notification, using iControl messaging.||iControl-based subscription messaging fails||/var/log/ltm|
|fpdd||The front panel display process draws screens on the LCD panel and manages LEDs on all platforms.||No front panel access or data||/var/log/ltm|
|httpd||The http process performs HTTP web server functions.||No Configuration utility||/var/log/httpd/httpd_errors|
|lacpd||The link aggregation control process creates link aggregation groups (trunks) based on user configuration. It implements IEEE 802.3ad – Link Aggregation Control Protocol (LACP). It also implements the high-availability feature Switchboard Failsafe.||No link aggregation functionality||/var/log/ltm|
|lopd||The lopd process is the lights-out processor (LOP) daemon for certain BIG-IP platforms.||The LOP subsystem does not function.||/var/log/ltm|
|mcpd||The master control program process is the messenger process that allows userland processes to communicate with TMM and vice versa.||No traffic management functionality; the system status cannot be retrieved or updated, and the system cannot be re-configured; other processes will not be functional||/var/log/ltm|
|pvad||The packet velocity accelerator process runs on systems equipped with the PVA ASIC chip.||The PVA runs in wire mode||/var/log/ltm|
|rmonsnmpd||The RMON snmp process provides remote monitoring, alarm, and event functionality.||Partial loss of SNMP||/var/log/daemon.log|
|snmpd||The SNMP process is the master SNMP agent. Without this process, no data will be exposed by SNMP, including data from the SNMP subagents. The process also exposes common SNMP data.||No SNMP functionality||/var/log/daemon.log|
|sod||The failover process causes the unit to become active or standby, and provides failover and restart capability through a high availability table.||No failover capability||/var/log/ltm|
|statsd||The stats process collects statistics from the system and records them in the rrd files.||No rrd data recorded for system graphs||/var/log/ltm|
|stpd||The STP process implements the IEEE Spanning Tree Protocol (STP) for preventing bridge loops. The protocols include the original STP, Rapid Spanning Tree Protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP).||No bridge loop detection||/var/log/ltm|
|subsnmpd*||The subsnmpd process is the traffic management SNMP agent.
*The subsnmpd process was introduced in BIG-IP 9.2.0.
|Partial loss of SNMP functionality||/var/log/daemon.log|
|syscalld||The syscall process manages system call functions.||Lose system call functions such as bp save from the Configuration utility||/var/log/ltm|
|tamd||The traffic authorization process authorizes traffic.||No remote authentication / authorization||/var/log/ltm|
|tmm||The traffic management microkernel is the process running on the BIG-IP host O/S that performs all of the traffic management for the system.||No traffic management for the system||/var/log/tmm
|tmrouted||The routing table management process updates the TMM routing table based on the kernel routing table.||TMM will not be able to learn or advertise routes||/var/log/ltm|
|tmsnmpd*||The snmp process for traffic management functions is an SNMP subagent that exposes common data of the traffic management system.
*The tmsnmpd process was removed from the BIG-IP software in version 9.1.3.
|Partial loss of SNMP||var/log/daemon.log|
|tomcat4||Tomcat provides web server functions for the BIG-IP web utility. Tomcat is an open-source implementation of Java Servlet and JavaServer Pages technologies developed under the Jakarta project at the Apache Software Foundation.||The Configuration utility does not function||/var/log/tomcat4/catalina.out|
|syslog-ng||The syslog-ng process performs system logging based on the syslog-ng utility.||Unable to generate system logs||/var/log/messages|
|zebosd||The ZebOS process updates the kernel routing table with routes learned by the advanced routing module when the feature is licensed. In BIG-IP 9.4.4 and later, this is done by tmrouted.||The advanced routing modules will not operate properly (versions prior to 9.4.4)||/var/log/ltm|
Starting and stopping core daemons
You can use the command line to manage most core daemons on the BIG-IP system. To stop, start, restart, or view the status of a core daemon, use the bigstart command.
For example, to view the status of the bcm56xxd process, type the following command:
bigstart status bcm56xxd
For information about using the bigstart utility, see the bigstart man page.
Secondary BIG-IP daemons
Secondary BIG-IP daemons are those that may not be essential to system operation. The following table lists secondary BIG-IP daemons:
|Secondary BIG-IP daemons|
|big3d||The big3d process is the GTM metrics collection process.|
|gtmd||The GTM process reads wide IP configuration and listens and responds to DNS queries containing wide IP names. This process is only active on systems running the BIG-IP GTM module.|
|named||The named process is the DNS server process.|
|ntpd||The ntp process sets and maintains the system time.|
|postfix||The postfix process sends and receives email.|
|radvd||The radv process is the router advertisement process for IPv6. It listens to router solicitations, and answers with router advertisements.|
|sshd||The ssh process provides remote access to the BIG-IP system command line interface.|
|tmzd||The tmz process provides software compression when compression is licensed.|
|zrd||The zrd process is the ZoneRunner process. This process is only active on systems running the BIG-IP GTM module.|
Starting and stopping secondary daemons
Use the Configuration utility to manage secondary BIG-IP daemons. The Configuration utility lists the name of each daemon and its current status.
To stop, start, restart, or view the status of a secondary daemon, perform the following procedure:
- Log in to the Configuration utility.
- Navigate to System > Services.
- In the process column, locate the name of the service you want to start, stop, or restart.
- Select the Service Select box.
- Click Start, Stop, or Restart.