PSTK cmdlet add-ncnfsservice is not creating correct service properties

StevePutre — Thu, 13 Feb 2025 16:38:57 GMT

We found what appears to be a bug or unintended behavior with add-ncnfsservice.

We want to create a new NFS service configuration on a vserver, but we want to have NFSv4.0 and NFSv4.1 disabled; only NFSv3 enabled.

We first obtain a default configuration:

$nfs_config = get-NcNfsService -template

If we examine the template values, we can see that NFSv3 is enabled and NFSv4 is disabled:
(I have shortened the output but I have attached the full output to my post)

PS> $nfs_config

Vserver GeneralAccess IsNfsv3 IsNfsv4 IsNfsv41 DefaultWindowsUser
------- ------------- ------- ------- -------- ------------------
True True False False

Using this template, I create a new NFS service on my SVM:
PS> add-NcNfsService -vservercontext XXXXXX -attributes $nfs_config

Vserver GeneralAccess IsNfsv3 IsNfsv4 IsNfsv41 DefaultWindowsUser
------- ------------- ------- ------- -------- ------------------
XXXXXXX True True True True

If I go to the OnTAP CLI and perform a "nfs show", it shows that v4.0 and v4.1 are enabled, which is not the desired config.

Please comment and provide a resolution for this.

Re: PSTK cmdlet add-ncnfsservice is not creating correct service properties

saharsh — Tue, 08 Apr 2025 05:20:13 GMT

Hi Steve,

We have identified the issue and will address it in the upcoming PSTK release.

topic Re: PSTK cmdlet add-ncnfsservice is not creating correct service properties in Microsoft Virtualization Discussions

PSTK cmdlet add-ncnfsservice is not creating correct service properties

Re: PSTK cmdlet add-ncnfsservice is not creating correct service properties