101 · Question #13
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.. The bigd daemon on F5 BIG-IP manages system health monitoring, and its failure can result in multiple outcomes including daemon restart, system reboot with standby takeover, or a direct failover event.
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
How the community answered
(44 responses)- A43% (19)
- B39% (17)
- E18% (8)
Why each option
The bigd daemon on F5 BIG-IP manages system health monitoring, and its failure can result in multiple outcomes including daemon restart, system reboot with standby takeover, or a direct failover event.
BIG-IP can detect the bigd failure and automatically attempt to restart the daemon, allowing the system to remain in active mode if the restart is successful.
bigd failure does not cause the TMM (Traffic Management Microkernel) daemon to restart - these are separate independent processes with their own restart behaviors.
If the bigd failure is severe enough, the BIG-IP watchdog mechanism may force a full system reboot, causing the standby unit to detect the failure and promote itself to active mode.
A bigd failure can also trigger a graceful failover where the active system signals the standby to take over as active without requiring a full reboot of the failed system.
Gathering member and node state information is a core responsibility of bigd itself, so a bigd failure would halt that monitoring function rather than allow it to continue.
Concept tested: F5 BIG-IP bigd daemon failure and HA failover outcomes
Source: https://support.f5.com/csp/article/K3503
Topics
Community Discussion
No community discussion yet for this question.