Forum Discussion

Re: Log OneConnect Reuse

isn't oneconnect stats acceptable?

sol8688: Overview of OneConnect profile statistics

http://support.f5.com/kb/en-us/solutions/public/8000/600/sol8688.html

anyway, for irule, i do not think SERVER_CONNECTED event is triggered on reused connection since it is existing connection.

[root@ve1023:Active] config  b virtual bar list
virtual bar {
   snat automap
   pool foo
   destination 172.28.19.79:80
   ip protocol 6
   rules rule1
   profiles {
      http {}
      oneconnect {}
      tcp {}
   }
}
[root@ve1023:Active] config  b pool foo list
pool foo {
   members {
      200.200.200.101:80 {}
      200.200.200.102:80 {}
   }
}
[root@ve1023:Active] config  b rule rule1 list
rule rule1 {
   when HTTP_RESPONSE {
   log local0. "client-side [IP::client_addr]:[TCP::client_port]->[IP::local_addr clientside]:[TCP::local_port clientside]|server-side [IP::local_addr]:[TCP::local_port]->[IP::remote_addr]:[TCP::remote_port]"
}
}

[root@ve1023:Active] config  b profile oneconnect stats reset

[root@ve1023:Active] config  tail -f /var/log/ltm
Apr  5 02:06:22 local/tmm info tmm[4797]: Rule rule1 : client-side 172.28.65.161:55818->172.28.19.79:80|server-side 200.200.200.10:55818->200.200.200.101:80
Apr  5 02:06:23 local/tmm info tmm[4797]: Rule rule1 : client-side 172.28.65.161:55819->172.28.19.79:80|server-side 200.200.200.10:55819->200.200.200.102:80
Apr  5 02:06:28 local/tmm info tmm[4797]: Rule rule1 : client-side 172.28.65.161:55820->172.28.19.79:80|server-side 200.200.200.10:55818->200.200.200.101:80
Apr  5 02:06:33 local/tmm info tmm[4797]: Rule rule1 : client-side 172.28.65.161:55821->172.28.19.79:80|server-side 200.200.200.10:55819->200.200.200.102:80

[root@ve1023:Active] config  b profile oneconnect
PROFILE ONECONNECT oneconnect
|        (curr, max, reuse, new) = (2, 2, 2, 2)
No RepliesBe the first to reply