A customer with a NetEye installation to which I had added the NeDi module asked me if I could integrate the saved configuration files of “discovered” network devices with NeDi.
NeDi, for those who are not yet familiar with it, is a Network Discovery tool based on many different network protocols.
The first action NeDi takes is to make sure that a network device is reachable via the network, and can inventory its components using the SNMP protocol.
It will therefore be necessary for network administrators to verify that:
NeDi will have to be configured for so that it will know:
The files responsible for configuring NeDi are:
You can choose whether to configure SNMP community in the seedlist file:
or run the configuration via the nedi.conf file:
where it is also possible to specify the configuration of the copy of the configuration file of devices subject to discovery, see this section:
If needed to fulfill security considerations, a hash can be entered in the pass field. In any case, access to the nedi.conf file is only allowed for the root user.
Having made the appropriate configuration changes, it’s now possible to customize the crontab file:
Here you should make use of the existing examples, or comment them out and instead insert your own desired crontab line:
Once you’ve finished the necessary configurations, you can launch the first scan, for example by using the following commands:
Consult the online help in nedi.pl to learn about syntax options, or make use of the graphical interface as shown here:
Did you read this article because you’re knowledgeable about networking? Do you have the skills necessary to manage networks? We’re currently hiring for roles like this as well as other roles here at Würth Phoenix.