I've mapped the entire L1 Physical Ethernet aggregation network for Telecom at one stage with graphviz and .dot (which netdot makes use of extensively). The trick is formatting Edge and Node Labels in a logical fashion and using a render mode and viewer that is appropriate to the size of the Directed Graph. I found using Hover I don't realistically think that any automatic tool is going to manage fully readable/usable output beyond a few dozen nodes without manual tweaking of label offsets etc. Like I said I ended up crafting .dot files through a few bash/gawk scripts out of CSV exports which allowed me to create rules as required for pretty and readable graphviz / .dot files. -Joel On 29 July 2014 11:18, Michael Fincham <michael(a)hotplate.co.nz> wrote:
On Tue, 29 Jul 2014 11:14:00 +1200, Joel Wirāmu Pauling wrote:
I have used graphviz and .dot files manually populated from CSV exports in the past with pretty good results. https://osl.uoregon.edu/redmine/projects/netdot/wiki , http://www.graphviz.org/Documentation/dotguide.pdf
I had a go at mashing up netdot w/ some graphs generated by parsing the XML versions of Juniper configs pulled by RANCID. It did not go especially well :)
I got the impression netdot was better suited to mapping fairly small networks. Mapping our "whole" network made a huge output with low readability.
-- Michael
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog