Updated Date: 04/21/2026
Resource Provisioning
You can manage the provisioning of system memory, disk space, and CPU usage among licensed modules on the BIG-IP system.
There are four available resource allocation settings for modules.
- None/Disabled
- Specifies that a module is not provisioned. A module that is not provisioned does not run.
- Dedicated
- Specifies that the system allocates all CPU, memory, and disk resources to one module. When you select this option, the system sets all other modules to None (Disabled).
- Nominal
- Specifies that, when first enabled, a module gets the least amount of resources required. Then, after all modules are enabled, the module gets additional resources from the portion of remaining resources.
- Minimum
- Specifies that when the module is enabled, it gets the least amount of resources required. No additional resources are ever allocated to the module.
After you have activated a license on the BIG-IP system, you can use the Configuration utility to provision the licensed modules.
-
On the Main tab, click System > Resource Provisioning.
-
For licensed modules, select either Minimum or Nominal, as needed.
-
Click Submit.
-
Reboot the system:
-
On the Main tab, click System > Configuration > Device > General.
-
Click Reboot.
-
You can use tmsh to provision the BIG-IP system. For more information about the tmsh provision options, type help sys provision.
Important: You must provision the BIG-IP system before you configure it; otherwise, you lose the system configuration when you provision the system.
-
Open the TMOS Shell (
tmsh).tmsh -
View the current provisioning of the system.
list sys provision
The system displays the provision configuration. In this example, the system has nominal provisioning for LTM and the other modules are unprovisioned.
`sys provision avr { } sys provision gtm { } sys provision lc { } sys provision ltm { level nominal }` -
Modify the current provisioning of the system using these parameters.
modify sys provision <module_name> level <level_type>
This example sets nominal provisioning for AVR.
modify sys provision avr level nominalThe system displays the provision configuration. In this example, the system now has nominal provisioning for LTM and AVR.
`sys provision avr { } sys provision gtm { } sys provision lc { } sys provision ltm { level nominal }` -
Save the changes to the stored configuration.
save sys config -
Verify the current provisioning of the system.
list sys provision
You can modify Management (mgmt) provisioning from the command line where Small equals 0 MB, Medium equals 200 MB, and Large equals 500 MB.
-
Open the TMOS Shell (
tmsh).tmsh -
Type
tmsh modify sys db provision.extramb value 500 -
Important: Provisioning the mgmt plane to large and performing a ConfigSync might cause an outage on the peer unit. See K31326690 for more information on this issue.
Some BIG-IP systems support configuring the type of FPGA firmware that is enabled. You can choose from these types, depending on the hardware platform and provisioned modules.
- L7L4_BALANCED_FPGA
- Suitable for all uses.
- L4_PERFORMANCE_FPGA
- Suitable for CGNAT standalone and BIG-IP Local Traffic Manager (LTM) L4-centric deployments.
Important: Changing the firmware type when using a multi-blade VIPRION® C2400 chassis is not recommended, as you might not get the expected scalable performance.
You can use the Configuration utility to select a specific FPGA firmware type.
-
On the Main tab, click System > Resource Provisioning.
-
For the FPGA Firmware Selection setting, select the check box for the FPGA firmware type that you would like to use.
-
Click Submit.
These platforms support FPGA firmware selection.
| Platform family | Platform model |
|---|---|
| VIPRION® | B2250 blade |
| VIPRION | C2200 chassis |
| VIPRION | C2400 chassis |