How is persistence configured.

Persistence is not an option within a pool's definition on BIG-IP; pools define members and load balancing methods, while persistence is handled at the virtual server layer via profiles.

BIG-IP treats persistence as a profile - you create a persistence profile of the desired type (source address, cookie, SSL session ID, etc.) and associate it with a virtual server. This design keeps persistence configuration modular and reusable across multiple virtual servers.

Persistence is not a global setting on BIG-IP; it must be explicitly configured and attached per virtual server, so virtual servers without a persistence profile use only the load balancing algorithm.

Persistence is not configured per pool member; individual members do not hold persistence configuration - the persistence profile on the virtual server manages the mapping between clients and members.