Send netdisco-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:

   1. Re: No snmpv3 connection even configured (Nick Nauwelaerts)
   2. Re: No snmpv3 connection even configured (?ern? Lubom?r (UNP-RPA))
--- Begin Message ---
since you're running a recent release i would advise to change to a device_auth 
config
(also see https://github.com/netdisco/netdisco/wiki/Release-Notes#2-041002)

the config in general can be very pickup about spaces & quotes, i've adapted my 
working config with your info:

device_auth:
  - tag: 'SNMPv3Test'
    user: 'userv3'
    auth:
      pass: 'Password*Tst'
      proto: 'SHA'
    priv:
      pass: 'Password*Tst'
      proto: 'AES'
    read: true
    write: false

if that doesn't solve the issue i would be interested what the following config 
does, do change the ip list to what your network requires.


host_groups:
  v3hosts_sha_aes:
    - 10.1.1.1
    - 10.1.1.2
    - 10.10.0.0/16

device_auth:
  - tag: 'SNMPv3Test'
    only: 'group:v3hosts_sha_aes'
    user: 'userv3'
    auth:
      pass: 'Password*Tst'
      proto: 'SHA'
    priv:
      pass: 'Password*Tst'
      proto: 'AES'
    read: true
    write: false



if none of that works deleting & rediscovering the device could provide a 
solution, but that also looses quite some history, so we would first try to 
troubleshoot this issue without resorting to delete&rediscover.


// nick



From: Černý Lubomír (UNP-RPA) [mailto:[email protected]]
Sent: Wednesday, April 3, 2019 13:03
To: '[email protected]' 
<[email protected]>
Subject: [Netdisco] No snmpv3 connection even configured

Hi.
We switched from snmpv2 to v3. Config is in place but discover proces did not 
even try to use v3. Only v1 and v2:
Discover proces tries several v2 communities but did not use v3 conection.

----------- Config:
# SNMP community string(s)
# ````````````````````````
snmp_auth:
snmpforce_v3:
   - tag: 'SNMPv3Test'
     user: userv3
     auth:
       pass: 'Password*Tst'
       proto: SHA
     priv:
       pass: 'Password*Tst'
       proto: AES
     read: true
     write: false


---------- CLI output:

netdisco@netdisco:~/bin$ ./netdisco-do -d 10.240.6.20 discover -D
[8019] 2019-04-03 10:52:38  info App::Netdisco version 2.042004 loaded.
[8019] 2019-04-03 10:52:38  info discover: [10.240.6.20] started at Wed Apr  3 
12:52:38 2019
[8019] 2019-04-03 10:52:38 debug discover: running with timeout 600s
[8019] 2019-04-03 10:52:38 debug => running workers for phase: check
[8019] 2019-04-03 10:52:38 debug -> run worker check/_base_/0
[8019] 2019-04-03 10:52:38 debug Discover is able to run.
[8019] 2019-04-03 10:52:38 debug => running workers for phase: early
[8019] 2019-04-03 10:52:38 debug -> run worker early/properties/100
[8019] 2019-04-03 10:52:38 debug snmp reader cache warm: [10.240.6.20]
[8019] 2019-04-03 10:52:38 debug [10.240.6.20:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:41 debug [10.240.6.20:161] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:44 debug [10.240.6.20:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:47 debug [10.240.6.20:161] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:50 debug [10.240.6.20:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:53 debug [10.240.6.20:161] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:56 debug discover failed: could not SNMP connect to 
10.240.6.20

Any idea, please ?

eL.

________________________________

Volg Aquafin op Facebook<https://www.facebook.com/AquafinNV> | 
Twitter<https://twitter.com/aquafinnv> | 
YouTube<http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?feature=mhee> | 
LinkedIN<http://www.linkedin.com/company/aquafin/products> | 
Instagram<https://www.instagram.com/aquafin_nv/>

In het kader van de uitoefening van onze taken verzamelen we bij Aquafin 
persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de 
betrokkenen zijn, kan je nalezen in onze privacy 
policy<https://www.aquafin.be/nl-be/privacy-policy>.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

--- End Message ---
--- Begin Message ---
Hi.
Section name change to device_auth: was the issue. Now works.

Thanks a lot !

eL.

From: Nick Nauwelaerts <[email protected]>
Sent: Wednesday, April 3, 2019 3:02 PM
To: Černý Lubomír (UNP-RPA) <[email protected]>; 
'[email protected]' <[email protected]>
Subject: RE: No snmpv3 connection even configured

since you're running a recent release i would advise to change to a device_auth 
config
(also see https://github.com/netdisco/netdisco/wiki/Release-Notes#2-041002)

the config in general can be very pickup about spaces & quotes, i've adapted my 
working config with your info:

device_auth:
  - tag: 'SNMPv3Test'
    user: 'userv3'
    auth:
      pass: 'Password*Tst'
      proto: 'SHA'
    priv:
      pass: 'Password*Tst'
      proto: 'AES'
    read: true
    write: false

if that doesn't solve the issue i would be interested what the following config 
does, do change the ip list to what your network requires.


host_groups:
  v3hosts_sha_aes:
    - 10.1.1.1
    - 10.1.1.2
    - 10.10.0.0/16

device_auth:
  - tag: 'SNMPv3Test'
    only: 'group:v3hosts_sha_aes'
    user: 'userv3'
    auth:
      pass: 'Password*Tst'
      proto: 'SHA'
    priv:
      pass: 'Password*Tst'
      proto: 'AES'
    read: true
    write: false



if none of that works deleting & rediscovering the device could provide a 
solution, but that also looses quite some history, so we would first try to 
troubleshoot this issue without resorting to delete&rediscover.


// nick



From: Černý Lubomír (UNP-RPA) [mailto:[email protected]]
Sent: Wednesday, April 3, 2019 13:03
To: '[email protected]' 
<[email protected]<mailto:[email protected]>>
Subject: [Netdisco] No snmpv3 connection even configured

Hi.
We switched from snmpv2 to v3. Config is in place but discover proces did not 
even try to use v3. Only v1 and v2:
Discover proces tries several v2 communities but did not use v3 conection.

----------- Config:
# SNMP community string(s)
# ````````````````````````
snmp_auth:
snmpforce_v3:
   - tag: 'SNMPv3Test'
     user: userv3
     auth:
       pass: 'Password*Tst'
       proto: SHA
     priv:
       pass: 'Password*Tst'
       proto: AES
     read: true
     write: false


---------- CLI output:

netdisco@netdisco:~/bin$ ./netdisco-do -d 10.240.6.20 discover -D
[8019] 2019-04-03 10:52:38  info App::Netdisco version 2.042004 loaded.
[8019] 2019-04-03 10:52:38  info discover: [10.240.6.20] started at Wed Apr  3 
12:52:38 2019
[8019] 2019-04-03 10:52:38 debug discover: running with timeout 600s
[8019] 2019-04-03 10:52:38 debug => running workers for phase: check
[8019] 2019-04-03 10:52:38 debug -> run worker check/_base_/0
[8019] 2019-04-03 10:52:38 debug Discover is able to run.
[8019] 2019-04-03 10:52:38 debug => running workers for phase: early
[8019] 2019-04-03 10:52:38 debug -> run worker early/properties/100
[8019] 2019-04-03 10:52:38 debug snmp reader cache warm: [10.240.6.20]
[8019] 2019-04-03 10:52:38 debug [10.240.6.20:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:41 debug [10.240.6.20:161] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:44 debug [10.240.6.20:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:47 debug [10.240.6.20:161] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:50 debug [10.240.6.20:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:53 debug [10.240.6.20:161] try_connect with ver: 1, 
class: SNMP::Info, comm: <hidden>
[8019] 2019-04-03 10:52:56 debug discover failed: could not SNMP connect to 
10.240.6.20

Any idea, please ?

eL.

________________________________

Volg Aquafin op Facebook<https://www.facebook.com/AquafinNV> | 
Twitter<https://twitter.com/aquafinnv> | 
YouTube<http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?feature=mhee> | 
LinkedIN<http://www.linkedin.com/company/aquafin/products> | 
Instagram<https://www.instagram.com/aquafin_nv/>

In het kader van de uitoefening van onze taken verzamelen we bij Aquafin 
persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de 
betrokkenen zijn, kan je nalezen in onze privacy 
policy<https://www.aquafin.be/nl-be/privacy-policy>.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to