This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
2_x:datamodel:start [2019/02/26 11:17] – [Zone Management] cnaud | 2_x:datamodel:start [2023/09/15 21:28] – [TeemIp Configuration] cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== TeemIp Data Model ====== | ||
+ | |||
+ | ===== IP Management ===== | ||
+ | IP Management is the heart of TeemIp. This is the place where IPv4 and IPv6 spaces are administered. A set of IP objects modelizes your IP spaces: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | |||
+ | <note tip> IPv4 and IPv6 spaces are unique per organization. Two different organizations, | ||
+ | </ | ||
+ | |||
+ | {{overview_group_module-3x.png? | ||
+ | |||
+ | |||
+ | And different [[2_x: | ||
+ | |||
+ | ===== CMDB ===== | ||
+ | |||
+ | The **Configuration Management Data Base** defines the objects (Configuration Items or **CIs**) that can be managed inside TeemIp, next to the pure IP objects (subnets, addresses, etc.). Widely inherited from iTop, it defines all the physical devices (PCs, Servers, Printers, Network devices, Telephones, etc.) but also some logicals elements (Groups, Application Solutions, Business Processes), software objects (Software Instances, Licenses, etc.), structuring entities (Organizations, | ||
+ | |||
+ | In order to keep the elements to manage as simple as possible while covering most IT needs, the configuration management domain has been split into 6 modules, including a TeemIp specific one that groups the objects related to network management. | ||
+ | |||
+ | ^ Module Name ^ Description | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | | [[2_x: | ||
+ | |||
+ | ===== Linking CIs to IPs ===== | ||
+ | In TeemIp, many configuration items have one or multiple IP addresses as attributes. These addresses are actually keys toward IPv4 or IPv6 objects managed through the IP Management module. When attaching or detaching an IP address to or from a CI, the following points should be kept in mind: | ||
+ | |||
+ | <note important> | ||
+ | * When a **CI is created** or modified, only addresses which status is **released** or **unassigned** (ie not allocated nor reserved) are offered, | ||
+ | * Status of an IP is automatically changed to **allocated** when it is **attached** to a device or to **released** when **removed** from it, | ||
+ | * When **attached** and if enabled through IP settings, the **name** of the CI is **copied** into the short name of the IP, | ||
+ | * When **detached** and if enabled through IP settings, the short name of the IP is **reset** to an empty string. | ||
+ | </ | ||
+ | |||
+ | More details can be found in the [[2_x: | ||
+ | |||
+ | ===== Automation ===== | ||
+ | When linking an IP together with a CI, one must insure that both the CI's and the IP's status are consistent. TeemIp provides configurable automation processes to help IP Administrators with that task. | ||
+ | * One will [[2_x: | ||
+ | * Another one will [[2_x: | ||
+ | * A last one will [[2_x: | ||
+ | |||
+ | These processes are documented in the [[2_x: | ||
+ | |||
+ | ===== TeemIp Configuration | ||
+ | |||
+ | TeemIp is a highly configurable application and many parameters allow you to adapt it to your own IP Management practices: | ||
+ | * [[2_x: | ||
+ | * The [[2_x: | ||
+ | * [[2_x: | ||
+ | * [[2_x: | ||
+ | |||