BIG-IP Next 20.1.0 Features

BIG-IP Next uses a combination of BIG-IP Next Central Manager, together with BIG-IP Next instances, to implement application delivery and security. The BIG-IP Next Central Manager manages the BIG-IP Next instances, assuming responsibility for all administrative and management tasks. The BIG-IP Next instances, responsible for data processing, provide robust automation capabilities, scalability, and ease-of-use for organizations running applications on-premise, in the cloud, or out at the edge.

Release Versions

  • BIG-IP Next LTM and BIG-IP Next Virtual Edition (VE) :: 20.1.0

  • BIG-IP Next Central Manager VE :: 20.1.0

  • F5OS-A :: 1.7.0

  • F5OS-C :: 1.6.2

BIG-IP Next Supported Hypervisors and Configuration

The following are the supported hypervisors and configuration for BIG-IP Next.

Note the following for F5OS-C 1.6.2:

  • Do not deploy BIG-IP and BIG-IP Next tenants in the same partition/blade.

  • For VELOS deployments, only 4 and 8 vCPUs tenants are supported on a single blade.

  • For VELOS deployments, there is a maximum of 8 vCPUs on a blade, either:

    • Two 4 vCPU BIG-IP Next tenants per blade

    • One 8 vCPU BIG-IP Next tenant per blade.

F5 rSeries:

  • rSeries 5000 appliances:

    • 5600: 4, 8, and 12 vCPU BIG-IP Next tenants

    • 5800: 4, 8, and 18

    • 5900: 4, 8, and 26

  • rSeries 10000 appliances:

    • 10600: 4, 8, and 24 vCPU BIG-IP Next tenants

    • 10800: 4, 8, and 28

    • 10900: 4, 8, and 36

VMware

  • VMware ESXi 7.0

  • 2, 4, 6, 8, 12, 16, and 24 vCPUs are supported

KVM

  • KVM on Ubuntu 22.04

  • 2, 4, 6, 8, 12, 16, and 24 vCPUs are supported

BIG-IP Next Central Manager Supported Hypervisors

  • VMware ESXi 7.0

Software Base Operating System

  • Ubuntu 22.04

BIG-IP Next Central Manager Management

Manage an rSeries BIG-IP Next instance from BIG-IP Next Central Manager

You can use a template to add a BIG-IP Next instance on an rSeries system to BIG-IP Next Central Manager to easily control all of the instance’s services and analytics with a single, unified management user interface.

Support for auto-failover upgrade for rSeries HA clusters

BIG-IP Next Central Manager supports upgrading to the latest release of rSeries HA clusters with the auto-failover upgrade feature. Both the primary and secondary instances of the HA cluster instance are upgraded when an upgrade is triggered on a rSeries HA cluster instance.

Support for auto-failover upgrade for VELOS HA clusters

BIG-IP Next Central Manager supports upgrading to the latest release of VELOS HA clusters with the auto-failover upgrade feature. Both the primary and secondary instances of the HA cluster instance are upgraded when an upgrade is triggered on a VELOS HA cluster instance.

Role-based User Access

BIG-IP Next Central Manager allows you to limit user access to specific BIG-IP Next instance features. You do this by assigning access based on job responsibilities, or roles. When you associate a user (or group of users) with one or more role, they have privileges only to the areas that are explicitly associated with that role (or roles).

The built-in roles are:

  • Administrator

  • Instance Manager

  • Application Manager

  • Certificate Manager

  • Security Manager

  • Auditor

BIG-IP Next Instance Management

Support for BIG-IP Next Central Manager on KVM

You can now install and configure the BIG-IP Next Central Manager on KVM.

Application Service Management

AS3 application services directly reference shared objects on BIG-IP Next Central Manager

Shared objects, such as certificates, WAF policies, and iRules in AS3 application services now reference the objects saved in BIG-IP Next Central Manager. Previously, these objects were embedded directly into the AS3 declaration. You will now fine the object name in the AS3 declaration as it is saved in BIG-IP Next Central Manager.

Add L3 Network (VLAN) configuration to FAST application services

If you have added L3 network VLANs to your BIG-IP Next instances, you can select one or more VLANs in the network before you deploy the FAST application service to the instance.