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.


Topics - mduling

Pages: [1]
1
Discovery / nedi.conf - a way to use border inclusively?
« on: May 02, 2017, 08:29:00 PM »
Running Nedi-1.5C.  I run nedi.pl with the -pr option, since lldp on some devices returns a neighbor ip that is in a vrf nedi can't reach and I can't control that on Cisco so far as I know, so I use -pr and the nodes that nedi times out on are picked up later in the discovery via route tables so nothing is missed.

But for a couple of devices I want to stop nedi from following the route tables, so I use the border keyword. But then then it misses the devices themselves instead of just the devices in its route table.

So is there a way to have the border command to be interpreted to discover the border device, but nothing beyond it? Before trying it I had supposed that's the way it would work. Could the border keyword include the border device, rather than excluding it? I can work around it by running a separate discover job with a separate nedi.conf without -r. It works fine, but I'm just wondering if it might be a good feature, or perhaps others haven't run into this.

2
Discovery / descfilter again
« on: September 17, 2014, 03:16:00 AM »
I switched from nedi 1.0.7 to 1.0.9 and now I see all my cisco capwap aps.  The descfilter seems not to work now as it did before.  What am I missing?

descfilter   ^ATA|AIR-[CL]AP

3
Any idea why the sup doesn't show up as a module in nedi?  enterprises.9.1.875  Thanks.


Chassis Type : WS-C4506-E

Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
 1     6  Sup 7L-E 10GE (SFP+), 1000BaseX (SFP)  WS-X45-SUP7L-E

4
Definition Files / 8-port 2960 - WS-C2960PD-8TT-L
« on: May 08, 2013, 10:35:53 PM »
I have a WS-C2960PD-8TT-L that reports as SNMPv2-SMI::enterprises.9.1.952 so I did this:

cp 1.3.6.1.4.1.9.1.798.def 1.3.6.1.4.1.9.1.952.def

and changed the type from WS-C2960-8TC-L
to WS-C2960PD-8TT-L

5
Definition Files / WS-C4503-E def
« on: April 13, 2013, 12:24:55 AM »
I have a 4503-E (Supervisor 6L-E) switch that reports as SNMPv2-SMI::enterprises.9.1.874, so I just duplicated the def file that my other 4503's were using (503).

cp

1.3.6.1.4.1.9.1.503.def
to
1.3.6.1.4.1.9.1.874.def

It works fine.

6
Discovery / Threshold alerts on vlan interfaces
« on: March 28, 2013, 02:06:18 AM »
I'm seeing some discovery alerts on my vlan interfaces.  Here's one:

"having 94% inbound traffic exeeds alert threshold of 75% for 3600s!

Why would I see those on a logical (vlan) interface?

7
Moni email alerting is now working as of the latest 1.0.8 RC, but syslog forwarding still isn't working.  Or maybe I don't understand what it is supposed to do.  I set forwarding on at level "info" for a monitored device and it doesn't appear to be doing anything special with the messages it is receiving for the source.

Anyway, what I'd really like is to have a global setting to send all syslog events higher than X to be emailed.  I'd hacked nedi 1.0 to do this but the code has changed so I'm not sure how to do it anymore.  I had inserted the 2nd line below (lines 1 and 3 are for context) in nedi 1.0 syslog.pl:

print "$src ($_[0])\tS:$sev\tL:$level\t$msg\n"  if $opt{v};
   if( $level == 200){&mon::SendMail("Syslog Alert!","$src: $msg!")}
   if( ! &db::Insert('messages','level,time,source,info',"\"$level\",\"$now\",\"$src\",\"$msg\"")

What do I need to do in nedi 1.0.8 to get important syslog messages emailed to me?

8
I'm moving from nedi 1.0 to 1.08 RC so I don't know how long nedi has been using this new style of starting the daemons without startup scripts.  I like it, but I don't know how it works so I just wanted to ask a question about that.  If a daemon crashes for some reason will it be restarted automatically after some interval?

9
Installation / Can't get moni alerts in 1.0.8 RC
« on: March 16, 2013, 01:29:20 AM »
Still beating my head against a wall on this one.  With my nedi 1.0.8 RC install, discovery alerts are working fine, but moni.pl doesn't alert me on device up/down/reboot even though I have "mail repeat" selected.  What am I missing?  It isn't even trying to send emails as seen by the "0 emails".

RMON:3 entries (dev) read from nedi.monitoring
RMON:0 entries (node) read from nedi.monitoring
RUSR:1 entries (groups & 8 AND (phone != "" OR email != "")) read from nedi.users

TRGT:NetOps-3750  Deps=0    Test=uptime
SNMP:Connect 10.10.10.169 biolamon99 v2 Tout:2s MaxMS:1472
ERR :No response from remote host '10.10.10.169'
DOWN:EVNT:[moni] is down
ALRT:0 mails from 0 events and 0 SMS sent

But my nedi 1.0 install does moni alerts up/down/reboot just fine:

xoxoUser:   1 entries (WHERE mon = "1") read from nedi.user
 mailing "Moni  Alert!" to: admin

xoxoUser:   1 entries (WHERE mon = "1") read from nedi.user
 mailing "Moni Recovery" to: admin
User:   1 entries (WHERE mon = "1") read from nedi.user
 mailing "Moni Reboot Alert!" to: admin

10
Has anyone ever seen this issue?  NeDi identifies all of my WS-C4510R-E's as 1.3.6.1.4.1.9.1.877.def, as it should.  But one of them does not report its temperature on 1.3.6.1.4.1.9.9.13.1.3.1.3.1, but rather on 1.3.6.1.4.1.9.9.13.1.3.1.3.41.

Must be a Cisco issue of some sort, but can I tell NeDi for the same class of device to use a different sysobj?

11
Installation / 1.0.8 RC 027 can't check email option in monitor
« on: March 05, 2013, 07:53:37 AM »
Hello, I installed 027 and it is discovering fine on CentOS.  I can select the monitor button in the devices list and I see the device I checked in the monitor section with latency stats and such, but I can't check the email button on the devices in the alerts box.  It stays in condition "x" for alerts even after I've checked it.  Any idea what the problem could be?  Thanks.

12
Discovery / Full/Empty Devices interface report
« on: November 06, 2012, 02:04:35 AM »
I see from an earlier question that the Full/Empty devices report "counts the ports where incoming traffic has been detected".  Please pardon my ignorance here, but is that percentage reported what was seen at the last discovery?  I'm looking for some way to find the number of ports that are unused over a period of time.  Thanks.

13
GUI / Problem graphing serial (T1) interface
« on: October 07, 2009, 07:49:17 PM »
I am using NeDi 1.02.  When I select my T1 interface on a Cisco router in Devices -> Graph it doesn't create a working graph.  I really like the graphing module and this is the first problem I've had with it.

It creates the host in Cacti with the message - "Success - new device-id: (44)"
But in the next line where it should create the interface I see the message - "Try --list-snmp-fields"

My interface is 'Se0/2/0:0' and here are the relevant snmp info:

IF-MIB::ifDescr.5 = STRING: Serial0/2/0:0
IF-MIB::ifSpeed.5 = Gauge32: 1536000

IF-MIB::ifInOctets.5 = Counter32: 280069902
IF-MIB::ifOutOctets.5 = Counter32: 3238021034

Any help appreciated.  Thanks.

14
GUI / Feature request - sortable columns in Reports -> Modules
« on: February 24, 2009, 12:50:56 AM »
Remo, if possible could you please make the Reports -> Modules window sortable by providing a triangle next to the column heads just like in the Devices -> List window?  That would be sweet.

15
Discovery / Feasible for NeDi to track HP printer information?
« on: February 20, 2009, 09:07:00 PM »
Would it be feasible for NeDi to have a feature that tracked HP network printers, so that it could have a few key graphs of printer info?  Perhaps a Node => Printers
or something such that pages printed, toner level, etc. would be listed, as are the 3 Cisco graphs (mem, temp, cpu) are for devices.

Not sure if this is feasible, or if so if it would dilute the focus of NeDi, but I'm curious.  Thanks!

Pages: [1]