<?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 Re: NetApp X66211B-5-C DAC Cable with Cisco 9500-32C in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/NetApp-X66211B-5-C-DAC-Cable-with-Cisco-9500-32C/m-p/459455#M12021</link>
    <description>&lt;P&gt;The &lt;A href="https://hwu.netapp.com/Cable/Index?type=1&amp;amp;cabletype=531660&amp;amp;partnumber=X66211B-5-C" target="_blank" rel="noopener"&gt;X66211B-5-C&lt;/A&gt; cable is a standards-based 5m 100GBASE-CR4 cable that we have formally tested with our hardware products. It is known to interoperate well with many switch vendor products.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco switch software (NX-OS, iOS) is known for actively calling out transceivers and cables as "unsupported" if they are not Cisco-branded products. Furthermore, Cisco TAC might become less helpful if 3rd party cables are being used - often requiring a Cisco-branded part to be used to progress with troubleshooting.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answer for #1:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The easiest path is to purchase Cisco cables, but that implies additional costs.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you search for this issue on the Internet, a common solution is to run these commands to help with 3rd-party compatibility with Catalyst switches (Info from this &lt;A href="https://community.cisco.com/t5/routing/c9500-12q-ios-xe-17-6-4-cvr-qsfp-sfp10g-going-errdisabled/td-p/4772990" target="_blank" rel="noopener"&gt;Cisco Community Forum thread )&lt;/A&gt;&lt;/P&gt;
&lt;PRE style="box-sizing: inherit; overflow: auto; font-family: revert; font-size: 14px; display: block; padding: 0px; margin: 0px; line-height: revert; word-break: break-all; overflow-wrap: break-word; color: #3e3e3e; background-color: #f5f5f5; border: 0px; border-radius: 4px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: revert; font-variant-east-asian: revert; font-variant-alternates: revert; font-variant-position: revert; font-variant-emoji: revert; font-weight: 300; font-stretch: revert; font-optical-sizing: revert; font-size-adjust: revert; font-kerning: revert; font-feature-settings: revert; font-variation-settings: revert; vertical-align: baseline; white-space: pre; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;no errdisable detect cause gbic-invalid&lt;/PRE&gt;
&lt;PRE style="box-sizing: inherit; overflow: auto; font-family: revert; font-size: 14px; display: block; padding: 0px; margin: 0px; line-height: revert; word-break: break-all; overflow-wrap: break-word; color: #3e3e3e; background-color: #f5f5f5; border: 0px; border-radius: 4px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: revert; font-variant-east-asian: revert; font-variant-alternates: revert; font-variant-position: revert; font-variant-emoji: revert; font-weight: 300; font-stretch: revert; font-optical-sizing: revert; font-size-adjust: revert; font-kerning: revert; font-feature-settings: revert; font-variation-settings: revert; vertical-align: baseline; white-space: pre; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;service unsupported-transceiver&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answer for #2 and #3:&lt;BR /&gt;&lt;A href="https://hwu.netapp.com" target="_blank" rel="noopener"&gt;NetApp Hardware Universe&lt;/A&gt; provides formal compatibility information between storage systems and supported back-end (cluster, storage, MetroCluster) switches.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But, NetApp does not formally document cable compatibility for &lt;SPAN data-markjs="true"&gt;front-end&lt;/SPAN&gt; data networking use-cases. We have a more flexible policy. Using 3rd party &lt;SPAN data-markjs="true"&gt;optics&lt;/SPAN&gt;/&lt;SPAN data-markjs="true"&gt;cables&lt;/SPAN&gt; is permitted, as long as they are similar in technology and compliant with applicable &lt;SPAN data-markjs="true"&gt;Ethernet&lt;/SPAN&gt; standards. Generally, you would avoid active copper and active optical technologies, unless we specifically have our own solutions for them (per HWU). If using another vendor’s &lt;SPAN data-markjs="true"&gt;cables&lt;/SPAN&gt;/&lt;SPAN data-markjs="true"&gt;optics&lt;/SPAN&gt;, best to stick with ones that are approved by the device/switch vendor.&lt;/P&gt;
&lt;P style="font-weight: 400;"&gt;In summary, for storage system front-end connectivity, the answer is “Try it – it might work.&amp;nbsp; YMMV”.&lt;/P&gt;
&lt;P style="font-weight: 400;"&gt;From a hardware support perspective, the customer or switch vendor is responsible any component replacement.&lt;/P&gt;</description>
    <pubDate>Fri, 14 Mar 2025 19:00:06 GMT</pubDate>
    <dc:creator>andris</dc:creator>
    <dc:date>2025-03-14T19:00:06Z</dc:date>
    <item>
      <title>NetApp X66211B-5-C DAC Cable with Cisco 9500-32C</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/NetApp-X66211B-5-C-DAC-Cable-with-Cisco-9500-32C/m-p/459441#M12020</link>
      <description>&lt;H4&gt;&lt;STRONG&gt;Issue Overview:&lt;/STRONG&gt;&lt;/H4&gt;&lt;P&gt;We recently deployed a &lt;STRONG&gt;NetApp AFF C800&lt;/STRONG&gt; system with two network cards installed in &lt;STRONG&gt;slots 3 and 5&lt;/STRONG&gt;. For connectivity, we are using the &lt;STRONG&gt;NetApp X66211B-5-C&lt;/STRONG&gt; 5m &lt;STRONG&gt;QSFP28 Direct Attach Copper (DAC) Cable&lt;/STRONG&gt;. However, when connecting this cable to a &lt;STRONG&gt;Cisco Catalyst 9500-32C (Q32)&lt;/STRONG&gt; switch, we receive the error:&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":police_car_light:"&gt;🚨&lt;/span&gt; &lt;STRONG&gt;"Cable unsupported"&lt;/STRONG&gt; &lt;span class="lia-unicode-emoji" title=":police_car_light:"&gt;🚨&lt;/span&gt;&lt;/P&gt;&lt;H4&gt;&lt;STRONG&gt;Questions &amp;amp; Challenges:&lt;/STRONG&gt;&lt;/H4&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;How can we resolve this compatibility issue?&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Is there a site or tool to compare compatibility between NetApp and Cisco switches?&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;How can we verify if the NetApp X66211B-5-C cable is compatible with the Cisco 9500 Q32 or other Cisco switches?&lt;/STRONG&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;U&gt;note:&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Cisco 9500 switch is running the latest firmware&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AhmedAlBatoosh_6-1741888252106.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/30413i63EE201E04135F05/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AhmedAlBatoosh_6-1741888252106.jpeg" alt="AhmedAlBatoosh_6-1741888252106.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AhmedAlBatoosh_7-1741888293926.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/30414i7B17DB6553179189/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AhmedAlBatoosh_7-1741888293926.jpeg" alt="AhmedAlBatoosh_7-1741888293926.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 17:52:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/NetApp-X66211B-5-C-DAC-Cable-with-Cisco-9500-32C/m-p/459441#M12020</guid>
      <dc:creator>AhmedAl-Batoosh</dc:creator>
      <dc:date>2025-03-13T17:52:37Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp X66211B-5-C DAC Cable with Cisco 9500-32C</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/NetApp-X66211B-5-C-DAC-Cable-with-Cisco-9500-32C/m-p/459455#M12021</link>
      <description>&lt;P&gt;The &lt;A href="https://hwu.netapp.com/Cable/Index?type=1&amp;amp;cabletype=531660&amp;amp;partnumber=X66211B-5-C" target="_blank" rel="noopener"&gt;X66211B-5-C&lt;/A&gt; cable is a standards-based 5m 100GBASE-CR4 cable that we have formally tested with our hardware products. It is known to interoperate well with many switch vendor products.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco switch software (NX-OS, iOS) is known for actively calling out transceivers and cables as "unsupported" if they are not Cisco-branded products. Furthermore, Cisco TAC might become less helpful if 3rd party cables are being used - often requiring a Cisco-branded part to be used to progress with troubleshooting.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answer for #1:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The easiest path is to purchase Cisco cables, but that implies additional costs.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you search for this issue on the Internet, a common solution is to run these commands to help with 3rd-party compatibility with Catalyst switches (Info from this &lt;A href="https://community.cisco.com/t5/routing/c9500-12q-ios-xe-17-6-4-cvr-qsfp-sfp10g-going-errdisabled/td-p/4772990" target="_blank" rel="noopener"&gt;Cisco Community Forum thread )&lt;/A&gt;&lt;/P&gt;
&lt;PRE style="box-sizing: inherit; overflow: auto; font-family: revert; font-size: 14px; display: block; padding: 0px; margin: 0px; line-height: revert; word-break: break-all; overflow-wrap: break-word; color: #3e3e3e; background-color: #f5f5f5; border: 0px; border-radius: 4px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: revert; font-variant-east-asian: revert; font-variant-alternates: revert; font-variant-position: revert; font-variant-emoji: revert; font-weight: 300; font-stretch: revert; font-optical-sizing: revert; font-size-adjust: revert; font-kerning: revert; font-feature-settings: revert; font-variation-settings: revert; vertical-align: baseline; white-space: pre; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;no errdisable detect cause gbic-invalid&lt;/PRE&gt;
&lt;PRE style="box-sizing: inherit; overflow: auto; font-family: revert; font-size: 14px; display: block; padding: 0px; margin: 0px; line-height: revert; word-break: break-all; overflow-wrap: break-word; color: #3e3e3e; background-color: #f5f5f5; border: 0px; border-radius: 4px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: revert; font-variant-east-asian: revert; font-variant-alternates: revert; font-variant-position: revert; font-variant-emoji: revert; font-weight: 300; font-stretch: revert; font-optical-sizing: revert; font-size-adjust: revert; font-kerning: revert; font-feature-settings: revert; font-variation-settings: revert; vertical-align: baseline; white-space: pre; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;service unsupported-transceiver&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answer for #2 and #3:&lt;BR /&gt;&lt;A href="https://hwu.netapp.com" target="_blank" rel="noopener"&gt;NetApp Hardware Universe&lt;/A&gt; provides formal compatibility information between storage systems and supported back-end (cluster, storage, MetroCluster) switches.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But, NetApp does not formally document cable compatibility for &lt;SPAN data-markjs="true"&gt;front-end&lt;/SPAN&gt; data networking use-cases. We have a more flexible policy. Using 3rd party &lt;SPAN data-markjs="true"&gt;optics&lt;/SPAN&gt;/&lt;SPAN data-markjs="true"&gt;cables&lt;/SPAN&gt; is permitted, as long as they are similar in technology and compliant with applicable &lt;SPAN data-markjs="true"&gt;Ethernet&lt;/SPAN&gt; standards. Generally, you would avoid active copper and active optical technologies, unless we specifically have our own solutions for them (per HWU). If using another vendor’s &lt;SPAN data-markjs="true"&gt;cables&lt;/SPAN&gt;/&lt;SPAN data-markjs="true"&gt;optics&lt;/SPAN&gt;, best to stick with ones that are approved by the device/switch vendor.&lt;/P&gt;
&lt;P style="font-weight: 400;"&gt;In summary, for storage system front-end connectivity, the answer is “Try it – it might work.&amp;nbsp; YMMV”.&lt;/P&gt;
&lt;P style="font-weight: 400;"&gt;From a hardware support perspective, the customer or switch vendor is responsible any component replacement.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Mar 2025 19:00:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/NetApp-X66211B-5-C-DAC-Cable-with-Cisco-9500-32C/m-p/459455#M12021</guid>
      <dc:creator>andris</dc:creator>
      <dc:date>2025-03-14T19:00:06Z</dc:date>
    </item>
  </channel>
</rss>

