-- Exhibit
-- Exhibit --
Refer to the exhibit.
A server administrator notices that one server is intermittently NOT being sent any HTTP requests. The server logs display no issues. The LTM Specialist notices log entries stating the node (172.16.20.1) status cycling between down and up. The pool associated with the virtual server (10.10.1.100) has a custom HTTP monitor applied.
Which tcpdump filter will help trace the monitor?
To trace the monitor traffic effectively, it is imperative to capture traffic that is specifically for health monitoring. The monitor would be sending HTTP requests to check the health of the node, and such traffic would be directed internally, to the specific node. Given that the node in question has an IP of 172.16.20.1 and is serving on port 80, the correct tcpdump filter would be one that monitors this internal HTTP traffic. Therefore, the command 'tcpdump -i internal port 80 and host 172.16.1.31' is well-suited to trace this monitor traffic as it aims to capture HTTP requests sent by the self IP (172.16.1.31) of the load balancer internally within the network.
Should be C, isn't it?
No, monitor Traffic is sent by Non-Floating Self-IP. Answer A is correct
A - Correct Health monitor traffic does not use Floating Self-IP.
This is a bit of a dumb question as we don’t know which device is active. I tested in a lab to make sure though and monitor traffic is definitely not send from the floating IP - answer is correct.
why is port 80?