Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
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
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: SNMPv3 help (Oliver Gorwits)
2. Re: SNMPv3 help (Socheat Sann)
3. Re: SNMPv3 help (Oliver Gorwits)
4. Ubiquiti EdgeRouter (Bernhard Marker)
5. Netdisco an VRF's (Sassan Dibadj)
--- Begin Message ---
Hi Socheat
On 2017-02-07 15:48, Socheat Sann wrote:
I recently force to upgrade all my network switches from SNMPv2 to
SNMPv3.
I been using Netdisco2 for a while and everything was running perfect
on SNMPv2 but not can't get Netdisco to connect to switches via
SNMPv3.
Your config looks okay. Can you please try putting the two passwords in
quotes, such as "$nMp34sw1tch3s!" ?
Also run netdisco-do with -D so it shows the Netdisco user matched. If
you are familiar with Perl you could try editing
lib/App/Netdisco/Util/SNMP.pm to debug as well.
regards,
Oliver.
I have combed the web and tried various thing before I reach out to
this mail group so any help is appreciated.
I verified my snmpv3 settings on my switches is correct. I tested by
doing snmpwalk from the same server netdisco is host on and it connect
and pull data fine. I also verified via another app (Solarwind
toolset).
I read the config manual multiple times and here is my setting in the
deployment.yml file:
# SNMP community string(s)
# ````````````````````````
snmp_auth:
- tag: Snmpv3cfg
user: NETDUSERV3
auth:
pass: $nMp34sw1tch3s!
proto: SHA
priv:
pass: $nMp34swEnCry!
proto: AES
I enabled logging when test via netdisco-do and see this flag which I
think may be the issue but I don't know why since I stated I'm using
Auth and Priv in the config file. Why is it flagging my sec level as
no Auth and no Priv.
snmp_build: Building SNMPv3 message (secName:"NETDUSERV3",
secLevel:noAuthNoPriv)...
[3512] 2017-02-07 15:17:16 info discover: finished at Tue Feb 7
10:17:16 2017
[3512] 2017-02-07 15:17:16 info discover: status error: discover
failed: could not SNMP connect to 192.168.99.18
-bash-4.1$
My server info:
Red Hat Enterprise Linux Server release 6.8 (Santiago)
Software Version App::Netdisco 2.034001
DB Schema v41
Dancer 1.3202
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by
GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17), 64-bit.DBI 1.633,
DBD::Pg 2.15.1
SNMP::Info 3.34
Perl 5.010001
Attached is the full debug.
Any help is appreciated.
Thank you,
-So
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
You are the man Oliver!
It works now. Apparently it did not like the special character in the
password portion. Not sure if that a bug with net-snmp or just the fact
for special characters, it need to be in quotes.
I validate by testing via manual snmpwalk. I had to put the password in
quotes as well there to get it working.
Just a FYI, here is the error when I do snmpwalk when I didn't put the
passwords in quotes:
Error: passphrase chosen is below the length requirements of the USM
(min=8).
snmpwalk: (The supplied password length is too short.)
Error generating a key (Ku) from the supplied authentication pass phrase.
Obviously my password length is not too short. If i put the passwords
portion in quotes, it went through.
Thanks again for pointing me in the right direction. Can't believe it was
something as simple as a quotes.
-So
On Tue, Feb 7, 2017 at 11:20 AM, Oliver Gorwits <oli...@cpan.org> wrote:
> Hi Socheat
>
> On 2017-02-07 15:48, Socheat Sann wrote:
> > I recently force to upgrade all my network switches from SNMPv2 to
> > SNMPv3.
> > I been using Netdisco2 for a while and everything was running perfect
> > on SNMPv2 but not can't get Netdisco to connect to switches via
> > SNMPv3.
>
> Your config looks okay. Can you please try putting the two passwords in
> quotes, such as "$nMp34sw1tch3s!" ?
>
> Also run netdisco-do with -D so it shows the Netdisco user matched. If
> you are familiar with Perl you could try editing
> lib/App/Netdisco/Util/SNMP.pm to debug as well.
>
> regards,
> Oliver.
>
> > I have combed the web and tried various thing before I reach out to
> > this mail group so any help is appreciated.
> >
> > I verified my snmpv3 settings on my switches is correct. I tested by
> > doing snmpwalk from the same server netdisco is host on and it connect
> > and pull data fine. I also verified via another app (Solarwind
> > toolset).
> >
> > I read the config manual multiple times and here is my setting in the
> > deployment.yml file:
> >
> > # SNMP community string(s)
> > # ````````````````````````
> > snmp_auth:
> > - tag: Snmpv3cfg
> > user: NETDUSERV3
> > auth:
> > pass: $nMp34sw1tch3s!
> > proto: SHA
> > priv:
> > pass: $nMp34swEnCry!
> > proto: AES
> >
> > I enabled logging when test via netdisco-do and see this flag which I
> > think may be the issue but I don't know why since I stated I'm using
> > Auth and Priv in the config file. Why is it flagging my sec level as
> > no Auth and no Priv.
> >
> > snmp_build: Building SNMPv3 message (secName:"NETDUSERV3",
> > secLevel:noAuthNoPriv)...
> >
> > [3512] 2017-02-07 15:17:16 info discover: finished at Tue Feb 7
> > 10:17:16 2017
> > [3512] 2017-02-07 15:17:16 info discover: status error: discover
> > failed: could not SNMP connect to 192.168.99.18
> > -bash-4.1$
> >
> > My server info:
> >
> > Red Hat Enterprise Linux Server release 6.8 (Santiago)
> >
> > Software Version App::Netdisco 2.034001
> > DB Schema v41
> > Dancer 1.3202
> > Bootstrap 2.3.1
> > PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by
> > GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17), 64-bit.DBI 1.633,
> > DBD::Pg 2.15.1
> > SNMP::Info 3.34
> > Perl 5.010001
> >
> > Attached is the full debug.
> >
> > Any help is appreciated.
> >
> > Thank you,
> >
> > -So
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> >
> > _______________________________________________
> > Netdisco mailing list
> > netdisco-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
--- Begin Message ---
On 2017-02-07 17:32, Socheat Sann wrote:
You are the man Oliver!
It works now. Apparently it did not like the special character in
the password portion. Not sure if that a bug with net-snmp or just
the fact for special characters, it need to be in quotes.
Thanks for letting us know, I'm glad it's working.
To be fair to you, we should have mentioned this in the docs. I will add
it to the next release.
regards,
oliver.
I validate by testing via manual snmpwalk. I had to put the password
in quotes as well there to get it working.
Just a FYI, here is the error when I do snmpwalk when I didn't put the
passwords in quotes:
Error: passphrase chosen is below the length requirements of the USM
(min=8).
snmpwalk: (The supplied password length is too short.)
Error generating a key (Ku) from the supplied authentication pass
phrase.
Obviously my password length is not too short. If i put the
passwords portion in quotes, it went through.
Thanks again for pointing me in the right direction. Can't believe
it was something as simple as a quotes.
-So
On Tue, Feb 7, 2017 at 11:20 AM, Oliver Gorwits <oli...@cpan.org>
wrote:
Hi Socheat
On 2017-02-07 15:48, Socheat Sann wrote:
I recently force to upgrade all my network switches from SNMPv2
to
SNMPv3.
I been using Netdisco2 for a while and everything was running
perfect
on SNMPv2 but not can't get Netdisco to connect to switches via
SNMPv3.
Your config looks okay. Can you please try putting the two
passwords in
quotes, such as "$nMp34sw1tch3s!" ?
Also run netdisco-do with -D so it shows the Netdisco user matched.
If
you are familiar with Perl you could try editing
lib/App/Netdisco/Util/SNMP.pm to debug as well.
regards,
Oliver.
I have combed the web and tried various thing before I reach out
to
this mail group so any help is appreciated.
I verified my snmpv3 settings on my switches is correct. I tested
by
doing snmpwalk from the same server netdisco is host on and it
connect
and pull data fine. I also verified via another app (Solarwind
toolset).
I read the config manual multiple times and here is my setting in
the
deployment.yml file:
# SNMP community string(s)
# ````````````````````````
snmp_auth:
- tag: Snmpv3cfg
user: NETDUSERV3
auth:
pass: $nMp34sw1tch3s!
proto: SHA
priv:
pass: $nMp34swEnCry!
proto: AES
I enabled logging when test via netdisco-do and see this flag
which I
think may be the issue but I don't know why since I stated I'm
using
Auth and Priv in the config file. Why is it flagging my sec
level as
no Auth and no Priv.
snmp_build: Building SNMPv3 message (secName:"NETDUSERV3",
secLevel:noAuthNoPriv)...
[3512] 2017-02-07 15:17:16 info discover: finished at Tue Feb
7
10:17:16 2017
[3512] 2017-02-07 15:17:16 info discover: status error:
discover
failed: could not SNMP connect to 192.168.99.18
-bash-4.1$
My server info:
Red Hat Enterprise Linux Server release 6.8 (Santiago)
Software Version App::Netdisco 2.034001
DB Schema v41
Dancer 1.3202
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu,
compiled by
GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17), 64-bit.DBI
1.633,
DBD::Pg 2.15.1
SNMP::Info 3.34
Perl 5.010001
Attached is the full debug.
Any help is appreciated.
Thank you,
-So
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot [1]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users [2]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot [1]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users [2]
Links:
------
[1] http://sdm.link/slashdot
[2] https://lists.sourceforge.net/lists/listinfo/netdisco-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi,
Is it possible to add new Ubiquiti Devices?
Like EdgeRouter X,X-sfp or EdgePoint R6,R8.
This Devices have Layer3 support, and atm in NetDisco2 the compatible devices
from Ubiquiti are only Accesspoints (L2).
Thank you very much.
BR
Bernhard
--- End Message ---
--- Begin Message ---
We are currently transitioning to having two main VRF's for our network here
and since about November netdisco is no longer pulling IP arp information on
the non-default VRF.
I did some research and added as second context along with a second community
name and I am able to pull the second VRF's IP's via snmpwalk when querying the
other community name.
I updated the netdisco deployment.yml to include the new community name and
even tried making it the first one it tries but it seems like I still only get
back IP ARP information on the default VRF.
We are running Cisco 7k Nexus platform and this is what I added to the cores.
snmp-server context clinical vrf clinical
snmp-server community xxxxxxxx ro
snmp-server mib community-map xxxxxx context clinical
SNMP walk I was using is below. If I use the regular community name it pulls
the default VRF's ARP and if I change it to the new community name it pulls the
non-default VRF's IP's.
snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
Is there something I can do to make netdisco pull this info again?
Thank you,
________________________________
UT Southwestern
Medical Center
The future of medicine, today.
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
