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

Pages: [1] 2
1
Discovery / Re: CLI access fail on 20% of my switches
« on: March 28, 2017, 11:49:12 AM »
Hello Forum,

no one any idea how to fix this isse?

Any feedback would be very much appreciated.

piet

2
Discovery / CLI access fail on 20% of my switches
« on: March 14, 2017, 08:24:00 AM »
Hello Forum,

I run NeDi 1.5.225p3 on Ubuntu 16.04 with PHP 5.6.30 and MySQL 5.7

In general, this system runs as expected.

But for approx. 20% of my switches (all Cisco) the configuration backup fails with errror
Code: [Select]
Prepare (CLI) ----------------------------------------------------------------
SSH :admin@10.10.10.23:22 Tout:2s OS:IOS EN:[\w+().-]+#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l admin 10.10.10.23
ERR0:pattern match timed-out
EVNT:MOD=B/1 L=150 CL=cfge TGT=SWITCH23 MSG=Config backup error: connection pattern match timed-out

I set
Code: [Select]
usessh always in nedi.conf.

The failing device types are different, i.e. WS-C3750-24FS-S (IOS 12.2(53)SE2), WS-C2960-24PC-L (IOS 12.2(53)SE2), WS-C3560G-24TS-S (IOS 12.2(53)SE2).

I tried to run nedi.pl in debug mode (/var/nedi/nedi.pl -v -d -b -a 10.10.10.23) to get additional information with input.log and output.log, but I could not get these files being created. I run the nedi.pl command as user www-data.

Does anybody has any hint how to fix this isse or at least how to get input.log and output.log being created?

Many thanks

piet



3
NeDiO / Re: Fresh NoDiO14 installation - Network rrds are empty
« on: March 23, 2015, 01:53:30 PM »
Nobody any idea what could case this problem?

4
NeDiO / Fresh NoDiO14 installation - Network rrds are empty
« on: March 03, 2015, 08:13:03 AM »
Hello Forum,
in my fresh installed NeDiO14, the network rrds are empty - i.e. on the "Monitoring Health" page as well as in "Device Graphs/Network Totals".

The rrds of a single device are all ok.

piet

5
Discovery / Error messages during discovery
« on: May 07, 2013, 11:31:39 AM »
Hello Forum,

first of all a really big 'Thank you' to Rickly for thie new NeDi release  :)

I performed a fresh install of NEDIO8.

Unfortunately the following errors occur during discovery process:

After the discovery process of the devices, nedi says:
Building nodes
ooioonoUse of uninitialized value in gethostbyaddr at /var/nedi/inc/libmisc.pm line 1191.

I receive many of these messages.

After these message I recive many of the following lines:
Argument "NODENAME" isn't numeric in pack at /var/nedi/inc/libmisc.pm line 554.


Any idea what can cause thise problem?

Piet



6
Discovery / Re: SNMP LOCATION
« on: September 12, 2012, 04:05:27 PM »
Hello NeDi Community,

we have some devices which are managed by an external company and where we just have SNMP read access.

The syslocation information has configured by the external provider and they are not willing to change it.

Therefore, I would like to set the location in the NeDi database manually, but as already described, the entry will be overwritten during the dicovery process.

Therefore it would be good to set a flag telling the dicovery process, to not touch the syslocation (and syscontact) antries in the database.

Piet

7
Discovery / Re: Network Discovery problem with 1.0.7
« on: March 01, 2012, 04:35:03 PM »
I did some manual optimization in the crontab to reduce parallel discovery as much as possible - is better now but sometimes, the problem still occurs.

I use SSH for getting bridge forwarding entries only (getfwd is set to dyn in nedi.conf). If I set that to SNMP only (getfwd snmp), do I loose information?

I wanted to get rid of that problem, before start backing up configs.


8
Discovery / Re: NeDi 1.0.7 bug
« on: February 24, 2012, 06:18:58 PM »
Have the same problem with graphs.

rrdtool dump /var/nedi/rrd(devicename/system.rrd shows the following values:
Quote
                        <!-- 2012-02-24 05:00:00 CET / 1330056000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v><v> NaN </v></row>
                        <!-- 2012-02-24 10:00:00 CET / 1330074000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v><v> NaN </v></row>
                        <!-- 2012-02-24 15:00:00 CET / 1330092000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v><v> NaN </v></row>

9
Discovery / Re: Network Discovery problem with 1.0.7
« on: February 24, 2012, 05:36:00 PM »
I run several tests again - but without success at the end  :(

But the whole story...

The availble patch has been applied.
I have several different seed files for diferent locations but just one nedi.conf. I tried to optimize the sequence of the userid - password list in nedi.conf and I got better results during the discovery process.
I started again with one specific seed file and with an empty database and the error appears later than before, when the userlist in nedi.conf was not optimized.
Every time I started the discovery process, the error appears several devices later and at the end, all devices of that seedfile are discovered without error.

Than I took the next seedfile and performed the same steps until all devices have been discoverd without errors.

I was happy and I thought, everything would be OK now.
But in real life, I run many discovery processes with different seed files in parallel and then I get the error again (Resource temporarily unavailable at /var/nedi/inc/libcli-iopty.pm line 927.)
The time nedi requires for a discovery of all devices of all locations one after another would be more than 24 hrs - but I would like to discover each location at least once a day...
But because of this problem, some locations are not completely discovered at all...

In addition, I receive the following error during the discovery process:
Quote
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libsnmp.pm line 292.

Do you have any additional hint?



10
Discovery / Re: Network Discovery problem with 1.0.7
« on: February 18, 2012, 04:30:12 PM »
I added the print command in line 480 (after the commented print command line)

I use several different userids, passwords and different enable passwords for the devices in different locations - therefore it is not always the first userid - password combination, which works.

The users section of nedi.conf looks like this:
Quote
usr   user1;1   password1   enapw1
usr   user1;2   password1   enapw2
usr   user1;3   password1   enapw3
usr   user2;1   password2   enapw1
usr   user2;2   password3   enapw1
usr   user3   password4   enapw4
usr   user4   password5   enapw5

I run the discovery process again with a fresh empty database - the first time the error occurs with seed no. 43

I attached three parts from the total discovery output - one, where the first userid - password combination works, another one where the 4th combination works and the last one, where the error occurs (the 4th userid password combination would work with that device as well)


11
Discovery / Re: Network Discovery problem with 1.0.7
« on: February 16, 2012, 06:33:45 PM »
I applied the patch as described and the
Quote
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libcli-iopty.pm line 479
problem disappeard  :)

Unfortunately, the
Quote
Resource temporarily unavailable
problem still remain  :(

The last nedi output just before the error occur is:
Quote
Prepare (CLI)  ----------------------------------------------------------------
SSH :user1;1:22 Tout:2s OS:IOS-wl EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user1 10.10.10.22
CLI2:Matched password:, sending password
CLI3:Password sent
CLI3:Matched denied, login failed
SSH :user1;2:22 Tout:2s OS:IOS-wl EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user1 10.10.10.22
Resource temporarily unavailable at /var/nedi/inc/libcli-iopty.pm line 926.

Before I started the discovery, I initialized the database again, so this happened with an empty DB - but the device where the error happened is not the very first one but no. 43 in the seedfile. The devices 1 - 42 are discoverd without any problems.
After starting the discorvery process again, it happened with seed59...

I am not sure, where to enter the additional print command - in line 468 of the unpatched or of the patched libcli-iopty.pm?
Could you please advice?

Thank you so much again for your support!


12
Discovery / Re: Network Discovery problem with 1.0.7
« on: February 15, 2012, 10:07:26 AM »
Thank you very much for your answer.

Yes, we use Cisco devices with SSH!

I tested again, but the error happens immediately after a fresh install when run the discovery process the very first time.

I currently have just 40 devices in the database, but whenever a new device is discovered, the error happens. I increased the :openfiles-cur=128:\ to 1024 anyway, but without success.

Maybe it happens because I use the same userid with different passwords?

Here an extract of the output:

Quote
Prepare (CLI)  ----------------------------------------------------------------
SSH :user1;1:22 Tout:2s OS:IOS EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user1 10.10.10.10
CLI2:Matched Password:, sending password
CLI3:Password sent
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libcli-iopty.pm line 479.
CLI4:Matched DESEEB033WC001AS01> (or gen. prompt with enpass &  cmd), enabling
ERR :pattern match timed-out
SSH :user1;2:22 Tout:2s OS:IOS EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user1 10.10.10.10
CLI2:Matched Password:, sending password
CLI3:Password sent
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libcli-iopty.pm line 479.
CLI4:Matched DESEEB033WC001AS01> (or gen. prompt with enpass &  cmd), enabling
ERR :pattern match timed-out
SSH :user1;3:22 Tout:2s OS:IOS EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user1 10.10.10.10
CLI2:Matched Password:, sending password
CLI3:Password sent
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libcli-iopty.pm line 479.
CLI4:Matched DESEEB033WC001AS01> (or gen. prompt with enpass &  cmd), enabling
ERR :pattern match timed-out
SSH :user2;1:22 Tout:2s OS:IOS EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user2 10.10.10.10
CLI2:Matched Password:, sending password
CLI3:Password sent
CLI3:Matched Password:, login failed
SSH :user2;2:22 Tout:2s OS:IOS EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l user2 10.10.10.10

That's the one issue I have, but the more important problem for me is, that the whole discovery preocess crashes suddenly - I could not find any regularity  :(

The message I receive from NeDi when the process crashes is
Quote
Resource temporarily unavailable at /var/nedi/inc/libcli-iopty.pm line 919.

What can I do to eliminate this problem?

Another question I have is, in which file(s) do I have to enter the fixes you posted here http://forum.nedi.ch/index.php?topic=1244.0 ?

Piet



13
Discovery / Network Discovery problem with 1.0.7
« on: February 13, 2012, 02:12:06 PM »
Hi Remo,

thank you so much for the new release  :)

Unfortunetly I have problems during the discovery process.

I use a fresh system install using the NeDiO7 ISO image and I did not copy any data, except some settings in the nedi.conf and my seedfiles.

When starting the new discovery process (using nedi.pl -p -u seedfile) I get the following message for each discovered device
Code: [Select]
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libcli-iopty.pm line 479.and at the end, the discovery process crashes with the message
Code: [Select]
Resource temporarily unavailable at /var/nedi/inc/libcli-iopty.pm line 919. :(

Do you have any idea what could cause that problem?

Piet

14
Hi Remo,

thank you very much again for your support  :)

Here is the output of the netstat-ln command when the error occur

Code: [Select]
Active Internet connections
Proto   Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp          0      0  x.y.16.155.25643     x.y.38.31.22         TIME_WAIT
tcp          0      0  x.y.16.155.14633     x.y.38.57.22         FIN_WAIT_2
tcp          0      0  x.y.16.155.34809     x.y.52.92.22         TIME_WAIT
tcp          0      0  x.y.16.155.8080      x.y.52.116.22        TIME_WAIT
tcp          0      0  x.y.16.155.33195     x.y.53.18.22         TIME_WAIT
tcp          0      0  x.y.16.155.28432     x.y.17.253.23        TIME_WAIT
tcp          0      0  x.y.16.155.46029     x.y.53.11.22         TIME_WAIT
tcp          0      0  x.y.16.155.30300     x.y.38.18.22         TIME_WAIT
tcp          0      0  x.y.16.155.15770     x.y.45.20.22         TIME_WAIT
tcp          0      0  x.y.16.155.29137     x.y.53.72.22         TIME_WAIT
tcp          0      0  x.y.16.155.1117      x.y.52.104.22        TIME_WAIT
tcp          0      0  x.y.16.155.15295     x.y.38.51.22         TIME_WAIT
tcp          0      0  x.y.16.155.38578     x.y.52.93.22         TIME_WAIT
tcp          0      0  x.y.16.155.3882      x.y.52.89.22         TIME_WAIT
tcp          0      0  x.y.16.155.7526      x.y.45.26.22         TIME_WAIT
tcp          0      0  x.y.16.155.41831     x.y.45.5.22          TIME_WAIT
tcp          0      0  x.y.16.155.22622     x.y.38.68.22         TIME_WAIT
tcp          0      0  x.y.16.155.27635     x.y.52.83.22         TIME_WAIT
tcp          0      0  x.y.16.155.12779     x.y.90.192.22        TIME_WAIT
tcp          0      0  x.y.16.155.20443     x.y.26.66.22         TIME_WAIT
tcp          0      0  x.y.16.155.29346     x.y.38.64.22         FIN_WAIT_2
tcp          0      0  x.y.16.155.2346      x.y.52.118.22        FIN_WAIT_2
tcp          0      0  x.y.16.155.22        x.y.31.109.61085     ESTABLISHED
tcp          0     52  x.y.16.155.22        x.y.31.109.61068     ESTABLISHED
Active Internet connections
Proto   Recv-Q Send-Q  Local Address          Foreign Address        (state)
udp          0      0  x.y.16.155.31070     x.y.250.114.123   
Active UNIX domain sockets
Address    Type   Recv-Q Send-Q      Inode       Conn       Refs    Nextref Addr
0xd8dd9b98 dgram       0      0        0x0 0xd2efb7c0        0x0 0xd2efb080
0xd8cbfd44 stream      0      0 0xd8b1db10        0x0        0x0        0x0 tabs/.sock
0xd8cbfb9c dgram       0      0        0x0 0xd2efb7c0        0x0 0xd2f6ffc0
0xd8cbf9f4 dgram       0      0        0x0 0xd2efb7c0        0x0 0xd2f1d9c0
0xd8cbf84c stream      0      0 0xd8c4b87c        0x0        0x0        0x0 /var/run/mysql/mysql.sock
0xd8dd9848 stream      0      0        0x0 0xd2efbc40        0x0        0x0
0xd8dd9774 stream      0      0        0x0 0xd2efbc80        0x0        0x0
0xd8dd96a0 stream      0      0        0x0 0xd2efbec0        0x0        0x0
0xd8dd95cc stream      0      0        0x0 0xd2efbe80        0x0        0x0
0xd8dd94f8 dgram       0      0        0x0 0xd2efb7c0        0x0        0x0
0xd8dd9424 stream      0      0        0x0 0xd2efb600        0x0        0x0
0xd8dd9350 stream      0      0        0x0 0xd2efb5c0        0x0        0x0
0xd8dd927c dgram       0      0 0xd8dc43c4        0x0        0x0        0x0 /var/empty/dev/log
0xd8dd91a8 dgram       0      0 0xd8dc4328        0x0        0x0        0x0 /var/www/dev/log
0xd8dd90d4 dgram       0      0 0xd8dc428c        0x0 0xd2f88e40        0x0 /dev/log

These are not too many connections I think.

15
Some additional information...

I run the discovery process (nedi.pl -p) several times today - withou interruptions yet - so I assume, that the problem is fixed now.

Unfortunately, the backing up configs (nedi.pl -vA "login != ''" -bB -SsmgrfpitedobwaOA) is still interrupted by the "Resource temporarily unavailable at ./inc/libcli-iopty.pm line 871" problem.

Would it be possible to just ignore that error and continue with the next device? Or does anyone have any idea regarding the real cause of that problem?

Pages: [1] 2