F5相关进程对应日志目录.docx

SOL8035: Overview of BIG-IP daemons General SolutionOriginal Publication Date: 10/29/2007Updated Date: 06/02/2010The 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 daemonsCore 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:DaemonDescriptionImpact if not runningLogs toalertdThe alert daemon monitors system error messages and triggers proper actions, such as sending snmptrap and displaying message on panel.No Alerts/var/log/ltmbcm56xxdThe switch daemon configures and controls the Broadcom 56xx switch chips.No switch traffic, LEDs not functional, STP and LACP not functional/var/log/ltm/var/log/bcm56xxdbigdThe bigd monitor daemon provides system health checks.Monitors not available/var/log/ltm bigdbdThe 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/ltmchmandThe 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/ltmclusterdThe clusterd daemon manages blade clustering for VIPRION systems.Blade clustering does not function/var/log/tmmcrondThe cron daemon executes scheduled commands and scripts.Cannot execute scheduled commands/var/log/croncssdThe config sync status daemon monitors configuration changes and establishes when the configuration needs to be synchronized between systems.No configsysnc status/var/log/ltmcsyncdThe csyncd daemon replicates portions of the filesystem between cluster members on VIPRION systems.No synchronization amongst cluster members/var/log/ltmeventdThe event daemon provides asynchronous event notification, using iControl messaging.iControl-based subscription messaging fails/var/log/ltmfpddThe front panel display daemon draws screens on the LCD panel and manages LEDs on all platforms.No front panel access or data/var/log/ltmhttpdThe http daemon performs HTTP web server functions.No Configuration utility/var/log/httpd/httpd_errorslacpdThe 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/ltmmcpdThe 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/ltmpvadThe packet velocity accelerator daemon runs on systems equipped with the PVA ASIC chip.The PVA runs in wire mode/var/log/ltmrmonsnmpdThe RMON SNMP daemon monitors interface statistics.Partial loss of snmp/var/log/daemon.logsnmpdThe SNMP daemon is the parent SNMP agent. Without this daemon, 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.logsodThe 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/ltmstatsdThe stats daemon collects statistics from the system and records them in the rrd files.No rrd data recorded for system graphs/var/log/ltmstpdThe STP daemon 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 syscalldThe syscall daemon manages system call functions.Lose system call functions such as bp save from GUI/var/log/ltmtamdThe traffic authorization daemon authorizes traffic.No remote authentication / authorization/var/log/ltmtmmThe 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/ltmtmroutedThe 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/ltmtmsnmpdThe 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.logtomcat4Tomcat 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.outsyslog-ngThe syslog-ng process performs system logging based on the syslog-ng utility.Unable to generate system logs/var/log/messageszebosdThe zebos daemon updates the kernel routing table with routes learned by the advanced routing module when the feature is licensed. In 9.4.4 and later this is done by tmroutedThe advanced routing modules will not operate properly (versions prior to 9.4.4)./var/log/ltmStarting and stopping core daemonsYou 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 bcm56xxdFor information about using the bigstart utility, see the bigstart man page.Secondary BIG-IP daemonsSecondary BIG-IP daemons are those that are not essential to system operation. The following table lists secondary BIG-IP services:Secondary daemonDescriptionbig3dThe 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 dThe named daemon is the DNS server daemon.ntpdThe ntp daemon sets and maintains the system time.postfixThe postfix process sends and receives email.radvdThe radv process is the router advertisement daemon for IPv6. It listens to router solicitations, and answers with router advertisements.sshdThe