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 [2023/09/15 21:17] – cnaud | 2_x:datamodel:start [2023/10/03 11:55] – [Linking CIs to IPs] cnaud | ||
---|---|---|---|
Line 30: | Line 30: | ||
| [[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 ===== | ===== Automation ===== | ||
Line 53: | Line 42: | ||
TeemIp is a highly configurable application and many parameters allow you to adapt it to your own IP Management practices: | TeemIp is a highly configurable application and many parameters allow you to adapt it to your own IP Management practices: | ||
- | * The [[2_x: | + | * [[2_x: |
- | * [[2_x: | + | * The [[2_x: |
- | * [[2_x: | + | * [[2_x: |
* [[2_x: | * [[2_x: | ||