<?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: IPV6 Mgmt LIFs  suddently become unreachable in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460365#M10209</link>
    <description>&lt;P&gt;No obvious issue found on the network side.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ping6 from the server to SVM’s ipv6 management LIF sporadically works but not always.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Apr 2025 16:17:34 GMT</pubDate>
    <dc:creator>Yosief</dc:creator>
    <dc:date>2025-04-28T16:17:34Z</dc:date>
    <item>
      <title>IPV6 Mgmt LIFs  suddently become unreachable</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460320#M10207</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Several servers are configured to use NetApp&amp;nbsp;&amp;nbsp;Version 9.9.1P2&amp;nbsp; as a storage backend.&amp;nbsp; Each server is connected using IPV6 mgmt/data LIFs to its own SVM. Each server deployed Trident CSI to communicate with its own SVM.&amp;nbsp; These configurations have been working fine without any issues for several months.&amp;nbsp; Suddenly, the IPV6 connection got dropped, and&amp;nbsp; the backend appeared offline from the server side:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&amp;nbsp;tridentctl get backends -n trident&lt;BR /&gt;+-------------+----------------+--------------------------------------+---------+------------+---------+&lt;BR /&gt;| NAME | STORAGE DRIVER | UUID | STATE | USER-STATE | VOLUMES |&lt;BR /&gt;+-------------+----------------+--------------------------------------+---------+------------+---------+&lt;BR /&gt;| nas-backend | ontap-nas | 718e796c-015a-43e4-9008-2186a2fc006c | offline | normal | 0 |&lt;BR /&gt;+-------------+----------------+--------------------------------------+---------+------------+---------+&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;SVMs with IPV4 mgmt/data LIFs work fine.&amp;nbsp; Only IPV6 is not working.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;I can ping the&amp;nbsp; SVM's LIFs gateway IPV6 address but not the mgmt LIF nor the data LIF.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;IPv6 is enabled on both cluster nodes:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;netapp-cluster-001::&amp;gt; network options ipv6 show&lt;/P&gt;&lt;P&gt;IPv6 Enabled: true&lt;BR /&gt;Router Advertisement (RA) Processing Enabled: true&lt;/P&gt;&lt;P&gt;From trident logs:&lt;/P&gt;&lt;P&gt;time="2025-04-24T06:47:15Z" level=error msg="Could not initialize storage driver." crdControllerEvent=add error="error initializing ontap-nas driver; could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post \"https://[xxxx:xxxx:xxx::2]/servlets/netapp.servlets.admin.XMLrequest_filer\": dial tcp [xxxx:xxxx:xxx::x]:443: connect: no route to host"&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;time="2025-04-25T01:16:53Z" level=error msg="API invocation failed. Post \"https://[xxxx:xxxx:xxx::2]/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea what caused the IPV6 connectivity to stop working.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Yosief G&lt;/P&gt;</description>
      <pubDate>Fri, 25 Apr 2025 01:30:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460320#M10207</guid>
      <dc:creator>Yosief</dc:creator>
      <dc:date>2025-04-25T01:30:34Z</dc:date>
    </item>
    <item>
      <title>Re: IPV6 Mgmt LIFs  suddently become unreachable</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460344#M10208</link>
      <description>&lt;P&gt;After further investigation, we found that the issue might be within the network between the NetApp and the servers.&amp;nbsp; &amp;nbsp;Will update the outcome.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Apr 2025 17:50:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460344#M10208</guid>
      <dc:creator>Yosief</dc:creator>
      <dc:date>2025-04-25T17:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: IPV6 Mgmt LIFs  suddently become unreachable</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460365#M10209</link>
      <description>&lt;P&gt;No obvious issue found on the network side.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ping6 from the server to SVM’s ipv6 management LIF sporadically works but not always.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Apr 2025 16:17:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/IPV6-Mgmt-LIFs-suddently-become-unreachable/m-p/460365#M10209</guid>
      <dc:creator>Yosief</dc:creator>
      <dc:date>2025-04-28T16:17:34Z</dc:date>
    </item>
  </channel>
</rss>

