Forum Discussion
ibrahimh2004_14
Nimbostratus
Dec 30, 2013persistence timeout
we configured persist timeout for universal to 7200 s but the entries still cleared after default timer 180 s. my version is 11.4.1 , any idea?
1 Reply
- nitass
Employee
it seems okay in my lab.
e.g.
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) show sys version Sys::Version Main Package Product BIG-IP Version 11.4.1 Build 608.0 Edition Final Date Wed Aug 14 17:23:43 PDT 2013 root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual bar ltm virtual bar { destination 172.28.20.15:80 ip-protocol tcp mask 255.255.255.255 pool foo profiles { http { } tcp { } } rules { myrule } source 0.0.0.0/0 source-address-translation { type automap } vs-index 31 } root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm rule myrule ltm rule myrule { when HTTP_REQUEST { persist uie [IP::client_addr]:[TCP::client_port] 7200 } } root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) show ltm persistence persist-records all-properties Sys::Persistent Connections universal - 172.28.20.15:80 - 200.200.200.101:80 ------------------------------------------------ TMM 1 Mode universal Value 192.168.206.171:62304 Age (sec.) 6884 Virtual Name /Common/bar Virtual Addr 172.28.20.15:80 Node Addr 200.200.200.101:80 Pool Name /Common/foo Client Addr 192.168.206.171 Owner entry Total records returned: 1
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects