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. SNMPv3 issue in Netdisco1 (Muris)
2. Re: SNMPv3 issue in Netdisco1 (Jeroen van Ingen)
3. Re: Cisco N5k Trunk VLANs not found for ports on FEX
(Jeroen van Ingen)
--- Begin Message ---
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 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 Christian,
Hmm, maybe it's a limitation or bug in the older NX-OS versions. It's
been ages since we ran a 5.x release so I don't remember if we ever had
this issue.
We currently run 6.0(2)N2(1) on the 5596's in one data center and
7.1(3)N1(2) on the 5596's in our other DC; both report VLAN membership
on trunks just fine.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 06/20/2017 12:09 PM, Christian Ramseyer wrote:
Hi guys
Given this setup:
204 Po204(SU) Eth LACP Eth106/1/7(P) Eth107/1/7(P)
*** # show fex 106 detail | include 1/7
Eth106/1/7 Up Po106
*** # show fex 107 detail | include 1/7
Eth107/1/7 Up Po107
interface port-channel204
description ***
switchport mode trunk
switchport trunk allowed vlan 461,475-476
Netdisco does not show anything in the VLAN Membership. The problem is
AFAICT Cisco-based, as the FEX ports are not included in VTP-MIB, e.g.
for vlanTrunkPortDynamicStatus:
interface: 369098955 port-channel204
.1.3.6.1.4.1.9.9.46.1.6.1.1.14.369098955 = No Such Instance currently
exists at this OID
Has anybody already noticed this or maybe even found a workaround? Our
N5k here still run 5.2(1)N1(9), but from the resolved issues in
5.2(1)N1(9a) and 5.2(1)N1(9b) it doesn't look like they would be any help.
Christian
------------------------------------------------------------------------------
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 ---
------------------------------------------------------------------------------
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
