MENU
Which two methods should the BIG-IP Administrator troubleshoot a Pool-member that's been marked "DOWN" by its Health Monitor? (Pick the 2 correct responses below)
When a health monitor marks a member 'Down,' the goal is to determine if the issue is at the network level or the application level.
Monitor Logging (Option A): In the Pool Member configuration, an administrator can enable 'Monitor Logging'. This generates a detailed text file in /var/log/monitors/ that shows the exact 'Send' string sent by the BIG-IP and the exact 'Receive' string (or lack thereof) returned by the server.
TCPdump (Option C): This is the most definitive way to see if the monitor traffic is even leaving the BIG-IP and if the server is responding with a TCP RST (reset) or an ICMP unreachable message. A command such as tcpdump -ni <vlan> host <member_ip> and port <member_port> is standard for this task.
Why not others? While the routing table (Option B) is useful for general connectivity, if other members in the same subnet are 'Up,' the routing is likely fine. Statistics (Option D) show that it is down but rarely why it is down at a protocol level.
Currently there are no comments in this discussion, be the first to comment!