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: Netdisco v2 Discover Question (David Weise)
   2. Re: NETBIOS suck only specific IP subnets ? (Oliver Gorwits)
   3. Re: Timestamp/Time zone issue (Oliver Gorwits)
   4. Re: Netdisco v2 Discover Question (Oliver Gorwits)
   5. Re: NETBIOS suck only specific IP subnets ? (Michael Butash)
   6. Re: discover device fail (Jeroen van Ingen)
--- Begin Message ---
hi,
So the job queue is now red, it says "discover failed: could not SNMP connect to 123.123.123.123/32. I looked in both logs and nothing of note. I checked deployment.yml and the community is good. I also restarted the daemon with the netdisco username instead of root. (gives error when I try to do that via root).

--David

On 3/13/2014 5:52 PM, Oliver Gorwits wrote:
On 2014-03-13 20:31, Joseph Bernard wrote:
Do you get a bunch of errors in the logs of the web gui?
Yes, as Joseph says, go to Admin -> Job Queue in the web interface and
see what it says.

If there are queued jobs (white rows) then either the daemon isn't
running, or it's somehow misconfigured. If there are errors (red rows),
hover the mouse over to see what happened.

Also you can up the log level and restart the daemon to see what it's
doing. Set this in your deployment.yml file:

log: info

And then restart the daemon and 'tail -f ~/logs/netdisco-daemon.log'.

regards,
oliver.

Thanks,
Joseph B.

On Mar 13, 2014, at 4:29 PM, David Weise <[email protected]>
  wrote:

hi,
Nope, that has been running the whole time.
--David

On 3/13/2014 1:01 PM, Oliver Gorwits wrote:
Hi David,

You need to start the backend daemon (netdisco-daemon) and it will
continue the work.

The discovery for all other switches and routers is currently
queued in
your database, waiting for the daemon to start.

regards,
oliver.

On 2014-03-13 16:43, David Weise wrote:
hi Everybody,
  I ran the following command on Netdisco v2.024004:

~/bin/netdisco-do -D discover -d 192.0.2.1

  Using the core CISCO router we have. Using netdisco v1.1 it found
all
attached routers and switches and populated the database. When I
ran
the command above it just found the core router and went no
further.
What command must I issue to find the rest of the network? Thanks
for
any help!
  --David

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases
and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users


<dweise.vcf>------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!

http://p.sf.net/sfu/13534_NeoTech_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users


<<attachment: dweise.vcf>>


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

On 2014-03-14 09:27, Černý Lubomír wrote:
Hi folks.

I need to block netbios to get info from part of our network.

I know, ARP and MAC suck can be limited to only specific subnets/host.

How can I limit the same for NETBIOS ?

Here's a reply for Netdisco 2:

In about two weeks we're going to release an update to Netdisco to improve support for Netbios name retrieval. I suggest you wait until then, because the performance will be much better.

That release will also include support for nbtstat_only and nbtstat_no which can be used in the same way as other *_only/*_no config options. Note that this setting refers to the *node* (i.e. the workstation IP).

(I'm not sure Netdisco 1 supports this feature??)

regards,
oliver.


S pozdravem / with regards

Lubomír Černý
ICT projektový manažer | ICT Project Manager

UNIPETROL SERVICES, s.r.o.
Kancelář | Office: Záluží 1, 436 70 Litvínov 7
Tel.: +420 476 162 150 | GSM: +420 736 506 248 | Fax: +420 476 768 432
[email protected] | www.unipetrolservices.cz




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

Whilst I don't have an immediate answer, we have opened a tracker for the discussion on this topic:

https://sourceforge.net/p/netdisco/netdisco2/96/

I note that in Netdisco 2 someone spotted two uses of localtime() which is probably wrong. I hope that's not what caused your issue.

Please feel free to add comments to that tracker with your findings.

regards,
oliver.

On 2014-03-14 14:33, David Koski wrote:
I have a very strange ongoing problem.  A while ago I noticed that
some of my timestamps in the database where 5 hours earlier but some
of the timestamps were correct (node_ip.time_first/node_ip.time_last
was fine, but node.time_first, node.time_recent, node.time_last were
all off).

So I went in to postgresql.conf and removed all my timezone settings,
and the times reversed.  With the ones being off no fine, and the
ones that were fine is off).

So obviously this is a table issue...  I checked all the table
definitions and they all say "timestamp without timezone" and default
to "now()".

So what am I missing?  I don't see how the database could be the
issue.  The dates continue to go in the database off depending on the
column, but they are all set to "without timezone"..

Anyone have any thoughts?  I'm anything but a whiz with postgres.

         Dave

------------

DAVID KOSKI

GCFA, GISP, GSEC, RHCE

ITS Communications Systems and Data Centers


734-647-8993 (Office)                                                           
                          734-678-5824 (Mobile)




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

On 2014-03-14 15:18, David Weise wrote:
 So the job queue is now red, it says "discover failed: could not
SNMP connect to 123.123.123.123/32. I looked in both logs and nothing
of note. I checked deployment.yml and the community is good.  I also
restarted the daemon with the netdisco username instead of root.
(gives error when I try to do that via root).

OK, thanks for the update, and your patience.

The next level of troubleshooting is to set the log level to debug and also to restart the daemon with SNMP tracing enabled. First, set the following in your deployment.yml config file:

log: debug

And then restart the daemon but setting the INFO_TRACE=1 environment variable. This will cause the lower SNMP::Info layer to log when it connects. Hopefully you will see (for snmp v1 and v2) details of what Netdisco is trying to do, and for v3 a little less info but a pointer to the "tag" of the config file.

As you might expect, the code for the netdisco-do and the daemon to make an SNMP connection is exactly the same, so I'm a bit puzzled why one works and the other does not.

Finally, yes, you should always start the daemons (both netdisco-web and netdisco-daemon) as the netdisco user (or whatever non-root user was used to install), as per the documentation. There is no need for Netdisco to have root privilege[1].

regards,
oliver.

[1] in the next release, we will support starting as root in order to bind netdisco-web to a privileged port number, then dropping privileges after. I still recommend the reverse proxy recipe, myself, though. Start-as-root is also good for run-control system integration.



--David

On 3/13/2014 5:52 PM, Oliver Gorwits wrote:
On 2014-03-13 20:31, Joseph Bernard wrote:
Do you get a bunch of errors in the logs of the web gui?
Yes, as Joseph says, go to Admin -> Job Queue in the web interface and
see what it says.

If there are queued jobs (white rows) then either the daemon isn't
running, or it's somehow misconfigured. If there are errors (red rows),
hover the mouse over to see what happened.

Also you can up the log level and restart the daemon to see what it's
doing. Set this in your deployment.yml file:

log: info

And then restart the daemon and 'tail -f ~/logs/netdisco-daemon.log'.

regards,
oliver.

Thanks,
Joseph B.

On Mar 13, 2014, at 4:29 PM, David Weise <[email protected]>
  wrote:

hi,
Nope, that has been running the whole time.
--David

On 3/13/2014 1:01 PM, Oliver Gorwits wrote:
Hi David,

You need to start the backend daemon (netdisco-daemon) and it will
continue the work.

The discovery for all other switches and routers is currently
queued in
your database, waiting for the daemon to start.

regards,
oliver.

On 2014-03-13 16:43, David Weise wrote:
hi Everybody,
  I ran the following command on Netdisco v2.024004:

~/bin/netdisco-do -D discover -d 192.0.2.1

Using the core CISCO router we have. Using netdisco v1.1 it found
all
attached routers and switches and populated the database. When I
ran
the command above it just found the core router and went no
further.
What command must I issue to find the rest of the network? Thanks
for
any help!
  --David


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases
and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users



<dweise.vcf>------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!


http://p.sf.net/sfu/13534_NeoTech_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users



------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users





--- End Message ---
--- Begin Message --- A quick hack might be to add a local outbound iptables rule blocking destination $subnets for tcp/139 and tcp/445 (forget which nd uses). I've had to do this with systems to avoid cranky devices, or regions that security gets annoyed with chronic poking discoveries.

-mb


On 03/15/2014 03:24 AM, Oliver Gorwits wrote:
Hi there,

On 2014-03-14 09:27, Černý Lubomír wrote:
Hi folks.

I need to block netbios to get info from part of our network.

I know, ARP and MAC suck can be limited to only specific
subnets/host.

How can I limit the same for NETBIOS ?
Here's a reply for Netdisco 2:

In about two weeks we're going to release an update to Netdisco to
improve support for Netbios name retrieval. I suggest you wait until
then, because the performance will be much better.

That release will also include support for nbtstat_only and nbtstat_no
which can be used in the same way as other *_only/*_no config options.
Note that this setting refers to the *node* (i.e. the workstation IP).

(I'm not sure Netdisco 1 supports this feature??)

regards,
oliver.

S pozdravem / with regards

Lubomír Černý
ICT projektový manažer | ICT Project Manager

UNIPETROL SERVICES, s.r.o.
Kancelář | Office: Záluží 1, 436 70 Litvínov 7
Tel.: +420 476 162 150 | GSM: +420 736 506 248 | Fax: +420 476 768
432
[email protected] | www.unipetrolservices.cz

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users




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

Are you sure that the "new" and "old" switches have exactly the same configuration for SNMP access?

I'm afraid that I still don't have any experience with SNMPv3, but I do notice a couple of things in the outputs that you pasted:

1) The device you're trying to discover has cached credentials in the database: it was last discovered using SNMPv1 and a community ending in the letter "c".

2) Now SNMPv1 (using the last-known-good credentials) fails and Netdisco tries SNMPv3, but the switch replies with an "authorizationError". I assume that deleting the device and trying to discover with SNMPv3 "from scratch" gives the same error?

3) Running snmpbulkwalk on the CLI succeeds, but you used "netdisco" as AuthPassword and "nedisco" (without the "t") as PrivPassword; did you copy/paste the commands and is it your actual configuration, or was it a typo when copying?


I hope this helps a bit; if not, hopefully someone more experienced with SNMPv3 can provide some pointers.


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands


On 03/05/2014 12:17 PM, [email protected] wrote:
hi list

I install some new hp switch

hpA512052CEI
hpA550028FEI
hpA550052CE

netdisco fail to discover these devices using snmp v3, but discover them
if v1 is enabled.

netdisco discover other old devices with snmp v3 same authPriv

snmpbulkwalk seems to work fine.


any suggestion?


Thanks,


Marco


root@netdisco:~# uname -a
Linux netdisco 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux


root@netdisco:~# netdisco -v
n e t  d i s c o
--------------------------------------------------
Netdisco Version   : 1.2
SNMP::Info Version : 3.12
Net-SNMP Version   : 5.0702
Perl Version       : 118.53.46.49.52.46.50


root@netdisco:~# netdisco -d 172.17.117.9 -D
n e t  d i s c o
--------------------------------------------------
Using Config File : /etc/netdisco/netdisco.conf
Loading topology information from /usr/share/netdisco/netdisco-topology.txt
0 entries loaded
Loading manual topology information from database
0 entries loaded
[172.17.117.9] Discover starting
   get_device(172.17.117.9)
   get_device(172.17.117.9) - Connecting using cached info: 172.17.117.9/c/1
   create_device(172.17.117.9,c,1*,AutoSpecify,bw:default)
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/3com
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/alcatel
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/allied
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/apc
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/arista
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/aruba
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/asante
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/bluecoat
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/bluesocket
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cabletron
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/checkpoint
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cisco
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/citrix
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/colubris
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/cyclades
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/d-link
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/dell
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/enterasys
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/extreme
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/extricom
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/f5
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/force10
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/foundry
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/h3c
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/hp
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/huawei
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/juniper
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/lantronix
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/mikrotik
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/net-snmp
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/netgear
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/netscreen
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/nortel
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/packetfront
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/pica8
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/rad
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/rfc
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/riverbed
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/ruckus
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/sonicwall
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/trapeze
SNMP::Info::init() - Adding new mibdir:/usr/share/netdisco/mibs/xirrus
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global(layers) Timeout at /usr/bin/netdisco line 1397
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
.1.3.6.1.2.1.1.1.0
SNMP::Info::_global(description) Timeout at /usr/bin/netdisco line 1397
SNMP::Info::specify() - Could not get info from device at
/usr/bin/netdisco line 1397
   Can't connect to 172.17.117.9
!  Could not connect to 172.17.117.9 with SNMP community and version
info in database.
   create_device(172.17.117.9,l,3,AutoSpecify,bw:default)
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global(layers) authorizationError (access denied to that
object) at /usr/bin/netdisco line 1397
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
.1.3.6.1.2.1.1.1.0
SNMP::Info::_global(description) authorizationError (access denied to
that object) at /usr/bin/netdisco line 1397
SNMP::Info::specify() - Could not get info from device at
/usr/bin/netdisco line 1397
[172.17.117.9] [Trying SNMP Version 1]
create_device(172.17.117.9,l,1)
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global(layers) Timeout at /usr/bin/netdisco line 1418
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
.1.3.6.1.2.1.1.1.0
SNMP::Info::_global(description) Timeout at /usr/bin/netdisco line 1418
SNMP::Info::specify() - Could not get info from device at
/usr/bin/netdisco line 1418
   Can't connect to 172.17.117.9
! Device Not Supported or I can't connect to it via SNMP.


root@netdisco:~# snmpbulkwalk -v3 -lauthPriv -uinitial -aMD5 -Anetdisco
-xDES -Xnedisco -mALL 172.17.117.9

SNMPv2-MIB::sysDescr.0 = STRING: HP Comware Platform Software, Software
Version 5.20.99 Release 2220P02
HP A5500-48G EI Switch with 2 Interface Slots
Copyright (c) 2010-2013 Hewlett-Packard Development Company, L.P.
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.25506.11.1.25
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (69778676) 8 days,
1:49:46.76
SNMPv2-MIB::sysContact.0 = STRING: x
SNMPv2-MIB::sysName.0 = STRING: NET0500
SNMPv2-MIB::sysLocation.0 = STRING: PN1-S
SNMPv2-MIB::sysServices.0 = INTEGER: 78
IF-MIB::ifNumber.0 = INTEGER: 58
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
...





------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk



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





--- End Message ---
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to