Virtual Server Cannot Access External Pool Members

All of the health checks are green for the pool members. I can also cURL to any of the pool members form the F5 TMSH.

Which stats are you looking at?

Also, can you tell us what your NAT settings are for this Virtual Server?

Try setting the VS source address translation to automap and see if it works. If so then there is a routing problem affecting the return traffic.

VS source address translation is set to automap.

I do not have NAT or SNAT configured for this VS since it is for internal use only. I know this is considered a sideband connection, so I'm not sure what is missing.

We use our edge firewall to handle SNAT translation for the other virtual servers and we do have an ACL rule that allows this ip to connect externally.

You should look at both VS stats and Pool stats, but otherwise I think you might need to use tcpdump to figure out what's happening.

When you use curl from the Big-IP command line, are you sure that you are using the same source IP as when using automap on your VS?

When you use curl from the Big-IP command line, are you sure that you are using the same source IP as when using automap on your VS?

This may be the part I am not understanding. We do not have any SNAT translations set up and the source IP for the Google VS is 0.0.0.0/0

You said you were using Automap for your VS's source address translation. Automap will let the Big-IP decide which IP to use for address translation. So if your Big-IP has multiple Self IPs, which is fairly common, it is possible that your curl command from the command line works because because it could use a different source IP than the one selected by the Big-IP's Automap feature on your VS.

I think tcpdump is your best friend in this scenario.

Thanks, I will try the tcpdump