Persistence is an option within each pool's definition.

Persistence is a profile type; an appropriate profile is created and associated with virtual server.

Persistence is a global setting; once enabled, loadbalancing choices are superceded by the persistence method that is specified.

Persistence is an option for each pool member. When a pool is defined, each member's definition includes the option for persistence.

insert

rewrite

passive

session

Cookie persistence allows persistence independent of IP addresses.

Cookie persistence allows persistence even if the data are encrypted from client to pool member.

Cookie persistence uses a cookie that stores the virtual server, pool name, and member IP address in clear text.

If a client's browser accepts cookies, cookie persistence will always cause a cookie to be written to the client's file system.

No SSL certificates are required on the pool members.

The pool members.SSL certificates must only exist.

The pool members.SSL certificates must be issued from a certificate authority.

The pool members.SSL certificates must be created within the company hosting the BIGIPs.

create profiles, create the iRule, create required pools, create the Virtual Server

create the Virtual Server, create required pools, create the iRule, edit the Virtual Server

create a custom HTTP profile, create required pools, create the Virtual Server, create the iRule

create required pools, create a custom HTTP profile, create the iRule, create the Virtual Server