Recent Posts

81

Discovery / Re: no interface colors on Device-Status-page

« Last post by miraculiks on May 02, 2023, 08:44:15 am »

Thanks for the hint. Works for me, too. However, there seem to be a number of differences between both old and new "Devices-Status.php". I will monitor whether there are interoperability problems with new modules.

82

GUI / Re: Devices list in cli write

« Last post by ahl on April 30, 2023, 12:09:16 pm »

Just in case it could help some one here ..
It did work without issue after copying the list from a text editor instead of an excel sheet ..
I don't know the reason behind that ..

83

GUI / Devices list in cli write

« Last post by ahl on April 30, 2023, 08:57:21 am »

Hi All;

I am trying to use the devices list on the cli write page but I get as a result "no devices".
Can we use IP addresses list or we have to use Devices names .. I tried both lists.

Regards and thanks in advance.

84

Discovery / Bug in 2.2 ?

« Last post by swepart on April 29, 2023, 01:33:37 am »

after updating from 2.1 to 2.2 the POE values ​​end up on the wrong interfaces, in discovery the correct interface is identified, so also in the "connection box", but in the interface list it is completely wrong.
I am using the same definition file in both versions and I messed around with ifnx and different POE mibs without luck

For now I have only seen it on IOS-XE based switches like Cisco 9200,9300

NeDi environment
Ubuntu 20.04
MariaDB 10.3.38
Nginx 1.18.0
PHP 7.4.3
NET-SNMP 5.8


See screencopies  below

85

GUI / Link Type Errors

« Last post by ukmuenster on April 24, 2023, 09:34:46 am »

Hi Nedi Community,

Question:
How can I correct link type errors (Topology/Linked)? We only use LLDP on all devices. Nevertheless, there are about 2 dozen devices in our network in NeDi, where one neighbor sees the other via LLDP, but a MAC link is displayed vice versa. Via CLI I can recognize the neighbor via LLDP on both devices.

Kind regards

Rainer

86

Discovery / Re: no interface colors on Device-Status-page

« Last post by cmesser on April 21, 2023, 08:50:34 am »

Hi,

I just updated 2.2 and noticed the same issue.
So I tried to copy the "Devices-Status.php" from the 2.1 package to the html sub directory.
This works, and also, it seems to be much faster displaying the interface list.

Regards

87

Discovery / Re: Cisco WLCs

« Last post by networkbo on April 08, 2023, 08:28:08 pm »

Hi all, I tried to change Operating System to IOS XR and configuration backup worked 

88

Discovery / Re: snmpdev

« Last post by mduling on March 31, 2023, 02:39:40 am »

Ok I figured it out. I assumed the text displayed during the discovery run was the system name or whatever I needed to match. But it isn't necessarily. For each device type that gave snmp timeouts I did an 'show lldp neighbor detail' and used part of the device description and it works. But the name may be very different from what the discovery script shows.

89

Discovery / Re: Parameter for SNMPv3 with SHA256 and AES

« Last post by MPell on March 23, 2023, 11:00:03 pm »

Hi Remo,

you made out the point. Using the patched USM.pm works like a charme. Thanks a lot for the hint!

Best regards, Markus

90

Discovery / Re: snmpdev

« Last post by mduling on March 23, 2023, 10:10:32 pm »

Maybe I don't understand how nosnmpdev works. I assumed it was to recognize the names of nodes via CDP/LLDP to not try to walk with snmp so we wouldn't see all the "SNMP failed" and associated timeouts slowing down discovery. But maybe the purpose of nosnmpdev is not to put those devices in the mysql database?

I do want the MAC/IP/OUI of nodes that I don't know the SNMP string of to be in the database, I just don't want the SNMP timeouts slowing down the discovery.

Is there a way to accomplish this? Thanks!