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: VLAN Port Map Device Tab (Nick Nauwelaerts)
--- Begin Message ---
wow, seems you spent spent quite some time on netdisco customization.

i even have a use for the port to device layout part, since i'm in the same 
boat with electrical trained technicians (also plc stuff) that are now forced 
to also have some idea of how computer stuff works.

so first things first, i guess you alrdy found that way to our github page. i 
hope you had a look at the wiki there? 
(https://github.com/netdisco/netdisco/wiki) if i do say so myself the docs for 
web or other extensions/plugins are well maintained and offer advice on how to 
organize your extra code. i think the first step would be to just publish the 
code you wrote, perhaps with a few pointers to things you hardcoded or took 
shortcuts on so those can be refactored.

now, netdisco alrdy pulls in a ton of perl modules, so for connecting to 
external systems (like rancid configs, or as you mentioned things like mrtg 
etc) the prefered way will be to create an external module. we have 2 of those 
atm, once that links to rancid config dumps 
(https://github.com/netdisco/nd2-web-plugin-rancid) & one that does something 
with observium (not sure if this one is still current). the benefits of having 
them as external modules is reducing core code/dependency bloat & having plugin 
specific config stuff not in the default config we ship.
items that only need base netdisco can most likely be integrated if they're not 
too device/vendor specific.

feel free to link your code as is, we have devs that have been working on 
netdisco for close or over 10 years so they can most likely deduce what the 
intent was (since you stated you used an "old & patched" netdisco version :) )

we also slack on irc:  #netdisco@freenode   - 
https://webchat.freenode.net/?randomnick=1&prompt=1&channels=%23netdisco
do allow a few hours (or days) for replies . most of us use bouncers so your 
message will not get lost.



as for the snmp::info force10 issue, the module has some vlan 
override/remapping code in it. perhaps this is no longer relevant for newer 
versions of ftos. feel free to open an issue on github for this 
(https://github.com/netdisco/snmp-info/issues/new) or hit is up on irc. this 
will require some data dumps of the whole device or at least the relevant mibs. 
we have a writeup on that here: 
https://github.com/netdisco/snmp-info/wiki/Simulating-Agents , this also 
mentions all the possible privacy issues and how we handle your data (bottom 
line: if it's private stuff we promise not to leak it...)


looking forward to hearing of you!

// nick


From: brian via netdisco-users [mailto:[email protected]]
Sent: Wednesday, January 29, 2020 21:26
To: [email protected]
Subject: [Netdisco] VLAN Port Map Device Tab


Hello list,

Not sure if this is of interest to anyone, but after being on my personal to-do 
list since the Netdisco 1 days, I have finally put together a pm/tt device tab 
to render a visual representation of the port state and VLAN info for switches.

But first there are VERY BIG PROBLEMS with it

   -It only works reliably for the subset of HP Procurve/Aruba and Cisco switch 
models that we have where I work

   -Code is garbage and would need major refactoring to be more flexible 
(Module lettering and stack numbering is poorly hardcoded, and vlan names are 
in a big switch/case statement. Lots of bad manual portname cleanup in both 
perl and TT)

   -It is developed against an old, heavily patched version of Netdisco and I 
haven't tested it against mainline...I constantly curse myself for not trying 
harder to get my patches accepted back into the main project

That said, it does some neat stuff that might be useful. We find field techs 
and related technical staff (electrical/PLC groups) find the data to be very 
useful when planning and carrying out work.

   -Renders based on one of: Serial port numbering, Module letter and port 
number and zero or one based cisco stack type numbering (0/5, 2/8 etc)

   -Lists all VLANs and auto colours them. Gives name or fixed colour if 
specified in the TT file. Trunks to other devices and Link aggregation groups 
are treated separately. Nice visual indication of STP blocking links

   -Has popup port info on hover over

   -clicks onto ports that advertise an IP via LLDP will go to that device's 
netdisco portmap, so you can navigate thru the network visually

It may be preferable to take the description and images that I've attached and 
use them as a mockup and reimplement from scratch avoiding my hacky code, but I 
can provide them if anyone wants them.

I also have a bunch of other plugins/integrations/improvements I'd like to get 
into mainline and source control if anyone is interested. The main ones are 
NFSen/NFDump, Graylog, SCCM, Smokeping, MRTG, a tools menu, Guacamole and 
(enhanced) RANCID. I have scripts that drive the configuration automagically 
from the netdisco db for all those tools.

(One other aside: the force10 vlan stuff is totally broken in SNMP-info, so I'm 
processing the RANCID config file with a bash script that generates SQL and 
building the port-vlan info from that after each device discover. I can also 
make that available if anyone needs it)

Thanks!



   -Brian Marshall

________________________________

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> | 
Instagram<https://www.instagram.com/aquafin_nv/>

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>.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

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

Reply via email to