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

Pages: [1] 2 3 ... 10
1
Thanks for the info!  I thought these switches were discovering correctly because the "Last Discover" was staying current. 

However, if I look at the "Device Status" page it has a red "Discover Outdated" and these are the switches with the blank "Last Status Change (Realtime)". 

I clicked the "Discover Now" button, and it discovers correctly, the "Discover Outdated" message goes away, and the interfaces show their Last Change.

Do you have idea on why this is happening, and how to prevent this?

Thanks!


2
We love being able to view a network device in Nedi and see how long each of the ports have been in their current state.   This lets us find ports that have been down for over a year so that we know that we can reuse these ports.  However, we are starting to find some models of switches do not have anything in this field, just a "-".

I assume this must be caused by a missing or wrong entry in the .DEF file.   Which one is it? 

Thanks!

Tristan

3
Definition Files / Re: Cisco 3850 stack def
« 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

4
I just wanted to say, Paraidomat, that is a neat hack to make Nedi discover 1/4 of your devices at the same time!

How does it handle new devices?  For instance, if a new device was plugged into existing two devices, which are being discovered by different Nedi processes?  Would the new device get added twice?  Or would the second process simply output an error, like "device exists, skipping".

5
Installation / Missing dependencies on "Install" instructions for Ubuntu
« on: September 16, 2016, 07:55:22 PM »
I recently used the Ubuntu instructions here:

http://www.nedi.ch/installation/

Nedi was working fine for the most part, but then I tried to initiate a backup using the web-interface.

https://nedi.mydomain.com/System-NeDi.php

That page caused Nedi to complain about some missing Perl modules.   I fixed it by installing these packages:

libdbi-perl
libdbd-mysql-perl

6
Ok, I got things working again by using PHP5.6, which requires using a PPA repository.

Code: [Select]

# This is needed for "apt-get-repository"
sudo apt-get install software-properties-common python-software-properties

# Add the new repo
sudo add-apt-repository ppa:ondrej/php

# Download package lists
sudo apt-get update

# Install Nedi dependencies
sudo apt-get install apache2 libapache2-mod-php5.6 mysql-server libnet-snmp-perl libcrypt-rijndael-perl libcrypt-hcesha-perl libcrypt-des-perl libdigest-hmac-perl libio-pty-perl libnet-telnet-perl libalgorithm-diff-perl librrds-perl php5.6-mysql php5.6-snmp php5.6-gd php5.6-mcrypt rrdtool libsocket6-perl

# I can't remember if this is required, or done by the packages above...
sudo a2enmod php5.6

# Restart Apache
sudo service apache2 restart

That should work for Ubuntu 16.04.  Let me know if I need to correct anything!

7
I just upgraded Ubuntu to 16.04 and it broke just like you described. 

What is the best way around this?  Sounds like we need to get php5 installed again?   

I'll post if I find out how to get this working again.

8
Thanks Remo!  I ran your SQL command using your nifty "System>Database" tool and it reduced my total nodes by ~90%.   

Before: 24.0 million nodes
After: 2.2 million nodes

Needless to say, Node reports are much faster.  (although I still wonder why I have 2 million nodes)

Thanks for your assistance!

Tristan

9
I noticed my Nodes feature has been getting slower and slower, so I checked on the quantity of nodes:

New    2,171
Active    4,525,308
Wlan    4,796,687
IP Change    1,063,297
IF Change    15,805,663
No Name    18,231
No IP    16,408
Discover Once    167,450

Total    24,563,767

There is no way there are that many nodes on our network! And these numbers keep growing.  My theory is that Nedi is creating a new Node entry any time there is a unique "DNS name + IP + MAC" combo.  On our wireless, we have 15 min DHCP leases so users could be seen on hundreds of different IPs.

I searched for one node with DNS name of "amelia-pond", and it came up with the 527 results.  The DNS name name was always the same, but the MAC address (including vendors) and IPs varied a lot. 

I am running Nedi version 1.5.225.  We didn't have this explosive growth problem with previous versions.

Cheers!

Tristan



10
Wow, once again I find something new and cool about Nedi.  Thanks for letting me know about the "-k" option!

Tristan

11
Discovery / SSH discovery fails if keys change... but I have a solution!
« on: January 21, 2015, 07:31:42 PM »
I keep seeing several email alerts from Nedi 1.4 that say this:

22) blg-100-sw1 CLI Bridge Fwd error: no working user

I found out that this is because SSH is warning that the key is different from the one in "~/.ssh/known_hosts"

Current:

ssh -o 'StrictHostKeyChecking no' -l nedi 10.1.6.1

Fixed:

ssh -o 'UserKnownHostsFile /dev/null' -o 'StrictHostKeyChecking no' -l nedi 10.1.6.1

Please add this change to Nedi so that it can still find devices with changed SSH keys!

/inc/libcli.pm, line 518 on Nedi 1.4
              my $known = "-o 'UserKnownHostsFile /dev/null' -o 'StrictHostKeyChecking no'";


Tristan

12
Discovery / Re: IP addresses via DHCP-snooping?
« on: January 21, 2015, 07:23:36 PM »
Dave,

Your idea is a good one.  I think the DHCP Snooping entries will stay in the switch until the next reboot.  This means it has a longer history than ARP, which has a 4-hour timer by default.  (I guess that would only matter if you ran Nedi less often then every 4 hours) 

This might provide the information needed:

http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-DHCP-SNOOPING-MIB

However, you do have a fairly uncommon setup (SNMP access to L2 devices, but not L3).  Hopefully you can sponsor the addition of the feature!

Cheers,

Tristan

13
Definition Files / Re: 1.3.6.1.4.1.9.1.674, Cisco FWSM
« on: January 21, 2015, 07:11:37 PM »
I don't think the ASA CLI code is working for us.  Here is what my email alert shows:

15) Campus-fw       Command no terminal pager returned ERROR: % Invalid input detected at '^' marker.
16) Campus-fw       Command show arp returned ERROR: % Invalid input detected at '^' marker.

Here is when I run discovery:

Code: [Select]
sudo ./nedi.pl -a 10.2.2.30 -v -d c

Prepare (CLI)  ----------------------------------------------------------------
PREP:arp supported and user nedi exists

ArpND (CLI)   -----------------------------------------------------------------
SSH :nedi@10.2.2.30:22 Tout:10s OS:IOS-asa EN:[\w+().-]+#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l nedi 10.2.2.30
CLI2:Matched 'password:' sending password
CLI3:Password sent
CLI4:Matched Campus-fw>  (without enpass)
DBG :Elevate=3 Min=0 Mode=C Notify=AbCDEfGijlMNopSTW
EVNT:MOD=C/3 L=150 CL=nede TGT=Campus-fw MSG=Command no terminal pager returned ERROR: % Invalid input detected at '^' marker.
MLQ :admin Campus-fw Command no terminal pager returned ERROR: % Invalid input detected at '^' marker.
EFWD:1 Mail and 0 SMS queued
DBG :Elevate=3 Min=0 Mode=C Notify=AbCDEfGijlMNopSTW
EVNT:MOD=C/3 L=150 CL=nede TGT=Campus-fw MSG=Command show arp returned ERROR: % Invalid input detected at '^' marker.
MLQ :admin Campus-fw Command show arp returned ERROR: % Invalid input detected at '^' marker.
EFWD:1 Mail and 0 SMS queued
ARPC:0 ARP entries found

Write ArpND -------------------------------------------------------------------
WAND:0 new IPs and 0 updates written

Is this because Nedi is not trying to "enable" before running those commands?

Tristan

14
GUI / Re: Creating amazingly cool network maps with Nedi!
« on: January 21, 2015, 06:57:46 PM »
Thanks for the information Remo!  I have updated my post with the updates.

15
Yes, this was on Nedi 1.4.   

The good news is it only happened on the first discover.  I can't get it to repeat, but if it does I will gather the debug info you requested.

Cheers,

Tristan

Pages: [1] 2 3 ... 10