Unlike most iTop's extensions, the definition of TeemIp configuration parameters is split between a dedicated class of objects, named Global IP Setting, and the general configuration file.

• Global IP Settings host the parameters that are specific to an organization,
• The general configuration file defines parameters that drive TeemIp's generic behaviour and enables the default value of Global IP Settings parameters to be overwritten.

Global IP Setting objects store all parameters that drive TeemIp behaviour.

From the Configuration menu, under the General Configuration sub-menu, the Global IP Settings shortcut displays the IP Setting used by the different organizations.

From the listing view, click on the “New…” menu to display the creation form.

From the detailed view of a Global IP Setting, click on the “Modify” button. Basically, all parameters can be changed here but, of course, the organization.

A Global IP Setting for a given organization is now mandatory to create an IP object for that organization. First option is to create the Global IP Setting before creating an IP Object. Second option is to directly create the IP Object. Indeed, as soon as the organization is selected in the IP object creation form, TeemIp checks if a corresponding Global IP Setting exits for that organization and automatically creates one if required.

When the Global IP Setting is automatically created, parameters are set with the default values defined in TeemIp's data model. It is however possible to overload these default values through the general Configuration file, as described below.

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 a specific 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 a specific 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',
		  ),
		),