Forum Discussion

Bubbagump_12531's avatar
Bubbagump_12531
Icon for Nimbostratus rankNimbostratus
Sep 16, 2014

Automap 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

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Bubbagump... Additional floating self ips on the egress vlan should work. Snat pool is probably better/cleaner though. Just my 2c of course.

     

    N

     

  • What's the major advantage to SNAT pools? It seems like a 6/half dozen scenario to me.

     

  • 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.

     

    • nathe's avatar
      nathe
      Icon for Cirrocumulus rankCirrocumulus
      Thanks Pete. Been offline for a while. Couldn't have said it any better.
  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus

    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