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
(33) |
Oct
|
Nov
|
Dec
|
From: Eric W. B. (he) <eb...@wh...> - 2024-09-13 15:17:23
|
I have a strange problem I only just noticed. I think it occurred because of a cpanm pull. I'm guessing that deployment.yml is no longer being read? As user netdisco (who has ownership of deployment.yml): netdisco@netdisco:~$ ls -la environments/ total 24 drwxrwxr-x 2 netdisco netdisco 4096 Sep 9 13:40 . drwxr-xr-x 18 netdisco netdisco 4096 Sep 9 13:59 .. -rw------- 1 netdisco netdisco 6462 Apr 19 14:50 deployment.yml -rw------- 1 netdisco netdisco 3483 Feb 3 2016 deployment.yml-bak -rw------- 1 netdisco netdisco 2256 Mar 24 2015 deployment.yml-orig netdisco@netdisco:~$ ~/bin/netdisco-do discover -d mvcovpn [544278] 2024-09-13 11:26:09 info App::Netdisco version 2.078000 loaded. [544278] 2024-09-13 11:26:09 info discover: [172.26.252.209] started at Fri Sep 13 07:26:09 2024 DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently unversioned. Please call upgrade on your schema to sync the DB. at /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121 [544278] 2024-09-13 11:26:10 info discover: finished at Fri Sep 13 07:26:10 2024 [544278] 2024-09-13 11:26:10 info discover: status error: error running job: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('dbname=netdisco','changeme',...) failed: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: Peer authentication failed for user "changeme" at /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639. at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Device.pm line 80 In general, netdisco appears to be operating normally. There are no errors in ./logs/netdisco-backend.log This failure only occurs from the command line. I found the username "changeme" in the default deployment.yml: ./perl5/lib/perl5/auto/share/dist/App-Netdisco/environments/deployment.yml: user: 'changeme' -- Clark 159a 508/289-3112 |
From: Eric W. B. (he) <eb...@wh...> - 2024-09-13 12:19:40
|
Nevermind. All set. I ran another cpanm pull and now all is well. On 9/13/24 07:42, Eric W. Bates (he) wrote: > I have a strange problem I only just noticed. I think it occurred > because of a cpanm pull. > > I'm guessing that deployment.yml is no longer being read? As user > netdisco (who has ownership of deployment.yml): > > netdisco@netdisco:~$ ls -la environments/ > total 24 > drwxrwxr-x 2 netdisco netdisco 4096 Sep 9 13:40 . > drwxr-xr-x 18 netdisco netdisco 4096 Sep 9 13:59 .. > -rw------- 1 netdisco netdisco 6462 Apr 19 14:50 deployment.yml > -rw------- 1 netdisco netdisco 3483 Feb 3 2016 deployment.yml-bak > -rw------- 1 netdisco netdisco 2256 Mar 24 2015 deployment.yml-orig > > netdisco@netdisco:~$ ~/bin/netdisco-do discover -d mvcovpn > [544278] 2024-09-13 11:26:09 info App::Netdisco version 2.078000 loaded. > [544278] 2024-09-13 11:26:09 info discover: [172.26.252.209] started at > Fri Sep 13 07:26:09 2024 > DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently > unversioned. Please call upgrade on your schema to sync the DB. at > /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121 > [544278] 2024-09-13 11:26:10 info discover: finished at Fri Sep 13 > 07:26:10 2024 > [544278] 2024-09-13 11:26:10 info discover: status error: error running > job: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: > DBI connect('dbname=netdisco','changeme',...) failed: connection to > server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: > Peer authentication failed for user "changeme" at > /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639. at > /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Device.pm line 80 > > In general, netdisco appears to be operating normally. There are no > errors in ./logs/netdisco-backend.log This failure only occurs from the > command line. > > I found the username "changeme" in the default deployment.yml: > > ./perl5/lib/perl5/auto/share/dist/App-Netdisco/environments/deployment.yml: > user: 'changeme' > |
From: Oliver G. <ol...@cp...> - 2024-09-12 10:02:48
|
Hi Muris Many thanks for the output. There's good and bad news! The implementation in Netdisco is not a small task, as SNMP::Info would need updating to load the MIB for some devices and also code to work out which devices that is done for. Then Netdisco needs a small patch to get the data, and database fields. I admit to feeling that for what is possibly quite niche, adding database fields seems a lot, plus then the user interface fields. The Netdisco side is at least copy-paste, mostly. One issue is that, in case you were not aware, there can be multiple modems per device! The data is in a table, and what you showed me is a table with one row, but it's quite feasible for a device to have multiple modems. We'd need to be able to cope with that complexity to implement the feature properly, which complicates the above, especially the Netdisco side. (as an aside, I do like that the table for the GSM module metadata is indexed on the ID of the FRU from ENTITY-MIB) On the other hand, there is actually, I think, a neat solution you can implement locally using *existing features* and deployment.yml only. Hurrah! (that's the good news bit) I just need to put some thought into the design and will write it up in the wiki, as it's quite interesting. If you are keen, you can at least open an issue on github with the feature request and copy in the content from our email thread for context. Kind regards Oliver. On Thu, 12 Sept 2024 at 07:36, Muris <alc...@gm...> wrote: > Hi Oliver , that works, can you also add the carrier type ? It is > c3gGsmNetwork > > > > It would be nice to have a report something like Reports > Device > Cisco > Cellular Routers IMEI > > > > Then it gives name of the router/ip address/carrier/imei/number. > > Maybe also something to track IMEI number & GSM network changes for a > specific device and when it was last seen/and or updated, with some > historical data > > > > ~/bin/netdisco-do show -d 10.1.1.1 -e CISCO-WAN-3G-MIB::c3gImei -D > > [22153] 2024-09-12 04:38:29 info App::Netdisco version 2.074001 loaded. > > [22153] 2024-09-12 04:38:29 info show: > [10.1.1.1]/CISCO-WAN-3G-MIB::c3gImei started at Thu Sep 12 14:08:29 2024 > > [22153] 2024-09-12 04:38:30 debug show: running with timeout 600s > > [22153] 2024-09-12 04:38:30 debug => running workers for phase: check > > [22153] 2024-09-12 04:38:30 debug -> run worker check/1000000 > "internal::backendfqdn" > > [22153] 2024-09-12 04:38:30 debug -> run worker check/1000000 > "internal::snmpfastdiscover" > > [22153] 2024-09-12 04:38:30 debug running with configured SNMP timeouts > > [22153] 2024-09-12 04:38:30 debug -> run worker check/0 "show" > > [22153] 2024-09-12 04:38:30 debug Show is able to run > > [22153] 2024-09-12 04:38:30 debug => running workers for phase: main > > [22153] 2024-09-12 04:38:30 debug -> run worker main/100 "show" > > [22153] 2024-09-12 04:38:30 debug snmp reader cache warm: [10.1.1.1] > > [22153] 2024-09-12 04:38:30 debug [10.1.1.1:161] try_connect with v: 2, > t: 0.2, r: 0, class: SNMP::Info::Layer3::CiscoSwitch, comm: <hidden> > > { > > 21 99424056879145 > > } > > [22153] 2024-09-12 04:38:32 info show: finished at Thu Sep 12 14:08:32 > 2024 > > [22153] 2024-09-12 04:38:32 info show: status done: Showed > CISCO-WAN-3G-MIB::c3gImei response from 10.1.1.1 > > > > > > ~/bin/netdisco-do show -d 10.1.1.1 -e CISCO-WAN-3G-MIB::c3gGsmNetwork -D > > [23874] 2024-09-12 04:41:30 info App::Netdisco version 2.074001 loaded. > > [23874] 2024-09-12 04:41:30 info show: > [10.1.1.1]/CISCO-WAN-3G-MIB::c3gGsmNetwork started at Thu Sep 12 14:11:30 > 2024 > > [23874] 2024-09-12 04:41:30 debug show: running with timeout 600s > > [23874] 2024-09-12 04:41:30 debug => running workers for phase: check > > [23874] 2024-09-12 04:41:30 debug -> run worker check/1000000 > "internal::backendfqdn" > > [23874] 2024-09-12 04:41:30 debug -> run worker check/1000000 > "internal::snmpfastdiscover" > > [23874] 2024-09-12 04:41:30 debug running with configured SNMP timeouts > > [23874] 2024-09-12 04:41:30 debug -> run worker check/0 "show" > > [23874] 2024-09-12 04:41:30 debug Show is able to run > > [23874] 2024-09-12 04:41:30 debug => running workers for phase: main > > [23874] 2024-09-12 04:41:30 debug -> run worker main/100 "show" > > [23874] 2024-09-12 04:41:30 debug snmp reader cache warm: [10.1.1.1] > > [23874] 2024-09-12 04:41:30 debug [10.1.1.1:161] try_connect with v: 2, > t: 0.2, r: 0, class: SNMP::Info::Layer3::CiscoSwitch, comm: <hidden> > > { > > 21 "Telstra" > > } > > [23874] 2024-09-12 04:41:32 info show: finished at Thu Sep 12 14:11:32 > 2024 > > [23874] 2024-09-12 04:41:32 info show: status done: Showed > CISCO-WAN-3G-MIB::c3gGsmNetwork response from 10.1.1.1 > > > > *From: *Oliver Gorwits <ol...@cp...> > *Date: *Wednesday 11 September 2024 at 23:58 > *To: *Muris <alc...@gm...> > *Cc: *"net...@li..." < > net...@li...> > *Subject: *Re: [Netdisco] Cisco IMEI tracker report for cellular services > > > > Hi Muris! > > > > I think this may be possible but can you send the output of this command, > please (to me direct by email is fine, if you don't wish to share widely): > > > > ~/bin/netdisco-do show -d x.x.x.x -e CISCO-WAN-3G-MIB::c3gImei -D > > > > regards, > > oliver. > > > > On Wed, 11 Sept 2024 at 07:35, Muris <alc...@gm...> wrote: > > Hi, > > > > I was wondering is it possible to add an extra field in netdisco to > collect Cisco IMEI numbers for tracking cellular services? > > > > The SNMP Oid for Cisco IMEI is .1.3.6.1.4.1.9.9.661.1.3.1.1.2 > > > > This way a report can be made with hostname of the router and attached IMEI > > > > I just thought this would be useful for tracking hundreds of routers on > cellular services and if they have been seen online/or if it matches with > the carrier etc > > > > Muris > > > > > > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > > |
From: Muris <alc...@gm...> - 2024-09-12 04:53:01
|
Hi Oliver , that works, can you also add the carrier type ? It is c3gGsmNetwork It would be nice to have a report something like Reports > Device > Cisco Cellular Routers IMEI Then it gives name of the router/ip address/carrier/imei/number. Maybe also something to track IMEI number & GSM network changes for a specific device and when it was last seen/and or updated, with some historical data ~/bin/netdisco-do show -d 10.1.1.1 -e CISCO-WAN-3G-MIB::c3gImei -D [22153] 2024-09-12 04:38:29 info App::Netdisco version 2.074001 loaded. [22153] 2024-09-12 04:38:29 info show: [10.1.1.1]/CISCO-WAN-3G-MIB::c3gImei started at Thu Sep 12 14:08:29 2024 [22153] 2024-09-12 04:38:30 debug show: running with timeout 600s [22153] 2024-09-12 04:38:30 debug => running workers for phase: check [22153] 2024-09-12 04:38:30 debug -> run worker check/1000000 "internal::backendfqdn" [22153] 2024-09-12 04:38:30 debug -> run worker check/1000000 "internal::snmpfastdiscover" [22153] 2024-09-12 04:38:30 debug running with configured SNMP timeouts [22153] 2024-09-12 04:38:30 debug -> run worker check/0 "show" [22153] 2024-09-12 04:38:30 debug Show is able to run [22153] 2024-09-12 04:38:30 debug => running workers for phase: main [22153] 2024-09-12 04:38:30 debug -> run worker main/100 "show" [22153] 2024-09-12 04:38:30 debug snmp reader cache warm: [10.1.1.1] [22153] 2024-09-12 04:38:30 debug [10.1.1.1:161] try_connect with v: 2, t: 0.2, r: 0, class: SNMP::Info::Layer3::CiscoSwitch, comm: <hidden> { 21 99424056879145 } [22153] 2024-09-12 04:38:32 info show: finished at Thu Sep 12 14:08:32 2024 [22153] 2024-09-12 04:38:32 info show: status done: Showed CISCO-WAN-3G-MIB::c3gImei response from 10.1.1.1 ~/bin/netdisco-do show -d 10.1.1.1 -e CISCO-WAN-3G-MIB::c3gGsmNetwork -D [23874] 2024-09-12 04:41:30 info App::Netdisco version 2.074001 loaded. [23874] 2024-09-12 04:41:30 info show: [10.1.1.1]/CISCO-WAN-3G-MIB::c3gGsmNetwork started at Thu Sep 12 14:11:30 2024 [23874] 2024-09-12 04:41:30 debug show: running with timeout 600s [23874] 2024-09-12 04:41:30 debug => running workers for phase: check [23874] 2024-09-12 04:41:30 debug -> run worker check/1000000 "internal::backendfqdn" [23874] 2024-09-12 04:41:30 debug -> run worker check/1000000 "internal::snmpfastdiscover" [23874] 2024-09-12 04:41:30 debug running with configured SNMP timeouts [23874] 2024-09-12 04:41:30 debug -> run worker check/0 "show" [23874] 2024-09-12 04:41:30 debug Show is able to run [23874] 2024-09-12 04:41:30 debug => running workers for phase: main [23874] 2024-09-12 04:41:30 debug -> run worker main/100 "show" [23874] 2024-09-12 04:41:30 debug snmp reader cache warm: [10.1.1.1] [23874] 2024-09-12 04:41:30 debug [10.1.1.1:161] try_connect with v: 2, t: 0.2, r: 0, class: SNMP::Info::Layer3::CiscoSwitch, comm: <hidden> { 21 "Telstra" } [23874] 2024-09-12 04:41:32 info show: finished at Thu Sep 12 14:11:32 2024 [23874] 2024-09-12 04:41:32 info show: status done: Showed CISCO-WAN-3G-MIB::c3gGsmNetwork response from 10.1.1.1 From: Oliver Gorwits <ol...@cp...> Date: Wednesday 11 September 2024 at 23:58 To: Muris <alc...@gm...> Cc: "net...@li..." <net...@li...> Subject: Re: [Netdisco] Cisco IMEI tracker report for cellular services Hi Muris! I think this may be possible but can you send the output of this command, please (to me direct by email is fine, if you don't wish to share widely): ~/bin/netdisco-do show -d x.x.x.x -e CISCO-WAN-3G-MIB::c3gImei -D regards, oliver. On Wed, 11 Sept 2024 at 07:35, Muris <alc...@gm...> wrote: Hi, I was wondering is it possible to add an extra field in netdisco to collect Cisco IMEI numbers for tracking cellular services? The SNMP Oid for Cisco IMEI is .1.3.6.1.4.1.9.9.661.1.3.1.1.2 This way a report can be made with hostname of the router and attached IMEI I just thought this would be useful for tracking hundreds of routers on cellular services and if they have been seen online/or if it matches with the carrier etc Muris _______________________________________________ Netdisco mailing list net...@li... https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
From: Oliver G. <ol...@cp...> - 2024-09-11 14:28:34
|
Hi Muris! I think this may be possible but can you send the output of this command, please (to me direct by email is fine, if you don't wish to share widely): ~/bin/netdisco-do show -d x.x.x.x -e CISCO-WAN-3G-MIB::c3gImei -D regards, oliver. On Wed, 11 Sept 2024 at 07:35, Muris <alc...@gm...> wrote: > Hi, > > > > I was wondering is it possible to add an extra field in netdisco to > collect Cisco IMEI numbers for tracking cellular services? > > > > The SNMP Oid for Cisco IMEI is .1.3.6.1.4.1.9.9.661.1.3.1.1.2 > > > > This way a report can be made with hostname of the router and attached IMEI > > > > I just thought this would be useful for tracking hundreds of routers on > cellular services and if they have been seen online/or if it matches with > the carrier etc > > > > Muris > > > > > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > |
From: Muris <alc...@gm...> - 2024-09-11 06:04:05
|
Hi, I was wondering is it possible to add an extra field in netdisco to collect Cisco IMEI numbers for tracking cellular services? The SNMP Oid for Cisco IMEI is .1.3.6.1.4.1.9.9.661.1.3.1.1.2 This way a report can be made with hostname of the router and attached IMEI I just thought this would be useful for tracking hundreds of routers on cellular services and if they have been seen online/or if it matches with the carrier etc Muris |
From: Oliver G. <ol...@cp...> - 2024-09-04 18:16:26
|
Many thanks! https://github.com/netdisco/netdisco/wiki/Troubleshooting#cant-connect-to-tcp-port-5000-on On Tue, 3 Sept 2024 at 13:35, Sven Duscha <sve...@tu...> wrote: > Hi Oliver, > > On 30.08.24 10:45, Oliver Gorwits wrote: > > No, I think it unlikely that the IPV default changed; it's been the same > since 2012. The IPV variable comes from the Net::Server package (socket > handling) which is in turn used by the Starman package (web server) which > is in turn used by Netdisco. > > My best guess is that Net::Server, when it checks for protocol support in > the operating system, is still getting the idea that IPv6 is > enabled/available. Something might have changed in the OS upgrade or > reinstallation of Netdisco to bring a newer library with different > behaviour, or there's another setting to set in Debian. I wouldn't know. > > > I see. I would have to check, if I can dig in a Debian 10 version and > compare it. I'd have to fire up a clone of my netdisco-VM booting the > backed up disk image. But I am not sure, if I have to the time for that. > > And I am not so familiar with Perl packages interna. > > > Perhaps ask Debian support or open a ticket against Net::Server? > Unfortunately, the Net::Server code isn't easy to follow, and I don't have > a reproducing system on which to investigate myself, but it's _probably_ > this bit: > https://metacpan.org/dist/Net-Server/source/lib/Net/Server/Proto.pm#L107, > in case anyone with a system with the issue wants to have a dig around. > > > Thank you for the hint. > > > Would you be willing/able to add a section to this wiki page with the hint > for others? https://github.com/netdisco/netdisco/wiki/Troubleshooting > > > This would be my suggestion for the troubleshooting wiki page: > > > When having updated from Debian 10 (Buster) to Debian (Bullseye), in order > to get Python3 version 3.9.2, because a minimum version of Python3.9 is > required for netdisco version 2.078000, there is a problem with binding the > local 5000 port to the server's IP address, if you are using an IPv4 > address. > > This can be seen in the netdisco logs, ~/logs/netdisco-web.log, where > netdisco tries to bind the local TCP port 5000 to an unset IPv6 address: > > 2024/08/29-14:55:55 Starman::Server (type Net::Server::PreFork) starting! pid(3862)Resolved [*]:5000 to [::]:5000, IPv6Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6Binding to TCP port 5000 on host :: with IPv62024/08/29-14:55:55 Can't connect to TCP port 5000 on :: [Invalid argument] at line 66 in file /home/netdisco/perl5/lib/perl5/Net/Server/Proto/TCP.pm > > > This can be solved by setting the environment variable IPV to 4, before > starting the netdisco web-frontend: > > $ export IPV=4 > $ /home/netdisco/bin/netdisco-web start > > The content of IPV can be checked by: > $ printenv | grep IPV > > It is advisable to set the IPV environment variable in your netdisco > user's .bashrc source script. > > > > > Best wishes, > > Sven > > > -- > Sven Duscha > Deutsches Herzzentrum München > TUM Universitätsklinikum > Lazarettstraße 36 > 80636 München > +49 89 1218 2602 > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
From: Sven D. <sve...@tu...> - 2024-09-03 10:46:13
|
Hi Oliver, On 30.08.24 10:45, Oliver Gorwits wrote: > No, I think it unlikely that the IPV default changed; it's been the > same since 2012. The IPV variable comes from the Net::Server package > (socket handling) which is in turn used by the Starman package (web > server) which is in turn used by Netdisco. > > My best guess is that Net::Server, when it checks for protocol support > in the operating system, is still getting the idea that IPv6 is > enabled/available. Something might have changed in the OS upgrade or > reinstallation of Netdisco to bring a newer library with different > behaviour, or there's another setting to set in Debian. I wouldn't know. I see. I would have to check, if I can dig in a Debian 10 version and compare it. I'd have to fire up a clone of my netdisco-VM booting the backed up disk image. But I am not sure, if I have to the time for that. And I am not so familiar with Perl packages interna. > Perhaps ask Debian support or open a ticket against Net::Server? > Unfortunately, the Net::Server code isn't easy to follow, and I don't > have a reproducing system on which to investigate myself, but it's > _probably_ this bit: > https://metacpan.org/dist/Net-Server/source/lib/Net/Server/Proto.pm#L107, > in case anyone with a system with the issue wants to have a dig around. Thank you for the hint. > Would you be willing/able to add a section to this wiki page with the > hint for others? https://github.com/netdisco/netdisco/wiki/Troubleshooting This would be my suggestion for the troubleshooting wiki page: When having updated from Debian 10 (Buster) to Debian (Bullseye), in order to get Python3 version 3.9.2, because a minimum version of Python3.9 is required for netdisco version 2.078000, there is a problem with binding the local 5000 port to the server's IP address, if you are using an IPv4 address. This can be seen in the netdisco logs, ~/logs/netdisco-web.log, where netdisco tries to bind the local TCP port 5000 to an unset IPv6 address: |2024/08/29-14:55:55 Starman::Server (type Net::Server::PreFork) starting! pid(3862) Resolved [*]:5000 to [::]:5000, IPv6 Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6 Binding to TCP port 5000 on host :: with IPv6 2024/08/29-14:55:55 Can't connect to TCP port 5000 on :: [Invalid argument] at line 66 in file /home/netdisco/perl5/lib/perl5/Net/Server/Proto/TCP.pm| This can be solved by setting the environment variable IPV to 4, before starting the netdisco web-frontend: $ export IPV=4 $ /home/netdisco/bin/netdisco-web start The content of IPV can be checked by: $ printenv | grep IPV It is advisable to set the IPV environment variable in your netdisco user's .bashrc source script. Best wishes, Sven -- Sven Duscha Deutsches Herzzentrum München TUM Universitätsklinikum Lazarettstraße 36 80636 München +49 89 1218 2602 |
From: Oliver G. <ol...@cp...> - 2024-08-30 08:45:58
|
Hi Sven, No, I think it unlikely that the IPV default changed; it's been the same since 2012. The IPV variable comes from the Net::Server package (socket handling) which is in turn used by the Starman package (web server) which is in turn used by Netdisco. My best guess is that Net::Server, when it checks for protocol support in the operating system, is still getting the idea that IPv6 is enabled/available. Something might have changed in the OS upgrade or reinstallation of Netdisco to bring a newer library with different behaviour, or there's another setting to set in Debian. I wouldn't know. Perhaps ask Debian support or open a ticket against Net::Server? Unfortunately, the Net::Server code isn't easy to follow, and I don't have a reproducing system on which to investigate myself, but it's _probably_ this bit: https://metacpan.org/dist/Net-Server/source/lib/Net/Server/Proto.pm#L107, in case anyone with a system with the issue wants to have a dig around. Would you be willing/able to add a section to this wiki page with the hint for others? https://github.com/netdisco/netdisco/wiki/Troubleshooting Kind regards Oliver. On Thu, 29 Aug 2024 at 23:35, Sven Duscha <sve...@tu...> wrote: > Hi Charles, > > On 29.08.24 17:57, Charlie Butera wrote: > > > > Try setting the Environment Variables IPV to 4, this fixed it for me. > > > > https://github.com/netdisco/netdisco/wiki/Environment-Variables#ipv > > > > This is what the correctly set env variable should look like > > ~ $ printenv | grep IPV > > IPV=4 > > > Thank you for the quick response. That did the job for me, too. > > So, they changed the default value of the IPV environment value from the > previous version? > > > Best regards, > > Sven > > > -- > Sven Duscha > Deutsches Herzzentrum München > TUM Universitätsklinikum > Lazarettstraße 36 > 80636 München > +49 89 1218 2602 > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
From: Sven D. <sve...@tu...> - 2024-08-29 21:20:19
|
Hi Charles, On 29.08.24 17:57, Charlie Butera wrote: > > Try setting the Environment Variables IPV to 4, this fixed it for me. > > https://github.com/netdisco/netdisco/wiki/Environment-Variables#ipv > > This is what the correctly set env variable should look like > ~ $ printenv | grep IPV > IPV=4 Thank you for the quick response. That did the job for me, too. So, they changed the default value of the IPV environment value from the previous version? Best regards, Sven -- Sven Duscha Deutsches Herzzentrum München TUM Universitätsklinikum Lazarettstraße 36 80636 München +49 89 1218 2602 |
From: Charlie B. <cb...@sq...> - 2024-08-29 16:49:57
|
Hey Sven, Try setting the Environment Variables IPV to 4, this fixed it for me. https://github.com/netdisco/netdisco/wiki/Environment-Variables#ipv This is what the correctly set env variable should look like ~ $ printenv | grep IPV IPV=4 *Charles Butera* *Network Engineer* cb...@sq... <kk...@sq...> Squarespace Squarespace.com On Thu, Aug 29, 2024 at 9:18 AM Sven Duscha <sve...@tu...> wrote: > Hi, > > I upgraded my netdisco installation to Debian11 to get python3.9 to solve > the Alien::Poetry issue. I also needed to install python3-distutils to make > it work. > > I could then upgrade from netdisco > > netdisco@netdisco:~/bin$ grep VERSION > ~netdisco/perl5/lib/perl5/App/Netdisco.pm > our $VERSION = '2.076004'; > > to > > netdisco@netdisco:/etc/apache2/sites-enabled$ grep VERSION > ~netdisco/perl5/lib/perl5/App/Netdisco.pm > our $VERSION = '2.078000'; > > > I did the deploy again and could start the backend and web-frontend which > claim to be running, but I can not connect to the webui. Apache says it can > not redirect to port 5000 and nmap -Pn localhost shows there is no service > running at 5000. > > So I looked in the log in ~/logs/netdisco-web.log and saw that apparently > netdisco-web tries to bind to a IPv6 address? > > > 2024/08/29-14:55:55 Starman::Server (type Net::Server::PreFork) starting! > pid(3862) > Resolved [*]:5000 to [::]:5000, IPv6 > Not including resolved host [0.0.0.0] IPv4 because it will be handled by > [::] IPv6 > Binding to TCP port 5000 on host :: with IPv6 > 2024/08/29-14:55:55 Can't connect to TCP port 5000 on :: [Invalid argument] > at line 66 in file /home/netdisco/perl5/lib/perl5/Net/Server/Proto/TCP.pm > 2024/08/29-14:55:55 Received QUIT. Running a graceful shutdown > 2024/08/29-14:55:55 Worker processes cleaned up > 2024/08/29-14:55:55 Server closing! > > > I have no IPv6 address configured, we are still running all on IPv4. I > checked /etc/sysctl.conf to see, if the Debian upgrade had turned on IPv6, > but there it is disabled: > > > net.ipv6.conf.all.disable_ipv6 = 1 > net.ipv6.conf.default.disable_ipv6 = 1 > net.ipv6.conf.lo.disable_ipv6 = 1 > > > How can I fix this error in Netdisco? > > > Best regards, > > Sven Duscha > > > -- > Sven Duscha > Deutsches Herzzentrum München > TUM Universitätsklinikum > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
From: Oliver G. <ol...@cp...> - 2024-08-29 15:16:58
|
whoops! thanks, I'll update the docs On Thu, 29 Aug 2024 at 03:35, Muris <alc...@gm...> wrote: > Great, I see it now, but one thing I picked up on in this > > > > https://metacpan.org/pod/SNMP::Info::Layer3::SilverPeak > > > > *Required MIBs* > > *STEELHEAD-MIB* > > > > I don’t think that’s meant to read STEELHEAD-MIB? > > > > > > *From: *Oliver Gorwits <ol...@cp...> > *Date: *Wednesday 28 August 2024 at 20:10 > *To: *Muris <alc...@gm...> > *Cc: *<net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Yep! hopefully very soon. The tests are passing, now. > > > > On Wed, 28 Aug 2024 at 11:35, Muris <alc...@gm...> wrote: > > Thanks oliver, but to make those mibs work it really needs the silverpeak > snmp > > Info module will you release that also? > > > > I want to update to latest netdisco but waiting when you update snmp info, > otherwise i have to hack the files. > > > > > > On 28 Aug 2024, at 16:24, Oliver Gorwits <ol...@cp...> wrote: > > > > Hi Muris, thanks for your patience, I've added the updated MIBs to the > repo (and will release soon, maybe today) > > > > On Mon, 22 Jul 2024 at 17:35, Muris <alc...@gm...> wrote: > > Hey Oliver, I just wanted to let you know I got the integration working > with Silverpeak and the code for it, its on the github page. > > > > Are you able to integrate this in the next update of netdisco and with > updated version 9.5 of the mibs? > > > > https://github.com/user-attachments/files/16327192/mibs-9.5.zip > > > > Many thanks ☺ > > > > Muris > > > > *From: *Muris <alc...@gm...> > *Date: *Monday 22 July 2024 at 12:08 > *To: *Oliver Gorwits <ol...@cp...>, < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hey, just to let you know I have been working on writing the SNMP info for > silverpeak integration, but I feel im almost there but I feel I am missing > something for netdisco to pick it up fully. > > > > Ive put up my code and testing on > https://github.com/netdisco/snmp-info/issues/524 > > > > I feel I am just missing a bit to get it working and picked up into > netdisco, feel free to review the code. > > > > Muris > > > > *From: *Muris <alc...@gm...> > *Date: *Wednesday 21 February 2024 at 17:32 > *To: *Oliver Gorwits <ol...@cp...>, < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hey Oliver, I also just remembered about this one, I know you added the > Aruba/Silverpeak Mibs for it, but it still says “unknown enterprises” > > > > Example below screenshot – is there a way to troubleshoot this why it’s > not using those additional Mibs? > > > > Just would like these devices to be classified properly for vendor/model > as it doesn’t seem to reference still anything from the Mibs. Im really > keen to get it showing correctly like all other devices. > > > > <image001.jpg> > > > > *From: *Muris <alc...@gm...> > *Date: *Tuesday, 29 August 2023 at 17:37 > *To: *Oliver Gorwits <ol...@cp...>, < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hi Oliver, thanks for adding the MIBS support. > > > > I updated to the latest netdisco with the mibs, but still it cant classify > the silverpeak devices, it still comes up as “unknown enterprises” for many > of them. > > > > Is there some troubleshooting I can execute on command to see whats going > on and if its mapping it to mibs or something? > > > > Thanks > > Muris > > > > *From: *Oliver Gorwits <ol...@cp...> > *Date: *Tuesday, 27 June 2023 at 17:22 > *To: *Muris <alc...@gm...>, <net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hi Muris, sure I will take a look at the ticket, many thanks, > > Oliver. > > > > On Thu, 22 Jun 2023 at 21:18, Muris <alc...@gm...> wrote: > > Hey oliver was also just going to ask would it please be possible if you > could add these to the mibs dir when you have a moment ? > > Have uploaded the zip a little while ago in that issues URL > > > Thanks in advance > > > > On 17 May 2023, at 22:00, Muris <alc...@gm...> wrote: > > > > Hi Oliver, just wanted to ask if you would be able to integrate these > Aruba/Silverpeak MIBS into netdisco, I have attached them a few months ago. > > > > We have number of these devices and having these mibs working would be > great, right now majority report as “unknown enterprises” etc > > > > *From: *Muris <alc...@gm...> > *Date: *Friday, 10 March 2023 at 22:00 > *To: *Oliver Gorwits <ol...@cp...> > *Cc: *"net...@li..." < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Thanks Oliver, have done and put it there ☺ > > > > *From: *Oliver Gorwits <ol...@cp...> > *Date: *Friday, 10 March 2023 at 21:33 > *To: *Muris <alc...@gm...> > *Cc: *"net...@li..." < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hi Muris > > > > Sure, please would you kindly open a ticket here on the netdisco-mibs > repository: https://github.com/netdisco/netdisco-mibs/issues > > > > Even better, if you can download the MIBs and attach them, please, because > Netdisco devs do not have a contract with Aruba to do that. > > > > Kind regards > > Oliver. > > > > On Fri, 10 Mar 2023 at 10:19, Muris <alc...@gm...> wrote: > > Hey guys, I was wondering if someone would be able to add the following > Aruba SDWAN/Silverpeak mibs into the base netdisco? > > > > https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip > > > > > > Originally from this link > > https://www.arubanetworks.com/techdocs/sdwan/mibs/ > > > > Thanks > > Muris > > _______________________________________________ > 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/ > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > |
From: Sven D. <sve...@tu...> - 2024-08-29 13:17:57
|
Hi, I upgraded my netdisco installation to Debian11 to get python3.9 to solve the Alien::Poetry issue. I also needed to install python3-distutils to make it work. I could then upgrade from netdisco netdisco@netdisco:~/bin$ |grep VERSION ~netdisco/perl5/lib/perl5/App/Netdisco.pm| our $VERSION = '2.076004'; to netdisco@netdisco:/etc/apache2/sites-enabled$ grep VERSION ~netdisco/perl5/lib/perl5/App/Netdisco.pm our $VERSION = '2.078000'; I did the deploy again and could start the backend and web-frontend which claim to be running, but I can not connect to the webui. Apache says it can not redirect to port 5000 and nmap -Pn localhost shows there is no service running at 5000. So I looked in the log in ~/logs/netdisco-web.log and saw that apparently netdisco-web tries to bind to a IPv6 address? 2024/08/29-14:55:55 Starman::Server (type Net::Server::PreFork) starting! pid(3862) Resolved [*]:5000 to [::]:5000, IPv6 Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6 Binding to TCP port 5000 on host :: with IPv6 2024/08/29-14:55:55 Can't connect to TCP port 5000 on :: [Invalid argument] at line 66 in file /home/netdisco/perl5/lib/perl5/Net/Server/Proto/TCP.pm 2024/08/29-14:55:55 Received QUIT. Running a graceful shutdown 2024/08/29-14:55:55 Worker processes cleaned up 2024/08/29-14:55:55 Server closing! I have no IPv6 address configured, we are still running all on IPv4. I checked /etc/sysctl.conf to see, if the Debian upgrade had turned on IPv6, but there it is disabled: net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 How can I fix this error in Netdisco? Best regards, Sven Duscha -- Sven Duscha Deutsches Herzzentrum München TUM Universitätsklinikum |
From: Muris <alc...@gm...> - 2024-08-29 00:51:34
|
Great, I see it now, but one thing I picked up on in this https://metacpan.org/pod/SNMP::Info::Layer3::SilverPeak Required MIBs STEELHEAD-MIB I don’t think that’s meant to read STEELHEAD-MIB? From: Oliver Gorwits <ol...@cp...> Date: Wednesday 28 August 2024 at 20:10 To: Muris <alc...@gm...> Cc: <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Yep! hopefully very soon. The tests are passing, now. On Wed, 28 Aug 2024 at 11:35, Muris <alc...@gm...> wrote: Thanks oliver, but to make those mibs work it really needs the silverpeak snmp Info module will you release that also? I want to update to latest netdisco but waiting when you update snmp info, otherwise i have to hack the files. On 28 Aug 2024, at 16:24, Oliver Gorwits <ol...@cp...> wrote: Hi Muris, thanks for your patience, I've added the updated MIBs to the repo (and will release soon, maybe today) On Mon, 22 Jul 2024 at 17:35, Muris <alc...@gm...> wrote: Hey Oliver, I just wanted to let you know I got the integration working with Silverpeak and the code for it, its on the github page. Are you able to integrate this in the next update of netdisco and with updated version 9.5 of the mibs? https://github.com/user-attachments/files/16327192/mibs-9.5.zip Many thanks ☺ Muris From: Muris <alc...@gm...> Date: Monday 22 July 2024 at 12:08 To: Oliver Gorwits <ol...@cp...>, <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Hey, just to let you know I have been working on writing the SNMP info for silverpeak integration, but I feel im almost there but I feel I am missing something for netdisco to pick it up fully. Ive put up my code and testing on https://github.com/netdisco/snmp-info/issues/524 I feel I am just missing a bit to get it working and picked up into netdisco, feel free to review the code. Muris From: Muris <alc...@gm...> Date: Wednesday 21 February 2024 at 17:32 To: Oliver Gorwits <ol...@cp...>, <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Hey Oliver, I also just remembered about this one, I know you added the Aruba/Silverpeak Mibs for it, but it still says “unknown enterprises” Example below screenshot – is there a way to troubleshoot this why it’s not using those additional Mibs? Just would like these devices to be classified properly for vendor/model as it doesn’t seem to reference still anything from the Mibs. Im really keen to get it showing correctly like all other devices. <image001.jpg> From: Muris <alc...@gm...> Date: Tuesday, 29 August 2023 at 17:37 To: Oliver Gorwits <ol...@cp...>, <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Hi Oliver, thanks for adding the MIBS support. I updated to the latest netdisco with the mibs, but still it cant classify the silverpeak devices, it still comes up as “unknown enterprises” for many of them. Is there some troubleshooting I can execute on command to see whats going on and if its mapping it to mibs or something? Thanks Muris From: Oliver Gorwits <ol...@cp...> Date: Tuesday, 27 June 2023 at 17:22 To: Muris <alc...@gm...>, <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Hi Muris, sure I will take a look at the ticket, many thanks, Oliver. On Thu, 22 Jun 2023 at 21:18, Muris <alc...@gm...> wrote: Hey oliver was also just going to ask would it please be possible if you could add these to the mibs dir when you have a moment ? Have uploaded the zip a little while ago in that issues URL Thanks in advance On 17 May 2023, at 22:00, Muris <alc...@gm...> wrote: Hi Oliver, just wanted to ask if you would be able to integrate these Aruba/Silverpeak MIBS into netdisco, I have attached them a few months ago. We have number of these devices and having these mibs working would be great, right now majority report as “unknown enterprises” etc From: Muris <alc...@gm...> Date: Friday, 10 March 2023 at 22:00 To: Oliver Gorwits <ol...@cp...> Cc: "net...@li..." <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Thanks Oliver, have done and put it there ☺ From: Oliver Gorwits <ol...@cp...> Date: Friday, 10 March 2023 at 21:33 To: Muris <alc...@gm...> Cc: "net...@li..." <net...@li...> Subject: Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco Hi Muris Sure, please would you kindly open a ticket here on the netdisco-mibs repository: https://github.com/netdisco/netdisco-mibs/issues Even better, if you can download the MIBs and attach them, please, because Netdisco devs do not have a contract with Aruba to do that. Kind regards Oliver. On Fri, 10 Mar 2023 at 10:19, Muris <alc...@gm...> wrote: Hey guys, I was wondering if someone would be able to add the following Aruba SDWAN/Silverpeak mibs into the base netdisco? https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip Originally from this link https://www.arubanetworks.com/techdocs/sdwan/mibs/ Thanks Muris _______________________________________________ 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: Oliver G. <ol...@cp...> - 2024-08-28 17:09:58
|
Thanks Joseph, good to get some feedback on use in the wild. Sorry to hear the update was a bit of a headache. I might look at "uv" instead of "poetry" which can (apparently) pull in its own Python if needed. Not sure pulling such binaries to the target is a great idea though. On the other hand, Python 3.9 (which is the dependency specified by Netdisco, I believe) is already quite old and any older than that are not-supported, or on a not-supported OS? It's a bit like PostgreSQL features... sooner or later we need a newer version. I'll make it more clear in the release documentation about the version requirement! regards Oliver. On Wed, 28 Aug 2024 at 17:35, Joseph Bernard <jh...@cl...> wrote: > Just an FYI for anyone running Netdisco on a system with Python 3.6, it > won’t install the latest versions. You need Python 3.8 or higher to > install the new dependency Python Poetry. While you could technically > install an older version of Poetry, I would be worried if things would even > work right with a version from 2 years ago. > > > > Thanks, > > Joseph B. > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > |
From: Joseph B. <jh...@cl...> - 2024-08-28 16:15:47
|
Just an FYI for anyone running Netdisco on a system with Python 3.6, it won’t install the latest versions. You need Python 3.8 or higher to install the new dependency Python Poetry. While you could technically install an older version of Poetry, I would be worried if things would even work right with a version from 2 years ago. Thanks, Joseph B. |
From: Oliver G. <ol...@cp...> - 2024-08-28 10:40:47
|
Yep! hopefully very soon. The tests are passing, now. On Wed, 28 Aug 2024 at 11:35, Muris <alc...@gm...> wrote: > Thanks oliver, but to make those mibs work it really needs the silverpeak > snmp > Info module will you release that also? > > I want to update to latest netdisco but waiting when you update snmp info, > otherwise i have to hack the files. > > > On 28 Aug 2024, at 16:24, Oliver Gorwits <ol...@cp...> wrote: > > > Hi Muris, thanks for your patience, I've added the updated MIBs to the > repo (and will release soon, maybe today) > > On Mon, 22 Jul 2024 at 17:35, Muris <alc...@gm...> wrote: > >> Hey Oliver, I just wanted to let you know I got the integration working >> with Silverpeak and the code for it, its on the github page. >> >> >> >> Are you able to integrate this in the next update of netdisco and with >> updated version 9.5 of the mibs? >> >> >> >> https://github.com/user-attachments/files/16327192/mibs-9.5.zip >> >> >> >> Many thanks ☺ >> >> >> >> Muris >> >> >> >> *From: *Muris <alc...@gm...> >> *Date: *Monday 22 July 2024 at 12:08 >> *To: *Oliver Gorwits <ol...@cp...>, < >> net...@li...> >> *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into >> netdisco >> >> >> >> Hey, just to let you know I have been working on writing the SNMP info >> for silverpeak integration, but I feel im almost there but I feel I am >> missing something for netdisco to pick it up fully. >> >> >> >> Ive put up my code and testing on >> https://github.com/netdisco/snmp-info/issues/524 >> >> >> >> I feel I am just missing a bit to get it working and picked up into >> netdisco, feel free to review the code. >> >> >> >> Muris >> >> >> >> *From: *Muris <alc...@gm...> >> *Date: *Wednesday 21 February 2024 at 17:32 >> *To: *Oliver Gorwits <ol...@cp...>, < >> net...@li...> >> *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into >> netdisco >> >> >> >> Hey Oliver, I also just remembered about this one, I know you added the >> Aruba/Silverpeak Mibs for it, but it still says “unknown enterprises” >> >> >> >> Example below screenshot – is there a way to troubleshoot this why it’s >> not using those additional Mibs? >> >> >> >> Just would like these devices to be classified properly for vendor/model >> as it doesn’t seem to reference still anything from the Mibs. Im really >> keen to get it showing correctly like all other devices. >> >> >> >> <image001.jpg> >> >> >> >> *From: *Muris <alc...@gm...> >> *Date: *Tuesday, 29 August 2023 at 17:37 >> *To: *Oliver Gorwits <ol...@cp...>, < >> net...@li...> >> *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into >> netdisco >> >> >> >> Hi Oliver, thanks for adding the MIBS support. >> >> >> >> I updated to the latest netdisco with the mibs, but still it cant >> classify the silverpeak devices, it still comes up as “unknown enterprises” >> for many of them. >> >> >> >> Is there some troubleshooting I can execute on command to see whats going >> on and if its mapping it to mibs or something? >> >> >> >> Thanks >> >> Muris >> >> >> >> *From: *Oliver Gorwits <ol...@cp...> >> *Date: *Tuesday, 27 June 2023 at 17:22 >> *To: *Muris <alc...@gm...>, <net...@li...> >> *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into >> netdisco >> >> >> >> Hi Muris, sure I will take a look at the ticket, many thanks, >> >> Oliver. >> >> >> >> On Thu, 22 Jun 2023 at 21:18, Muris <alc...@gm...> wrote: >> >> Hey oliver was also just going to ask would it please be possible if you >> could add these to the mibs dir when you have a moment ? >> >> Have uploaded the zip a little while ago in that issues URL >> >> >> Thanks in advance >> >> >> >> On 17 May 2023, at 22:00, Muris <alc...@gm...> wrote: >> >> >> >> Hi Oliver, just wanted to ask if you would be able to integrate these >> Aruba/Silverpeak MIBS into netdisco, I have attached them a few months ago. >> >> >> >> We have number of these devices and having these mibs working would be >> great, right now majority report as “unknown enterprises” etc >> >> >> >> *From: *Muris <alc...@gm...> >> *Date: *Friday, 10 March 2023 at 22:00 >> *To: *Oliver Gorwits <ol...@cp...> >> *Cc: *"net...@li..." < >> net...@li...> >> *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into >> netdisco >> >> >> >> Thanks Oliver, have done and put it there ☺ >> >> >> >> *From: *Oliver Gorwits <ol...@cp...> >> *Date: *Friday, 10 March 2023 at 21:33 >> *To: *Muris <alc...@gm...> >> *Cc: *"net...@li..." < >> net...@li...> >> *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into >> netdisco >> >> >> >> Hi Muris >> >> >> >> Sure, please would you kindly open a ticket here on the netdisco-mibs >> repository: https://github.com/netdisco/netdisco-mibs/issues >> >> >> >> Even better, if you can download the MIBs and attach them, please, >> because Netdisco devs do not have a contract with Aruba to do that. >> >> >> >> Kind regards >> >> Oliver. >> >> >> >> On Fri, 10 Mar 2023 at 10:19, Muris <alc...@gm...> wrote: >> >> Hey guys, I was wondering if someone would be able to add the following >> Aruba SDWAN/Silverpeak mibs into the base netdisco? >> >> >> >> >> https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip >> >> >> >> >> >> Originally from this link >> >> https://www.arubanetworks.com/techdocs/sdwan/mibs/ >> >> >> >> Thanks >> >> Muris >> >> _______________________________________________ >> 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: Muris <alc...@gm...> - 2024-08-28 09:57:44
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Thanks oliver, but to make those mibs work it really needs the silverpeak snmp<div>Info module will you release that also?</div><div><br></div><div>I want to update to latest netdisco but waiting when you update snmp info, otherwise i have to hack the files.</div><div><div dir="ltr"><div><div><br></div></div></div><div dir="ltr"><br><blockquote type="cite">On 28 Aug 2024, at 16:24, Oliver Gorwits <ol...@cp...> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Hi Muris, thanks for your patience, I've added the updated MIBs to the repo (and will release soon, maybe today)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 22 Jul 2024 at 17:35, Muris <<a href="mailto:alc...@gm...">alc...@gm...</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg8866021869214385471"><div lang="EN-AU" style="overflow-wrap: break-word;"><div class="m_8866021869214385471WordSection1"><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Hey Oliver, I just wanted to let you know I got the integration working with Silverpeak and the code for it, its on the github page.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Are you able to integrate this in the next update of netdisco and with updated version 9.5 of the mibs?<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><a href="https://github.com/user-attachments/files/16327192/mibs-9.5.zip" target="_blank">https://github.com/user-attachments/files/16327192/mibs-9.5.zip</a><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Many thanks </span><span lang="EN-GB" style="font-family:"Apple Color Emoji"">☺</span><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Muris<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>><br><b>Date: </b>Monday 22 July 2024 at 12:08<br><b>To: </b>Oliver Gorwits <<a href="mailto:ol...@cp..." target="_blank">ol...@cp...</a>>, <<a href="mailto:net...@li..." target="_blank">net...@li...</a>><br><b>Subject: </b>Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:12pt;font-family:Aptos,sans-serif"><u></u> <u></u></span></p></div><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Hey, just to let you know I have been working on writing the SNMP info for silverpeak integration, but I feel im almost there but I feel I am missing something for netdisco to pick it up fully.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Ive put up my code and testing on <a href="https://github.com/netdisco/snmp-info/issues/524" target="_blank">https://github.com/netdisco/snmp-info/issues/524</a><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">I feel I am just missing a bit to get it working and picked up into netdisco, feel free to review the code.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Muris<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>><br><b>Date: </b>Wednesday 21 February 2024 at 17:32<br><b>To: </b>Oliver Gorwits <<a href="mailto:ol...@cp..." target="_blank">ol...@cp...</a>>, <<a href="mailto:net...@li..." target="_blank">net...@li...</a>><br><b>Subject: </b>Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:12pt;font-family:Aptos,sans-serif"><u></u> <u></u></span></p></div><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Hey Oliver, I also just remembered about this one, I know you added the Aruba/Silverpeak Mibs for it, but it still says “unknown enterprises”<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Example below screenshot – is there a way to troubleshoot this why it’s not using those additional Mibs?<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Just would like these devices to be classified properly for vendor/model as it doesn’t seem to reference still anything from the Mibs. Im really keen to get it showing correctly like all other devices.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><div><image001.jpg></div><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>><br><b>Date: </b>Tuesday, 29 August 2023 at 17:37<br><b>To: </b>Oliver Gorwits <<a href="mailto:ol...@cp..." target="_blank">ol...@cp...</a>>, <<a href="mailto:net...@li..." target="_blank">net...@li...</a>><br><b>Subject: </b>Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco<u></u><u></u></span></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Hi Oliver, thanks for adding the MIBS support.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">I updated to the latest netdisco with the mibs, but still it cant classify the silverpeak devices, it still comes up as “unknown enterprises” for many of them.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Is there some troubleshooting I can execute on command to see whats going on and if its mapping it to mibs or something?<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Thanks<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Muris<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><u></u> <u></u></span></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Oliver Gorwits <<a href="mailto:ol...@cp..." target="_blank">ol...@cp...</a>><br><b>Date: </b>Tuesday, 27 June 2023 at 17:22<br><b>To: </b>Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>>, <<a href="mailto:net...@li..." target="_blank">net...@li...</a>><br><b>Subject: </b>Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco<u></u><u></u></span></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Hi Muris, sure I will take a look at the ticket, many thanks,<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Oliver.<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">On Thu, 22 Jun 2023 at 21:18, Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>> wrote:<u></u><u></u></p></div><blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin:5pt 0cm 5pt 4.8pt"><div><p class="MsoNormal">Hey oliver was also just going to ask would it please be possible if you could add these to the mibs dir when you have a moment ?<u></u><u></u></p><div><p class="MsoNormal">Have uploaded the zip a little while ago in that issues URL<br> <u></u><u></u></p></div><div><p class="MsoNormal">Thanks in advance<u></u><u></u></p></div><div><div><p class="MsoNormal" style="margin-bottom:12pt"><u></u> <u></u></p><blockquote style="margin-top:5pt;margin-bottom:5pt"><p class="MsoNormal" style="margin-bottom:12pt">On 17 May 2023, at 22:00, Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>> wrote:<u></u><u></u></p></blockquote></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><p class="MsoNormal"><u></u><u></u></p><div><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Hi Oliver, just wanted to ask if you would be able to integrate these Aruba/Silverpeak MIBS into netdisco, I have attached them a few months ago.</span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">We have number of these devices and having these mibs working would be great, right now majority report as “unknown enterprises” etc</span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>><br><b>Date: </b>Friday, 10 March 2023 at 22:00<br><b>To: </b>Oliver Gorwits <<a href="mailto:ol...@cp..." target="_blank">ol...@cp...</a>><br><b>Cc: </b>"<a href="mailto:net...@li..." target="_blank">net...@li...</a>" <<a href="mailto:net...@li..." target="_blank">net...@li...</a>><br><b>Subject: </b>Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco</span><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Thanks Oliver, have done and put it there </span><span lang="EN-GB" style="font-family:"Apple Color Emoji"">☺</span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Oliver Gorwits <<a href="mailto:ol...@cp..." target="_blank">ol...@cp...</a>><br><b>Date: </b>Friday, 10 March 2023 at 21:33<br><b>To: </b>Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>><br><b>Cc: </b>"<a href="mailto:net...@li..." target="_blank">net...@li...</a>" <<a href="mailto:net...@li..." target="_blank">net...@li...</a>><br><b>Subject: </b>Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco</span><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Hi Muris</span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif"> </span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Sure, please would you kindly open a ticket here on the netdisco-mibs repository: <a href="https://github.com/netdisco/netdisco-mibs/issues" target="_blank">https://github.com/netdisco/netdisco-mibs/issues</a></span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif"> </span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Even better, if you can download the MIBs and attach them, please, because Netdisco devs do not have a contract with Aruba to do that.</span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif"> </span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Kind regards</span><u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:"Trebuchet MS",sans-serif">Oliver.</span><u></u><u></u></p></div></div><p class="MsoNormal"> <u></u><u></u></p><div><div><p class="MsoNormal">On Fri, 10 Mar 2023 at 10:19, Muris <<a href="mailto:alc...@gm..." target="_blank">alc...@gm...</a>> wrote:<u></u><u></u></p></div><blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin:5pt 0cm 5pt 4.8pt"><div><div><div><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Hey guys, I was wondering if someone would be able to add the following Aruba SDWAN/Silverpeak mibs into the base netdisco?</span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><a href="https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip" target="_blank">https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip</a></span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Originally from this link</span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"><a href="https://www.arubanetworks.com/techdocs/sdwan/mibs/" target="_blank">https://www.arubanetworks.com/techdocs/sdwan/mibs/</a></span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Thanks </span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-GB" style="font-family:Arial,sans-serif">Muris</span><u></u><u></u></p></div></div><p class="MsoNormal">_______________________________________________<br>Netdisco mailing list<br><a href="mailto:net...@li..." target="_blank">net...@li...</a><br><a href="https://sourceforge.net/p/netdisco/mailman/netdisco-users/" target="_blank">https://sourceforge.net/p/netdisco/mailman/netdisco-users/</a><u></u><u></u></p></div></blockquote></div></div></div></blockquote></div></div></blockquote></div></div></div> </div></blockquote></div> </div></blockquote></div></body></html> |
From: Oliver G. <ol...@cp...> - 2024-08-28 08:07:47
|
Many thanks Jeremiah! This has been added to SNMP::Info for the next release. On Fri, 26 Apr 2024 at 15:32, Jeremiah Garmatter <j-g...@on...> wrote: > Thanks for the input Michael, I saw some of your other posts while > reviewing the netdisco-user archives. It's a shame Meraki hasn't corrected > their issues after all this time. > > Sure thing Oliver, see below for my additions to Info.pm and the contents > of Meraki.pm. I can get the MAC addresses from each port but I don't get > VLANs, which would be nice to have. > > > Info.pm: > --Around line 1750-- > my %l3sysoidmap = ( > 29671 => 'SNMP::Info::Layer3::Meraki', <------ Right here, > obtained from an archived netdisco-user email. > 9 => 'SNMP::Info::Layer3::CiscoSwitch', > --Around line 1900-- > $objtype = 'SNMP::Info::Layer3::C3550' if $desc =~ /(C3550|C3560)/; > $objtype = 'SNMP::Info::Layer3::C4000' if $desc =~ /Catalyst > 4[05]00/; > $objtype = 'SNMP::Info::Layer3::Foundry' if $desc =~ /foundry/i; > $objtype = 'SNMP::Info::Layer3::ERX' if $desc =~ /erx/i; > > # Meraki MS3* <-------- Right here, match the description with > any of our Meraki devices (MS390 and 355). > $objtype = 'SNMP::Info::Layer3::Meraki' > if $desc =~ /^Meraki\sMS3/; > > # Aironet - older non-IOS > $objtype = 'SNMP::Info::Layer3::Aironet' > > Created Meraki.pm: > # I whipped this up from the suggestions in the included link and other pm > files. > # https://sourceforge.net/p/netdisco/mailman/message/37257000/ > # - custom addition 4/25/24 > > package SNMP::Info::Layer3::Meraki; > > use strict; > use warnings; > use Exporter; > use SNMP::Info::Layer3; > > @SNMP::Info::Layer3::Meraki::ISA = qw/SNMP::Info::Layer3 Exporter/; > @SNMP::Info::Layer3::Meraki::EXPORT_OK = qw//; > > our ($VERSION, %GLOBALS, %MIBS, %FUNCS, %MUNGE); > > $VERSION = '3.970001'; > > %MIBS = ( > %SNMP::Info::Layer2::MIBS, %SNMP::Info::Layer3::MIBS, > ); > > %GLOBALS = ( > %SNMP::Info::Layer2::GLOBALS, %SNMP::Info::Layer3::GLOBALS, > ); > > %FUNCS = ( %SNMP::Info::Layer2::FUNCS, %SNMP::Info::Layer3::FUNCS, ); > > %MUNGE = ( %SNMP::Info::Layer2::MUNGE, %SNMP::Info::Layer3::MUNGE, ); > > sub layers { > return '00000110'; > } > > > > <https://www.google.com/url?q=https://onu.edu&source=gmail-html&ust=1674828335432000&usg=AOvVaw28_De1JtB-AXSBY3ffLqIg> > <https://www.google.com/url?q=https://www.instagram.com/ohionorthern/?hl%3Den&source=gmail-html&ust=1674828335432000&usg=AOvVaw2T5Mr7Skb1malhmRz_e6L7> > <https://www.google.com/url?q=https://www.facebook.com/OhioNorthern/&source=gmail-html&ust=1674828335432000&usg=AOvVaw3nAxUn3wIQnybVvpceEIDC> > <https://www.google.com/url?q=https://twitter.com/ohionorthern?ref_src%3Dtwsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor&source=gmail-html&ust=1674828335432000&usg=AOvVaw2gJCHRWcjlGtZi5ft71zQz> > <https://www.google.com/url?q=https://www.youtube.com/channel/UCvdGjbOWVUkVJZVm0l-px7g&source=gmail-html&ust=1674828335432000&usg=AOvVaw1nIUlB6-a3l6ENfFlK-WfL> > *Jeremiah Garmatter* > Linux Systems Administrator > Office of Information Technology > IT Building 107 > 419-772-1074 > j-g...@on... > > > On Fri, Apr 26, 2024 at 5:36 AM Oliver Gorwits <ol...@cp...> wrote: > >> Hi Jeremiah! >> >> Many thanks for getting in touch. Are you able to share the modifications >> to Info.pm and Meraki.pm that you made in order to get the macsuck and >> arpnip working? >> >> Also did the macsuck and arpnip work enough so you are OK with the >> results, or is more still missing? >> >> (honestly, as others have said, the Meraki support is difficult for SNMP, >> so it might never be complete, and we could consider alternatives later >> such as CLI scraping or APIs) >> >> Kind regards, >> Oliver. >> >> On Thu, 25 Apr 2024 at 19:32, Jeremiah Garmatter <j-g...@on...> >> wrote: >> >>> Hello, >>> >>> We recently added a few Meraki MS switches to our network. >>> After reviewing some archived emails regarding Meraki I have come to the >>> conclusion that Meraki and SNMP-based monitoring tools are not very >>> compatible. I have issues with both Netdisco and another tool, Cacti, >>> regarding only the Meraki devices. >>> >>> That being said, I was able to perform a macsuck and arpnip after >>> following the instructions within an archived email. I had to modify the >>> ~netdisco/perl5/lib/perl5/SNMP/Info.pm file and create a >>> ~netdisco/perl5/lib/perl5/SNMP/Info/Layer3/Meraki.pm file. >>> >>> I can't help but feel that I hacked the solution together from the >>> emails and other Layer3 device files. I am not very confident in this >>> approach since I don't know much about the inner workings of Netdisco or >>> the Perl files. >>> >>> I am curious if anyone else has created their own "Meraki.pm" kind of >>> file and if you would be willing to share it. >>> >>> <https://www.google.com/url?q=https://onu.edu&source=gmail-html&ust=1674828335432000&usg=AOvVaw28_De1JtB-AXSBY3ffLqIg> >>> <https://www.google.com/url?q=https://www.instagram.com/ohionorthern/?hl%3Den&source=gmail-html&ust=1674828335432000&usg=AOvVaw2T5Mr7Skb1malhmRz_e6L7> >>> <https://www.google.com/url?q=https://www.facebook.com/OhioNorthern/&source=gmail-html&ust=1674828335432000&usg=AOvVaw3nAxUn3wIQnybVvpceEIDC> >>> <https://www.google.com/url?q=https://twitter.com/ohionorthern?ref_src%3Dtwsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor&source=gmail-html&ust=1674828335432000&usg=AOvVaw2gJCHRWcjlGtZi5ft71zQz> >>> <https://www.google.com/url?q=https://www.youtube.com/channel/UCvdGjbOWVUkVJZVm0l-px7g&source=gmail-html&ust=1674828335432000&usg=AOvVaw1nIUlB6-a3l6ENfFlK-WfL> >>> *Jeremiah Garmatter* >>> Linux Systems Administrator >>> Office of Information Technology >>> IT Building 107 >>> 419-772-1074 >>> j-g...@on... >>> _______________________________________________ >>> 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: Oliver G. <ol...@cp...> - 2024-08-28 06:59:25
|
Hi Linwood First, I guess at the command line, if they have it, you can show lldp neighbors or similar for cdp, and it works - you can see the neighbor device of the other vendor? Second, the has_topo() method is looking for standard SNMP table records of neighbors, and perhaps they're not implemented yet on the platform. Do you have a support contract to ask them if it's implemented? Third, sometimes the stuff is in SNMP but in a custom/wrong location. We can possibly do a bit of work if you send an snmpwalk output ( https://github.com/netdisco/netdisco/wiki/Snapshot#snmpwalk-option), but it depends on someone finding the time. The best option is always for the vendor to Do The Right Thing and put neighbor info into the standard place in SNMP. regards Oliver. On Tue, 2 Jul 2024 at 17:34, on@LEFerguson.com <on...@le...> wrote: > Well, my electricians are 2 hours late and still not here so I spent a > few minutes trying to figure this out, and I do see one thing. > > > > When accessing my core Netgear switch I get a Netdisco error. > > > > SNMP::Info 3.970001 > > SNMP::Info::device_type() layers:01001111 id:4526 sysDescr:"NETGEAR > 24-Port Gigabit PoE+ Smart Managed Pro Switch with 4 SFP Ports (GS728TPv2), > Software Version 6.0.10.20, Boot Version 1.0.0.5" > > [1756991] 2024-07-02 14:30:18 debug [192.168.130.2] neigh - removed 0 > outdated manual topology links > > [1756991] 2024-07-02 14:30:18 debug [192.168.130.2] neigh - setting > manual topology links > > SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 : > .1.0.8802.1.1.2.1.3.6.0 > > SNMP::Info::_global(lldp_sys_cap) NOSUCHOBJECT at > /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Neighbors.pm > line 120. > > SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId : > .1.0.8802.1.1.2.1.4.1.1.5 > > > > This is on what I think is current, version 2.76.5 > > > > > That line is here: > > > > sub store_neighbors { > > my $device = shift; > > my @to_discover = (); > > > > my $snmp = App::Netdisco::Transport::SNMP->reader_for($device) > > or return (); # already checked! > > > > # first allow any manually configured topology to be set > > # and do this before we cache the rows in vars->{'device_ports'} > > set_manual_topology($device); > > > > if (!defined $snmp->has_topo) { > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Line 120 > > debug sprintf ' [%s] neigh - neighbor protocols are not enabled', > $device->ip; > > return @to_discover; > > } > > > > I struggle with perl so am not sure if that means the object $snmp is not > found (I think so), or that a OID it is referencing is not found. > > > > What’s odd is that this switch DOES show neighbors (two other netgears), > but when I run: > > > > ~/bin/netdisco-do discover::neighbors -d closetsw.leferguson.com -DIS > > > > At the end it shows > > > > [1770671] 2024-07-02 14:41:29 info discover::neighbors: status info: > [192.168.130.2] neigh - processed 0 neighbors > > > > If I compare the run to the other netgears (much older devices), those do > not get the above error and do show this switch as a neighbor. > > > > I’m not sure what to look for though if that’s a perl error. Note that > netdisco does a fine job of discovering this switch in general, the details > page looks right, the ports page right (the uplink port to the AP shows the > AP by name and IP). So… not sure what “not found” means. > > > > > > *From:* on@LEFerguson.com > *Sent:* Tuesday, July 2, 2024 9:44 AM > *To:* net...@li... > *Subject:* Mikrotik and Neighbors > > > > Mikrotik now (probably for sometime but I just noticed, running 7.15.2) > supports both LLDP and CDP for neighbor discovery, and SNMP. > > > > I have a Netgear switch between all the mikrotik devices. > > > > Both Netgear and Mikrotik see their neighbors in their own display, but > Netdisco does not show them as neighbors (other than netgear to netgear > which works, at the moment I have no Mikrotik to Mikrotik). > > > > I’ve been down the rathole of figuring neighbor issues out and it can be a > long one so with apologies in advance for not yet doing my homework…. > > > > Has anyone chased this particular rat yet, and knows the situation and/or > workaround or settings? > > > > If not, when I get some time will try to find out. > > > > Linwood > > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > |
From: Oliver G. <ol...@cp...> - 2024-08-28 06:54:55
|
Hi Muris, thanks for your patience, I've added the updated MIBs to the repo (and will release soon, maybe today) On Mon, 22 Jul 2024 at 17:35, Muris <alc...@gm...> wrote: > Hey Oliver, I just wanted to let you know I got the integration working > with Silverpeak and the code for it, its on the github page. > > > > Are you able to integrate this in the next update of netdisco and with > updated version 9.5 of the mibs? > > > > https://github.com/user-attachments/files/16327192/mibs-9.5.zip > > > > Many thanks ☺ > > > > Muris > > > > *From: *Muris <alc...@gm...> > *Date: *Monday 22 July 2024 at 12:08 > *To: *Oliver Gorwits <ol...@cp...>, < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hey, just to let you know I have been working on writing the SNMP info for > silverpeak integration, but I feel im almost there but I feel I am missing > something for netdisco to pick it up fully. > > > > Ive put up my code and testing on > https://github.com/netdisco/snmp-info/issues/524 > > > > I feel I am just missing a bit to get it working and picked up into > netdisco, feel free to review the code. > > > > Muris > > > > *From: *Muris <alc...@gm...> > *Date: *Wednesday 21 February 2024 at 17:32 > *To: *Oliver Gorwits <ol...@cp...>, < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hey Oliver, I also just remembered about this one, I know you added the > Aruba/Silverpeak Mibs for it, but it still says “unknown enterprises” > > > > Example below screenshot – is there a way to troubleshoot this why it’s > not using those additional Mibs? > > > > Just would like these devices to be classified properly for vendor/model > as it doesn’t seem to reference still anything from the Mibs. Im really > keen to get it showing correctly like all other devices. > > > > [image: A white background with black text Description automatically > generated] > > > > *From: *Muris <alc...@gm...> > *Date: *Tuesday, 29 August 2023 at 17:37 > *To: *Oliver Gorwits <ol...@cp...>, < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hi Oliver, thanks for adding the MIBS support. > > > > I updated to the latest netdisco with the mibs, but still it cant classify > the silverpeak devices, it still comes up as “unknown enterprises” for many > of them. > > > > Is there some troubleshooting I can execute on command to see whats going > on and if its mapping it to mibs or something? > > > > Thanks > > Muris > > > > *From: *Oliver Gorwits <ol...@cp...> > *Date: *Tuesday, 27 June 2023 at 17:22 > *To: *Muris <alc...@gm...>, <net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hi Muris, sure I will take a look at the ticket, many thanks, > > Oliver. > > > > On Thu, 22 Jun 2023 at 21:18, Muris <alc...@gm...> wrote: > > Hey oliver was also just going to ask would it please be possible if you > could add these to the mibs dir when you have a moment ? > > Have uploaded the zip a little while ago in that issues URL > > > Thanks in advance > > > > On 17 May 2023, at 22:00, Muris <alc...@gm...> wrote: > > > > Hi Oliver, just wanted to ask if you would be able to integrate these > Aruba/Silverpeak MIBS into netdisco, I have attached them a few months ago. > > > > We have number of these devices and having these mibs working would be > great, right now majority report as “unknown enterprises” etc > > > > *From: *Muris <alc...@gm...> > *Date: *Friday, 10 March 2023 at 22:00 > *To: *Oliver Gorwits <ol...@cp...> > *Cc: *"net...@li..." < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Thanks Oliver, have done and put it there ☺ > > > > *From: *Oliver Gorwits <ol...@cp...> > *Date: *Friday, 10 March 2023 at 21:33 > *To: *Muris <alc...@gm...> > *Cc: *"net...@li..." < > net...@li...> > *Subject: *Re: [Netdisco] Adding Aruba SDWAN/Silverpeak MIBS into netdisco > > > > Hi Muris > > > > Sure, please would you kindly open a ticket here on the netdisco-mibs > repository: https://github.com/netdisco/netdisco-mibs/issues > > > > Even better, if you can download the MIBs and attach them, please, because > Netdisco devs do not have a contract with Aruba to do that. > > > > Kind regards > > Oliver. > > > > On Fri, 10 Mar 2023 at 10:19, Muris <alc...@gm...> wrote: > > Hey guys, I was wondering if someone would be able to add the following > Aruba SDWAN/Silverpeak mibs into the base netdisco? > > > > https://www.arubanetworks.com/website/techdocs/sdwan-PDFs/mibs/mibs-9.2.zip > > > > > > Originally from this link > > https://www.arubanetworks.com/techdocs/sdwan/mibs/ > > > > Thanks > > Muris > > _______________________________________________ > Netdisco mailing list > net...@li... > https://sourceforge.net/p/netdisco/mailman/netdisco-users/ > > |
From: Muris <alc...@gm...> - 2024-08-01 09:12:37
|
I think I found the issue with the nexus, via SNMP it’s not getting any of the vrf data and subnets when I do a snmp walk.. so that’s the reason its not capturing data except the vlan ids under the “vlans” tab in netdisco. In the netdisco database in device_ip its missing ip,alias, subnet,port for vlans which it cannot get to map, but in device_port in the “port” table it does have like Vlan3733 and under “name” it does have the description of the subnet. I was thinking is it possible to use the Nexus SSH collector NXOS.pm to send this command to the device – “show startup-config interface | no-more” and then reading the config file it grabs the subnets what it needs example and stores it in device_ip in the db from vlan interfaces - interface Vlan3733 vrf member TESTING ip address 10.1.1.2/24 description ** TEST VLAN ** no shutdown In the above, Vlan3733 is stored in “port”, the ip address the script calculates the subnet its part of eg 10.1.1.0/24 and stores it in “subnet”, the ip address of the interface 10.1.1.2 is stored in the “alias”, and the ip of the nexus address itself it just adds another entry for itself under “ip” , this is to store the entry in device_ip in the database. This way the subnet will be referenced and have an entry as belonging part of this device. As netdisco doesn’t support vrf yet, there isn’t an entry for vrf member, or a way to display it on the web interface so that’s ok I suppose until netdisco3 comes out. Is it possible to add this as a subroutine in the NXOS.pm for the ssh collector, how difficult would that be and then store it in the db? One thing I can’t understand also in Catalyst Cisco 6500’s all the vrfs all the subnets are read by netdisco and don’t have any issues displaying the data, but the nexus seems different. Muris From: Muris <alc...@gm...> Date: Tuesday 30 July 2024 at 19:45 To: "net...@li..." <net...@li...> Subject: Netdisco and Nexus MPLS Hey all, I have another question – is there a reason why a Nexus Core in MPLS would not be displaying all the subnets in the “addresses” tab of the webpage. It only lists the interfaces, port channel associated, but anything to do with vlans in vrf members it doesn’t display anything under “addresses” is there a way to get it to display all vlans on a nexus? It doesn’t have to display the vrf member, but at least the ip address of the vlan and description, but having all of them would be nice I suppose. Thanks Muris |
From: Jethro B. <jet...@st...> - 2024-07-30 15:55:54
|
And to now answer another point from Christian (apols for mangling these messages): Christian Ramseyer <ram...@ne...> wrote: > ?On 27.07.2024 03:10, Muris wrote: > Alright thanks if there is already a modification for Aruba.pm but that modification doesnt work for ArubaOS Controllers, what then? > > Is it possible to put in that sub routine a second one if it detects a controller using sysDescr AurbaOs, to go to a different routine in Aruba.pm? > And if you have an example how that might look? Yes this is common, there is a very long function in Info.pm that tries to find the best matching class based on SNMP oids, sysDescr regex etc. Check around the Cisco identification, there is a lot of specific subclasses for that brand: https://github.com/netdisco/snmp-info/blob/master/lib/SNMP/Info.pm#L1900 $objtype = 'SNMP::Info::Layer3::C3550' if $desc =~ /(C3550|C3560)/; $objtype = 'SNMP::Info::Layer3::C4000' if $desc =~ /Catalyst 4[05]00/; ... etc.. If it turned out that ArubaOS v10 needed something else doing to obtain the Arp table now, you could use sysDescr within SNMP::Info::Layer3::Aruba: SNMP::Info::device_type() layers:00000111 id:14823 sysDescr:"ArubaOS (MODEL: Aruba7240XM), Version 8.10.0.12 LSR (89862)" and test this in the function at_paddr to see if this is version 10, and do something different instead (look at another MIB maybe if the data is elsewhere). Normally, at_paddr uses ipNetToMediaPhysAddress, but as https://github.com/netdisco/snmp-info/issues/452 discusses this isn't populated on the separate ArubaOS-CX platform, and perhaps this is the case for ArubaOS v10 too[*] Alternatively you might use sysDescr in Info.pm to select a new module SNMP::Info::Layer3::ArubaSomethingElse that does the right thing, but there's a danger there of a lot of duplication with the current SNMP::Info::Layer3::Aruba. [*] does anyone know if ArubaOS 10 for wireless is based on ArubaOSCX, as they move to this cloud management paradigm? Don't get me started on my regular pontifications about the confusion of Aruba (and HP) operating systems and further confusion of the naming of modules within SNMP-Info: https://github.com/netdisco/snmp-info/issues/469 https://github.com/netdisco/snmp-info/issues/527 Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks, Network Manager, Information Services Directorate, University Of Strathclyde, Glasgow, UK The University of Strathclyde is a charitable body, registered in Scotland, number SC015263. ________________________________ From: Jethro Binks <jet...@st...> Sent: 30 July 2024 16:22 To: neil--- <net...@li...> Subject: Re: [Netdisco] ARP matching for netdisco A bit late sorry, but this is a good point from Neil. If it helps, my Aruba wireless is running 8.10, identifies as SNMP::Info::Layer3::Aruba, and I get plenty of arpnips (but almost all APs and few end stations in my case, since the wireless controllers aren't the routing interface for moclient vlans). [8045] 2024-07-30 15:13:14 debug arpnip - processed 1135 ARP Cache entries No idea what happens in 10-land, and no recollection about 6.4. Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks, Network Manager, Information Services Directorate, University Of Strathclyde, Glasgow, UK The University of Strathclyde is a charitable body, registered in Scotland, number SC015263. ________________________________ From: neil--- via netdisco-users <net...@li...> Sent: 26 July 2024 18:34 To: Christian Ramseyer <ram...@ne...>; Muris <alc...@gm...>; neil--- <net...@li...> Subject: Re: [Netdisco] ARP matching for netdisco I don’t the Aruba stuff has been updated since ArubaOS 6.X (Aruba is currently pushing customers from version 8 to 10 which has the control plane in the cloud ). Neil On Fri, Jul 26, 2024, at 11:03 AM, Christian Ramseyer wrote: Hi Muris On 25.07.2024 06:27, Muris wrote: > Hey all, > > Ive picked up another issue ive come across in relation to arpnip’s and > netdisco picking up for matching to mac addresses > > * Ive found on ArubaOS controllers this does not work, and gets 0 arps > and ive seen it on a couple of Aruba switches or two. This is > running the netdisco-do arpnip function when I look at the output. > * Ive also noticed on Cisco SDWAN platform using Cisco ISR 1127/1131 > which has VRF’s on a router it also doesn’t appear to match arps to > macs probably because it has VRFs? > > I tried to use the SSH script in this instance but still didn’t work. > The routers I have are running IOS XE, which doesn’t seem to work with > the SSH collector, as that only has IOS and IOSXR > > 1) I wanted to ask, is there a troubleshooting method for arps > retrieval, and what part of code handles the arp matching? > 3) What part of the code in netdisco looks at arp retrieval and then > storing it into the db into particular method? Is there something that > can be tweaked how it interprets the data, say for a Aruba Controller, > or a Cisco router with vrfs etc For 1 + 3 I use something like this: Run netdisco-do arpnip on the commandline with debugging flags: -D (always, general debugging) -SI (snmp OIDs + snmp info layer) -Q (DB queries, ignore unless you suspect a db issue) e.g. "netdisco-do -DIS -d lab2-ce2 arpnip" To see whats going wrong it's very helpful to compare a device with the expected outcome to the one where stuff doesn't work. >From the debugging you can tell which OIDs are used, whether they send back a response etc. I often also just forget about netdisco and try to get what I need with regular snmpwalk/get, then figure out where the mismatch is. Or conclude that the device does not have the data at all. If you grep around in the code for strings appearing in the debug output it's easy to find where stuff happens, e.g (shortened): $ shopt -s globstar $ egrep '(store_arp|processed.*ARP Cache)' **/* 2>/dev/null lib/App/Netdisco/Util/Node.pm:=head2 store_arp( \%host, $now?, $device_ip ) lib/App/Netdisco/Util/Node.pm:sub store_arp { lib/App/Netdisco/Util/Node.pm: debug sprintf 'store_arp - device %s mac %s ip %s', lib/App/Netdisco/Worker/Plugin/Arpnip/Nodes.pm:use App::Netdisco::Util::Node qw/che lib/App/Netdisco/Worker/Plugin/Arpnip/Nodes.pm: store_arp(\%$_, $now, $device->ip) Then just start hacking around in there until it works :) > > 2) What if I have a IOS XE router with vrf’s is it able to retrieve IP > to mac mappings? If I can do a “show arp vrf 2000” this shows the list, > but how do I make that available into netdisco? > I actually just tried this on regular IOS-XE and I seem to get all VRFs from the regular SNMP method, e.g.: # show version Cisco IOS XE Software, Version 17.09.03a Cisco IOS Software [Cupertino], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.9.3a, RELEASE SOFTWARE (fc2) cisco ISR4331/K9 lab2-CE2#show vrf Name Default RD Protocols Interfaces Mgmt-intf <not set> ipv4,ipv6 Gi0 VPRN-KTV1 65126:20923 ipv4,ipv6 Lo1 Gi0/0/0 Gi0/0/2.3811 lab2-CE2#show ip arp lab2-CE2#show ip arp Protocol Address Age (min) Hardware Addr Type Interface Internet 10.18.220.233 89 4055.82a1.xxxx ARPA GigabitEthernet0/0/2.3899 Internet 10.18.220.234 94 147b.ac00.xxxx ARPA GigabitEthernet0/0/2.3899 Internet 10.18.220.238 - 70d3.791a.xxxx ARPA GigabitEthernet0/0/2.3899 lab2-CE2# lab2-CE2#show ip arp vrf VPRN-KTV1 Protocol Address Age (min) Hardware Addr Type Interface Internet 10.18.199.129 89 4055.82a1.xxxx ARPA GigabitEthernet0/0/2.3811 Internet 10.18.199.130 90 147b.ac00.xxxx ARPA GigabitEthernet0/0/2.3811 Internet 10.18.199.134 - 70d3.791a.xxxx ARPA GigabitEthernet0/0/2.3811 Internet 10.30.194.49 - 70d3.791a.xxxx ARPA GigabitEthernet0/0/0 Internet 10.30.194.50 0 001c.7fa3.xxxx ARPA GigabitEthernet0/0/0 lab2-CE2# netdisco-do -D -d lab2-ce2 arpnip ... [13904] 2024-07-26 15:24:42 debug => running workers for phase: store [13904] 2024-07-26 15:24:42 debug -> run worker store/0 "arpnip::nodes" [13904] 2024-07-26 15:24:42 debug resolving 8 ARP entries with max 50 outstanding requests [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 40:55:82:a1:xx:xx ip 10.18.220.233 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 14:7b:ac:00:xx:xx ip 10.18.199.130 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 70:d3:79:1a:xx:xx ip 10.30.194.49 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 14:7b:ac:00:xx:xx ip 10.18.220.234 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 40:55:82:a1:xx:xx ip 10.18.199.129 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 00:1c:7f:a3:xx:xx ip 10.30.194.50 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 70:d3:79:1a:xx:xx ip 10.18.220.238 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 70:d3:79:1a:xx:xx ip 10.18.199.134 [13904] 2024-07-26 15:24:42 debug [10.18.165.188] arpnip - processed 8 ARP Cache entries [13904] 2024-07-26 15:24:42 debug [10.18.165.188] arpnip - processed 0 IPv6 Neighbor Cache entries So I suspect the trouble is related to the SDWAN features or a specific release? Generally the more virutalization and software defined doohickeys a platform has the less likely it is to cough up all arp entries via SNMP. If you need to make an SSH Collector for IOS-XE SDWAN, you best figure out first what commands are needed, then copy an existing one an make it work. Many already do something like enumerate all contexts/vrf/vdoms and then run commands for each, you can look at e.g. CPVSX, ASAContext or FortiOS. Good luck Christian > > Sorry if its been asked before .. but im finding lately due to the > environment getting complex I wouldn’t mind how the whole arp storing > works and getting more things to work better . > > Muris > > > > _______________________________________________ > Netdisco mailing list > net...@li...<mailto:net...@li...> > 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 _______________________________________________ Netdisco mailing list net...@li...<mailto:net...@li...> https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
From: Jethro B. <jet...@st...> - 2024-07-30 15:37:56
|
A bit late sorry, but this is a good point from Neil. If it helps, my Aruba wireless is running 8.10, identifies as SNMP::Info::Layer3::Aruba, and I get plenty of arpnips (but almost all APs and few end stations in my case, since the wireless controllers aren't the routing interface for moclient vlans). [8045] 2024-07-30 15:13:14 debug arpnip - processed 1135 ARP Cache entries No idea what happens in 10-land, and no recollection about 6.4. Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks, Network Manager, Information Services Directorate, University Of Strathclyde, Glasgow, UK The University of Strathclyde is a charitable body, registered in Scotland, number SC015263. ________________________________ From: neil--- via netdisco-users <net...@li...> Sent: 26 July 2024 18:34 To: Christian Ramseyer <ram...@ne...>; Muris <alc...@gm...>; neil--- <net...@li...> Subject: Re: [Netdisco] ARP matching for netdisco I don’t the Aruba stuff has been updated since ArubaOS 6.X (Aruba is currently pushing customers from version 8 to 10 which has the control plane in the cloud ). Neil On Fri, Jul 26, 2024, at 11:03 AM, Christian Ramseyer wrote: Hi Muris On 25.07.2024 06:27, Muris wrote: > Hey all, > > Ive picked up another issue ive come across in relation to arpnip’s and > netdisco picking up for matching to mac addresses > > * Ive found on ArubaOS controllers this does not work, and gets 0 arps > and ive seen it on a couple of Aruba switches or two. This is > running the netdisco-do arpnip function when I look at the output. > * Ive also noticed on Cisco SDWAN platform using Cisco ISR 1127/1131 > which has VRF’s on a router it also doesn’t appear to match arps to > macs probably because it has VRFs? > > I tried to use the SSH script in this instance but still didn’t work. > The routers I have are running IOS XE, which doesn’t seem to work with > the SSH collector, as that only has IOS and IOSXR > > 1) I wanted to ask, is there a troubleshooting method for arps > retrieval, and what part of code handles the arp matching? > 3) What part of the code in netdisco looks at arp retrieval and then > storing it into the db into particular method? Is there something that > can be tweaked how it interprets the data, say for a Aruba Controller, > or a Cisco router with vrfs etc For 1 + 3 I use something like this: Run netdisco-do arpnip on the commandline with debugging flags: -D (always, general debugging) -SI (snmp OIDs + snmp info layer) -Q (DB queries, ignore unless you suspect a db issue) e.g. "netdisco-do -DIS -d lab2-ce2 arpnip" To see whats going wrong it's very helpful to compare a device with the expected outcome to the one where stuff doesn't work. >From the debugging you can tell which OIDs are used, whether they send back a response etc. I often also just forget about netdisco and try to get what I need with regular snmpwalk/get, then figure out where the mismatch is. Or conclude that the device does not have the data at all. If you grep around in the code for strings appearing in the debug output it's easy to find where stuff happens, e.g (shortened): $ shopt -s globstar $ egrep '(store_arp|processed.*ARP Cache)' **/* 2>/dev/null lib/App/Netdisco/Util/Node.pm:=head2 store_arp( \%host, $now?, $device_ip ) lib/App/Netdisco/Util/Node.pm:sub store_arp { lib/App/Netdisco/Util/Node.pm: debug sprintf 'store_arp - device %s mac %s ip %s', lib/App/Netdisco/Worker/Plugin/Arpnip/Nodes.pm:use App::Netdisco::Util::Node qw/che lib/App/Netdisco/Worker/Plugin/Arpnip/Nodes.pm: store_arp(\%$_, $now, $device->ip) Then just start hacking around in there until it works :) > > 2) What if I have a IOS XE router with vrf’s is it able to retrieve IP > to mac mappings? If I can do a “show arp vrf 2000” this shows the list, > but how do I make that available into netdisco? > I actually just tried this on regular IOS-XE and I seem to get all VRFs from the regular SNMP method, e.g.: # show version Cisco IOS XE Software, Version 17.09.03a Cisco IOS Software [Cupertino], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.9.3a, RELEASE SOFTWARE (fc2) cisco ISR4331/K9 lab2-CE2#show vrf Name Default RD Protocols Interfaces Mgmt-intf <not set> ipv4,ipv6 Gi0 VPRN-KTV1 65126:20923 ipv4,ipv6 Lo1 Gi0/0/0 Gi0/0/2.3811 lab2-CE2#show ip arp lab2-CE2#show ip arp Protocol Address Age (min) Hardware Addr Type Interface Internet 10.18.220.233 89 4055.82a1.xxxx ARPA GigabitEthernet0/0/2.3899 Internet 10.18.220.234 94 147b.ac00.xxxx ARPA GigabitEthernet0/0/2.3899 Internet 10.18.220.238 - 70d3.791a.xxxx ARPA GigabitEthernet0/0/2.3899 lab2-CE2# lab2-CE2#show ip arp vrf VPRN-KTV1 Protocol Address Age (min) Hardware Addr Type Interface Internet 10.18.199.129 89 4055.82a1.xxxx ARPA GigabitEthernet0/0/2.3811 Internet 10.18.199.130 90 147b.ac00.xxxx ARPA GigabitEthernet0/0/2.3811 Internet 10.18.199.134 - 70d3.791a.xxxx ARPA GigabitEthernet0/0/2.3811 Internet 10.30.194.49 - 70d3.791a.xxxx ARPA GigabitEthernet0/0/0 Internet 10.30.194.50 0 001c.7fa3.xxxx ARPA GigabitEthernet0/0/0 lab2-CE2# netdisco-do -D -d lab2-ce2 arpnip ... [13904] 2024-07-26 15:24:42 debug => running workers for phase: store [13904] 2024-07-26 15:24:42 debug -> run worker store/0 "arpnip::nodes" [13904] 2024-07-26 15:24:42 debug resolving 8 ARP entries with max 50 outstanding requests [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 40:55:82:a1:xx:xx ip 10.18.220.233 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 14:7b:ac:00:xx:xx ip 10.18.199.130 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 70:d3:79:1a:xx:xx ip 10.30.194.49 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 14:7b:ac:00:xx:xx ip 10.18.220.234 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 40:55:82:a1:xx:xx ip 10.18.199.129 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 00:1c:7f:a3:xx:xx ip 10.30.194.50 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 70:d3:79:1a:xx:xx ip 10.18.220.238 [13904] 2024-07-26 15:24:42 debug store_arp - device 10.18.165.188 mac 70:d3:79:1a:xx:xx ip 10.18.199.134 [13904] 2024-07-26 15:24:42 debug [10.18.165.188] arpnip - processed 8 ARP Cache entries [13904] 2024-07-26 15:24:42 debug [10.18.165.188] arpnip - processed 0 IPv6 Neighbor Cache entries So I suspect the trouble is related to the SDWAN features or a specific release? Generally the more virutalization and software defined doohickeys a platform has the less likely it is to cough up all arp entries via SNMP. If you need to make an SSH Collector for IOS-XE SDWAN, you best figure out first what commands are needed, then copy an existing one an make it work. Many already do something like enumerate all contexts/vrf/vdoms and then run commands for each, you can look at e.g. CPVSX, ASAContext or FortiOS. Good luck Christian > > Sorry if its been asked before .. but im finding lately due to the > environment getting complex I wouldn’t mind how the whole arp storing > works and getting more things to work better . > > Muris > > > > _______________________________________________ > Netdisco mailing list > net...@li...<mailto:net...@li...> > 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 _______________________________________________ Netdisco mailing list net...@li...<mailto:net...@li...> https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
From: Jethro B. <jet...@st...> - 2024-07-30 15:25:13
|
Hi again Muris, I installed this and it worked fine and seemed to give some reasonable results back. You could add it to https://github.com/netdisco/netdisco/wiki/Custom-Reports perhaps, or I could do that for you? Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks, Network Manager, Information Services Directorate, University Of Strathclyde, Glasgow, UK The University of Strathclyde is a charitable body, registered in Scotland, number SC015263. ________________________________ From: Muris <alc...@gm...> Sent: 30 July 2024 15:24 To: net...@li... <net...@li...> Subject: [Netdisco] Addon report - what devices subnets are configured Hi all, I made an addon report for showing what subnets are configured on which devices with their descriptions and vlan ids. This only works well considering the devices pull all the information in the “Addresses” tab in netdisco user interface. I had some issues with Nexus MPLS devices, where the vlans don’t fully show under the “Addresses” tab so if netdisco doesn’t see the subnets it won’t capture everything (hoping that will be fixed one day) If you would like to trial it - Modify the deployment.yml file, find “reports:” on bottom then add it underneath - tag: SubnetsConfiguredOnDevices category: IP label: 'Subnets Configured on Devices' columns: - {Subnet: 'Subnet'} - {Description: 'Description'} - {VLANID: 'VLAN ID'} - {DeviceNameConfigured: 'Device Name Configured'} query: | SELECT DISTINCT CAST(s.net AS TEXT) AS Subnet, dp.name AS Description, COALESCE(dp.vlan, di.port) AS VLANID, d.name AS DeviceNameConfigured FROM subnets s JOIN device_ip di ON s.net = di.subnet JOIN device d ON di.ip = d.ip JOIN device_port dp ON di.ip = dp.ip AND dp.port LIKE '%lan%' AND dp.port = di.port WHERE s.net IS NOT NULL ORDER BY Subnet, Description, VLANID, DeviceNameConfigured |