<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>I would suggest using a registered cabler who will adhere to the ACA Cabling Rules</div>
<div><br>
</div>
<div><a href="http://www.acrs.com.au/">http://www.acrs.com.au/</a><br>
</div>
<div><br>
</div>
<div>Cheers</div>
<div>Paul</div>
<div><br>
On 11/06/2013, at 5:45 PM, "Alan Maher" <<a href="mailto:alanmaher@gmail.com">alanmaher@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>I can sympathise with this scenario, having seen it only too often over</span><br>
<span>the years.</span><br>
<span>From the early morning call to establish why the network is down, and then to</span><br>
<span>wander around trying to establish which of the overnight cleaners "accidentally"</span><br>
<span>knocked out a co-ax terminator from the wall outlet in a token ring set up.</span><br>
<span>To the MD who thought that co-ax outlet might be an aerial input for his new</span><br>
<span>4.5" portable tv so he could watch the cricket.</span><br>
<span>To the many companies whose server set up just "growed like topsy" and live and dead</span><br>
<span>equipment lived alongside the biggest pile of spaghetti in the world.</span><br>
<span>Where modems and patch connections were all laying around the floor in a spare</span><br>
<span>office recently vacated by the photo copier.</span><br>
<span>Where offices were connected by Cat 5 punched through a hole in the suspended ceiling</span><br>
<span>and dragged around in all directions (including through the A/C ducting) by the tame</span><br>
<span>sparky.</span><br>
<span>Being called in by the BIG suppliers, as the client refused to pay their outrageous, inflated fees</span><br>
<span>to tidy the mess up, and they in turn refused to guarantee their big iron unless the mess was sorted.</span><br>
<span>And of course, there was a Mexican standoff re payment for said Big Iron.</span><br>
<span>To the A/C guys who discovered the problem was all the "crazy" blues wires that were covering the</span><br>
<span>the inlet on their A/C unit- and simply cut them all off.</span><br>
<span>To the large corporation with a head office/warehouse scenario who seemed to have around 200</span><br>
<span>outlets, but at a rough count , some 500 cables coming into a big mess on the floor.</span><br>
<span>Apparently, when the tame sparky ran a new cable, and it didn't work, they just called him back to</span><br>
<span>run another one.</span><br>
<span>A quick visit showed said tame sparky had cable tied all his data cables to warehouse to the 3inch</span><br>
<span>thick, 3 phase, mains cable to the warehouse.</span><br>
<span>Yes, it all worked well (sometimes), until such time as the warehouse plugged in all their electric fork hoists to</span><br>
<span>be re-charged.</span><br>
<span>And my favourite is still- "Can't you just put in one of those raised floors like the big guys have</span><br>
<span>and cover it all up?"</span><br>
<span></span><br>
<span>Yes, I am showing my age, but most of it is common sense.</span><br>
<span>Sorting out the mess afterwards can take a bit of time, but it is mostly a question of following</span><br>
<span>a plan (any plan will do, so long as it can be documented and explained).</span><br>
<span>Colour coding cables helps, and nothing beats a label printer to attach labels to the cables</span><br>
<span>so that everything is simple- input-output etc.</span><br>
<span>The key word is "Structured cabling"- google it, and you will find untold resources and opinions.</span><br>
<span>The rest is just plain hard work and untangling spaghetti.</span><br>
<span>Having a sense of humour, and an account at the scrap metal place for beer money obtained</span><br>
<span>from all the surplus copper helps.</span><br>
<span></span><br>
<span>Have fun.</span><br>
<span></span><br>
<span>Alan Maher</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>On 11/06/2013 12:56 p.m., Ross Wheeler wrote:</span><br>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Hi all.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>I've been asked to assist with the redesign of a medium-sized business's IT infrastructure and am looking for any actual standards or guidelines relevant to Australia. The current site is quite a mess, ad-hoc additions and changes
over many years and multiple people in charge.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Particular issues would include such things as OH&S requirements, best-practice for server/comms/cable racks, server room considerations against most risks etc.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Photos of some "well thought out" installations and racks would be beneficial.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>To be clear, this is not a multi-million dollar datacentre. It's an entity of a couple of hundred staff with perhaps 2 or 3 racks of servers and comms gear, probably one additional enclosure for cable termination, patch etc.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>They want to depart from the old "spaghetti everywhere" environment to something more managable. Suspended floors and rack doors to simply cover the mess up (but leave the underlying problems) are not where they want to be. They're
sick of downtime and network instability because the wrong cable has been unplugged, or in accessing one cable another has been dislodged. Of avoidable downtime because nobody can find or follow anything to fix or work around a problem, etc.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Anyone got anything they can share?</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>TIA,</span><br>
</blockquote>
<blockquote type="cite"><span>RossW</span><br>
</blockquote>
<blockquote type="cite"><span>_______________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>AusNOG mailing list</span><br>
</blockquote>
<blockquote type="cite"><span><a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a></span><br>
</blockquote>
<blockquote type="cite"><span><a href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a></span><br>
</blockquote>
<span></span><br>
<span>_______________________________________________</span><br>
<span>AusNOG mailing list</span><br>
<span><a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a></span><br>
<span><a href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a></span><br>
</div>
</blockquote>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 1pt; BORDER-BOTTOM: medium none; mso-border-top-alt: solid windowtext .5pt">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; mso-border-top-alt: solid windowtext .5pt; mso-padding-alt: 1.0pt 0cm 0cm 0cm"><SPAN
lang=EN-US
style="FONT-SIZE: 9pt; LAYOUT-GRID-MODE: line; mso-bidi-font-size: 10.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-no-proof: yes"><?xml:namespace
prefix = o ns = "urn:schemas-microsoft-com:office:office"
/><o:p> </o:p></SPAN></P></DIV>
<P class=MsoBodyText3 style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-ansi-language: EN-US; mso-no-proof: yes">This
message and its attachments may contain legally privileged or confidential
information. It is for the intended addressee(s) only.</SPAN><SPAN
style="mso-no-proof: yes"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN
style="FONT-SIZE: 9pt; LAYOUT-GRID-MODE: line; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; mso-fareast-language: EN-US; mso-no-proof: yes">If
you are not the intended recipient you must not disclose or use the information
contained in it. If you have received this email in error please notify us
immediately by return email and delete the document.<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US
style="FONT-SIZE: 9pt; LAYOUT-GRID-MODE: line; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-no-proof: yes">Any
views expressed in this message are those of the individual sender, except where
the sender specifies and with authority, states them to be the views of the
Company.<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN
style="FONT-SIZE: 9pt; LAYOUT-GRID-MODE: line; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; mso-fareast-language: EN-US; mso-no-proof: yes">Uecomm
accepts no liability for any damage caused by this email or its attachments due
to viruses, interference, interception, corruption or unauthorised
access.<o:p></o:p></SPAN></P>
<P></P>
<HR>
This e-mail message has been scanned for Viruses and Content and cleared by
<STRONG><FONT color=#ff8000>NetIQ MailMarshal</FONT> </STRONG>
<HR>
</body>
</html>