Manual Chapter : Determine the network configuration needed for your deployment

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 8.0.0
Manual Chapter

Determine the network configuration needed for your deployment

The deployment requirements for the BIG-IQ solution you install depends on which functions you need to perform. Generally, as you add interfaces and subnets to your BIG-IQ solution, you can expect increases in performance level, security, and dependability.
BIG-IQ deployment options
What functions does your deployment need to perform?
Which hardware components do you need?
Optimal number of interfaces and subnets
Manage and configure BIG-IP devices. For example, you might want to just manage virtual edition licenses or configure local traffic and security policy objects.
2 BIG-IQ CM systems (1 active, 1 standby)
BIG-IP devices
eth0 to access the BIG-IQ CM.
eth1 and a single (Discovery) subnet to communicate to the BIG-IQ devices.
Manage and configure BIG-IP devices.
Collect and view Local Traffic, DNS, and Device statistical data from the BIG-IP devices.
Collect, manage, and view events and alerts from BIG-IP services (like LTM, APM, or FPS).
2 BIG-IQ CM systems (1 active, 1 standby)
BIG-IP devices
3 or more DCDs.
An external storage device (if you choose to back up your DCD content).
eth0 to access the BIG-IQ CM
eth1 and a (Discovery) subnet to communicate to the BIG-IQ devices.
eth2 (see note below the table) and a (Cluster) subnet to communicate to handle data management and storage on the DCDs.
Manage and configure BIG-IP devices.
Collect and view Local Traffic, DNS, and Device statistical data from the BIG-IP devices.
Collect, manage, and view events and alerts from BIG-IP services (like LTM, APM, or FPS).
Separate network traffic to support large, distributed deployments of the F5 BIG-IQ solution for improved performance, security, and interactions in multiple data center environments.
Or, for disaster recovery capability, you could operate multiple data centers, each with its own set of BIG-IQ systems. (For additional detail, refer to
Managing Disaster Recovery Scenarios
in the
Setting up and Configuring a BIG-IQ Centralized Management Solutio
n article on s
upport.f5.com
)
2 BIG-IQ CM systems (1 active, 1 standby
3 or more DCDs
BIG-IP devices
An external storage device (if you choose to back up your DCD content)
eth0 to access the BIG-IQ CM
eth1 and a (Discovery) subnet to communicate to the BIG-IQ devices.
eth2 (see note below the table) and a (Cluster) subnet to communicate to handle data management and storage on the DCDs.
eth3 (see note below the table) and a (Listener) subnet to improve performance
If you plan to use the eth2 and eth3 interfaces, but your VE has only 2 interfaces, use the software application for the hypervisor used to create your VE instances to add two additional interfaces.