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: report - ip inventory issue (Oliver Gorwits)
2. Re: Juniper FAN and PS info (Oliver Gorwits)
3. Re: discover stalls during lldp related snmp query with OID
".1.0.8802.1.1.2.1.4.1.1.11 (Oliver Gorwits)
4. Re: Fw: Checkpoint VSX (Oliver Gorwits)
5. Re: Problem with Netdisco device discovery (Oliver Gorwits)
--- Begin Message ---
Hi Brian
On 2017-10-25 15:00, Cuttler, Brian R (HEALTH) wrote:
Reviewed with my manager. The switches are in the discover_only range,
that is the end point switches but not the site router.
The switches have port-to-MAC address mappings, and the router has
MAC-to-IP mappings. So the router must also be discovered by Netdisco to
complete the data and allow the inventory report to run.
The router needs to support SNMP and have the tables. So it depends what
model you're using and so on.
regards,
oliver.
I have been corrected in that discover_only is not for end use IP
range discovery, which in retrospect makes sense.
Why if the switch is being learned don’t the end point devices not
show up in IP inventory report as it does else where in my network?
thank you,
Brian
FROM: Cuttler, Brian R (HEALTH) [mailto:brian.cutt...@health.ny.gov]
SENT: Wednesday, October 25, 2017 9:35 AM
TO: Hans Erasmus <erasmushan...@gmail.com>
CC: netdisco-users@lists.sourceforge.net
SUBJECT: Re: [Netdisco] report - ip inventory issue
_ATTENTION: This email came from an external source. Do not open
attachments or click on links from unknown senders or unexpected
emails._
Good morning Hans,
The switches that host the end points are in the 10.56.69.0 range, the
site router is as well.
The end point switches are being discovered and display switch
interface information that includes IPs in the range what I am trying
to get an IP Report on. I’m thought once the interface information
was included in the rancid database there would be enough there to
generate a report on the IP range.
If I have the switches, don’t I have the data? Do I also need to
discover the site’s router?
thank you,
Brian
_ATTENTION: This email came from an external source. Do not open
attachments or click on links from unknown senders or unexpected
emails._
This might seem like a silly question, but what are the IP's of the
routers containing the ARP tables for said subnet? If your router has
an IP address of 10.57.57.254 for instance, which is within the /23
but falls outside the scope of the /24, it will not be discovered. It
might also be that one of the other segments carries a /24 route in
stead of a /23 route, and this was discovered by Netdisco previously,
and because the 2 overlap, it is being ignored? I am not sure, I just
throwing out ideas here.
Regards
Hans
On Tue, 24 Oct 2017 at 22:31 Cuttler, Brian R (HEALTH)
<brian.cutt...@health.ny.gov> wrote:
Hello netdisco users.
I start with an apology, now that am writing you I realize I don't
know exactly what version I'm running, doesn't seem to be a button
or file to tell me that, though I am running netdisco2 rather than
netdisco.
Platform is FreeBSD 9.3.
Netdisco is terrific, could hardly go a day with out, however now
that I'm moving the last of my buildings to dynamic DNS I wanted to
pull an ip inventory for the network in use there. This is the
smallest building and supports only a /23 network and I manage only
3 switches there, else I'd have probably noted the issue sooner.
Issue is that what I ask for a report "ip inventory" and specify
the network 10.57.56.0/23 [1] I get zero results back, despite being
able to see addresses in that range when I examine the individual
switches.
I'd thought I needed to modify the ~/environment/deployment.yml
file, but process of elimination makes me second guess myself on
that.
Specifically, the file contains 10.57.56.0/24 [2] in the
discovery_only section, and those nodes do not show up.
I have other network ranges that are similarly mistakes, a /24 when
there should be a /21, but all found. And I have other ranges that
are not listed at all that display correctly.
So, I'm thinking I either don't know what I'm doing in the
deployment.yml file (likely) or perhaps I have a serious problem
(seems unlikely).
Removing and re-discovering one of the switches involved did not
seem to make any difference.
Thanks in advance for your help.
Brian Cuttler
Wadsworth Center
Albany, NY
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [3]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users [4]
Links:
------
[1] http://10.57.56.0/23
[2] http://10.57.56.0/24
[3] http://sdm.link/slashdot
[4] 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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Davide
Do you want hardware information or status/health information on the FAN
and PS?
regards,
oliver.
On 2017-11-20 15:07, Davide Garofalo wrote:
Juniper EX2000 and EX4000 series.
2017-11-20 16:06 GMT+01:00 Davide Garofalo
<davide.garof...@gmail.com>:
Hi all,
anybody know how i can get information about FAN and PS from my
juniper switches??
I found this from snmpwal:
[netdisco@netdisco Info]$ snmpwalk -v2c -cXXXX Y.Y.Y.Y
1.3.6.1.4.1.2636.3.1.6.1.6
SNMPv2-SMI::enterprises.2636.3.1.6.1.6.1 = STRING: "chassis frame"
SNMPv2-SMI::enterprises.2636.3.1.6.1.6.2 = STRING: "Power Supply
slot"
SNMPv2-SMI::enterprises.2636.3.1.6.1.6.4 = STRING: "FAN slot"
SNMPv2-SMI::enterprises.2636.3.1.6.1.6.7 = STRING: "FPC slot"
SNMPv2-SMI::enterprises.2636.3.1.6.1.6.8 = STRING: "PIC slot"
SNMPv2-SMI::enterprises.2636.3.1.6.1.6.9 = STRING: "Routing Engine
slot"
--
DAVIDE GAROFALO
--
DAVIDE GAROFALO
------------------------------------------------------------------------------
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 Giorgio,
On 2018-01-12 18:04, Giorgio Bagnato wrote:
Hi all,
After installing Netdisco version 2.38.5, I run a discover on devices
of my network.
During discover, when netdisco execute the lldp related snmp query
with OID ".1.0.8802.1.1.2.1.4.1.1.11", the process stalls.
My first impression is that this is a bug in the SNMP LLDP
implementation on your devices. What is the device model/platform and
software version you're using? Have you asked your vendor about this?
See also:
http://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?oid=1.0.8802.1.1.2.1.4.1.1.11
regards,
oliver.
I tried to repeat the same query with snmpwalk directly from command
line and I got the same behaviour.
But if I add ".0" at the end of the OID and then I execute the snmp
query with the OID ".1.0.8802.1.1.2.1.4.1.1.11.0" instead of
".1.0.8802.1.1.2.1.4.1.1.11" everything is all right and discover
process goes on.
It seems that the correct OID is ".1.0.8802.1.1.2.1.4.1.1.11.0" but
netdisco uses by default ".1.0.8802.1.1.2.1.4.1.1.11" .
As workaround I disabled lldp on all devices.
The question is:
- can I configure netdisco discover step to use OID
".1.0.8802.1.1.2.1.4.1.1.11.0" (with ".0" at the end) instead of OID
".1.0.8802.1.1.2.1.4.1.1.11" ?
- if not, is it possible to patch netdisco to use the right OID
".1.0.8802.1.1.2.1.4.1.1.11.0" ?
Thanks,
Giorgio
------------------------------------------------------------------------------
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 Michael
That sounds like a tricky deployment! Thanks for the feedback and yes
you are right - virtual contexts, VRFs, etc are going to require some
significant development in netdisco, but it is something we want to do
eventually.
By the way, we have a new, experimental support for Check Point SNMP
here:
https://metacpan.org/pod/SNMP::Info::Layer3::CheckPoint
It does require a reconfiguration on the CP, but if you can get it
working, please let us know!
regards,
oliver.
On 2017-11-03 18:49, Michael Butash wrote:
Working with a customer and doing some discovery/topology polling, I
ran into this with VSX as well, and remembered this thread...
So much the same issue, VSX cluster (cp41k), and since hitting the
same management IP, but needing multiple v3 contexts to do so, I can't
get Netdisco to see them as separate devices/instances. I can get
the contexts to return proper data, but ND only sees a single ip to
snmpv3 device vs as +1 host.
Once it learns the first community/context to poll the device, it
sticks with that, and only uses that v3 setup ever again, never
increments to try another v3 setup with a different context to get
_all_ the vsx instances. Even commenting the prior context-based v3
setup it'll never try it again with a different context setting.
Seems ND needs a craftier setup to instantiate around v3 contexts on
the same IP address for checkpoint. I can't much imagine any other
reasonable management tool works with them either without some serious
hacks, but might be worth considering for a ND feature add for the
poor folks stuck with these abysmal Checkpoints...
-mb
On Thu, Jun 26, 2014 at 11:36 PM, Veeramachaneni <t...@yahoo.com>
wrote:
Dear All,
Still now there is no improvement on this issue.
Is there any alternative method to manually update ARP table.
Regards,
T9En
----- Forwarded Message -----
FROM: Veeramachaneni <t...@yahoo.com>
TO: "netdisco-users@lists.sourceforge.net"
<netdisco-users@lists.sourceforge.net>
SENT: Friday, 24 January 2014 3:13 PM
SUBJECT: Checkpoint VSX
Dear All,
I have successfully installed ND-2 in my environment. But , for
moving to production I'm facing an issue with ND2 & checkpoint
VSX.
Checkpoint VSX (virtual firewalls) supports SNMP-V3 and i am able to
discover the device with SNMP-v3. To do ArpNip it need to use
context number. ND2 is doing ARPNIP to default context only. In the
said VSX box i'm having total 9 contexts. How can i do ArpNip to all
available context.
the default ArpNip is feteching "snmpbulkwalk -v 3 -l authNopriv -u
netdisco -A netdisco 192.168.1.1 atPhysAddress" this output.
But i require "snmpbulkwalk -n ctxname_vsid4 -v 3 -l authNopriv -u
netdisco -A netdisco 192.168.1.1 atPhysAddress" and all contexts.
I tried configuring context_prefix in snmp_auth but no use.
Regards,
T9en
------------------------------------------------------------------------------
Open source business process management suite built on Java and
Eclipse
Turn processes into business applications with Bonita BPM Community
Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft [1]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users [2]
Links:
------
[1] http://p.sf.net/sfu/Bonitasoft
[2] 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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Ted
I have not seen this error before, and at first glance it is within the
Net::DNS distribution, which is one of Netdisco's dependencies, rather
than Netdisco itself.
Let's make sure you have the latest version. Please run:
~netdisco/perl5/bin/localenv cpanm Net::DNS
And then try to discover the device again?
regards,
oliver.
On 2018-01-22 19:40, tbucha...@vinu.edu wrote:
I am running Netdisco on CentOS 6.9 fully updated and recently had an
error appear when trying to discover a newly configured device on the
network. I say "newly configured device" since it is possible (I can
not confirm) that this switch was on the network and in Netdisco
previously.
Netdisco details are here:
Software Version
App::Netdisco 2.38.28
SNMP::Info 3.39
DB Schema 46
PostgreSQL 8.4.20
Perl 5.10.1
When performing a discover on the device IP address, the process fails
and the error below appears. This is actually copied from the
Undiscovered Neighbors report so Netdisco does correctly identify the
device.
id: dh-231-2960S type: cisco WS-C2960S-48FPS-L Modification of a
read-only value attempted at
/home/netdisco/perl5/lib/perl5/x86_64-linux-thread-multi/Net/DNS/Resolver/Base.pm
line 223.
Any assistance in troubleshooting/correcting this problem is greatly
appreciated.
--
Ted Buchanan
Computer/Network Analyst - Vincennes University
tbucha...@vinu.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 ---
------------------------------------------------------------------------------
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
