Forum Discussion
RSchill_194035
Nimbostratus
Mar 26, 2015Changed behaviour after after supposedly successful migration
We just replaced six older F5s (1500, 1600 and 3400 from 2005 and 2008) with 2 F5 Big IP 4000 using partions to separate the rulesets.
Everthing works fine, just a minor inconvenience showed up, as t...
StephanManthey
Nacreous
Mar 26, 2015Hi,
by default the virtual server will not change the source IP when forwarding the packets to the poolmember.
Exceptions for setups using OneConnect and PerformanceHTTP. In this case source IP may change as existing idle serverside connections are re-used (connection multiplexing).
If you noticed source NAT in the past I assume there is SNAT AutoMap configured for the virtual servers or there is a so called Default SNAT configured (lookup your SNAT List configurations, please).
The self IPs were used, if there was no floating self IP configured.
Since TMOS v11 it´s mandatory to have a floating self IP in the traffic-group used by your your virtual servers for proper SNATing.
I would recommend to grep your bigip.conf (separate files for admin partitions will be found in /config/partitions/ for SNAT entries (may also appear i.e. in iRules).
Thanks, Stephan
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects