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: SSHCollector Issues (Graybeal, Andrew C.)
2. Re: ND2 LLDP discovery on Juniper EX series switches
(Miroslav Lednicky)
3. Re: ND2 LLDP discovery on Juniper EX series switches
(Miroslav Lednicky)
4. Re: ND2 LLDP discovery on Juniper EX series switches
(Oliver Gorwits)
5. Re: SSHCollector Issues (Oliver Gorwits)
6. Re: Arpnip polling L2 switches (Oliver Gorwits)
7. Error During Update (Bavo Seesink)
8. Re: IBM BNT device version number problem (Jeroen van Ingen)
--- Begin Message ---
Ok, so I got SNMP enabled on our test ASA. Discovered this device. Ran SSH
collector against it - and it works fine. I'll try the pseudo devices, but
knowing this works is probably enough to just enable SNMP on our production ASA.
Only thing is I never get any message that it actually worked. I see there's a
number of outputs in the ssh-collector script:
"[%s] arpnip - retrieved %s entries"
"arpnip - processed %s ARP Cache entries from %s devices"
"WARNING: no entries received from <$hostlabel>"
None of these outputs ever occur. If I revert to the original script (remove
the debugging I've added), the script still works, but it outputs nothing other
than "Connection to <IP-address> closed by remote host." Is this the intended
behavior?
I also could be completely wrong, but I couldn't find anything that says how
you're supposed to run the ssh-collector. I just have a cron job pointing at
~/bin/netdisco-sshcollector. Is this right?
Sorry about all these questions - Perl is not my strong suit.
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Wednesday, May 13, 2015 6:32 PM
To: [email protected]
Subject: Re: [Netdisco] SSHCollector Issues
On 2015-05-13 22:12, Graybeal, Andrew C. wrote:
> I don't believe so - we currently are not allowing Netdisco to poll
> the ASA with SNMP and also ASAs in general don't support CDP.
>
> Netdisco just sees the ASA as a node connected to devices that are
> discoverable.
Okay, thanks for answering anyway.
So, another thought... Netdisco has the concept of pseudo (fake)
devices that can be created to link together two other devices (e.g. a
hub, etc). You go to Admin -> Pseudo Device, and create the device.
First I'd try doing that and seeing if netdisco-sshcollector works.
If not... go into the database and change the vendor field in the
device table from "netdisco" to whatever you like. This changes the
device from pseudo to "real". Then also add that device to discover_no,
macsuck_no, arpnip_no. Then try the sshcollector again.
Good luck!
regards,
oliver.
--- End Message ---
--- Begin Message ---
Cody Wood <cwood@...> writes:
>
> I think I have LLDP set correctly on all the Juniper switches. I can run
'show lldp neighbors' while ssh'ed
> into a juniper switch and it outputs a list of all connected juniper and
cisco switches and routers and on
> what port they are connected.
>
> It does walk through my network and discovers all cisco devices fine.
>
> Thanks,
>
> Cody Wood
>
Hello,
I have the same problem.
I have switch ex3300, Junos 14.1X53-D25.2
If I have very simple configuration:
lldp {
interface all;
}
then command
show lldp neighbors
works OK, but netdisco writes:
SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype :
.1.0.8802.1.1.2.1.4.2.1.3
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
[9110] 2015-05-15 16:33:07 debug [10.0.0.1] neigh - CDP/LLDP not enabled!
After add management-address to lldp configuration:
lldp {
management-address 10.0.0.1;
interface all;
}
netdisco can find support for lldp but writes:
SNMP::Info::_load_attr lldp_rem_cap_spt : LLDP-MIB::lldpRemSysCapSupported :
.1.0.8802.1.1.2.1.4.1.1.11
[9365] 2015-05-15 16:51:40 debug [10.0.0.1] neigh - port for
IID:105105.603.1 not resolved, skipping
What can be wrong?
Thank you
Miroslav
--- End Message ---
--- Begin Message ---
Miroslav Lednicky <miroslav.lednicky@...> writes:
>
> Cody Wood <cwood <at> ...> writes:
>
> >
> > I think I have LLDP set correctly on all the Juniper switches. I can run
> 'show lldp neighbors' while ssh'ed
> > into a juniper switch and it outputs a list of all connected juniper and
> cisco switches and routers and on
> > what port they are connected.
> >
> > It does walk through my network and discovers all cisco devices fine.
> >
I found solution:
Configuration for correct interoperability Juniper EX switch and ND2:
lldp {
management-address 10.0.0.1;
port-id-subtype interface-name;
interface all;
}
Miroslav
--- End Message ---
--- Begin Message ---
On 2015-05-16 21:09, Miroslav Lednicky wrote:
I found solution:
Configuration for correct interoperability Juniper EX switch and ND2:
lldp {
management-address 10.0.0.1;
port-id-subtype interface-name;
interface all;
}
Many thanks, I've added a note to the Troubleshooting doc for the next
release.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Andrew,
On 2015-05-14 17:36, Graybeal, Andrew C. wrote:
Only thing is I never get any message that it actually worked. I see
there's a number of outputs in the ssh-collector script:
"[%s] arpnip - retrieved %s entries"
"arpnip - processed %s ARP Cache entries from %s devices"
"WARNING: no entries received from <$hostlabel>"
Sorry about that, the ssh collector script wasn't setting up its
logging environment correctly. I've fixed this, added some docs to the
script, and this will be in the next release.
I also could be completely wrong, but I couldn't find anything that
says how you're supposed to run the ssh-collector. I just have a cron
job pointing at ~/bin/netdisco-sshcollector. Is this right?
Yes, that's right, just use Cron. I've added this to the docs, sorry
once again.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Matt,
On 2015-05-14 15:01, Cavaness, Matt wrote:
I'm running into an issue where Arpnip is polling ARP tables on layer
2 switches. The result is that when admins SSH to the switch
management, Arpnip correlates the MAC address of the connected admin
to the MAC address of the upstream router.
In spite of this, the device info page only shows layer 2
capabilities.
I'm a little confused by what you say. So these problematic devices are
reported as *not* having Layer 3 in the Device Details tab, but Netdisco
queues an arpnip job for them?
It should be the case that you can test this by using the following
command:
~netdisco/bin/netdisco-do arpnip -d x.x.x.x
For example, I can do the following:
$ bin/netdisco-do arpnip -d x.x.x.x
[86657] 2015-05-17 20:54:39 info App::Netdisco version 2.032003
loaded.
[86657] 2015-05-17 20:54:39 info arpnip: started at Sun May 17
21:54:39 2015
[86657] 2015-05-17 20:54:40 info arpnip: finished at Sun May 17
21:54:40 2015
[86657] 2015-05-17 20:54:40 info arpnip: status done: Skipped arpnip
for device x.x.x.x without OSI layer 3 capability
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi all,
Sorry for the late response :-(
Thanks for helping.
When i change the directory where netdisco 2.0 is installed.
and update from there the install works.
I have an install script to install netdisco 2.0 and it is not installed with
root access.
It is not really a problem now i know. :-)
Thanks for the help.
Greetings
Palermo
--- End Message ---
--- Begin Message ---
On 05/12/2015 07:01 PM, Andy Ruhl wrote:
On Tue, May 12, 2015 at 8:35 AM, Jeroen van Ingen
<[email protected] <mailto:[email protected]>> wrote:
SNMP::Info determines what SNMP objects to query for each device, eg to
determine the os_ver.
Looks like all three IBM switch models are classified as
SNMP::Info::Layer3::IBMGbTor devices, which always requests the object
IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0
(.1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0) to determine the software version.
The IBM-GbTOR-10G-L2L3-MIB in netdisco-mibs however seems specific to
the G8124 model.
What MIBs should be used for models other than the G8124 ? They would
have to be included in netdisco-mibs and SNMP::Info has to be updated to
use the correct MIBs and objects for each model.
Thanks!
The G8052 and G8264 firmware comes with the MIB files. I put them in the
netdisco-mibs directory but I was unaware that I had to do something else.
I'm trying to figure out SNMP::Info but not getting very far. Can you
point me in the right direction?
It depends. Are the models similar enough to share most of the vendor
specific code or are they so different (eg completely different
operating system or acquired / OEM'ed from different companies) that
each model or group of models should be put in a separate device class?
For example: depending on the model, an HP switch is classified as
SNMP::Info::Layer2::HP4000 (old ProCurve models with only menu driven
interface), SNMP::Info::Layer2::HP (more current ProCurve models that
also have a CLI and differ in SNMP support), SNMP::Info::Layer2::HPVC
for VirtualConnect interconnects in blade chassis and
SNMP::Info::Layer3::H3C for HP switches running Comware operating system.
Without any information about the (dis)similarities between the
platforms and without seeing the MIB contents it's hard to advise or
assist you.
Can you provide a bit more background / info on the various models and
can you upload the MIBs that you'd need in a Sourceforge ticket for
netdisco-mibs ?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
--- End Message ---
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
