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

romolo82's avatar
romolo82
Icon for Cirrus rankCirrus
May 18, 2022
Solved

Nodes forwarding

Hi everybody, I have an issue with a request of my customer.  The request is the following: - An IP source 212.141.49.18 goes towards a VS on the LB with 192.168.18.46, this IP balances to nodes 19...
application delivery
  • Sebastiansierra's avatar
    Sebastiansierra
    May 20, 2022

    Hi,

    No problem, always is a pleasure to help, The feature that allows this configuration is Autolasthop, the flow is:

    212.141.49.18 to VS 192.168.18.46 -- VS 192.168.18.46 to pool 192.168.1.2 and 192.168.1.3 -- pool 192.168.1.2 and 192.168.1.3 to new vs  192.168.18.47 ----- new vs  192.168.18.47 to pool 192.168.18.36 and 192.168.18.37.

     

    Hope it´s works.

Sebastiansierra's avatar
Sebastiansierra
Icon for MVP rankMVP
May 19, 2022

Hi,

You need to configure a second layer of balancing, how? the server 192.168.1.2-3 must point to a new virtual server that has a pool with the IP 192.168.18.36 and 192.168.18.37.

  • romolo82's avatar
    romolo82
    Icon for Cirrus rankCirrus
    May 19, 2022

    Hi Sebastian, very interesting, thanks.

    So, the flow goes from 212.141.49.18 to VS 192.168.18.46, VS balances towards servers 192.168.1.2-3 and servers 192.168.1.2-3 must respond to ANOTHER VS with nodes 192.168.18.36 and 192.168.18.37, right? Should this new VS have also a new IP (so, NOT 192.168.18.46)? And how can two server nodes respond to the new server, with a SNAT? In this manner does the flow return to the original source 212.141.49.18?
    Sorry for a lot of question, but a very difficult issue for me.