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

aits_network_pr's avatar
aits_network_pr
Icon for Nimbostratus rankNimbostratus
Feb 08, 2017

Loadbalancing based on source IP

Hi all,   Thank you to have a look on the issue I am facing.   For PRTG, I created 2 virtual servers (UDP / 2055). POOL containing server PRTG 1> POOL containing server PRTG 2>   the idea...
application delivery
LTM
aits_network_pr's avatar
aits_network_pr
Icon for Nimbostratus rankNimbostratus
Feb 08, 2017

That's very clear. thank you. but the issue is that this is not a TCP established session that really ends after a while. The PRTG clients push netflow traffic all the time to the LB via UDP 2055. We set the new VS 2 days ago and we still don't see traffic arriving to it. I don't know how to reset the LB so that it can take this new config into account.

 

Kai_Wilke's avatar
Kai_Wilke
Icon for MVP rankMVP
Feb 08, 2017

Hi A+,

The F5 handles UDP in a stateful manner. So as long as the client port of the PRTG clients remains the same, the the individual UDP-datagrams will match the existing "UDP-connection" entry and configuration change won't become active.

To kill the existing "UDP-connection" entry issue the command below...

[root@hostname:Standalone] config  tmsh delete sys connection cs-server-addr 10.104.100.1 cs-server-port 2055

After killing the connection entries to your VS-PRTGXX virtual, the very next UDP-datagramm will create a new session using the updated configuration.

Cheers, Kai