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: IP address confusion when discovering Arista switch
      (Oliver Gorwits)
   2. Re: Multiple Subnets NOT showing up in IP Inventory & LDAP AD
      authentication don't work (Oliver Gorwits)
   3. Trying to test MIBS, but install seems stuck (Hans Erasmus)
--- Begin Message ---
Hi Mark

Yes that's an interesting one!

The DELETE SQL statements at the end are the part of Netdisco where it tries to determine the best IP for the device. Netdisco has decided to renumber the device to 192.168.1.2 so it first deletes any device with that IP, then renumbers (and issues a log message):

https://github.com/netdisco/netdisco/blob/master/lib/App/Netdisco/Core/Discover.pm#L101

Do you have reverse_sysname or device_identity configured?

What is in the device_ip DB table for this device (check both IPs)?

And what is the output of:

~netdisco/bin/netdisco-do show -DI -d 10.1.2.3 -e ip_index
~netdisco/bin/netdisco-do show -DI -d 192.168.1.2 -e ip_index

regards,
Oliver.

On 2017-08-10 00:17, Mark Boolootian wrote:
We have a very odd problem with an
Arista switch that sits in the center of
our data center.  It has IP 10.1.2.3.

Recently, I noticed that when I looked
up the device in netdisco, it was
reporting with the IP 192.168.1.2.

That IP address belongs to a host
on a VLAN that runs through the Arista
switch.  But the host is a host, it
isn't running an L2 discovery protocol,
it has another (Brocade) switch between
it and the Arista switch, so I have no
idea how the Arista switch is reporting

​the host IP address 
​instead of its own.

​
I ran a discover with debug enabled in
hopes that someone might be able to
provide some hint about the cause of
trouble (or some additional recommendations
on troubleshooting).

I've truncated the output as it didn't seem
like all of it would be useful.

​Suggestions welcome.

best,
mark​

netdisco@noc-prod-netdisco-2 ~]$ netdisco-do discover -d aristaswitch
-DIQ
SELECT me.version, me.installed
  FROM dbix_class_schema_versions me
WHERE 1 = 0
SELECT me.version
  FROM dbix_class_schema_versions me
ORDER BY installed DESC
  LIMIT '1'
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE me.alias = '10.1.2.3' AND me.ip = '10.1.2.3'
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE alias = '10.1.2.3'
SELECT me.ip, me.creation, me.dns, me.description, me.uptime,
me.contact, me.name [1], me.location, me.layers, me.ports, me.mac,
me.serial, me.model, me.ps1_type, me.ps2_type, me.ps1_status,
me.ps2_status, me.fan, me.slots, me.vendor, me.os, me.os_ver, me.log,
me.snmp_ver, me.snmp_comm, me.snmp_class, me.vtp_domain,
me.last_discover, me.last_macsuck, me.last_arpnip, to_char(
last_arpnip, 'YYYY-MM-DD HH24:MI' ), to_char( last_discover,
'YYYY-MM-DD HH24:MI' ), to_char( last_macsuck, 'YYYY-MM-DD HH24:MI' ),
extract( epoch
      FROM age( now(  ), last_arpnip ) ), extract( epoch
      FROM age( now(  ), last_discover ) ), extract( epoch
      FROM age( now(  ), last_macsuck ) ), replace( age( timestamp
'epoch' + uptime / 100 * interval '1 second', timestamp '1970-01-01
00:00:00-00' ) ::text, 'mon', 'month' )
  FROM device me
WHERE me.ip = '10.1.2.3'
[20828] 2017-08-09 22:50:15  info discover: [10.1.2.3] started at Wed
Aug  9 15:50:15 2017
SELECT me.ip, me.snmp_comm_rw, me.snmp_auth_tag_read,
me.snmp_auth_tag_write
  FROM community me
WHERE me.ip = '10.1.2.3'
SELECT me.ip, me.snmp_comm_rw, me.snmp_auth_tag_read,
me.snmp_auth_tag_write
  FROM community me
WHERE me.ip = '10.1.2.3'
[20828] 2017-08-09 22:50:15 debug [10.1.2.3] try_connect with ver: 3,
class: SNMP::Info, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(uptime) Unknown user name at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 180.
[20828] 2017-08-09 22:50:16 debug [10.1.2.3] try_connect with ver: 3,
class: SNMP::Info, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(uptime) Unknown user name at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 180.
[20828] 2017-08-09 22:50:16 debug [10.1.2.3] try_connect with ver: 2,
class: SNMP::Info, 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 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.37
SNMP::Info::device_type() layers:00001110 id:30065 sysDescr:"Arista
Networks EOS version 4.12.5.1 running on an Arista Networks DCS-7504"
SNMP::Info 3.37
SNMP::Info::device_type() layers:00001110 id:30065 sysDescr:"Arista
Networks EOS version 4.12.5.1 running on an Arista Networks DCS-7504"
[20828] 2017-08-09 22:50:16 debug [10.1.2.3] try_connect with ver: 2,
new class: SNMP::Info::Layer3::Arista, comm: <hidden>
SNMP::Info::_load_attr ip_index : IP-MIB::ipAdEntIfIndex :
.1.3.6.1.2.1.4.20.1.2
SNMP::Info::_load_attr i_index : IF-MIB::ifIndex :
.1.3.6.1.2.1.2.2.1.1
SNMP::Info::_load_attr i_description : IF-MIB::ifDescr :
.1.3.6.1.2.1.2.2.1.2
SNMP::Info::_load_attr ip_netmask : IP-MIB::ipAdEntNetMask :
.1.3.6.1.2.1.4.20.1.3
[20828] 2017-08-09 22:50:17 debug  [10.1.2.3] device - aliased as
10.1.2.3
[20828] 2017-08-09 22:50:17 debug  [10.1.2.3] device - aliased as
172.16.90.1
[20828] 2017-08-09 22:50:17 debug  resolving 2 aliases with max 50
outstanding requests
SNMP::Info::_validate_autoload_method(vtp_d_name) Unable to resolve
method.
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
.1.3.6.1.2.1.1.1.0
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global name : SNMPv2-MIB::sysName.0 : .1.3.6.1.2.1.1.5.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 :
.1.3.6.1.2.1.1.7.0
SNMP::Info::_global ports : IF-MIB::ifNumber.0 : .1.3.6.1.2.1.2.1.0
SNMP::Info::_global mac : IF-MIB::ifPhysAddress.1 :
.1.3.6.1.2.1.2.2.1.6.1
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(mac) NOSUCHINSTANCE at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 186.
SNMP::Info::_validate_autoload_method(ps1_type) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(ps2_type) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(ps1_status) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(ps2_status) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(fan) Unable to resolve method.
SNMP::Info::_validate_autoload_method(slots) Unable to resolve method.
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 :
.1.3.6.1.2.1.1.2.0
SNMP::Info::_global serial1 : CISCO-SMI::temporary.6.3.0 :
.1.3.6.1.4.1.9.3.6.3.0
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve
method.
SNMP::Info::_global(serial1) NOSUCHOBJECT at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 190.
SNMP::Info::_load_attr e_parent : ENTITY-MIB::entPhysicalContainedIn :
.1.3.6.1.2.1.47.1.1.1.1.4
SNMP::Info::_load_attr e_serial : ENTITY-MIB::entPhysicalSerialNum(1)
: .1.3.6.1.2.1.47.1.1.1.1.11.1
SNMP::Info::_global contact : SNMPv2-MIB::sysContact.0 :
.1.3.6.1.2.1.1.4.0
SNMP::Info::_global location : SNMPv2-MIB::sysLocation.0 :
.1.3.6.1.2.1.1.6.0
BEGIN WORK
DELETE FROM device_ip
WHERE ip = '10.1.2.3'
[20828] 2017-08-09 22:50:17 debug  [10.1.2.3] device - removed 0
aliases
INSERT INTO device( contact, description, dns, fan, ip, last_discover,
layers, location, mac, model, name, os, os_ver, ports, ps1_status,
ps1_type, ps2_status, ps2_type, serial, slots, snmp_class, snmp_comm,
snmp_ver, uptime, vendor )
  VALUES( '', 'Arista Networks EOS version 4.12.5.1 running on an
Arista Networks DCS-7504', 'aristaswitch.ucsc.edu [2]', NULL,
'10.1.2.3', now(  ), '00001110', '', NULL, 'DCS7504', 'dca', 'EOS',
'4.12.5.1', '166', NULL, NULL, NULL, NULL, 'JSH12490569', NULL,
'SNMP::Info::Layer3::Arista', 'XXX', '2', '3030342205', 'arista' )
SAVEPOINT savepoint_0
INSERT INTO device_ip( alias, dns, ip, port, subnet )
  VALUES( ?, ?, ?, ?, ? ) : '__BULK_INSERT__'
RELEASE SAVEPOINT savepoint_0
[20828] 2017-08-09 22:50:18 debug  [10.1.2.3] device - added 2 new
aliases
COMMIT
BEGIN WORK
DELETE FROM device_ip
WHERE ip IN (
    SELECT me.ip
      FROM device me
    WHERE ip = '192.168.1.2' AND serial = 'JSH12490569' AND vendor =
'arista'
   )
DELETE FROM device_vlan
WHERE ip IN (
    SELECT me.ip
      FROM device me
    WHERE ip = '192.168.1.2' AND serial = 'JSH12490569' AND vendor =
'arista'
   )
DELETE FROM device_power
WHERE ip IN (
    SELECT me.ip
      FROM device me
    WHERE ip = '192.168.1.2' AND serial = 'JSH12490569' AND vendor =
'arista'
   )
DELETE FROM device_module
WHERE ip IN (
    SELECT me.ip
      FROM device me
    WHERE ip = '192.168.1.2' AND serial = 'JSH12490569' AND vendor =
'arista'
   )
DELETE FROM community
WHERE ip IN (
    SELECT me.ip
      FROM device me
    WHERE ip = '192.168.1.2' AND serial = 'JSH12490569' AND vendor =
'arista'
   )
DELETE FROM admin
WHERE device IN (
    SELECT me.ip
      FROM device me
    WHERE ip = '192.168.1.2' AND serial = 'JSH12490569' AND vendor =
'arista'
   )


Links:
------
[1] http://me.name
[2] http://aristaswitch.ucsc.edu

------------------------------------------------------------------------------
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 ---
--- Begin Message ---
Hi Burhan

For multiple IP subnets, make sure Netdisco is polling your router or default gateway, so that it can pick up all the node IP addresses:

https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices

For AD authentication, see here:

https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Configuration.pod#ldap

regards,
oliver.

On 2017-08-09 12:55, Mahmood, Burhan wrote:
Good Afternoon,

I am so happy that finally I managed to get NetDisco working. I am
running it on Ubuntu 14.02 LTS in a VM environment with 2 NICS
attached to this VM currently. In my work environment I have multiple
domains and subnets which Netdisco is unable to discover so far.

Everything else seems to work fine so far except I have couple of
questions.

1. How do I get multiple subnets displayed on Netdisco GUI under IP
Inventory? ( while file to edit and what ) ?

2. How do I get Netdisco GUI authenticate against my AD credentials? (
which file to edit , I assume it will be deployment.yml file )

Hope to hearing from you guys soon.

Burhan Mahmood

Senior Systems Administrator

b.mahm...@ucl.ac.uk


------------------------------------------------------------------------------
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 ---
--- Begin Message ---
Hi All

I am trying to do my bit and test some D-link MIBS which I hope to be able
to add to netdisco-mibs for the community to use. I am using the
instructions from this link
<https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs>.

However, the step where it says "7. Bootstrap net-snmp with custom
configuration: EXTRAS/scripts/setmaxtc" I ran the following command:

/usr/bin/perl EXTRAS/scripts/setmaxtc

and now it seems the thing is stuck. It just states:

Building net-snmp dependancies(1)...  and has been on this step now for
roughly about 4 hours. Is this normal? How long should this take? (First
time running it).

Attached is a print screen of what happened up to now.

Regards

Hans[image: Netdisco-mibs-error.png]

--- 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

Reply via email to