spud_141786
Mar 25, 2014Nimbostratus
evaluating Automap port usage
One drawback of using Automap is source TCP port exhaustion. Is there a convenient way to view the "high water mark" for Automap source port usage for a specific self IP address?
Interesting question. Was thinking about using tables, adding/removing unique instances of TCP::server_port during the SERVER_CONNECTED and SERVER_CLOSED events and then send a warning via an outbound call (also via an iRule) but I think the answer could be simpler. :)
You could always monitor the connections to the pool members that the self IP communicates with via SNMP and aggregate them in a graph.
In my case though I did not want to risk ever running out so I took the maximum connections and multiplied it by 10, added it to a SNAT Pool used that instead of automap. Internal IP's are free after all. :)
/Patrik