Hello,
Several servers are configured to use NetApp Version 9.9.1P2 as a storage backend. Each server is connected using IPV6 mgmt/data LIFs to its own SVM. Each server deployed Trident CSI to communicate with its own SVM. These configurations have been working fine without any issues for several months. Suddenly, the IPV6 connection got dropped, and the backend appeared offline from the server side:
tridentctl get backends -n trident
+-------------+----------------+--------------------------------------+---------+------------+---------+
| NAME | STORAGE DRIVER | UUID | STATE | USER-STATE | VOLUMES |
+-------------+----------------+--------------------------------------+---------+------------+---------+
| nas-backend | ontap-nas | 718e796c-015a-43e4-9008-2186a2fc006c | offline | normal | 0 |
+-------------+----------------+--------------------------------------+---------+------------+---------+
SVMs with IPV4 mgmt/data LIFs work fine. Only IPV6 is not working.
I can ping the SVM's LIFs gateway IPV6 address but not the mgmt LIF nor the data LIF.
IPv6 is enabled on both cluster nodes:
netapp-cluster-001::> network options ipv6 show
IPv6 Enabled: true
Router Advertisement (RA) Processing Enabled: true
From trident logs:
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"
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)"
Any idea what caused the IPV6 connectivity to stop working.
Thank you
Yosief G
