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 - rickli

Pages: [1] 2 3 ... 151
1
Installation / Re: DOM values
« on: October 11, 2019, 10:06:26 AM »
Yes, by adding the different types (as reported by switch) and thresholds to nedi.conf:

dom-alert   CCM-1241   3   -10   3   -12   default-settings

2
Other / Re: Asset suggestion
« on: October 11, 2019, 10:04:32 AM »
Interesting suggestion, duly noted. Also nice to hear people are using or at least looking into the asset management features :-)

3
Discovery / Re: VRF Discovery on Nexus 7k
« on: October 11, 2019, 10:00:45 AM »
I'm working on this for NeDi 2.0. I plan to add the VRF method to the definition for every device...

4
Discovery / Re: Using arpwatch tables to import IP's to Nedi
« on: October 11, 2019, 09:59:32 AM »
Yeh, gonna make it official today :-) I'm busier than usual, hence the silence over here...

5
Discovery / Re: Using arpwatch tables to import IP's to Nedi
« on: September 05, 2019, 02:37:57 PM »
Ups, I meant SSH not SNMP. They don't support that Mib...

6
Installation / Re: Nedi 1.9
« on: September 05, 2019, 02:33:58 PM »
This can be seen on various Nedi versions. I don't really know why it occurs, but apparently the encoding should be set upon creating the DB. I'll do this in coming NeDi versions from now on...

In order to fix exiting DBs (NeDi 2.0 will have templates in System-Database):
LTER DATABASE nedi DEFAULT COLLATE utf8_unicode_ci;

Then execute this for every table showing a warning (e.g. devices):
LTER TABLE devices CONVERT TO CHARACTER SET utf8;

Add an A at the beginning (can't post the proper query due to security :-)

7
Discovery / Re: Using arpwatch tables to import IP's to Nedi
« on: August 19, 2019, 10:07:32 AM »
You might as well just upgrade to 1.8 as it supports reading Palo's ARP cache via SNMP. It'll be relased officially in a few weeks :-)

http://www.nedi.ch/pub/nedi-1.8C.pkg

8
Discovery / Re: Cisco backup config error
« on: August 19, 2019, 10:00:33 AM »
Did the SSH keys change on the switches and you have "known" set in nedi.conf? In that case you could simply update the keys with nedi.pl -kK ...

9
Discovery / Re: Cisco backup config error
« on: August 06, 2019, 11:02:25 AM »
I know this can be frustrating at times (and I should renew the CLI tutorial)...

If you add -dc the log files should be created, where you can exactly see what's sent and received. Try uncommenting only those credentials that are supposed to work on those devices (or log files get overwritten).

One scenario could be that the banner (or some other output) is interpreted as error. But this should be seen in the log as well.
I did improve this in 1.8, which will be public soon. So it might be worth the wait...

10
Discovery / Re: CDPD link changed on discovery
« on: July 22, 2019, 11:05:26 AM »
Tx for the feedback. I'll release 1.8 to the public soon, which will ignore phone links...

11
Unfortunately Microsens' SNMP implementation is buggy. If you set LLDP in the .def you'll see a bunch of errors (because they do not use a 14th field in the OID). I'm more than happy to help, if they're willing to fix it :-)

12
Did this work with the old version? Anyhow, open the Definition (Geo-triangle in Devices-Status) and change the MAC Address selectbox to "Q-bridge" or "Q-bridge indexed". Write the .def and discover to check...

13
Discovery / Re: Dicovery - Netfilter error.
« on: July 05, 2019, 10:14:38 AM »
Simply append it to the regexp |10\.99\.99\.

14
Discovery / Re: CDPD link changed on discovery
« on: July 05, 2019, 10:12:28 AM »
The change looks good to me. Do you see NeDi trying to discover the phone with SNMP? You probably have to add a match for the type in nedi.conf nosnmpdev.

15
Discovery / Re: CDPD link changed on discovery
« on: June 24, 2019, 12:17:22 PM »
Phones should create CDPF links, which won't create notifactions like that. So the proper fix is to have those phones properly recognised. How good are your Perl skills? :)
Look at the function Disprot() in libsnmp.pm, if you dare. There's a section where all the phones are defined. Simply add another if for yours to match (look for $main::dev{$neb{$i}{$n}{'na'}}{ic} = "phon";). I can help in a remote session, if you want. Just send me a mail...

Pages: [1] 2 3 ... 151