<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic S/N/K-Series 10G Ports may not support Auto-negotiation Changes in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/s-n-k-series-10g-ports-may-not-support-auto-negotiation-changes/m-p/49058#M569</link>
    <description>Article ID: 15084 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series&lt;BR /&gt;
Matrix N-Series DFE&lt;BR /&gt;
K-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Issued the 'set port negotiation...' command in order to modify the local auto-negotiation state, or issued one of the 'set port advertise...' or 'clear port advertise...' (&lt;A href="http://bit.ly/IjeiXP" target="_blank" rel="nofollow noreferrer noopener"&gt;13285&lt;/A&gt;) commands in order to adjust feature advertisement to the attached peer port. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
10-gigabit ports tend to respond to such commands with an error message; for example:S1 Chassis(su)-&amp;gt;&lt;B&gt;set port negotiation tg.1.1 disable&lt;/B&gt;&lt;BR /&gt;
tg.1.1 does not support specified feature.&lt;BR /&gt;
S1 Chassis(su)-&amp;gt;&lt;B&gt;clear port advertise tg.1.1 bpause&lt;/B&gt;&lt;BR /&gt;
failed to get ifMauAutoNegCapAdvertisedBits on port tg.1.1.&lt;BR /&gt;
tg.1.1 failed to be set.&lt;BR /&gt;
S1 Chassis(su)-&amp;gt;&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
Of 10-gigabit port media types (&lt;A href="http://bit.ly/1i9pjey" target="_blank" rel="nofollow noreferrer noopener"&gt;9852&lt;/A&gt;), only a RJ45 "10GBase-T" connection supports auto-negotiation disablement/re-enablement or adjustment of auto-negotiation advertisement. &lt;BR /&gt;
&lt;BR /&gt;
Any other 10G port type - whether copper or fiber - supports neither of these and will generate error messaging, the meaning of which may or may not be clear. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD). &lt;BR /&gt;
&lt;BR /&gt;
Workaround: In the case of a desired advertisement change, if the attached peer device supports the operation then make the change there. The auto-negotiated result will be the highest functionality that the two attached ports are advertised to support.</description>
    <pubDate>Thu, 28 Nov 2013 00:26:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-28T00:26:00Z</dc:date>
    <item>
      <title>S/N/K-Series 10G Ports may not support Auto-negotiation Changes</title>
      <link>https://community.extremenetworks.com/t5/faqs/s-n-k-series-10g-ports-may-not-support-auto-negotiation-changes/m-p/49058#M569</link>
      <description>Article ID: 15084 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series&lt;BR /&gt;
Matrix N-Series DFE&lt;BR /&gt;
K-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Issued the 'set port negotiation...' command in order to modify the local auto-negotiation state, or issued one of the 'set port advertise...' or 'clear port advertise...' (&lt;A href="http://bit.ly/IjeiXP" target="_blank" rel="nofollow noreferrer noopener"&gt;13285&lt;/A&gt;) commands in order to adjust feature advertisement to the attached peer port. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
10-gigabit ports tend to respond to such commands with an error message; for example:S1 Chassis(su)-&amp;gt;&lt;B&gt;set port negotiation tg.1.1 disable&lt;/B&gt;&lt;BR /&gt;
tg.1.1 does not support specified feature.&lt;BR /&gt;
S1 Chassis(su)-&amp;gt;&lt;B&gt;clear port advertise tg.1.1 bpause&lt;/B&gt;&lt;BR /&gt;
failed to get ifMauAutoNegCapAdvertisedBits on port tg.1.1.&lt;BR /&gt;
tg.1.1 failed to be set.&lt;BR /&gt;
S1 Chassis(su)-&amp;gt;&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
Of 10-gigabit port media types (&lt;A href="http://bit.ly/1i9pjey" target="_blank" rel="nofollow noreferrer noopener"&gt;9852&lt;/A&gt;), only a RJ45 "10GBase-T" connection supports auto-negotiation disablement/re-enablement or adjustment of auto-negotiation advertisement. &lt;BR /&gt;
&lt;BR /&gt;
Any other 10G port type - whether copper or fiber - supports neither of these and will generate error messaging, the meaning of which may or may not be clear. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD). &lt;BR /&gt;
&lt;BR /&gt;
Workaround: In the case of a desired advertisement change, if the attached peer device supports the operation then make the change there. The auto-negotiated result will be the highest functionality that the two attached ports are advertised to support.</description>
      <pubDate>Thu, 28 Nov 2013 00:26:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/s-n-k-series-10g-ports-may-not-support-auto-negotiation-changes/m-p/49058#M569</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-28T00:26:00Z</dc:date>
    </item>
  </channel>
</rss>

