Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Discovery question (Oliver Gorwits)
2. Re: How to modify a device type that is incorrectly listed?
(Oliver Gorwits)
--- Begin Message ---
Hi Barry
Thanks for upgrading!
I suggest you start with the doc for the discover_no_type setting here:
https://github.com/netdisco/netdisco/wiki/Configuration#code-discover_no_type-code
As you can see, since Netdisco 1.x we've added several settings which would
make control of discovery far simpler. You may be able to remove your
discover_no_type entry completely and just set discover_waps to false.
To clean out the job queue (which is the table called admin, confusingly),
run:
~/bin/netdisco-do psql -e 'delete from admin'
regards,
oliver.
On Mon, 8 Apr 2019 at 12:19, Dean, Barry <[email protected]> wrote:
> Firstly I give permission for you all to do a slow hand clap! I have just
> recently installed NetDisco 2.40.3, an upgrade from 1.1, look it’s not my
> fault that 1.1 was stable enough to be used all these years!
>
>
>
> When I initially started “netdisco-backend” I was missing the filter that
> prevented NetDisco from trying to inventory phones and APs via SNMP, I
> think I have this fixed now, but my job queue is still full of requests to
> scan these devices.
>
>
>
> Is there a database change I can make to stop it doing this? has it stored
> a “scan in the future” flag against these IPs? They are not in the devices
> table.
>
>
>
> If not I guess my filter is not working (same one I used on 1.1
> essentially):
>
>
>
> discover_no_type:
>
> - '(?i)phone'
>
> - '(?i)mitel'
>
> - '(?i)(?:wap|wireless)'
>
> - 'cisco\s+AIR-[LC]AP'
>
>
>
> But still I have lots of jobs for the APs (last entry). Any help
> appreciated. We are enjoying version 2.x and plan a switch off 1.1 as soon
> as I wrestle back control of the job queue!
>
>
>
> --
>
> *Barry Dean*
>
>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Similar reply to my recent message about adding a new model for Meru APs, I
think. Here's an excerpt:
The MIB file is in the netdisco-mibs folder but isn't actually loaded at
> runtime, so Netdisco (and more specifically the SNMP::Info library) can't
> do the translation [from registration/enterprises.x.x.x.x]. The MIBs to be
> loaded are specified by the SNMP::Info "Device Class" which you can see in
> Netdisco's Device Details tab, and I assume for this that either there's
> no specific class and you get the default one (SNMP::Info::Layer2 or
> whatever) or the Meru class isn't loading the MIB.
>
> So, assuming the former, the solution is to have a more specific
> SNMP::Info device class (SNMP::Info::Layer2::Meru for example) and then
> have that class load the MIB. The assigning of the class is done on things
> like matching the device's vendor (enterprises.15983).
>
> A nice design but not easy to access for the beginner. So do let us know
> if you can do the above, or else open a ticket in the SNMP::Info github
> repo and copy the above and it may get done. This certainly thinks we could
> benefit from a redesign to make on-boarding of new platforms somewhat
> easier.
>
On Thu, 4 Apr 2019 at 21:54, Nick Nauwelaerts <[email protected]>
wrote:
> seems this one never got answered.
>
>
>
> at first glance it seems to be due to either missing mibs or strange snmpd
> behaviour. could you provide us with the output of:
>
> netdisco-do discover -DI -d ip.of.your.device
>
>
>
> thx
>
>
>
> // nick
>
>
>
> *From:* Chris Hill [mailto:[email protected]]
> *Sent:* Sunday, March 10, 2019 00:56
> *To:* [email protected]
> *Subject:* [Netdisco] How to modify a device type that is incorrectly
> listed?
>
>
>
> Hello,
>
>
>
> Looking to somehow modify a device type listed as: registration.64.3.1.1.1.
> I know the correct model name. I have a few other examples on the network
> I’m currently discovering.
>
>
>
> How can I fix this so it’s listed correctly?
>
>
>
> Chris
>
> ------------------------------
>
> *Volg Aquafin op Facebook <https://www.facebook.com/AquafinNV> | Twitter
> <https://twitter.com/aquafinnv> | YouTube
> <http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?feature=mhee> |
> LinkedIN <http://www.linkedin.com/company/aquafin/products> | Instagram
> <https://www.instagram.com/aquafin_nv/> *
>
> In het kader van de uitoefening van onze taken verzamelen we bij Aquafin
> persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de
> betrokkenen zijn, kan je nalezen in onze privacy policy
> <https://www.aquafin.be/nl-be/privacy-policy>.
>
> P Denk aan het milieu. Druk deze mail niet onnodig af.
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
