For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

littlebunny's avatar
littlebunny
Icon for Nimbostratus rankNimbostratus
Mar 19, 2019

Virtual Server not working

Hello

 

I've set up a new virtual server and pointed it to an existing HTTPS virtual pool. However, when I browse to it I get 'The site can't be reached". We have another virtual server pointing to the same virtual pool and it works fine, the only difference is that the working one has a private IP and the non-working one has a public IP. For the vlan setup, should I only be enabling the vlan that the virtual server IP resides on? And should I enable SNAT or Automap? Any other ideas on what to check? If I look in the virtual server statistics I see connections being successfully made, it just doesn't seem to be reaching the nodes.

 

Thanks LB

 

application delivery
BIG-IP
BIG-IP Access Policy Manager (APM)
big-ip ltm

2 Replies

  • Dylan_375544's avatar
    Dylan_375544
    Icon for Cirrocumulus rankCirrocumulus
    Mar 19, 2019

    You want to enable SNAT Automap if the default gateway of your back end server is NOT the BIG-IP, that will prevent asynchronous routing. The vlan should be enabled that the back end server is on.

     

    Hope that helps! If it does please up-vote and select this answer, it would be greatly appreciated!

     

    -Dylan

     

  • Rico's avatar
    Rico
    Icon for Cirrus rankCirrus
    Mar 19, 2019

    You may want to check your vlan configuration. Can you post the output of a tcpdump to help diagnose the issues? Perhaps the device is having a routing issue. I have run into an issue before where requests come out the incorrect interface on the F5 if a floating IP is configured in the incorrect vlan.

     

    If you have any more questions, I am sure I can help.