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 ... 8 9 [10]
Discovery / Re: Cisco WS-C3560V2 Defgen / Discovery
« on: July 06, 2010, 05:30:44 PM »
That is great!  I didn't think I was going to get away that easy!  ;)


Discovery / Re: Discover doesn't finish
« on: July 06, 2010, 05:29:56 PM »
Wow, I think you just might have the largest networks ever used with Nedi!  I thought we were big with 800 devices.  This means that both of you are a great guinea pigs for testing and finding bugs!  Please continue to post your issues and resolutions to this forum.  What version of Nedi are you guys running?  Nedi 1.0.5?

The sad thing is that Nedi is helping us manage tens of millions of dollars of network equipment, but Nedi is being developed for free in the spare time of one brilliant person!  Imagine the possibilities if Remo could work full-time on Nedi....  but then how would he pay his rent? 

Remo, are you available for hire if someone wanted direct support from you?

Discovery / Re: Cisco WS-C3560V2 Defgen / Discovery
« on: June 19, 2010, 12:29:01 AM »
Did you try the defgen tool in the web interface?



Thanks for your contribution to Nedi!  This is a very useful project and we appreciate all assistance and communication.  I think I have been using Nedi for over 5 years and we still use it on a daily basis!

Remo, any consideration into using a distributed versioning tool, something like Launchpad?  This way you can work on your code, and developers like Steffen can create branches, then you can consider merging the branches. (DISCLAIMER: I am not a programmer)



Discovery / Re: Anyone got any Cisco ASA to work with nedi
« on: June 03, 2010, 06:59:00 PM »
This guy wrote a function to pull the ARP table out of FWSM using SNMP.  He created it for Cacti, but perhaps this can be used in Nedi?  We just moved most of our datacenter to our FWSM, so we really miss seeing the ARP table!




This is not very easy, because "sh arp" outputs names instead of IP addresses if you defined them.

The newest FWSM release finally permits to read ARP table by SNMP. But of course not with standard OIDs so it's currently not useable.


Discovery / Re: Discovering PoE
« on: December 02, 2009, 06:20:28 PM »
Remo - We can help test this feature when you start working on it.


Good point, but our switches and APs are in the same networks.

Remo - It still looks like Nedi is spending 32 seconds on my APs, even the ones that have the "! SNMP" tag during discovery.

Can anyone else confirm this?


I'm not sure, this is what I see.  Those IP addresses are for wireless access points...   No name, not discoverable          741/8-32s   No name, not discoverable          371/262-32s   No name, not discoverable          740/8-32s   No name, not discoverable          370/262-32s   No name, not discoverable          739/8-32s   No name, not discoverable          369/262-32s   No name, not discoverable          738/8-32s

I am only seeing 64 of these, so perhaps the other 200+ are correctly being discarded.  I will find out what CDP neighbors are showing for these IPs.

Discovery / Nedi should try passwords in nedi.conf if authenticataion fails
« on: September 09, 2009, 06:32:36 PM »
During the initial discovery of a device, Nedi uses the passwords in nedi.conf to authenticate to the device.  However, after Nedi has authenticated once, it stores the successful username in the database and always tries to use those credentials.

The problem happens when you change username/passwords on your devices.  Nedi keeps trying the old password and doesn't fall-back to trying the passwords in nedi.conf.

The work-around is to delete the device and let Nedi rediscover it. 

Is this something you can fix, Remo?



Discovery / Re: cannot discover
« on: September 09, 2009, 06:27:39 PM »
Are you using a paid version of Groundwork?  If so, they would be the best to ask this question.  I have not used Groundwork.

Good luck!

Here is the actual line I used in nedi.conf:

nosnmpdev       IP (Phone|Telephone)|C1130|C1140|C1310|C1200|C1240

However, Nedi is still trying to discover all of my C1130 access points.  Did I enter it correctly?  Any ideas?


Remo suggested I look at the output of this command, using the IP address of the switch that is connected to one of our APs:

./nedi.pl -vt

This output shows a lot of information, but the CDP information is the most interesting for my question:

CDP: Gi1/0/9> bldg-103-ap IP: Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.4(18a)JA1, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Fri 23-Jan-09 20:07 by prod_rel_team SV:0 P:12200mW on Fa0-FD Vl0 !SNMP

Looks like I need to add a listing for the model number, "C1130".  I'll test that and report back on how it works.

# Regular expression to match discovery protocol description of non-SNMP
# platforms (like lightweight/controlled APs).
nosnmpdev       IP (Phone|Telephone)|MAP-|AIR-|C1130

Nedi is wasting 30 seconds per lightweight AP, and we have over 300 of them.  So over 2 hours of wasted time.  How can we tell Nedi to not discover these devices?  I tried this setting but Nedi is still hitting the APs...

# Regular expression to match discovery protocol description of non-SNMP
# platforms (like lightweight/controlled APs).
nosnmpdev       IP (Phone|Telephone)|MAP-|AIR-

News / Re: NeDi 1.0.5
« on: September 04, 2009, 07:42:20 PM »
Hi Remo!

Good to talk with you again, and good to hear about the net::app progress!  I still hang out in the #nedi IRC channel if you ever want to chat.

We are having a good experience with 1.0.4, I just installed it yesterday.  It is discovering all of our devices  (759) and nodes (8,070), but none of the backups are working yet (./nedi.pl -ArpB).  I have to look into that further.  UPDATE: I found out that 37 devices ARE getting backups, so it is partially working.  I'll try to find out more.

I like the feature you added for redirecting users to the login-page and back to the page they were trying to access.  This saves me when my session times out, I can quickly get back to where I was.

One other problem is that Nedi is wasting 30 seconds per lightweight AP, and we have over 300 of them.  So almost 2 hours of wasted time.  How can we tell Nedi to not discover these devices?  I tried this setting but it is still hitting the APs...

# Regular expression to match discovery protocol description of non-SNMP
# platforms (like lightweight/controlled APs).
nosnmpdev       IP (Phone|Telephone)|MAP-|AIR-



News / Re: NeDi 1.0.5
« on: September 02, 2009, 06:07:19 PM »
Sounds good, Remo, keep up the good work!

I think we have just reached 5 years of using Nedi, and we still love it and rely on it.  Our biggest problem is trying to get it to support SSH, because we are starting to require SSH-only on our network devices.  I will try a more recent version of Nedi and see if I can get it working.

Thanks for your excellent work, Remo!

Tristan Rhodes

Pages: 1 ... 8 9 [10]