This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
extensions:teemip-ip-discovery-extension [2022/09/30 11:53] – cnaud | extensions:teemip-ip-discovery-extension [2023/06/20 08:35] – [IP Discovery - Extension] cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{ icons8-binoculars-48.png}}====== IP Discovery - Extension ====== | + | {{ icons8-binoculars-48.png}} |
+ | ====== IP Discovery - Extension ====== | ||
---- dataentry summary ---- | ---- dataentry summary ---- | ||
name : IP Discovery - Extension | name : IP Discovery - Extension | ||
Line 5: | Line 6: | ||
index_hidden | index_hidden | ||
level_hidden | level_hidden | ||
- | version | + | version |
- | release_dt | + | release_dt |
- | TeemIp | + | TeemIp |
- | iTop : 2.7.x - 3.x | + | iTop : 3.x |
code : teemip-ip-discovery | code : teemip-ip-discovery | ||
localization | localization | ||
Line 17: | Line 18: | ||
keyword_tags | keyword_tags | ||
dependencies_s | dependencies_s | ||
- | download_wiki | + | download_wiki |
github_wiki | github_wiki | ||
- | php-max | + | php-max |
---- | ---- | ||
Line 254: | Line 255: | ||
In the case where IP lookup has been enabled for a subnet, discovery operations may return FQDN for IPs and it may happen that these FQDNs differs from the registered one. In such case, the "Other Actions" | In the case where IP lookup has been enabled for a subnet, discovery operations may return FQDN for IPs and it may happen that these FQDNs differs from the registered one. In such case, the "Other Actions" | ||
- | When the action is launched, TeemIp will try to best match a registered domain name within the FQDN. If found, the preceding characters in the FQDN will be considered as the IP's short name, as long as it complies with the hostname format Our above example will give: | + | When the action is launched, TeemIp will try to best match a registered domain name within the FQDN. If found, the preceding characters in the FQDN will be considered as the IP's short name, as long as it complies with the hostname format. Our above example will give: |
{{ classdetails_ipv4address_ipdiscovery3x_nomenu.png }} | {{ classdetails_ipv4address_ipdiscovery3x_nomenu.png }} | ||
Line 261: | Line 262: | ||
* The **Explode discovered FQDN** menu is available at Subnet, IP range and IP levels... as long as the IP Lookup has been authorized in the discovery parameters of the related subnet. | * The **Explode discovered FQDN** menu is available at Subnet, IP range and IP levels... as long as the IP Lookup has been authorized in the discovery parameters of the related subnet. | ||
* When applied at Subnet or IP range level, all IPs contained in them will have their discovered FQDN exploded, if feasible. | * When applied at Subnet or IP range level, all IPs contained in them will have their discovered FQDN exploded, if feasible. | ||
+ | </ | ||
+ | <note warning> | ||
+ | The **Explode discovered FQDN** menu will not appear if there is no domain name that can match with the discovered FQDN ! | ||
</ | </ | ||