2.2 Device Communication

In order for Indeni to run its full set of intelligent knowledge checks, you need to Create a User in the management system for the device you want to add, then add that user to a Credential Set. We recommend creating a unique Indeni user for auditing and security purposes.

The privilege level required varies depending on the device type. When possible, we avoid the need to use an administrative account for accessing the device, but in some cases, it cannot be avoided due to limitations to the network device.

If communication between Indeni and the analyzed devices passes through a firewall, please allow the following:

  • SSH (TCP 22) – Used for collecting information from the analyzed devices.
  • HTTPS (TCP 443)
  • Ping (ICMP Echo) – Devices are pinged regularly by Indeni to ensure they are responding.
  • SNMP – Used for collecting information from the analyzed devices.

Please see the below chart for vendor port requirements:

Common Communication Issues

If the Indeni server is unable to communicate with the device, it will return an error.  The most common reasons for a communication issue are:

  1. An issue with the credentials – either 
    1. You have mis-typed the username/password in the Credential Set
    2. The device’s IP Address is not in the subnet(s) assigned to the Credential Set
    3. Those credentials don’t exist on that device or don’t have the correct permissions
  2. Connectivity issues between the device and the Indeni server.  This could be
    1. Basic connectivity between Indeni server and device.  The easiest way to test this is to logon directly to the Indeni server’s Linux interface and ping the device.
    2. SSH connectivity between the Indeni server and the device.  Validate that SSH is enabled on the device using port 22.