How are memory and disk allocated to different modules on bigip appliance?

HI Herman,

Part 1
=======

On a Big-IP appliance, the memory and disk space allocated to different modules can be managed through the "Resource Provisioning" feature, allowing you to specify how much of the system's resources each module should use, with options like "Minimum," "Nominal," or "Dedicated" allocation depending on your needs; essentially, you can set specific amounts of memory and disk space for each module based on its anticipated usage, with the system automatically adjusting resource allocation accordingly. 

Key points about resource allocation on a Big-IP appliance:

Module-specific allocation:
Each licensed module on the Big-IP system can be assigned a specific amount of memory and disk space. 

Allocation settings:
You can choose between "Minimum" (least amount of resources), "Nominal" (balanced allocation based on module needs), or "Dedicated" (all available resources allocated to a single module). 
Flexible resource management:
Especially with vCMP guests, you can fine-tune the resource allocation for each guest based on the specific modules it is running and the traffic it is handling. 

How to check memory and disk usage for modules:
Configuration Utility:
Access the "System > Resource Provisioning" section within the Big-IP configuration utility to view and adjust resource allocation for each module. 
Command line:
Use commands like df -h to check available disk space on different mounted volumes and monitor disk usage. 

Part 2
=======

Management provisioning allocates additional memory for the BIG-IP Linux host system. There are three default settings: Small (default), Medium, and Large.

When you use the Configuration utility to configure the Provisioning setting for Management (MGMT), the system allocates additional memory to the control plane using the following default values. These values are in addition to the base memory allocation for Management (MGMT):

Small memory allocation is 0 MB.
Medium memory allocation is 200 MB.
Large memory allocation is 500 MB.
You can also use the TMOS Shell (tmsh) to modify the system database variable provision.extramb to use a custom allocation of additional memory for Management (MGMT). For example, you can configure an additional memory value other than Small, Medium, or Large. Any additional memory configured for Management (MGMT) (control plane) is deducted from TMM (data plane).

Recommendations

Before you modify BIG-IP system provisioning or add more memory to an existing Management setting, review the available system memory.

For large configurations containing more than 2000 configured objects, for Management (MGMT), in the Provisioning column, select Large.

For units with at least two provisioned modules (LTM+ASM+other, LTM+APM+other, and LTM+AVR+other), running on BIG-IP 14.1 or later and medium-large configurations (500+ configuration objects), select Large.

For units running on BIG IP 15.x or later, select Large.

For units provisioned with three or more software modules and running on BIG IP 15.x or later, set <numeric value>to 2048 (or even 4096 if enough resources are available), using command as previously described in step 3 of the "Modify the provisioned memory value using tmsh".