BIG-IP Administration Support and Troubleshooting (F5CAB5)

When a BIG-IP slows down or a virtual server stops passing traffic, application uptime is on the line — and the fix too often depends on one senior engineer or an escalation to the vendor. This course gives network support engineers, technical operations staff, and system administrators a repeatable troubleshooting workflow. The workflow covers four areas:

• Resource baselining: documenting what normal resource use looks like and telling control plane activity apart from data plane activity.
• Performance checks: ruling out license throughput limits and interface errors.
• Packet captures: using tcpdump correctly, including turning off PVA acceleration so traffic can actually be captured.
• Load balancing and pools: verifying persistence profiles and confirming the chosen load balancing method fits the environment.

Role fit: This course is best for practitioners who already administer BIG-IP day to day. It maps to the F5CAB5 exam toward the F5 Certified Administrator, BIG-IP credential.

Time investment: About 5.2 hours across six skills. Team Leads can realistically assign it over one to two weeks alongside normal duties.

Upgrade readiness and support escalation: The upgrade content emphasizes pre-upgrade checks, including creating a BIG-IP Archive backup and confirming the current version before making changes. The course also covers confirming BIG-IP functionality by reviewing statistics in the web UI and terminal. The final skill covers when and how to open a support case, so escalations arrive with useful diagnostics.

How CBT Nuggets supports the outcome: Each skill ends with validation questions that reinforce exam readiness. Training Managers can group this course into Playlists with related F5CAB courses and track progress through Team Reporting.

When an application slows down or a virtual server stops passing traffic, your team needs a repeatable process instead of guesswork. This course gives IT Practitioners a structured BIG-IP troubleshooting workflow built on scenarios drawn from day-to-day operations.

For example, when users report slowness, your team learns to check performance stats, inspect interfaces for RX/TX errors, confirm license throughput limits, and look for core files before escalating. When a user can't connect, they learn to filter a tcpdump capture by the client's IP address and read a reset response to identify when a service isn't running on the destination.

• Faster root-cause isolation: Team members learn to separate control plane from data plane CPU usage with the top command and compare results against a documented baseline of normal utilization.
• Fewer misdiagnosed load balancing issues: Engineers learn to verify rate and connection limits, identify which virtual servers and pool members are affected, and review configurations that may need to change to improve load balancing services.
• Reliable packet captures: Staff learn tcpdump options such as capturing on all interfaces (0:0) and limiting packet counts (-c), and learn to set PVA Acceleration to none so accelerated Fast L4 traffic can be captured.
• Lower-risk upgrades: Teams learn to schedule maintenance windows, reactivate licenses before upgrading, and install to a separate volume.

The result for IT Directors is less downtime, cleaner escalations, and engineers who can resolve common BIG-IP issues before opening a support case.

Knowledge

• How BIG-IP separates control plane and data plane activity, and why that distinction matters when troubleshooting resource constraints
• Why documenting a performance baseline at deployment, and again as users are added, is essential for spotting abnormal utilization
• The limitations of tcpdump on BIG-IP, including why traffic fully accelerated by the ePVA chip (such as with Fast L4) is not captured unless PVA Acceleration is set to none
• How load balancing method choice, persistence profiles (default vs. fallback), and virtual server types such as Performance HTTP affect application behavior
• How platform lifecycle, software versioning, documented software and disk information, and current backups support upgrade planning and help minimize downtime

Ability

• Use the top command and BIG-IP performance statistics to identify which processes, such as TMM, Java, or mysqld, are consuming CPU and memory
• Run targeted packet captures with tcpdump, filtering by client IP and capturing on the 0:0 interface when appropriate
• Work through a structured slowness checklist: review performance stats, check interfaces for status and RX/TX errors, verify license throughput limits, and look for core files
• Diagnose why virtual servers and pools are not passing traffic, including interpreting resets that indicate a service isn't running on the destination
• Prepare for a BIG-IP upgrade by creating and downloading a backup archive, documenting software and disk information, and confirming functionality afterward through the web UI and terminal
• Gather the right diagnostic evidence before opening an F5 support case