<?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 not a VDX - but a SFP NIC phys link - needs cable re-insertion to come back up. in Data Center (VDX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-vdx/not-a-vdx-but-a-sfp-nic-phys-link-needs-cable-re-insertion-to/m-p/6279#M171</link>
    <description>Hi.&lt;BR /&gt;It's not about my VDXes this time, yet I hope an expert or two could comment.&lt;BR /&gt;I have a couple of boxes which sport Emulex Corporation OneConnect cards, 1 NIC each box, which NICs connects directly (so directly attached cables) to each other (no switches) and those work, meaning communicate, but... only till next reboot!? After which reboot such a "link" can only be brought back through physical re-connection - suffices to pull SFP cable out from one box and a second later push it back.&lt;BR /&gt;&lt;BR /&gt;So I wonder if there can be some kernel/module (Linux) parameters which can be filled with - would anybody know? - in order to remedy this weird behaviour.&lt;BR /&gt;many thanks, L.&amp;nbsp;&lt;BR /&gt;</description>
    <pubDate>Tue, 23 Nov 2021 22:04:00 GMT</pubDate>
    <dc:creator>Pawel_Eljasz</dc:creator>
    <dc:date>2021-11-23T22:04:00Z</dc:date>
    <item>
      <title>not a VDX - but a SFP NIC phys link - needs cable re-insertion to come back up.</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/not-a-vdx-but-a-sfp-nic-phys-link-needs-cable-re-insertion-to/m-p/6279#M171</link>
      <description>Hi.&lt;BR /&gt;It's not about my VDXes this time, yet I hope an expert or two could comment.&lt;BR /&gt;I have a couple of boxes which sport Emulex Corporation OneConnect cards, 1 NIC each box, which NICs connects directly (so directly attached cables) to each other (no switches) and those work, meaning communicate, but... only till next reboot!? After which reboot such a "link" can only be brought back through physical re-connection - suffices to pull SFP cable out from one box and a second later push it back.&lt;BR /&gt;&lt;BR /&gt;So I wonder if there can be some kernel/module (Linux) parameters which can be filled with - would anybody know? - in order to remedy this weird behaviour.&lt;BR /&gt;many thanks, L.&amp;nbsp;&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Nov 2021 22:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/not-a-vdx-but-a-sfp-nic-phys-link-needs-cable-re-insertion-to/m-p/6279#M171</guid>
      <dc:creator>Pawel_Eljasz</dc:creator>
      <dc:date>2021-11-23T22:04:00Z</dc:date>
    </item>
  </channel>
</rss>

