Obviously, IP Address objects in TeemIp modelize addresses of the Internet Protocol. Both version 4 and version 6 are supported.
|Organization||Foreign key to a(n) Organization||Yes|
|Status||Possible values: allocated, released, reserved, unassigned||Yes|
|Usage||Foreign key to a(n) IP Address Usage||No|
|Note||Multiline character string||No|
|Requestor||Foreign key to a(n) Person||No|
|Allocation date||Date (year-month-day)||No|
|Release date||Date (year-month-day)||No|
|Short Name||Alphanumeric string||No|
|Domain Name||Foreign key to a(n) Domain||No|
|Aliases||Array of alphanumeric strings||No|
|Subnet||Foreign key to a(n) Subnet||No|
|Range||Foreign key to a(n) IP Range||No|
|Contacts||All the contacts for this IP|
|Documents||All the documents linked to this IP|
|Notifications||List of related notifications - Present if a notification trigger exists for that class|
|NAT IPs||All other IPs linked to this IP in a NAT relationship|
|CIs||All the configuration items configured with the IP|
|History||History of all changes made to the IP|
The IP Addresses shortcuts of the IP Management module on the explorer menu display all the IPv4 or IPv6 Addresses of the selected organization or all IPv4 or IPv6 Addresses if no organization is selected.
From the listing view, click on the “New…” menu to display the creation form.
An implicit but intuitive set of rules are followed when an IP address is created:
At creation time, global settings “Allow Duplicate Names” and “Ping IP before assigning it ?” can be overwritten. Note that a change on these parameters, if any, only applies to the current creation and don’t affect the value of the global parameters. If it is required to change them globally, these can be changed through the Global IP Settings menu of the Data Administration module.
From the detailed view of an IP Address, click on the “Modify” button.
Basically, all parameters can be changed here but, of course, the IP address itself.
Next to standard actions, a set of specific actions can be applied to IP Addresses. These can be found in the “Other Actions” menu available from the details page.
These specific actions are described in below chapters.
This action applies to IP Addresses that are released, reserved or unassigned. Its purpose is to allocate the address to a CI without having to open the modification form of the targeted CI.
Three parameters control the action:
|Target class||List the instantiated classes of objects that may be linked to an IP address||Yes|
|Functional CI||List the CIs of class defined by Target class which an IP address can be allocated to||Yes|
|IP Attribute||IP attribute of the CI that the IP should be allocate to||Yes|
These parameters are automatically computed and may differ from one data model to another. For instance, a server may have only one IP address (it's management IP, like in the standard data model) or multiple ones (a management and a backup IP). Once the CI is selected, TeemIp confirms the operation through the following screen.
This action simply unallocate the IP from all CIs that it may be allocated to. This includes IP Interfaces. Action is launched as soon as the action is selected. A confirmation screen is then displayed.
TeemIp has been designed to provide a comprehensive modelization and documentation of the link(s) that a CI and an IP address may share together.
Some CIs, like servers or network devices, have one IP attribute that represents their management IP. For them:
Some others CIs, like IP interfaces attached to routers, may host several IP addresses. For them:
Changes on CIs may have an impact on IPs. Here is what happens when…
When an IP is set to the status “Released”, it is automatically removed from all CIs and all interfaces.
TeemIp may automatically and periodically check the status of IPs and their coherency with the CIs they are attached to, if any. This behaviour is driven by a set of parameters defined in Global IP Settings. For any given organization, should the configuration parameter… :