F5 BIG-IP LTM Troubleshooting – A Practical Guide
Local Traffic Manager (LTM)
is widely used to manage application traffic, improve performance, and ensure high availability.
However, when issues arise, rapid and methodical troubleshooting is essential to minimize downtime.
1. Understanding the LTM Traffic Flow
Before troubleshooting, it is important to understand the standard traffic flow:
- Client → Virtual Server
- Virtual Server → Pool
- Pool → Pool Members (Nodes)
- Optional: iRules, Profiles, Persistence
Tip: Always verify where the traffic is failing in this chain before making configuration changes.
2. Virtual Server Troubleshooting
Common Symptoms
- Application not reachable
- Connection timeouts
- TCP resets
Checks to Perform
tmsh show ltm virtual <virtual_name>
- Ensure the virtual server is Enabled
- Verify correct destination IP and port
- Confirm the correct pool is attached
3. Pool and Pool Member Issues
Pool Status Validation
tmsh show ltm pool <pool_name>
Common Problems
- Health monitors marking members down
- Incorrect service port
- Firewall blocking server responses
Best Practice: Always test backend servers directly using curl or telnet from the BIG-IP shell.
4. Health Monitor Troubleshooting
Why Monitors Fail
- Incorrect send/receive string
- Application returning unexpected HTTP codes
- SSL handshake failures
Useful Commands
tmsh show ltm monitor
tail -f /var/log/ltm
5. iRule Troubleshooting
Misconfigured iRules are a frequent cause of traffic disruption.
Common iRule Issues
- Incorrect event handling
- Syntax errors
- Unintended traffic drops
Debugging Example
log local0. "Client IP: [IP::client_addr]"
Logs can be viewed using:
tail -f /var/log/ltm
6. Persistence & Profile Issues
Symptoms
- Users randomly logged out
- Session stickiness failures
Things to Verify
- Correct persistence profile applied
- Cookie or source IP persistence matches application logic
- No conflicting persistence profiles
7. SSL & Certificate Troubleshooting
Common SSL Errors
- Handshake failures
- Certificate expired or mismatched
- Unsupported cipher suites
Verification Commands
tmsh list sys crypto cert
tmsh list ltm profile client-ssl
8. Performance & Latency Issues
Possible Causes
- High CPU or memory utilization
- Connection limits reached
- Slow backend servers
Performance Checks
tmsh show sys performance
tmsh show sys cpu
tmsh show sys memory
9. Packet Capture & Advanced Debugging
When configuration checks are insufficient, packet capture is invaluable.
tcpdump -i 0.0:nnn -s0 -w /var/tmp/ltm_capture.pcap
- Analyze traffic using Wireshark
- Check SYN/SYN-ACK flows
- Identify resets or retransmissions
10. Final Troubleshooting Checklist
- Virtual server status
- Pool member health
- Monitor behavior
- iRules logic
- Persistence settings
- SSL profiles
- System performance
Conclusion: A structured, layer-by-layer approach is the fastest way to isolate and resolve F5 BIG-IP LTM issues.