T Techclick ← All lessons
F5 · LTM · Course hub · Interactive lesson

F5 BIG-IP LTM complete course, module by module

Seven interactive lessons mapped to the Techclick LTM PDFs in OneDrive_1_8-26-2026.zip. Same lab IPs, linked runbooks, scored quizzes.

12 min read · L2 primary · Quiz at end

After this page you can

Lessons · F5 LTM series

F5 LTM recorded course · 7 modules

Same lab numbers on every page: client 198.51.100.50, VIP 192.0.2.100, Self IPs 192.0.2.10 / 10.20.20.10, members 10.20.20.101–103.

  1. Hub · Course map ← you are here
  2. M1 · Fundamentals & admin
  3. M2 · Networking & traffic flow
  4. M3 · Virtual Servers & pools
  5. M4 · Profiles, SNAT, SSL
  6. M5 · Monitors, iRules, policies
  7. M6 · High availability
  8. M7 · Troubleshooting

Next → M1 · Fundamentals & admin

Recorded course + workbooks: My Courses · syllabus F5 LTM / GTM / ASM

Why this series exists

The OneDrive pack you opened today — OneDrive_1_8-26-2026.zip — is the Techclick F5 BIG-IP LTM recorded course: Modules 1–7 plus the training PPT. This hub is the public blog map of that same course. Each module is one interactive lesson with a runbook, portal mock, traps table, and scored quiz.

Hero · ADC in the path
Users, an application delivery controller, and three backend servers
Clients never talk to Web01 directly. They talk to a Virtual IP. BIG-IP chooses a healthy pool member.

Use this page as the table of contents. Then walk the modules in order. Do not jump to iRules before Self IPs. The PDFs are built as a ladder: admin plane → data-plane networking → publish the app → process the app → prove health → survive a device failure → troubleshoot without guessing.

Quick answer

BIG-IP LTM is a full proxy. The client TCP session ends on the Virtual Server. A second session starts toward a pool member. Everything useful — SSL offload, SNAT, persistence, HTTP iRules — happens because those two sessions are independent.

Mental model

Say this out loud before Module 1: TMM moves packets. MCPD moves config. The Management IP never carries the application.

Flow 1 · course ladder
M1Planes + TMSHM2VLAN / Self IPM3VS + PoolM4SNAT / SSLM5Health / L7M6–7HA + proof

Read left to right. Each module unlocks the next object you can safely configure.

Journey · client to server
Packet path through VLANs and the load balancer engine
Module 2 is the wiring. Module 3 hangs the application on that wiring. If Module 2 is wrong, Module 3 looks 'down' forever.

How to use the seven lessons

ModuleYou can doDo not skip
1 FundamentalsExplain TMOS / TMM / MCPD; license, provision, UCSNTP, save sys config
2 NetworkingVLAN tagged/untagged, Self IP, Port Lockdown, route, ARPManagement plane for app traffic
3 VS & PoolsNode vs member vs pool vs VS; Round Robin vs Least ConnectionsCalling the VIP 'the pool'
4 Profiles / SNAT / SSLChoose Automap vs No-SNAT; offload vs re-encrypt vs passthroughHTTP cookie persist on passthrough
5 Monitors / iRulesHTTP monitor with Host + recv string; Policy before iRuleICMP as 'the app is up'
6 HADevice Trust → Device Group → ConfigSync → traffic groupAutomatic Sync from a dirty box
7 TroubleshootProblem statement, last-known-good, tcpdump both sidesChanging config as step 1

M1 · Fundamentals & admin

Open the lesson →

M2 · Networking & traffic flow

Open the lesson →

M3 · Virtual Servers & pools

Open the lesson →

M4 · Profiles, SNAT, SSL

Open the lesson →

M5 · Monitors, iRules, policies

Open the lesson →

M6 · High availability

Open the lesson →

M7 · Troubleshooting

Open the lesson →

Shared lab numbers

Every runbook on this series uses documentation-range addresses so you can copy without leaking a customer network.

ObjectValueWhere you see it
Management IP192.168.100.10System > Platform
External VLAN / Self IP192.0.2.0/24 · 192.0.2.10Network > VLANs / Self IPs
Internal VLAN / Self IP10.20.20.0/24 · 10.20.20.10Network > Self IPs
VIP192.0.2.100:443Local Traffic > Virtual Servers
Pool members10.20.20.101–103:443Local Traffic > Pools
Client198.51.100.50tcpdump host filter

How a request actually runs

Flow 2 · runtime after Module 3
DNSwww → VIPVS matchIP+port+VLANProfilesTCP/HTTP/SSLPoolhealthy memberReturnvia SNAT/ALH

If any box is red in production, stop there. Do not skip layers.

Ops · prove it
Operations desk with abstract health tiles
Green tiles are not a feeling. They are tmsh show ltm pool, monitor status, and a packet that came back.

Series-wide traps

TrapWhat you seeFirst proof
Mgmt IP used as VIPGUI works, app users cannot connectVIP is a Virtual Server destination, not System > Platform
VLAN tag mismatchInterface up, no ARP, no VS statsSwitch/port-group tag must match BIG-IP tagged/untagged
No-SNAT + wrong gatewayClient SYN in, no server-side SYN-ACKtcpdump both VLANs; then SNAT Automap or fix server default gateway
ICMP monitor onlyPool green, HTTP 500 to usersHTTP monitor with Host header and a known recv string
Change first, capture laterNew bug plus the original bugWrite the problem statement. Then capture.
Pilot checklist

Knowledge check

These six questions span the whole recorded course. Miss one → open that module.

Q1

What processes application traffic on BIG-IP?

Correct: b. Module 1: TMM is the data plane. MCPD is config. Re-read mental model.
Q2

Port Lockdown Allow Default limits which traffic?

Correct: b. Module 2: Port Lockdown is not a VS filter.
Q3

A pool member is best described as:

Correct: b. Module 3 hierarchy.
Q4

Cookie persistence on SSL passthrough will:

Correct: b. Module 4: passthrough has no HTTP profile.
Q5

First health check for a vhosted web app should be:

Correct: c. Module 5.
Q6

First troubleshooting step in an incident is:

Correct: b. Module 7: do not start by changing config.

Sources

Related: Course hub · Syllabus · My Courses · F5 LTM interview