BIG-IP R5800

BIG-IP R5800 is the middle performance tier of the F5 r5000 Series, designed for enterprise application delivery and security environments that need more compute capacity than R5600 without immediately moving to the fully enabled R5900. The platform combines 128 GB of system memory, high-speed 25G and 100G networking, FPGA-assisted processing, and flexible BIG-IP tenant allocation in a 1RU appliance.

R5800 is especially relevant where several application or security workloads need to share one physical F5 system. Its license makes 18 vCPUs available to BIG-IP tenants, compared with 12 on R5600. Because all three r5000 tiers share the same underlying hardware, an existing R5800 can later move to R5900 through F5 Pay-as-you-Grow licensing rather than a chassis replacement.

Series Highlights

• Mid-level performance tier of the F5 r5000 Series
• 1RU physical BIG-IP appliance
• 18 vCPUs available for tenant workloads
• 128 GB system memory
• 108 GB memory reserved for BIG-IP tenants
• Supports up to 18 tenants depending on tenant sizing
• Eight 10G/25G SFP+/SFP28 interfaces
• Two 40G/100G QSFP+/QSFP28 interfaces
• 960 GB M.2 SSD storage

BIG-IP R5800 At a glance

What it is: Mid-tier F5 r5000 Series application delivery and security appliance

Product family: BIG-IP rSeries License

Platform layer: F5OS

Tenant compute capacity: Up to 18 vCPUs

System memory: 128 GB

Memory reserved for tenants: 108 GB

Maximum tenant count: Up to 18, depending on tenant image and resource allocation

Storage: 960 GB M.2 SSD

Interfaces: Eight 10G/25G ports plus two 40G/100G ports

Typical role: Enterprise ADC, application security, SSL/TLS processing, DNS, access, and multi-tenant BIG-IP consolidation

Series Overview

The r5000 hardware contains a 16-core Intel Xeon processor presented as 32 logical vCPUs through hyperthreading. Six vCPUs are reserved for the F5OS platform layer. On R5800, eight additional vCPUs are disabled by licensing, leaving 18 vCPUs available for tenant workloads. R5900 unlocks the full 26 tenant vCPUs available after the F5OS reservation.

That positioning makes R5800 a useful consolidation platform. Compute can be assigned to one larger tenant or divided among several BIG-IP instances according to the workload. F5 currently lists a theoretical maximum of 18 tenants on R5800, but that figure assumes minimum-sized tenants. F5 specifically cautions that single-vCPU tenants are intended only for very light LTM or DNS workloads and are not the preferred design for most production environments.

Network capacity is unchanged across the standard r5000 hardware platform: eight 10G/25G optical interfaces and two 40G/100G ports provide substantially more high-speed connectivity than the r4000 family.

Licensing and Part Number Guidance

The R5800 model determines available platform compute, but the final order must also account for the BIG-IP License services that will run on the appliance.Traffic management, application security, DNS, access, network security, support, optics, and redundancy can all affect the final ordering scope.

The other decision is where to enter the r5000 PAYG ladder. R5600, R5800, and R5900 use the same physical hardware. F5 allows R5600 to move to either R5800 or R5900, while an R5800 can later be upgraded to R5900 through a license change.

For a workload that already requires considerably more than 12 vCPUs, R5800 can avoid undersizing the initial deployment. If usage is already approaching 18 vCPUs, however, R5900 should be priced at the same time rather than planning an immediate second upgrade.

Common Use Cases

The r5000 architecture also uses FPGA hardware acceleration for functions such as selected traffic-processing and DDoS-related workloads, differentiating it from the smaller r2000/r4000 platforms.

Models, Licenses, and Ordering Scope

F5 currently offers the r5000 hardware with AC, standard DC, and supported HVDC configurations, so power should be treated as an ordering requirement rather than an afterthought.

What to Check Before Requesting a Quote

Start by identifying what each BIG-IP tenant will actually do. An 18-vCPU R5800 running one large LTM and Advanced WAF workload is very different from an appliance split across several smaller DNS, LTM, access, or security instances.

Provide expected traffic, SSL/TLS volume, security inspection, tenant count, BIG-IP modules, interface speeds, HA requirements, and anticipated growth. Tenant image type also matters because F5 offers lightweight and multi-module images with different CPU, memory, and disk requirements. Current documentation recommends sizing tenants around the actual workload rather than maximizing the theoretical tenant count.

If R5800 would begin production with most of its 18 available vCPUs already committed, compare R5900 before placing the order. The extra headroom may be commercially cleaner than consuming the remaining PAYG step shortly after deployment.

Activation and Delivery Notes

R5800 is licensed and configured first at the F5OS platform layer. Tenants inherit capabilities such as the platform license, VLAN access, and selected management properties from the system; F5 advises against installing or removing the platform license from inside an individual tenant.

During deployment, administrators import the appropriate BIG-IP tenant image, allocate vCPU and memory, assign VLANs, and then place the tenant into its deployed state. Each tenant receives dedicated compute resources and can be managed independently through its own web interface, CLI, or API. Before delivery, confirm the BIG-IP entitlement, R5800 performance tier, tenant allocation, optics, power configuration, support, and HA quantity. An R5800-to-R5900 PAYG upgrade can later unlock additional compute on the same r5000 hardware.