F5 rSeries CPU and TMM Report

The F5 rSeries CPU and TMM Report workflow automatically fetches all F5 rSeries host devices and collects CPU and Traffic Management Module (TMM) memory utilization metrics. This report enables centralized monitoring of F5 rSeries device health through a consolidated tabular view.

Overview

The F5 rSeries CPU and TMM Report is a predefined workflow designed to provide comprehensive health monitoring for F5 rSeries host devices. By automatically collecting CPU and memory utilization data, this report helps operations teams track device performance, identify resource constraints, and plan capacity expansion.

Key benefits of the F5 rSeries CPU and TMM Report include:

  • Automated collection of CPU and TMM memory metrics from all F5 rSeries devices
  • Centralized tabular view for easy analysis and comparison
  • Real-time health monitoring of F5 rSeries infrastructure
  • Historical trending for capacity planning and forecasting
  • Identification of resource bottlenecks and performance issues
  • Support for scheduled automated execution
  • Executive-friendly reporting for stakeholder communication

Report Metrics and Data

The F5 rSeries CPU and TMM Report collects and displays the following metrics for each F5 rSeries host device:

CPU Utilization

Description: The percentage of CPU resources currently in use by the F5 rSeries host device. This metric reflects the total processing load across all CPU cores.

TMM Memory Utilization

Description: The percentage of Traffic Management Module memory currently in use. TMM handles all traffic processing and application delivery functions.

Accessing the F5 rSeries CPU and TMM Report

To access and run the F5 rSeries CPU and TMM Report workflow:

  1. Log into the AppViewX application with valid credentials.
  2. Go to Menu > ADC > AUTOMATION > Workflow Catalog > View/Run.
  3. Select F5 rSeries CPU and TMM Report from the workflow list
  4. Provide a name and description for the report request
  5. Configure schedule settings if desired (or leave for immediate execution)
  6. Click Submit to create the report request

Prerequisites for Report Execution

For the F5 rSeries CPU and TMM Report to execute successfully, ensure:

  • At least one F5 rSeries host device is onboarded in ADC inventory
  • F5 rSeries devices are reachable and accessible from AppViewX
  • Network connectivity exists between AppViewX and rSeries devices
  • RESTCONF API is enabled on F5 rSeries devices for data collection
  • Valid credentials are configured for rSeries device access
  • Firewall rules allow AppViewX to communicate with rSeries management interface (typically port 8888)
  • User role has permissions to run ADC+ workflows
Important: If no F5 rSeries host devices are available in the inventory, the workflow will fail with an error message: "No F5 rSeries devices available in the inventory"

Report Output and Display

The F5 rSeries CPU and TMM Report generates output in the following formats:

Tabular View

The primary output is a tabular view displaying all collected metrics for each F5 rSeries device:

F5 rSeries Device CPU Utilization (%) TMM Memory (%) Collection Status Timestamp
rSeries-Device-1 (192.168.1.10) 45.2 62.8 Success 2026-04-29 12:30:15 UTC
rSeries-Device-2 (192.168.1.11) 78.5 81.3 Success 2026-04-29 12:30:16 UTC

Drill-Down Capability

Click on any device row to access detailed information:

  • Per-core CPU utilization breakdown
  • Memory allocation details (used/available/total)
  • Historical trend data if available
  • Related device configuration and settings

Scheduling Recurring Reports

The F5 rSeries CPU and TMM Report supports automated scheduling for regular health monitoring:

  • One-time Execution: Run the report immediately without scheduling
  • Daily: Execute the report every day at a specified time
  • Weekly: Run on specific days each week (e.g., every Monday at 8:00 AM)
  • Monthly: Execute on specific dates each month
  • Custom: Define complex recurring schedules using cron expressions

Recommended scheduling intervals depend on your monitoring needs:

  • Production Environments: Daily or multiple times per week for continuous monitoring
  • Development/Test: Weekly unless troubleshooting specific issues
  • Capacity Planning: Bi-weekly or monthly for trend analysis

Interpreting Report Results

High CPU Utilization (>85%)

Indication: The F5 rSeries device is processing at elevated CPU levels, potentially indicating traffic surges or configuration issues.

Actions to Consider:

  • Investigate active virtual services and traffic patterns
  • Review traffic processing policies for inefficiencies
  • Check for runaway processes or memory leaks
  • Plan for load balancing across additional rSeries devices if sustained
  • Contact F5 support if elevated levels persist unexpectedly

High TMM Memory Utilization (>85%)

Indication: The Traffic Management Module is running with limited available memory, which could impact performance and stability.

Actions to Consider:

  • Review active connections and persistence settings
  • Audit virtual services for excessive memory consumption
  • Check for memory allocation issues in pool configurations
  • Consider upgrading rSeries device memory if needed
  • Implement connection limits or throttling if not already configured

Metric Collection Failures

Indication: The workflow might not collect metrics from one or more F5 rSeries devices.

Possible Causes:

  • Network connectivity issues between AppViewX and rSeries device
  • RESTCONF API not responding or disabled on device
  • Expired or invalid credentials for device access
  • Firewall blocking communication on management port (8888)
  • rSeries device offline or unreachable