Welcome, Guest. Please login or register.

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Discovery / two Cisco ASAs with same name
« Last post by AndyConnock on February 12, 2018, 11:43:47 PM »
been experimenting with NeDi over a week now.  got it up and running (youtube vids came in very handy).  currently making my way thru discovery debugging and figuring it all out but i've hit a bit of a stumbling block.

i have two ASAs, a production (x.y.x.254 address) and failover (x.y.z.252 address).  seems both have the same fqdn "ciscoasa" so of course, each time one is discovered it replaces the "ciscoasa" device record with the diff IP and SN etc each time a discovery takes place.

seeings how nedi requires unique device names, is there any kind of trick i can use to have the two devices show up separately without resorting to modifying the name of the device on the ASA itself...  i'm not sure what effect that will have and don't really want to risk it.   ;D
12
Discovery / Re: No Config-Backup after Change
« Last post by markus on February 01, 2018, 09:19:30 AM »
I have edited line 1674 in libmisc.pm from
Code: [Select]
if($skip =~ /s/ or $main::dev{$dv}{fs} == $main::now or $main::dev{$dv}{bup} ne 'A'){# Skip sysinfo or new devs force backup (or non-active are updated)
to that:
Code: [Select]
if($skip =~ /s/ or $main::dev{$dv}{fs} lt $main::now or $main::dev{$dv}{bup} ne 'A'){# Skip sysinfo or new devs force backup (or non-active are updated)
Now, NeDi reads the config every time, but the Datebase is only Updated when the Config has changed. That is want I want, but I do not think that I have done right....
13
Installation / Re: Upgrade from 1.5 to 1.6
« Last post by pc_sg on January 31, 2018, 08:56:27 AM »
Thanks.
I had to change "cliport = 0" in "device" table.
Even rare, another way to do it bulk will be useful.


Regards!
14
Installation / Re: Upgrade from 1.5 to 1.6
« Last post by rickli on January 30, 2018, 06:55:44 PM »
NeDi won't retry CLI access after if it didn't work the first time. Reset it in Devices-Status. To debug you can use -v -dc and look at the resulting input- and output.log files...
15
Installation / Re: Running moni.pl as a systemd service
« Last post by rickli on January 30, 2018, 06:54:06 PM »
Interesting, tx. I've been using startup scripts for Debian, CentOS etc. Is there an advantage of using systemd?
16
News / Re: Anyone using descfilter?
« Last post by rickli on January 30, 2018, 06:47:05 PM »
Tx for the feedback. This option only applies to the description read via SNMP and won't affect CDP, LLDP or nosnmpdev at all.

It only made sense in rare cases, that's why I'd like to replace it. It seems nobody is using it anyway :-)

17
News / Re: Optical Monitoring
« Last post by rickli on January 30, 2018, 06:44:37 PM »
Tx for the feedback. I'll add a skip option and try to find a way to assign them to the appropriate interface...
18
News / Re: Optical Monitoring
« Last post by gerold on January 29, 2018, 01:47:12 PM »
Hi Remo,

I haven't seen optical transmit or receive levels being out of range at our site.
Judging from my personal experience, monitoring the interface error counters is much more important.
So if this gets implement, please add a global option to enable/disable it. I would probably turn it off.

It's not that important where the values will be stored, but they should be displayed in the context of the corresponding interface.

YMMV.
19
Installation / Running moni.pl as a systemd service
« Last post by gerold on January 29, 2018, 11:52:40 AM »
Hi everybody,

since I no longer enjoyed  (re)starting moni.pl manually, I wrote the following service definition in order to let systemd care for the monitoring process.

Code: [Select]
$ cat /etc/systemd/system/nedimoni.service
[Unit]
Description=NeDi monitoring daemon for network infrastructure
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=nediusr
ExecStart=/opt/nedi/current/moni.pl
PrivateTmp=yes
Restart=always
RestartSec=180
#StandardError=syslog
IPAccounting=yes

[Install]
WantedBy=multi-user.target

To see that services status in NeDi, I patched System-Services.php as follows.

Code: [Select]
===================================================================
RCS file: ./RCS/System-Services.php,v
retrieving revision 1.1
diff -u -r1.1 ./System-Services.php
--- ./System-Services.php       2018/01/22 11:17:41     1.1
+++ ./System-Services.php       2018/01/22 11:29:04
@@ -134,6 +134,12 @@
 </tr>
 </table>
 <p>
+<h2>systemd moni status</h2>
+<div class="textpad code pre txta tqrt">
+$ systemctl status -l nedimoni.service
+<?= shell_exec('systemctl status -l nedimoni.service') ?>
+
+</div><br>
 
 <h2><?= $cmdlbl ?></h2>
 

Hope this helps!

Gerold
20
News / Re: Anyone using descfilter?
« Last post by mduling on January 24, 2018, 04:22:26 AM »
Hi Remo. It would be helpful if the comments for ignoredesc were more specific. For example, what desc is it looking for? lldp desc? I don't think CDP has a description field. Many of the lldp description fields devices report are generic such as 'Linux', but sometimes they're more specific.

For nosnmpdev, since I'm using that apparently "discovery protocol description" allows for using what CDP reports as 'Device ID', yet it would seem to also support CDP 'platform ID' since my regexp for that has one of each in it: AIR-([CL]|A)P|^S[EI]P

Also, does a match for nosnmpdev "not discover" as with ignoredesc? Not trying to get metaphysical here but since nedi is so uber flexible, sometimes I'm not sure what 'not discover' actually means. Does it mean not put it in the DB or put it in the DB but do nothing else with it? For nosnmpdev I know it means the latter. For ignoredesc I'm not sure.
Pages: 1 [2] 3 4 ... 10