<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>Beers always help dull the pain :)</div>
<div><br>
</div>
<div>Here is a link to the ACIF S009:2013 cabling rules <a href="http://www.commsalliance.com.au/__data/assets/pdf_file/0017/39203/S009_2013.pdf">http://www.commsalliance.com.au/__data/assets/pdf_file/0017/39203/S009_2013.pdf</a></div>
<div><br>
</div>
<div>During my 35years in Telcoland I have also witnessed lots of wondrous agricultural solutions across service providers and customers that only many many beers would dare put right! </div>
<div><br>
</div>
<div>Some suggestions-</div>
<div>For any new installations take advantage of the opportunity and plan, ensure quality and have zero tolerance to messy cabling and installation right from the start. With cabinets, select the correct dimensions from the start otherwise the equipment may
not fit, or there may not be enough space for cable management, suggest 800x900 or bigger. Ensure vertical rails are set far enough back to ensure cabinet doors do not squish against the copper/optical patchleads. Airflow, power consumption, powerstrips with
correct ratings are important. Dual power strips from diverse feeds, UPS, equipment stacking with sufficient gaps to allow for airflow and avoid over stacking and high temperatures. Insert cable management to allow for neat runs, use correct lengths of patch
leads. Have a cable labelling standardl to easily identify end points of all patches and for equipment. Keep records in a CMDB and a paper copy on-site of the cabinet layout and all patching details. Ensure cabinets are properly bonded to a telco earth.</div>
<div>Ensure optical patches/cables are also run neatly avoiding macro bends and clean fibres before plugging them in with an appropriate fibre cleaning kit. Use Velcro instead of cable ties where you want to neaten cables so you don't cut your hands on sharp
edges and make it easy for future changes..</div>
<div>With multi cabinets plan for some inter cabinet patching ties which will allow ease, flexibility and neatness. If budget allows add some remote environmental measurement capability for heat, power consumption and maybe even security. Always know where
the keys are and ensure they are labelled to match you cabinet numbers - too many cabinets have been forced open by a screwdriver! If you employ contractors or remote hands to do any changes at remote sites then insist on a photo of their work as a quality
check.</div>
<div><br>
</div>
<div>Cheers</div>
<div>Paul</div>
<div><br>
On 11/06/2013, at 7:49 PM, "Alan Maher" <<a href="mailto:alanmaher@gmail.com">alanmaher@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>That is not (nor has ever been) a requirement in NZ.<br>
Any fool with side cutters and punch down tool can wire their own home,<br>
office or spaceship using a guide off the internet for phone/data/satellite etc.<br>
It is only where the Telco demarcation point exists that determines any standard<br>
or checking.<br>
Hence, many of the circus style events that I have listed (I could add many more)<br>
but there you go. Non mains voltage stuff is pretty much a free for all here.<br>
"Standards" as such, are now being driven through the certification by suppliers such<br>
as Krone, Molnex et al.<br>
I once spent a slightly bleary eyed day in discussion in Melbourne on how to manage<br>
Telco connections, having just spent a late night untangling the shambles created<br>
in a local office by the "Clown with the punch down tool".(Obviously colour-blind)<br>
And I wasn't even able to recover sufficient copper for beer.<br>
But, after comparing notes with my Aussie compatriots, they were kind enough<br>
to buy me one, or two.<br>
That eased the pain.<br>
<br>
Cheers<br>
Alan<br>
<br>
<div class="moz-cite-prefix">On 11/06/2013 9:21 p.m., Ramsay, Paul wrote:<br>
</div>
<blockquote cite="mid:66024459-F5C8-43BE-912B-22DD229B5BC9@uecomm.com.au" type="cite">
<div>I would suggest using a registered cabler who will adhere to the ACA Cabling Rules</div>
<div><br>
</div>
<div><a moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a></span><br>
</blockquote>
<blockquote type="cite"><span><a moz-do-not-send="true" 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 moz-do-not-send="true" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a></span><br>
<span><a moz-do-not-send="true" 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 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" lang="EN-US"><!--?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 style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-ansi-language:
EN-US; mso-no-proof: yes" lang="EN-US">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 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" lang="EN-US">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>
<hr>
This e-mail message has been scanned for Viruses and Content and cleared by <strong>
<font color="#ff8000">NetIQ MailMarshal</font> </strong>
<hr>
</blockquote>
<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>