<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:Calibri;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">While this isn’t the first time that we’ve seen this issue, it is the first time that I’ve posted to try to resolve it rather than work around it.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have a Brocade/Foundry RX-4 with (2) 24 port fiber cards (RX-BI-24F) and (2) 24 port copper cards (RX-BI-24C). One of our transit providers is NTT, with whom we have a single GigE circuit delivered over single mode fiber. It is a multi-km
run, from 800 South Hope to One Wilshire, then on to 900 North Alameda in LA, but well within normal LX transceiver range. While we see light (neg 11 received) in optical monitoring, we cannot get a link to establish. No combination of auto-negotiate / manual
speed settings on our side or NTT’s has been able to get a link up.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If we use the same optic in a FESX424, the link comes up immediately. In fact, any non generic optic works in the FESX424, but will not generate a link on the RX. Other links come up without a problem on the RX, including over SMF and MMF,
and using the same optic. The link also fails to come up in a CES2048F. </p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We previously had the same issue on a Cogent circuit in Phoenix using a CER2024F-RT and on a Cogent circuit in Philadelphia using a RX-4. Like NTT, they were running Cisco on their end. In each of those cases, we had to work around the
issue by inserting a basic Layer 2 Cisco device in between and doing either a MMF or copper connection between. This, however, is not really a solution.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does anyone have any insight as to what we can do here? NTT is running Champion One optics. While we asked them to try switching out optics, they only had optics from the same manufacturer, so it didn’t help. We’ve tried using genuine Brocade,
Approved Optics coded to Brocade, and Finisair on our end. None of them have made any difference at all. The next effort will be to try to find some optics of the same manufacturer as NTT (Champion One), though this shouldn’t be necessary unless I am missing
something.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
</div>
</body>
</html>