Hi Paul,<div><br></div><div>Fancy seeing you here :) </div><div><br></div><div>I think most of us have spent at least some time doing enterprise/campus type work, and to a certain extent I've seen people want a lot of information but yeah I think there was some confusion about what was trying to be performed.<div>
<br></div><div>There are any number of programs that will walk your network and pull out information using various methods, but yeah what you do with that then is another kettle of fish entirely. As Mark and a few others mention, scripting is part of our job and I think the right answer is modifying an existing tool to pull out the data you want.</div>
<div><br></div><div>Taking a moment to pimp Andrew Fort again, he suggested a while back that there's value in writing your own NMS that can do exactly what you want to it to, and had a bunch of time-saving tips that he'd picked up along the way. Depending on the size of the network and how much you want to visualise, there's merit in at least considering some of them! Like adding an understanding of how to figure out what VLANs are on what port depending on the type of device, and making sure they marry up. Easy on some devices, not so easy on others.</div>
<div><br></div><div>I suppose network configuration is such a wide and varied thing that it's difficult to model all useful configuration so it's really up to us to decide what we need to capture and model it ourselves.</div>
<div><br></div><div>--<br>Christopher Pollock,<br>io Networks Pty Ltd.<div>e. <a href="mailto:chris@ionetworks.com.au" target="_blank">chris@ionetworks.com.au</a><br>p. 1300 1 2 4 8 16</div><div>d. 07 3188 7588</div><div>
m. 0410 747 765</div><div>skype: christopherpollock</div><div><a href="http://twitter.com/chrisionetworks" target="_blank">twitter.com/chrisionetworks</a></div><div><div><a href="http://www.ionetworks.com.au" target="_blank">http://www.ionetworks.com.au</a><br>
In-house, Outsourced.</div></div><br>
<br><br><div class="gmail_quote">On Fri, Jul 27, 2012 at 2:32 PM, Paul Gear <span dir="ltr"><<a href="mailto:ausnog@libertysys.com.au" target="_blank">ausnog@libertysys.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
<div>On 27/07/12 12:32, Christopher Pollock
wrote:<br>
</div>
<blockquote type="cite">
I suppose the short answer is that this is a fairly bespoke
requirement. I can't think of a time I've ever thought to try to
do this.</blockquote>
<br></div>
Hi Chris,<br>
<br>
Really? I can understand it being fairly unimportant in the service
provider world, but would have thought it's what every enterprise,
campus, or data centre network engineer would want to know (in many
cases, would <i>have</i> to know) about his or her network.<br>
<br>
Perhaps i muddied the waters by talking about producing a script to
perform the VLAN manipulations. If the data were provided in an
appropriate form, producing a script would be a trivial exercise, so
let's assume that i don't care about that for the moment.<br>
<br>
Is there possibly a better place to ask - a list more
enterprise/campus-oriented? I find it really hard to believe that
no one else wants to know this.<br>
<br>
Regards,<br>
Paul<br>
<br>
P.S. Looking forward to talking more about this in person next
week... <span><span> :-) </span></span><br>
</div>
<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></blockquote></div><br></div></div>