TeemIp IP Discovery Extension represents the TeemIp side of TeemIp IP Discovery solution. It defines the discovery parameters and allows discovery results to be fed back and displayed.

Reminder: TeemIp IP Discovery provides a solution to TeemIp administrators to discover or scan their IP networks and to document within TeemIp the results of these discoveries and scans.

The solution is made of 2 components:

• a discovery engine, called the IP Discovery Collector or the IP Discovery Application, that discovers IPs through pings, DNS reverse lookups and port scanning,
• a TeemIp extension, called the IP Discovery Extension, that adapts TeemIp's standard data model to store the discovery outputs and enables communication between a TeemIp instance and the different discovery engines deployed on the network.

The IP Discovery extension, which is described in this page, is installed on a TeemIp instance. It models the IP Discovery applications that are connected to TeemIp and display the output provided by these applications.

Each instance of a remote IP Discovery Application defines:

• what discovery method to use (ping and / or IP lookup and / or port scanning),
• what subnets to discover.

A given subnet can only be discovered by one remote application and the functions to be used for its discovery can be restricted: ie deny ping, IP lookup or scan if these have been enabled globally.

TeemIp IP Discovery extension is licensed under the terms of the GNU Affero General Public License Version 3 as published by the Free Software Foundation. This gives you legal permission to copy, distribute and/or modify TeemIp IP Discovery under certain conditions. Read the ’license.txt’ file in the distribution. TeemIp IP Discovery is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.  

The nice binocular icon attached to the IP Discovery Application in TeemIp has been found on IconFinder and Icons Land.

Discovery of IPv6 networks is not handled at this stage.

The extension doesn't require anything more than what is necessary to install and run TeemIp.

When adding the extension on an TeemIp standalone or iTop application, just use the standard installation process.

No specific configuration is required in TeemIp's configuration file or in IP configs for that extension.

Once installed, the extension will alter the IP Management menu by adding a sub menu group under the Tools section.

It provides statistics on IP addresses and discovery results.

Clicking on the count figure next to an IP Discovery application provides the list of subnets discovered by the given application.

The IP Discovery applications shorcut displays all the applications that belong to the selected organization.

These objects define the remote applications that actually perform the discovery work. They enable these remote applications to communicate with TeemIp, list the subnets to be discovered and define how they should be discovered.

From the listing view, click on the “New…” menu to display the creation form.

• UUID attribute uniquely identifies the remote IP Discovery application and must be unique across TeemIp, regardless the organization it belongs to. UUID is automatically generated by TeemIp when the application is created.
• Ping, IP Lookup and Scan functions can be enabled or disabled globally for the application. If enabled, these function can be disabled individually for each subnets to be scanned.
• DNS Server #1 and #2 can either be an IP address or a domain name.

The extension enhances the IP Subnet datamodel so that an IP discovery application can look after them. For that purpose, the following attributes are added:

IP discovery attributes alter the subnet detailed page as follows:

The 3 attributes Ping, IP lookup and Scan enabled for subnet may change the way the subnet's IP discovery application will discover the subnet:

• If one of these 3 discovery functions is enabled at the application level, it may be denied at the subnet level.
• However, if a function is disabled at the application level, it cannot be enabled at the subnet one.

The IP Discovery Module alters the standard TeemIp datamodel so that discovery results can be visualized at both the subnet and the IP address levels.

From the detailed display of a subnet, selecting 'List & Pick' under 'Other Actions' menu will show:

The following image may appear next to each IP of the subnet:

• indicates that an IP pings,
• indicates that an answer is received when IP is scanned,
• indicates that a DNS entry exists for that IP and DNS output is provided just after the icon.

These flags reflects the latest status provided by the remote application. If an IP was pinging in the past and if the latest discovery finds out that this IP doesn't ping anymore, then the ping image will not be shown anymore.

Discovery flags (, , ) will never appear next to an IP that doesn't exist within TeemIp. This is due to the default behaviour of the application: newly discovered IPs that don't exist in TeemIp are automatically created with the status “unassigned”.

The IP Discovery Module alters as well the IPAddress datamodel so that discovery informations related to IP addresses can be displayed at their level. The following attributes are added:

IP discovery attributes alter the address details screen as follows:

• The IP discovery application is inherited from the subnet that that IP belongs to.
• All IP discovery parameters are, of course, read only as they are the result of the discovery process.

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” menu offers the possibility to explode this FQDN into a short name and a domain name and to register them as IP attributes. This action is highlighted in the red circle of the image above.

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: