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

paulpatriot_129's avatar
paulpatriot_129
Icon for Nimbostratus rankNimbostratus
Jun 27, 2016

What is the CLI to list open connections on the F5 Management Interface?

Trying to determine if a connections is not releasing when connected to the F5.

 

2 Replies

  • Just noticed you now want this info for your management address!

    In that case netstat will do the trick and devbabu's:

    netstat -an | grep management_ip_here" will work just fine.

    If you need connection information related to the data interfaces use the below.

    In v11 from TMSH use "show sys connection" or "show sys conn" for short

    in v10 / you can use - "bigpipe conn show all | grep -A5 x.x.x.x"

    enter tmsh from bash or type your tmsh commands with "tmsh" first, but you can't tab auto-complete unless you're in tmsh
    
    [root@big-ip-lab-1:ModuleNotLicensed:Active:Disconnected] config  tmsh
    
     root@(big-ip-lab-1)(cfg-sync Disconnected)(ModuleNotLicensed:Active)(/Common)(tmos) show sys conn
     Options:
          all-properties   exa              kil              peta             save-to-file     yotta            |
          default          gig              meg              raw              tera             zetta
    Properties:
          age              cs-client-port   cs-server-port   ss-client-addr   ss-server-addr   type
          cs-client-addr   cs-server-addr   protocol         ss-client-port   ss-server-port   {
    

    Since the BIG-IP is a full proxy you'll be able to show client and serverside information respective to the client and serverside of the connection through the BIG-IP.

    For example if you make a call to a VIP your IP would be the "client side" "cs-client-addr" and the VIP would be the server side "cs-server-addr".

    Similarly the BIG-IP to the pool members is the "ss", where the BIG-IP is now the client and the pool member / node is the server.