Welcome, Guest. Please login or register.

Poll

Do you want to monitor nodes?

No, I only care about devices. Nodes come and go...
7 (53.8%)
Not yet, but I may use it in the future!
2 (15.4%)
Yes, I love adding multiple nodes to monitoring at once.
4 (30.8%)

Total Members Voted: 13

Voting closed: August 11, 2013, 05:24:21 PM

Author Topic: NeDi 1.0.9 Progress  (Read 21811 times)

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2509
    • View Profile
    • NeDi
NeDi 1.0.9 Progress
« on: May 31, 2013, 09:55:55 PM »
I've started working on the next development cycle of NeDi. I'll focus on monitoring improvements (individual thresholds for example) and GUI enhancements. One of of the latter being inline-maps. Here's a little taste:
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

raider82

  • Jr. Member
  • **
  • Posts: 91
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #1 on: June 03, 2013, 09:33:26 AM »
Hi Remo,

great to see, there is already development in the project again. Here are some ideas from my side. Maybe you like some of them ;-)
  • functionality to add the server into an ACL based on the user in a config file and the ACL delivered in a parameter (I use a separate script at the moment and try to get in into nedi)
  • option to turn on auto-deletion of devices if not re-discovered within x days (I use an SQL script at the moment that deletes devices that have not been discovered within the last week)
  • option to turn on auto-deletion for events older than x days (again I currently use an SQL)
  • storing the used config in NeDi within the discovery (implemented in my system as enhancement) -> allows reports and assures correct user for Devices-Write
  • Devices-Write with logging functionality (currently replaced Devices-Write by an individual solution)
  • Devices-Write with parameters (being able to use the output for some other commands)
  • vendor MAC table in NeDi to join SQLs to this table for vendor MACs (I currently use a single table)
  • port-channel information (I currently do have this based on SSH commands)

If you want to have details on some of my implementations, just let me know.

Best regards,
Matthias

ascii

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #2 on: June 03, 2013, 11:15:58 AM »
maybe to read port information via ssh also.

i'm currently running into problems with 802.1x.
via snmp i always get vlan 1 on a Cisco 3650V2
looking at the CLI i get the correct vlan.

Code: [Select]
ess-c15-75#show mac address-table | i Fa
  90    0004.0091.6e68    STATIC      Fa0/5
  90    0004.009a.fb09    STATIC      Fa0/44
  90    0004.00aa.aff3    STATIC      Fa0/6
  90    0004.00c9.67d8    STATIC      Fa0/2
  90    0004.00ee.1a4e    STATIC      Fa0/9
  90    0004.00ee.a297    STATIC      Fa0/4
  90    0007.4d2d.276d    DYNAMIC     Fa0/14
  90    0007.4d2d.282e    DYNAMIC     Fa0/13
  90    0007.4d2d.3f36    DYNAMIC     Fa0/41
  90    0007.4d2d.3f38    DYNAMIC     Fa0/43
  90    001b.7810.559e    STATIC      Fa0/7
  90    00c0.ee44.ef50    STATIC      Fa0/37
 503    000e.8cf3.5d01    DYNAMIC     Fa0/21
 503    000e.8cf3.5d03    DYNAMIC     Fa0/21
 503    4437.e66d.a1e4    STATIC      Fa0/17
 503    4437.e66e.4351    STATIC      Fa0/18
 503    4437.e66e.438b    STATIC      Fa0/48
 503    4437.e66e.bb21    STATIC      Fa0/16
 503    4437.e66e.bb50    STATIC      Fa0/22
 503    4437.e66e.bb97    STATIC      Fa0/45
 503    4437.e66e.bbc6    STATIC      Fa0/8
 503    4437.e66e.bbf4    STATIC      Fa0/1
 503    4437.e66e.bbf5    STATIC      Fa0/20
 503    4437.e66e.c7b8    STATIC      Fa0/10
 503    4437.e66e.c7ce    STATIC      Fa0/40
 503    4437.e66e.c7d1    STATIC      Fa0/38
 503    4437.e66e.c7d2    STATIC      Fa0/19

this is probably also a bug with ciscos snmp values

aurelien-93

  • Newbie
  • *
  • Posts: 48
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #3 on: June 03, 2013, 03:10:46 PM »
good job

I'm interested in by port channel informations !

best regard


raider82

  • Jr. Member
  • **
  • Posts: 91
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #4 on: June 04, 2013, 11:50:16 AM »
I'm interested in by port channel informations !
You mean how to get Port-Channel information in NeDi? Just send me a short private notice and I will send the source code.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2509
    • View Profile
    • NeDi
Re: NeDi 1.0.9 Progress
« Reply #5 on: June 05, 2013, 11:47:12 PM »
ascii, this is supported already! For switches using IOS-old (e.g. 3524-XL) in the .def you'll need to set getfwd in nedi.conf to sec for it to work. IOS devices should work even with getfwd set to dyn.

It might be worth to try Q-bridge in Defgen as well, maybe they'll support it eventually...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

ascii

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #6 on: June 06, 2013, 07:21:05 AM »
i have it set to sec.
when i change the OID in the defgen to 1.3.6.1.4.1.9.9.220.1.1 (http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.4.1.9.9.220.1.1#oidContent ) i get the 802.1x Port.
the problem is that not all the port on these switch types have 802.1x Ports

i will test  a little bit with Q-bridge

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2509
    • View Profile
    • NeDi
Re: NeDi 1.0.9 Progress
« Reply #7 on: June 06, 2013, 05:35:45 PM »
If you discover with -v, do you get any FWDC: lines? (bridge-forward via CLI)
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

ascii

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #8 on: June 07, 2013, 08:42:06 AM »
yes i get the FWDs

BridgeFwd (CLI)   -------------------------------------------------------------
CMD :show mac address-table | e CPU|Switch|Router|/.*,
FWDC:f0def12c7386 on Fa0/4 vl56
FWDC:536 bridge forwarding entries found
DISC:Cli bridge fwd = OK-Bridge

i left out the uplink port since it's to much output
the vlan is the correct one but it's not written in the database

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2509
    • View Profile
    • NeDi
Re: NeDi 1.0.9 Progress
« Reply #9 on: June 07, 2013, 05:07:34 PM »
Ah ok, now the question is why it's not written! Do those MACs show up in the BNOD: lines further down at all? That's where all collected nodes are assigned to the best suited interface and written to nodes.
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

michieltimmers

  • Newbie
  • *
  • Posts: 35
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #10 on: June 12, 2013, 03:11:38 PM »
1.0.9? cool!

here are some ideas, might not all be possible to implement but maybe also gives you new ideas.

  • Check for standard config lines in a config that all devices should have. Like ACL, NTP etc..
  • Check if a config is saved by comparing ccmHistoryRunningLastChanged and ccmHistoryRunningLastSaved
  • Check if NTP server is synchronized, "check ntp status". Needs to be done with CLI..SNMP not possible
  • Custom overview page, I like to add Device Type, % CPU, Memory Free, Temperature as defaults in the overview

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2509
    • View Profile
    • NeDi
Re: NeDi 1.0.9 Progress
« Reply #11 on: June 12, 2013, 06:08:40 PM »
thanks for the feedback. This actually supports the other config enhancement requests. I'm thinking 3 new columns for devices: lastbackup, lastchange, lastsave and you can play with them any way you want in devices-list...

Devcies-Write in 1.0.9 changes to output in iframes, which means you get to see all output on the same page!

Not sure, what you mean with overview? Would selecting and sorting by those columns work in devices-list too?
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

harry

  • Full Member
  • ***
  • Posts: 124
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #12 on: June 13, 2013, 08:03:37 AM »
Hi Remo,
Can we have ISDN status notification added in to monitoring?
This will help us a lot. we have 32 ISDN sites with 28xx and 38xx's.

Let me know if you want me to run any test or information.

Re
Harshit.

michieltimmers

  • Newbie
  • *
  • Posts: 35
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #13 on: June 13, 2013, 06:59:01 PM »
Not sure, what you mean with overview? Would selecting and sorting by those columns work in devices-list too?

When I now search for a device the default columns are Device, Main IP, Serial, Location, Contact and Last Discover. I would like to add Device Type, % CPU, Memory Free and Temperature. And remove Contact as the default shown columns. Maybe there is already a way of doing this.

Nick

  • Newbie
  • *
  • Posts: 11
    • View Profile
Re: NeDi 1.0.9 Progress
« Reply #14 on: June 14, 2013, 01:51:50 AM »
Hi,

What about introducing EOL notices from several vendors in order to run EOL report for HW/SW refresh planning?

I'm not sure if it is feasible to introduce it into a minor release, but maybe for 1.1 ;)

Cheers,
Nick