F5-CSE key terms

A BIG-IP configuration object that presents a listener address and port to clients and forwards matching traffic to a pool or other destination according to its type and profiles.

A named group of pool members that receive traffic from a virtual server, along with a load balancing method and health monitoring configuration that determine which members are eligible.

A node address and service port combination that belongs to a pool and can receive load-balanced connections, with its own optional ratio, priority, and monitor assignments.

A logical object representing a backend server IP address that BIG-IP manages; nodes own monitor state and can be referenced by multiple pools at once.

The algorithm a pool uses to choose among available members, such as round robin, least connections, observed, predictive, or ratio-based variants.

A pool setting that restricts traffic to members in the highest-priority group that still has enough available members, enabling standby tiers of servers.

A probe configuration that periodically tests a node or pool member and marks it up or down, removing failed members from load balancing selection.

Two monitor timers: the interval sets how often a probe is sent, and the timeout sets how long BIG-IP waits for a reply before counting the probe as failed.

The payload a monitor transmits to a service, such as an HTTP request or a TCP payload, whose expected response determines whether the target is considered healthy.

The exact or pattern-matched text a monitor must find in the service response for the probe to pass; a mismatch marks the object down.

Configuration objects attached to virtual servers that control protocol behavior and features such as TCP settings, HTTP parsing, SSL termination, persistence, and authentication.

A profile that keeps a client bound to the same pool member across requests, using methods such as source address, cookie, SSL session ID, or destination address.

An HTTP persistence method where BIG-IP inserts or reads a cookie identifying the chosen pool member, so returning clients are directed to that same member.

A persistence method that maps a client source IP address to a pool member for a configured timeout, keeping all sessions from that address on one server.

Event-driven Tcl-based scripts attached to virtual servers that inspect and modify traffic, select pools dynamically, redirect requests, or log data during connection processing.

A named point in connection processing, such as CLIENT_ACCEPTED or HTTP_REQUEST, at which an iRule's associated script block executes.

Choosing the target pool for a connection at runtime, which can be static on the virtual server or dynamic via an iRule or local traffic policy.

The virtual server setting that defines which listener address and port, or wildcard network, causes BIG-IP to accept and process an incoming connection.

Secure Network Address Translation rewrites the client source address to a translation address so backend servers see and reply to BIG-IP rather than the original client.

A node or pool member threshold that caps concurrent connections; when reached, BIG-IP stops selecting that member until connections fall below the limit.

A client-side or server-side configuration object holding certificates, keys, ciphers, and protocol versions used when BIG-IP terminates or initiates TLS.

The practice of decrypting TLS traffic at BIG-IP so that backend servers receive plaintext, offloading cryptographic work and enabling layer 7 inspection.

A deployment where BIG-IP decrypts client TLS and re-encrypts traffic to the backend server using a separate server-side SSL profile.

The public certificate plus matching private key installed on BIG-IP and referenced by an SSL profile to prove identity and complete the TLS handshake.

The ordered set of intermediate and root certificates that must accompany a server certificate so clients can build a trusted path to a known authority.

The profile applied to the client-facing side of a virtual server that determines which certificate, key, ciphers, and TLS versions are offered to connecting clients.

An access control configuration, often built with APM, that authenticates users and evaluates authorization before granting access to a protected virtual server or application.

The object that binds an access policy and its associated settings to a virtual server so that requests are gated by authentication and authorization checks.

The sequence in which BIG-IP applies listeners, profiles, iRules, persistence, and pool selection to a connection, which determines where a change takes effect.

A visual and logical view of how virtual servers, pools, and nodes relate, used to understand traffic flow and spot misconfigured or orphaned objects.

A set of BIG-IP devices configured to synchronize and fail over together, sharing configuration and, optionally, connection and persistence state.

A device group whose members synchronize configuration and participate in failover, so traffic moves to a peer when the active device becomes unavailable.

The operation that copies configuration objects from one BIG-IP to its device group peers so all members share a consistent running configuration.

The process by which a standby BIG-IP in a device group takes over active traffic handling, often triggered by a health check, manual command, or network failure.

A self IP address shared within a device group that moves to the active device, giving clients and peers a stable address during failover.

A high availability feature that replicates connection and persistence state to a standby device so established sessions survive a failover event.

The Traffic Management Shell, a command-line interface on BIG-IP used to create, modify, inspect, and save configuration objects and to run maintenance commands.

A diagnostic snapshot command that collects logs, configuration, and system state from BIG-IP into a single file for analysis or support escalation.