Quick Take
Quick Take: Buying rSeries on headline Gbps is how ADC projects end up short of SSL capacity. Size r2600 (~13 Gbps L7) through r5900 (~95 Gbps L7) and r10900 (~190 Gbps) against RSA TPS and F5OS tenants, not peak L4. F5-BIG-PEM-R5900 is a module SKU, not a chassis. Plan 14 days for quote lock; keep PDU under 80 percent.
rSeries Front Panel, Ports & Throughput
Quick Answer: Front-panel port density follows chassis class: r2600 and r2800 land in the 13 to 17 Gbps L7 class, r5600 through r5900 in the 60 to 95 Gbps class, and r10900 near 190 Gbps. SSL RSA TPS and F5OS tenants scale on the same ladder. Confirm optics, dual PSU, and F5OS on the official platform guide before you freeze the RFQ.
Performance figures follow F5 rSeries datasheets (peak / hardware-accelerated). Confirm software modules (LTM, ASM/AWAF, DNS, APM), F5OS version, and HA pair on the quote. Related: FortiADC F-Series, F5 price increase, SKU Lookup. Request a quote.
| Model class | L4 / L7 throughput (typ.) | SSL RSA 2k TPS (order) | Tenants (up to) |
|---|---|---|---|
| r2600 / r2800 | ~20/13 → ~25/17 Gbps | Low thousands–tens of K | 1 |
| r5600 / r5800 | ~95/60 → ~95/85 Gbps | ~tens–100K class | ~8–18 |
| r5900 | ~95/95 Gbps | ~100K class | ~26 |
| r10600 / r10800 | ~190/125 → ~190/145 Gbps | ~100–150K class | ~24–28 |
| r10900 | ~190/190 Gbps | ~200K class | ~36 |
| r12x00-DS (high density) | ~195 Gbps class | up to ~400K class | 50+ class |
Front-panel I/O follows the chassis class: r2600/r2800 are 1RU ADC edges, r5600/r5800/r5900 add denser 25/100 GbE options, and r10900/r12x00-DS land in the 190 Gbps class. Confirm SFP+/QSFP cages, dual-PSU airflow, and F5OS on the official platform guide — not a gray-market photo — before you freeze optics on the RFQ.
Exact TPS (RSA vs ECDHE-ECDSA) and compression/DDoS SYN-cookie rates vary by SKU — lock the datasheet row on the RFQ. VE / cloud instances are sized differently from appliances.
Overview
Quick Answer: Every rSeries box is a 1RU appliance running F5OS on the host with BIG-IP tenants layered above it, dual power supplies, and FPGA acceleration from the r5000 class upward. Consolidation is the point: several separate BIG-IP instances collapse into one chassis, provided the vCPU budget per tenant is planned.
F5OS & Tenancy
Quick Answer: F5OS holds back host vCPUs before anything is left for BIG-IP tenants, so tenant count and vCPU per tenant must be fixed before you pick a chassis tier. LTM, AWAF, APM, and DNS licenses sit on top of the hardware price, and an active standby pair needs both units quoted.
- Multi-tenancy densifies LTM / security / DNS workloads on one box
- HA typically active/standby pairs (or cluster designs per module)
- Migration from iSeries: expect higher SSL/ECC efficiency on rSeries
- Modules (LTM, AWAF, APM, DNS, etc.) are licensed separately from hardware
Use Cases
Quick Answer: Enterprise ADC refresh, SSL offload at scale, app security (AWAF), and multi-tenant service provider / shared enterprise edges. Map i5800-class → r5000-class and i10800-class → r10000-class, then validate with F5 sizing tools. r10800/r10900 when ECDHE TPS and L7 RPS dominate the BOM.
iSeries refresh
Map i5800-class → r5000-class and i10800-class → r10000-class, then validate with F5 sizing tools.
SSL / API gateway density
r10800/r10900 when ECDHE TPS and L7 RPS dominate the BOM.
Vs FortiADC
Fortinet-centric ADC path — see FortiADC F-Series.
Buying Checklist
Quick Answer: Fix the L7 throughput, request rate, and SSL transaction target under your real cipher mix first; that number picks the tier. Then add tenant count, the module bundle you actually license, a second unit for failover, transceivers, and the support entitlement, because those lines move the total as much as the tier choice.
- L7 Gbps, RPS, and SSL TPS (RSA + ECDHE)
- r2000 / r5000 / r10000 / denser DS tier
- Tenant count and vCPU per tenant
- LTM + security/DNS/APM module bundle
- Active/standby pair and sync networking
- Transceivers and dual PSU airflow
- F5 support / premium entitlements
Search F5 parts on SKU Lookup. Commercial context: June 2026 F5 price note.
How to Order an rSeries: Four Steps From Throughput to RFQ
Quick Answer: BIG-IP rSeries is a chassis-replacement appliance line running F5OS with tenant isolation, and the order path is four steps: size SSL transaction throughput before L4 Gbps, pick the tenant count, decide subscription term, then RFQ peer columns on identical meters. Sizing on headline L4 bandwidth alone is the classic overbuy.
Step 1 — Size on SSL, not headline bandwidth. The ladder runs from 7 Gbps-class entries to 95 Gbps and 190 Gbps platforms, but the number that decides real deployments is software or hardware SSL transactions per second at your certificate mix — quote that line explicitly. Step 2 — Count tenants, not just boxes. F5OS tenancy lets one appliance host isolated load-balancer tenants; freeze how many you need plus the management split. Step 3 — Choose subscription term deliberately. Perpetual versus multi-year subscription moves three-year cost more than the chassis tier does; price both before committing. Step 4 — RFQ matched columns. Submit one brief so r2000 against r5000-plus arrives on identical meters with dated lead times — plan for 14 to 35 business days door-to-dock, keep PDU circuits under 80 percent of rated draw, and hold both vendors to the same SLA lines before signing.
RFQ checklist before you PO
Quick Answer: Freeze model and option SKUs, support or subscription years, ship-by date, and HA or spare needs on one dated ATP before you compare channel prints. Use the checklist below, validate lines on SKU Lookup when the brand is indexed, then open a BOM risk RFQ — soft channel prices stay industry estimate or pending confirmation.
- Model / MPN lines — chassis and options matching this page (not a vague family name).
- Quantities + HA — single unit vs pair; spare FRUs if required.
- Support / subscription years — tier and term on the same quote as hardware.
- Ship-by / quote validity — lock reprice-until-ship language when memory or list cliffs apply.
- Acceptance — Service Tag / serials vs PO; reject surprise third-party parts without paperwork.
Which Part Numbers Should You Freeze on the RFQ (4 SKUs)?
Quick Answer: When quoting F5-BIG-LTM-R2600 and sibling configurations across these 4 part numbers, lock the exact base MPN, redundant power supplies, optics, and matching 1-year or 3-year support tier on separate lines before comparing vendor discounts. Channel net pricing remains industry estimate / pending confirmation.
| Ordering SKU | Key Configuration & Boundary | Adjacent BOM Lines to Freeze |
|---|---|---|
F5-BIG-LTM-R2600 | ~20/13 Gbps L4/L7, ~7K SSL TPS, 32 GB RAM, one tenant. LTM, support years, and HA as separate lines. | F5-BIG-LTM-R2600 ×2, F5OS-A train, STD vs PRE / L1-3 vs L3, SFP28 as drawn |
F5-BIG-LTM-R5900 | ~95/95 Gbps L4/L7, ~100K SSL TPS, 128 GB RAM, up to 26 tenants. Confirm dual PSU and modules. | F5-BIG-LTM-R5900 ×2, AWAF / APM / DNS as drawn, Second 650 W if required, STD vs PRE / L1-3 vs L3 |
F5-BIG-LTM-R10600 | ~190/125 Gbps L4/L7, ~115K SSL TPS, 256 GB RAM, 24 tenants, 16× 25G + 4× 100G, dual 1200 W, RAID-1. | F5-BIG-LTM-R10600 ×2, r10800 / r10900 if required, AWAF / APM / DNS as drawn, SFP28 / QSFP28 as drawn |
F5-BIG-BTA-R2800 | r2800 BEST, 25/17 Gbps L4/L7, 15K SSL TPS, 15 Gbps compression, 2 tenants. Not r2600. | F5-BIG-LTM-R2800, F5-BIG-LTM-R2600, SFP28/SFP+ per drawing, Second AC R2XXX if dual |
Frequently Asked Questions
Quick Answer: High-end rSeries density absorbs most VIPRION chassis workloads, so a chassis is worth keeping only where scale or sunk investment justifies the footprint. Virtual editions suit elastic cloud edges, while the appliances win on predictable SSL transaction rates, hardware offload, and tenants per rack unit.
F5-BIG-PEM-R5900 is the Policy Enforcement Manager software SKU for an r5900 chassis, not a standalone box. F5-BIG-APM-R5600 is Access Policy Manager on r5600. Pair each with the matching rSeries hardware, LTM, F5OS, and HA. Confirm modules on a dated CPQ.
The official rSeries platform specifications are in F5's hardware guide: r5000/r10000 platform guide (techdocs.f5.com). This page is the RFQ ladder — L7 throughput, SSL TPS, and tenant count — so you size before opening the vendor guide. Lock modules and F5OS on the quote.
Many chassis workloads consolidate onto high-end rSeries density. Keep VIPRION/chassis only when scale or existing investment requires it — validate with F5.
VE fits elastic / cloud edges. Hardware rSeries wins on deterministic SSL TPS, FPGA offload, and dense tenancy per RU.
BENQUAN GLOBAL LIMITED supplies BIG-IP rSeries and support. Contact info@benquan.hk or request a quote.
Key Takeaway
Key Takeaway: Start from the SSL transaction target under your production cipher mix: r2600 and r2800 cover small edges, the r5000 tier carries most enterprise refreshes, and an r10900 or DS model earns its price only past the 150K TPS class. BENQUAN GLOBAL LIMITED supplies F5 BIG-IP rSeries appliances with competitive pricing.