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. cleaning vlan inventory (Eric Doutreleau)
2. Re: cleaning vlan inventory (Oliver Gorwits)
3. Re: Netdisco an VRF's (Oliver Gorwits)
4. Re: Ubiquiti EdgeRouter (Oliver Gorwits)
5. Re: Avaya phones serial nr and new mibs ? (Oliver Gorwits)
6. Re: Netdisco an VRF's (Cardinal-Richards, Emma)
--- Begin Message ---
Hi
i m using App::Netdisco 2.034002
and i have problem with the vlan inventory.
I found in this inventory some vlan that doesn't exist anymore.
for example if i click on the name or the number of this kind of vlan to
list in which switch i can find them i got
the following message No matching records.
Is there a way to trmove them from the inventory?
--- End Message ---
--- Begin Message ---
Hi Eric,
On 2017-02-18 14:01, Eric Doutreleau wrote:
i m using App::Netdisco 2.034002
and i have problem with the vlan inventory.
I found in this inventory some vlan that doesn't exist anymore.
Normally when a device is discovered, the associated VLANs should be
scrubbed and reinserted to the database, so I don't know how this came
about (unless it's very old data from an earlier version).
You can delete all rows in the device_vlan and device_port_vlan, and
then run a discoverall job to rediscover all devices. That should clean
the data.
regards,
oliver.
for example if i click on the name or the number of this kind of vlan
to
list in which switch i can find them i got
the following message No matching records.
Is there a way to trmove them from the inventory?
------------------------------------------------------------------------------
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 Sassan,
The short answer is that Netdisco is not VRF-aware so I don't think
there's a way to get this to work.
It has long been on the wishlist but is a significant patch and we've
not had anyone step forward to try. I can give some pointers if anyone
is interested (I suggest opening a ticket or wiki page on github to
discuss, but only if there is genuinely the time to commit to
implementing).
As an aside, Netdisco caches the community last used to successfully
connect to a device, so this is why you have not be able to test
collecting per-VRF IPs by editing deployment.yml. The way to do this is
to delete the device then re-discover and re-arpwalk.
regards,
oliver.
On 2017-02-14 14:49, Sassan Dibadj wrote:
We are currently transitioning to having two main VRF's for our
network here and since about November netdisco is no longer pulling IP
arp information on the non-default VRF.
I did some research and added as second context along with a second
community name and I am able to pull the second VRF's IP's via
snmpwalk when querying the other community name.
I updated the netdisco deployment.yml to include the new community
name and even tried making it the first one it tries but it seems like
I still only get back IP ARP information on the default VRF.
We are running Cisco 7k Nexus platform and this is what I added to the
cores.
snmp-server context clinical vrf clinical
snmp-server community xxxxxxxx ro
snmp-server mib community-map xxxxxx context clinical
SNMP walk I was using is below. If I use the regular community name it
pulls the default VRF's ARP and if I change it to the new community
name it pulls the non-default VRF's IP's.
snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
Is there something I can do to make netdisco pull this info again?
Thank you,
-------------------------
UT Southwestern
Medical Center
The future of medicine, today.
------------------------------------------------------------------------------
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 Bernhard,
On 2017-02-13 22:46, Bernhard Marker wrote:
Is it possible to add new Ubiquiti Devices?
Like EdgeRouter X,X-sfp or EdgePoint R6,R8.
Looks like we have a couple of tickets open on this topic:
Identification of the device class:
https://github.com/netdisco/snmp-info/issues/144
Wireless nodes: https://github.com/netdisco/netdisco/issues/230
If neither of them are what you'd like, please open a new ticket
(probably best in the snmp-info tracker:
https://github.com/netdisco/snmp-info/issues)
regards,
oliver.
This Devices have Layer3 support, and atm in NetDisco2 the compatible
devices from Ubiquiti are only Accesspoints (L2).
Thank you very much.
BR
Bernhard
------------------------------------------------------------------------------
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 Jethro and Lubomír,
I remembered that we have a nice feature to help with VoIP handsets with
PCs connected, and other situations where you have LLDP/CDP connected
device without SNMP tables. It allows the handset to be discovered but
allows the MACs to gather on the upstream switchport at the same time
(normally not done once a downstream device is suspected).
macsuck_unsupported and macsuck_unsupported_type
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Configuration.pod#macsuck_unsupported
Hope this helps!
regards,
oliver.
On 2017-02-02 09:47, Jethro R Binks wrote:
VoIP handsets are also "device-like" in other ways as well: they often
run
LLDP, take in tagged and untagged VLANs, and often have a pass-through
port for a connected PC so they are a bit bridgy-like too. But agree
they
often don't run SNMP so you can't necessarily get at the info that
might
be in them!
Here, I get the handsets number via its LLDP announcements, which I can
see from the switch.
Because they LLDP but don't SNMP, they show up as Inaccessible
neighbours
in Netdisco (for me).
Jethro.
. . . . . . . . . . . . . . . . . . . . . . . .
.
Jethro R Binks, Network Manager,
Information Services Directorate, University Of Strathclyde, Glasgow,
UK
The University of Strathclyde is a charitable body, registered in
Scotland, number SC015263.
On Thu, 2 Feb 2017, Oliver Gorwits wrote:
Hi Lubomír,
On 2017-02-02 08:13, Černý Lubomír wrote:
> We have several Avaya VoIP phone and would like to get inventory in
> Netdisco2.
>
> I tried to add new mib into ~/netdisco-mibs/ but discover is still not
> able to get serial number.
In Netdisco, telephones are treated as "nodes" that are end-devices
such
as workstations or printers. This page explains the difference between
nodes and devices:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
So Netdisco only gets details such as serial number from the devices.
Nodes are only an IP/MAC-address entry.
I think Netdisco could possibly treat phones as devices (it's not
common
for phones to have SNMP enabled, though), but it would need support in
the SNMP::Info library first.
regards,
oliver.
> No SN even for mibs included in Netdisco package aka Avaya 46xx and
> 96xx
>
> New mibs for 16xx are on:
> ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt [1]
>
> Any idea why netdisco can not read SN from Avaya ? The value can be
> read via snmpget.
>
> Thx.
>
> Lubomir
>
>
>
> Links:
> ------
> [1] ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt
>
> ------------------------------------------------------------------------------
> 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
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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 ---
In the meantime... I've got Netdisco to discover the ARP information from our
multiple data centre VRFs using the method as described in the attached older
Netdisco mailing list post.
Regards,
Emma
> -----Original Message-----
> From: Oliver Gorwits [mailto:oli...@cpan.org]
> Sent: 19 February 2017 11:52
> To: netdisco-users@lists.sourceforge.net
> Subject: Re: [Netdisco] Netdisco an VRF's
>
> Hi Sassan,
>
> The short answer is that Netdisco is not VRF-aware so I don't think
> there's a way to get this to work.
>
> It has long been on the wishlist but is a significant patch and we've
> not had anyone step forward to try. I can give some pointers if anyone
> is interested (I suggest opening a ticket or wiki page on github to
> discuss, but only if there is genuinely the time to commit to
> implementing).
>
> As an aside, Netdisco caches the community last used to successfully
> connect to a device, so this is why you have not be able to test
> collecting per-VRF IPs by editing deployment.yml. The way to do this is
> to delete the device then re-discover and re-arpwalk.
>
> regards,
> oliver.
>
> On 2017-02-14 14:49, Sassan Dibadj wrote:
> > We are currently transitioning to having two main VRF's for our
> > network here and since about November netdisco is no longer pulling IP
> > arp information on the non-default VRF.
> >
> > I did some research and added as second context along with a second
> > community name and I am able to pull the second VRF's IP's via
> > snmpwalk when querying the other community name.
> >
> > I updated the netdisco deployment.yml to include the new community
> > name and even tried making it the first one it tries but it seems like
> > I still only get back IP ARP information on the default VRF.
> >
> > We are running Cisco 7k Nexus platform and this is what I added to the
> > cores.
> >
> > snmp-server context clinical vrf clinical
> >
> > snmp-server community xxxxxxxx ro
> >
> > snmp-server mib community-map xxxxxx context clinical
> >
> > SNMP walk I was using is below. If I use the regular community name it
> > pulls the default VRF's ARP and if I change it to the new community
> > name it pulls the non-default VRF's IP's.
> >
> > snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
> >
> > Is there something I can do to make netdisco pull this info again?
> >
> > Thank you,
> >
> > -------------------------
> >
> > UT Southwestern
> >
> > Medical Center
> >
> > The future of medicine, today.
> >
> >
> > ------------------------------------------------------------------------------
> > 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
>
> ------------------------------------------------------------------------------
> 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
--- Begin Message ---
Hi Christian,
That's very nice! I´ve also tested it and it works fine! Thanks a mil for this
litte "christmas" present.
That makes the nexus discovery with vrf more easy and thus doesn´t require a
complex snmp config.
Sebastian
-----Ursprüngliche Nachricht-----
Von: Christian Ramseyer [mailto:r...@networkz.ch]
Gesendet: Mittwoch, 9. Dezember 2015 20:58
An: Sebastian Rösch <roe...@alcera.de>
Cc: Jeroen van Ingen <j.vaningensche...@utwente.nl>;
netdisco-users@lists.sourceforge.net
Betreff: Re: [Netdisco] Best way to discover Cisco Nexus N5K
On 08/12/15 13:42, Sebastian Rösch wrote:
> exactly, currently I have different snmp communites for each vrf.
> My favorite way would be to fetch the addresses with the ssh collector,
> because you there is a command in nexus for showing all vrf´s content:
> "show ip arp vrf all". That would be great... because I could remove all the
> additional devices I´ve just added for arpnipping the different vrf´s.
> But so far I wasn´t able to add another device type as described here, I´m
> not very familiar with all that perl stuff.....
> http://search.cpan.org/~oliver/App-Netdisco/bin/netdisco-sshcollector
>
> What do I need to do for this?
Hi Sebastian & List
Here is a module that I just made and tested on a N5kC5596Up. You must store
the file in lib/perl5/App/Netdisco/SSHCollector/Platform/NXOS.pm
(there's already all the other platform-specific .pm files there), then
reference it in deployment.yml like this:
sshcollector:
- hostname: 'n5.example.com'
user: whatever
password: topsecret
platform: NXOS
Maybe Olvier or another Netdisco dev can add it to the distro for future
releases.
Hope that helps
Christian
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- 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
