Forum Discussion

Matt_70198's avatar
Matt_70198
Icon for Nimbostratus rankNimbostratus
Feb 28, 2013

Source address persistence

If i do a tmsh sh ltm persistence persist-records I just see the VIP address and the node address... I would expect to see the public source IP of the client? We do not have any nat or snat enabled. Is this normal?

 

Is there a way I can tell if a client IP has a persistance record on the F5 and what node it points to?

 

I assume that source address persistence gets refreshed as the client sends data back and forth over the load balancer? It doesn't automatically timeout x seconds after the persistence is created correct? It times out x seconds after it's been idle?

 

 

tmsh sh ltm persistence persist-records

 

source-address 10.10.8.7:443 10.10.9.21:443 1

 

source-address 10.10.8.7:443 10.10.9.22:443 1

 

source-address 10.10.8.7:443 10.10.9.21:443 1

 

source-address 10.10.8.7:443 10.10.9.21:443 1

 

source-address 10.10.8.7:443 10.10.9.22:443 1

 

source-address 10.10.8.7:443 10.10.9.21:443 1

 

source-address 10.10.8.7:443 10.10.9.21:443 1

 

 

Thanks!

 

config
design

4 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Mar 01, 2013
    can you try "show ltm persistence persist-records all-properties"? 

    root@ve10(Active)(tmos) show ltm persistence persist-records all-properties
Sys::Persistent Connections
source-address - 172.28.19.252:80 - 200.200.200.101:80
------------------------------------------------------
  TMM           0
  Mode          source-address
  Key           192.168.206.75
  Age (sec.)    8
  Virtual Name  bar
  Virtual Addr  172.28.19.252:80
  Node Addr     200.200.200.101:80
  Pool Name     foo
  Client Addr   192.168.206.75

Total records returned: 1
  • Matt_70198's avatar
    Matt_70198
    Icon for Nimbostratus rankNimbostratus
    Mar 01, 2013
    Aha, I didn't see that all-properties option when I did ?... Thank Nitass!

     

     

    What causes the persistence to be refreshed? I can look at my own connection an see the age time increase with time... when I click some links it doesn't reset, then I click another link and the age resets and goes back to 0.
  • Matt_70198's avatar
    Matt_70198
    Icon for Nimbostratus rankNimbostratus
    Mar 01, 2013

    Also one more question, if there is persistence to a given node... and that node goes offline, what happens with that persistence record? Is it dropped automatically?

     

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Mar 01, 2013
    What causes the persistence to be refreshed? I can look at my own connection an see the age time increase with time... when I click some links it doesn't reset, then I click another link and the age resets and goes back to 0.it will be refreshed if bigip receives (processes) request. are you sure if that content is not from (browser or proxy) cache?

    if there is persistence to a given node... and that node goes offline, what happens with that persistence record? Is it dropped automatically?i understand the record will be updated upon receiving request. 

    [root@ve10:Active] config  b virtual bar list
virtual bar {
   snat automap
   pool foo
   destination 172.28.19.252:80
   ip protocol 6
   persist mysource
   profiles {
      http {}
      tcp {}
   }
}
[root@ve10:Active] config  b pool foo list
pool foo {
   monitor all http
   members {
      200.200.200.101:80 {}
      200.200.200.111:80 {}
   }
}
[root@ve10:Active] config  b profile mysource list
profile persist mysource {
   mode source addr
   timeout indefinite
}

1. pool members are up, persistence record is created.

[root@ve10:Active] config  b pool foo|grep -i pool\ member
+-> POOL MEMBER foo/200.200.200.101:80   active,up
+-> POOL MEMBER foo/200.200.200.111:80   active,up

[root@ve10:Active] config  b persist show all
PERSISTENT CONNECTIONS
|     Mode source addr   Value 172.28.19.251
|        virtual 172.28.19.252:80   node 200.200.200.111:80   age 58sec

2. the pool member in persistence record is down but the record still exists.

[root@ve10:Active] config  b pool foo|grep -i pool\ member
+-> POOL MEMBER foo/200.200.200.101:80   active,up
+-> POOL MEMBER foo/200.200.200.111:80   inactive,down

[root@ve10:Active] config  b persist show all
PERSISTENT CONNECTIONS
|     Mode source addr   Value 172.28.19.251
|        virtual 172.28.19.252:80   node 200.200.200.111:80   age 195sec

3. the client sends another request. persistence record is updated to new pool member.

[root@ve10:Active] config  b persist show all
PERSISTENT CONNECTIONS
|     Mode source addr   Value 172.28.19.251
|        virtual 172.28.19.252:80   node 200.200.200.101:80   age 2sec