Forum Discussion

Altostratus

Oct 27, 2022

no outbound traffic pool

Hello, Kindly help me solve this issue please. My pool member is not getting any outbound traffic. Inbound traffic is ok. --Below the vs config ltm virtual VS_force { destination xxxxxxxx:443 ...

application delivery

sbroulaye

Altostratus

Oct 28, 2022

Thanks Kevin for this insightful explanation.

Please find in attachment the logs I collected from the tcpdump input you asked to do.

I would like to know why the pool member (172.17.31.254) is communicating both with the self ip (172.17.31.18) and the floating ip (172.17.31.16). Because our BIG-IPs are in HA active/active mode, so the traffic to the pool member is going through the floating ip.

Thanks in advance.

Kevin_Stewart

Employee

Oct 31, 2022

it's hard to say for sure, but since the .18 (presumably) monitor traffic is doing well, it would seem as if the server never completes the TCP 3WH for the .16 request. I also see two different ports (32255 and 32270). Are you certain the server can respond on that port, or isn't in any way configured to block .16? If this is a web app, can you curl to it from the BIG-IP?

curl -vk http://172.17.31.254:32255

sbroulaye
Altostratus
Oct 31, 2022
32270 is another service deployed on the same pool member; it has the same issue as 32255.
Yes the service works perfectly if we bypass the BIG-IP by directly accessing the pool member ip address.
It's a web app, kindly find in attachment the snapshot of the curl fom big-ip to pool member.
- Kevin_Stewart
  Employee
  Oct 31, 2022
  When you access directly are you using http or https?
  
  Are you using a server SSL profile on the BIG-IP?
  - sbroulaye
    Altostratus
    Oct 31, 2022
    We're accessing directly using http://172.17.31.254:32255/#/sessions
    No server SSL profile configured in this specific VS, only client SSL profile.