<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 27/07/2012 2:32 PM, Paul Gear wrote:<br>
</div>
<blockquote cite="mid:501219E5.4010406@libertysys.com.au"
type="cite">
<div class="moz-cite-prefix">On 27/07/12 12:32, Christopher
Pollock wrote:<br>
</div>
<blockquote
cite="mid:CAK6biYjHBQbDpLzq-E5jW_9RF6YVfAGUdVbzJrHDoM7eLxvNuw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
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>
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.</blockquote>
<br>
Most of the stuff I've seen in this area is template driven design,
so all the switch configuration auto generated and consistent.<br>
</body>
</html>