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

Doran_Lum_13484's avatar
Doran_Lum_13484
Icon for Nimbostratus rankNimbostratus
Feb 10, 2014

Time Sync issue on Application Servers

Hi all, currently we face some issue where two of our VM are recording slight difference in time capture of the transaction. I have check the VM tools and it's not sync to the ESX host. I have also c...
cloud
f5
microsoft
TMOS
vmware
nitass's avatar
nitass
Icon for Employee rankEmployee
Feb 10, 2014

is irule and tcl clock command useful? anyway, CLIENT_CLOSED is triggered when connection is closed either by manual or idle timeout.

e.g.

 config

root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual bar
ltm virtual bar {
    destination 172.28.24.10:23
    ip-protocol tcp
    mask 255.255.255.255
    pool foo
    profiles {
        mytcp { }
    }
    rules {
        myrule
    }
    source 0.0.0.0/0
    source-address-translation {
        type automap
    }
    vs-index 7
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm profile tcp mytcp
ltm profile tcp mytcp {
    app-service none
    defaults-from tcp
    idle-timeout 60
    keep-alive-interval 4294967295
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm rule myrule
ltm rule myrule {
    when CLIENT_ACCEPTED {
  set start [clock seconds]
}
when CLIENT_CLOSED {
  log local0. "Client=[IP::client_addr]:[TCP::client_port] VS=[IP::local_addr]:[TCP::local_port] Duration=[expr {[clock seconds] - $start}] sec"
}
}

 /var/log/ltm

[root@ve11a:Active:In Sync] config  tail -f /var/log/ltm
Feb 11 00:07:32 ve11a info tmm1[13662]: Rule /Common/myrule : Client=192.168.206.178:57236 VS=172.28.24.10:23 Duration=64 sec