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: Multiple Neighbors to a Single Interface? (Oliver Gorwits)
2. Re: appropriate SNMPv3 view (Oliver Gorwits)
3. Re: appropriate SNMPv3 view (Eric W. Bates)
4. Re: appropriate SNMPv3 view (Oliver Gorwits)
5. Re: Switches with empty os_ver fields (Oliver Gorwits)
--- Begin Message ---
Hi Jason
On 2018-03-12 20:51, Jason Garrett wrote:
It
appears NetDisco only allows you have a device and a corresponding
interface 1 time as the Left Device and 1 time as the Right device. Is
that true?
Yes this is true.
The workaround we have is the creation of a "pseudo device" in Netdisco
which acts as your VPN cloud. This works well if your network is fairly
static, as after setting it up there's not a lot to do.
Go into Admin menu and select Pseudo Devices. Create one with enough
ports to cover all your sites. Connect site devices to the pseudo device
ports.
I hope this helps,
regards,
oliver.
Thanks!
Jason Garrett
Diocese of Lincoln Schools
Education Technology: (402) 473-0600
Email: jason-garr...@cdolinc.net
------------------------------------------------------------------------------
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://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Eric
On 2018-03-09 00:39, Eric W. Bates wrote:
We're trying to deploy a more secure SNMP and to that end we're
implementing SNMP v3.
Part of the standard definition for SNMP v3 is the use of a view.
My (somewhat feeble) understanding of SNMP views is that they act as an
internal ACL to the device but are not something the managing agent
(Netdisco) needs to know about. The view (ACL) says what MIBs are
available for a given username/credential set.
(in SNMPv3 there are also contexts, which are a different thing)
So you need to assign the view (VIEW_WHOI) to the group used by the
username used by Netdisco.
Many examples exist in Google, such as:
snmp-server ifindex persist
snmp-server view VIEW_WHOI iso included
snmp-server group v3group v3 priv read VIEW_WHOI
snmp-server user v3user v3group v3 auth sha pass123 priv des56 pass456
Hope this helps?
regards,
oliver.
However, I can't find a list of acceptable "views" nor their contents.
Specifically, the problem today is netdisco's failure to pull the lldp
oid's:
SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 :
.1.0.8802.1.1.2.1.3.6.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(lldp_sys_cap) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discov
er.pm line 676.
SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId :
.1.0.8802.1.1.2.1.4.1.1.5
SNMP::Info::_global cdp_run : CISCO-CDP-MIB::cdpGlobalRun.0 :
.1.3.6.1.4.1.9.9.23.1.3.1.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(cdp_run) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm
line 676.
The view on the cisco I have is:
snmp-server view VIEW_WHOI internet included
snmp-server view VIEW_WHOI mib-2 included
snmp-server view VIEW_WHOI system included
snmp-server view VIEW_WHOI cisco included
But I'm really just guessing.
Is there a recommended view for netdisco?
Is there a list of view objects somewhere on line?
Is there a list of what MIB's these objects include?
Thanks.
--- End Message ---
--- Begin Message ---
On 03/17/2018 08:55 AM, Oliver Gorwits wrote:
Hi Eric
On 2018-03-09 00:39, Eric W. Bates wrote:
We're trying to deploy a more secure SNMP and to that end we're
implementing SNMP v3.
Part of the standard definition for SNMP v3 is the use of a view.
My (somewhat feeble) understanding of SNMP views is that they act as an
internal ACL to the device but are not something the managing agent
(Netdisco) needs to know about. The view (ACL) says what MIBs are
available for a given username/credential set.
(in SNMPv3 there are also contexts, which are a different thing)
So you need to assign the view (VIEW_WHOI) to the group used by the
username used by Netdisco.
Many examples exist in Google, such as:
snmp-server ifindex persist
snmp-server view VIEW_WHOI iso included
snmp-server group v3group v3 priv read VIEW_WHOI
snmp-server user v3user v3group v3 auth sha pass123 priv des56 pass456
Yah. We've gotten that far. The basic problem is that the LLDP oids
which netdisco wants to read to find neighbors is not encompassed by the
pre-defined cisco views named: "internet" "mib-2" "system" or "cisco"
So I need help either composing my own view (every attempt on the ciscos
has been rejected -- so this is really a cisco question); or identifying
a pre-defined view which already includes the LLDP oids.
I had hoped that another netdisco user had already worked this out.
Hope this helps?
regards,
oliver.
However, I can't find a list of acceptable "views" nor their contents.
Specifically, the problem today is netdisco's failure to pull the lldp
oid's:
SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 :
.1.0.8802.1.1.2.1.3.6.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(lldp_sys_cap) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discov
er.pm line 676.
SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId :
.1.0.8802.1.1.2.1.4.1.1.5
SNMP::Info::_global cdp_run : CISCO-CDP-MIB::cdpGlobalRun.0 :
.1.3.6.1.4.1.9.9.23.1.3.1.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(cdp_run) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm
line 676.
The view on the cisco I have is:
snmp-server view VIEW_WHOI internet included
snmp-server view VIEW_WHOI mib-2 included
snmp-server view VIEW_WHOI system included
snmp-server view VIEW_WHOI cisco included
But I'm really just guessing.
Is there a recommended view for netdisco?
Is there a list of view objects somewhere on line?
Is there a list of what MIB's these objects include?
Thanks.
------------------------------------------------------------------------------
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://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Eric
Oh I see. I think you can use a numeric OID in the view command, such
as:
snmp-server view VIEW_WHOI 1.0.8802.1.1.2 included
or even
snmp-server view VIEW_WHOI 1 included
(not sure if there needs to be a leading dot on the ID).
regards,
oliver.
On 2018-03-17 14:18, Eric W. Bates wrote:
On 03/17/2018 08:55 AM, Oliver Gorwits wrote:
Hi Eric
On 2018-03-09 00:39, Eric W. Bates wrote:
We're trying to deploy a more secure SNMP and to that end we're
implementing SNMP v3.
Part of the standard definition for SNMP v3 is the use of a view.
My (somewhat feeble) understanding of SNMP views is that they act as
an internal ACL to the device but are not something the managing agent
(Netdisco) needs to know about. The view (ACL) says what MIBs are
available for a given username/credential set.
(in SNMPv3 there are also contexts, which are a different thing)
So you need to assign the view (VIEW_WHOI) to the group used by the
username used by Netdisco.
Many examples exist in Google, such as:
snmp-server ifindex persist
snmp-server view VIEW_WHOI iso included
snmp-server group v3group v3 priv read VIEW_WHOI
snmp-server user v3user v3group v3 auth sha pass123 priv des56 pass456
Yah. We've gotten that far. The basic problem is that the LLDP oids
which netdisco wants to read to find neighbors is not encompassed by
the pre-defined cisco views named: "internet" "mib-2" "system" or
"cisco"
So I need help either composing my own view (every attempt on the
ciscos has been rejected -- so this is really a cisco question); or
identifying a pre-defined view which already includes the LLDP oids.
I had hoped that another netdisco user had already worked this out.
Hope this helps?
regards,
oliver.
However, I can't find a list of acceptable "views" nor their
contents.
Specifically, the problem today is netdisco's failure to pull the
lldp
oid's:
SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 :
.1.0.8802.1.1.2.1.3.6.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(lldp_sys_cap) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discov
er.pm line 676.
SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId :
.1.0.8802.1.1.2.1.4.1.1.5
SNMP::Info::_global cdp_run : CISCO-CDP-MIB::cdpGlobalRun.0 :
.1.3.6.1.4.1.9.9.23.1.3.1.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(cdp_run) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm
line 676.
The view on the cisco I have is:
snmp-server view VIEW_WHOI internet included
snmp-server view VIEW_WHOI mib-2 included
snmp-server view VIEW_WHOI system included
snmp-server view VIEW_WHOI cisco included
But I'm really just guessing.
Is there a recommended view for netdisco?
Is there a list of view objects somewhere on line?
Is there a list of what MIB's these objects include?
Thanks.
------------------------------------------------------------------------------
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://sourceforge.net/p/netdisco/mailman/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://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Andy
The output of this command will allow me to simulate the device and work
out the os/os_ver fields to use:
snmpwalk -v 2c -c {community} -ObentU {device} .1
thanks,
oliver.
On 2017-08-14 16:43, Andy Ruhl wrote:
I updated Netdisco, did netdisco-deploy, and restarted.
No change unfortunately.
The class for the G8264 is still this:
SNMP::Info::Layer3::IBMGbTor
I can get whatever info you need.
Thanks.
Andy
On Mon, Aug 14, 2017 at 8:17 AM, Oliver Gorwits <oli...@cpan.org>
wrote:
Hi Andy
I believe we have just updated Netdisco's MIB bundle for the G8264.
Please run netdisco-deploy and try a discover on the devices, and let
us
know how it goes.
regards,
oliver.
On 2017-07-12 16:24, Andy Ruhl wrote:
Ok. All are this class:
SNMP::Info::Layer3::IBMGbTor
I'm not 100% sure if that's correct, the non working 2 have MIBs that
have specific names:
GbTOR-G8264.mib
GbTOR-G8052.mib
These come with the firmware download for the switches.
Here's some data:
(G8124, good)
$ netdisco-do show -d x.x.x.19 -DI -e Layer3::IBMGbTor::os_ver
[3259] 2017-07-12 14:47:15 info show: started at Wed Jul 12 14:47:15
2017
[3259] 2017-07-12 14:47:15 debug [x.x.x.19] try_connect with ver: 2,
class: SNMP::Info::Layer3::IBMGbTor, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 :
.1.3.6.1.2.1.1.7.0
SNMP::Info::_global agSoftwareVersion :
IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0 :
.1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0
"7.11.10" <------------- BINGO
[3259] 2017-07-12 14:47:16 info show: finished at Wed Jul 12
14:47:16
2017
[3259] 2017-07-12 14:47:16 info show: status done: Showed os_ver
response from x.x.x.19.
(G8264, bad)
$ netdisco-do show -d x.x.x.18 -DI -e Layer3::IBMGbTor::os_ver
[3441] 2017-07-12 14:47:26 info show: started at Wed Jul 12 14:47:26
2017
[3441] 2017-07-12 14:47:26 debug [x.x.x.18] try_connect with ver: 2,
class: SNMP::Info::Layer3::IBMGbTor, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 :
.1.3.6.1.2.1.1.7.0
SNMP::Info::_global agSoftwareVersion :
IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0 :
.1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(agSoftwareVersion) NOSUCHOBJECT at
/home/netdisco/bin/netdisco-do line 142.
[3441] 2017-07-12 14:47:27 info show: finished at Wed Jul 12
14:47:27
2017
[3441] 2017-07-12 14:47:27 info show: status error: error running
job: When calling p() without prototypes, please pass arguments as
references at /home/netdisco/bin/netdisco-do line 142.
(G8052, bad)
$ netdisco-do show -d x.x.x.17 -DI -e Layer3::IBMGbTor::os_ver
[4825] 2017-07-12 15:18:45 info show: started at Wed Jul 12 15:18:45
2017
[4825] 2017-07-12 15:18:45 debug [x.x.x.17] try_connect with ver: 2,
class: SNMP::Info::Layer3::IBMGbTor, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 :
.1.3.6.1.2.1.1.7.0
SNMP::Info::_global agSoftwareVersion :
IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0 :
.1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(agSoftwareVersion) NOSUCHOBJECT at
/home/netdisco/bin/netdisco-do line 142.
[4825] 2017-07-12 15:18:45 info show: finished at Wed Jul 12
15:18:45
2017
[4825] 2017-07-12 15:18:45 info show: status error: error running
job: When calling p() without prototypes, please pass arguments as
references at /home/netdisco/bin/netdisco-do line 142.
I can keep working on this as long as I can figure it out.
Andy
On Wed, Jul 12, 2017 at 7:34 AM, Oliver Gorwits <oli...@cpan.org>
wrote:
Hi Andy,
On 2017-07-12 15:09, Andy Ruhl wrote:
Thanks for your help yesterday Oliver.
:-)
I have 2 switches that have always had blank os_ver fields.
Based on yesterday's troubleshooting, I tried the same stuff but
I'm
not getting anywhere.
I would start with the one which is working, and find the Device
Class
which
SNMP::Info is using: either from the device table in the database or
the
Device Class field shown in Device -> Details tab in the web.
Find the source file for that online somewhere here:
https://metacpan.org/release/SNMP-Info
Look for an os_ver() subroutine, and see what it's doing. Perhaps it
pulls
agSoftwareVersion which works for that model.
The other thing to do is check which Device Class the *not working*
devices
are being assigned. Hopefully the same as the working device.
If not, then it may be a case of updating the rules in SNMP/Info.pm
which
assign the Device Classes. You can force a device class for testing
(we
strip SNMP::Info from the front of the classname):
~netdisco/bin/netdisco-do show -d 1.2.3.4 -e Layer3::HP::os_ver
If the device class is correct for the not-working devices, then
it'll
probably be related to which SNMP leaf to get. As in the JUNOS
software
version example you had before, sometimes we need to fetch a couple
of
leaves and try them in turn.
regards,
oliver.
Here is some psql info:
model | vendor | os_ver
--------------+---------+---------------
G8052 | ibm |
G8264, Stack | ibm |
G8124-E | ibm | 7.11.10
The G8124-E is the only switch that has ever had a populated os_ver
field, it never worked for the others.
So I did discover with -DISQ and I don't see a version string
anywhere
in the output that looks like "7.11.10".
I did notice this for 8052 and 8264 devices:
SNMP::Info::_global(agSoftwareVersion) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line
186.
Any hints on how to continue for this one?
Thanks.
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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 ---
------------------------------------------------------------------------------
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
