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

Pages: [1] 2 3 4
1
News / Re: Anyone using descfilter?
« on: January 24, 2018, 04:22:26 AM »
Hi Remo. It would be helpful if the comments for ignoredesc were more specific. For example, what desc is it looking for? lldp desc? I don't think CDP has a description field. Many of the lldp description fields devices report are generic such as 'Linux', but sometimes they're more specific.

For nosnmpdev, since I'm using that apparently "discovery protocol description" allows for using what CDP reports as 'Device ID', yet it would seem to also support CDP 'platform ID' since my regexp for that has one of each in it: AIR-([CL]|A)P|^S[EI]P

Also, does a match for nosnmpdev "not discover" as with ignoredesc? Not trying to get metaphysical here but since nedi is so uber flexible, sometimes I'm not sure what 'not discover' actually means. Does it mean not put it in the DB or put it in the DB but do nothing else with it? For nosnmpdev I know it means the latter. For ignoredesc I'm not sure.

2
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.

3
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

4
Well it looks like I was mistaken.  I went back to check on it and I do see these supervisors now.

5
News / Re: NeDi 1.0.9 Progress
« on: June 25, 2013, 02:27:38 AM »
What about something simple like markdown:  http://daringfireball.net/projects/markdown/basics  Not sure where the source files to be edited would be kept though.  Could we use a git repo?

In any case I think someone should be designated to edit and refine the contributions into a coherent whole.  I'd be glad to help out if I can.

6
1) Make sure your have an email account defined in User -> Profile and sending email works.

2) Make sure syslog.pl is running and you've edited it to listen on a different port than the default if you want to start/stop it in System -> Services  I use port 1514.

3) Set the device to send its syslog to nedi using the same port as the listener is set to.  I use 1514.  For example, "logging host <nedi_host_ip> transport udp port 1514"

If 2 & 3 above are all working, you can see that the device in question's log messages are showing up in Monitoring -> Events  That has to work before nedi will be able to forward anything.

4) In Monitoring -> Setup selet the device, and choose 'forward' and for level limit choose 'alert', and then click the Update button.

7
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

8
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

9
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.

10
Database / Re: cyclic DB clean up
« on: April 11, 2013, 07:46:22 PM »
Does this script need to be updated for 1.08?  I'm running the latest RC and it is giving me this:

optimizing tables (7/8)
+-----------------+----------+----------+-----------------------------------+
| Table           | Op       | Msg_type | Msg_text                          |
+-----------------+----------+----------+-----------------------------------+
| nedi.chat       | optimize | status   | Table is already up to date       |
| nedi.configs    | optimize | status   | Table is already up to date       |
| nedi.devdel     | optimize | Error    | Table 'nedi.devdel' doesn't exist |
| nedi.devdel     | optimize | status   | Operation failed                  |


Also, I was getting this message until I inserted a space between & and >>

./nedi_db_maintenance.sh: line 20: syntax error near unexpected token `>'
./nedi_db_maintenance.sh: line 20: `      mysql --host="$dbhost" --user="$dbuser" --password="$dbpass" "$dbname" --ssl -B -e "$sql" &>> $logfile'

11
Discovery / Re: Threshold alerts on vlan interfaces
« on: March 30, 2013, 02:00:40 AM »
I thought it wasn't the only one, but right now the only switch I can find that nedi reported errors on a vlan is a 2950.  We have few of those and I'm not worried about it.  Perhaps Cisco has end-of-lifed them anyway.

12
Discovery / Re: Threshold alerts on vlan interfaces
« on: March 30, 2013, 01:42:46 AM »
Yes I see those.  Here is one on one of my switch's vlan 3.  I obscured the actual vlan name but pasted the rest.

Vl3  - Myvlan_3  having 25449 inbound errors for 3600s!

13
Discovery / Re: Threshold alerts on vlan interfaces
« on: March 29, 2013, 10:46:20 PM »
Hmn.  Maybe I was confused.  I can't find the message I was referring to and I omitted the source when I pasted it.  Maybe it was just inbound errors on the vlan interface.

14
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?

15
Ok, I was just curious.  Thanks!

Pages: [1] 2 3 4