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/10/03 11:55] – [Linking CIs to IPs] 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: | ||
+ | |||
+ | |||
+ | ===== 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: | ||
+ | |||