# F5 LTM Module 1 fundamentals & device admin

Source: https://ai.techclick.in/blog_f5_ltm_module_1_fundamentals
Markdown: https://ai.techclick.in/blog_f5_ltm_module_1_fundamentals.md
Publisher: Techclick Infosec Pvt Ltd

Learn BIG-IP planes (management, control, TMM), Management IP vs Self IP vs VIP, TMSH, licensing, resource provisioning, and UCS backup.

Lessons  ·  F5 LTM series  · Module 1

   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 .

- Hub · Course map
- M1 · Fundamentals & admin ← you are here
- M2 · Networking & traffic flow
- M3 · Virtual Servers & pools
- M4 · Profiles, SNAT, SSL
- M5 · Monitors, iRules, policies
- M6 · High availability
- M7 · Troubleshooting
     Next → M2 · Networking & traffic flow

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

## The ticket that starts every F5 career

 Night shift: “The new BIG-IP is licensed. GUI opens. Nobody can publish an application.” The trap is treating BIG-IP like a Linux router with a pretty web UI. It is not. Application traffic never uses the Linux kernel stack. It uses TMM.

   Hero · three planes

   Three planes, three jobs. Mix them and you will put a VIP on the management NIC.

  Quick answer

  TMM  processes application traffic.  MCPD  validates and pushes configuration. The  Management IP  is out-of-band admin only. License, then provision LTM, then save to disk, then take a UCS. Config in memory is not a backup.

  Say this out loud

 Provision puts CPU and RAM on a licensed module. Licensing without provisioning leaves LTM dark. Saving config writes memory to disk. UCS is the restore image — including keys.

## Mental model: ADC, TMOS, TMM, MCPD

 A traditional Layer-4 load balancer forwards on IP and port. An Application Delivery Controller (ADC) works at Layers 4–7: SSL, HTTP, persistence, health, iRules. F5 BIG-IP LTM is that ADC. Physical appliances, Virtual Edition on ESXi/KVM/Hyper-V, and public-cloud images all run the same TMOS idea.

   Flow 1 · who does what

       Flow 1 · who does what

- Admin GUI / TMSH MCPD validate + DB Config DB bigip.conf TMM data plane Admin input never becomes a packet. MCPD writes the config DB; TMM applies it to live traffic. TMOS (Traffic Management Operating System) is the glue: Linux host + TMM + MCPD + GUI + TMSH. The Linux host gives you Bash and files. It does not load-balance HTTPS. Interview line from the PDF: “What processes application traffic — TMM or MCPD?” Answer: TMM. Plane Interface / IP Carries Management mgmt NIC · Management IP e.g. 192.168.100.10 HTTPS GUI, SSH, iControl REST, licensing Control / config MCPD + config DB Object create/modify, HA sync of config Data Self IPs + VIPs on VLANs Client ↔ TMM ↔ pool member ## Management IP vs Self IP vs VIP Management IP Self IP Virtual IP Purpose Admin the box BIG-IP's own address on a VLAN Client-facing listener GUI path System > Platform Network > Self IPs Local Traffic > Virtual Servers App traffic? No Yes (TMM) Yes (VS match) HA Not the floating app IP Floating Self IP moves with traffic group VIP floats with the same group Common mistake Never use a Self IP as the client-facing application address. Never route production traffic through mgmt. Module 2 builds the VLANs; this module only locks the names. ## Runbook — first-day device ### Side A · platform #### Hostname, DNS, NTP, time zone GUI: System > Platform. Skip NTP and SSL certificates, HA timers, and log correlation all lie. This is the number-one first-day miss in the Module 1 PDF.
- #### Management IP + route Set mgmt address, mask, and management default route so https://192.168.100.10 and SSH work from the admin laptop. This path is out-of-band.
- #### Admin password Change default admin immediately. Prefer TMSH over raw Bash for config — MCPD must own the files.

     https://192.168.100.10/tmui/Control/jspmap/tmui/system/license/list

     Training mock · not live

       System > License

### License

        Registration key  XXXXX-XXXXX-XXXXX-XXXXX-XXXXXXX

  Activation  Automatic (internet) or manual/offline

  Status  Active · LTM licensed

  TMSH  tmsh show sys license

        Cancel  Finished

   Source: F5 ltm module 1.pdf · GUI path System > License. Never bypass licensing.

### Side B · license then provision

 A Registration Key activates modules. After license, you still must provision. Provisioning allocates CPU, memory, and disk among licensed modules.

     Level  Meaning  When      None  No resources  Licensed but not needed on this box    Minimum  Small allocation  Lab / light auxiliary module    Nominal  Balanced  Typical production LTM    Dedicated  Maximum; other modules squeezed  One module must win

     https://192.168.100.10/tmui/Control/jspmap/tmui/system/provision

     Training mock · not live

       System > Resource Provisioning

### Resource Provisioning

        LTM  Nominal

  DNS / APM / AFM / WAF  None — unless this chassis is supposed to run them

  TMSH  tmsh show sys provision

        Cancel  Finished

   PDF trap: provisioning APM/AFM/WAF on an LTM-only box steals TMM memory.

### Side C · save and UCS

 GUI and TMSH changes are live in memory. Reboot without save and they vanish. UCS is the disaster-recovery archive: config, certs/keys, users, license.

  TMSH · save + UCS  tmsh save sys config
tmsh save sys ucs /var/local/ucs/backup-$(date +%Y%m%d).ucs
tmsh list sys ucs
# restore is destructive — lab first
# tmsh load sys ucs /var/local/ucs/backup-20240101.ucs

 GUI: System > Archives → Create. Store the file off-box. Restoring onto different hardware may need platform-migrate / no-license flags — test in lab. Source:  BIG-IP Archives .

   Journey · license to UCS

   Order is the runbook: license → provision → configure later modules → save → UCS. Reverse it and you restore an empty box.

## Access methods

     Method  Use  Avoid      GUI HTTPS  Day-to-day objects, first setup  Using it as the only skill in an outage    SSH + TMSH  Show/list/modify, scripts  Editing bigip.conf in vi    Bash  Logs, tcpdump, files  Unsupported config file edits that MCPD cannot track

  First-level health  tmsh show sys license
tmsh show sys provision
tmsh show sys performance all-stats
tmsh show sys memory
tmsh show ltm virtual
tmsh show net self

   Ops · first-level health

   If license is unhappy, Virtual Servers can go dark. Check this before rewriting pools.

## Traps + proof

     Failure  Symptom  Proof      No NTP  HA oddness, SSL time errors, unusable logs  System > Platform time vs NTP peer    Licensed but not provisioned  LTM objects missing or module inactive  tmsh show sys provision    Unsaved config  Changes gone after reboot  tmsh save sys config after every real change    UCS only on the box  Disk dies, backup dies  Copy UCS off-box the same day    Bash-edited conf  MCPD / TMM disagree  Use TMSH/GUI; reload from known UCS

  You are done with Module 1 when

- You can draw mgmt vs Self IP vs VIP on a whiteboard.

- tmsh show sys license and tmsh show sys provision both look sane.

- A dated UCS file exists off the device.

## Knowledge check

   Judgment items from Module 1 — planes, license, save, UCS.

   Q1
   Application HTTPS is processed by:

      MCPD     Bash iptables     TMM     The mgmt NIC

   Correct:  c . TMM is the data plane.

   Q2
   Where do you set the Management IP?

      Network > Self IPs     Local Traffic > Virtual Servers     System > Platform     Local Traffic > Nodes

   Correct:  c . System > Platform / setup utility.

   Q3
   Licensed but LTM objects unavailable. First check:

      tcpdump     tmsh show sys provision     Delete UCS     Enable Allow All

   Correct:  b . Provision after license.

   Q4
   GUI change vanished after reboot. Cause:

      TMM crash only     Config was not saved to disk     Port Lockdown     No SNAT

   Correct:  b . tmsh save sys config.

   Q5
   A UCS archive includes:

      Running connections only     Config, keys, users, license     Just /var/log/ltm     Only the Management IP

   Correct:  b . Treat UCS as secret.

   Q6
   Preferred way to change BIG-IP objects:

      vi /config/bigip.conf     TMSH or GUI so MCPD tracks it     iptables     Editing in /tmp then reboot

   Correct:  b . Do not bypass MCPD.

       Check answers
       Reset

## Sources

- Techclick PDF: F5 ltm module 1.pdf (from OneDrive_1_8-26-2026.zip, 26 Aug 2026)

- Companion deck: F5-Ltm-Training-Ppt (1).pptx.pdf

- Archives: BIG-IP UCS archives

- Official lab paths: F5 cert Lab 1 — VLANs, Self IPs, pools, virtual servers

- TMSH virtual server reference: ltm virtual

- Related deep dives on this site: SSL modes · SNAT · Persistence · VS/pools · VIP down / tcpdump

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

---
Cite this Techclick lesson with the source URL. Do not invent fees, batch dates, or job guarantees.
Browse all lessons: https://ai.techclick.in/blogs
AI index: https://ai.techclick.in/llms.txt
