netdisco-users Digest, Vol 118, Issue 3

Wed, 13 Apr 2016 06:42:35 -0700 

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. Adding ASA to ND2 (Nikolaos Milas)
   2. Re: Adding ASA to ND2 (Oliver Gorwits)
   3. Re: Adding ASA to ND2 (Nikolaos Milas)
   4. Re: Adding ASA to ND2 (Jeroen van Ingen)
   5. SNMP::Info::Layer3::Nexus serial is wrong (Thomas Wollner)
   6. Re: SNMP::Info::Layer3::Nexus serial is wrong (Thomas Wollner)
--- Begin Message --- 
Hello,

I'm trying to integrate a new ASA in our ND2.
I have managed to use ssh-collector successfully, but I can't find a way to add ASA to the inventory. Discover fails, although snmpwalk is successful (from the same server/account netdisco runs). 

Any advice? Am I doing something wrong?
(Note: Below I've changed real domain name to "example")

$ ~/bin/netdisco-do discover -D -d 195.251.204.233
[23963] 2016-04-10 07:29:53 info discover: started at Sun Apr 10 10:29:53 2016 [23963] 2016-04-10 07:29:53 debug [195.251.204.241] try_connect with ver: 2, class: SNMP::Info::Layer3::Cisco, comm: <hidden> [23963] 2016-04-10 07:30:09 debug [195.251.204.241] try_connect with ver: 2, class: SNMP::Info, comm: <hidden> [23963] 2016-04-10 07:30:13 debug [195.251.204.241] try_connect with ver: 1, class: SNMP::Info::Layer3::Cisco, comm: <hidden> [23963] 2016-04-10 07:30:16 debug [195.251.204.241] try_connect with ver: 1, class: SNMP::Info, comm: <hidden> [23963] 2016-04-10 07:30:19 debug [195.251.204.241] try_connect with ver: 2, class: SNMP::Info::Layer3::Cisco, comm: <hidden> [23963] 2016-04-10 07:30:22 debug [195.251.204.241] try_connect with ver: 2, class: SNMP::Info, comm: <hidden> [23963] 2016-04-10 07:30:25 debug [195.251.204.241] try_connect with ver: 1, class: SNMP::Info::Layer3::Cisco, comm: <hidden> [23963] 2016-04-10 07:30:28 debug [195.251.204.241] try_connect with ver: 1, class: SNMP::Info, comm: <hidden> [23963] 2016-04-10 07:30:31 info discover: finished at Sun Apr 10 10:30:31 2016 [23963] 2016-04-10 07:30:31 info discover: status error: discover failed: could not SNMP connect to 195.251.204.241 

$ snmpwalk -v 2c -c secretstring 195.251.204.233
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Adaptive Security Appliance Version 9.5(2) 
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1408
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (334636900) 38 days, 17:32:49.00 
SNMPv2-MIB::sysContact.0 = STRING: [email protected]
SNMPv2-MIB::sysName.0 = STRING: FW-PEN.private.example.gr
SNMPv2-MIB::sysLocation.0 = STRING: pen
SNMPv2-MIB::sysServices.0 = INTEGER: 4
IF-MIB::ifNumber.0 = INTEGER: 39
IF-MIB::ifIndex.2 = INTEGER: 2
...
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1 = STRING: "ASA 5525-X with SW, 8 GE Data, 1 GE Mgmt, AC" 
...

Thanks in advance,
Nick

--- End Message ---
--- Begin Message --- 
Hi Nick,
One thing to check is to run the Netdisco command again and confirm that the correct SNMP community is being picked up: 

SHOW_COMMUNITY=1 ~/bin/netdisco-do discover -D -d 195.251.204.233
You will see in the output that commd:<hidden> is changed to be your community string (or username for SNMPv3). 

regards,
oliver.

On 2016-04-10 11:55, Nikolaos Milas wrote:

Hello,

I'm trying to integrate a new ASA in our ND2.
I have managed to use ssh-collector successfully, but I can't find a way 
to add ASA to the inventory. Discover fails, although snmpwalk is
successful (from the same server/account netdisco runs).

Any advice? Am I doing something wrong?
(Note: Below I've changed real domain name to "example")

$ ~/bin/netdisco-do discover -D -d 195.251.204.233
[23963] 2016-04-10 07:29:53  info discover: started at Sun Apr 10
10:29:53 2016
[23963] 2016-04-10 07:29:53 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:09 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:13 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:16 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:19 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:22 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:25 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:28 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:31  info discover: finished at Sun Apr 10
10:30:31 2016
[23963] 2016-04-10 07:30:31  info discover: status error: discover
failed: could not SNMP connect to 195.251.204.241

$ snmpwalk -v 2c -c secretstring 195.251.204.233
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Adaptive Security Appliance
Version 9.5(2)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1408
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (334636900) 38 days,
17:32:49.00
SNMPv2-MIB::sysContact.0 = STRING: [email protected]
SNMPv2-MIB::sysName.0 = STRING: FW-PEN.private.example.gr
SNMPv2-MIB::sysLocation.0 = STRING: pen
SNMPv2-MIB::sysServices.0 = INTEGER: 4
IF-MIB::ifNumber.0 = INTEGER: 39
IF-MIB::ifIndex.2 = INTEGER: 2
...
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1 = STRING: "ASA 5525-X with SW, 8 GE
Data, 1 GE Mgmt, AC"
...

Thanks in advance,
Nick


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ 
gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

--- End Message ---
--- Begin Message --- 
On 11/4/2016 12:43 μμ, Oliver Gorwits wrote:


One thing to check is to run the Netdisco command again and confirm that
the correct SNMP community is being picked up:
...


Thank you Oliver,
I checked and yes, the correct community string is being used. However, discovery does not work. 

Any other ideas?

Nick

--- End Message ---
--- Begin Message --- 
Hi Nick,

That's odd... "works for me" with ASA 5585X.
To verify, I deleted the ASA on our test server and rediscovered it. Rediscover log: 

netdisco@linux249:~$ netdisco-do discover -d 172.31.146.79 -DI
[20940] 2016-04-11 11:32:04  info App::Netdisco version 2.033005 loaded.
[20940] 2016-04-11 11:32:05 info discover: started at Mon Apr 11 13:32:05 2016 [20940] 2016-04-11 11:32:05 debug [172.31.146.79] try_connect with ver: 2, class: SNMP::Info, comm: <hidden> 
SNMP::Info::_global uptime : SNMPv2-MIB::sysUpTime.0 : .1.3.6.1.2.1.1.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_global(uptime) Timeout at /opt/netdisco/git/netdisco-ng/Netdisco/lib/App/Netdisco/Util/SNMP.pm line 176. [20940] 2016-04-11 11:32:08 debug [172.31.146.79] try_connect with ver: 1, class: SNMP::Info, comm: <hidden> 
SNMP::Info::_global uptime : SNMPv2-MIB::sysUpTime.0 : .1.3.6.1.2.1.1.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_global(uptime) Timeout at /opt/netdisco/git/netdisco-ng/Netdisco/lib/App/Netdisco/Util/SNMP.pm line 176. [20940] 2016-04-11 11:32:11 debug [172.31.146.79] try_connect with ver: 2, class: SNMP::Info, comm: <hidden> 
SNMP::Info::_global uptime : SNMPv2-MIB::sysUpTime.0 : .1.3.6.1.2.1.1.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_global(uptime) Timeout at /opt/netdisco/git/netdisco-ng/Netdisco/lib/App/Netdisco/Util/SNMP.pm line 176. [20940] 2016-04-11 11:32:14 debug [172.31.146.79] try_connect with ver: 1, class: SNMP::Info, comm: <hidden> 
SNMP::Info::_global uptime : SNMPv2-MIB::sysUpTime.0 : .1.3.6.1.2.1.1.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_global(uptime) Timeout at /opt/netdisco/git/netdisco-ng/Netdisco/lib/App/Netdisco/Util/SNMP.pm line 176. [20940] 2016-04-11 11:32:17 debug [172.31.146.79] try_connect with ver: 2, class: SNMP::Info, comm: <hidden> 
SNMP::Info::_global uptime : SNMPv2-MIB::sysUpTime.0 : .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 description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0 
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.31
SNMP::Info::device_type() layers:00000100 id:9 sysDescr:"Cisco Adaptive Security Appliance Version 9.4(1)" 
SNMP::Info 3.31
SNMP::Info::device_type() layers:00000100 id:9 sysDescr:"Cisco Adaptive Security Appliance Version 9.4(1)" [20940] 2016-04-11 11:32:17 debug [172.31.146.79] try_connect with ver: 2, new class: SNMP::Info::Layer3::CiscoASA, comm: <hidden> 

[...] etc
So our install tries a few communities and on the first succesful one it continues.
During initial discovery phase, when all communities are tried, the SNMP timeout is relatively short IIRC. Could it be that the ASA is somewhat slow to respond to eg the query for sysUptime? 


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
Telephone +31 53 489 2526, Fax +31 53 489 2383
[email protected]; http://www.utwente.nl/icts
(working on Mondays, Tuesdays and alternating Fridays)

On 04/10/2016 12:55 PM, Nikolaos Milas wrote:

Hello,

I'm trying to integrate a new ASA in our ND2.

I have managed to use ssh-collector successfully, but I can't find a way
to add ASA to the inventory. Discover fails, although snmpwalk is
successful (from the same server/account netdisco runs).

Any advice? Am I doing something wrong?
(Note: Below I've changed real domain name to "example")

$ ~/bin/netdisco-do discover -D -d 195.251.204.233
[23963] 2016-04-10 07:29:53  info discover: started at Sun Apr 10
10:29:53 2016
[23963] 2016-04-10 07:29:53 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:09 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:13 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:16 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:19 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:22 debug [195.251.204.241] try_connect with
ver: 2, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:25 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info::Layer3::Cisco, comm: <hidden>
[23963] 2016-04-10 07:30:28 debug [195.251.204.241] try_connect with
ver: 1, class: SNMP::Info, comm: <hidden>
[23963] 2016-04-10 07:30:31  info discover: finished at Sun Apr 10
10:30:31 2016
[23963] 2016-04-10 07:30:31  info discover: status error: discover
failed: could not SNMP connect to 195.251.204.241

$ snmpwalk -v 2c -c secretstring 195.251.204.233
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Adaptive Security Appliance
Version 9.5(2)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1408
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (334636900) 38 days,
17:32:49.00
SNMPv2-MIB::sysContact.0 = STRING: [email protected]
SNMPv2-MIB::sysName.0 = STRING: FW-PEN.private.example.gr
SNMPv2-MIB::sysLocation.0 = STRING: pen
SNMPv2-MIB::sysServices.0 = INTEGER: 4
IF-MIB::ifNumber.0 = INTEGER: 39
IF-MIB::ifIndex.2 = INTEGER: 2
...
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1 = STRING: "ASA 5525-X with SW, 8 GE
Data, 1 GE Mgmt, AC"
...

Thanks in advance,
Nick


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

--- End Message ---
--- Begin Message --- 
Hello List,
during discovery of a couple of cisco nexus N5KC5672UP switches, we found out that the serial reported back is wrong.
We use netdisco-mibs-2.4 and snmp::info version 3.31 (which should be latest). The switches in question are running Software Version 7.1(2)N1(1) and have some FEXes connected. 

here are the relevant debug parts of the discovery phase:
SNMP::Info::_load_attr e_serial : ENTITY-MIB::entPhysicalSerialNum(26061) : .1.3.6.1.2.1.47.1.1.1.1.11.26061 SNMP::Info::_load_attr e_serial : leaf = .1.3.6.1.2.1.47.1.1.1.1.11 , var = $VAR1 = bless( [ 
                 'entPhysicalSerialNum',
                 '26061',
                 'SPC1423059A     ',
                 'OCTETSTR'
               ], 'SNMP::Varbind' );
DEBUG: Serial: SPC1423059A
<<<<<

when we lookup the entity-id 26061, we get the following result:
SNMPv2-SMI::mib-2.47.1.1.1.1.2.26061 = STRING: "Ethernet1/16(celsius)"
In netdisco-1 webinterface under "Device Details", we get the following (wrong serial):
Model / Serial cisco N5KC5672UP (SNMP::Info::Layer3::Nexus) / SPC1423059A 


and under "Device Modules" we get the correct one.
Fabric [VPC domain:231] (Fabric [VPC domain:231]) [hw: 1.0] [serial: FOC1932R1B1] / cevContainerNexusLogicalFabric / N5K-C5672UP Nexus 5672UP Chassis (Nexus 5672UP Chassis) [hw: 1.0] [serial: FOC1932R1B1] / cevChassisN5KC5672UP / N5K-C5672UP
So the question is: how can we manage to get the good serial under device-modules even in the device details section? 

Can someone please shed some light on this?
If you need more information please let me know.

thanks in advance,

best regards,

Tom

--- End Message ---
--- Begin Message --- 

Hello List,
after a deep dive into snmp::info and his modules, we found the cause for our problem with the wrong serial.
the nexus switch has a lot of interface sensors which have the wrong parent in the snmp tree entity-mib, where the parent is set to 0, thus the serial() function of the nexus.pm has no chance to get the correct serial number.
As a temporary workaround (it is more a dirty hack) I applied the following patch to the nexus.pm module, which works for me.
diff /usr/local/share/perl/5.10.1/SNMP/Info/Layer3/Nexus.pm /usr/local/share/perl/5.10.1/SNMP/Info/Layer3/Nexus.pm.dist.3.31 
89,92d88
<                 my $len_iid = length($iid);
<                 if ($len_iid gt 3) {
<                     next;
<                 }
As you can see, I just check the length of the entity-id and if there are more than 3 characters, I assume it is a submodul and thus skipping the parent = 0 check for them. this way we get the correct serial into the device table.
I checked the patched nexus.pm against the N5kC5020pBf, N5kC5548UP, N5kC5548p, N5KC5672UP Nexus modells and it seems it carries us over all of them. 

best regards,
cheers,

Tom




Am 2016-04-12 17:40, schrieb Thomas Wollner:

Hello List,

during discovery of a couple of cisco nexus N5KC5672UP switches, we
found out that the serial reported back is wrong.

We use netdisco-mibs-2.4 and snmp::info version 3.31 (which should be
latest). The switches in question are running Software Version
7.1(2)N1(1) and have some FEXes connected.

here are the relevant debug parts of the discovery phase:




SNMP::Info::_load_attr e_serial :
ENTITY-MIB::entPhysicalSerialNum(26061) :
.1.3.6.1.2.1.47.1.1.1.1.11.26061
SNMP::Info::_load_attr e_serial : leaf = .1.3.6.1.2.1.47.1.1.1.1.11 ,
var = $VAR1 = bless( [
                  'entPhysicalSerialNum',
                  '26061',
                  'SPC1423059A     ',
                  'OCTETSTR'
                ], 'SNMP::Varbind' );
DEBUG: Serial: SPC1423059A
<<<<<

when we lookup the entity-id 26061, we get the following result:
SNMPv2-SMI::mib-2.47.1.1.1.1.2.26061 = STRING: "Ethernet1/16(celsius)"



In netdisco-1 webinterface under "Device Details", we get the following
(wrong serial):

Model / Serial  cisco N5KC5672UP (SNMP::Info::Layer3::Nexus) /
SPC1423059A


and under "Device Modules" we get the correct one.

       Fabric [VPC domain:231] (Fabric [VPC domain:231]) [hw: 1.0]
[serial: FOC1932R1B1] / cevContainerNexusLogicalFabric / N5K-C5672UP
       Nexus 5672UP Chassis (Nexus 5672UP Chassis) [hw: 1.0] [serial:
FOC1932R1B1] / cevChassisN5KC5672UP / N5K-C5672UP


So the question is: how can we manage to get the good serial under
device-modules even in the device details section?

Can someone please shed some light on this?
If you need more information please let me know.

thanks in advance,

best regards,

Tom



------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and 
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

--- End Message ---
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to