Welcome, Guest. Please login or register.

Author Topic: Anyone using descfilter?  (Read 1648 times)

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2632
    • View Profile
    • NeDi
Anyone using descfilter?
« on: October 24, 2017, 12:01:31 PM »
There's a descfilter option in nedi.conf, which let's you avoid discovering HP Laserprinters for example. Usually no one using this option, but I'm wondering if anyone relies on it?

I'm asking as I'm optimizing the discovery for 1.8 and may have to replace it with a name and sysobjidfilter instead...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Anyone using descfilter?
« Reply #1 on: November 08, 2017, 08:24:42 PM »
Is this the same as 'ignoredesc' because I can't find any 'descfilter' option in nedi.conf.
If there is another way to filter out these devices i'll change to that.

Code: [Select]
# Do not discover devices containing these strings in the description (e.g. Printers etc.)
ignoredesc      LaserJet|JETDIRECT|HP-UX|Windows|NTserver|snom|HiveAP|snom300-SIP

Mark.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2632
    • View Profile
    • NeDi
Re: Anyone using descfilter?
« Reply #2 on: November 29, 2017, 11:54:18 AM »
Oh yes it is :) It's been changed to ignoredesc to fit in with the rest. But I guess it's not that popular anyway...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Anyone using descfilter?
« Reply #3 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.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2632
    • View Profile
    • NeDi
Re: Anyone using descfilter?
« Reply #4 on: January 30, 2018, 06:47:05 PM »
Tx for the feedback. This option only applies to the description read via SNMP and won't affect CDP, LLDP or nosnmpdev at all.

It only made sense in rare cases, that's why I'd like to replace it. It seems nobody is using it anyway :-)

Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo