<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
We have EoSDH equipment (by NSN) which is indeed not able to
auto-negotiate.<br>
The strange thing is that older cards supported auto-negotiation, while
newer ones do not<br>
<br>
--<br>
Tassos<br>
<br>
Mark Tinka wrote on 20/08/2010 11:20:
<blockquote cite="mid:201008201620.43124.mtinka@globaltransit.net"
type="cite">
<pre wrap="">On Friday, August 20, 2010 03:34:24 pm Mikael Abrahamsson
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">+1 on the "use autoneg unless you really have to force
duplex".
</pre>
</blockquote>
<pre wrap="">
We have a customer that connects to us over Gig-E, but their
end is an EoSDH implementation.
As it were, that SDH box either won't auto-neg (which I
can't believe), or they're too scared to make it so.
They're just about the only customer we're hard-coding for,
and less than 1% of our customers don't connect to us via
Ethernet.
Mark.
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
cisco-nsp mailing list <a class="moz-txt-link-abbreviated" href="mailto:cisco-nsp@puck.nether.net">cisco-nsp@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nsp">https://puck.nether.net/mailman/listinfo/cisco-nsp</a>
archive at <a class="moz-txt-link-freetext" href="http://puck.nether.net/pipermail/cisco-nsp/">http://puck.nether.net/pipermail/cisco-nsp/</a></pre>
</blockquote>
<br>
</body>
</html>