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: Aerohive mibs (Oliver Gorwits)
2. Re: IP Inventory not working properly (Oliver Gorwits)
3. Re: Switches with empty os_ver fields (Andy Ruhl)
--- Begin Message ---
Hi Scott
On 2017-07-19 01:40, Golden, Scott wrote:
in info it does not see recognize them as aerohive
The output of this command for one of the APs will allow me to get
things working:
snmpwalk -v 2c -c {community} -ObentU {device} .1
thanks,
oliver.
no vendor/model
no os/version
but in description
AP550, HiveOS 8.0r1 build-161337
and nothing for layers
also nothing about it being wifi AP
SCOTT GOLDEN
Systems Analyst
Boston Globe Media Partners, LLC
978-340-8207
[email protected]
On Wed, Jul 12, 2017 at 8:17 AM,
<[email protected]> wrote:
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 [3]
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: Juniper devices about 14.x and higher have blank os_ver
(Andy Ruhl)
2. Re: aerohive AP mibs (Oliver Gorwits)
---------- Forwarded message ----------
From: Andy Ruhl <[email protected]>
To: "[email protected]"
<[email protected]>
Cc:
Bcc:
Date: Tue, 11 Jul 2017 16:09:31 -0700
Subject: Re: [Netdisco] Juniper devices about 14.x and higher have
blank os_ver
This is solved. It also fixed on EX8xxx switches the trailing comma
in
the os_ver entry, which shouldn't be there.
Thanks.
Andy
On Tue, Jul 11, 2017 at 1:04 PM, Oliver Gorwits <[email protected]>
wrote:
Hi Andy,
On 2017-07-11 17:36, Andy Ruhl wrote:
Ok, that was it.
There is no version info in description(). It's in
lldp_sysdesc().
Thanks for that report. I've pushed version 3.37 of SNMP::Info to
CPAN. Let
me know how it turns out.
regards,
oliver.
The regexp you're using for description() should be moved to
lldp_sysdesc().
I edited Juniper.pm and did a discovery and it worked (it
populated
the os_ver field), but I'm not sure if it's going to break other
stuff
so I changed it back.
Here's the raw data:
SNMP::Info::_global lldp_sysdesc : LLDP-MIB::lldpLocSysDesc.0 :
.1.0.8802.1.1.2.1.3.4.0
"Juniper Networks, Inc. ex4500-40f , version 12.3R12.4 Build
date:
2016-01-20 05:53:00 UTC "
SNMP::Info::_global lldp_sysdesc : LLDP-MIB::lldpLocSysDesc.0 :
.1.0.8802.1.1.2.1.3.4.0
"Juniper Networks, Inc. ex4500-40f Ethernet Switch, kernel JUNOS
15.1R5.5, Build date: 2016-11-25 16:33:55 UTC Copyright (c)
1996-2016
Juniper Networks, Inc."
Shall I open a bug?
Andy
On Tue, Jul 11, 2017 at 7:20 AM, Oliver Gorwits
<[email protected]> wrote:
Hi Andy
I suspect that the regular expressions and assumptions in the
SNMP::Info
Juniper module are not matching on your device:
https://metacpan.org/source/OLIVER/SNMP-Info-3.36/lib/SNMP/Info/Layer3/Juniper.pm#L109
[4]
You could try the following Netdisco commands to get the two
description
fields and make an assessment:
~netdisco/bin/netdisco-do show -DI -d 1.2.3.4 -e description
~netdisco/bin/netdisco-do show -DI -d 1.2.3.4 -e lldp_sysdesc
(this assumes the device is recognised as a Juniper, which you
can
confirm
in the Device Class field shown in Netdisco Device => Details
tab)
regards,
Oliver.
On 2017-07-11 14:34, Andy Ruhl wrote:
I've been upgrading Juniper devices, and I noticed that their
os_ver
is blank in versions 14.x and higher.
I'm not much of an SNMP person, so if someone could point me
in the
right direction to find out if there is something I can do, I
would
appreciate it.
Stuff I've done:
Used -DISQ with discover on an older and newer device and
looked at
the output but I can't find anything specific.
Did snmpbulkwalk on both devices and looked in the output and
I see
different strings for the version but I don't know what this
means.
Found MIBs from the current version of a device and put them
in
netdisco-mibs/juniper but it didn't make any difference.
If I knew what to look for maybe I could figure this out. And
also
figure out another device that has a blank os_ver that nobody
cares
about probably.
Andy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's
most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[2]
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
[3]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
---------- Forwarded message ----------
From: Oliver Gorwits <[email protected]>
To: [email protected]
Cc:
Bcc:
Date: Wed, 12 Jul 2017 12:07:44 +0100
Subject: Re: [Netdisco] aerohive AP mibs
Hi Scott
On 2017-07-08 04:18, Golden, Scott wrote:
i have aerohive AP's
when i try to discover them i dont see that that netdiscoo see;s
them
as aerohive
This hasn't been ignored! I did a quick check over of the updated
MIBs and in fact there isn't much difference! Nevertheless I'll
import them when I get a moment.
We may be missing something in SNMP::Info Perl module, then. I have
some Aerohive in production I can take a look at. What do you mean
by "not seeing"?
regards,
oliver.
SCOTT GOLDEN
Systems Analyst
Boston Globe Media Partners, LLC
978-340-8207 [1]
[email protected]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [2]
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
Links:
------
[1] tel:978-340-8207
[2] http://sdm.link/slashdot
[3] https://lists.sourceforge.net/lists/listinfo/netdisco-users
[4]
https://metacpan.org/source/OLIVER/SNMP-Info-3.36/lib/SNMP/Info/Layer3/Juniper.pm#L109
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Sebastian
On 2018-01-12 16:15, Sebastian Rösch wrote:
I generated a subnet inventory report. I found at least one address,
that is not shown, though it is in use.
In order to look into this further, can you send some more details such
as:
- the IP you are missing
- the settings each of the sidebar fields
- the full URL in the browser window after searching
Many thanks,
oliver.
I can also find it in the
nodes table, and it is active. How can this be? In this report there
aren´t also shown all ip addresses, if I select "List IP´s Never
Seen".
Today I updated netdisco to the most current version 2.38.9, but that
doesn´t change anything.
Any ideas, what´s wrong here?
Thanks,
Sebastian
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Yeah, I see the os version in this output multiple times.
Let me know if there is anything else I can do.
Andy
On Sat, Mar 17, 2018 at 7:59 AM, Oliver Gorwits <[email protected]> wrote:
> 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 <[email protected]> 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 <[email protected]> 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
>>>>>> [email protected]
>>>>>> 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
>>>>> [email protected]
>>>>> 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
>>>> [email protected]
>>>> 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
>>> [email protected]
>>> 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
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
