Welcome, Guest. Please login or register.

Recent Posts

Pages: 1 ... 8 9 [10]
91
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
92
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.
93
Definition Files / Re: search def for WS-C2960-8TC-S
« Last post by dobst on January 23, 2018, 01:09:31 PM »
Update: Removed leading space in type description

Code: [Select]
# Definition for 1.3.6.1.4.1.9.1.1006 created by Defgen 1.8 on 23.Jan 2018 (admobst)
 
# General
SNMPv 2HC
Type WS-C2960-8TC-S
Typoid
Sysdes
OS IOS
Icon w3bp
Size 1
Bridge VLX
ArpND oldphy
Dispro LLDPXN|CDP
Serial 1.3.6.1.2.1.47.1.1.1.1.11.1001
Bimage 1.3.6.1.4.1.9.2.1.73.0
CfgChg 1.3.6.1.4.1.9.9.43.1.1.1.0
CfgWrt 1.3.6.1.4.1.9.9.43.1.1.3.0
VLnams 1.3.6.1.4.1.9.9.46.1.3.1.1.4.1
VLnamx
Group 1.3.6.1.4.1.9.9.46.1.2.1.1.2.1
Mode 1.3.6.1.4.1.9.9.46.1.2.1.1.3.1
 
# Interfaces
StartX
EndX
IFname 1.3.6.1.2.1.31.1.1.1.1
IFaddr oldadr
IFalia 1.3.6.1.2.1.31.1.1.1.18
IFalix
InBcast 1.3.6.1.2.1.31.1.1.1.9
InDisc 1.3.6.1.2.1.2.2.1.13
OutDisc 1.3.6.1.2.1.2.2.1.19
IFvlan 1.3.6.1.4.1.9.9.68.1.2.2.1.2
IFvlix
IFpowr 1.3.6.1.4.1.9.9.402.1.2.1.9.1 S
IFpwix 1.3.6.1.4.1.9.5.1.4.1.1.11.1
IFdupl 1.3.6.1.2.1.10.7.2.1.19
IFduix
Halfdp 2
Fulldp 3
 
# Modules
Modesc 1.3.6.1.2.1.47.1.1.1.1.2
Moclas 1.3.6.1.2.1.47.1.1.1.1.5
Movalu 10
Moslot 1.3.6.1.2.1.47.1.1.1.1.7
Modhw
Modsw
Modfw 1.3.6.1.4.1.9.9.13.1.3.1.3
Modser 1.3.6.1.2.1.47.1.1.1.1.11
Momodl
 
# RRD Graphing
CPUutl 1.3.6.1.4.1.9.9.109.1.1.1.1.8.1
Temp
MemCPU 1.3.6.1.4.1.9.9.48.1.1.1.6.1
Custom MemIO;G;Bytes 1.3.6.1.4.1.9.9.48.1.1.1.6.2
94
Discovery / No Config-Backup after Change
« Last post by markus on January 23, 2018, 08:45:19 AM »
Hey all!

We have some issues with the Config-Backup feature on Cisco devices...
The initial backup with -B10 is working properly on every device. SSH and SNMP are working properly too. The OID for ConfChange is 1.3.6.1.4.1.9.9.43.1.1.1.0 and for ConfWrite is 1.3.6.1.4.1.9.9.43.1.1.3.0, they are updated properly.
When I change the config without write, NeDi shows the Exclamation Mark in Device-Status.

The Value cfgchange in devices Table is updated too, when i Change the config.
When I run nedi.pl with -b or -B10, it says "DISC:Config hasn't been changed. Not backing up."  :(

So, when everything is updated and working good..... I do not find the reason, why does NeDi not back up the config.....

We are using the following NeDi, installed with the very great nebuntu.sh   :-*
/var/nedi/nedi.pl version 1.6.100 calling Getopt::Std::getopts (version 1.12 [paranoid]),
running under Perl version 5.26.0.
95
News / Optical Monitoring
« Last post by rickli on January 22, 2018, 05:44:16 PM »
A question for you experts. Would you agree to monitor send and receive signal strength would be the most important?
Also, would it suffice to test against a minimum threshold or do we need to test against a maximum threshold as well?

I'm looking at getting this feature into 1.8, but I don't want to snmpwalk more OIDs than absolutely necessary...

Another open issue, do I assign the optics to the interfaces or the modules? Depending on equipment vendor one is easier than the other. However, I lean towards modules because the DB structure won't need changing and would be more efficient (rather than adding unused fields on thousands of copper ports).
96
Installation / Re: Upgrade from 1.5 to 1.6
« Last post by pc_sg on January 19, 2018, 08:20:43 AM »
No answers...
So I did the manual update (replaced files from tgz file, reinitialized database with "./nedi.pl -i", new disocovery, but now I've a new problem: first discovery get the right cli credentials, subsequents returns


PREP:No working user
DISC:Clistatus = no working user


What can I do?


Thanks in advance.


P.S. which is the right command line syntax to obtain "cli" debug? Old syntax seems no more working.
97
Definition Files / WS-C2960S-24TS-S 1.3.6.1.4.1.9.1.1257
« Last post by dobst on January 17, 2018, 08:52:14 AM »
Code: [Select]
# Definition for 1.3.6.1.4.1.9.1.1257 created by Defgen 1.8 on 17.Jan 2018 (admobst)
 
# General
SNMPv 2HC
Type WS-C2960S-24TS-S
Typoid 1.3.6.1.2.1.47.1.1.1.1.13.1001
Sysdes
OS IOS
Icon w2an
Size 1
Bridge VLX
ArpND old
Dispro CDP
Serial 1.3.6.1.4.1.9.3.6.3.0
Bimage 1.3.6.1.4.1.9.2.1.73.0
CfgChg 1.3.6.1.4.1.9.9.43.1.1.1.0
CfgWrt 1.3.6.1.4.1.9.9.43.1.1.3.0
VLnams 1.3.6.1.4.1.9.9.46.1.3.1.1.4.1
VLnamx
Group 1.3.6.1.4.1.9.9.46.1.2.1.1.2.1
Mode 1.3.6.1.4.1.9.9.46.1.2.1.1.3.1
 
# Interfaces
StartX
EndX
IFname 1.3.6.1.2.1.31.1.1.1.1
IFaddr old
IFalia 1.3.6.1.2.1.31.1.1.1.18
IFalix
InBcast 1.3.6.1.2.1.31.1.1.1.3
InDisc 1.3.6.1.2.1.2.2.1.13
OutDisc 1.3.6.1.2.1.2.2.1.19
IFvlan 1.3.6.1.4.1.9.9.68.1.2.2.1.2
IFvlix
IFpowr
IFpwix
IFdupl 1.3.6.1.4.1.9.5.1.4.1.1.10
IFduix 1.3.6.1.4.1.9.5.1.4.1.1.11
Halfdp 1
Fulldp 2
 
# Modules
Modesc 1.3.6.1.2.1.47.1.1.1.1.2
Moclas 1.3.6.1.2.1.47.1.1.1.1.5
Movalu 6|9|10
Moslot 1.3.6.1.2.1.47.1.1.1.1.7
Modhw 1.3.6.1.2.1.47.1.1.1.1.8
Modsw 1.3.6.1.2.1.47.1.1.1.1.10
Modfw 1.3.6.1.2.1.47.1.1.1.1.9
Modser 1.3.6.1.2.1.47.1.1.1.1.11
Momodl 1.3.6.1.2.1.47.1.1.1.1.13
 
# RRD Graphing
CPUutl 1.3.6.1.4.1.9.9.109.1.1.1.1.8.1
Temp 1.3.6.1.4.1.9.9.13.1.3.1.3.1008
MemCPU 1.3.6.1.4.1.9.9.48.1.1.1.6.1
Custom MemIO;G;Bytes 1.3.6.1.4.1.9.9.48.1.1.1.6.2
98
GUI / Assets Management
« Last post by Alimachina on January 16, 2018, 10:23:34 AM »
Hi,
I'm using the 1.5 version and have some trouble with the Assets Management module and Serial numbers.

The inventory don't update automatically : the devices are mark at "No Inventory" after the 1st discovery but don't update after next discovery.
If I manually add a device as "Active", it'll remain "Active" even if the device isn't and the next discovery can't find it.
And same, if I put a device as "Inactive" (then I delete the device, like if it's put in stock) and I reuse the device later (a new discovery show it up) it'll stay mark as "Inactive".

In the NeDi Yt videos, we can see it update itself after a new discovery.

Maybe I missed something ?
99
Definition Files / Re: Cisco 3850 stack def
« Last post by tristanbob on January 12, 2018, 12:36:22 AM »
Cisco has released the Catalyst 9300 (which is really just a 3850X).   I used the 3850 stack .def file below:

Code: [Select]
sudo cp 1.3.6.1.4.1.9.1.1745.def 1.3.6.1.4.1.9.1.2494.def
sudo chown www-data:www-data 1.3.6.1.4.1.9.1.2494.def

Just replace "38xx" with "39xx" and this is working great for us!

Tristan
100
Discovery / Re: Multiple CDP neighbors on a single port
« Last post by rickli on January 11, 2018, 10:42:27 PM »
You need to set it on that particular port in Devices-Interfaces not in nedi.conf...
Pages: 1 ... 8 9 [10]