Forum Discussion
NimbostratusHelp Needed: Tracking Unreachable Traffic and Public IPs in F5 XC
Hi all,
I’m troubleshooting unreachable traffic in F5 XC and need to identify which Regional Edge (RE) locations cannot reach my backend servers (BE). Here are my questions:
- How can I track failed requests or unreachable servers in F5 XC? Are there specific logs or error codes (e.g., 503, 504) I should look for?
- Where can I find the public IPs of the REs trying to reach my backend servers?
- Any tips on monitoring backend server health and setting up alerts for when traffic can’t reach my backend?
Appreciate any insights or resources!
Thanks!
1 Reply
- tysmith
MVP
I'm assuming you're talking about an HTTP load balancer based on context here (but feel free to clarify otherwise).
To your first question - look for 503 under Home -> Multi-Cloud App Connect -> {namespace} -> Overview -> Performance -> Http. The requests tab will show (sampled) requests through your LB. You can easily filter for 50x and see under `rsp_code_details` there will be an indication if it's timing out at origin (or no viable origin available, if they're failing health checks). The `dst_site` under a given request will also indicate which RE it was attempting to egress from, so that can help identify if you have consistent RE-specific failures (like a local network firewall block).
I also* assume you've seen the docs around XC egress IPs per region... but I'm not sure I've seen anything specific to a given RE. Do you have origin-side monitoring where you see connection issues?
