下面是BIG-IP系统中各个守护进程的解释,详见:http://support.f5.com/kb/en-us/solutions/public/8000/000/sol8035.html?sr=12130346

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 services 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 are not critical for basic operation. The tasks required to manage these daemons is different depending on whether the daemon is a core or an optional daemon.
 
Core BIG-IP daemons
 
Core BIG-IP daemons are those that are essential to system operation. The following table lists the core BIG-IP services, and indicates the impact to BIG-IP system operation if the service is not running:
 
Daemon
Description
Impact if not running
Logs to
bigd
The bigd monitor daemon provides system health checks.
健康检查由bigd管控,可以通过top命令查看其CPU消耗。
Monitors not available
/var/log/ltm
bigdbd
The bigdb daemon loads the mcpd daemon with the initial values from the BigDB.dat database, and adds any changes to these values to the BigDB.dat database.
Cannot initalize mcpd, cannot load or save BigDB.dat values
/var/log/ltm
chmand
The chassis manager deamon 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 daemons
/var/log/ltm
cssd
The config sync status daemon monitors configuration changes and establishes when the configuration needs to be synchronized between systems.
No configsysnc status
/var/log/ltm
fpdd
The front panel display daemon draws screens on the LCD panel and manages LEDs on all platforms.
No front panel access or data
/var/log/ltm
httpd
The http daemon performs HTTP web server functions.
No Configuration utility
/var/log/httpd/httpd_errors
lacpd
The link aggregation control daemon 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
mcpd
The master control program daemon is the messenger daemon 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 daemons will not be functional
/var/log/ltm
pvad
The packet velocity accelerator daemon runs on systems equipped with the PVA ASIC chip.
The PVA runs in wire mode,即所有流量都由cpu处理。
/var/log/ltm
sod
The failover daemon 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 daemon collects statistics from the system and records them in the rrd files.
No rrd data recorded for system graphs
/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
/var/log/ltm
tmrouted
The routing table management daemon 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 daemon for traffic management functions is an snmp subagent that exposes common data of the traffic management system.
Partial loss of snmp
/var/log/daemon.log
tomcat4
Tomcat provides web server functions for the BIG-IP web utiltiy. 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
 
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 service, 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 are not essential to system operation. The following table lists secondary BIG-IP services:
daemon
Description
big3d
The big3d daemon is the GTM / 3-DNS metrics collection daemon.
gtmd *
The GTM daemon reads wide IP configuration and listens and responds to DNS queries containing wide IP names.
named
The named daemon is the DNS server daemon.
ntpd
The ntp daemon sets and maintains the system time.
postfix
The postfix process sends and receives email.
radvd
The radv process is the router advertisement daemon for IPv6. It listens to router solicitations, and answers with router advertisements.
sshd
The ssh daemon provides remote access to the BIG-IP system command line interface.
tmzd
The tmz daemon provides software compression when compression is licensed.
zrd *
The zrd daemon is the ZoneRunner daemon.
*These daemons are 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 service 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.
Click System.
Click Services.
In the Service column, locate the name of the daemon you want to start, stop, or restart.
Select the Service Select box.
Click the Start, Stop, or Restart button.