You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
(26) |
Jul
(35) |
Aug
(36) |
Sep
(56) |
Oct
(44) |
Nov
(31) |
Dec
(38) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(63) |
Feb
(88) |
Mar
(91) |
Apr
(68) |
May
(41) |
Jun
(102) |
Jul
(44) |
Aug
(25) |
Sep
(47) |
Oct
(106) |
Nov
(48) |
Dec
(65) |
| 2005 |
Jan
(125) |
Feb
(140) |
Mar
(67) |
Apr
(62) |
May
(52) |
Jun
(62) |
Jul
(60) |
Aug
(68) |
Sep
(57) |
Oct
(51) |
Nov
(141) |
Dec
(67) |
| 2006 |
Jan
(86) |
Feb
(108) |
Mar
(97) |
Apr
(134) |
May
(25) |
Jun
(67) |
Jul
(49) |
Aug
(40) |
Sep
(60) |
Oct
(84) |
Nov
(87) |
Dec
(27) |
| 2007 |
Jan
(69) |
Feb
(64) |
Mar
(32) |
Apr
(27) |
May
(7) |
Jun
(8) |
Jul
(17) |
Aug
(40) |
Sep
(27) |
Oct
(94) |
Nov
(83) |
Dec
(79) |
| 2008 |
Jan
(33) |
Feb
(19) |
Mar
(18) |
Apr
(8) |
May
(34) |
Jun
(51) |
Jul
(45) |
Aug
(24) |
Sep
(13) |
Oct
(2) |
Nov
(27) |
Dec
(26) |
| 2009 |
Jan
(28) |
Feb
(17) |
Mar
(55) |
Apr
(8) |
May
(35) |
Jun
(42) |
Jul
(9) |
Aug
(15) |
Sep
(28) |
Oct
(15) |
Nov
(75) |
Dec
(74) |
| 2010 |
Jan
(26) |
Feb
(14) |
Mar
(39) |
Apr
(67) |
May
(45) |
Jun
(40) |
Jul
(118) |
Aug
(54) |
Sep
(19) |
Oct
(25) |
Nov
(29) |
Dec
(19) |
| 2011 |
Jan
(45) |
Feb
(23) |
Mar
(6) |
Apr
(49) |
May
(18) |
Jun
(13) |
Jul
(14) |
Aug
(30) |
Sep
(7) |
Oct
(23) |
Nov
(17) |
Dec
(35) |
| 2012 |
Jan
(12) |
Feb
(12) |
Mar
(16) |
Apr
(26) |
May
(19) |
Jun
(21) |
Jul
(57) |
Aug
(30) |
Sep
(46) |
Oct
(35) |
Nov
(23) |
Dec
(67) |
| 2013 |
Jan
(49) |
Feb
(52) |
Mar
(10) |
Apr
(42) |
May
(33) |
Jun
(25) |
Jul
(7) |
Aug
(39) |
Sep
(41) |
Oct
(55) |
Nov
(56) |
Dec
(47) |
| 2014 |
Jan
(25) |
Feb
(23) |
Mar
(68) |
Apr
(63) |
May
(67) |
Jun
(62) |
Jul
(59) |
Aug
(78) |
Sep
(36) |
Oct
(54) |
Nov
(58) |
Dec
(77) |
| 2015 |
Jan
(45) |
Feb
(87) |
Mar
(88) |
Apr
(48) |
May
(45) |
Jun
(14) |
Jul
(22) |
Aug
(38) |
Sep
(26) |
Oct
(52) |
Nov
(50) |
Dec
(22) |
| 2016 |
Jan
(23) |
Feb
(47) |
Mar
(10) |
Apr
(21) |
May
(22) |
Jun
(30) |
Jul
(17) |
Aug
(10) |
Sep
(12) |
Oct
(30) |
Nov
(30) |
Dec
(8) |
| 2017 |
Jan
(17) |
Feb
(28) |
Mar
(8) |
Apr
(4) |
May
(21) |
Jun
(59) |
Jul
(34) |
Aug
(50) |
Sep
|
Oct
(21) |
Nov
(6) |
Dec
(40) |
| 2018 |
Jan
(51) |
Feb
(32) |
Mar
(43) |
Apr
(18) |
May
(13) |
Jun
(5) |
Jul
(1) |
Aug
(27) |
Sep
(16) |
Oct
(47) |
Nov
(6) |
Dec
(27) |
| 2019 |
Jan
(20) |
Feb
(25) |
Mar
(12) |
Apr
(32) |
May
(15) |
Jun
(14) |
Jul
(11) |
Aug
(27) |
Sep
(34) |
Oct
(25) |
Nov
(22) |
Dec
(6) |
| 2020 |
Jan
(42) |
Feb
(32) |
Mar
(2) |
Apr
(10) |
May
(7) |
Jun
(10) |
Jul
(8) |
Aug
(12) |
Sep
(30) |
Oct
(28) |
Nov
(10) |
Dec
(8) |
| 2021 |
Jan
(11) |
Feb
(15) |
Mar
(14) |
Apr
(26) |
May
(14) |
Jun
(22) |
Jul
(14) |
Aug
(25) |
Sep
(33) |
Oct
(1) |
Nov
(35) |
Dec
(7) |
| 2022 |
Jan
(15) |
Feb
(7) |
Mar
(3) |
Apr
|
May
(8) |
Jun
(5) |
Jul
(8) |
Aug
(25) |
Sep
(17) |
Oct
(19) |
Nov
(4) |
Dec
(5) |
| 2023 |
Jan
(19) |
Feb
(8) |
Mar
(49) |
Apr
(4) |
May
(5) |
Jun
(14) |
Jul
(13) |
Aug
(10) |
Sep
(3) |
Oct
(18) |
Nov
(22) |
Dec
(27) |
| 2024 |
Jan
(18) |
Feb
(6) |
Mar
(7) |
Apr
(11) |
May
(2) |
Jun
(10) |
Jul
(24) |
Aug
(14) |
Sep
(38) |
Oct
(19) |
Nov
|
Dec
(17) |
| 2025 |
Jan
(8) |
Feb
(3) |
Mar
(19) |
Apr
(18) |
May
(16) |
Jun
(2) |
Jul
(14) |
Aug
(21) |
Sep
(27) |
Oct
(9) |
Nov
(12) |
Dec
(1) |
| 2026 |
Jan
(8) |
Feb
(10) |
Mar
(4) |
Apr
(10) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(12) |
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
|
|
From: Eric M. <er...@je...> - 2026-11-12 03:36:25
|
Hi Damon, Netdisco 2.118000, released this week, reads Arista EOS VRFs over SNMP. With the new store_vrfs setting on, discover and arpnip read each VRF in its own SNMP context, community@VRF over SNMPv2c or the VRF name as the SNMPv3 context, and store its addresses, subnets and ARP entries under that VRF. The EOS SSH collector does the same for ARP entries and subnets. It is off by default. The setting is described here: https://github.com/netdisco/netdisco/wiki/Configuration#store_vrfs Eric On Aug 25, 2026, at 4:49 PM, "Beals, Damon G via netdisco-users" <net...@li...> wrote: Yeah I just tried to limit the Arista to using community@VRF and looks like discovery tries to do a .1.3.6.1.2.1.1.3.0 which is sysuptime, and of course that fails in the VRF but works in main. I will mess with SnmpV3 and see if that might work any better. I think I found a bug in the latest version 2.105.3, if it do a netdisco-do dumpconfig if dies with a undef.. ~/bin/netdisco-do dumpconfig [345380] 2026-08-25 18:02:59 info App::Netdisco version 2.105003 loaded. [345380] 2026-08-25 18:02:59 info dumpconfig: started at Tue Aug 25 14:02:59 2026 undef [345380] 2026-08-25 18:02:59 info dumpconfig: finished at Tue Aug 25 14:02:59 2026 [345380] 2026-08-25 18:02:59 info dumpconfig: status done: Dumped config Damon Beals Network Architect Indiana University 317.274.7946 From: Michael Butash <mi...@bu...> Sent: Tuesday, August 25, 2026 12:14 To: net...@li... <net...@li...> Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? VRF's have been an issue for any snmp management open or commercial since people started using them in the early 2000's with MPLS, later with firewall vendor contexts, and mostly screws over management tools where ever this is used. Most NMS's doing discovery don't expect to hit a single node pretending to be multiple nodes, almost universally they crap the bed when you try, and mostly the same situation here. Your best bet is to treat them as separate, different devices, but if I remember Netdisco will typically see enough by serial number and such to attribute them as the same device, and still try to lump them together incorrectly. Netdisco just requires some fundamental changes to allow multiple of the same devices as separate instances, and I'm not at all sure how hard that would be. I'd say ask an LLM and see these days if something that can be cleanly done. -mb On Tue, Aug 25, 2026 at 8:55 AM Beals, Damon G via netdisco-users < net...@li... > wrote: Thanks for the response, I didn't realize this was an issue, I thought it was just a config issue. I think I will try to modify the config so that only the Arista switches will use community@VRF, and the other devices will use community. Right now we only have one VRF to deal with, but we do plan on doing more. Damon Beals Network Architect Indiana University 317.274.7946 From: Christian Ramseyer < ram...@ne... > Sent: Friday, August 21, 2026 19:02 To: Beals, Damon G < db...@iu... >; net...@li... < net...@li... > Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? Hi Damon The mailing list is still in use but it's not so frequented anymore, so for visibility github might be a bit better. Anyways I'm afraid for Arista there is currently no support to use SNMP this way. Cisco has a similar feature where a vlan can be appended and Netdisco is using these through special hints in the respective snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to find out more. There's also an snmp v3 variant, where the better formalized snmp v3 context can be used in a similar way, even for VRFs https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FVendor-Tips%23vrfs-and-nxos&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421158854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S63SD8cZWiULsWHQiVY%2B%2Ftpeb5cJQLaGVcaPiwiJvJ8%3D&reserved=0 Lastly there is a third way that is used with many vendors, which is not using snmp but SSH to run specific commands for arp and mac-address table collection: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Ftree%2Fmaster%2Flib%2FApp%2FNetdisco%2FSSHCollector%2FPlatform&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421186948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kjqImd0oB6oNgsHBEaY4tE4U6zUSZ464Tv2F1xcqPNk%3D&reserved=0 But from quickly looking at all of these things it seems there is nothing already working for Arista. You'd need to either experiment yourself or get some motivated colleagues/students/LLMs to do it. If you get it to work, pull requests for snmp-info or Netdisco are of course highly appreciated. How to get started with hacking is in https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FDeveloping%23tldr-i-just-want-to-clone-the-repo-and-get-started&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421205401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kcy49cPzyO%2BgZcebEtH6xHfK%2Bp7JlerreinbgbkKWUw%3D&reserved=0 Cheers Christian On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: > Is this email list still active? Or should I just open a ticket on github? > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > ------------------------------------------------------------------------ > *From:* Beals, Damon G via netdisco-users <netdisco- > us...@li... > > *Sent:* Tuesday, August 18, 2026 13:48 > *To:* net...@li... <netdisco- e > us...@li... > > *Subject:* [External] [Netdisco] Using two or more snmp communities for > the same node? > This message was sent from a non-IU address. Please exercise caution > when clicking links or opening attachments from external sources. > > So I just discovered our Arista switches can provide information about a > VRF if you add the VRF to the snmp community. For example > community@VRF. Doing test via snmpwalks, I do get the information from > that VRF. > > My question is, how do I get netdisco to use both community, and > community@VRF for the same node, or what if we have 4 or 5 VRF we need > to collect from? From my test it looks like once netdisco finds a > working snmp it caches that community and doesn't use others? > > >From the docs > "Each is tried in turn when polling the device, and then the working > community string will be cached in the database. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco-users%2F&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421228299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ed2laTG%2FGykuO9rJvY%2BOpKCbB3%2BilSBiWGgXsHX1ZWY%3D&reserved=0 _______________________________________________ Netdisco mailing list net...@li... https://sourceforge.net/p/netdisco/mailman/netdisco-users/ _______________________________________________ Netdisco mailing list net...@li... https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
|
From: Andy M. <an...@un...> - 2026-10-27 09:21:07
|
Hi mailing list, I’m writing to share an update on the Meraki integration work discussed around NetDisco issue #1369: https://github.com/netdisco/netdisco/issues/1369 The work started from osmogr’s netdisco-meraki project, which provided a valuable, working foundation for bringing Meraki Dashboard data into NetDisco. We’re grateful for that initial implementation. Building on it, we’ve developed and tested a more complete site-local extension against a NetDisco deployment: https://github.com/osmogr/netdisco-meraki The extension keeps SNMP discovery as NetDisco’s normal device-discovery path and uses the Dashboard API to enrich information that SNMP does not provide reliably. It currently provides: - Device enrichment by a unique serial match, including firmware/software version, chassis/serial identity, MAC address, and location, while retaining the SNMP-discovered management IP. - Meraki MS switch port names and state, native VLAN and VLAN membership, plus available topology/neighbour information. MX/Z appliance VLAN interfaces, routed addresses, and verified management CIDR data are also represented. - Available STP and PoE state, supported power-supply inventory, and MR access-point SSID/BSSID and radio band/channel/power data, using NetDisco’s existing tables. - Client MAC/IP observations through NetDisco’s native macsuck and arpnip workers. Wired clients are placed only when the Dashboard serial and switch port map to known NetDisco records. Wireless clients are associated with a uniquely matched AP on a logical wireless interface, with SSID observations stored separately. This supports the built-in AP Client Count report and adds AP-total and AP-by-SSID reports. - Pagination, rate-limit and transient-error handling, and snapshot reconciliation that preserves existing data when an API response is incomplete or invalid. A Meraki macsuck hook also reconciles VLAN 0 duplicates when a recent API observation provides a matching nonzero VLAN. The NetDisco integration is currently a standalone site-local extension: worker plugins are loaded through extra_worker_plugins, the reports through extra_web_plugins, and discovery/client data is handled in worker phases. It does not require a NetDisco core fork or schema change. merakisync handles initial or targeted inventory work; merakiclients handles recurring client updates. On our test deployment we reduced the client poll to hourly because the normal macsuck and arpnip waves already take a substantial portion of their hourly cycle. The current client path still launches native per-device ingest commands, so reducing that fan-out and aligning client data with normal per-device worker processing is an important next step. We validated the extension on a NetDisco 2.112 test host. In one client-poll check, 1,074 current AP client associations were visible across 247 APs, and the AP-total and per-SSID counts reconciled. This is representative validation, not exhaustive coverage of every Meraki family or client-movement case. Our proposed longer-term direction is to fetch and paginate each network’s client snapshot once, stage only complete results, then let normal per-device macsuck/arpnip workers consume the relevant observations. That should avoid a separate command per affected device and make API data easier to schedule and reconcile alongside NetDisco’s existing collection. There are known limits: Dashboard does not reliably identify the client’s physical radio band, the API does not provide the signal-quality history needed for RSSI/SNR reporting in our test organization, and client placement reflects the online/recent API view rather than a continuous event stream. We’re also considering how best to align API requests with a shared NetDisco HTTP transport if that is the project’s preferred direction. SNMP::Info device recognition is a separate workstream in netdisco/snmp-info PR #627; it is not part of these API integration changes: https://github.com/netdisco/snmp-info/pull/627 I’ve asked in the original repository and issue discussion about the preferred contribution route but haven’t yet heard back. I’d appreciate maintainers’ advice: should we prepare a draft PR against osmogr’s repository, continue this as a separately maintained extension, or propose moving the appropriate pieces into NetDisco itself? We want to preserve credit for the original work and follow the project’s preferred architecture before publishing a fork or opening a PR. The current implementation and its detailed change history are available in our working copy; I can provide a fork or draft PR for review once we’ve agreed on the right destination. Finally, it would be remiss of me not to mention that a substantial amount of the work on this has been done with the use of Codex. Thanks, Andy |
|
From: Eric M. <er...@je...> - 2026-10-12 00:41:23
|
Hi all, We have started a series of database changes aimed at four questions commonly asked: Why does my database need so much maintenance? Which MAC or IP addresses are duplicated, and where? Was a device or address really absent, or just not polled? Can Netdisco handle the same addresses reused in different VRFs or VXLAN segments? The plan, in phases, is tracked here: https://github.com/netdisco/netdisco/issues/1728 A future release will need PostgreSQL 14 or newer. Until then Netdisco keeps working with 9.6 and newer. Netdisco's Docker images already ship PostgreSQL 18, and every supported long-term distribution packages 14 or newer. The current minimum, and whether your distribution's PostgreSQL is new enough, are at the top of the Release Notes: https://github.com/netdisco/netdisco/wiki/Release-Notes#minimum-postgresql-version We would like to hear from you, on the issue or on this list, if you: run Netdisco on PostgreSQL older than 14 run an SPB, VXLAN or MLAG network query Netdisco's database directly with your own SQL, from custom reports or from other tools such as Grafana Thanks, Eric |
|
From: Golden, S. <sco...@gl...> - 2026-09-30 17:37:54
|
trying to update and i get the following error netdisco@netdisco:~$ ~/bin/localenv cpanm --notest --force App::Netdisco --> Working on App::Netdisco Fetching http://www.cpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.109001.tar.gz ... OK Configuring App-Netdisco-2.109001 ... OK ==> Found dependencies: Authen::TacacsPlus --> Working on Authen::TacacsPlus Fetching http://www.cpan.org/authors/id/M/MI/MIKEM/Authen-TacacsPlus-0.28.tar.gz ... OK Configuring Authen-TacacsPlus-0.28 ... OK Building Authen-TacacsPlus-0.28 ... FAIL ! Installing Authen::TacacsPlus failed. See /home/netdisco/.cpanm/work/1790787773.1830/build.log for details. Retry with --force to force install it. ! Installing the dependencies failed: Module 'Authen::TacacsPlus' is not installed ! Bailing out the installation for App-Netdisco-2.109001. this iis on ubuntu 26.04.1 LTS *Scott Golden* Senior Systems Analyst Boston Globe Media Partners, LLC 978-340-8207 sco...@gl... |
|
From: Mackie, P. <Pau...@ge...> - 2026-08-27 13:42:04
|
Hi everyone, I have a problem with Netdisco (official Docker image) that has only started in recent months. I can't pinpoint it, but jobs just seem to get stuck in the queue and never execute (discover,macsuck and arpnip). Even if I clear the job queue they will return (as expected) and get stuck before ever executing. But if I discover manually via GUI or netdisco-do, it works first time and then also completes the 'stuck' arpnip and macsuck jobs directly afterwards. Is there anything different between an automated discover and a manual discover? Is there anything I can do to debug a device and see exactly what happens when the first job is created after clearing the job queue? I did a tcpdump and I'm pretty sure the discover is never attempted. Thanks in advance for any advice you may have... App::Netdisco 2.105.3 SNMP::Info 3.977.0 DB Schema 99 PostgreSQL 18.00.6 Perl 5.42.2 Python 3.14.7 Best regards, Paul Mackie Network & Cloud Solution Architect GEA INTERNAL |
|
From: Eric M. <er...@je...> - 2026-08-26 02:12:39
|
Thanks for the report. You are right that nothing was dumped. The "Dumped config" line made it look like the job had worked, when in fact it printed nothing at all. This is fixed and will be in the next release. Versions 2.104000 through 2.105003 are affected. Until then you can still dump a single setting, which was never broken: ~/bin/netdisco-do dumpconfig -p workers That takes one top-level setting name. On Aug 25, 2026, at 4:49 PM, "Beals, Damon G via netdisco-users" <net...@li...> wrote: Yeah I just tried to limit the Arista to using community@VRF and looks like discovery tries to do a .1.3.6.1.2.1.1.3.0 which is sysuptime, and of course that fails in the VRF but works in main. I will mess with SnmpV3 and see if that might work any better. I think I found a bug in the latest version 2.105.3, if it do a netdisco-do dumpconfig if dies with a undef.. ~/bin/netdisco-do dumpconfig [345380] 2026-08-25 18:02:59 info App::Netdisco version 2.105003 loaded. [345380] 2026-08-25 18:02:59 info dumpconfig: started at Tue Aug 25 14:02:59 2026 undef [345380] 2026-08-25 18:02:59 info dumpconfig: finished at Tue Aug 25 14:02:59 2026 [345380] 2026-08-25 18:02:59 info dumpconfig: status done: Dumped config Damon Beals Network Architect Indiana University 317.274.7946 From: Michael Butash <mi...@bu...> Sent: Tuesday, August 25, 2026 12:14 To: net...@li... <net...@li...> Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? VRF's have been an issue for any snmp management open or commercial since people started using them in the early 2000's with MPLS, later with firewall vendor contexts, and mostly screws over management tools where ever this is used. Most NMS's doing discovery don't expect to hit a single node pretending to be multiple nodes, almost universally they crap the bed when you try, and mostly the same situation here. Your best bet is to treat them as separate, different devices, but if I remember Netdisco will typically see enough by serial number and such to attribute them as the same device, and still try to lump them together incorrectly. Netdisco just requires some fundamental changes to allow multiple of the same devices as separate instances, and I'm not at all sure how hard that would be. I'd say ask an LLM and see these days if something that can be cleanly done. -mb On Tue, Aug 25, 2026 at 8:55 AM Beals, Damon G via netdisco-users < net...@li... > wrote: Thanks for the response, I didn't realize this was an issue, I thought it was just a config issue. I think I will try to modify the config so that only the Arista switches will use community@VRF, and the other devices will use community. Right now we only have one VRF to deal with, but we do plan on doing more. Damon Beals Network Architect Indiana University 317.274.7946 From: Christian Ramseyer < ram...@ne... > Sent: Friday, August 21, 2026 19:02 To: Beals, Damon G < db...@iu... >; net...@li... < net...@li... > Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? Hi Damon The mailing list is still in use but it's not so frequented anymore, so for visibility github might be a bit better. Anyways I'm afraid for Arista there is currently no support to use SNMP this way. Cisco has a similar feature where a vlan can be appended and Netdisco is using these through special hints in the respective snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to find out more. There's also an snmp v3 variant, where the better formalized snmp v3 context can be used in a similar way, even for VRFs https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FVendor-Tips%23vrfs-and-nxos&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421158854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S63SD8cZWiULsWHQiVY%2B%2Ftpeb5cJQLaGVcaPiwiJvJ8%3D&reserved=0 Lastly there is a third way that is used with many vendors, which is not using snmp but SSH to run specific commands for arp and mac-address table collection: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Ftree%2Fmaster%2Flib%2FApp%2FNetdisco%2FSSHCollector%2FPlatform&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421186948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kjqImd0oB6oNgsHBEaY4tE4U6zUSZ464Tv2F1xcqPNk%3D&reserved=0 But from quickly looking at all of these things it seems there is nothing already working for Arista. You'd need to either experiment yourself or get some motivated colleagues/students/LLMs to do it. If you get it to work, pull requests for snmp-info or Netdisco are of course highly appreciated. How to get started with hacking is in https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FDeveloping%23tldr-i-just-want-to-clone-the-repo-and-get-started&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421205401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kcy49cPzyO%2BgZcebEtH6xHfK%2Bp7JlerreinbgbkKWUw%3D&reserved=0 Cheers Christian On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: > Is this email list still active? Or should I just open a ticket on github? > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > ------------------------------------------------------------------------ > *From:* Beals, Damon G via netdisco-users <netdisco- > us...@li... > > *Sent:* Tuesday, August 18, 2026 13:48 > *To:* net...@li... <netdisco- e > us...@li... > > *Subject:* [External] [Netdisco] Using two or more snmp communities for > the same node? > This message was sent from a non-IU address. Please exercise caution > when clicking links or opening attachments from external sources. > > So I just discovered our Arista switches can provide information about a > VRF if you add the VRF to the snmp community. For example > community@VRF. Doing test via snmpwalks, I do get the information from > that VRF. > > My question is, how do I get netdisco to use both community, and > community@VRF for the same node, or what if we have 4 or 5 VRF we need > to collect from? From my test it looks like once netdisco finds a > working snmp it caches that community and doesn't use others? > > >From the docs > "Each is tried in turn when polling the device, and then the working > community string will be cached in the database. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco-users%2F&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421228299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ed2laTG%2FGykuO9rJvY%2BOpKCbB3%2BilSBiWGgXsHX1ZWY%3D&reserved=0 _______________________________________________ Netdisco mailing list net...@li... https://sourceforge.net/p/netdisco/mailman/netdisco-users/ _______________________________________________ Netdisco mailing list net...@li... https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
|
From: Beals, D. G <db...@iu...> - 2026-08-25 20:48:50
|
Yeah I just tried to limit the Arista to using community@VRF and looks like discovery tries to do a .1.3.6.1.2.1.1.3.0 which is sysuptime, and of course that fails in the VRF but works in main. I will mess with SnmpV3 and see if that might work any better. I think I found a bug in the latest version 2.105.3, if it do a netdisco-do dumpconfig if dies with a undef.. ~/bin/netdisco-do dumpconfig [345380] 2026-08-25 18:02:59 info App::Netdisco version 2.105003 loaded. [345380] 2026-08-25 18:02:59 info dumpconfig: started at Tue Aug 25 14:02:59 2026 undef [345380] 2026-08-25 18:02:59 info dumpconfig: finished at Tue Aug 25 14:02:59 2026 [345380] 2026-08-25 18:02:59 info dumpconfig: status done: Dumped config Damon Beals Network Architect Indiana University 317.274.7946 ________________________________ From: Michael Butash <mi...@bu...> Sent: Tuesday, August 25, 2026 12:14 To: net...@li... <net...@li...> Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? VRF's have been an issue for any snmp management open or commercial since people started using them in the early 2000's with MPLS, later with firewall vendor contexts, and mostly screws over management tools where ever this is used. Most NMS's doing discovery don't expect to hit a single node pretending to be multiple nodes, almost universally they crap the bed when you try, and mostly the same situation here. Your best bet is to treat them as separate, different devices, but if I remember Netdisco will typically see enough by serial number and such to attribute them as the same device, and still try to lump them together incorrectly. Netdisco just requires some fundamental changes to allow multiple of the same devices as separate instances, and I'm not at all sure how hard that would be. I'd say ask an LLM and see these days if something that can be cleanly done. -mb On Tue, Aug 25, 2026 at 8:55 AM Beals, Damon G via netdisco-users <net...@li...<mailto:net...@li...>> wrote: Thanks for the response, I didn't realize this was an issue, I thought it was just a config issue. I think I will try to modify the config so that only the Arista switches will use community@VRF, and the other devices will use community. Right now we only have one VRF to deal with, but we do plan on doing more. Damon Beals Network Architect Indiana University 317.274.7946 ________________________________ From: Christian Ramseyer <ram...@ne...<mailto:ram...@ne...>> Sent: Friday, August 21, 2026 19:02 To: Beals, Damon G <db...@iu...<mailto:db...@iu...>>; net...@li...<mailto:net...@li...> <net...@li...<mailto:net...@li...>> Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? Hi Damon The mailing list is still in use but it's not so frequented anymore, so for visibility github might be a bit better. Anyways I'm afraid for Arista there is currently no support to use SNMP this way. Cisco has a similar feature where a vlan can be appended and Netdisco is using these through special hints in the respective snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to find out more. There's also an snmp v3 variant, where the better formalized snmp v3 context can be used in a similar way, even for VRFs https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FVendor-Tips%23vrfs-and-nxos&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421158854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S63SD8cZWiULsWHQiVY%2B%2Ftpeb5cJQLaGVcaPiwiJvJ8%3D&reserved=0<https://github.com/netdisco/netdisco/wiki/Vendor-Tips#vrfs-and-nxos> Lastly there is a third way that is used with many vendors, which is not using snmp but SSH to run specific commands for arp and mac-address table collection: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Ftree%2Fmaster%2Flib%2FApp%2FNetdisco%2FSSHCollector%2FPlatform&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421186948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kjqImd0oB6oNgsHBEaY4tE4U6zUSZ464Tv2F1xcqPNk%3D&reserved=0<https://github.com/netdisco/netdisco/tree/master/lib/App/Netdisco/SSHCollector/Platform> But from quickly looking at all of these things it seems there is nothing already working for Arista. You'd need to either experiment yourself or get some motivated colleagues/students/LLMs to do it. If you get it to work, pull requests for snmp-info or Netdisco are of course highly appreciated. How to get started with hacking is in https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FDeveloping%23tldr-i-just-want-to-clone-the-repo-and-get-started&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421205401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kcy49cPzyO%2BgZcebEtH6xHfK%2Bp7JlerreinbgbkKWUw%3D&reserved=0<https://github.com/netdisco/netdisco/wiki/Developing#tldr-i-just-want-to-clone-the-repo-and-get-started> Cheers Christian On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: > Is this email list still active? Or should I just open a ticket on github? > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > ------------------------------------------------------------------------ > *From:* Beals, Damon G via netdisco-users <netdisco- > us...@li...<mailto:us...@li...>> > *Sent:* Tuesday, August 18, 2026 13:48 > *To:* net...@li...<mailto:net...@li...> <netdisco- e > us...@li...<mailto:us...@li...>> > *Subject:* [External] [Netdisco] Using two or more snmp communities for > the same node? > This message was sent from a non-IU address. Please exercise caution > when clicking links or opening attachments from external sources. > > So I just discovered our Arista switches can provide information about a > VRF if you add the VRF to the snmp community. For example > community@VRF. Doing test via snmpwalks, I do get the information from > that VRF. > > My question is, how do I get netdisco to use both community, and > community@VRF for the same node, or what if we have 4 or 5 VRF we need > to collect from? From my test it looks like once netdisco finds a > working snmp it caches that community and doesn't use others? > > >From the docs > "Each is tried in turn when polling the device, and then the working > community string will be cached in the database. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > > _______________________________________________ > Netdisco mailing list > net...@li...<mailto:net...@li...> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco-users%2F&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421228299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ed2laTG%2FGykuO9rJvY%2BOpKCbB3%2BilSBiWGgXsHX1ZWY%3D&reserved=0<https://sourceforge.net/p/netdisco/mailman/netdisco-users/> _______________________________________________ Netdisco mailing list net...@li...<mailto:net...@li...> https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
|
From: Christian R. <ram...@ne...> - 2026-08-25 20:06:17
|
Good news, I've now noticed that the EOS Collector that @robertlynch3 submitted a while ago already has VRF support for subnets + arp tables: https://github.com/netdisco/netdisco/blame/master/lib/App/Netdisco/SSHCollector/Platform/EOS.pm So I'd just try using that. But before I noticed this I had Codex draft a quick combined patch for snmp-info + Netdisco, it could serve as an outline if anybody is really serious about this: https://gist.github.com/rc9000/0b07e2a240b62e3445ad353eb2431535 (completely untested, 100% AI, I haven't touched an Arista device in my life, but looks good to me as a first step) Cheers Christian On 25.08.2026 17:38, Beals, Damon G wrote: > Thanks for the response, I didn't realize this was an issue, I thought > it was just a config issue. > > I think I will try to modify the config so that only the Arista switches > will use community@VRF, and the other devices will use community. Right > now we only have one VRF to deal with, but we do plan on doing more. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > ------------------------------------------------------------------------ > *From:* Christian Ramseyer <ram...@ne...> > *Sent:* Friday, August 21, 2026 19:02 > *To:* Beals, Damon G <db...@iu...>; netdisco- > us...@li... <net...@li...> > *Subject:* Re: [Netdisco] [External] Using two or more snmp communities > for the same node? > Hi Damon > > The mailing list is still in use but it's not so frequented anymore, so > for visibility github might be a bit better. > > Anyways I'm afraid for Arista there is currently no support to use SNMP > this way. Cisco has a similar feature where a vlan can be appended and > Netdisco is using these through special hints in the respective > snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to > find out more. > > There's also an snmp v3 variant, where the better formalized snmp v3 > context can be used in a similar way, even for VRFs > https://nam12.safelinks.protection.outlook.com/? > url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FVendor- > Tips%23vrfs-and- > nxos&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421158854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S63SD8cZWiULsWHQiVY%2B%2Ftpeb5cJQLaGVcaPiwiJvJ8%3D&reserved=0 <https://github.com/netdisco/netdisco/wiki/Vendor-Tips#vrfs-and-nxos> > > Lastly there is a third way that is used with many vendors, which is not > using snmp but SSH to run specific commands for arp and mac-address > table collection: > https://nam12.safelinks.protection.outlook.com/? > url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Ftree%2Fmaster%2Flib%2FApp%2FNetdisco%2FSSHCollector%2FPlatform&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421186948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kjqImd0oB6oNgsHBEaY4tE4U6zUSZ464Tv2F1xcqPNk%3D&reserved=0 <https://github.com/netdisco/netdisco/tree/master/lib/App/Netdisco/SSHCollector/Platform> > > But from quickly looking at all of these things it seems there is > nothing already working for Arista. You'd need to either experiment > yourself or get some motivated colleagues/students/LLMs to do it. If you > get it to work, pull requests for snmp-info or Netdisco are of course > highly appreciated. How to get started with hacking is in > https://nam12.safelinks.protection.outlook.com/? > url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FDeveloping%23tldr-i-just-want-to-clone-the-repo-and-get-started&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421205401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kcy49cPzyO%2BgZcebEtH6xHfK%2Bp7JlerreinbgbkKWUw%3D&reserved=0 <https://github.com/netdisco/netdisco/wiki/Developing#tldr-i-just-want-to-clone-the-repo-and-get-started> > > Cheers > Christian > > > > On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: >> Is this email list still active? Or should I just open a ticket on github? >> >> Damon Beals >> Network Architect >> Indiana University >> 317.274.7946 >> >> ------------------------------------------------------------------------ >> *From:* Beals, Damon G via netdisco-users <netdisco- >> us...@li...> >> *Sent:* Tuesday, August 18, 2026 13:48 >> *To:* net...@li... <netdisco- e >> us...@li...> >> *Subject:* [External] [Netdisco] Using two or more snmp communities for >> the same node? >> This message was sent from a non-IU address. Please exercise caution >> when clicking links or opening attachments from external sources. >> >> So I just discovered our Arista switches can provide information about a >> VRF if you add the VRF to the snmp community. For example >> community@VRF. Doing test via snmpwalks, I do get the information from >> that VRF. >> >> My question is, how do I get netdisco to use both community, and >> community@VRF for the same node, or what if we have 4 or 5 VRF we need >> to collect from? From my test it looks like once netdisco finds a >> working snmp it caches that community and doesn't use others? >> >> >From the docs >> "Each is tried in turn when polling the device, and then the working >> community string will be cached in the database. >> >> Damon Beals >> Network Architect >> Indiana University >> 317.274.7946 >> >> >> _______________________________________________ >> Netdisco mailing list >> net...@li... >> https://nam12.safelinks.protection.outlook.com/? > url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco- > users%2F&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421228299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ed2laTG%2FGykuO9rJvY%2BOpKCbB3%2BilSBiWGgXsHX1ZWY%3D&reserved=0 <https://sourceforge.net/p/netdisco/mailman/netdisco-users/> > -- Christian Ramseyer, netnea ag Network Management. Security. OpenSource. https://www.netnea.com Phone: +41 79 644 77 64 |
|
From: Victor L. <vl...@bm...> - 2026-08-25 18:13:08
|
|
From: Michael B. <mi...@bu...> - 2026-08-25 16:46:36
|
VRF's have been an issue for any snmp management open or commercial since people started using them in the early 2000's with MPLS, later with firewall vendor contexts, and mostly screws over management tools where ever this is used. Most NMS's doing discovery don't expect to hit a single node pretending to be multiple nodes, almost universally they crap the bed when you try, and mostly the same situation here. Your best bet is to treat them as separate, different devices, but if I remember Netdisco will typically see enough by serial number and such to attribute them as the same device, and still try to lump them together incorrectly. Netdisco just requires some fundamental changes to allow multiple of the same devices as separate instances, and I'm not at all sure how hard that would be. I'd say ask an LLM and see these days if something that can be cleanly done. -mb On Tue, Aug 25, 2026 at 8:55 AM Beals, Damon G via netdisco-users < net...@li...> wrote: > Thanks for the response, I didn't realize this was an issue, I thought it > was just a config issue. > > I think I will try to modify the config so that only the Arista switches > will use community@VRF, and the other devices will use community. Right > now we only have one VRF to deal with, but we do plan on doing more. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > ------------------------------ > *From:* Christian Ramseyer <ram...@ne...> > *Sent:* Friday, August 21, 2026 19:02 > *To:* Beals, Damon G <db...@iu...>; net...@li... > <net...@li...> > *Subject:* Re: [Netdisco] [External] Using two or more snmp communities > for the same node? > > Hi Damon > > The mailing list is still in use but it's not so frequented anymore, so > for visibility github might be a bit better. > > Anyways I'm afraid for Arista there is currently no support to use SNMP > this way. Cisco has a similar feature where a vlan can be appended and > Netdisco is using these through special hints in the respective > snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to > find out more. > > There's also an snmp v3 variant, where the better formalized snmp v3 > context can be used in a similar way, even for VRFs > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FVendor-Tips%23vrfs-and-nxos&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421158854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S63SD8cZWiULsWHQiVY%2B%2Ftpeb5cJQLaGVcaPiwiJvJ8%3D&reserved=0 > <https://github.com/netdisco/netdisco/wiki/Vendor-Tips#vrfs-and-nxos> > > Lastly there is a third way that is used with many vendors, which is not > using snmp but SSH to run specific commands for arp and mac-address > table collection: > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Ftree%2Fmaster%2Flib%2FApp%2FNetdisco%2FSSHCollector%2FPlatform&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421186948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kjqImd0oB6oNgsHBEaY4tE4U6zUSZ464Tv2F1xcqPNk%3D&reserved=0 > <https://github.com/netdisco/netdisco/tree/master/lib/App/Netdisco/SSHCollector/Platform> > > But from quickly looking at all of these things it seems there is > nothing already working for Arista. You'd need to either experiment > yourself or get some motivated colleagues/students/LLMs to do it. If you > get it to work, pull requests for snmp-info or Netdisco are of course > highly appreciated. How to get started with hacking is in > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FDeveloping%23tldr-i-just-want-to-clone-the-repo-and-get-started&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421205401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kcy49cPzyO%2BgZcebEtH6xHfK%2Bp7JlerreinbgbkKWUw%3D&reserved=0 > <https://github.com/netdisco/netdisco/wiki/Developing#tldr-i-just-want-to-clone-the-repo-and-get-started> > > Cheers > Christian > > > > On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: > > Is this email list still active? Or should I just open a ticket on > github? > > > > Damon Beals > > Network Architect > > Indiana University > > 317.274.7946 > > > > ------------------------------------------------------------------------ > > *From:* Beals, Damon G via netdisco-users <netdisco- > > us...@li...> > > *Sent:* Tuesday, August 18, 2026 13:48 > > *To:* net...@li... <netdisco- e > > us...@li...> > > *Subject:* [External] [Netdisco] Using two or more snmp communities for > > the same node? > > This message was sent from a non-IU address. Please exercise caution > > when clicking links or opening attachments from external sources. > > > > So I just discovered our Arista switches can provide information about a > > VRF if you add the VRF to the snmp community. For example > > community@VRF. Doing test via snmpwalks, I do get the information from > > that VRF. > > > > My question is, how do I get netdisco to use both community, and > > community@VRF for the same node, or what if we have 4 or 5 VRF we need > > to collect from? From my test it looks like once netdisco finds a > > working snmp it caches that community and doesn't use others? > > > > >From the docs > > "Each is tried in turn when polling the device, and then the working > > community string will be cached in the database. > > > > Damon Beals > > Network Architect > > Indiana University > > 317.274.7946 > > > > > > _______________________________________________ > > Netdisco mailing list > > net...@li... > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco-users%2F&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421228299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ed2laTG%2FGykuO9rJvY%2BOpKCbB3%2BilSBiWGgXsHX1ZWY%3D&reserved=0 > <https://sourceforge.net/p/netdisco/mailman/netdisco-users/> > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > |
|
From: Beals, D. G <db...@iu...> - 2026-08-25 15:55:00
|
Thanks for the response, I didn't realize this was an issue, I thought it was just a config issue. I think I will try to modify the config so that only the Arista switches will use community@VRF, and the other devices will use community. Right now we only have one VRF to deal with, but we do plan on doing more. Damon Beals Network Architect Indiana University 317.274.7946 ________________________________ From: Christian Ramseyer <ram...@ne...> Sent: Friday, August 21, 2026 19:02 To: Beals, Damon G <db...@iu...>; net...@li... <net...@li...> Subject: Re: [Netdisco] [External] Using two or more snmp communities for the same node? Hi Damon The mailing list is still in use but it's not so frequented anymore, so for visibility github might be a bit better. Anyways I'm afraid for Arista there is currently no support to use SNMP this way. Cisco has a similar feature where a vlan can be appended and Netdisco is using these through special hints in the respective snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to find out more. There's also an snmp v3 variant, where the better formalized snmp v3 context can be used in a similar way, even for VRFs https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FVendor-Tips%23vrfs-and-nxos&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421158854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S63SD8cZWiULsWHQiVY%2B%2Ftpeb5cJQLaGVcaPiwiJvJ8%3D&reserved=0<https://github.com/netdisco/netdisco/wiki/Vendor-Tips#vrfs-and-nxos> Lastly there is a third way that is used with many vendors, which is not using snmp but SSH to run specific commands for arp and mac-address table collection: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Ftree%2Fmaster%2Flib%2FApp%2FNetdisco%2FSSHCollector%2FPlatform&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421186948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kjqImd0oB6oNgsHBEaY4tE4U6zUSZ464Tv2F1xcqPNk%3D&reserved=0<https://github.com/netdisco/netdisco/tree/master/lib/App/Netdisco/SSHCollector/Platform> But from quickly looking at all of these things it seems there is nothing already working for Arista. You'd need to either experiment yourself or get some motivated colleagues/students/LLMs to do it. If you get it to work, pull requests for snmp-info or Netdisco are of course highly appreciated. How to get started with hacking is in https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FDeveloping%23tldr-i-just-want-to-clone-the-repo-and-get-started&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421205401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kcy49cPzyO%2BgZcebEtH6xHfK%2Bp7JlerreinbgbkKWUw%3D&reserved=0<https://github.com/netdisco/netdisco/wiki/Developing#tldr-i-just-want-to-clone-the-repo-and-get-started> Cheers Christian On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: > Is this email list still active? Or should I just open a ticket on github? > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > ------------------------------------------------------------------------ > *From:* Beals, Damon G via netdisco-users <netdisco- > us...@li...> > *Sent:* Tuesday, August 18, 2026 13:48 > *To:* net...@li... <netdisco- e > us...@li...> > *Subject:* [External] [Netdisco] Using two or more snmp communities for > the same node? > This message was sent from a non-IU address. Please exercise caution > when clicking links or opening attachments from external sources. > > So I just discovered our Arista switches can provide information about a > VRF if you add the VRF to the snmp community. For example > community@VRF. Doing test via snmpwalks, I do get the information from > that VRF. > > My question is, how do I get netdisco to use both community, and > community@VRF for the same node, or what if we have 4 or 5 VRF we need > to collect from? From my test it looks like once netdisco finds a > working snmp it caches that community and doesn't use others? > > >From the docs > "Each is tried in turn when polling the device, and then the working > community string will be cached in the database. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco-users%2F&data=05%7C02%7Cdbeals%40iu.edu%7C58b776e3d2c34c28748208deffd83f53%7C1113be34aed14d00ab4bcdd02510be91%7C1%7C0%7C639229501421228299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ed2laTG%2FGykuO9rJvY%2BOpKCbB3%2BilSBiWGgXsHX1ZWY%3D&reserved=0<https://sourceforge.net/p/netdisco/mailman/netdisco-users/> |
|
From: Christian R. <ram...@ne...> - 2026-08-21 23:02:26
|
Hi Damon The mailing list is still in use but it's not so frequented anymore, so for visibility github might be a bit better. Anyways I'm afraid for Arista there is currently no support to use SNMP this way. Cisco has a similar feature where a vlan can be appended and Netdisco is using these through special hints in the respective snmp-info modules, look for cisco_comm_indexing/snmp_comm_reindex to find out more. There's also an snmp v3 variant, where the better formalized snmp v3 context can be used in a similar way, even for VRFs https://github.com/netdisco/netdisco/wiki/Vendor-Tips#vrfs-and-nxos Lastly there is a third way that is used with many vendors, which is not using snmp but SSH to run specific commands for arp and mac-address table collection: https://github.com/netdisco/netdisco/tree/master/lib/App/Netdisco/SSHCollector/Platform But from quickly looking at all of these things it seems there is nothing already working for Arista. You'd need to either experiment yourself or get some motivated colleagues/students/LLMs to do it. If you get it to work, pull requests for snmp-info or Netdisco are of course highly appreciated. How to get started with hacking is in https://github.com/netdisco/netdisco/wiki/Developing#tldr-i-just-want-to-clone-the-repo-and-get-started Cheers Christian On 21.08.2026 16:03, Beals, Damon G via netdisco-users wrote: > Is this email list still active? Or should I just open a ticket on github? > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > ------------------------------------------------------------------------ > *From:* Beals, Damon G via netdisco-users <netdisco- > us...@li...> > *Sent:* Tuesday, August 18, 2026 13:48 > *To:* net...@li... <netdisco- e > us...@li...> > *Subject:* [External] [Netdisco] Using two or more snmp communities for > the same node? > This message was sent from a non-IU address. Please exercise caution > when clicking links or opening attachments from external sources. > > So I just discovered our Arista switches can provide information about a > VRF if you add the VRF to the snmp community. For example > community@VRF. Doing test via snmpwalks, I do get the information from > that VRF. > > My question is, how do I get netdisco to use both community, and > community@VRF for the same node, or what if we have 4 or 5 VRF we need > to collect from? From my test it looks like once netdisco finds a > working snmp it caches that community and doesn't use others? > > >From the docs > "Each is tried in turn when polling the device, and then the working > community string will be cached in the database. > > Damon Beals > Network Architect > Indiana University > 317.274.7946 > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
|
From: Beals, D. G <db...@iu...> - 2026-08-21 20:35:18
|
Is this email list still active? Or should I just open a ticket on github? Damon Beals Network Architect Indiana University 317.274.7946 ________________________________ From: Beals, Damon G via netdisco-users <net...@li...> Sent: Tuesday, August 18, 2026 13:48 To: net...@li... <net...@li...> Subject: [External] [Netdisco] Using two or more snmp communities for the same node? This message was sent from a non-IU address. Please exercise caution when clicking links or opening attachments from external sources. So I just discovered our Arista switches can provide information about a VRF if you add the VRF to the snmp community. For example community@VRF. Doing test via snmpwalks, I do get the information from that VRF. My question is, how do I get netdisco to use both community, and community@VRF for the same node, or what if we have 4 or 5 VRF we need to collect from? From my test it looks like once netdisco finds a working snmp it caches that community and doesn't use others? >From the docs "Each is tried in turn when polling the device, and then the working community string will be cached in the database. Damon Beals Network Architect Indiana University 317.274.7946 |
|
From: Beals, D. G <db...@iu...> - 2026-08-18 20:36:31
|
So I just discovered our Arista switches can provide information about a VRF if you add the VRF to the snmp community. For example community@VRF. Doing test via snmpwalks, I do get the information from that VRF. My question is, how do I get netdisco to use both community, and community@VRF for the same node, or what if we have 4 or 5 VRF we need to collect from? From my test it looks like once netdisco finds a working snmp it caches that community and doesn't use others? >From the docs "Each is tried in turn when polling the device, and then the working community string will be cached in the database. Damon Beals Network Architect Indiana University 317.274.7946 |
|
From: Weidner,André <And...@mu...> - 2026-08-12 09:51:28
|
Hello everyone,
Current System: Netdisco 2.102.0 running on Oracle Linux 9.8
We recently installed more than 100 Lancom switches in our environment. Adding them to Netdisco worked decent through LLDP discovery. The Lancom management cloud is rather limited. Netdisco is far superior for getting an overview for the entire network.
Problems:
The device vendor is correctly recognized as "Lancom", but the model number is shown in the format "enterprises.2356.16.8.XXXX". XXXX represents the model number of the devices:
3510 GS-3510XP
6128 XS-6128QF
* The GS-3510XP is reported to be a Layer2 device but is actually a Layer3 device.
* The firmware field is not populated, but it can be read with snmpget at
* OID .1.3.6.1.2.1.47.1.1.1.1.10.1 and .1.3.6.1.2.1.47.1.1.1.1.9.1 for the 3510
* OID .1.3.6.1.2.1.32.2.1.1.1.0 and .1.3.6.1.2.1.47.1.1.1.1.10.2 for the 6128
* The 802.1x status is not collected
We have a similar problem with some HPe gear. The vendor is recognized correctly, but the model numer show "EtherSwitch.200" instead of JL686A or 1930. The 802.1x status is also not collected.
What I tried:
I searched for ways to add MIBs to Netdisco. There are mentions of a "netdisco-mibs-installer" but it is not present on my system.
I added the MIB file for the GS-3510XP from https://github.com/netdisco/netdisco-mibs/issues/238 to the netdisco-mibs/lancom folder but to no avail.
Any help would be appreciated.
Kind regards,
A. Weidner
|
|
From: Joseph B. <jh...@cl...> - 2026-08-10 17:32:46
|
Adding "macsuck_all_vlans: true" has fixed my issue without adding a noticeable amount of time to macsuck under Poller Performance. I found an old issue on github that seemed similar hinting that it's a bug with Cisco and SNMPv2 and that moving to SNMPv3 might fix it. If that does fix it, I'll report back, though it might be a few months. Thanks, Joseph B. On 7/31/26, 7:33 AM, "Christian Ramseyer" <ram...@ne... <mailto:ram...@ne...>> wrote: Hi snmp-info exposes per vlan interface information like i_vlan and i_vlan_membership. You can run netdisco-do macsuck -DIS -d <ip> to see what is called and returned. There is a config option https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_all_vlans macsuck_all_vlans Value: Boolean. Default: false. Set to macsuck all VLANs, not just the ones that are being used on ports. This is a debug option. Set this if you think that the option of not macsucking VLANs that aren’t in use on device ports is somehow interfering. I'm not sure how bad or slow globally enabling this would be and if it solves your problem. Worth a try, or to make a targeted fix you maybe can figure out where snmp-info goes wrong and patch it for the device class in question. Cheers Christian On 30.07.2026 18:18, Joseph Bernard via netdisco-users wrote: > I did a debug run of netdisco-do macsuck and found the message “not in > use by any port - skipping" on several vlans that do have devices. How > does it determine which vlans are in use? Can I override it? I have a > feeling that the mechanism isn’t taking into account the dynamic vlan > assignments we have on our Cisco switches. > > Thanks, > > Joseph B. > |
|
From: Christian R. <ram...@ne...> - 2026-07-31 11:33:48
|
Hi snmp-info exposes per vlan interface information like i_vlan and i_vlan_membership. You can run netdisco-do macsuck -DIS -d <ip> to see what is called and returned. There is a config option https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_all_vlans macsuck_all_vlans Value: Boolean. Default: false. Set to macsuck all VLANs, not just the ones that are being used on ports. This is a debug option. Set this if you think that the option of not macsucking VLANs that aren’t in use on device ports is somehow interfering. I'm not sure how bad or slow globally enabling this would be and if it solves your problem. Worth a try, or to make a targeted fix you maybe can figure out where snmp-info goes wrong and patch it for the device class in question. Cheers Christian On 30.07.2026 18:18, Joseph Bernard via netdisco-users wrote: > I did a debug run of netdisco-do macsuck and found the message “not in > use by any port - skipping" on several vlans that do have devices. How > does it determine which vlans are in use? Can I override it? I have a > feeling that the mechanism isn’t taking into account the dynamic vlan > assignments we have on our Cisco switches. > > Thanks, > > Joseph B. > |
|
From: Eric B. <eb...@wh...> - 2026-07-30 18:57:18
|
Generally I would assume that making sure your python is up to 3.10 is an exercise for the reader. I did nothing because Ubuntu's current version is 3.12 and I generally update the system regularly. I don't use python enough to remember when it upgraded; but 3.10 was quite a while ago. ** ericx@ericx-office2 ** ~ ** Thu Jul 30 08:16:48 $ python3 --version Python 3.12.3 If you're running the container version, it should have it's own python in the image: ** admin_ebates@arm-netsrv1 ** ~ ** Thu Jul 30 08:21:38 $ docker exec netdisco-backend python3 --version Python 3.12.11 On 7/30/26 07:31, Muris wrote: This email originated outside of WHOI. Please use caution if clicking on links or opening attachments. Anyone share any insight on this ? will it auto upgrade ? From: Muris <alc...@gm...><mailto:alc...@gm...> Date: Sunday, 14 June 2026 at 18:36 To: "net...@li..."<mailto:net...@li...> <net...@li...><mailto:net...@li...> Subject: Netdisco Python 3.10 dependency Hey all, I saw the new newer netdisco requires python 3.10, is there a particular procedure to get it to 3.10, or its meant to do this automatically? 2.099001 - 2026-05-27 [ENHANCEMENTS] * update Python minimum version from 3.9 to 3.10 Thanks Muris _______________________________________________ Netdisco mailing list net...@li...<mailto:net...@li...> https://sourceforge.net/p/netdisco/mailman/netdisco-users/ -- MS #46 Clark 159a |
|
From: Joseph B. <jh...@cl...> - 2026-07-30 17:50:45
|
I did a debug run of netdisco-do macsuck and found the message “not in use by any port - skipping" on several vlans that do have devices. How does it determine which vlans are in use? Can I override it? I have a feeling that the mechanism isn’t taking into account the dynamic vlan assignments we have on our Cisco switches. Thanks, Joseph B. |
|
From: Michael B. <mi...@bu...> - 2026-07-30 14:29:54
|
This is more a distribution issue with your linux than it is a netdisco issue. Your distribution has a supported range of python versions in it, and if nothing newer, you need a newer distribution update that does. I'm assuming this is a static distribution with periodic releases ala ubuntu/debian, rh/cent/fedora vs a rolling release like arch? Might need to jump to a new major version with so old a python, one reason I stopped using ubuntu vs arch. -mb On Thu, Jul 30, 2026 at 4:31 AM Muris <alc...@gm...> wrote: > Anyone share any insight on this ? will it auto upgrade ? > > > > *From: *Muris <alc...@gm...> > *Date: *Sunday, 14 June 2026 at 18:36 > *To: *"net...@li..." < > net...@li...> > *Subject: *Netdisco Python 3.10 dependency > > > > Hey all, > > > > I saw the new newer netdisco requires python 3.10, is there a particular > procedure to get it to 3.10, or its meant to do this automatically? > > > > 2.099001 - 2026-05-27 > > [ENHANCEMENTS] > > * update Python minimum version from 3.9 to 3.10 > > > > Thanks > > Muris > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > |
|
From: Muris <alc...@gm...> - 2026-07-30 11:31:34
|
Anyone share any insight on this ? will it auto upgrade ? From: Muris <alc...@gm...> Date: Sunday, 14 June 2026 at 18:36 To: "net...@li..." <net...@li...> Subject: Netdisco Python 3.10 dependency Hey all, I saw the new newer netdisco requires python 3.10, is there a particular procedure to get it to 3.10, or its meant to do this automatically? 2.099001 - 2026-05-27 [ENHANCEMENTS] * update Python minimum version from 3.9 to 3.10 Thanks Muris |
|
From: Cleveland, D. R <dc...@id...> - 2026-07-30 11:21:39
|
Hello Christian. Problem solved. Thanks for your guidance! It turns out I needed to specify the auth proto in deployment.yml, where I didn't have to before. Once I added it, the discover job went through, and the devices are on the map again. Thank you! Damian Cleveland 609.279.6265 IDA CCR-P 805 Bunn Drive Princeton, NJ 08540 ________________________________ From: Christian Ramseyer <ram...@ne...> Sent: Wednesday, July 29, 2026 8:12:43 PM To: Cleveland, Damian R; Netdisco Subject: Re: [EXT] Re: [Netdisco] SNMPv3 configured Palo Altos no longer showing up in Netdisco ok great, the try_connect stuff shows that some credentials from deployment.yml device_auth are tried but none of them work. Either you don't have the same values in there that work with the snmpwalk command line, or there is a more subtle difference caused by YAML formatting or defaults picked by one tool but not the other. You can use https://github.com/netdisco/netdisco/wiki/Environment-Variables#nd2_show_community to show the value being sent, and check https://github.com/netdisco/netdisco/wiki/Configuration#device_auth for examples with correct v3 parameters. One common scenario of "it worked once" is upgrades on the Palo side requiring stronger crypto in the SNMP config now. There is some pointers to the correct names like AES128 here: https://github.com/netdisco/netdisco/wiki/Vendor-Tips#snmpv3-on-cisco-with-non-standard-priv-algorithms Good luck On 29.07.2026 17:39, Cleveland, Damian R wrote: > Thanks for responding, Christian > > Here's what's happening: > > [netdisco@greennetadmin ~]$ netdisco-do -D discover -d 192.168.42.220 > [1710551] 2026-07-29 15:34:49 info App::Netdisco version 2.080003 loaded. > [1710551] 2026-07-29 15:34:49 info discover: [192.168.42.220] started > at Wed Jul 29 11:34:49 2026 > [1710551] 2026-07-29 15:34:49 debug discover: running with timeout 600s > [1710551] 2026-07-29 15:34:49 debug //// CHECK \\\\ phase > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Internal::BackendFQDN p1000000 > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Internal::SNMPFastDiscover > p1000000 > [1710551] 2026-07-29 15:34:49 debug running with configured SNMP timeouts > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Discover p0 > [1710551] 2026-07-29 15:34:49 debug ⬅ (done) Discover is able to run. > [1710551] 2026-07-29 15:34:49 debug //// EARLY \\\\ phase > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:34:49 debug snmp reader cache warm: [192.168.42.220] > [1710551] 2026-07-29 15:34:49 debug [192.168.42.220:161] try_connect > with v: 3, t: 0.2, r: 0, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect > with v: 2, t: 0.2, r: 0, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect > with v: 3, t: 3, r: 2, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect > with v: 2, t: 3, r: 2, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:35:17 debug [192.168.42.220:161] try_connect > with v: 1, t: 3, r: 2, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:35:44 debug ⬅ (defer) discover failed: could not > SNMP connect to 192.168.42.220 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug //// MAIN \\\\ phase > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::CanonicalIP p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Entities p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Neighbors p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Neighbors::DOCSIS > p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker PythonShim > netdisco.worklet.discover.nexthopneighbors.main.cli.juniper_junos p200 > [1710551] 2026-07-29 15:35:44 debug ⬅ (info) skip: acls restricted > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::NextHopNeighbors p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::PortPower p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::PortProperties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties::Tags p0 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties::Tags p0 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::VLANs p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Wireless p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::WithNodes p0 > [1710551] 2026-07-29 15:35:44 debug //// STORE \\\\ phase > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::NextHopNeighbors p0 > [1710551] 2026-07-29 15:35:44 debug //// LATE \\\\ phase > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Hooks p0 > [1710551] 2026-07-29 15:35:44 debug ⬅ (info) [192.168.42.220] hooks - > skipping due to incomplete job > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Snapshot p0 > [1710551] 2026-07-29 15:35:44 debug ⬅ (defer) discover failed: could not > SNMP connect to 192.168.42.220 > [1710551] 2026-07-29 15:35:44 info discover: finished at Wed Jul 29 > 11:35:44 2026 > [1710551] 2026-07-29 15:35:44 info discover: status defer: discover > failed: could not SNMP connect to 192.168.42.220 > > Again, the walk seems to work just fine. > > Thanks, > > > Damian Cleveland > > 609.279.6265 > > IDA CCR-P > > 805 Bunn Drive > > Princeton, NJ 08540 > > ------------------------------------------------------------------------ > *From:* Christian Ramseyer <ram...@ne...> > *Sent:* Wednesday, July 29, 2026 11:05:20 AM > *To:* Cleveland, Damian R; Netdisco > *Subject:* [EXT] Re: [Netdisco] SNMPv3 configured Palo Altos no longer > showing up in Netdisco > *** This email originated outside of IDA. Please verify that you > recognize the sender and know the content is safe before proceeding. *** > > > Hi Damian, I'd try running > netdisco-do -D discover -d <ip> > in a terminal to see exactly what netdisco tries to do with the device. > > Cheers > Christian > > > On 29.07.2026 13:47, Cleveland, Damian R wrote: >> Hello, >> >> >> My Palo Altos are no longer showing up in Netdisco. >> >> They are configured with SNMPv3 and worked at one point. >> >> I can still walk the device from the Netdisco instance, and I've >> restarted the services to no avail. >> >> Any advice would be appreciated. >> >> >> Thank you, >> >> >> Damian Cleveland >> >> 609.279.6265 >> >> IDA CCR-P >> >> 805 Bunn Drive >> >> Princeton, NJ 08540 >> -- Christian Ramseyer, netnea ag Network Management. Security. OpenSource. https://www.netnea.com Phone: +41 79 644 77 64 |
|
From: Christian R. <ram...@ne...> - 2026-07-30 00:12:54
|
ok great, the try_connect stuff shows that some credentials from deployment.yml device_auth are tried but none of them work. Either you don't have the same values in there that work with the snmpwalk command line, or there is a more subtle difference caused by YAML formatting or defaults picked by one tool but not the other. You can use https://github.com/netdisco/netdisco/wiki/Environment-Variables#nd2_show_community to show the value being sent, and check https://github.com/netdisco/netdisco/wiki/Configuration#device_auth for examples with correct v3 parameters. One common scenario of "it worked once" is upgrades on the Palo side requiring stronger crypto in the SNMP config now. There is some pointers to the correct names like AES128 here: https://github.com/netdisco/netdisco/wiki/Vendor-Tips#snmpv3-on-cisco-with-non-standard-priv-algorithms Good luck On 29.07.2026 17:39, Cleveland, Damian R wrote: > Thanks for responding, Christian > > Here's what's happening: > > [netdisco@greennetadmin ~]$ netdisco-do -D discover -d 192.168.42.220 > [1710551] 2026-07-29 15:34:49 info App::Netdisco version 2.080003 loaded. > [1710551] 2026-07-29 15:34:49 info discover: [192.168.42.220] started > at Wed Jul 29 11:34:49 2026 > [1710551] 2026-07-29 15:34:49 debug discover: running with timeout 600s > [1710551] 2026-07-29 15:34:49 debug //// CHECK \\\\ phase > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Internal::BackendFQDN p1000000 > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Internal::SNMPFastDiscover > p1000000 > [1710551] 2026-07-29 15:34:49 debug running with configured SNMP timeouts > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Discover p0 > [1710551] 2026-07-29 15:34:49 debug ⬅ (done) Discover is able to run. > [1710551] 2026-07-29 15:34:49 debug //// EARLY \\\\ phase > [1710551] 2026-07-29 15:34:49 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:34:49 debug snmp reader cache warm: [192.168.42.220] > [1710551] 2026-07-29 15:34:49 debug [192.168.42.220:161] try_connect > with v: 3, t: 0.2, r: 0, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect > with v: 2, t: 0.2, r: 0, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect > with v: 3, t: 3, r: 2, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect > with v: 2, t: 3, r: 2, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:35:17 debug [192.168.42.220:161] try_connect > with v: 1, t: 3, r: 2, class: SNMP::Info, comm: <hidden> > [1710551] 2026-07-29 15:35:44 debug ⬅ (defer) discover failed: could not > SNMP connect to 192.168.42.220 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 > [1710551] 2026-07-29 15:35:44 debug //// MAIN \\\\ phase > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::CanonicalIP p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Entities p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Neighbors p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Neighbors::DOCSIS > p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker PythonShim > netdisco.worklet.discover.nexthopneighbors.main.cli.juniper_junos p200 > [1710551] 2026-07-29 15:35:44 debug ⬅ (info) skip: acls restricted > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::NextHopNeighbors p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::PortPower p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::PortProperties p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties::Tags p0 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties::Tags p0 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::VLANs p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Wireless p100 > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::WithNodes p0 > [1710551] 2026-07-29 15:35:44 debug //// STORE \\\\ phase > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::NextHopNeighbors p0 > [1710551] 2026-07-29 15:35:44 debug //// LATE \\\\ phase > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Hooks p0 > [1710551] 2026-07-29 15:35:44 debug ⬅ (info) [192.168.42.220] hooks - > skipping due to incomplete job > [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Snapshot p0 > [1710551] 2026-07-29 15:35:44 debug ⬅ (defer) discover failed: could not > SNMP connect to 192.168.42.220 > [1710551] 2026-07-29 15:35:44 info discover: finished at Wed Jul 29 > 11:35:44 2026 > [1710551] 2026-07-29 15:35:44 info discover: status defer: discover > failed: could not SNMP connect to 192.168.42.220 > > Again, the walk seems to work just fine. > > Thanks, > > > Damian Cleveland > > 609.279.6265 > > IDA CCR-P > > 805 Bunn Drive > > Princeton, NJ 08540 > > ------------------------------------------------------------------------ > *From:* Christian Ramseyer <ram...@ne...> > *Sent:* Wednesday, July 29, 2026 11:05:20 AM > *To:* Cleveland, Damian R; Netdisco > *Subject:* [EXT] Re: [Netdisco] SNMPv3 configured Palo Altos no longer > showing up in Netdisco > *** This email originated outside of IDA. Please verify that you > recognize the sender and know the content is safe before proceeding. *** > > > Hi Damian, I'd try running > netdisco-do -D discover -d <ip> > in a terminal to see exactly what netdisco tries to do with the device. > > Cheers > Christian > > > On 29.07.2026 13:47, Cleveland, Damian R wrote: >> Hello, >> >> >> My Palo Altos are no longer showing up in Netdisco. >> >> They are configured with SNMPv3 and worked at one point. >> >> I can still walk the device from the Netdisco instance, and I've >> restarted the services to no avail. >> >> Any advice would be appreciated. >> >> >> Thank you, >> >> >> Damian Cleveland >> >> 609.279.6265 >> >> IDA CCR-P >> >> 805 Bunn Drive >> >> Princeton, NJ 08540 >> -- Christian Ramseyer, netnea ag Network Management. Security. OpenSource. https://www.netnea.com Phone: +41 79 644 77 64 |
|
From: Cleveland, D. R <dc...@id...> - 2026-07-29 15:39:55
|
Thanks for responding, Christian Here's what's happening: [netdisco@greennetadmin ~]$ netdisco-do -D discover -d 192.168.42.220 [1710551] 2026-07-29 15:34:49 info App::Netdisco version 2.080003 loaded. [1710551] 2026-07-29 15:34:49 info discover: [192.168.42.220] started at Wed Jul 29 11:34:49 2026 [1710551] 2026-07-29 15:34:49 debug discover: running with timeout 600s [1710551] 2026-07-29 15:34:49 debug //// CHECK \\\\ phase [1710551] 2026-07-29 15:34:49 debug ⮕ worker Internal::BackendFQDN p1000000 [1710551] 2026-07-29 15:34:49 debug ⮕ worker Internal::SNMPFastDiscover p1000000 [1710551] 2026-07-29 15:34:49 debug running with configured SNMP timeouts [1710551] 2026-07-29 15:34:49 debug ⮕ worker Discover p0 [1710551] 2026-07-29 15:34:49 debug ⬅ (done) Discover is able to run. [1710551] 2026-07-29 15:34:49 debug //// EARLY \\\\ phase [1710551] 2026-07-29 15:34:49 debug ⮕ worker Discover::Properties p100 [1710551] 2026-07-29 15:34:49 debug snmp reader cache warm: [192.168.42.220] [1710551] 2026-07-29 15:34:49 debug [192.168.42.220:161] try_connect with v: 3, t: 0.2, r: 0, class: SNMP::Info, comm: <hidden> [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect with v: 2, t: 0.2, r: 0, class: SNMP::Info, comm: <hidden> [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect with v: 3, t: 3, r: 2, class: SNMP::Info, comm: <hidden> [1710551] 2026-07-29 15:34:50 debug [192.168.42.220:161] try_connect with v: 2, t: 3, r: 2, class: SNMP::Info, comm: <hidden> [1710551] 2026-07-29 15:35:17 debug [192.168.42.220:161] try_connect with v: 1, t: 3, r: 2, class: SNMP::Info, comm: <hidden> [1710551] 2026-07-29 15:35:44 debug ⬅ (defer) discover failed: could not SNMP connect to 192.168.42.220 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties p100 [1710551] 2026-07-29 15:35:44 debug //// MAIN \\\\ phase [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::CanonicalIP p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Entities p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Neighbors p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Neighbors::DOCSIS p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker PythonShim netdisco.worklet.discover.nexthopneighbors.main.cli.juniper_junos p200 [1710551] 2026-07-29 15:35:44 debug ⬅ (info) skip: acls restricted [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::NextHopNeighbors p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::PortPower p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::PortProperties p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties::Tags p0 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Properties::Tags p0 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::VLANs p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Wireless p100 [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::WithNodes p0 [1710551] 2026-07-29 15:35:44 debug //// STORE \\\\ phase [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::NextHopNeighbors p0 [1710551] 2026-07-29 15:35:44 debug //// LATE \\\\ phase [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Hooks p0 [1710551] 2026-07-29 15:35:44 debug ⬅ (info) [192.168.42.220] hooks - skipping due to incomplete job [1710551] 2026-07-29 15:35:44 debug ⮕ worker Discover::Snapshot p0 [1710551] 2026-07-29 15:35:44 debug ⬅ (defer) discover failed: could not SNMP connect to 192.168.42.220 [1710551] 2026-07-29 15:35:44 info discover: finished at Wed Jul 29 11:35:44 2026 [1710551] 2026-07-29 15:35:44 info discover: status defer: discover failed: could not SNMP connect to 192.168.42.220 Again, the walk seems to work just fine. Thanks, Damian Cleveland 609.279.6265 IDA CCR-P 805 Bunn Drive Princeton, NJ 08540 ________________________________ From: Christian Ramseyer <ram...@ne...> Sent: Wednesday, July 29, 2026 11:05:20 AM To: Cleveland, Damian R; Netdisco Subject: [EXT] Re: [Netdisco] SNMPv3 configured Palo Altos no longer showing up in Netdisco *** This email originated outside of IDA. Please verify that you recognize the sender and know the content is safe before proceeding. *** Hi Damian, I'd try running netdisco-do -D discover -d <ip> in a terminal to see exactly what netdisco tries to do with the device. Cheers Christian On 29.07.2026 13:47, Cleveland, Damian R wrote: > Hello, > > > My Palo Altos are no longer showing up in Netdisco. > > They are configured with SNMPv3 and worked at one point. > > I can still walk the device from the Netdisco instance, and I've > restarted the services to no avail. > > Any advice would be appreciated. > > > Thank you, > > > Damian Cleveland > > 609.279.6265 > > IDA CCR-P > > 805 Bunn Drive > > Princeton, NJ 08540 > |
|
From: Christian R. <ram...@ne...> - 2026-07-29 15:21:47
|
Hi Damian, I'd try running netdisco-do -D discover -d <ip> in a terminal to see exactly what netdisco tries to do with the device. Cheers Christian On 29.07.2026 13:47, Cleveland, Damian R wrote: > Hello, > > > My Palo Altos are no longer showing up in Netdisco. > > They are configured with SNMPv3 and worked at one point. > > I can still walk the device from the Netdisco instance, and I've > restarted the services to no avail. > > Any advice would be appreciated. > > > Thank you, > > > Damian Cleveland > > 609.279.6265 > > IDA CCR-P > > 805 Bunn Drive > > Princeton, NJ 08540 > |