201 · Question #323
Assume the bigd daemon fails on the active system. Which three are possible results? (Choose three.)
The correct answer is A. The active system will restart the bigd daemon and continue in active mode. C. The active system will reboot and the standby system will go into active mode. D. The active system will failover and the standby system will go into active mode. When the bigd daemon fails on an active BIG-IP system, the system can be configured to attempt to restart the daemon, initiate a failover, or even trigger a system reboot, depending on the configured watchdog and failover actions.
Question
Assume the bigd daemon fails on the active system. Which three are possible results? (Choose three.)
Options
- AThe active system will restart the bigd daemon and continue in active mode.
- BThe active system will restart the tmm daemon and continue in active mode.
- CThe active system will reboot and the standby system will go into active mode.
- DThe active system will failover and the standby system will go into active mode.
- EThe active system will continue in active mode but gather member and node state information from
How the community answered
(31 responses)- A81% (25)
- B13% (4)
- E6% (2)
Why each option
When the bigd daemon fails on an active BIG-IP system, the system can be configured to attempt to restart the daemon, initiate a failover, or even trigger a system reboot, depending on the configured watchdog and failover actions.
The BIG-IP system's watchdog process monitors critical daemons like bigd and can be configured to automatically restart a failed daemon, allowing the system to continue in active mode without interruption.
The tmm daemon is the Traffic Management Microkernel, distinct from bigd (the health monitor daemon); a bigd failure typically does not directly cause a tmm restart.
If the bigd daemon failure is deemed critical or persistent, the system's failsafe configuration might trigger a system reboot, which would cause a failover to the standby unit.
A bigd daemon failure can be configured as a failover condition, leading the active system to immediately relinquish its active status and transition to standby mode, allowing the peer system to take over as active.
If bigd fails, the system cannot reliably gather real-time member and node state information, making it unlikely to continue operating normally in active mode for an extended period, especially for health checks.
Concept tested: F5 BIG-IP daemon failure responses
Source: https://techdocs.f5.com/en-us/bigip-15-1-0/big-ip-system-administration/managing-failover.html
Topics
Community Discussion
No community discussion yet for this question.