It's great to see all this discussion about network mapping tools. Having up to date maps is crucial in support the infrastructure. <br>I recently completed a infrastructure map, (4 in fact). I had only wished this post came about before I started. Used Visio, god I hate it!!! Will play around with yED.<br>
<br>Cheers,<br><br>Ivan Jukic<br><br><br><div class="gmail_quote">On 19 September 2011 15:39, Andrew Fort <span dir="ltr"><<a href="mailto:afort@choqolat.org">afort@choqolat.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sun, Sep 18, 2011 at 9:41 PM, Simon Knight <<a href="mailto:simon.knight@gmail.com">simon.knight@gmail.com</a>> wrote:<br>
> yEd is a free diagram drawing tool, comparable to Omnigraffle or<br>
> Visio. After tracing over 200 network maps for our Topology Zoo<br>
> project, I prefer yEd whenever I have to use OmniGraffle for drawing<br>
> diagrams (and doesn't have the price tag)<br>
> <a href="http://www.yworks.com/en/products_yed_download.html" target="_blank">http://www.yworks.com/en/products_yed_download.html</a><br>
><br>
> On a related note, I am very interested in the requirements network<br>
> operators have for both network drawing and network visualisation<br>
> tools. Joel Obstfeld from Juniper spoke briefly about some of the<br>
> stuff we are doing at the University of Adelaide with regards to<br>
> network design and configuration. Our aim would be to take a network<br>
> diagram from something like yEd, Visio or Omnigraffle, and construct<br>
> the network configuration from this. We are part way into this process<br>
> - we can generate working configurations from a network diagram - and<br>
> would like to get some input from industry in terms of network design<br>
> and config tasks.<br>
<br>
</div>In my view, this sounds like a solution to the wrong problem.<br>
<br>
Have the network database provision your network resources, build the<br>
config, and the diagrams. Doing it the other way around seems to<br>
encourage divergence from your standards.<br>
<div class="im"><br>
> Visualisation is also a key part of network operations, and is<br>
> something we are also interested in.<br>
><br>
> Any feedback or input is welcomed - either on or off list.<br>
><br>
> Cheers<br>
> Simon<br>
><br>
><br>
> On Mon, Sep 19, 2011 at 1:57 PM, Matt Taylor <<a href="mailto:matt@mt.au.com">matt@mt.au.com</a>> wrote:<br>
>> On 19/09/2011 2:02 PM, Mark Newton wrote:<br>
>>><br>
>>> Playing around with Network Weathermap was what inspired me to<br>
>>> throw together this:<br>
>>> <a href="http://nodemap.internode.on.net" target="_blank">http://nodemap.internode.on.net</a><br>
>>><br>
>>> The website version hasn't been updated for quite a while, but it's<br>
>>> GPL so you can pick it up and run with it if you want.<br>
>>><br>
>>> - mark<br>
>><br>
>> Looks great, thanks for that link mate!<br>
>><br>
>> Matt.<br>
>><br>
>> _______________________________________________<br>
>> AusNOG mailing list<br>
>> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
>> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
>><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
<br>
<br>
<br>
</div><font color="#888888">--<br>
Andrew Fort (<a href="mailto:afort@choqolat.org">afort@choqolat.org</a>)<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br>