Documentation

User Tools

Site Tools

Trace: • ip-addresses
2_x:datamodel:ip-addresses

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
2_x:datamodel:ip-addresses [2024/07/24 15:45] – [Automation] cnaud2_x:datamodel:ip-addresses [2026/01/21 15:51] (current) – [Automation] cnaud
Line 35: Line 35:
 <note important> <note important>
 The attribute "Status" is more than informative. It does have an impact on what can and cannot be done with an IP. Meanings of different values are: The attribute "Status" is more than informative. It does have an impact on what can and cannot be done with an IP. Meanings of different values are:
-  * **Allocated**: IP is in use and potentially allocated to a CI. It cannot be allocated to another CI without being released or unassigned first unless the IP Setting **Allow attachement of already allocated IPs to CIs** is set to **Yes**. +  * **Allocated**: IP is in use and potentially attached to a CI or an interface. It cannot be attached to another CI without being released or unassigned first unless the IP Setting **Allow attachement of already allocated IPs to CIs** is set to **Yes**. 
-  * **Released**: IP is not in use anymore and can be re-allocated if required+  * **Released**: IP is not in use anymore and doesn't ping. It and can be re-allocated or reserved if required
   * **Reserved**: IP is not in use yet but will be allocated (activated) at a point in time. It can be allocated from the IP detail menu but is invisible from the CI edition menu.   * **Reserved**: IP is not in use yet but will be allocated (activated) at a point in time. It can be allocated from the IP detail menu but is invisible from the CI edition menu.
-  * **Unassigned**: IP exists in TeemIp without any clear status and can be allocated or reserved.+  * **Unassigned**: IP exists and pings but it is not attached to a CI or an interface. It can be allocated or reserved. 
 + 
 +If [[extensions:teemip-ip-discovery|IP Discovery Datamodel extension]] is installed, versions 3.2.0 and above bring the additional status **Discovered** to the IPObject class and therefore to the IP Addresses. This value may be set by the [[collectors:teemip-ip-discovery-collector|IP Discovery Data collector]] to newly discovered IPs and changed afterwards by the Hostmaster.
 </note> </note>
  
Line 184: Line 186:
   * IPs that are in state Allocated cannot be set as IP attribute unless IP setting **Allow attachment of already allocated IPs to CIs** is set to **Yes**,   * IPs that are in state Allocated cannot be set as IP attribute unless IP setting **Allow attachment of already allocated IPs to CIs** is set to **Yes**,
   * Reserved IPs are... reserved,   * Reserved IPs are... reserved,
-  * Once a CI is created or updated, the status of its attached IP is automatically changed to Allocated, +  * Once a CI is created or updated, the status of its attached IP is automatically changed to **Allocated**, 
-  * If a Management IP is removed from the CI, its status becomes Unassigned unless it is still linked to another CI.+  * If a Management IP is removed from the CI, its status becomes **Released** unless it is still linked to another CI.
  
 Some others CIs, like IP interfaces attached to routers, may host several IP addresses. For them: Some others CIs, like IP interfaces attached to routers, may host several IP addresses. For them:
   * One or more IPs (with no limitation of quantity) can be attached to them,    * One or more IPs (with no limitation of quantity) can be attached to them, 
   * An IP can be attached to them, regardless their status,    * An IP can be attached to them, regardless their status, 
-  * Once an interface is created or updated, the status of its attached IPs is automatically changed to Allocated, +  * Once an interface is created or updated, the status of its attached IPs is automatically changed to **Allocated**, 
-  * If a link with an IP address is removed, status of IP moves back to Unassigned unless it is still linked to another CI.+  * If a link with an IP address is removed, status of IP moves back to **Released** unless it is still linked to another CI.
  
 <note important> <note important>
Line 229: Line 231:
    * **Allocate IPs attached to production CIs** (*) be set to **Yes**, TeemIp will make sure that IPs attached to CIs are "Allocated".    * **Allocate IPs attached to production CIs** (*) be set to **Yes**, TeemIp will make sure that IPs attached to CIs are "Allocated".
    * **Release IPs from CIs that become obsolete** (*) be set to **Yes**, TeemIp will release all IPs that are still allocated to obsolete CIs,    * **Release IPs from CIs that become obsolete** (*) be set to **Yes**, TeemIp will release all IPs that are still allocated to obsolete CIs,
-   * **Un-allocate IPs that are not attached to a CI** (*) be set to **Yes**, TeemIp will unassign the IPs that are no longer attached to a CI,+   * **Un-allocate IPs that are not attached to a CI** (*) be set to **Yes**, TeemIp will unassign the IPs that are not attached to a CI,
    * **Release IPs from subnets that are released** be set to **Yes**, TeemIp will release all IPs that belong to released subnets,    * **Release IPs from subnets that are released** be set to **Yes**, TeemIp will release all IPs that belong to released subnets,
    * **Allow attachment of already allocated IPs to CIs** be set to **Yes**, TeemIp will allow, from the CI details screen, the attachment of an allocated IP to a CI.    * **Allow attachment of already allocated IPs to CIs** be set to **Yes**, TeemIp will allow, from the CI details screen, the attachment of an allocated IP to a CI.
-   * **Detach released IPs from CIs** be set to **Yes**, TeemIp will detach IPs which status moves to "Released" from all CIs and interfaces.  +   * **Detach released IPs from CIs** be set to **Yes**, TeemIp will detach IPs which status moves to "Released" from all CIs. This does not include interfaces for which released IPs are always detached.  
  
 The 3 first actions (*) are handled by background tasks which default parameters can be overwritten in the configuration file.  The 3 first actions (*) are handled by background tasks which default parameters can be overwritten in the configuration file. 
2_x/datamodel/ip-addresses.1721835956.txt.gz · Last modified: by cnaud

Page Tools