For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

edgranados_1975's avatar
edgranados_1975
Icon for Nimbostratus rankNimbostratus
Oct 21, 2016

Inet port exhaustion

Getting Inet port exhaustion on 10.xxx.xxx.xxx to 10.xxx.xxx.xxx:443

 

We have migrated from a 10.2.3 box to a new 11.6.1 box, after a few hours we started to see this alarm. 10.xxx.xxx.xxx:443 is the self IP of the old box. No clue why is causing this from that IP

 

Any help?

 

application delivery
LTM

1 Reply

  • Jinshu's avatar
    Jinshu
    Icon for Cirrus rankCirrus
    Oct 21, 2016

    Connections are defined by the source IP:port and destination IP:port combination. The most common situation is that port exhaustion happens on the source side, when they're headed for a common port.

     

    You are seeing this alerts on self IP address because of your SNAT (automap) configuration.

     

    The simple fix is to add more addresses to the SNAT pool and/or create a unique SNAT pool per LB pool.

     

    Please go through the F5 solution for this. https://support.f5.com/kb/en-us/solutions/public/7000/800/sol7820.html?sr=15280517exhaustion

     

    -Jinshu