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: Can I easily patch Netdisco or SNMP to add neighbors?
([email protected])
2. Re: Can I easily patch Netdisco or SNMP to add neighbors?
(Nick Nauwelaerts)
--- Begin Message ---
One reason I don't care for manual topology is one forgets to update it, but I
like this idea; rather than thinking of it as manual, I can have a set of them
which are generated by a script that pulls from the proprietary OID (and when
not generated in a run delete any of that type, identified by subnet or port
type or something).
Thank you. Sometimes the tool we need is laying in plain sight, unseen.
Thank you.
But... I'm still really curious about this feature to pull neighbors from eigrp
-- is there a on/off switch or something? Or documentation for how it should
be working?
Linwood
-----Original Message-----
From: Brian Marshall [mailto:[email protected]]
Sent: Friday, August 3, 2018 12:27 AM
To: [email protected]
Subject: Re: [Netdisco] Can I easily patch Netdisco or SNMP to add neighbors?
What I've done in the past for device classes that don't play nicely with lldp
or snmp for some reason, but that I can map in some other way, is to autocreate
entries in the manual topology table, eg :
insert into topology (dev1, port1, dev2, port2) values ('192.168.3.4',
'wlan0', '192.168.3.8', 'wlan0');
remember to create the link in both directions for netdisco to create
bidirectional links (unfortunately it won't fall back on the logical thing if a
link only exists in one direction)
you can script this via the psql command something like :
psql -c "insert into..."
you can put a sudo -u netdisco in front of the psql to execute as the netdisco
user and make the db permissions stuff easier
If you have an easy way to pull info, then processing it with grep/cut/sed/awk
and feeding it to xargs -n1 to drive psql or something works wonders with
little effort. I have dozens of scripts that feed into or are fed from the
netdisco DB.
On 08/02/2018 03:13 PM, [email protected] wrote:
> I'm feeling pretty dense here, but how does this become active? I
> wasn't aware it would use those protocols (note to self: Read the
> release notes!) I'm running that code, and use eigrp, and I don't
> see signs it is doing anything.
>
> For example, I have nodes connected over a microwave ring that passes
> eigrp and shows neighbors, but does not pass lldp or cdp. Shouldn't I
> see that as neighbors and connected devices from eigrp on the VLAN
> interface they connect to? I don't. I'd like to.
>
> Though it's an interesting question - I have other places where LLDP
> divisible devices are in between EIGRP neighbors, and don't really
> want to see them come up as connected.
>
> I tried briefly to see if there is control in deployment.yml or elsewhere.
>
> I can do (now that I see it) a show of -e eigrp_peers and get the
> right answers, but I don't see that info being used anywhere in terms
> of the neighbors display? Or ports (though the show doesn't show the
> VLAN interface).
>
> Thanks for pointing to this. Would love to understand it better.
>
> Linwood
>
>
> -----Original Message-----
> From: Nick Nauwelaerts [mailto:[email protected]]
> Sent: Thursday, August 2, 2018 4:07 PM
> To: [email protected]; [email protected]
> Subject: RE: [Netdisco] Can I easily patch Netdisco or SNMP to add
> neighbors?
>
> heya,
> while i'm far from the expert on this, i have a somewhat related todo
> item (netdisco should be able to map 2 stage routing dependencies
> iirc). as such, since you're talking about ip adresses i guess it's
> somehow routed or black box enough to be considered as routed.
>
> as such, perhaps its easiest to plug your data into:
> https://github.com/netdisco/netdisco/blob/master/lib/App/Netdisco/Work
> er/Plugin/Discover/Neighbors/Routed.pm
>
> and emulate ospf or bgp handling.
> https://metacpan.org/pod/SNMP::Info::Layer3 seems a plausible starting
> point for that.
>
>
> hopefully someone with a decent understanding of netdisco workings can
> comment.
>
> // nick
>
>
>
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, August 2, 2018 21:01
> To: [email protected]
> Subject: [Netdisco] Can I easily patch Netdisco or SNMP to add neighbors?
>
> We have a bunch of microwave devices (NEC iPaso) that do not behave
> nicely with LLDP, or pulling port info generally.
>
> But they do have an OID from which I can pull neighbors over the
> microwave network, it just provides a list of adjacent IP addresses,
> which correspond to discovered hosts, that it does on its own
> management microwave network. I can probably find the adjacent port
> as well (corresponding to the radios).
>
> Is there any easy way to inject such into Netdisco's discover (or
> whatever appropriate place)? or associated SNMP code? Currently the
> SNMP class is SNMP::Info::Layer2. The neighbor information is in a
> proprietary mib.
>
> I don't want to fork the snmp code to produce a class specifically for
> them, as (a) I've never done it and it's a lot of work, and (b) I
> can't do it publically as NEC won't release their MIB's except under NDA.
>
> I was wondering if there are any hooks in the code where one can
> easily add an additional call just for neighbor information, to a
> proprietary place?
>
> Yes, I know I can add manual topology, but the obvious risks of that
> are as changes occur, someone as to remember to go fix it.
>
> Linwood.
>
> PS. Would you consider flagging (color, icon, something) manual
> topology on the ports display and neighbor graph, so one can remember
> what they have done (and not) manually?
>
>
>
>
> ----------------------------------------------------------------------
> -------- 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
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> ________________________________
>
> Volg Aquafin op Facebook<https://www.facebook.com/AquafinNV> |
> Twitter<https://twitter.com/aquafinnv> |
> YouTube<http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?featur
> e=mhee>
> | LinkedIN<http://www.linkedin.com/company/aquafin/products>
>
> In het kader van de uitoefening van onze taken verzamelen we bij
> Aquafin persoonsgegevens. Hoe we omgaan met deze gegevens en wat de
> rechten van de betrokkenen zijn, kan je nalezen in onze privacy
> policy<https://www.aquafin.be/nl-be/privacy-policy>.
>
> [https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_capt
> ion/public/2018-06/email_banner_web.jpg]<https://www.aquafin.be/
> <https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_capt
> ion/public/2018-06/email_banner_web.jpg%5d%3chttps:/www.aquafin.be/>>
> P Denk aan het milieu. Druk deze mail niet onnodig af.
>
>
>
> ----------------------------------------------------------------------
> -------- 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
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
--- End Message ---
--- Begin Message ---
that's the part i still need to have a look took, on how to get that data. it's
hasnt been relevant to us yet since we're on managed mpls with all our sites
and i havent had time yet to check if we dont have the required access to get
the routing tables, or if the vrf configs are an issue, or if i just
misconfigured something, or any other number of reasons.
but since you said your devices are being labeled layer 2 devices, i guess
thats the first thing to look at. most of this seems to come from the info
netdisco gets from snmp::info, so that would be my starting point.
i've only dabbled a bit with this; but snmp::info does provide a way to test
against classes:
documentation for it here:
https://metacpan.org/pod/distribution/SNMP-Info/contrib/util/test_class.pl
you might be able to try & see if you get eigrp info with that & the right
snmp::info module.
// nick
From: [email protected] [mailto:[email protected]]
Sent: Friday, August 3, 2018 00:14
To: Nick Nauwelaerts <[email protected]>;
[email protected]
Subject: RE: [Netdisco] Can I easily patch Netdisco or SNMP to add neighbors?
I'm feeling pretty dense here, but how does this become active? I wasn't aware
it would use those protocols (note to self: Read the release notes!) I'm
running that code, and use eigrp, and I don't see signs it is doing anything.
For example, I have nodes connected over a microwave ring that passes eigrp and
shows neighbors, but does not pass lldp or cdp. Shouldn't I see that as
neighbors and connected devices from eigrp on the VLAN interface they connect
to? I don't. I'd like to.
Though it's an interesting question - I have other places where LLDP divisible
devices are in between EIGRP neighbors, and don't really want to see them come
up as connected.
I tried briefly to see if there is control in deployment.yml or elsewhere.
I can do (now that I see it) a show of -e eigrp_peers and get the right
answers, but I don't see that info being used anywhere in terms of the
neighbors display? Or ports (though the show doesn't show the VLAN interface).
Thanks for pointing to this. Would love to understand it better.
Linwood
-----Original Message-----
From: Nick Nauwelaerts [mailto:[email protected]]
Sent: Thursday, August 2, 2018 4:07 PM
To: [email protected]; [email protected]
Subject: RE: [Netdisco] Can I easily patch Netdisco or SNMP to add neighbors?
heya,
while i'm far from the expert on this, i have a somewhat related todo item
(netdisco should be able to map 2 stage routing dependencies iirc). as such,
since you're talking about ip adresses i guess it's somehow routed or black box
enough to be considered as routed.
as such, perhaps its easiest to plug your data into:
https://github.com/netdisco/netdisco/blob/master/lib/App/Netdisco/Worker/Plugin/Discover/Neighbors/Routed.pm
and emulate ospf or bgp handling. https://metacpan.org/pod/SNMP::Info::Layer3
seems a plausible starting point for that.
hopefully someone with a decent understanding of netdisco workings can comment.
// nick
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Thursday, August 2, 2018 21:01
To: [email protected]
Subject: [Netdisco] Can I easily patch Netdisco or SNMP to add neighbors?
We have a bunch of microwave devices (NEC iPaso) that do not behave nicely with
LLDP, or pulling port info generally.
But they do have an OID from which I can pull neighbors over the microwave
network, it just provides a list of adjacent IP addresses, which correspond to
discovered hosts, that it does on its own management microwave network. I can
probably find the adjacent port as well (corresponding to the radios).
Is there any easy way to inject such into Netdisco's discover (or whatever
appropriate place)? or associated SNMP code? Currently the SNMP class is
SNMP::Info::Layer2. The neighbor information is in a proprietary mib.
I don't want to fork the snmp code to produce a class specifically for them, as
(a) I've never done it and it's a lot of work, and (b) I can't do it publically
as NEC won't release their MIB's except under NDA.
I was wondering if there are any hooks in the code where one can easily add an
additional call just for neighbor information, to a proprietary place?
Yes, I know I can add manual topology, but the obvious risks of that are as
changes occur, someone as to remember to go fix it.
Linwood.
PS. Would you consider flagging (color, icon, something) manual topology on the
ports display and neighbor graph, so one can remember what they have done (and
not) manually?
------------------------------------------------------------------------------
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
[email protected]
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
________________________________
Volg Aquafin op Facebook<https://www.facebook.com/AquafinNV> |
Twitter<https://twitter.com/aquafinnv> |
YouTube<http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?feature=mhee> |
LinkedIN<http://www.linkedin.com/company/aquafin/products>
In het kader van de uitoefening van onze taken verzamelen we bij Aquafin
persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de
betrokkenen zijn, kan je nalezen in onze privacy
policy<https://www.aquafin.be/nl-be/privacy-policy>.
[https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_caption/public/2018-06/email_banner_web.jpg]<https://www.aquafin.be/<https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_caption/public/2018-06/email_banner_web.jpg%5d%3chttps:/www.aquafin.be/>>
P Denk aan het milieu. Druk deze mail niet onnodig af.
--- 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
