Part 2: Getting Started

1. Preparation

Indeni Server

  • The Indeni Server will require an IP Address (along with the Subnet Mask and Gateway). This IP Address will require SSH (port 22) and SSL (port 443) access to the devices being inspected.  
  • The IP Address should also be able to reach on ports 80 and 443 (http and https). This is for the server to upload logs if needed, download new versions as they are released and for sending a heartbeat
  • You will also need to know the IP Address of the preferred DNS and NTP servers.

Inspected Devices

In order to connect to these devices, we will need to know:

  • The IP Address of the devices.
  • That SSH is enabled and using the default port 22.
  • The credentials (username and password) for the devices.

2. Install Indeni

See 1.2 Installation for installation instructions.

3. Install the Indeni License

If you are running the “POC” version, you will receive a License from your Sales Executive. In the Indeni webUI, browse to Settings > About and click the “Upload License” button to apply the Indeni License.

4. Connect Devices for Inspection

4.1 Create users on Vendor Devices

In order for full automation to take place, a unique Indeni user must first be created with the appropriate permissions. See 2.1 Creating Users on Vendor Devices.

4.2 Create Credential Sets

The first step to inspecting your devices is to create the credential set – the logon credentials that will be used to query the devices. See 5.1 Credential Sets for instructions.

The credentials also include the Subnet which will use those credentials.  If all of your devices are using the same credentials, you can simply set this to to have it apply to all devices.  Otherwise, if your devices use different credentials, you can create multiple credential sets, and then specify the Network and Mask for each (which can be an exact IP Address such as or a subnet such as

If there are overlapping Subnets (such as and, the Indeni server will try to connect using the most specific Subnet.  If those credentials fail, it will then try the next most specific Subnet.  So in our example, the /32 subnet would be tried first and then the /16 subnet.

4.3 Add Devices

Next, you can add the devices you want to inspect.  You just have to provide a Name for the device and the IP Address. Indeni will interrogate the device (using the credential sets you have created) to determine the device Vendor, OS, etc. Further information about adding devices in 5.2 Adding Devices.

BlueCat acquires Indeni to boost its industry-leading DNS, DHCP and IP address management platform to help customers proactively assess network health and prevent outages.