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

Pages: [1]
1
Discovery / Re: nodes not populating interfaces
« on: March 30, 2018, 07:16:49 PM »
the switch side of the radwin wifi and the remote radwin are both discovered as devices (they appear in Nedi as devices) however i don't see neighbour info.

from the switch point of view (CLI), i can see all the MACs on that single port including the radwin on both sides, and the devices located on the remote side.  just seems like Nedi stopped telling me there was a population of 7 nodes on that interface.  now it's blank.

i've attached a few pics, if you don't mind quickly having a look.  :)

2
Discovery / Re: nodes not populating interfaces
« on: March 26, 2018, 06:58:36 PM »
it's a radwin 2000 on both sides.  there really hasn't been any change to the nodes on either side of the wifi connection.  particularly on the port in question...  the radwin radio has been there for a couple years, and NeDi (up until just a couple weeks ago) *was* reporting the 7 or so nodes on that port.  now it shows none, even though doing a show mac-address table on that port does indeed show all the MAC addresses of the devices.

i just looked at my original question.  i said i don't have visibility on the port.  i should re-word that statement.  i still "see" the port, it's green in Nedi indicating that it's connected and i can still monitor realtime traffic.  and the devices on the other side of that wifi link are all visible and operating fine from a network point of view.  just that Nedi can't see them anymore.

appreciate you taking the time to answer.  if there's anything else i can add here (screencaps, etc) i'll gladly do so.

thanks!

3
Discovery / nodes not populating interfaces
« on: March 15, 2018, 08:12:19 PM »
just this morning i noticed the population of a port on one of my switches went from 7 to blank.
under Device, Status, i select the switch in question and scroll down to see list of ports and this port that had a population of 7 devices connected to it (it's port Fa0/4 btw) - i know i saw this last week.  i was able to do some real-time traffic analysis on this port (as it's one end of a line of sight wifi connection).  i can still do that, but now i don't have visibility on that port.  if i do a "sh mac address-table int fa0/4" i see the devices, but i don't see them in Nedi.  it was working.  i haven't done anything drastic i can think of.  any ideas?

4
Discovery / Re: graphs not populating
« on: February 28, 2018, 12:44:19 AM »
i might be answering my own question and a few days of discoveries will tell but i noticed the ownership permissions under  /var/nedi/rrd were not all set to www-data.www-data...

so i ran:  chown -R www-data.www-data /var/nedi

a couple hours ago (i do discoveries once per hour), and i'm starting to see entries.  we shall see.

anyone think i am on the right track?

5
Discovery / graphs not populating
« on: February 24, 2018, 06:37:56 AM »
well, i've searched the forum and can't figure out why my graphs aren't populating.
when i look in /var/nedi/rrd my devices are there tons of .rrd files in there and timestamps that are up to date.  they appear to be generating!
my rrdstep in nedi.conf is:  rrdstep 3600 and rrdsize 1000 (the defaults)
my crontab entry looks like this:

0 * * * *       /var/nedi/nedi.pl -Aall > /var/log/nedi/nedi-`date +\%H`.run 2>&1
0 0    * * *    /var/nedi/nedi.pl -v -b -Aall -SAF > /var/log/nedi/nedi-00.bup 2>&1

been running Nedi since 8-Feb.
any ideas?

6
Discovery / two Cisco ASAs with same name
« 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

Pages: [1]