<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I guess if its just Layer 1 then it doesn’t matter, Fibre-1 should go to Fibre 1, Fibre 2 should go to Fibre 2?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Unless you suggest crossing over ports from one end to the other </span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It Doesn’t become RX or TX until you plug something into it..<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>S<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ausnog-bounces@lists.ausnog.net [mailto:ausnog-bounces@lists.ausnog.net] <b>On Behalf Of </b>Andrew Warburton<br><b>Sent:</b> Wednesday, June 13, 2012 3:00 PM<br><b>To:</b> john@netniche.com.au<br><b>Cc:</b> ausnog@ausnog.net<br><b>Subject:</b> Re: [AusNOG] TX/RX Conventions<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hey guys,<o:p></o:p></p><div><p class=MsoNormal>No need to get too complicated, this is just Layer 1 ie. Physical layer, no rocket science required.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Andrew<o:p></o:p></p><div><p class=MsoNormal>On 13 June 2012 13:45, <<a href="mailto:john@netniche.com.au" target="_blank">john@netniche.com.au</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>On 13.06.2012 07:21, Tom Sykes wrote:<o:p></o:p></p><p class=MsoNormal>I'm interested to understand which conventions/standards (if any) are<br>being used by operators to identify the TX/RX in fibre patching<br>panels/trays - in environments like a meet me room or datacentre.<o:p></o:p></p><p class=MsoNormal><br>Hi Tom,<br><br>I'm not aware of any convention other than the "flip it if it doesn't work and curse shutdown-by-default policies".<br><br>Cisco appear to place TX on the "left" of the optics (first port). The LC connector specification chickens out from making a distinction, and the SFP/SFP+ specifications also don't make a commitment (they allow for copper and single-fibre, after all).<br><br>From a purely logical point of view, TX should be on the "first" port of a group. This is because it's difficult to test for the absence of a signal, so if only 1 of two ports has a signal on it that should ideally be the first one you try.<br><br>Otherwise, you're condemning engineers everywhere to a sequence of try port 1, nope, try port 2 - that's a 30 second gain in productivity for the industry each time they plug in a patch lead :)<br><br>John<br><br>_______________________________________________<br>AusNOG mailing list<br><a href="mailto:AusNOG@lists.ausnog.net" target="_blank">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><o:p></o:p></p></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><p class=MsoNormal><strong><span style='font-family:"Arial","sans-serif";color:#333399'>Andrew Warburton</span></strong><o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Business Development Manager | Wholesale</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-NZ style='font-size:8.0pt;font-family:"Tahoma","sans-serif";color:black'>AAPT Limited, 180 - 188 Burnley St Richmond, VIC 3121<br></span><strong><span lang=EN-NZ style='font-size:7.5pt;font-family:"Arial","sans-serif";color:black'>P +61 3 </span></strong><span lang=EN-NZ style='font-size:7.5pt;font-family:"Arial","sans-serif";color:black'>8308 3838 | <strong><span style='font-family:"Arial","sans-serif"'>M +61 426 779 333</span></strong></span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div><pre>This communication, including any attachments, is confidential. If you are not the intended<o:p></o:p></pre><pre>recipient, you should not read it - please contact me immediately, destroy it, and do not<o:p></o:p></pre><pre>copy or use any part of this communication or disclose anything about it.<o:p></o:p></pre><pre><o:p> </o:p></pre></div></body></html>