Security appliances

Load balancers sit in front of your applications and are chosen by what they must do (load balancing, global server load balancing, network firewall, web application firewall, remote-access VPN) and how much traffic they must handle, not by port count. These are the families SKUit's vendors position for that role; each family page lists its models and the software packages they are sold with.

1 vendor · 5 product families · 12 platforms

F5

5 families F5 positions for this role

  • rSeries r10000 Series

    F5's upper mid-range rSeries application delivery controller — one 1U appliance sold as three licensed models, r10600, r10800 and r10900, which differ in tenancy (vCPUs and BIG-IP tenants), throughput, SSL rate, connection capacity and compression. 4x 100G/40G QSFP28/QSFP+ plus 16x 25G/10G SFP28/SFP+; no RJ45 data ports and no 1G connectivity. It carries an FPGA and a dedicated hardware DDoS engine rated at 160M SYN cookies per second on every model, two 1200 W power supplies as standard, dual RAID 1 SSDs and a removable fan tray. The four QSFP28 ports work in two pairs, and both ports in a pair must run at the same speed; F5's platform guide and data sheet state they do not support breakout cables. The BIG-IP module entitlement is fused into the appliance part number.

  • rSeries r2000 Series

    F5's smallest rSeries application delivery controller — one 1U appliance sold as two licensed models, r2600 and r2800, which differ in tenancy (CPUs and BIG-IP tenants), throughput, SSL rate, connection rate and compression path. 4x 10G/1G RJ45 plus 4x 25G/10G/1G SFP28 in a single port group with three mutually exclusive speed modes. No FPGA and no hardware DDoS engine on this platform. The BIG-IP module entitlement is fused into the appliance part number: there is no bare hardware SKU and no separate base-licence SKU.

  • rSeries r4000 Series

    F5's entry x86-class rSeries application delivery controller — one 1U appliance sold as two licensed models, r4600 and r4800, which differ in tenancy (CPUs and BIG-IP tenants), throughput, SSL rate, connection rate and compression path. 4x 10G/1G RJ45 plus 4x 25G/10G/1G SFP28 in a single port group with three mutually exclusive speed modes. No FPGA, no hardware DDoS engine and no NEBS Level 3 listing on this platform — those belong to the r5000/r10000/r12000 rungs. The BIG-IP module entitlement is fused into the appliance part number: there is no bare hardware SKU and no separate base-licence SKU.

  • rSeries r5000 Series

    F5's mid-range rSeries application delivery controller — one 1U appliance sold as three licensed models, r5600, r5800 and r5900, which differ in tenancy (vCPUs and BIG-IP tenants), throughput, SSL rate, connection capacity and compression. 2x 100G/40G QSFP28/QSFP+ plus 8x 25G/10G SFP28/SFP+; no RJ45 data ports and no 1G connectivity. Unlike the r2000 and r4000 it carries an FPGA and a dedicated hardware DDoS engine rated at 80M SYN cookies per second on every model. The two QSFP28 ports must run at the same speed as each other, and F5's platform guide and data sheet state they do not support breakout cables. The BIG-IP module entitlement is fused into the appliance part number: there is no bare hardware SKU and no separate base-licence SKU.

  • VELOS

    F5's chassis-based application delivery controller. A 4RU CX410 chassis holds up to eight BX110 blades and ships with two system controllers; capacity grows by adding blades, each adding 95 Gbps of L4/L7 throughput and 100,000 SSL TPS. The BIG-IP function is part of the chassis and blade part numbers, and every blade takes the chassis's function. AC and DC are separate chassis.

Other roles

The same catalog, by the job it does

Create a validated BOM with security appliances

SKUit turns a use case into a complete, orderable bill of materials — the right platform, optics, licences and power, reconciled against the same validated data shown on this page.

To create a bill of materials for security appliances, you need to log in or create an account.