The standard General Configuration file that can be reached under the Configuration menu may host parameters for TeemIp. If any, these will be grouped within the “Modules specific settings” part, under the teemip-ip-mgmt block. This block hosts different set of parameters dedicated to different TeemIps features.

	'teemip-ip-mgmt' => array (
		'feature_1' => array (
		  ...
		),
		...
		'feature_n' => array (
		  ...
		),
	),

The following chapters describe the different features available.

This block is used to overwrite the default TeemIp parameters defined in the data model. It contains sub-blocks of parameters dedicated to the different TeemIp extensions and a general attribute to enable or disable the whole block. All the parameters defined here above can be reset but only the ones that need to be overwritten should sit here.

The structure of the block is as follows:

In the following example, only parameter 'request_creation_ipv4_offset' will be changed to 5 where its defaults value is 0.

		'default_global_ip_settings' => array (
		  'enabled' => true,
		  'ip_request_parameters' => 
		  array (
		    'request_creation_ipv4_offset' => 5,
		  ),
		),

This block defines how one can navigate between adjacent IPs, a feature described in the IP Address chapter. It holds the following parameter:

Example:

		'ip_navigation' => array (
		  'enabled' => true,
		  'within_subnet_only' => true,
		),

TeemIp may periodically look for IPs that are attached to obsolete CIs and make sure they are in the “released” status. The behaviour of that feature is defined in the specific 'ip_release_on_ci_status' configuration block and is driven by the following parameters:

		'ip_release_on_ci_status' => array (
		  'enabled' => false,
		  'debug' => false,
		  'periodicity' => 3600,
		  'status_list' => 
		  array (
		    0 => 'obsolete',
		  ),
		),

TeemIp may periodically look for IPs that are attached to implementation or production CIs and make sure they are in the “allocated” status. The behaviour of that feature is defined in the specific 'ip_allocate_on_ci_status' configuration block and is driven by the following parameters:

		'ip_allocate_on_ci_status' => array (
		  'enabled' => false,
		  'debug' => false,
		  'periodicity' => 3600,
		  'status_list' => 
		  array (
		    0 => 'implementation',
		    1 => 'production',
		  ),
		),

TeemIp may periodically look for IPs that are not attached to any CIs and make sure they are in the “unassigned” status. The behaviour of that feature is defined in the specific 'ip_unassign_on_no_ci' configuration block and is driven by the following parameters:

		'ip_unassign_on_no_ci' => array (
		  'enabled' => false,
		  'debug' => false,
		  'periodicity' => 3600,
		  'target_status' => 'unassigned',
		),

Capacity planning in TeemIp is done on the fly i.e. when an IP address is added or removed to or from an IP Range or subnet. It can be done as well through a background task which behaviour is defined in the specific 'handle_ip_watermarks' configuration block and is driven by the following parameters:

		'handle_ip_watermarks' => array (
		  'enabled' => false,
		  'debug' => false,
		  'periodicity' => 86400,
		  'target_classes' => 
		  array (
		    0 => 'IPv4Subnet',
		    1 => 'IPv4Range',
		  ),
		),