F5-301A key terms

A dedicated Ethernet port on a BIG-IP device used for out-of-band administration, kept separate from the data-plane VLANs that handle application traffic.

The command-line shell on BIG-IP used to configure and inspect objects such as virtual servers, pools, and VLANs, and to run show, create, and modify commands.

A logical container that groups BIG-IP configuration objects so different teams or applications can share one device without seeing or changing each other's settings.

The process of adding a valid license file or registration key to a BIG-IP so licensed modules and throughput limits become available for configuration.

Setting how much memory and CPU a BIG-IP module such as LTM may use; the module must be provisioned before its features can be configured.

A layer-2 broadcast domain configured on BIG-IP, with tagged or untagged interfaces, that separates traffic and connects the device to network segments.

An IP address assigned to a BIG-IP VLAN that the device uses to communicate on that network, answer management traffic, and serve as a source for some connections.

A self IP that can move between cluster members during failover, typically used so clients and peers reach the active device at a consistent address.

A self IP setting that restricts which protocols and ports the BIG-IP accepts on that address, reducing exposed management and service access.

A route with destination 0.0.0.0/0 that tells BIG-IP where to send traffic for networks it does not know more specific routes for.

A BIG-IP object representing a real server by its IP address; pools reference nodes, and monitors can check node health.

A logical group of servers, represented as pool members, that receive traffic from one or more virtual servers after load-balancing decisions.

A node plus a service port, such as 10.1.1.1:80, that belongs to a pool and can be selected to receive client requests.

A test configured on a node or pool member that periodically checks whether the service is responding, marking it up or down based on results.

The algorithm a pool uses to choose a member for each new connection, such as round robin, least connections, or observed.

A BIG-IP listener defined by an address and port that accepts client traffic and forwards it according to its profiles, pool, and persistence settings.

The destination IP address configured on a virtual server; clients connect to this address and BIG-IP handles it locally rather than routing it.

A reusable set of settings attached to a virtual server that controls protocol behavior, such as TCP, HTTP, SSL, or persistence handling.

The pool a virtual server sends traffic to for a connection when no iRule or persistence decision selects a different destination.

A profile that keeps a client's sessions going to the same pool member for a period, using methods such as source address or cookies.

A Tcl-based script attached to a virtual server that can inspect and change traffic events, choose pools, redirect requests, or modify headers.

A BIG-IP feature that reuses server-side TCP connections for multiple client requests, reducing connection overhead to back-end servers and improving efficiency.

Source network address translation; BIG-IP replaces a client's source address with a chosen translation address so servers see the BIG-IP or a SNAT address.

A group of translation IP addresses that BIG-IP can use for SNAT, allowing many client connections to share a set of source addresses.

A SNAT mode in which BIG-IP uses the virtual server's own self IP address as the translation address for outbound server-side connections.

A BIG-IP configuration that translates the destination address and port of incoming packets to an internal server, often used for inbound access without a virtual server.

A digital document containing a public key and identity information, signed by a certificate authority, that lets clients verify a server's identity.

The secret cryptographic key paired with a certificate's public key; BIG-IP needs it to decrypt TLS traffic and prove ownership of the certificate.

A file containing a server certificate plus intermediate CA certificates, installed on BIG-IP so clients can build a complete chain of trust.

A BIG-IP profile that defines how the virtual server terminates TLS from clients, including certificates, cipher suites, and protocol versions.

Certificate signing request; a block of encoded information sent to a certificate authority to request a signed certificate for a key pair.

A collection of BIG-IP devices that share configuration and failover state in a device service cluster, with one member active for a traffic group.

The secure relationship established between BIG-IP devices, using certificates, that allows them to join a trust domain and synchronize configuration.

The process of copying configuration objects from one BIG-IP in a device group to its peers so all members have matching settings.

A high-availability feature that copies active connection state to a standby BIG-IP so established sessions can continue after a failover.

The primary BIG-IP log for local traffic events, including virtual server, pool, monitor, iRule, and connection messages useful during troubleshooting.

A packet capture utility available on BIG-IP that records traffic on an interface or VLAN for analysis of connection and routing problems.

A diagnostic snapshot that collects BIG-IP configuration, logs, and system state into a file for support analysis or review with iHealth.

A standard protocol BIG-IP supports for sending traps and exposing performance and health data to network management and monitoring platforms.

An F5 service that analyzes an uploaded QKView against known issues and best practices, producing detailed diagnostic findings and recommendations.