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

Pages: [1]
1
Discovery / Across WAN discoveries
« on: August 03, 2017, 01:51:09 AM »
Need some help NeDi community with WAN discoveries. I just got a new instance running and am able to discover local devices and to go across the WAN, I added core devices in the seedlist. Needless to say, everything works like a charm. The only issue that I'm having is that for whatever reason my netfilters are not working as they should and I'm picking up unwanted phones via CDP. This issue is slowing down the discovery process as we have hundreds of phones that NeDi is attempting to connect to. Below is the configuration that I'm using..

The execution is nedi.pl -po

Filters
netfilter       10.130.50|192.168.168|172.30.127|172.30.1|172.30.0|10.130.230
netfilter       ^(?!172.30.130).*$|^(?!172.30.131).*$|^(?!10.130.80).*$

Any insight is highly appreciated! The second filter is my attempt to ignore the phones.

-Casrlos

2
Discovery / Re: Hourly Notices
« on: August 26, 2012, 04:26:31 PM »
One more suggestion. When discovering new devices, it is often difficult to determine which ones are being monitored and which are not. It would be great to have a "being monitored" column in the Device page so that you can see the ones not being monitored and activate them. The way I am doing it now is by using "First Seen" and searching in that order to find the most recent additions and then adding them to monitoring. Needless to say, during the busiest season of the year for us, we are adding switches and APs at almost 3 to 4 a day. I tried doing a Monitor all from the Device page, but it over-writes certain individual device settings.

3
Discovery / Re: Hourly Notices
« on: August 24, 2012, 11:17:06 PM »
Thank you.

4
Discovery / Re: Hourly Notices
« on: August 24, 2012, 05:08:31 PM »
By issue I mean a device going down and not responding to ICMP.

5
Discovery / Re: Hourly Notices
« on: August 22, 2012, 07:13:42 PM »
Thanks for the regexps tip, it worked perfectly!

Anyway, about this "nagging" saga (got your joke).. Let's say that a switch goes down @ 1am and NeDi sends out an email to my network admins. In our case, that email will have been burried by a lot of emails that each admin has to go through. So, it would be great if NeDi could send a reminder email every hour or so (again you choose the frequency) reminding the admin(s) that the issue still exists. There is a similar function in another tool that we use on the server side call Zenoss. With that tool, you can program how often to receive a reminder email until the issue is either closed or acknowledged by an admin.

Regards,
-C

6
Discovery / Re: Hourly Notices
« on: August 20, 2012, 10:03:21 PM »
By nagging I mean that it would be great if NeDi could send an email about an active issue until it is resolved. Is that possible in the current version?

Also, the "forward" feature in monitoring is pretty cool. If I want to add multiple forwarding (such as SPANTREE and Error Disable) how do I separate them. I tried adding them individually, but they overwrite each other. I type in SPANTREE and click on Update and then I type Error Disable and SPANTREE is overwritten.

Thanks,
-C

7
Discovery / Hourly Notices
« on: August 17, 2012, 02:23:44 PM »
Remo,
     As usual, I can only say good things about NeDi and how well it works to help us manage our Cisco infrastructure. As a possible feature, is there a possibility that NeDi can email admins to report an issue at a regular frequency until the issue is acknowledged or resolved? We receive hundreds of emails on a daily basis and sometimes NeDi emails get lost in the shuffle. This is generally not a big issue during the week as the NeDi GUI makes it easy to see what's up and what's down. But on the weekends however, it is kind of hard to check a GUI when your focus is on family. I think a "nag" email from NeDi every hour or so would certainly get your attention that something is wrong and had not been addressed. I've looked around the interface to find such a function, but have not found anything.

Thank you for your consideration,
-Carlos Lakomy

8
Discovery / WAN Discovery using 1.0.7
« on: July 13, 2012, 02:35:54 AM »
Rickli,
    It has been a while since I have bothered you, but I seem to be stuck in discovering across my since I upgraded from 1.0.5 to 1.0.7. My NeDi instance (running on Ubuntu) is on the 1.13.75.0 network in my HQ. HQ also has networks 1.13.50, 1.13.230, and 192.168.0.0 which I need to poll. On the WAN side, I have 17.3.124, 17.3.127, and 17.3.152 To limit the polling during discovery (-pob) phase, I added the netfilter to nedi.conf (netfilter   1.13.75.1|192.168|1.13.50|10.130.50|10.13.230|17.3.124|17.3.127|17.3.152). When I execute ./nedi.pl -pob, everything works fine and NeDi discovers everything on the LAN, but it never crosses across the WAN links. I tried using border, but I'm not exactly sure how it works. I entered the IP address of the WAN router local IP and the IP of the WAN router on the other side and still got nothing. I then tried a seedlist and added several WAN network devices and NeDi found them. I did that to proof that I could 100% access the WAN. Any ideas?

Thanks again, and I apologize for the remedial question as I should know the platform better by now..

-C

9
General Topics / Printer Toner
« on: April 07, 2011, 11:34:08 PM »
Rickli,
    It has been a while since I communicated with you and hope all is well. You may not recall, but I use NeDi to monitor over 1,000 network devices that support the US Tennis Open every year. This year, we are looking to also monitor a large number of HP and Xerox printers as well. I'm looking for toner levels and to receive syslog traps regarding paper jams and such. I do recall you writing something a while back about supporting printers, but I cannot recall. Is this something that can be done and if so what would I need to do. I have already added 10 printers in the seedlist file along with the community string, but so far nothing.
    As always, your assistance is always welcomed and much appreciated.

Regards,
-Carlos Lakomy

10
Definition Files / Does anyone have a good 1.3.6.1.4.1.9.1.745.def?
« on: March 18, 2010, 03:44:41 PM »
I've been racking my brain trying to create a def file for a 5505 ASA and have yet to reach success. Before I continue down this road, does anyone happen to have a working def for this device?

Thank you in advance,
-CLakomy

11
Installation / Enabling SSH
« on: October 15, 2009, 05:20:15 AM »
For those of you who have been banging your heads installing Net::SSH:Perl, I finally installed it by following some directions that addressed the YAM not installed issue.

From the terminal prompt (Ubuntu);

**This will install YAM**
1 - sudo apt-get install libyaml-perl

**Go into the CPAN interface/shell
2 - sudo perl -MCPAN -e

**Install/Verify that you have this digest installed
3 - install Digest::SHA1"

**Install/Verify that you have this digest installed
4 - install Digest::SHA"

**Finally, proceed with the SSH piece
5 - install Net::SSH:Perl

Hope these simple steps will work for you as it did for me. One issue though and you'll find this in the NEDI.CONF file. SSH will not use the EN password. So that is my next stumbling block.. If anyone has figured this out, do let me know.

Thanks,
-Carlos

PS - Hey Remo, hope all is well with you...

12
Installation / Path Problem on Ubuntu 9.04
« on: August 18, 2009, 02:20:36 AM »
Quick question...

I just installed NeDi on a Ubuntu 9.04 by following the directions for the same OS. I installed it in /opt/nedi as per the instructions. However, it looks like somewhere in the PL or PHP files is a path variable pointing to /var/.
Can someone tell me what file I have to update to set the correct path variable? Also, what would be the syntax?

Since I run the network system at the US Tennis Open, I have thousands of devices to monitor which is why I had to upgrade to this new server.

-Carlos Lakomy

Pages: [1]