Pool Statistics

have you seen this one?

 

 

sol8457: Connection limits configured on pool members or nodes within a Clustered Multi-Processing configuration are incorrectly enforced per TMM instance

 

http://support.f5.com/kb/en-us/solutions/public/8000/400/sol8457.html

 

 

hope this helps.

Yes but I 've Release 11.1.0, not 9.6.x

Yes but I 've Release 11.1.0, not 9.6.xthe solution is applied to up to 11.2.1. the 9.6.0 and 9.6.1 issue is each blade (instead of each tmm) incorrectly performs connection limit.

So, It's a bug....right?

On VIPRION the connection limit should apply per blade. Are these nodes in any other Pools? Perhaps you could change the connection limit to 3000 and apply it to the Pool rather than the Nodes.

So, It's a bug....right?yes, it is.

I've just one blade. Each node is in three different pools and I must use connection limit on the node...

Nitass, What Lies Beneath,

 

thanks for your quick answers but I need to summarize...

 

It's a single blade and the pool statistics menù show 750 connections per node instead of 1500 per node.

 

 

Can I say..."You need to update the Viprion to solve this issue" ?

 

Iirc that bug hasn't been fixed yet has it?

 

 

 

From memory, the way its doing things is dividing the number of connections max by the number of tmm's on the blade... So you get 750 per tmm...

 

 

H

sorry i think i was wrong. sol8457 should not be the case. i was able to get a number of connection limit i set.

[root@c2400:/S1-green-P:Active:Standalone] config  tmsh show sys version

Sys::Version
Main Package
  Product  BIG-IP
  Version  11.2.0
  Build    2451.0
  Edition  Hotfix HF1
  Date     Tue Jun  5 23:45:09 PDT 2012

Hotfix List
ID387964  ID387843

[root@c2400:/S1-green-P:Active:Standalone] config  tmsh show sys tmm-info|grep -i sys\:\:tmm\:
Sys::TMM: 1.0
Sys::TMM: 1.1
Sys::TMM: 1.2
Sys::TMM: 1.3
Sys::TMM: 1.4
Sys::TMM: 1.5
Sys::TMM: 1.6
Sys::TMM: 1.7

root@(c2400)(cfg-sync Standalone)(/S1-green-P:Active)(/Common)(tmos) list ltm virtual bar
ltm virtual bar {
    destination 100.100.100.100:80
    ip-protocol tcp
    mask 255.255.255.255
    pool foo
    profiles {
        tcp { }
    }
    snat automap
    vlans-disabled
}
root@(c2400)(cfg-sync Standalone)(/S1-green-P:Active)(/Common)(tmos) list ltm pool foo
ltm pool foo {
    members {
        200.200.200.101:80 {
            address 200.200.200.101
        }
        200.200.200.111:80 {
            address 200.200.200.111
        }
    }
}
root@(c2400)(cfg-sync Standalone)(/S1-green-P:Active)(/Common)(tmos) list ltm node 200.200.200.101
ltm node 200.200.200.101 {
    address 200.200.200.101
    connection-limit 40
}
root@(c2400)(cfg-sync Standalone)(/S1-green-P:Active)(/Common)(tmos) list ltm node 200.200.200.111
ltm node 200.200.200.111 {
    address 200.200.200.111
    connection-limit 40
}

 on client

 ab -n 100 -c 100 http://100.100.100.100/
This is ApacheBench, Version 2.0.40-dev <$Revision: 1.146 $> apache-2.0
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright 2006 The Apache Software Foundation, http://www.apache.org/

Benchmarking 100.100.100.100 (be patient)...
Test aborted after 10 failures

apr_socket_connect(): Connection reset by peer (104)

 on bigip

[root@c2400:/S1-green-P:Active:Standalone] config  tmsh show ltm node 200.200.200.101 | grep -i maximum
  Maximum Connections          40        -
[root@c2400:/S1-green-P:Active:Standalone] config  tmsh show ltm node 200.200.200.111 | grep -i maximum
  Maximum Connections          40        -