Documentation

User Tools

Site Tools

Trace:
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 [2023/10/03 15:52] – [Automation] cnaud2_x:datamodel:ip-addresses [2024/07/26 11:23] (current) – [Automation] cnaud
Line 39: Line 39:
   * **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 in TeemIp without any clear status and 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 79: Line 81:
 By definition, FQDNs are absolute domain names. They specify the exact location of domain names in the tree hierarchy of the Domain Name System (DNS). This is why they end up with a dot.\\ By definition, FQDNs are absolute domain names. They specify the exact location of domain names in the tree hierarchy of the Domain Name System (DNS). This is why they end up with a dot.\\
 \\ \\
 +According to configuration parameter **Allow Duplicate Names**, unicity of the FQDN is checked:
 +  * Duplicates may exist in different organizations,
 +  * Within an organization, duplicates may exist in different [[extensions:teemip-zone-mgmt#views|DNS views]],
 +  * If parameter is set to:
 +    * **No**, all other cases of duplicates are rejected, 
 +    * **Dual stack**, duplicates may exist between IPv4 and IPv6 spaces,
 +    * **Yes**, unicity of FQDN is not verified.
 +
 According to configuration parameter **Compute FQDN when short name is empty**, the FQDN may be computed regardless the content of the Short Name and DNS Domain. According to configuration parameter **Compute FQDN when short name is empty**, the FQDN may be computed regardless the content of the Short Name and DNS Domain.
 </note> </note>
Line 91: Line 101:
 For v6 IPs, a simple autocompletion mechanism is used to help typing the IP: its first 64 bits are copied from the subnet IP… which can, of course, be manually changed by the user.  For v6 IPs, a simple autocompletion mechanism is used to help typing the IP: its first 64 bits are copied from the subnet IP… which can, of course, be manually changed by the user. 
 </note> </note>
-==== Modify an IP Address ====+==== Modifying an IP Address ====
 From the detailed view of an IP Address, click on the {{pen-icon.png?nolink|Edit icon}} button. From the detailed view of an IP Address, click on the {{pen-icon.png?nolink|Edit icon}} button.
  
Line 214: Line 224:
  
 ==== Releasing IPs ==== ==== Releasing IPs ====
-When an IP is set to the status "Released", it is automatically removed from all CIs and all interfaces.+When an IP is set to the status "Released", it is removed from all CIs and all interfaces if IP Setting **Detach released IPs from CIs** is set to Yes (which is the default setting).
  
 ==== Automation ==== ==== Automation ====
Line 224: Line 234:
    * **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. 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. 
Line 265: Line 276:
 | target_status | Status of the IP once the action is done | | target_status | Status of the IP once the action is done |
  
 +Please, refer to the [[2_x:datamodel:configuration|Configuration File]] chapter for further details.
2_x/datamodel/ip-addresses.1696341132.txt.gz · Last modified: 2023/10/03 15:52 by cnaud

Page Tools