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

Pages: [1] 2 3 ... 18
Installation / Re: Upgrade from 1.5 to 1.6
« on: January 31, 2018, 08:56:27 AM »
I had to change "cliport = 0" in "device" table.
Even rare, another way to do it bulk will be useful.


Installation / Re: Upgrade from 1.5 to 1.6
« 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.

Installation / Re: Upgrade from 1.5 to 1.6
« on: January 11, 2018, 02:54:51 PM »
After a while, but again on the same topic...

Now I'm trying to upgrade the production NeDi from 1.5 to 1.6C, from the web interface (to preserve database)
I've also modified PHP upload limit to 128 MB (in the usual two places), to avoid already reported problems.
Also reissued "chown -R www-data:www-data /var/nedi/"

This is what is shown after the update try:

Read nedi-1.6C.tgz Backup msg.txt Backup devtools.php Backup iftools.php Backup crontab Backup nedi.conf Backup seedlist Backup agentlist gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now [/size]
Errors Write nedi-1.6C.tgz

Now what I can do ?

Thanks in advance!

Discovery / Re: Identify where "rogue" switches are connected to
« on: December 13, 2017, 02:23:47 PM »
Yes and no.
Not exactly...
No and yes!

After the database cleaning the nodes report showed on some switched and port a abnormal number of nodes seen (max was 190 on a sigle port!).

After some time (now apprx 4 hours later, so more then 16 discoveries, one on every 15 minutes) the same report shows much, much less nodes/port, and a reasonable amount of nodes per port and per device.

If this is true and stable, should be reliable enough to detect where "rogue" switches are connected to.

Thanks a lot for your adivice!

(Once more: how often is fine to run the cleaning script using crontab?  ;) [size=78%])[/size]

Discovery / Re: Identify where "rogue" switches are connected to
« on: December 13, 2017, 10:30:08 AM »
I saw the strange "root instead of nedi.conf dbuser" access mod in the distributed file. If I don't remove the root part in fron of the relevant line it give errors.

But even modified, it shows some other errors.
    "ERROR 1227 (42000) at line 2: Access denied; you need (at least one of) the RELOAD privilege(s) for this operation"
so a gave all rights to "nedi" db user.

    "ERROR 1186 (HY000) at line 3: Binlog closed, cannot RESET MASTER"

 and then

    "nedi.chat       optimize        note    Table does not support optimize, doing recreate + analyze instead"
but next
    "nedi.chat       optimize        status  OK
and the same for all the other tables

Then no messages like a "done", it remains like hanged until I press enter...

Anyway nodes table now seems cleaned.

Other advices?

Thanks again!

Discovery / Re: Identify where "rogue" switches are connected to
« on: December 13, 2017, 08:52:21 AM »
Indeed I used the one in "contrib".

The "production" NeDi is still the 1.5.225, I had always trouble doing an upgrade through NeDi web interface, and doing it manually always need a database rebuild, so all history lossing.
Maybe the script in this release is not the latest one?
Should I use the one in 1.6 ? Is it compatible?

Discovery / Re: Identify where "rogue" switches are connected to
« on: December 06, 2017, 04:08:47 PM »
Quick brief reply: never done a maintenance. Tested right now, some problem with authentication (root, nedi uses a nedi.conf use and password) and then another possible error "ERROR 1186 (HY000) at line 3: Binlog closed, cannot RESET MASTER".

I'll do a look to your advices, maybe from next monday (we have a short vacation starting this evening  :)  ) the I'll report here.

Thanks a lot!

Discovery / Identify where "rogue" switches are connected to
« on: December 06, 2017, 02:46:38 PM »
Maybe this is an already answered question, but haven't find it.
I need to identify where "rogue" switches are connected in our LAN.
Rogue means unmanaged switches used to increase available port in areas where official LAN is not well or enough distributed (but not only, so "rogue")
If anyone ask why we in ICT don't know them, it depends on some anarchy of employees and relevant responsible, and past carelessness of old ICT chiefs...

I supposed Population is the answer, but i present only in few reports (i.e. Reports - Combination) but is not easy to use.
And seems that Population hold all MAC detected on a given port from the first discovery of each device, and is of course too much, I need a shorter period, even current situation.

Else I must do a switch by switch MAC address table export and consolidation, a really huge work.

Maybe NeDi is able to do the same in a simpler way, or maybe a artfully query in the NeDi database.

Could anyone help me?

Thanks in advance!

Definition Files / Wanted: Mellanox SX1012 def file
« on: November 13, 2017, 09:08:41 AM »
As in object.
Else, some advices to make one (from which template start, etc...)

Thanks a lot in advance!

Installation / Re: Upgrade from 1.5 to 1.6
« on: October 25, 2017, 08:11:48 AM »
I'll be never able to thank you enough for this! ;D

Installation / Re: Upgrade from 1.5 to 1.6
« on: October 23, 2017, 08:56:11 AM »


  location ~ \.php$ {
      fastcgi_split_path_info ^(.+\.php)(/.+)$;
      fastcgi_param SCRIPT_FILENAME   $document_root$fastcgi_script_name;
      fastcgi_param QUERY_STRING              $query_string;
      fastcgi_param REMOTE_ADDR               $remote_addr;
      include        fastcgi_params;
      fastcgi_pass unix:/var/run/php/php7.1-fpm.sock;
      fastcgi_buffering off;

But after a search in the forum about PHP, I found this thread [size=78%]https://forum.nedi.ch/index.php?topic=2066.0[/size]
Than I changed 7.1 to 7.0 in configuration files (not in script) and now seems OK.
Now 1.6 is running both under Apache and nginx, (http and https) even this is a little confusing. Luckily "System - Files" procedure now don't show browser download window any more.

I'll look for a smooth upgrade procedure. I can't (and don't want) to migrate from Debian to Ubuntu and/or do reinstallations from scratch.

Anyway, don't worry for me. I'm (we are) not a paying client. My company is too huge for caring the opinion of a "low level" technician like me, so for the moment I can't convince them to subscribe...
Maybe soon I'll change my assignment and so the duty will be for another one.

Thanks a lot anyway!

Installation / Re: Upgrade from 1.5 to 1.6
« on: October 20, 2017, 02:07:18 PM »
Thanks for your answer!
I'l do something in next days, using some spare time.

Anyway, which is the cause of missing update using "System - Files" procedure?
How can I find the cause?

I like to upgrade the "production" NeDi installation, but I'm afraid of possible conseguence and lost of historical data.

Thanks again!

Installation / Upgrade from 1.5 to 1.6
« on: October 18, 2017, 11:30:29 AM »
Tested yesterday an upgrade from 1.5 to 1.6 on a "test" machine (Debian 9), where 1.5 was running fine.
"System - Files" procedure don't work. Choosed local file (freshly downloaded nedi-1.6C.tgz), then Execute button, but nothing happens at all.
Tested with Chrome, even in Incognito mode to avoid addons interference, without success. The same with IE 11.
So I did a overwrite of NeDi folder with the ones in downloaded file, reinitialized database with "./nedi.pl -i user pwd" procedure.
Now seems OK, but If I choose "System - Files", browser try do download "System-Files.php".
Tried to do what is done by "nebuntu.sh", firstly only the "apt" line (with some errors) the the whole script. No success.
Maybe something is not fully compatible in Debian compared with Ubuntu.
I can uninstall and reinstall all in this Debian machine (any script or procedure to make it like a fresh instaled Debian?), but can't start from scratch.

Any advice?

Thanks in advance!

LAN/Switching / Re: Feature request: Stack monitoring/Error detection.
« on: September 11, 2017, 04:27:01 PM »
Wow, nice.
I suppose is available in latest release (1.6 or 1.7 ?)

I have to be patient  ;)


LAN/Switching / Re: Feature request: Stack monitoring/Error detection.
« on: August 29, 2017, 09:50:45 AM »
Am I wrong, or your request hasn't received an answer?

Pages: [1] 2 3 ... 18