Manual Chapter : CE file for deployment concepts

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 6.1.0
Manual Chapter

CE file for deployment concepts

The number of devices of each type that will best meet your company's needs depends on a number of factors. Refer to the
F5 BIG-IQ Centralized Management: Data Collection Device Sizing Guide
on
support.f5.com
for details.
With the addition of the DCD cluster, you can manage alerts and events on your managed devices as well as monitor performance analytics.
  • Traffic from the BIG-IQ devices to the BIG-IP devices. This traffic is always initiated by the BIG-IQ devices.
  • If you have a secondary BIG-IQ device, there is also traffic between the BIG-IQ devices to support high availability syncing.

When do I need extra resources?

When the BIG-IQ system you deploy manages a number of devices that exceeds specified thresholds, F5 recommends that you use 8 CPUs and either 32 or 64 GB of RAM. These thresholds vary depending on which modules are licensed on the devices that the BIG-IQ manages and where the devices are deployed.
The following table lists thresholds for each BIG-IP module that impacts the amount of RAM that a BIG-IQ requires. For example, if the BIG-IQ manages more than 32 devices provisioned with the Access module, you should use 32 GB instead of 16.
A BIG-IQ managing devices...
Needs 32 GB to manage more than:
provisioned with Access
32 devices
provisioned with ADC
80 devices
provisioned with ASM
40 devices
provisioned with DNS
100 devices
provisioned with FPS
50 devices
deployed in a VMware service scaling group
100 devices
deployed in an AWS or Azure service scaling group
50 devices
This is a rough approximation. Depending on the number of objects on each BIG-IP, you might need more or less RAM. Additionally, when the devices managed by the BIG-IP are provisioned with multiple modules, the RAM requirement increases.
  • Create a service scaling group where you specify thresholds and alert settings for auto-scaling and health monitoring.
  • Create a service template to standardize an application for self-service deployment.
  • Give users role-based access to the service template and the service scaling group resources.
  • Use one of the templates you have permissions for to create an application and deploy it to the devices in a service scaling group.