Welcome, Guest. Please login or register.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ghermant

Pages: [1]
Discovery / Cisco EoL information upload
« on: June 22, 2020, 12:24:25 PM »
It is mentioned in the NeDi Guide that it is possible to upload the Cisco EoL date and information (ciscoeol.tgz) in NeDi.

Do you know how to use it and what is the format?


Installation / Re: Issue updating from 1.7 to 1.8
« on: June 08, 2020, 04:41:16 PM »
Hi, if this can help (I faced the same kind of issue as I forgot to run the updatedb stuff after upgrading...) here is a small procedure I tested on production environments to update the DB schema and structure to your current NeDi files and scripts version.

1/ Identify the current version of NeDi DB
Go to System/Database, find the System table and click on Show icon (eye icon) and take a note of the current NeDi DB structure version.

All the trick is done by replacing your current /nedi/inc/libdb.pm with an older version so that this older version will do the required database upgrade for you without touching the other NeDi files.

I have attached to the post the original libdb.pm files for NeDi version 1.7 and 1.8.
If you prefer to extract them on your own, you have to download the NeDi install files for both 1.7C and 1.8C from www.nedi.ch, extract them and get the libdb.pm in the /inc directory.

2/ Please make a backup of your current libdb.pm file:
# cp -p libdb.pm libdb.pm.bak

3/ Stop all NeDi active background processes.

4/ If your current version of NeDi (files and scripts) is 1.8:
If the version shown in the NeDi DB is 1.6xx or 1.7
--> copy libdb.pm.1.7 to /nedi/inc/
Replace the current libdb.pm with the libdb.pm.1.7 file:
# cp libdb.pm.1.7 libdb.pm

Go to the NeDi web interface in System/NeDi and select "reset" after making sure that the login field contains "updatedb" and then execute.
The DB should update correctly to the 1.7.100 version

Then, copy libdb.pm.1.8 to /nedi/inc/
Replace the current libdb.pm with the libdb.pm.1.8 file:
# cp libdb.pm.1.8 libdb.pm

Go to the NeDi web interface in System/NeDi and select "reset" after making sure that the login field contains "updatedb" and then execute.
The DB should update correctly to the 1.8.100 version.

Do not forget at the end to recover your original libdb.pm file:
# cp libdb.pm.bak libdb.pm

Hope this will help you and will avoid you to go through all files upgrade process that is very impacting if you made any customisation to your def files...

Installation / Re: Radius Web Authentication - Reply Attributes
« on: January 31, 2020, 05:16:15 PM »
Hello any update on this questions?


Discovery / Nodes names not resolved - how to debug?
« on: January 28, 2020, 11:17:41 AM »
I have an issue to do reverse lookup on discovered nodes IP.
It seems that NeDi is not performing any reverse lookup when new node are discovered.

Using DIG on server CLI, I am able to reverse lookup manually the IP of the discovered nodes so I suspect the issue is within NeDi.

How can I debug it and is there any basic stuff I would have forgotten to activate in NeDi to have these node IP reverse lookups?


Discovery / Net::Nslookup not available
« on: January 28, 2020, 11:10:32 AM »
I have been using NeDi for along time and recently noticed that every time I kick off NeDi.pl, the first line says that Net::Nslookup is not available when I run the script as NeDi user.

DNS :Net::Nslookup not available
CLI :IO-Pty loaded
WEB :LWP-UserAgent loaded

when I run it as root, the module looks to be available to NeDi script:
DNS :Net::Nslookup loaded
CLI :IO-Pty loaded
WEB :LWP-UserAgent loaded

The Net::Nslookup module is correctly installed on the server and I tested it with a basic script.
Is there any way to fix it or to debug?


Installation / Re: Update MAC Vendor OUI Database?
« on: January 03, 2020, 12:53:56 PM »
How to make this OUI update to work with NeDi 1.7?
It seems that the -N option refers to IP or names in 1.7.

[nedi]$ perl /var/nedi/nedi.pl -v -N oui
CLI :IO-Pty loaded
Invalid IP: oui.1.1.1 at /var/nedi/nedi.pl line 192.


News / Re: NeDi 1.8 to be made available to the community?
« on: October 11, 2019, 10:27:35 AM »
Looks to be a good hint ascii!  ;D


Database / Empty snapshots in NeDi 1.7
« on: October 11, 2019, 10:20:38 AM »
Whenever I try to perform a snapshot on my NeDi server using the System/Snapshot menu it ends up with an empty db:

(see screenshot)

Do you know what is going wrong here?

Thanks & Brgds,

News / NeDi 1.8 to be made available to the community?
« on: October 10, 2019, 01:38:06 PM »
Hello Rickli,
Do you know when NeDi 1.8 will be released to the community?

Best Regards,

Discovery / Re: Prevent NeDi to connect to Cisco IP phones web page
« on: June 19, 2019, 12:48:43 PM »
Got it, just found that -SW will prevent NeDi from connecting using HTTP/S to the phones.



Definition Files / Re: assistance with Palo Alto .def files
« on: June 19, 2019, 10:07:53 AM »
Hello Rickli,
Could you please send me the def files package you are using for Palo Alto?

Thanks in advance.

Discovery / Prevent NeDi to connect to Cisco IP phones web page
« on: June 19, 2019, 10:00:58 AM »
I am trying to find out a way to prevent NeDi from trying to access Cisco IP Phones web pages when an IP Phone is discovered as a CDP/LLDP neighbour.

The phones have their web page disabled and this web connection try and timeout increases the discovery duration.

Thanks for your help.


Definition Files / Re: assistance with Palo Alto .def files
« on: June 14, 2019, 09:53:39 AM »
Could you please post your Palo Alto working def files?

We have a bunch of them and we are struggling to get at least IP  on Interfaces.

Thanks in advance.


Discovery / SNMP v3 with AES or DES but with same community name
« on: December 04, 2018, 04:57:09 PM »

We have some devices that were configured to use SNMP v3 with AES encryption and some other older devices with DES.

For both of these devices, we used the same community name and the only difference between them is the encryption method (AES or DES).

I found an issue in Nedi (1.7) that does not allow to have both of these SNMP communities defined in the nedi.conf file.

Like this:
#           name   aprot   apass      pprot   ppass
comm   mycomm   sha           ver3pa55           aes           ver3pa55
comm   mycomm   sha           ver3pa55           des           ver3pa55

If I test the above config for a discovery on a DES device, it fails and Nedi do not even test the second community.
It looks like Nedi considers the second one using AES as the same one as the DES one.

It is even worst as this look also that the encryption method is not stored in the database and associated to a device:
If a device were discovered using DES but the nedi.conf file contains the AES one, refreshing the device fails as it read the encryption method indicated in the nedi.conf file.

Would you know how to update the libsnmp.pl lib so that Nedi first test in AES and fallback in DES if needed or store this parameter by device in the DB?

Thanks & Brgds,

News / Nedi 1.7 to be made available to the community?
« on: September 12, 2018, 10:42:00 AM »
Do you know if and when Nedi 1.7 will be released to the community?


Pages: [1]