When gathering data from relevant BIG-IP tools to understand where a failure occurred, which tool can capture SSL handshake information for troubleshooting SSL-related issues?

Question

Options

• Assldump
• Btcpdump
• Csession variables
• DAPM log

• A
  88% (30)
• B
  3% (1)
• C
  3% (1)
• D
  6% (2)

Explanation

ssldump is the correct tool because it is specifically designed to decode and display SSL/TLS handshake details - including cipher negotiation, certificate exchange, and alert messages - making it ideal for diagnosing SSL-related failures on BIG-IP.

tcpdump (B) captures raw network packets at the TCP/IP level but cannot decode the SSL/TLS layer; you'd see encrypted bytes with no handshake visibility unless combined with ssldump. Session variables (C) are APM-specific runtime variables that store user/session state during policy execution - they reflect what happened after a session was established, not why SSL failed. APM log (D) records access policy events and authentication outcomes, which is useful post-handshake but won't show the low-level SSL negotiation details needed to pinpoint handshake failures.

Memory tip: Think "SSLdump = dump the SSL handshake to screen." If the question mentions SSL negotiation, certificates, or cipher suites, ssldump is your answer - it's the only tool on the list that speaks TLS natively.

No community discussion yet for this question.