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: SNMPv3 issue in Netdisco1 (Muris)
2. Netdisco2 sometimes misses connected hosts data & SSH
Collector (Muris)
--- Begin Message ---
Thanks Jeroen, I have them running in parallel, in v2 it works fine. I will
look to moving everything to v2.
On 22/6/17, 4:23 pm, "Jeroen van Ingen" <[email protected]> wrote:
Hi Muris,
I'm not sure how I can explain this best, but I'll give it a try:
SNMPv3 defines mechanisms for secure interaction between an SNMP agent
and an SNMP manager, and the SNMP objects that are added for SNMPv3 are
only the ones that are needed to configure those mechanisms, and to
collect statistics about those mechanisms.
SNMPv3 doesn't affect existing SNMP objects, it's only about the way to
retrieve them in a secure way. For example: IF-MIB::ifTable has the same
OID, doesn't matter if it's pulled via SNMPv2 or SNMPv3.
Similar to IF-MIB, SNMPv2-MIB also defines commonly used objects; from
the top of my head, SNMPv2-MIB is the successor to RFC1213-MIB, and both
contain the "system" group with objects like sysDescr, sysContact,
sysServices, etcetera. These are objects that Netdisco needs to retrieve
first; doesn't matter if the transport is SNMPv1, SNMPv2 or SNMPv3 (and
yes, the objects in SNMPv2-MIB are accessible over SNMPv1 transport as
well).
Looking at the output you've given, Netdisco actually did try connecting
to the device using SNMPv3: there's a '3' in the create_device() line
signifying that SNMPv3 is used, and the error that you get
(authorizationError) is only seen with SNMPv3.
Can't tell you what the root cause for this issue is; might be that the
SNMPv3 config on your device doesn't match what you've configured in
Netdisco, or could be something else; we've had a few small bugs wrt
SNMPv3 support in Netdisco or in SNMP::Info iirc.
Netdisco 1 isn't maintained anymore; I strongly suggest that you upgrade
to Netdisco 2. No known SNMPv3 bugs there, and more people that may be
willing to help you troubleshoot.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 06/22/2017 05:04 AM, Muris wrote:
> Hi,
>
> I am running Netdisco 1 on an older install, and trying to use SNMPv3 to
> get data from a device, and even forced it to grab data using SNMPv3..
> however even its forced on snmpv3, for some reason the SNMPv2 MIB spits
> out an error, any ideas? Why isnt it going to the SNMPv3 MIB?
>
> In netdisco v2.0 it works fine, but 1.0 cant get it working, comes up
> with authorisation error on v1.
>
> netdisco -D -d 10.x.x.x
> n e t d i s c o
> --------------------------------------------------
> Using Config File : /usr/share/netdisco/netdisco.conf
> Loading topology information from
/usr/share/netdisco/netdisco-topology.txt
> 3 entries loaded
> [10.x.x.x] Discover starting
> get_device(10.x.x.x)
> ! [10.x.x.x] Forcing SNMPv3 by config file.
> ! [10.x.x.x] Forcing SNMPv3 by config file.
> create_device(10.x.x.x,s,3*,AutoSpecify,bw:default)
> SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 :
.1.3.6.1.2.1.1.7.0
> SNMP::Info::_global(layers) authorizationError (access denied to that
> object) at /usr/sbin/netdisco line 1359
> SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
> .1.3.6.1.2.1.1.1.0
> SNMP::Info::_global(description) authorizationError (access denied to
> that object) at /usr/sbin/netdisco line 1359
> SNMP::Info::specify() - Could not get info from device at
> /usr/sbin/netdisco line 1359
> Can't connect to 10.x.x.x
> ! Device Not Supported or I can't connect to it via SNMP.
>
--- End Message ---
--- Begin Message ---
Hi All,
I would like to say thanks to the person who came up with the SSH Collector
for Nexus/ASA devices its really awesome and working well. Can it also
connect via telnet ?
I have come up with a problem, as i have around 3000 devices, for some
reason the macksuck and arp, on the automatic arpnips/walks dont fully
populate the data for a switch, when i go into the switch some ports show
up but blanks next to them on connected devices..
However, if i manually force a discover/arpnip/macwalk through the
webinterface the data populates straight away.
Is there any reason for this? How can it completely do it automated without
me refreshing a device manually? (Well the netdisco-backend should be doing
it but some reason some data dissapears when displayed)
I was thinking the SSH Collector of arps maybe could be conflicting with
netdisco arps to populate data...not sure..but at the moment needing the
ssh collector due to mpls and nexus with vrfs etc.
To cater for this many devices, i have 8 CPUs set on a Xeon machine with
16gb ram, and running the backend worker on AUTO * 4 in deployment config.
Postgresql is optimised with pgtune, and running latest netdisco version
released 22/06/17
Any troubleshooting/recommendations would be appreciated :)
Thankyou, Muris
--- 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
