BIG-IP R4600

BIG-IP R4600 is the base performance tier of the F5 r4000 Series, designed for application delivery and security environments that have outgrown smaller r2000 appliances but do not yet require the density of r5000 or higher platforms. It provides more CPU and memory for BIG-IP workloads, supports limited multi-tenancy, and retains a compact 1RU footprint.

The underlying r4000 hardware contains 16 physical CPU cores, but the R4600 license makes 12 cores available to BIG-IP tenants. The same chassis can later operate as an R4800 after a Pay-as-you-Grow license upgrade unlocks the remaining capacity. That gives buyers a useful middle ground: deploy enough performance for the current project while keeping an upgrade path inside the same hardware platform.

Series Highlights

• Base performance tier of the F5 r4000 Series
• 1RU physical application delivery platform
• 12 CPU cores available for BIG-IP workloads
• 64 GB system memory
• 48 GB memory reserved for tenants
• Supports up to two BIG-IP tenants
• Four 1G/10G/25G optical interfaces
• 480 GB M.2 SSD storage

BIG-IP R4600 At a glance

What it is: Mid-range F5 r4000 Series application delivery and security appliance

Product family: BIG-IP rSeries License

Platform: F5OS with BIG-IP tenant architecture

CPU capacity: 12 cores available to tenants

System memory: 64 GB

Memory for tenants: 48 GB

Tenant capacity: Up to two

Storage: 480 GB M.2 SSD

Interfaces: Four 1G/10G RJ45 plus four 1G/10G/25G SFP/SFP+/SFP28 ports

Series Overview

BIG-IP R4600 uses the same physical r4000 appliance as R4800. The platform contains 16 CPU cores with no hyperthreading and does not reserve dedicated cores exclusively for the F5OS platform layer. On R4600, four of those cores are disabled by licensing, leaving 12 available for tenant workloads.

That additional capacity is a meaningful step above the r2000 family. R4600 also doubles system memory to 64 GB and reserves 48 GB for tenants. F5 currently supports a maximum of two tenants on the model, with a minimum allocation of four CPU cores and 12 GB of memory per tenant.

The physical interface layout remains flexible rather than unusually dense: four copper ports can operate at 1G or 10G, while four SFP28 ports support 1G, 10G, or 25G optics.

Licensing and Part Number Guidance

The R4600 hardware designation only describes the platform capacity. The final order must also reflect which BIG-IP services are required. One deployment may primarily use BIG-IP License services such as LTM for load balancing, health monitoring, persistence, and SSL handling. Another may combine application delivery with Advanced WAF, DNS, AFM, APM, or other supported BIG-IP services. F5 offers multiple BIG-IP service families, so the appliance SKU and software entitlement should be sized together rather than independently.

The other major decision is whether R4600 leaves enough headroom. Because R4600 and R4800 use the same r4000 hardware, an eligible PAYG license upgrade can unlock the remaining CPU resources and move the platform to R4800 capacity without replacing the appliance. If utilization is expected to approach the R4600 ceiling soon after deployment, comparing the initial R4800 price can be more sensible than planning an early upgrade.

Common Use Cases

F5 recommends building redundancy between corresponding BIG-IP tenants on separate rSeries appliances; the F5OS platforms themselves do not form an HA pair.

Models, Licenses, and Ordering Scope

What to Check Before Requesting a Quote

Do not select R4600 only from a headline throughput requirement. Start with the applications and services behind it. Confirm peak traffic, TLS volume, concurrent connections, security inspection, required BIG-IP modules, interface speeds, tenant separation, and expected growth. A deployment running LTM alone can place a very different load on the platform from one combining LTM with application-security processing.

If this is a refresh, include the existing F5 model and licensed modules. rSeries is F5’s current appliance architecture replacing iSeries, but moving from an old i4600 or another appliance should be based on real workload measurements rather than model-name similarity.

Activation and Delivery Notes

Licensing and network resources are managed at the F5OS platform layer. BIG-IP tenants inherit capabilities such as the system license and assigned VLANs, so a separate platform license should not be installed directly inside each tenant.

After basic platform networking and licensing are configured, the required BIG-IP tenant image can be deployed, CPU and memory assigned, and application-level services configured inside the tenant. F5’s current setup workflow separates system configuration from tenant configuration for this reason.

Before shipment, confirm software entitlement, optics, power supplies, HA quantity, support, and whether the initial design should leave room for a future PAYG upgrade.

Related F5 Categories

BIG-IP R4600 belongs to the BIG-IP rSeries License family. A smaller deployment may be better served by BIG-IP R2800, especially where one primary workload and lower CPU demand are expected. If the project needs all 16 r4000 CPU cores or more tenant flexibility, compare BIG-IP R4800. For environments requiring substantially higher tenant density, more memory, or broader consolidation, the r5000 Series represents the next meaningful platform step rather than simply adding more r4000 appliances.