Destination ip address persistence

You could just load-balance 100% of the requests between ServerA and ServerB. Alternatively, you can take maximum advantage of back-end server cache by removing the load-balancing where not needed. You can use destination IP persistence to ensure a request is routed to a server which has the response content cached, instead of load-balancing to a random server which has to search for the content on its storage unit... "It's somewhere on the hard-drive, just a sec, let me find it!" :)

Destination address Persistence

Persistence based on the destination address is much like source address persistence. Except that the F5 examines the destination of the packet rather than the source. Now, you might ask yourself, when would this actually be useful? Think of a setup where an LTM is load balancing a set of proxy servers that are doing caching. Clients would be forced through the proxies to the external site (read destination) and the proxy would cache that site. Going forward, it would make sense to balance clients going to the same destination to the same proxy since that particular proxy already has the website cached.

F5 LTM VE – Configuring Persistence