Forum Discussion
NimbostratusAutomap SNAT and port exhaustion
We are currently using Automap SNAT in our environment and I am trying to design for a large increase in connections. Can we add to the available port space available for automap SNAT simply by adding an additional floating IP to the VLAN? Or will we be forced to create a SNAT pool to use multiple IPs to accommodate >64k connections?
5 Replies
natheCirrocumulus
Bubbagump... Additional floating self ips on the egress vlan should work. Snat pool is probably better/cleaner though. Just my 2c of course.
N
Bubbagump_12531What's the major advantage to SNAT pools? It seems like a 6/half dozen scenario to me.
pete_71470Cirrostratus
With SNAT pools you decide which virtual uses which pools. With an extra floating self-ip in the egress vlan, the entire vlan is affected. This might not matter in your deployment. Some nodes don't behave well (Exchange, for example) to having their source-ip change during their sessions so in this case having extra floats could causes surprises down the road.
- natheThanks Pete. Been offline for a while. Couldn't have said it any better.
- Hamish
With SNAT pools, you can add an iRule to choose the particular SNAT IP your client connection uses. That way the IP doesn't change mid session.
H
