F5CAB2 Questions and Answers

In BIG-IP traffic management,persistence profilescause existing client connections (and subsequent requests) to be repeatedly sent to the same pool member. When persistence is enabled, simply preventing new connections is not sufficient if the requirement is toimmediately remove all existing connections.

Key behavior of pool member states:

Forced Offline

Immediately removes the pool member from load balancing.

Terminates all existing connections, regardless of persistence.

Prevents new connections from being established.

This is the correct state when urgent maintenance or troubleshooting is required.

Disabled

Preventsnew connectionsfrom being sent to the pool member.

Allows existing connections to continue, which is not acceptable when persistence is configured and connections must be cleared immediately.

Offline (non-forced)

Similar to Disabled behavior depending on context.

Doesnot guarantee immediate terminationof existing connections.

Manually deleting connections via the command line

Is unnecessary and operationally inefficient.

BIG-IP already provides a supported mechanism (Forced Offline) to cleanly and immediately remove traffic.

Conclusion:

To immediately removeall existing connections, including those maintained by persistence, the BIG-IP Administrator must set the pool member to aForced Offlinestate. This directly satisfies the requirement without additional manual steps.

MAC Masquerade allows a traffic group to use a shared MAC address to speed up failover. When the system DB variable tm.macmasqaddr_per_vlan is enabled, the BIG-IP generates a unique MAC address for each VLAN by algorithmically modifying the base MAC address using theVLAN ID.

The calculation forVLAN 1501works as follows:

Base MAC:The administrator set the base to 02:12:34:56:00:00.

VLAN ID Conversion:The decimal VLAN ID (1501) must be converted into hexadecimal.

$1501 \div 16 = 93$ remainder13(Din hex)

$93 \div 16 = 5$ remainder13(Din hex)

$5 \div 16 = 0$ remainder5

Result: $1501$ (Decimal) =05DD(Hex).

Substitution:The BIG-IP replaces the last two octets of the base MAC address with the hexadecimal representation of the VLAN ID.

Final Result:02:12:34:56:05:dd.

On BIG-IP systems,physical interface bandwidth is fixedby the link speed (for example, 1GbE or 10GbE). When traffic demand exceeds the capacity of a single interface, BIG-IP provideslink aggregationthroughtrunks.

Key concepts involved:

InterfacesA single physical interface (such as 1.1) is limited to its negotiated link speed. You cannot exceed this capacity through software tuning alone.

Trunks (Link Aggregation)Atrunkcombines multiple physical interfaces into a single logical interface.

BIG-IP supports LACP and static trunks.

Traffic is distributed across member interfaces, increasingaggregate bandwidthand providingredundancy.

VLANs are then assigned to thetrunk, not directly to individual interfaces.

Why optionBis correct:

Creating atrunk with two interfacesallows BIG-IP to use both physical links simultaneously.

This increases total available bandwidth (for example, two 10Gb interfaces → up to 20Gb aggregate capacity).

This is thedocumented and supported methodfor scaling bandwidth on BIG-IP.

Why the other options are incorrect:

A. Increase the MTUMTU changes affect packet size and efficiency,not total bandwidth capacity.

C. Assign two interfaces to the VLANBIG-IP doesnotsupport assigning a VLAN to multiple interfaces directly. VLANs must be associated withone interface or one trunk.

D. Set the media speed manuallyMedia speed can only be set up to the physical capability of the interface and connected switch port. It cannot exceed the hardware limit.

Conclusion:

To increase total available bandwidth on BIG-IP when a single interface is insufficient, the administrator must create atrunk object with multiple interfacesand move the VLAN onto the trunk. This aligns directly with BIG-IP data plane design and best practices.

BIG-IP virtual server types define how traffic is handled at the data plane when it matches a virtual server’s destination address and service port.

According to BIG-IP Administration Data Plane Concepts:

Standard virtual server

The default and most commonly used type

Accepts client connections andforwards traffic to pool members

Supports bothTCP and UDPtraffic

Allows full use of profiles (UDP, FastL4, persistence, etc.) and iRules

Required when the goal is toprocess and pass traffic through BIG-IP

Drop virtual server

Silently discards matching traffic

No response is sent to the client

Reject virtual server

Actively rejects traffic by sending an error response

For UDP, BIG-IP may send an ICMP unreachable message

Block virtual server

Used to block traffic at the virtual server level

Traffic is neither forwarded nor processed by pools

In this scenario:

The administrator explicitly wants the UDP traffic to beforwarded

Only aStandard virtual serverforwards traffic to a pool or next-hop destination

Why the Other Options Are Incorrect:

A. Drop– Traffic is silently discarded

B. Reject– Traffic is actively rejected

C. Block– Traffic is blocked and not forwarded

Key Data Plane Concept Reinforced:

When traffic must beaccepted and forwarded—regardless of whether it is TCP or UDP—the BIG-IP administrator must use aStandard virtual server, which is the only virtual server type designed for normal application traffic processing.

===========

Understanding the default behavior of aStandard Virtual Serverregarding address and port translation is fundamental to BIG-IP administration.

Source Address Translation (SNAT):By default, the BIG-IP system doesnotperform Source Address Translation (SNAT). This means that the packet's source IP address (theClient IP) remains preserved as it passes through the BIG-IP to the pool member. This is critical for backend servers to identify the original client for logging and security purposes. Therefore, the client IP address is unchanged between the client-side and server-side connections.

Destination Address Translation (DAT):By default, a Standard Virtual Serveralwaysperforms Destination Address Translation. The BIG-IP system changes the destination IP from the Virtual Server's IP address to the IP address of the specificPool Memberselected by the load balancing algorithm. Consequently, the server-side destination IP is different from the client-side destination IP.

Port Translation:By default,Port Translationis enabled. If a Virtual Server is listening on port 80 and the selected pool member is configured for port 8080, the BIG-IP will translate the destination port. Even if the ports happen to be the same, thesettingallows for change, whereas the default SNAT setting (None) ensures the client IP remains static.

F5 BIG-IP uses aConfigSyncmechanism to ensure that all members of a Device Service Cluster (DSC) share the same configuration.

Manual Synchronization:By default, configuration changes made on one device (the "source") do not automatically propagate to other members.

Direction of Sync:Once a Virtual Server is created on device 1, that device's configuration is now "newer" than the rest of the group. The administrator must initiate a synchronization from themodified device (device 1) to the Sync-Failover group.

Consistency:This ensures that if a failover occurs, device 2 (the standby) will have the exact same Virtual Server configuration and can take over traffic immediately without interruption.

SNAT Automapis a feature that automatically selects a self-IP address to use as the source address for translated packets. The selection logic follows a strict hierarchy to ensure that traffic is routable back to the BIG-IP:

Egress VLAN Priority:The BIG-IP first looks at the VLAN through which the traffic is exiting toward the pool member (the egress VLAN).

Floating Self-IP Preference:If the egress VLAN has afloating self-IP address, the BIG-IP will always prefer it for SNAT Automap. This is critical for High Availability (HA) because, during a failover, the floating IP moves to the new active device, allowing existing connections to be maintained or correctly timed out.

Non-Floating Fallback:If no floating self-IP is available on the egress VLAN, the system will use a floating self-IP from a different VLAN. If no floating IPs exist at all, it will then fall back to the non-floating self-IP.

Key Data Plane Concept:

The management IP is never used for data plane traffic. In this scenario, since the administrator has configured a floating self-IP, that specific address becomes the source for all SNAT Automap traffic leaving that VLAN to ensure symmetric routing during HA events.

When handling high-volume UDP traffic where the BIG-IP does not need to maintain any session history or relationship between packets, aStatelessvirtual server is the appropriate choice.

No Connection Tracking:A stateless virtual server does not create or maintain entries in the BIG-IP connection table. This means the system processes each packet as an individual event, without "considering previous connections" or packets from the same source.

High Performance:Because the system bypasses the overhead of state management, stateless virtual servers provide the highest possible throughput for UDP and ICMP traffic.

Use Cases:This is ideal for services like DNS (stateless queries) or some types of syslog traffic where each packet is independent and doesn't require the persistence or protocol inspection typically provided by a full-proxy.

Why other options are incorrect:

Forwarding:While a Forwarding (IP) virtual server can handle UDP, it still maintains a state entry in the connection table to ensure return traffic is handled correctly.

Standard:This is a full-proxy virtual server. It is inherently stateful and requires a connection table entry for every flow it manages.

Reject:This is a special virtual server type that simply drops incoming traffic and, in the case of TCP, sends a reset (RST) or, for UDP, sends an ICMP unreachable message. It is not a load balancing type.

TheForced Offlinestate is a critical administrative tool used during maintenance to ensure a device remains in a non-functional state relative to the traffic group.

Preventing Active Status:When a device is in "Forced Offline," it is effectively disqualified from the HA election process. Even if the other peer fails, a device in Forced Offline willnotbecome active. This is vital during maintenance (like firmware upgrades or hardware replacement) to prevent an unstable or half-configured device from attempting to process traffic.

Traffic Termination:Placing a device in Forced Offline triggers the system to stop accepting new connections and, depending on the configuration, can facilitate the termination of existing connections so that the administrator can perform work without the data plane actively utilizing system resources.

Persistence Handling:Unlike the "Disabled" state, Forced Offline ignores persistence records, ensuring that no new traffic is steered to the device via session affinity.

To select the correct virtual server type, an administrator must balance the need for L7 intelligence versus raw throughput and hardware offloading:

Performance (Layer 4) Virtual Server:This type is designed for maximum speed. It uses thefastL4profile, which allows the BIG-IP system to leverage theePVA (Embedded Packet Velocity Accelerator)hardware chip. When a Performance (L4) virtual server is used, the system processes packets at the network layer (L4) without looking into the application payload (L7). This fulfills the requirement for hardware acceleration and avoids the overhead of HTTP optimization features, which are not needed in this scenario.

Performance (HTTP) Virtual Server:While fast, this type uses thefasthttpprofile to provide some L7 awareness and optimization (like header insertion or small-scale multiplexing). Since the requirement specifically states HTTP optimization isnotrequired, the L4 variant is more efficient.

Standard Virtual Server:This is a full-proxy type. While it offers the most features (SSL offload, iRules, Compression), it processes traffic primarily in the TMOS software layer (or via high-level hardware assistance), which is "slower" than the pure hardware switching path of the Performance (L4) type.

Stateless Virtual Server:This is typically used for specific UDP/ICMP traffic where the system does not need to maintain a connection table. It is not appropriate for standard HTTP (TCP) applications requiring persistent sessions or stateful load balancing.

By choosingPerformance (Layer 4)with thefastL4profile, the organization ensures that the traffic is handled by the hardware acceleration chips, providing the lowest latency and highest throughput possible for their HTTP application.

The primary distinction between Activ41e and Standby units revolves around which unit is currently processing traffic.

Traffic Objects (C & E):The unit in the43Activestate is the only one that answers ARP requests forVirtual Server addressesandFloating Self-IPs. The Standby unit remains "quiet" for these addresses to avoid IP conflicts on the network.

Monitors (A - False):Boththe Active and Standby units perform health monitors on pool members by default. This ensures that the Standby unit is ready to take over with an up-to-date view of the pool's health.

Failover (B - False):A failover trigger (like a VLAN fail-safe) causes the Active unit to go Standby and the Standby unit to go Active; it affects both.

Management (D - False):Configuration changes can technically be made on either unit (though it is best practice to make them on the Active unit) and then synchronized to the peer.

The BIG-IP system uses a specific precedence algorithm to determine which virtual server (listener) should process an incoming packet when multiple virtual servers might match the criteria. Since BIG-IP version 11.3.0, the system evaluates three primary factors in a fixed order of importance:

Destination Address:The system first looks for the most specific destination match. A "Host" address (mask /32) is preferred over a "Network" address (mask /24, /16, etc.), which is preferred over a "Wildcard" (0.0.0.0/0).

Source Address:If multiple virtual servers have identical destination masks, the system then evaluates the source address criteria. Again, a specific source host match is preferred over a source network or a wildcard source.

Service Port:Finally, if both destination and source specifications are equal, the system checks the port. A specific port match (e.g., 80) is preferred over a wildcard port (e.g., or 0).

Following this logic, a virtual server configured with a specificdestination host, a specificsource host, and a specificservice portrepresents the highest level of specificity and thus the highest preference.

When managing a large environment with hundreds of Virtual Servers, the most efficient way to identify the relationship between an iRule and the objects it manages is to view the properties of the iRule itself.

iRule Properties:Within the BIG-IP Configuration Utility, navigating toLocal Traffic > iRulesand selecting a specific iRule provides a "Statistics" or "Usage" tab (depending on the version). This view explicitly lists all Virtual Servers currently associated with that specific iRule.

Centralized Management:Instead of manually checking 235 individual Virtual Servers under the "Virtual Servers" menu, the iRules menu acts as a central point of reference for that specific logic.

Data Plane Impact:Because iRules can modify traffic flow, headers, and load balancing decisions, seeing the full list of affected Virtual Servers is critical before making adjustments to avoid unintended side effects across the application portfolio.

In BIG-IP LTM, apool member statedirectly affects how traffic is handled at the data plane level. When a pool member ismanually disabled, BIG-IP changes the member’s availability state todisabled, which has specific and predictable traffic-handling consequences.

According to BIG-IP Administration Data Plane Concepts:

Adisabled pool member:

Doesnot accept new connections

Continues to processexisting non-persistent connectionsuntil they naturally close

Isremoved from load-balancing decisions, including persistence lookups

Most importantly for this question:

Persistent connections(such as those created using source-address persistence, cookie persistence, or SSL persistence) arenot honoredfor a disabled pool member

BIG-IP willnot send new persistent trafficto a disabled member, even if persistence records exist

Therefore, when a pool member is manually disabled, itstops processing persistent connections, while allowing existing non-persistent flows to drain gracefully.

Why the Other Options Are Incorrect:

B– Persistent connections are not honored for a disabled pool member

C– Existing connections are not immediately terminated when a pool member is disabled

D– Only the disabled pool member stops accepting new connections, not all pool members

Key Data Plane Concept Reinforced:

Manually disabling a pool member is agraceful administrative actionthat prevents new and persistent traffic from reaching the member while allowing existing connections to complete, which is critical for maintenance and troubleshooting scenarios.

===========