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: Exporting data from Netdisco 2 for Icinga (Oliver Gorwits)
   2. Re: Search Failed error message (Oliver Gorwits)
   3. Re: sshcollector doesn?t fetch arp entries (Oliver Gorwits)
   4. Re: App::Netdisco 2.032005 Not showing device DNS names (only
      showing IP's) (Oliver Gorwits)
   5. Re: IP Inventory sometimes does not list never-seen IPs
      (Oliver Gorwits)
   6. Custom SQL/Web reporting (Andy Sainsbury)
   7. ASR9k (Nenad Tomasevic)
--- Begin Message --- For info, I have just squashed a bug where the hostnames (DNS) of the devices were not being properly stored to the database. This would have resulted in neighbor graphs with IP addresses only. The names should definitely be there! Sorry about that.

On the second part, yes the SQL for the neighbor relations is a little tricky to dig out. This query might be useful:

https://metacpan.org/source/OLIVER/App-Netdisco-2.032005/lib/App/Netdisco/DB/Result/Virtual/UnDirEdgesAgg.pm

regards,
oliver.

On 2015-07-09 14:55, Zachary McGibbon wrote:
Yes, it draws the map however this is not as useful right now as it
only shows the IP address and I know there is a feature request to
have the names and not just the IP displayed.  On our network we have
around 1000 Cisco switches/routers combined so being able to export
this parent/child relationship to Icinga is what we are looking for as
it is the tool we use for monitoring out network.  We want to know
when a switch or router goes down what is impacted by the outage and
which equipment is at fault.

Another option, is if there was a table view or csv export of the
neighbors or something like that, I could probably parse it.  I've
looked through the PostgreSQL database and haven't found a good way to
extract the parent/child relationships.

- Zachary

On Wed, Jul 8, 2015 at 12:47 PM, Mark Cooper <[email protected] [1]>
wrote:

Going to any device and looking at the details, then the neighbors,
does that not already draw a map for you?

Thanks,
Coop



Links:
------
[1] mailto:[email protected]




--- End Message ---
--- Begin Message ---
Hi Andy,

On 2015-06-26 02:25, Andy Sainsbury wrote:
I'm finding that a couple of devices in my environment are causing the "Ports" search to fail with the message "Search failed! Please contact
your site administrator.", and was wondering if anybody else has
encountered that problem?

If this can be reliably reproduced, then it's probably a mistake in some SQL being generated inside the app. To get a dump of the query you can stop the netdisco-web part, and run:

DBIC_TRACE=1 ~/bin/localenv plackup ~/bin/netdisco-web-fg

regards,
oliver.

I've run pgtune on my VM, and have plenty of free resources but can't
figure out what is causing the time out and subsequent error.

Any starting points would be great.

Regards,

Andy Sainsbury
-Network Engineer 
-Melbourne University

PS Love the ap, its making my life so much easier!




--- End Message ---
--- Begin Message ---
Hi Sebastian,

You can set log=debug in the deployment.yml file to enable more logging.

Unfortunately beyond that, you really need to dig into the code to work out what's going on. Under the hood the sshcollector uses Expect to scrape the CLI. Perhaps it's using the wrong command for your platform or railing to login correctly.

The source is here, which you could copy and try modifying?

https://metacpan.org/source/OLIVER/App-Netdisco-2.032005/lib/App/Netdisco/SSHCollector/Platform/ASA.pm

The $ssh parameter is a Net::OpenSSH connection to the device.

regards,
oliver.


On 2015-06-10 16:53, Sebastian Rösch wrote:
I´ve updated to 2.032005 and installed netdisco-sshcollector. I
configured the deployment.yml and I´m still not able to retrieve the
arp table from my cisco asa. On the ASA I see the established ssh
connection from netdisco, but theres nothing happening I think. Does
it take a long time to finish?

This is the output from the command Line and it doesn´t change:

netdisco@ubuntu:~$ netdisco-sshcollector -DQ

[1760] 2015-06-10 15:42:03 debug 10.206.254.3 1760 arpnip()

What can I do? How can I troubleshoot this?

Best Regards

Sebastian




--- End Message ---
--- Begin Message --- Again, sorry about this, the bug is fixed in the repo and I'll get a release out today with the fix.

That should enable you to remove the reverse_sysname setting.

regards,
oliver.

On 2015-06-17 15:08, Bill Richardson wrote:
Solved:

I needed to add this to me config:

reverse_sysname: true

Now the dns field in device table is being updated and I see hostname
instead of IP's

Surprised no one else has asked this before? I must be a little slow J


FROM: Bill Richardson
 SENT: Wednesday, June 17, 2015 8:46 AM
 TO: '[email protected]'
 SUBJECT: RE: App::Netdisco 2.032005 Not showing device DNS names
(only showing IP's)

One more update:

If I add manually add a dns name to the device table dns field it
works. So how do I get the DNS fields to update automatically in the
device table?

FROM: Bill Richardson
 SENT: Wednesday, June 17, 2015 8:19 AM
 TO: '[email protected]'
 SUBJECT: RE: App::Netdisco 2.032005 Not showing device DNS names
(only showing IP's)

So just to be clear

table "device" the dns field has no data

table "device_ip" does have data in the dns field

Looking at the debug output of a discovery it looks like it only
updates the device_ip table:

INSERT INTO device_ip( alias, dns, ip, port, subnet )

 VALUES( ?, ?, ?, ?, ? ) : '__BULK_INSERT__'

Ok so is this dns data only in the device_ip table? If so what do I
need to do to show that in the neighbor maps?

FROM: Bill Richardson
 SENT: Wednesday, June 17, 2015 7:52 AM
 TO: '[email protected]'
 SUBJECT: App::Netdisco 2.032005 Not showing device DNS names (only
showing IP's)

I have looked thru the doc's and have searched this list but can't
seem to determine why I'm not seeing my device hostnames showup? Nodes
all seem to resolve but none of the devices have anything data in the
DNS table. Looking at the neighbor maps all devices show IP's no
names.

My config has this entry:

dns:

 max_outstanding: 50

Doing a discovery and looking at the debug output as so:

"netdisco-do discover -d switch-name -D" I see that its resolving:

"debug resolving 7 aliases with max 50 outstanding requests"

Doing a tcpdump and looking at port 53 (while running a discovery) I
see the proper DNS requests and responses

Any thoughts on why this is not working?

Thank you.. Bill




--- End Message ---
--- Begin Message ---
Hi Nikolas,

On 2015-06-06 19:02, Nikolaos Milas wrote:
I notice that when running the "IP Inventory" Report, *on one**subnet*, never-seen IP addresses won't get displayed, even if I check "List IP's
Never Seen". See:

That's a strange bug! ;)

Would you have a problem sending me data from your database so I can try to work through the code/SQL here? Feel free to contact me off-list (oliver at cpan dot org) or on IRC.

Without source data, I'm not sure I'll be able to reproduce the problem.

regards,
oliver.


    http://iweb.noa.gr/files/ip-report-20150606.jpg

This happens always with the particular subnet, but it never happens
with other subnets. The affected subnet is 195.251.202.0/25. (It also
happens with 195.251.202.0/24, but it does not happen for example with
195.251.203.0/24 or 195.251.204.0/24.)

Am I doing something wrong, or should you please take a look at it?

Thanks in advance.

All the best,
Nick





------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users




--- End Message ---
--- Begin Message ---
Hi there,

I'm having difficulty working out the syntax required to post a report in
the environment.yml file to represent the following SQL query:

SELECT device.name,
       device.serial,
       device.model,
       device.os_ver,
       device_module.description,
       device_module.serial,
       device_module.model,
       device_module.class
FROM device_module
INNER JOIN device ON device.ip=device_module.ip
WHERE device.vendor LIKE 'cisco'
  AND device_module.model ~ '-SUP'
ORDER BY device.os_ver;

I can build custom reports from data originating from one table after
reading the documents:

  - tag: host_list
     category: Device
     label: 'List of All Devices'
     columns:
       - {name: 'Name'}
       - {model: 'Model'}
       - {serial: 'Serial'}
       - {os: 'OS'}
       - {os_ver: 'OS Version'}

  query: |
       SELECT d.name, d.model, d.serial, d.os, d.os_ver
         FROM device d
       ORDER BY name

Just I can't work out the method of writing up the syntax for more
complicated SQL queries across multiple tables.

Any help much appreciated!

Regards,

Andy Sainsbury
Network Engineer
University of Melbourne

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

Our setup is;

Software

Version

App::Netdisco<http://netdisco.org>

2.032006

DB Schema<https://metacpan.org/module/netdisco-db-deploy>

v40

Dancer<http://http:/perldancer.org/>

1.3140

Bootstrap<http://getbootstrap.com>

2.3.1

PostgreSQL<http://www.postgresql.org>

PostgreSQL 9.4.3 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.9.2-10) 
4.9.2, 64-bit.
 DBI 1.631, DBD::Pg 3.4.2

SNMP::Info<http://snmp-info.sourceforge.net/>

3.28

Perl<http://www.perl.org>

5.020002




And it seems there is bug in device aliasing method affecting only ASR 9000 
series, actually aliasing doesn't work for some reason.

We discover devices based on the external script output, basicaly all pinglable 
IP's from some subnets are going to Netdisco for discovering.

Problem is most of the ASR have multiple pingable IP's from those subnets and 
Netdisco for some reason doesn't get it those are aliases.

Real life scenario, if we discover 10.10.20.130 and 10.10.20.132, which is same 
device, we get two devices with same hostname, serial number, IP addresses, 
neighbours and stuff in database;

netdisco@netdisco:~$ ~/bin/netdisco-do discover -d 10.10.20.130 -D -S
[50143] 2015-07-29 12:02:39  info discover: started at Wed Jul 29 14:02:39 2015
[50143] 2015-07-29 12:02:39 debug [10.10.20.130] try_connect with ver: 2, 
class: SNMP::Info::Layer3::Cisco, comm: <hidden>
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/3com
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/aerohive
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/alcatel
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/allied
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/apc
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/arista
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/aruba
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/asante
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/avaya
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/bluecoat
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/bluesocket
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/cabletron
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/checkpoint
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/cisco
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/citrix
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/colubris
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/cyclades
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/d-link
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/dell
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/enterasys
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/extreme
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/extricom
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/f5
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/force10
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/fortinet
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/foundry
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/h3c
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/hp
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/huawei
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/ibm
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/juniper
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/lantronix
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/meraki
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/mikrotik
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/motorola
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/net-snmp
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/netapp
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/netgear
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/netscreen
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/nortel
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/packetfront
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/paloalto
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/pica8
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/rad
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/rfc
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/riverbed
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/ruckus
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/sentry
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/sonicwall
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/trapeze
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/xirrus
Read OLD-CISCO-SYS-MIB
Read CISCO-RTTMON-MIB
Read Q-BRIDGE-MIB
Read ENTITY-MIB
Read CISCO-STP-EXTENSIONS-MIB
Read POWER-ETHERNET-MIB
Read CISCO-CLASS-BASED-QOS-MIB
Read LLDP-EXT-DOT3-MIB
Read CISCO-ENTITY-VENDORTYPE-OID-MIB
Read CISCO-FLASH-MIB
Read CISCO-CONFIG-COPY-MIB
Read EtherLike-MIB
Read CISCO-EIGRP-MIB
Read CISCO-PROCESS-MIB
Read CISCO-STACK-MIB
Read LLDP-EXT-DOT1-MIB
Read CISCO-VTP-MIB
Read CISCO-VLAN-MEMBERSHIP-MIB
Read IPV6-MIB
Read CISCO-IMAGE-MIB
Read CISCO-PRODUCTS-MIB
Read BRIDGE-MIB
Read CISCO-IETF-IP-MIB
Read CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
Read CISCO-CDP-MIB
Read SNMPv2-MIB
Read OLD-CISCO-SYSTEM-MIB
Read IP-MIB
Read CISCO-POWER-ETHERNET-EXT-MIB
Read CISCO-MEMORY-POOL-MIB
Read OSPF-MIB
Read LLDP-MIB
Read BGP4-MIB
Read ADSL-LINE-MIB
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.127.10.0
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.84.66.226
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.10.20.133
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
212.91.123.86
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.11.120.255
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.101.120.1
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.10.20.141
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 10.0.0.1
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 10.64.1.47
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.243.33.130
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.11.121.1
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.101.120.255
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.224.12.2
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.64.166.2
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
172.23.23.21
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 10.64.1.46
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 10.64.25.2
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.10.20.130
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.10.20.145
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.10.10.196
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.10.20.137
[50143] 2015-07-29 12:02:39 debug  [10.10.20.130] device - aliased as 
10.243.33.162
[50143] 2015-07-29 12:02:39 debug  resolving 22 aliases with max 50 outstanding 
requests
error:snmp_translate_obj:Unknown OID ps1_type
error:snmp_translate_obj:Unknown OID ps2_type
error:snmp_translate_obj:Unknown OID ps1_status
error:snmp_translate_obj:Unknown OID ps2_status
error:snmp_translate_obj:Unknown OID fan
error:snmp_translate_obj:Unknown OID slots
[50143] 2015-07-29 12:02:40 debug  [10.10.20.130] device - removed 22 aliases
[50143] 2015-07-29 12:02:40 debug  [10.10.20.130] device - added 22 new aliases
error:snmp_translate_obj:Unknown OID i_ignore
error:snmp_translate_obj:Unknown OID i_duplex_admin
error:snmp_translate_obj:Unknown OID agg_ports
[50143] 2015-07-29 12:02:41 debug  [10.10.20.130] interfaces - removed 46 
interfaces
[50143] 2015-07-29 12:02:41 debug  [10.10.20.130] interfaces - added 46 new 
interfaces
error:snmp_translate_obj:Unknown OID i_ssidlist
[50143] 2015-07-29 12:02:44 debug  [10.10.20.130] vlans - removed 0 device VLANs
[50143] 2015-07-29 12:02:44 debug  [10.10.20.130] vlans - added 0 new device 
VLANs
[50143] 2015-07-29 12:02:44 debug  [10.10.20.130] vlans - removed 0 port VLANs
[50143] 2015-07-29 12:02:44 debug  [10.10.20.130] vlans - added 0 new port VLANs
[50143] 2015-07-29 12:02:44 debug  [10.10.20.130] power - 0 power modules
[50143] 2015-07-29 12:02:46 debug  [10.10.20.130] modules - removed 292 chassis 
modules
[50143] 2015-07-29 12:02:46 debug  [10.10.20.130] modules - added 292 new 
chassis modules
[50143] 2015-07-29 12:02:46 debug  [10.10.20.130] neigh - setting manual 
topology links
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.10.20.138, type [cisco ASR9K Series], on GigabitEthernet0/0/0/0 to discovery 
queue
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.10.20.142, type [cisco ASR9K Series], on GigabitEthernet0/0/0/1 to discovery 
queue
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.84.66.230, type [cisco WS-C2960S-48TS-L], on GigabitEthernet0/0/0/2 to 
discovery queue
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.10.20.129, type [cisco ASR9K Series], on TenGigE0/0/2/0 to discovery queue
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.10.20.134, type [cisco ASR9K Series], on TenGigE0/0/2/1 to discovery queue
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.10.20.146, type [Cisco uBR10000], on TenGigE0/0/2/2 to discovery queue
[50143] 2015-07-29 12:02:48 debug  [10.10.20.130] neigh - adding neighbor 
10.84.66.228, type [cisco WS-C3750X-48], on TenGigE0/0/2/3 to discovery queue
[50143] 2015-07-29 12:02:48  info discover: finished at Wed Jul 29 14:02:48 2015
[50143] 2015-07-29 12:02:48  info discover: status done: Ended discover for 
10.10.20.130
netdisco@netdisco:~$
netdisco@netdisco:~$
netdisco@netdisco:~$ ~/bin/netdisco-do discover -d 10.10.20.132 -D -S
[50146] 2015-07-29 12:03:00  info discover: started at Wed Jul 29 14:03:00 2015
[50146] 2015-07-29 12:03:01 debug [10.10.20.132] try_connect with ver: 2, 
class: SNMP::Info::Layer3::Cisco, comm: <hidden>
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/3com
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/aerohive
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/alcatel
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/allied
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/apc
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/arista
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/aruba
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/asante
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/avaya
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/bluecoat
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/bluesocket
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/cabletron
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/checkpoint
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/cisco
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/citrix
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/colubris
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/cyclades
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/d-link
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/dell
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/enterasys
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/extreme
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/extricom
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/f5
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/force10
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/fortinet
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/foundry
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/h3c
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/hp
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/huawei
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/ibm
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/juniper
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/lantronix
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/meraki
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/mikrotik
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/motorola
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/net-snmp
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/netapp
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/netgear
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/netscreen
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/nortel
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/packetfront
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/paloalto
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/pica8
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/rad
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/rfc
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/riverbed
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/ruckus
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/sentry
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/sonicwall
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/trapeze
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/xirrus
Read IPV6-MIB
Read ADSL-LINE-MIB
Read OLD-CISCO-SYSTEM-MIB
Read CISCO-RTTMON-MIB
Read POWER-ETHERNET-MIB
Read EtherLike-MIB
Read LLDP-EXT-DOT3-MIB
Read IP-MIB
Read CISCO-EIGRP-MIB
Read CISCO-IMAGE-MIB
Read CISCO-CLASS-BASED-QOS-MIB
Read CISCO-PRODUCTS-MIB
Read CISCO-STP-EXTENSIONS-MIB
Read Q-BRIDGE-MIB
Read CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
Read CISCO-POWER-ETHERNET-EXT-MIB
Read CISCO-CONFIG-COPY-MIB
Read CISCO-FLASH-MIB
Read CISCO-IETF-IP-MIB
Read BRIDGE-MIB
Read ENTITY-MIB
Read OSPF-MIB
Read OLD-CISCO-SYS-MIB
Read LLDP-MIB
Read CISCO-VTP-MIB
Read CISCO-ENTITY-VENDORTYPE-OID-MIB
Read CISCO-PROCESS-MIB
Read CISCO-MEMORY-POOL-MIB
Read LLDP-EXT-DOT1-MIB
Read BGP4-MIB
Read CISCO-CDP-MIB
Read SNMPv2-MIB
Read CISCO-VLAN-MEMBERSHIP-MIB
Read CISCO-STACK-MIB
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 10.64.1.46
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.84.66.226
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.243.33.162
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.127.10.0
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.224.12.2
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.243.33.130
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.10.10.196
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.10.20.145
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.10.20.130
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.101.120.1
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
212.91.123.86
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.11.121.1
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.64.166.2
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
172.23.23.21
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.10.20.137
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.10.20.133
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.10.20.141
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.101.120.255
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 10.0.0.1
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 10.64.1.47
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 10.64.25.2
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - aliased as 
10.11.120.255
[50146] 2015-07-29 12:03:01 debug  resolving 22 aliases with max 50 outstanding 
requests
error:snmp_translate_obj:Unknown OID ps1_type
error:snmp_translate_obj:Unknown OID ps2_type
error:snmp_translate_obj:Unknown OID ps1_status
error:snmp_translate_obj:Unknown OID ps2_status
error:snmp_translate_obj:Unknown OID fan
error:snmp_translate_obj:Unknown OID slots
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - removed 22 aliases
[50146] 2015-07-29 12:03:01 debug  [10.10.20.132] device - added 22 new aliases
error:snmp_translate_obj:Unknown OID i_ignore
error:snmp_translate_obj:Unknown OID i_duplex_admin
error:snmp_translate_obj:Unknown OID agg_ports
[50146] 2015-07-29 12:03:03 debug  [10.10.20.132] interfaces - removed 46 
interfaces
[50146] 2015-07-29 12:03:03 debug  [10.10.20.132] interfaces - added 46 new 
interfaces
error:snmp_translate_obj:Unknown OID i_ssidlist
[50146] 2015-07-29 12:03:05 debug  [10.10.20.132] vlans - removed 0 device VLANs
[50146] 2015-07-29 12:03:05 debug  [10.10.20.132] vlans - added 0 new device 
VLANs
[50146] 2015-07-29 12:03:05 debug  [10.10.20.132] vlans - removed 0 port VLANs
[50146] 2015-07-29 12:03:05 debug  [10.10.20.132] vlans - added 0 new port VLANs
[50146] 2015-07-29 12:03:06 debug  [10.10.20.132] power - 0 power modules
[50146] 2015-07-29 12:03:08 debug  [10.10.20.132] modules - removed 292 chassis 
modules
[50146] 2015-07-29 12:03:08 debug  [10.10.20.132] modules - added 292 new 
chassis modules
[50146] 2015-07-29 12:03:08 debug  [10.10.20.132] neigh - setting manual 
topology links
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
error:snmp_translate_obj:Unknown OID hasSONMP
error:snmp_translate_obj:Unknown OID hasFDP
error:snmp_translate_obj:Unknown OID hasEDP
error:snmp_translate_obj:Unknown OID hasAMAP
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.10.20.138, type [cisco ASR9K Series], on GigabitEthernet0/0/0/0 to discovery 
queue
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.10.20.142, type [cisco ASR9K Series], on GigabitEthernet0/0/0/1 to discovery 
queue
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.84.66.230, type [cisco WS-C2960S-48TS-L], on GigabitEthernet0/0/0/2 to 
discovery queue
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.10.20.129, type [cisco ASR9K Series], on TenGigE0/0/2/0 to discovery queue
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.10.20.134, type [cisco ASR9K Series], on TenGigE0/0/2/1 to discovery queue
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.10.20.146, type [Cisco uBR10000], on TenGigE0/0/2/2 to discovery queue
[50146] 2015-07-29 12:03:10 debug  [10.10.20.132] neigh - adding neighbor 
10.84.66.228, type [cisco WS-C3750X-48], on TenGigE0/0/2/3 to discovery queue
[50146] 2015-07-29 12:03:10  info discover: finished at Wed Jul 29 14:03:10 2015
[50146] 2015-07-29 12:03:10  info discover: status done: Ended discover for 
10.10.20.132

Does anbody else have similar situation/explanation/solution..?

KR,

Nenad

<<attachment: winmail.dat>>


--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to