BIG-IP Administration Install, Initial Configuration, and Upgrade (F5CAB1)

For IT leaders: BIG-IP sits in front of the applications your business depends on, so a botched upgrade, a misconfigured management IP, or an unlicensed module can quickly become a customer-facing outage. This course gives network administrators, system engineers, and DevOps practitioners a shared, repeatable baseline for installing, securing, and upgrading BIG-IP. It also supports preparation for the F5CAB1 exam.

Role fit: This course is best for practitioners who already have networking fundamentals and now administer or will soon inherit F5 infrastructure. Team Leads can use it to standardize how staff handle module provisioning and licensing, console-based recovery when management access fails, End User Diagnostics, and UCS and software image management.

Risk and change management: The upgrade content walks through a documented process for HA pairs:

• Sync the devices.
• Review virtual servers, pools, and iRules.
• Generate a QKView for iHealth analysis.
• Force the active unit to standby.
• Test connections before you continue, and fail back if needed.

That sequence maps directly to change-control and maintenance-window practices that reduce upgrade risk.

Time investment: Plan for about 5.2 hours per learner across six skills. Budget extra time for the hands-on lab build.

How CBT Nuggets supports the outcome: Learners build their own BIG-IP Virtual Edition lab on ESXi, VMware Workstation, or Hyper-V, with web servers behind it. That lab gives them practice without touching production. Validation challenges reinforce each skill. Team Reporting lets Training Managers track course progress across the team.

IT teams use this training to run BIG-IP changes with less risk and recover faster when something breaks. The scenarios come straight from day-to-day F5 administration: an unreachable management IP, a hardware health check before opening a support case, and a software upgrade on a production HA pair.

• Safer upgrades on HA pairs: Your team will follow a step-by-step process for deploying a new software image. They review virtual servers, pools, and iRules after the upgrade, then generate a QKView for iHealth analysis. Next, they force the active unit to standby and test connections, with a clear fail-back path if checks fail. The result is fewer change-window outages.
• Faster recovery from lockouts: When the management IP gives no response over the browser or SSH, practitioners know to connect through the console port. From there, they open the host subsystem and use TMSH to confirm the management address hasn't been misconfigured.
• Better user experience during failures: Admins validate user-facing failure behavior and document what users see when an application path breaks, making it easier to distinguish expected failover behavior from raw errors that need troubleshooting.
• Quicker, better-documented support cases: Your team will run End User Diagnostics from the EUD menu and document the diagnostic results. They also check module provisioning and licensing status, then use iHealth and DevCentral before they escalate to F5.

Learners build and practice these tasks in a BIG-IP Virtual Edition lab, so your team can rehearse changes without touching production.

Knowledge

• How a BIG-IP lab topology is structured across external, internal, and management networks, and how BIG-IP Virtual Edition deploys in VMware, Hyper-V, or other virtualized environments
• What application objects are, and how virtual servers, pools, load balancing, and fallback hosts with HTTP redirection keep applications available to users
• How module provisioning differs from licensing, and how to review CPU, memory, and disk use by provisioned module
• The role of F5 support resources: DevCentral for community knowledge, iHealth for QKView analysis, and End User Diagnostics (EUD) for hardware testing
• The sequence for upgrading an HA pair safely, including config review, QKView checks, failover, and connection testing

Ability

• Build a working BIG-IP virtual lab with back-end web servers to safely practice configuration and upgrade tasks
• Connect to the BIG-IP Configuration utility through the management interface and verify management connectivity during lab deployment
• Review module provisioning and resource use from the resource provisioning page, and spot modules that are provisioned but not licensed
• Run EUD tests from the console, read pass and fail results, and keep records from shared/log/eud.log
• Sync an HA pair, force the active unit to standby, and validate traffic before continuing a software upgrade, which lowers the risk of downtime
• Generate a QKView file and upload it to iHealth to check system health before and after changes