You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Trident 24.02 may have issues with NVMe in ONTAP 9.14 when mounting volumes due to the length of the subsystem.
Customers should know about it.
++
here is part of the discussion with the Eng team with some details:
When Trident implemented NVMe driver, the max length of subsystem that ONTAP used was 96 chars and that’s what Trident used. However, ONTAP has changed the max length of NVMe subsystem from 96 chars to 64 chars in 9.14.1.
This ONTAP change breaks the backward compatibility.
For the file system volumes, the NVMe subsystem is a combination of host-node-name and trident UUID . So in this specific case, the name of the subsystem should be “r740xd-1.skc-lab.rd.abcdefghijklm.no + 36 chars of trident UUID = 73 chars
As you can see this would have been fine before 9.14 (as the max length there was 96 char) but for 9.14 it is not and hence the REST call error.
Good thing is that we have already fixed this in Trident and the fix will be available in 24.06.
The user has 3 options:
Wait for the Trident fix in 24.06
Change the node name to something short so that the whole subsystem name is < 64 chars
Try the POC on ONTAP 9.13
Public issues must not contain sensitive information
This issue contains no sensitive information.
The text was updated successfully, but these errors were encountered:
Page URL
https://docs.netapp.com/us-en/trident/trident-get-started/requirements.html
Page title
Requirements
Summary
Hi,
Trident 24.02 may have issues with NVMe in ONTAP 9.14 when mounting volumes due to the length of the subsystem.
Customers should know about it.
++
here is part of the discussion with the Eng team with some details:
Public issues must not contain sensitive information
The text was updated successfully, but these errors were encountered: