How is persistence configured.

Persistence profiles are not defined inside a pool's configuration; pools define load balancing methods and member lists, while persistence is handled at the virtual server level through a separate profile association.

F5 BIG-IP implements persistence methods (Source Address Affinity, Cookie, Universal, etc.) as dedicated profile types. An administrator creates a persistence profile with the desired method and parameters, then associates that profile directly with a virtual server - making persistence flexible and independently configurable per virtual server.

Persistence is not a global BIG-IP setting; it is scoped to individual virtual servers via profile association, allowing different virtual servers to have different or no persistence configurations.

Persistence is not configured per individual pool member; it is applied at the virtual server level using a persistence profile that tracks client connections across all eligible pool members.