Strange Persistence records

Which LTM version and platform are you running? Can you provide a sample of the persistence records from 'b persist all show all'? I'd guess this is because you have a CMP enabled virtual server on a compatible version and platform and each TMM instance is creating its own persistence record. You can disable CMP for the virtual server if you need to use some form of persistence other than cookie insert.

 

 

For info on CMP you can check SOL7751:

 

 

SOL7751: Overview of Clustered Multi-Processing

 

https://support.f5.com/kb/en-us/solutions/public/7000/700/sol7751.html

 

 

Aaron

I'm using the LTM Big-IP 6800 and running the 9.4.7 software version, so I don't use CMP.

Here is the cap:

   
 PERSISTENT CONNECTIONS   
 ...   
 |     Mode source addr   Value 1.x.x.221   
 |        virtual 1.x.x.85:https   node 1.x.x.78:http   age 1126sec   
 |     Mode source addr   Value 1.x.x.221   
 |        virtual 1.x.x.85:https   node 1.x.x.84:http   age 46sec   
 ...   
 

Same source adress, but different destiny nodes... and this is repeated in many other cases.

Thanks hoolio

The 6800 supports CMP in 10:

 

 

SOL9763: Clustered Multi-Processing on the BIG-IP 6400 and BIG-IP 6800 platforms

 

https://support.f5.com/kb/en-us/solutions/public/9000/700/sol9763.html

 

 

If that's not the issue, then can you post anonymised copies of the VS, pool and source address persistence profile configuration using 'b virtual VS_NAME list', 'b pool POOL_NAME list' and 'b persist PERSIST_PROFILE_NAME'?

 

 

Thanks,

 

Aaron

I'm not using CMP. As I said, I'm using the 9.4.7 software version. Here is the information you asked me.

VIRTUAL ADDRESS 1.x.x.85   UNIT 1  
 |     ARP enable  
 |     (cur, max, limit, tot) = (77, 145, 0, 489122)  
 |     (pkts,bits) in = (8.489M, 26.00G), out = (9.455M, 71.91G)  
 +-> VIRTUAL virtual_443   SERVICE https  
 |     PVA acceleration none  
 |     (cur, max, limit, tot) = (74, 124, 0, 140736)  
 |     (pkts,bits) in = (6.218M, 23.99G), out = (7.247M, 55.81G)  
 |     requests (total) = 2.040M  
 +-> RULE iRule  
 +-> HTTP_REQUEST   1136756 total   1 fail   0 abort  
 +-> LB_SELECTED   756626 total   0 fail   0 abort  
 +-> POOL pool_80  LB METHOD observed   MIN/CUR ACTIVE MEMBERS 0/4  
 |     (cur, max, limit, tot) = (0, 23, 0, 23062)  
 |     (pkts,bits) in = (147439, 139.3M), out = (111301, 517.2M)  
 +-> POOL MEMBER pool_80/1.x.x.51:http   active,up  
 |   |     session enabled    priority 1    ratio 1  
 |   |     (cur, max, limit, tot) = (0, 6, 0, 5658)  
 |   |     (pkts,bits) in = (39522, 36.22M), out = (28880, 95.32M)  
 |   |     requests (total) = 5659  
 +-> POOL MEMBER pool_80/1.x.x.78:http   active,up  
 |   |     session enabled    priority 1    ratio 1  
 |   |     (cur, max, limit, tot) = (0, 7, 0, 7517)  
 |   |     (pkts,bits) in = (52298, 47.80M), out = (37482, 126.2M)  
 |   |     requests (total) = 7519  
 +-> POOL MEMBER pool_80/1.x.x.84:http   active,up  
 |   |     session enabled    priority 1    ratio 1  
 |   |     (cur, max, limit, tot) = (0, 5, 0, 6826)  
 |   |     (pkts,bits) in = (38090, 38.89M), out = (30909, 205.3M)  
 |   |     requests (total) = 6902  
 +-> POOL MEMBER pool_80/1.x.x.84:http   active,up  
 |     session enabled    priority 1    ratio 1  
 |     (cur, max, limit, tot) = (0, 5, 0, 3061)  
 |     (pkts,bits) in = (17529, 16.42M), out = (14030, 90.26M)  
 |     requests (total) = 3085

pool pool_80 {  
 lb method observed  
 monitor all HTTP  
 partition someone  
 members  
 1.x.x.51:http  
 1.x.x.78:http  
 1.x.x.84:http  
 1.x.x.84:http  
 }

The persistence profile configuration is the default one for a source address persistence.

Thanks for that. Yeah, I was just pointing out that you could upgrade to 10 for CMP support.

 

 

Can you also post the iRule attached to the VS?

 

 

Thanks,

 

Aaron

The iRule isn't relevant (I think), select a pool using the information provided by the URI

Yes, I guess it would make sense that the value (source IP) and the virtual IP:port would be the same in two different persistence records if you have two different pools associated with the same VIP via the iRule.

 

 

Aaron

Thanks for your help Hoolio!!