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 ... 140
LAN/Switching / Re: Feature request: Stack monitoring/Error detection.
« on: September 13, 2017, 04:21:18 PM »
1.6 will definitely support most things I mentioned. I'll make it public next month...

Database / Re: Populate network devices in Nagios from NeDi
« on: September 13, 2017, 04:19:55 PM »
Cool, thanks for contributing your work!

LAN/Switching / Re: Feature request: Stack monitoring/Error detection.
« on: September 01, 2017, 12:15:23 PM »
Nope, you're right :)

In the meantime NeDi learned to deal with stacks. If a member disappears, the change in stack size will be reported. You can also forward this event as email or raise its level with that it appears red-flashy in Monitorin-Health.

Definition Files / Re: Dlink DGS-1510 def files and some questions
« on: September 01, 2017, 12:11:45 PM »
1: Compare with the ESX .def. You can use the 2 OIDs, which will be used to calculate the difference of the results
2: Is the result an integer? Otherwise I don't have an idea to make this useful

Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: August 10, 2017, 03:47:55 PM »
IFvlix is required if the portindexes in the PVID table differ from the actual IF-indexes. It can't be the same OID as for PVIDs...

Discovery / Re: Across WAN discoveries
« on: August 10, 2017, 03:45:55 PM »
In general phones should not be contaced though. What version of NeDi and what kind of phones do you have?

Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: July 14, 2017, 10:55:19 AM »
There's a bunch of similar ones available (check with nedi.pl -y). I'd use this one as template:
Juniper             Ex4200              

GUI / Re: Scheduled downtime for devices
« on: July 11, 2017, 11:43:31 AM »
Good question and I'm sure everybody encounters this situation. The monitoring service can be stopped in System-Services, but the proper approach is the maintenance mode (explained at 45:05): https://youtu.be/K5YuPGyQMmg?list=FL1aYM5K5bXjuU4cBy2FpY3g

« on: July 09, 2017, 07:17:18 PM »
I suspect slow DNS servers can cause such issues, as NeDi blocks the DB while waiting for an answer. I'll change this, but you can try with -n to see if it makes any difference.

1. I once thought a int(10) would be enough to hold broadcasts within a discovery. Turns out it isn't! It's initialized with int(20), but older DB's still have int(10).

2. Similarly it can happen that wlan controllers return a very long username like "Remo's MACbook or even more nonsense". Depending on your DB settings it just gets truncated or a screetching halt (your case). I'll be changing libdb.pm line 1867 in 1.7p1 to:

my $user   = $dbh->quote($m->{$dv}{$mcvl}{us}?substr($m->{$dv}{$mcvl}{us},0,30):'');

Limiting to 30 characters to hold escapes characters for singlequotes. Still might need work on ever stranger usernames!

Discovery / Re: Manually Adding / Importing Devices?
« on: June 28, 2017, 03:24:22 PM »
Great to hear, thanks for the feedback! Hope it becomes so important that you want to buy the subscription ;)

You can create devices by directly inserting them into the devices table or by clicking the "green plus" in Devices-Status...

There's even a cloudlink.pl script that can create virtual links to such manually added devices (to represent provider clouds for example)

Discovery / Re: Problem discovery Switch Huawei
« on: June 28, 2017, 03:20:20 PM »
Looks like the PVID is not indexed to the correct if-indexes. You can define a PVID Index in Defgen to have it mapped correctly.

I don't know the correct OID for Huawei, but it should be documented somewhere in their MIBs. Perhaps it's somewhere near

Definition Files / Re: Please remake the need for defgen in Nedi
« on: June 13, 2017, 10:31:55 AM »
Well MIBs only describe OIDs. You still need to know what to ask...

I've decided to skip MIBs 15 years ago to avoid the overhead. I went for individual .def files to avoid constraints between types as well...

15 years later I'm still happy with this decision as it is robust and pretty reliable.

In 1.7 I've added a new function to copy any existing .def over an unknown type. This will make life much easier!

Discovery / Re: Customizing the "Discover Now" button
« on: June 13, 2017, 10:25:05 AM »
Good point. It might make sense to make FQDN configurable in nedi.conf...

Good! the '@' could be supported in the hostname, but I've never encountered it before...

Anyone let me know, if this is required in future versions.

Pages: [1] 2 3 ... 140