Forum Discussion
Andrew-F5
Aug 26, 2020Employee
This is mostly due to either (1) not enough ports on the SNAT IP or (2) your virtual server is configured to 'preserve strict' for it's source port preservation option.
To resolve the first issue you would either (1) switch from SNAT automap to SNAT pool with mulitiple SNAT IPs or (2) add more SNAT IPs if you're already using a SNAT pool on the virtual server.
To resolve the first issue you could switch the source port preservation from 'preserve strict' to 'preserve' in the virtual server advanced configuration.
K8246: How the BIG-IP system handles SNAT port exhaustion
K13433: Configuring source port preservation for SNATs