If this is DART 6.0 then the file to edit for NFSv4 is different, look at the documentation (I think it's "config")  Claude
My attempts to limit an NFS export to nfsv4-only fail on the Celerra simulator (NAS 6.0.36). This worked okay for me with NAS 5.6.43. I have correctly changes netd from hivers=3 to hivers=v4 and rebooted as documented. The command fails claiming NFS was started with V3 inspite of the change to .../netd.  I even rebooted the whole appliance out of desperation.  My complete sequence of command line configurations are shown below. Please advise.    server_param server_2 -facility nfsv4 -modify domain -value eng.e-dialog.com  cat /nas/server/slot_2/netd routed nfs start hivers=4 statd lockd pax rquotad action=start ndmp port=10000 xattrp snmpd kerbinit  server_cpu server_2 -reboot now /nas/sbin/uc_config -convert start 8859-1.txt -mover server_2 /nas/sbin/uc_config -convert start big5.txt -mover server_2 /nas/sbin/uc_config -convert start 8859-1.txt -mover server_2  nas_volume -name stv1 -create -Stripe 1024000 d7,d8,d9,d10 nas_volume -name stv2 -create -Stripe 1024000 d7,d8,d9,d10 nas_volume -name stv2 -create -Stripe 1024000 d11,d12,d13,d14 nas_volume -name mtv1 -create -Meta stv1 nas_volume -name mtv2 -create -Meta stv2  nas_fs -name queue -create mtv1 nas_fs -name mm3 -create mtv2  server_mountpoint server_2 -create /queue server_mountpoint server_2 -create /mm3  server_mount server_2 -option accesspolity=MIXED,nooplock,rwlock,nfsv4delegation=NONE queue /queue server_mount server_2 -option accesspolity=MIXED,nooplock,rwlock,nfsv4delegation=NONE mm3 /mm3 server_export server_2 -Protocol nfs -option access=10.0.13.0/255.255.252.0,root=10.0.13.0/255.255.252.0,nfsv4only -comment 'NFS v4 only export for queue' /queue server_2 : Error 22: server_2 : Invalid argument Export Error: Nfs has been started with HI_VERS 3. Cannot export as nfsv4 only.
Failures with: server_export -option nfsv4only