BIG-IP R2600

BIG-IP R2600 is the entry performance tier of the F5 r2000 Series, built for organizations that need dedicated BIG-IP application delivery and security on current rSeries hardware without stepping into a larger multi-tenant appliance. It fits smaller and mid-sized application environments where load balancing, SSL/TLS processing, application security, access control, DNS, or network protection need to run on a physical F5 platform.

The R2600 uses the same underlying r2000 hardware architecture as the r2800, but its available processing capacity is controlled by licensing. This is an important buying detail: an organization can start with an r2600 and later unlock r2800 performance through F5 Pay-as-you-Grow licensing instead of replacing the appliance.

Series Highlights

• Entry performance tier within the F5 r2000 Series
• 1RU physical BIG-IP appliance
• Four licensed CPU cores available to its BIG-IP tenant
• Supports one BIG-IP tenant
• 32 GB system memory and 480 GB SSD storage
• 1G, 10G, and 25G interface support
• Runs BIG-IP services through the F5OS platform architecture
• Upgradeable from r2600 to r2800 through Pay-as-you-Grow licensing

BIG-IP R2600 At a glance

What it is: Entry-level F5 r2000 Series application delivery and security appliance

Product family: BIG-IP rSeries License

Platform software: F5OS

Tenant capacity: One BIG-IP tenant with up to four CPU cores

System memory: 32 GB

Storage: 480 GB M.2 SSD

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

Typical use: Application delivery, load balancing, SSL offload, WAF, DNS, access services, and smaller physical ADC environments

Series Overview

The BIG-IP R2600 belongs to F5’s current rSeries hardware architecture. The physical r2000 chassis contains an eight-core Intel Atom processor, 32 GB of memory, a 480 GB SSD, four optical ports capable of 1G/10G/25G operation, and four copper 1G/10G ports. It is a compact 1RU system suited to environments where a dedicated physical appliance is preferred over BIG-IP Virtual Edition.

What distinguishes r2600 from r2800 is primarily the licensed processing capacity. On r2600, four of the eight physical CPU cores are available to the BIG-IP tenant; r2800 unlocks all eight. The r2600 supports one tenant, with F5 currently documenting four CPU cores and 24 GB of memory reserved for tenant use.

This makes R2600 a practical starting point when present traffic requirements are moderate but some growth is expected.

Licensing and Part Number Guidance

Ordering BIG-IP R2600 requires more than choosing the appliance chassis. The part number also needs to reflect the BIG-IP services required by the application environment.

An LTM-focused deployment may need traffic management and SSL services, while another R2600 may be ordered for Advanced WAF, Access Policy Manager, DNS, or a broader application-security requirement within the BIG-IP License portfolio. F5 replacement mappings also show product-specific r2600 SKUs for different BIG-IP service families rather than one universal r2600 part number.

The other important license decision is capacity. F5’s Pay-as-you-Grow (PAYG) model allows an r2600 to be upgraded to r2800 by changing the license and unlocking the remaining CPU resources. The underlying r2000 hardware does not need to be replaced.

For buyers expecting substantial growth, comparing the cost of an R2600 plus a future PAYG upgrade against ordering r2800 from the beginning is worthwhile.

Common Use Cases

Models, Licenses, and Ordering Scope

What to Check Before Requesting a Quote

Start with the application rather than the SKU. Confirm what BIG-IP must actually do: basic load balancing, TLS termination, Advanced WAF, remote or application access, DNS, firewalling, or several services together.

Then estimate normal and peak traffic, SSL demand, interface speeds, HA requirements, and expected growth. If the environment already runs an iSeries or older BIG-IP appliance, include its model, licensed modules, current traffic, and software version. F5 specifically positions rSeries as its newer application delivery hardware architecture and provides migration paths from previous platforms.

This information makes it much easier to determine whether R2600 is sufficient or whether r2800 or a larger rSeries platform is the better purchase.

Activation and Delivery Notes

The appliance is licensed at the F5OS system layer. BIG-IP tenants inherit licensing and other platform capabilities from the system, so administrators should not attempt to install a separate platform license directly inside the tenant. Before delivery, confirm the exact service bundle, power configuration, optics, support coverage, and whether one or two appliances are required. After platform activation, the compatible BIG-IP tenant image is deployed and assigned the available r2600 resources. If a future PAYG upgrade is purchased, licensing can unlock the additional processing capacity required to move the platform from r2600 to r2800 performance.

Related F5 Categories

BIG-IP R2600 sits under the BIG-IP rSeries License family. Buyers who need the same r2000 hardware with greater available processing capacity should compare BIG-IP R2800. Larger workloads, higher tenant counts, or more consolidation may require the r4000, r5000, or higher rSeries families. For organizations still operating iSeries appliances, the broader BIG-IP rSeries category is also useful when planning a hardware refresh rather than selecting a replacement only by matching the old model number.