F5 301B BIG-IP LTM study plan
F5 301B BIG-IP LTM · Give each week a clear focus.
8 weeks · About 6 hours per week
BIG-IP LTM configuration and virtual servers
Map the full request path from client to pool member and identify where LTM configuration objects (virtual server, profile, pool, node, monitor) attach.
Build a standard virtual server with a destination address, port, and default pool, and verify it appears correctly in the configuration.
Configure a wildcard virtual server and a network virtual server, then explain when each is appropriate.
Create and test a forwarding (Layer 2) virtual server for a non-IP protocol and record the required settings.
Your checkpoint
A one-page diagram plus configuration notes showing four virtual server types (standard, wildcard, network, forwarding) with the exact settings used and a pass/fail test result for each.
Profiles and traffic processing
Identify the default profiles inherited by a new virtual server and explain the effect of each on traffic processing.
Configure TCP, HTTP, and OneConnect profiles on a test virtual server and observe connection reuse behavior.
Adjust an HTTP profile to insert a header and a TCP profile to change idle timeout, then verify the change with a client request.
Explain profile inheritance and precedence when a profile is set on both the virtual server and the pool.
Your checkpoint
A profile comparison table listing five profiles, their key settings, and observed traffic effects, backed by at least three client-side test results.
Pools, nodes, and load balancing methods
Create a pool with three nodes and set a health monitor on each member.
Configure and compare Round Robin, Least Connections, and Ratio load balancing methods using synthetic traffic.
Enable and test priority group activation so that a standby pool member takes traffic only when active members fall below a threshold.
Explain how node and member states (up, down, checking, forced offline) affect pool selection.
Your checkpoint
A load-balancing test log showing request distribution across three members for each of three methods, with a short written explanation of the observed differences.
Persistence and session management & Monitors and health checking
Configure source address affinity persistence and verify that repeated client requests reach the same pool member.
Configure cookie persistence and compare its behavior with source address persistence when a client address changes.
Create a custom HTTP monitor with send and receive strings and confirm member state changes when the expectation fails.
Explain persistence timeout, mirroring, and the interaction between persistence and monitor-driven failover.
Your checkpoint
A persistence and monitoring lab report with four test cases: source address persistence, cookie persistence, monitor pass, and monitor fail, each with captured evidence and a conclusion.
SSL/TLS termination and client certificate handling
Configure client-side SSL termination on a virtual server using a certificate and key, and confirm a successful TLS handshake.
Enable client certificate request and require a valid client certificate for a test connection.
Configure server-side SSL so LTM re-encrypts traffic to the pool member and verify the full chain.
Explain certificate chain order, SNI, and the effect of an incomplete chain on client trust.
Your checkpoint
A TLS configuration checklist with test results for four scenarios: termination only, mutual TLS, re-encryption, and an intentionally broken chain, each with the error observed and the fix applied.
iRules and traffic manipulation
Write an iRule that redirects HTTP to HTTPS and verify the redirect with a client request.
Write an iRule that selects a pool based on a URI path and test at least two paths.
Use an iRule event (HTTP_REQUEST or CLIENT_ACCEPTED) to log or insert a header, and confirm the effect in the connection trace.
Explain iRule event order and the difference between connection-side and request-side events.
Your checkpoint
A set of three working iRules with comments, plus a test matrix showing input, expected behavior, and observed behavior for each.
BIG-IP LTM configuration and virtual servers & Troubleshooting and monitoring LTM objects
Use the configuration utility and tmsh to compare a virtual server's effective settings against its configured settings.
Trace a failing request through virtual server, pool, and monitor states to identify the blocking object.
Interpret pool member status reasons and map each to a likely configuration cause.
Review logs and statistics for a virtual server to confirm traffic is reaching the intended pool.
Your checkpoint
A troubleshooting decision tree covering five common failure symptoms (no pool member available, TLS handshake failure, persistence mismatch, monitor down, iRule error) with the first diagnostic command for each.
BIG-IP LTM configuration and virtual servers & Profiles and traffic processing & Pools, nodes, and load balancing methods & Persistence and session management & Monitors and health checking & SSL/TLS termination and client certificate handling & iRules and traffic manipulation & Troubleshooting and monitoring LTM objects
Re-run a timed mixed-domain practice set and score each domain separately.
Revisit the two lowest-scoring domains and correct the specific configuration misunderstandings behind each missed item.
Rebuild one end-to-end scenario from scratch: virtual server, profile, pool, persistence, monitor, TLS, and one iRule.
Summarize the exam objectives you can now demonstrate without notes and list remaining gaps.
Your checkpoint
A final readiness scorecard by domain, a rebuilt end-to-end configuration that passes all checks, and a short list of remaining weak areas with a review action for each.
Milestones
Week 2: Can build a working virtual server with a non-default profile and explain the traffic effect of each profile without consulting notes.
Week 4: Can configure persistence and a custom monitor from memory and correctly predict member state changes in three scenarios.
Week 6: Can terminate TLS, require a client certificate, and write a redirect iRule, each verified by a passing client test.
Week 8: Scores at least 80% on a timed mixed-domain practice set and can rebuild the full end-to-end scenario without reference material.