101 · Question #199
A site has assigned the ICMP monitor to all nodes and a custom monitor, based on the HTTP template, to a pool of web servers. The HTTPbased monitor is working in all cases. The ICMP monitor is failing
The correct answer is D. The pool members whose nodes are failing the ICMPbased monitor will be marked unavailable.. When a node-level monitor fails, all pool members residing on that node are marked unavailable regardless of any passing pool-level monitors.
Question
A site has assigned the ICMP monitor to all nodes and a custom monitor, based on the HTTP template, to a pool of web servers. The HTTPbased monitor is working in all cases. The ICMP monitor is failing for 2 of the pool member 5 nodes. All other settings are default. What is the status of the monitor is working in all cases. The ICMP monitor is failing for 2 of the pool member. 5 nodes. All other settings are default. What is the status of the pool members.
Options
- AAll pool members are up since the HTTPbased monitor is successful.
- BAll pool members are down since the ICMPbased monitor is failing in some cases.
- CThe pool members whose nodes are failing the ICMPbased monitor will be marked disabled.
- DThe pool members whose nodes are failing the ICMPbased monitor will be marked unavailable.
How the community answered
(33 responses)- A21% (7)
- B9% (3)
- C3% (1)
- D67% (22)
Why each option
When a node-level monitor fails, all pool members residing on that node are marked unavailable regardless of any passing pool-level monitors.
A passing pool-level HTTP monitor alone is not sufficient; the node-level ICMP monitor failure makes the node unavailable, which cascades to all pool members on that node.
Only the 2 pool members whose corresponding nodes fail the ICMP monitor are affected; the remaining pool members on passing nodes continue to receive traffic normally.
'Disabled' is an administrative state set intentionally by an operator via the management interface, not a state resulting from a monitor failure.
BIG-IP applies the most restrictive health status across all monitors in the hierarchy - node, pool, and pool member. When the ICMP node monitor fails for 2 nodes, the pool members on those nodes are marked 'unavailable' because the underlying node is considered down, overriding the passing HTTP pool monitor result.
Concept tested: F5 BIG-IP monitor hierarchy and cascading node unavailability
Source: https://techdocs.f5.com/en-us/bigip-15-1-0/big-ip-local-traffic-manager-monitors-reference/monitor-instance-status.html
Topics
Community Discussion
No community discussion yet for this question.